ceremony-ci-probe/changelog.d
claude-bot-andresmgsl 0b77d4b860 fix: the CONSUMERS.md stub's issues: types match the caller's, parity-tested
The stub published [opened, labeled, unlabeled, assigned, unassigned,
closed] while ceremony's own caller listens on eight types — PR #32's
70db91f widened the caller by edited and reopened and the stub never
followed. Both are load-bearing: an edited body rewrites the Blocked-by
declaration the reconcile sweep parses, and a reopened issue re-enters
the queue wearing labels derived at close (#144).

The stub's list is now byte-identical to the caller's, a parity row in
test/labels.test.sh keeps it that way (red on a dropped type, a drift,
or a reorder in one file only), and one adoption note names the tag the
widened list rides in on. The caller does not narrow.

Closes #144

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-24 13:43:35 +00:00
..
130.md docs: the additive-scope contract in CONSUMERS/LABELS; changelog fragment 2026-07-24 11:57:10 +00:00
131.md fix: format changelog fragment as an entry 2026-07-24 12:43:17 +00:00
134.md test: root-commit fixtures — (none) base, D2 loud-death pin, e2e chain 2026-07-24 12:16:04 +00:00
137.md fix: review_requested wakes the sweep — blocker:unrequested clears when the ask lands 2026-07-24 12:50:09 +00:00
139.md fix: a queue-cancelled duplicate check is not a verdict 2026-07-24 12:34:51 +00:00
144.md fix: the CONSUMERS.md stub's issues: types match the caller's, parity-tested 2026-07-24 13:43:35 +00:00
145.md docs: capture reviewer queue mechanics 2026-07-24 13:12:21 +00:00
README.md feat: convert Unreleased entries to changelog.d fragments 2026-07-24 11:11:23 +00:00

changelog.d/ — the next release's section, one fragment per issue

Machine-assembled by bin/changelog-assemble (#112): every PR that changes behavior writes one file here — <issue>.md, the exact prose that will be published, nothing else — and the release PR folds them all into the next ## X.Y.Z — DATE section of CHANGELOG.md, consuming them. Distinct filenames never conflict, which is this directory's whole reason to exist. This README is the marker that keeps the directory tracked when it holds no fragments (#112 D1) — changelog-armed refuses a tree without it; do not delete it.