From fb352144098bb0a31bddb4f972db8ea559aed018 Mon Sep 17 00:00:00 2001 From: claude-bot-andresmgsl Date: Fri, 24 Jul 2026 11:22:34 +0000 Subject: [PATCH 1/4] release: version 0.2.0 goes bare Co-Authored-By: Claude Fable 5 --- VERSION | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VERSION b/VERSION index c992723..0ea3a94 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -0.1.1-dev +0.2.0 -- 2.45.2 From 15a33a63007c0ab425489702bd33fb3939872cd4 Mon Sep 17 00:00:00 2001 From: claude-bot-andresmgsl Date: Fri, 24 Jul 2026 11:22:45 +0000 Subject: [PATCH 2/4] release: assemble the 0.2.0 section, consuming 28 fragments MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit bin/changelog-assemble 0.2.0 — the section and the fragment deletions in one commit, per #118. changelog.d/ keeps its README.md marker and stays armed by existing. Co-Authored-By: Claude Fable 5 --- CHANGELOG.md | 31 +++++++++++++++++++++++++++++++ changelog.d/101.md | 1 - changelog.d/104.md | 1 - changelog.d/105.md | 1 - changelog.d/109.md | 1 - changelog.d/112.md | 1 - changelog.d/113.md | 1 - changelog.d/114.md | 1 - changelog.d/115.md | 1 - changelog.d/116.md | 1 - changelog.d/126.md | 1 - changelog.d/51.md | 1 - changelog.d/52.md | 1 - changelog.d/57.md | 1 - changelog.d/58.md | 1 - changelog.d/61.md | 1 - changelog.d/68.md | 1 - changelog.d/69.md | 1 - changelog.d/72.md | 1 - changelog.d/73.md | 1 - changelog.d/74.md | 1 - changelog.d/77.md | 1 - changelog.d/84.md | 1 - changelog.d/85.md | 1 - changelog.d/86.md | 1 - changelog.d/91.md | 1 - changelog.d/93.md | 1 - changelog.d/95.md | 1 - changelog.d/98.md | 1 - 29 files changed, 31 insertions(+), 28 deletions(-) delete mode 100644 changelog.d/101.md delete mode 100644 changelog.d/104.md delete mode 100644 changelog.d/105.md delete mode 100644 changelog.d/109.md delete mode 100644 changelog.d/112.md delete mode 100644 changelog.d/113.md delete mode 100644 changelog.d/114.md delete mode 100644 changelog.d/115.md delete mode 100644 changelog.d/116.md delete mode 100644 changelog.d/126.md delete mode 100644 changelog.d/51.md delete mode 100644 changelog.d/52.md delete mode 100644 changelog.d/57.md delete mode 100644 changelog.d/58.md delete mode 100644 changelog.d/61.md delete mode 100644 changelog.d/68.md delete mode 100644 changelog.d/69.md delete mode 100644 changelog.d/72.md delete mode 100644 changelog.d/73.md delete mode 100644 changelog.d/74.md delete mode 100644 changelog.d/77.md delete mode 100644 changelog.d/84.md delete mode 100644 changelog.d/85.md delete mode 100644 changelog.d/86.md delete mode 100644 changelog.d/91.md delete mode 100644 changelog.d/93.md delete mode 100644 changelog.d/95.md delete mode 100644 changelog.d/98.md diff --git a/CHANGELOG.md b/CHANGELOG.md index d297992..b5060a9 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,37 @@ fragments — one `changelog.d/.md` per PR, never an edit to this file — and the release PR assembles them into the next section here (`bin/changelog-assemble`, #112). +## 0.2.0 — 2026-07-24 + +- `test/changelog-assembled.test.sh` — keep the trio interaction aligned with fragment mode: a dropped entry makes armed red too, while a hand-edited section leaves assembled as the sole red (#126). +- `actions/changelog-assembled` — a release PR's stamped section must be byte-for-byte what the fragments it consumed assemble to, replayed from the merge base; inapplicable trees pass with a NOTICE (#116). +- `changelog-armed` — treat `changelog.d/` as the arming, validate every development fragment, and require bare releases to consume the directory into their exact publishable section (#115). +- `lib/changelog.sh` + `bin/changelog-assemble` — read the `changelog.d/` fragments, assemble one release section (canonical group order, one shape per repo), and consume exactly what was published (#114). +- BUILDER.md — the directed hold is the parked claim's fifth shape, its attention demand is acknowledged in the declaration comment, and its board bookkeeping covers in-flight work; TRIAGE.md no longer excludes it (#113). +- Ceremony adopts `changelog.d/` — a PR writes one fragment per issue instead of editing `CHANGELOG.md`, the release PR assembles the section, and `## Unreleased` is gone (#112). +- BUILDER.md — the handed-off PR is the parked claim's fourth shape, its handoff is its declaration, and shape 2 covers the round awaiting its first verdicts (#109). +- `labels-reconcile` — warn once per sweep when a repository lacks labels declared by the pinned core taxonomy (#105). +- `LABELS.md` — drop the vendored scope-table enumeration; the per-repo set lives in `.github/labels.conf` and the repo's own CONTRIBUTING (#104). +- `labels-reconcile` — a degraded mergeability/checks read now logs gh's actual stderr (collapsed, bounded) beside the byte-identical counted line, and the blind-sweep warning leads with the observed reason instead of asserting the permissions cause (#101). +- Changelog publication — count entries instead of bytes, refuse dangling grouped headings, and seed grouped re-arms with Added/Changed/Fixed (#98). +- `labels-reconcile` — grant callers private-repo check reads and warn when an entire PR sweep is blind (#95). +- `labels-reconcile` — the bootstrap now retires the six GitHub defaults `LABELS.md` publishes as deleted, tolerating both an already-absent label and a refused delete (#93). +- `issueflow-reconcile` — a triage-authored issue arrival stands down with exit 0 instead of killing the run before the sweep (#91). +- FLEET.md — the assignee's `attention` wake: one role-independent trigger ahead of every per-role list, one acked session per demand; a spec on paper until `duty.sh` polls it (#86). +- `attention` doctrine — define its assignee-owned pickup, ack, queue and clock semantics across labels, triage, and builder roles (#85). +- `attention` — add the issue-only, hand-set assignee-demand flag to the core label taxonomy (#84). +- One issue at a time counts build work in flight: the parked claim's three shapes, its declared-never-inferred comment, and triage's duty to name a directed hold as a park (#77). +- FLEET.md — the operator notifier's `needs-ruling` queue (one tracked message per item, edited in place across the rungs) and triage's past-24h wake condition; a spec on paper until an operator updates the box (#74). +- The sweep observes the escalation contract: a malformed escalation is named field-by-field, and the ladder's 12h/24h rungs each draw one comment to the flag-setter — comment-only, per-episode, both surfaces (#73). +- Ruling doctrine — define every human-owned trigger, the fixed escalation shape, and the 0–24h builder-to-triage ladder (#72). +- `issueflow-reconcile` — nudge once when an `offsite` flag outlives every visible cross-referenced PR (#69). +- `offsite` — protect claimed issues whose PR lives in another repository from the claim-reclaim clock (#68). +- `issueflow-reconcile` — keep cross-repo references out of local dependency decisions and require triage to resolve cross-repo blockers by hand (#61). +- `actions/runner-isolated` — a `pull_request`-triggered job may never run on a self-hosted runner (#58). +- Cross-repo doctrine: the panel is the PR's repo's roster, a review request is authorization but not panel membership, and `Part of #N` replaces the `Closes #N` that cannot cross repos (#57). +- The sweep's `needs-ruling` invariants, one implementation for both surfaces: the issue-side staleness exemption, the bare-flag check (comment-only, the label is never removed), and the 7-day nudge to the decider (#52). +- `needs-ruling` — the cross-cutting flag for a pending human decision, excluded from `state:needs-human` and from the staleness sweep (#51). + ## 0.1.0 — 2026-07-22 - `lib/version.sh` — one version abstraction, `file` and `package-json` backends (#3). diff --git a/changelog.d/101.md b/changelog.d/101.md deleted file mode 100644 index fae50f9..0000000 --- a/changelog.d/101.md +++ /dev/null @@ -1 +0,0 @@ -- `labels-reconcile` — a degraded mergeability/checks read now logs gh's actual stderr (collapsed, bounded) beside the byte-identical counted line, and the blind-sweep warning leads with the observed reason instead of asserting the permissions cause (#101). diff --git a/changelog.d/104.md b/changelog.d/104.md deleted file mode 100644 index 8428e43..0000000 --- a/changelog.d/104.md +++ /dev/null @@ -1 +0,0 @@ -- `LABELS.md` — drop the vendored scope-table enumeration; the per-repo set lives in `.github/labels.conf` and the repo's own CONTRIBUTING (#104). diff --git a/changelog.d/105.md b/changelog.d/105.md deleted file mode 100644 index df8841f..0000000 --- a/changelog.d/105.md +++ /dev/null @@ -1 +0,0 @@ -- `labels-reconcile` — warn once per sweep when a repository lacks labels declared by the pinned core taxonomy (#105). diff --git a/changelog.d/109.md b/changelog.d/109.md deleted file mode 100644 index 326c6f6..0000000 --- a/changelog.d/109.md +++ /dev/null @@ -1 +0,0 @@ -- BUILDER.md — the handed-off PR is the parked claim's fourth shape, its handoff is its declaration, and shape 2 covers the round awaiting its first verdicts (#109). diff --git a/changelog.d/112.md b/changelog.d/112.md deleted file mode 100644 index 29738cf..0000000 --- a/changelog.d/112.md +++ /dev/null @@ -1 +0,0 @@ -- Ceremony adopts `changelog.d/` — a PR writes one fragment per issue instead of editing `CHANGELOG.md`, the release PR assembles the section, and `## Unreleased` is gone (#112). diff --git a/changelog.d/113.md b/changelog.d/113.md deleted file mode 100644 index 35c5087..0000000 --- a/changelog.d/113.md +++ /dev/null @@ -1 +0,0 @@ -- BUILDER.md — the directed hold is the parked claim's fifth shape, its attention demand is acknowledged in the declaration comment, and its board bookkeeping covers in-flight work; TRIAGE.md no longer excludes it (#113). diff --git a/changelog.d/114.md b/changelog.d/114.md deleted file mode 100644 index 160da0f..0000000 --- a/changelog.d/114.md +++ /dev/null @@ -1 +0,0 @@ -- `lib/changelog.sh` + `bin/changelog-assemble` — read the `changelog.d/` fragments, assemble one release section (canonical group order, one shape per repo), and consume exactly what was published (#114). diff --git a/changelog.d/115.md b/changelog.d/115.md deleted file mode 100644 index 324eb08..0000000 --- a/changelog.d/115.md +++ /dev/null @@ -1 +0,0 @@ -- `changelog-armed` — treat `changelog.d/` as the arming, validate every development fragment, and require bare releases to consume the directory into their exact publishable section (#115). diff --git a/changelog.d/116.md b/changelog.d/116.md deleted file mode 100644 index 1acdd6a..0000000 --- a/changelog.d/116.md +++ /dev/null @@ -1 +0,0 @@ -- `actions/changelog-assembled` — a release PR's stamped section must be byte-for-byte what the fragments it consumed assemble to, replayed from the merge base; inapplicable trees pass with a NOTICE (#116). diff --git a/changelog.d/126.md b/changelog.d/126.md deleted file mode 100644 index e6558e9..0000000 --- a/changelog.d/126.md +++ /dev/null @@ -1 +0,0 @@ -- `test/changelog-assembled.test.sh` — keep the trio interaction aligned with fragment mode: a dropped entry makes armed red too, while a hand-edited section leaves assembled as the sole red (#126). diff --git a/changelog.d/51.md b/changelog.d/51.md deleted file mode 100644 index 688a2c1..0000000 --- a/changelog.d/51.md +++ /dev/null @@ -1 +0,0 @@ -- `needs-ruling` — the cross-cutting flag for a pending human decision, excluded from `state:needs-human` and from the staleness sweep (#51). diff --git a/changelog.d/52.md b/changelog.d/52.md deleted file mode 100644 index cafdc0b..0000000 --- a/changelog.d/52.md +++ /dev/null @@ -1 +0,0 @@ -- The sweep's `needs-ruling` invariants, one implementation for both surfaces: the issue-side staleness exemption, the bare-flag check (comment-only, the label is never removed), and the 7-day nudge to the decider (#52). diff --git a/changelog.d/57.md b/changelog.d/57.md deleted file mode 100644 index b79fb23..0000000 --- a/changelog.d/57.md +++ /dev/null @@ -1 +0,0 @@ -- Cross-repo doctrine: the panel is the PR's repo's roster, a review request is authorization but not panel membership, and `Part of #N` replaces the `Closes #N` that cannot cross repos (#57). diff --git a/changelog.d/58.md b/changelog.d/58.md deleted file mode 100644 index 791b399..0000000 --- a/changelog.d/58.md +++ /dev/null @@ -1 +0,0 @@ -- `actions/runner-isolated` — a `pull_request`-triggered job may never run on a self-hosted runner (#58). diff --git a/changelog.d/61.md b/changelog.d/61.md deleted file mode 100644 index 9edee59..0000000 --- a/changelog.d/61.md +++ /dev/null @@ -1 +0,0 @@ -- `issueflow-reconcile` — keep cross-repo references out of local dependency decisions and require triage to resolve cross-repo blockers by hand (#61). diff --git a/changelog.d/68.md b/changelog.d/68.md deleted file mode 100644 index f5ad678..0000000 --- a/changelog.d/68.md +++ /dev/null @@ -1 +0,0 @@ -- `offsite` — protect claimed issues whose PR lives in another repository from the claim-reclaim clock (#68). diff --git a/changelog.d/69.md b/changelog.d/69.md deleted file mode 100644 index 45a4d80..0000000 --- a/changelog.d/69.md +++ /dev/null @@ -1 +0,0 @@ -- `issueflow-reconcile` — nudge once when an `offsite` flag outlives every visible cross-referenced PR (#69). diff --git a/changelog.d/72.md b/changelog.d/72.md deleted file mode 100644 index 34824e7..0000000 --- a/changelog.d/72.md +++ /dev/null @@ -1 +0,0 @@ -- Ruling doctrine — define every human-owned trigger, the fixed escalation shape, and the 0–24h builder-to-triage ladder (#72). diff --git a/changelog.d/73.md b/changelog.d/73.md deleted file mode 100644 index db95180..0000000 --- a/changelog.d/73.md +++ /dev/null @@ -1 +0,0 @@ -- The sweep observes the escalation contract: a malformed escalation is named field-by-field, and the ladder's 12h/24h rungs each draw one comment to the flag-setter — comment-only, per-episode, both surfaces (#73). diff --git a/changelog.d/74.md b/changelog.d/74.md deleted file mode 100644 index 0d81292..0000000 --- a/changelog.d/74.md +++ /dev/null @@ -1 +0,0 @@ -- FLEET.md — the operator notifier's `needs-ruling` queue (one tracked message per item, edited in place across the rungs) and triage's past-24h wake condition; a spec on paper until an operator updates the box (#74). diff --git a/changelog.d/77.md b/changelog.d/77.md deleted file mode 100644 index 956ff97..0000000 --- a/changelog.d/77.md +++ /dev/null @@ -1 +0,0 @@ -- One issue at a time counts build work in flight: the parked claim's three shapes, its declared-never-inferred comment, and triage's duty to name a directed hold as a park (#77). diff --git a/changelog.d/84.md b/changelog.d/84.md deleted file mode 100644 index b5e00fe..0000000 --- a/changelog.d/84.md +++ /dev/null @@ -1 +0,0 @@ -- `attention` — add the issue-only, hand-set assignee-demand flag to the core label taxonomy (#84). diff --git a/changelog.d/85.md b/changelog.d/85.md deleted file mode 100644 index 42ef042..0000000 --- a/changelog.d/85.md +++ /dev/null @@ -1 +0,0 @@ -- `attention` doctrine — define its assignee-owned pickup, ack, queue and clock semantics across labels, triage, and builder roles (#85). diff --git a/changelog.d/86.md b/changelog.d/86.md deleted file mode 100644 index 8b6f008..0000000 --- a/changelog.d/86.md +++ /dev/null @@ -1 +0,0 @@ -- FLEET.md — the assignee's `attention` wake: one role-independent trigger ahead of every per-role list, one acked session per demand; a spec on paper until `duty.sh` polls it (#86). diff --git a/changelog.d/91.md b/changelog.d/91.md deleted file mode 100644 index 89cd4bc..0000000 --- a/changelog.d/91.md +++ /dev/null @@ -1 +0,0 @@ -- `issueflow-reconcile` — a triage-authored issue arrival stands down with exit 0 instead of killing the run before the sweep (#91). diff --git a/changelog.d/93.md b/changelog.d/93.md deleted file mode 100644 index 7902fac..0000000 --- a/changelog.d/93.md +++ /dev/null @@ -1 +0,0 @@ -- `labels-reconcile` — the bootstrap now retires the six GitHub defaults `LABELS.md` publishes as deleted, tolerating both an already-absent label and a refused delete (#93). diff --git a/changelog.d/95.md b/changelog.d/95.md deleted file mode 100644 index 0c933bc..0000000 --- a/changelog.d/95.md +++ /dev/null @@ -1 +0,0 @@ -- `labels-reconcile` — grant callers private-repo check reads and warn when an entire PR sweep is blind (#95). diff --git a/changelog.d/98.md b/changelog.d/98.md deleted file mode 100644 index 1c200cb..0000000 --- a/changelog.d/98.md +++ /dev/null @@ -1 +0,0 @@ -- Changelog publication — count entries instead of bytes, refuse dangling grouped headings, and seed grouped re-arms with Added/Changed/Fixed (#98). -- 2.45.2 From 682b9cb8929aa8c50a3101b64ca57fee7b09fef1 Mon Sep 17 00:00:00 2001 From: claude-bot-andresmgsl Date: Fri, 24 Jul 2026 11:22:48 +0000 Subject: [PATCH 3/4] release: CEREMONY_SELF_REF 0.1.0 -> 0.2.0 in both carriers Co-Authored-By: Claude Fable 5 --- .github/workflows/labels.yml | 2 +- .github/workflows/release.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/labels.yml b/.github/workflows/labels.yml index 0c69c8a..0cea584 100644 --- a/.github/workflows/labels.yml +++ b/.github/workflows/labels.yml @@ -24,7 +24,7 @@ on: env: # A called workflow arrives without its repository. Keep this literal pin # aligned with the ceremony release consumed by callers (issue #9 D3). - CEREMONY_SELF_REF: "0.1.0" + CEREMONY_SELF_REF: "0.2.0" jobs: scope: diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index ac2cfc7..4456c63 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -129,7 +129,7 @@ env: # `ref:` accepts ${{ env }}; `uses:` strings do not — which is why the # shared logic arrives as script files via checkout, not as inner `uses:` # references. - CEREMONY_SELF_REF: "0.1.0" + CEREMONY_SELF_REF: "0.2.0" VERSION_SOURCE: ${{ inputs.version-source }} jobs: -- 2.45.2 From c0df9f436d7e986dfe4a24017c35a52a14c32fab Mon Sep 17 00:00:00 2001 From: claude-bot-andresmgsl Date: Fri, 24 Jul 2026 11:37:11 +0000 Subject: [PATCH 4/4] =?UTF-8?q?release:=20record=20the=200.2.0=20drill=20?= =?UTF-8?q?=E2=80=94=20six=20probes=20on=20a=20fragment-shaped=20scratch?= =?UTF-8?q?=20consumer?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Fable 5 --- drills/0.2.0.md | 119 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 119 insertions(+) create mode 100644 drills/0.2.0.md diff --git a/drills/0.2.0.md b/drills/0.2.0.md new file mode 100644 index 0000000..a2e6c9f --- /dev/null +++ b/drills/0.2.0.md @@ -0,0 +1,119 @@ +# 0.2.0 — drill record + +Run 2026-07-24, by `claude-bot-andresmgsl`, against the release candidate +`heavy-duty/ceremony@682b9cb8929aa8c50a3101b64ca57fee7b09fef1` (PR #129's +head at drill time — the ceremony PR adds only `VERSION`, the assembled +section with its fragment deletions, the self-ref stamps, and this record; +no machinery differs between the drilled tree and the released one). + +Where: scratch private repo `claude-bot-andresmgsl/ceremony-drill-0.2.0`, +carrying the `docs/CONSUMERS.md` caller stubs (modulo the pin deviation +below) and a fixture consumer tree in the **fragment shape** this release +exists to ship: `VERSION` `0.5.0-dev`, `CHANGELOG.md` preamble plus a +shipped `## 0.4.0` section, `changelog.d/` with its `README.md` marker and +two fragments, `drills/`, and the five guard actions in CI at the drill +ref. Archived after this record was written; deletion needs the +`delete_repo` scope this box's token deliberately lacks, so the operator +owns the final delete — the repo is the evidence's scaffolding, this file +is the evidence. Run ids below are kept for the record's own audit trail. + +## The deviation: the self-drill deadlock recurs past the first release + +The spec (#118) expected the 0.1.0 record's fork deviation to be moot — +"`0.1.0` exists, so the pinned path runs straight." It does not, for +ceremony's *own* drill: the candidate tree pins +`CEREMONY_SELF_REF: "0.2.0"` — the very stamp this PR makes — and the +consumer path checks out `heavy-duty/ceremony` at exactly that ref, which +cannot exist before the merge. What `0.1.0` existing does make moot is the +*consumer-side* deadlock: a governed repo drilling its own release pins +ceremony at a real tag and runs straight. Raised on #118 before drilling; +proceeded per the deviation triage already ruled for #11, unchanged in +shape: **no `0.2.0`-named ref on the canonical repo**; the scratch callers +pin the fork ref `claude-bot-andresmgsl/ceremony@drill/0.2.0` — the +candidate tree with exactly one line changed per pin carrier +(`release.yml` and `labels.yml`, both — `self-ref-check.sh` requires the +carriers to agree), `CEREMONY_SELF_REF: "0.2.0"` → +`"682b9cb8929aa8c50a3101b64ca57fee7b09fef1"`. Every `.ceremony-src` byte +the doors executed still came from `heavy-duty/ceremony` at the candidate +SHA (reachable there via PR #129's pull ref); the fork supplied +orchestration YAML differing by the one line the ceremony stamps each +release anyway. Drilling against `0.1.0` instead would not have been a +drill of the candidate: `lib/changelog.sh`, which both doors source for +notes extraction, is +214 lines since `0.1.0` (fragment mode; #98). + +## The probes + +| # | probe | run | result | +|---|---|---|---| +| a | merge-door ceremony, fragment shape | 30089779736 (attempt 1) | ✅ exactly one release | +| b | mislabeled ordinary PR | 30089842547 | ✅ green NOTICE no-op | +| c | bare-version PR, no label | 30089908740 | ✅ refused, red, created nothing | +| d | re-run of the completed ceremony | 30089779736 (attempt 2) | ✅ refused, red, created nothing | +| e | tag door, manual matching tag | 30090053523 | ✅ published, no bump | +| f | tag door, mismatched tag | 30090082676 | ✅ refused, red, created nothing | + +**(a) The ceremony, in fragment shape.** PR `release: 0.5.0` — hand-set +`release` label, `VERSION` `0.5.0-dev` → `0.5.0`, and the stamp made by +the candidate's own `bin/changelog-assemble 0.5.0`: two fragments folded +into `## 0.5.0 — 2026-07-24` (newest issue first), deleted in the same +commit, `changelog.d/` left holding only its `README.md` marker — no +re-arm edit, armed by existing. The five guard actions at the drill ref — +`changelog-armed`, `changelog-monotonic`, `changelog-assembled`, +`drill-recorded`, `runner-isolated` — all green on that PR (run +30089703224): the assembled guard replayed the assembly from the merge +base and matched it byte-for-byte, live, on the mechanism this release +ships. Merged. The one run: facts +`ver='0.5.0' base_ver='0.5.0-dev' labeled='yes'` → `ceremony=yes` → tag +`0.5.0` on the merge commit (`9b9e58e`), release `0.5.0` published with +the assembled section — verbatim, both bullets — as its body, and main +re-armed to `0.5.1-dev` by the run itself. The GITHUB_TOKEN tag create +and bump push fired **no** second run (anti-recursion held). + +**(b) Mislabeled ordinary PR.** Docs-only PR wearing the `release` label. +Green: `NOTICE: the version '0.5.1-dev' is -dev and unchanged by this PR — +release-flow work under the release label, not a ceremony. Nothing to +publish.` No tag, no release. + +**(c) Bare-version PR without the label.** The ceremony's edits — +`0.5.1-dev` → `0.5.1`, a section assembled from a fragment — label +deliberately absent. Red at decide: +`the version transitioned ('0.5.1-dev' -> '0.5.1') but no merged, +release-labeled PR is behind this commit — a release is a labeled ceremony +PR, not a bare push — creating nothing.` No tag, no release; main +reverted to the armed state afterwards, and the revert push itself ran +green as a no-op (run 30090017774), as it should. + +**(d) Re-run of the completed ceremony.** Re-ran (a)'s run. Red at the +nothing-may-exist assert: +`tag '0.5.0' already exists — this release already happened, or a manual +tag won the race; refusing to re-release, creating nothing.` Release +count still exactly one. + +**(e) Tag door.** Branch with `VERSION` `0.6.0` and its section assembled +from a fragment; manual `0.6.0` tag pushed at its head (never merged to +main). The tag door published release `0.6.0` with that section as its +body; the merge door correctly skipped. Main untouched: `VERSION` stayed +`0.5.1-dev` — the fallback does not rewrite main. + +**(f) Mismatched tag.** Tag `9.9.9` pushed at main (tree version +`0.5.1-dev`). Red: +`tag '9.9.9' does not match the tree's version '0.5.1-dev' — creating +nothing.` No release, and the operator-facing remediation text printed as +designed. + +## Failures + +None among the probes; every refusal path was checked for droppings — the +only releases and workflow-created tags that exist are (a)'s and (e)'s. + +One finding outside the probe set, written down plainly: the fixture's +**initial push** — the very first commit of the scratch repo, caller +included — ran the merge door red (run 30089682128): `lib/facts.sh` +resolves the base as `MERGE_SHA^1` when `event.before` is all-zeros, and +a repo's first commit has no parent, so `git rev-parse` fails loudly +(exit 128) before deciding. Nothing was created, and every subsequent +push behaved; but a greenfield consumer bootstrapping caller-first will +meet one red run on its first push, which the doctrine's "every +legitimate non-ceremony is a green NOTICE no-op" does not intend. +`facts.sh` is unchanged since `0.1.0` — not a candidate regression, not a +blocker for this release; escalated as a discussion, not fixed here. -- 2.45.2