dan-claude-bot 13aa499dad fix: a -dev endstate is always work — the post-release bump must not run red ... The four-state table called '-dev but changed' half a ceremony and refused — but that state IS the mandatory post-release bump PR (bare -> X.Y.(Z+1)-dev after every release), which would have put a red run on main once per release, forever. A tree that ends -dev is by definition not a release: every such merge is work, and no-ops green with a NOTICE. The red verdicts now guard only bare endstates. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-19 15:40:48 +00:00
..
scripts	feat(release): publish the tagged version's changelog section (#83)	2026-07-18 22:17:51 +00:00
workflows	fix: a -dev endstate is always work — the post-release bump must not run red	2026-07-19 15:40:48 +00:00
labeler.yml	feat: label automation — the state reconciler, path-scoped labeler, and CONTRIBUTING	2026-07-18 18:31:51 +00:00