chore(commands): add /prerelease, update /precommit CHANGELOG step

- Add .claude/commands/prerelease.md with full pre-release checklist
- Remove "I must do this manually" from precommit CHANGELOG step —
  the agent handles it

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: nanotaboada

.claude/commands/precommit.md

@@ -1,8 +1,10 @@
 Run the pre-commit checklist for this project:
 
-1. Remind me to update `CHANGELOG.md` `[Unreleased]` section (Added / Changed / Fixed / Removed) — I must do this manually.
+1. Update `CHANGELOG.md` `[Unreleased]` section — add an entry under the
+   appropriate subsection (Added / Changed / Fixed / Removed) describing the
+   changes made, referencing the issue number.
 2. Run `uv run flake8 .` — must pass.
 3. Run `uv run black --check .` — must pass (run `uv run black .` to auto-fix).
 4. Run `uv run pytest --cov=./ --cov-report=term` — all tests must pass, coverage must be ≥80%.
 
-Run steps 2–4, report the results clearly, then propose a branch name and commit message for my approval using the format `type(scope): description (#issue)` (max 80 chars; types: `feat` `fix` `chore` `docs` `test` `refactor` `ci` `perf`). Do not create the branch or commit until I explicitly confirm.
+Run steps 1–4, report the results clearly, then propose a branch name and commit message for my approval using the format `type(scope): description (#issue)` (max 80 chars; types: `feat` `fix` `chore` `docs` `test` `refactor` `ci` `perf`). Do not create the branch or commit until I explicitly confirm.

.claude/commands/prerelease.md

@@ -0,0 +1,39 @@
+Run the pre-release checklist for this project:
+
+1. **Detect current release and propose next**: Read `CHANGELOG.md` for the
+   coach naming convention (A–Z table) and the most recent release heading.
+   Run `git tag --sort=-v:refname` to confirm the latest tag. Determine the
+   next codename (next letter in the A–Z sequence after the current one) and
+   infer the version bump from the `[Unreleased]` section: any entry marked
+   BREAKING → MAJOR; entries under Added → MINOR; only Changed/Fixed/Removed
+   → PATCH. Present the proposed `vX.Y.Z-{codename}` and ask me to confirm
+   or override before proceeding. Do not continue until I confirm.
+
+2. **Verify working tree**: Confirm we are on `master` with a clean working
+   tree. Pull latest if behind remote.
+
+3. **Create release branch**: `release/vX.Y.Z-{codename}`.
+
+4. **Update CHANGELOG.md**: Move all content under `[Unreleased]` to a new
+   release heading `[X.Y.Z - Codename] - {today's date}`. Leave a fresh
+   `[Unreleased]` with all four empty subsections:
+   Added / Changed / Fixed / Removed.
+
+5. **Propose commit and ask for confirmation**:
+   `docs(changelog): release vX.Y.Z Codename`
+   Do not commit until I confirm.
+
+6. **After confirmation**: commit, push the branch, open a PR into `master`.
+
+7. **Stop and wait for my explicit confirmation** that:
+   - All CI checks have passed
+   - CodeRabbit review comments have been addressed
+   - The PR has been merged into `master`
+   Do not create or push the tag until I give this confirmation.
+
+8. **After I confirm**: pull `master`, then propose the annotated tag
+   `vX.Y.Z-{codename}` with message `Release X.Y.Z - Codename` and ask for
+   approval. Do not tag until I confirm.
+
+9. **After confirmation**: create and push the tag. The CD pipeline triggers
+   automatically.