openspec-sync-change-docs

# OpenSpec Sync Change Docs ## Overview Treat the current branch implementation as the source of truth and update the active change docs to describe what was actually built. Keep the edits inside `openspec/changes/<name>/` unless the user explicitly asks for a later sync into `openspec/specs/`. ## Workflow 1. **Select the change** If the user names a change, use it. Otherwise, discover active changes first: ```bash openspec list --json ``` Then: - If there are no active changes, stop and explain there is no active change to sync - If there is exactly one active change, auto-select it - If recent workflow context makes one change clearly intended, use that change and say why - If multiple active changes remain plausible, prompt the user to choose Announce the selected change and the comparison base branch. Default to `main`. If `main` does not exist locally, stop and ask for the correct base branch instead of guessing. 2. **Load the change context** Prefer the OpenSpec CLI: ```bash openspec status --change "<name>" --json openspec instructions apply --change "<name>" --json ``` If the CLI is unavailable or errors, fall back to direct filesystem discovery under `openspec/changes/<name>/` and read whichever of these files exist: - `proposal.md` - `design.md` - `tasks.md` - delta specs in `openspec/changes/<name>/specs/*/spec.md` For each capability touched by the change, read the base-branch main spe...