Update to Basic Memory Cloud

{
  "name": "memory-ci-capture",
  "description": "Synthesize GitHub delivery context into a concise Basic Memory project update. Use in CI after `bm ci collect` prepares a ProjectUpdateContext; return only structured AgentSynthesis JSON for `bm ci publish`.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 338
    }
  ],
  "skill_md_contents": "---\nname: memory-ci-capture\ndescription: Synthesize GitHub delivery context into a concise Basic Memory project update. Use in CI after `bm ci collect` prepares a ProjectUpdateContext; return only structured AgentSynthesis JSON for `bm ci publish`.\n---\n\n# Memory CI Capture\n\nTurn a meaningful GitHub delivery moment into project memory. GitHub records the\nmechanics. Basic Memory remembers what changed and why.\n\n## Inputs\n\nRead the `ProjectUpdateContext` JSON produced by `bm ci collect` at\n`.github/basic-memory/project-update-context.json`. Treat it as the immutable\nsource of truth for repository, event type, PR number, workflow run, SHA, source\nURL, timestamps, and deployment environment.\n\nDo not invent tests, deploy checks, linked issues, product impact, or decisions.\nIf evidence is absent, say so briefly in `verification` or leave the field empty.\n\n## Output\n\nReturn only JSON matching the `AgentSynthesis` shape:\n\n```json\n{\n  \"summary\": \"What changed.\",\n  \"why_it_matters\": \"Why this update matters for future humans and agents.\",\n  \"user_facing_changes\": [],\n  \"internal_changes\": [],\n  \"verification\": [],\n  \"follow_ups\": [],\n  \"decision_candidates\": [],\n  \"task_candidates\": []\n}\n```\n\n## Synthesis Rules\n\n- Prefer a short explanation over a commit-by-commit changelog.\n- Preserve intent, changed behavior, source links, verification evidence present\n  in the context, and concrete follow-ups.\n- Put explicit product or architecture decisions in `decision_candidates` only\n  when the source context clearly contains them.\n- Put future work in `task_candidates` only when it is concrete enough to act on.\n- Keep the tone factual and useful. This is project memory, not marketing copy.\n\n## Event Guidance\n\nFor merged pull requests, focus on why the PR existed, what area changed, what\nissues it advanced or closed, and what verification evidence appears in the\ncontext.\n\nFor production deploys, focus on what reached production, the deployed SHA,\nenvironment, workflow run, and verification evidence. Do not overclaim success\nbeyond the workflow and source facts.\n"
}