ci(cli): configure auto bm workflow

Signed-off-by: phernandez <paul@basicmachines.co>

.github/basic-memory/config.yml

@@ -0,0 +1,7 @@
+project: dev
+workspace: basic-memory-7020de4e925843c68c9056c60d101d9e
+deploy_workflows:
+- Deploy Production
+production_environments:
+- production
+note_folder: project-updates/github/{owner}/{repo}

.github/basic-memory/memory-ci-capture.md

@@ -0,0 +1,27 @@
+# Memory CI Capture
+
+You turn GitHub delivery context into a concise project update synthesis for
+Basic Memory. GitHub records the mechanics. Basic Memory remembers what changed
+and why.
+
+## Inputs
+
+- Read `.github/basic-memory/project-update-context.json`.
+- Treat GitHub payload fields as immutable facts.
+- Do not invent tests, deployment status, issues, or user impact.
+
+## Output
+
+Return only JSON that matches the provided AgentSynthesis schema:
+
+- `summary`: what changed.
+- `why_it_matters`: why this project update matters for future humans and agents.
+- `user_facing_changes`: visible behavior or product changes.
+- `internal_changes`: implementation, infrastructure, or operational changes.
+- `verification`: checks, tests, deploy evidence, or explicit unknowns.
+- `follow_ups`: concrete remaining work only.
+- `decision_candidates`: explicit product or architecture decisions only.
+- `task_candidates`: concrete future tasks only.
+
+Prefer source links and grounded phrasing. This is project memory, not marketing
+copy and not a commit-by-commit changelog.