release-sync

Release Content Sync

Sync the latest OrchestKit release to external knowledge systems.

CC ≥ 2.1.118 (M122): Sync triggers on the new claude plugin tag annotated tag (in addition to plain git tag). The tag's annotation embeds the plugin manifest version, which release-sync uses as the canonical source-of-truth for the version being synced. See src/skills/chain-patterns/references/plugin-tag.md.

What This Does

1. Reads the latest CHANGELOG entry, CLAUDE.md, and hook README
2. Updates the OrchestKit NotebookLM KB notebook with fresh sources
3. Ingests the release digest into HQ Knowledge Base (if available)
4. Optionally generates a new podcast from the updated notebook

Prerequisites

• MCP servers: notebooklm-mcp and/or hq-content
• NotebookLM notebook ID stored in .claude/release-sync-config.json

Step 1: Detect Version and Read Sources

# Read current version from CLAUDE.md
version = Grep(pattern="Current.*\\d+\\.\\d+\\.\\d+", path="CLAUDE.md")

# Read CHANGELOG — extract latest release section
changelog = Read("CHANGELOG.md", limit=80)

# Read hook architecture summary
hook_readme = Read("src/hooks/README.md", limit=100)

# Read CLAUDE.md for project overview
claude_md = Read("CLAUDE.md")

Step 2: Load Config

config = Read(".claude/release-sync-config.json")
# Expected format:
# {
#   "notebooklm_notebook_id": "0a05e680-e33b-4d8c-94b2-5df26a1af329",
#   "hq_kb_project": "orchestkit"
# }

If config doesn't exist, prompt user:

AskUserQuestion(questions=[{
  "question": "NotebookLM notebook ID for OrchestKit KB?",
  "header": "Configuration",
  "options": [
    {"label": "Use default", "description": "OrchestKit v7 — Complete KB (0a05e680...)"},
    {"label": "I'll provide", "description": "Enter a custom notebook ID"}
  ]
}])

Step 2b: Choose Sync Targets

Ask for the four target values: notebooklm, hq_kb, slack, notes.

# Skip the form when targets are explicit:
#   /ork:release-sync --targets=notebooklm,slack  → skip, use those
#
# Otherwise ask. This used to prefer an ork-elicit MCP form and fall back to
# AskUserQuestion; the server was retired (EPIC C mechanism 11) because
# AskUserQuestion is the CC-native surface for this and a permanent MCP tool
# slot to restate it was the parallel mechanism. One path now.
#
# ALL targets default to False — OrchestKit is open-source and these targets
# (notebook IDs, HQ KB, Slack) are user-private infrastructure the plugin
# cannot assume is configured. The user explicitly opts in.
targets = {
  "notebooklm": ask_yn("Push to NotebookLM?", default=False),
  "hq_kb":      ask_yn("Push to HQ KB?",       default=False),
  "slack":      ask_yn("Announce in Slack?",   default=False),
  "notes":      ""
}