`release 00.5.0` passed the newer-version guard (its key equals 0.5.0's)
and the exact-string duplicate check, then wrote `## [00.5.0]` and deleted
the entries before `check` rejected the file (Pullfrog on #82).
- Versions take no leading zeros, in `release`, `notes` and the headings
`check` accepts.
- `release` checks the file it is about to write and changes nothing
unless it passes, so any other bad result also leaves CHANGELOG.md and
the entries as they were.
Claude-Session: https://claude.ai/code/session_01RqPPVeVDrnLoP7NUZmLRxY
`release 0.4.9` on a changelog topped by 0.5.0 wrote the section above it
with a backwards compare link and deleted the entries; `check` caught the
file only afterwards (Pullfrog on #82). The version is now compared before
anything is written.
Also: the #78 entry names the calendar's open offers and the session API's
read-path allowlist, added there since.
Claude-Session: https://claude.ai/code/session_01RqPPVeVDrnLoP7NUZmLRxY
Release notes were written by hand on GitHub at tag time, so the contents
of a stacked release had to be pieced together from every PR, and output
changes that scripts and agents rely on were easy to miss.
- CHANGELOG.md backfills every published release (0.2.0 to 0.4.0) from its
GitHub notes, verbatim.
- A PR adds changes/unreleased/<branch-name>.md instead of editing
CHANGELOG.md, so stacked PRs never conflict. changes/README.md gives the
sections, including Output Changes for JSON, MCP and error-code changes.
- scripts/changelog.sh: `check` validates entries and CHANGELOG.md,
`release X.Y.Z` folds the entries into a new section (ordered by PR), and
`notes X.Y.Z` prints a section as GitHub release notes.
- The release workflow sets the GitHub notes from the tag's section.
- New flake check `changelog` runs scripts/changelog-test.sh; both scripts
are shellchecked.
- Entries for 0.5.0: #73, #74, #75, #78, #79, #80, #81 and this PR.
Claude-Session: https://claude.ai/code/session_01RqPPVeVDrnLoP7NUZmLRxY
