update-changeloglisted

# Update Changelog ## Step 0 — Bind the version If an argument that looks like a version number was provided (e.g., `v1.2.0`, `1.2.0`, `v2.0.0-rc.1`), store it as `VERSION`, normalising to include a `v` prefix if absent. Otherwise VERSION defaults to `Unreleased`. **STOP gate:** Verify `CHANGELOG.md` exists in the repo root using the Read tool. If it does not exist, report "CHANGELOG.md not found at repo root." and halt. ## Step 1 — Get today's date Run `date +%Y-%m-%d` and store the result as `TODAY`. ## Step 2 — Draft entries from commits Run: ```sh git log --oneline main..HEAD ``` Store the result as `COMMIT_LIST`. If the command fails, report the error and halt. **STOP gate:** If `COMMIT_LIST` is empty, tell the user: "No commits found ahead of `main` — nothing to changelog. Is that expected?" and halt. Draft changelog entries from `COMMIT_LIST`. Group them under `### Category` subheadings. Use the categories that best match the changes (e.g., `### New Skills`, `### PDCA Framework Redesigns`, `### Beads and Workflow`, `### Build and Distribution`, `### Dependency Updates`, `### Documentation`). Prefer the established category names from the existing changelog over inventing new ones. Classify each entry as one of: - **Regular entry** — new feature, bug fix, config change, anything user-visible - **Migration note** — anything requiring user action: renamed files or commands, removed options, changed install paths, new required config keys Skip internal-only c