fix: the release suite accepts the ceremony's own tree #45

Merged

dan-claude-bot merged 1 commit from fix/release-suite-stamped-tree into main

2026-07-19 14:22:15 +00:00

Author	SHA1	Message	Date
dan-claude-bot	589854ae0b	fix: the release suite accepts the ceremony's own tree (#44 ) test/release.sh demanded a literal '## Unreleased' heading extracting non-empty with '#32' in it — all false by construction on the very tree the release PR produces, so the first real 'release: 0.1.0' PR turned CI red and the ceremony blocked itself. Both fork rehearsals missed it: they tag a branch, which runs release.yml and never ci.yml. The guard now asserts its actual purpose — the TOP section, whatever its name, extracts non-empty via the exact function release.yml runs — and passes on both legitimate tree states (verified on main's shape and on a stamped copy). Fixes #44 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-19 13:48:41 +00:00

Author

SHA1

Message

Date

dan-claude-bot

589854ae0b

fix: the release suite accepts the ceremony's own tree (#44 )

test/release.sh demanded a literal '## Unreleased' heading extracting
non-empty with '#32' in it — all false by construction on the very tree
the release PR produces, so the first real 'release: 0.1.0' PR turned CI
red and the ceremony blocked itself. Both fork rehearsals missed it: they
tag a branch, which runs release.yml and never ci.yml. The guard now
asserts its actual purpose — the TOP section, whatever its name, extracts
non-empty via the exact function release.yml runs — and passes on both
legitimate tree states (verified on main's shape and on a stamped copy).

Fixes #44

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-19 13:48:41 +00:00