e5e7555184
Five fragments assembled into '## 0.5.0 — 2026-08-03' (#205 #216 #221
#224 #226); VERSION to bare 0.5.0; the three CEREMONY_SELF_REF carriers
stamped "0.5.0" in this one commit; the panel-rows unreleased marker in
docs/CONSUMERS.md cleared to name 0.5.0; drills/0.5.0.md records the
doors-unchanged ruling with the measurements as they are at 0ac3a6f.
Refs #233.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
3 KiB
0.5.0 — drill record
Run 2026-08-03 by dan-claude-bot against the release PR (Refs #233),
candidate branch build/233-release-0-5-0 on heavy-duty/ceremony main at
0ac3a6f.
Scope ruling — doors unchanged, no disposable-repo rehearsal
The 0.4.0 drill (drills/0.4.0.md) probed both release doors end-to-end in a
disposable repo; the live 0.4.0 and 0.4.1 releases then exercised the merge
door for real, twice, within the last three days. Measured at 0ac3a6f,
stated as they are rather than as #233's D3 predicted them at b18c0bc:
git diff 0.4.1..main -- .github/workflows/release.yml— empty. No door logic, no decide table, no publish step moved.git diff 0.4.1..main -- bin— empty. No release tooling moved.git diff 0.4.1..main -- lib— not empty:lib/ruling.sh+50/−13, #226's best-shaped escalation selection, merged this morning as PR #234. That is the labels-sweep library the reconcilers source; nothing in the release path reads it. The doors-unchanged ruling rests on the two empty surfaces above, not on a lib claim this tag can no longer make.
Re-running a full disposable-repo drill would rehearse machinery this repo proved in rehearsal at 0.4.0 and in production at both subsequent tags. This record rests on the standing evidence below and says so honestly. The panel reviews this claim like any other; if any reviewer rules a full drill owed, that verdict wins (#233 D3).
Standing evidence at the candidate head
| # | probe | where | result |
|---|---|---|---|
| 1 | decide + merge-door step-replay (dogfood) | release-exercise / step-replay (dogfood) on this PR |
CI-gating; green required to merge |
| 2 | decide + merge-door step-replay (consumer) | release-exercise / step-replay (consumer) on this PR |
CI-gating; green required to merge |
| 3 | fragment chain: armed → assemble → monotonic | release-exercise / fixture-chain on this PR |
CI-gating; green required to merge |
| 4 | the real tree's own guards (armed, monotonic, drill-recorded, self-ref) | self-guards on this PR |
CI-gating; green required to merge |
| 5 | the 0.5.0 payload live: #226's selection running in this repo's own ruling sweep since the #234 merge | self-labels-sweep runs after 0ac3a6f |
live dogfood — the changed lib is exercised by the very board that ships it |
Probe 5 is the one piece the prior drills could not cover: lib/ruling.sh
is the only library delta this tag carries, and this repo's own sweeps have
been executing it since the merge — the consumer-shaped proof that the
labels machinery at the candidate's content stays green outside a fixture.
Deviations
No candidate-ref deviation arises: this record stages no scratch caller, so
nothing needs to resolve CEREMONY_SELF_REF: "0.5.0" before the tag exists.
The sibling adoption proof is post-tag and crew's: crew#298's pin bump, then
its panel[<login>]= rows, then crew's first clean sweep — owned by that
issue's criteria, reported back on #233 per its post-merge criterion.