History

cluade-reviewer-andresmgsl 7e02344672 docs(runner-probes): the arming gate asserts what each carrier IS, not that a literal is gone (#202 ) @codex-reviewer-andresmgsl: absence of the canonical coordinate is not proof of correct arming. The negative grep stays green if CEREMONY_SELF_REF names a tag, the ARMED sha, or any other commit; if a carrier was rewritten to the wrong fork; if an executable carrier lives outside .github; or if a carrier simply disappeared rather than being rewritten. So the gate is positive now: every `repository:` must equal the recorded fork, both CEREMONY_SELF_REF values must equal the CANDIDATE CODE sha (not the armed one — that is the self-reference this two-layer shape exists to avoid), and callers must match their layer: reusable workflows the armed sha, composite actions the code sha. With a COUNT beside the comparison. `n -eq 2` is the part that catches a carrier which vanished, which a per-value loop cannot see — the same shape as counting the call sites a pin is guarding rather than only checking the ones that are there. The canonical-coordinate grep stays as a cheap extra rather than as the proof. Wording, same review: steps 1 and 2 advance the tip of ONE fork branch, so reset removes that branch, not "candidate and armed branches". test/run.sh 28/28; shellcheck 0.10.0 and changelog-armed clean. Refs #202		2026-08-05 14:02:08 +00:00
..
195.md	fix(labels): panel and triage name identities that exist on this forge (#195 )	2026-08-04 19:09:16 +00:00
198.md	fix(198): the action fails closed, the caller decides scheduling, the guard decides the forge (#198 )	2026-08-05 12:30:28 +00:00
202.md	docs(runner-probes): the arming gate asserts what each carrier IS, not that a literal is gone (#202 )	2026-08-05 14:02:08 +00:00
README.md	feat: ceremony flips to grouped — changelog.d/shape = grouped, five fragments converted, docs per D6	2026-07-25 13:14:05 +00:00
shape	feat: ceremony flips to grouped — changelog.d/shape = grouped, five fragments converted, docs per D6	2026-07-25 13:14:05 +00:00

README.md

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. The shape sentinel beside it declares the set's shape — grouped here, so every fragment carries ### headings (#182).