forked from heavy-duty/ceremony
d48374ff00
The #226 delta sits behind reconcile_ruling's needs-ruling gate and this board has no such item — the post-merge sweeps ran the file, never the delta. The record now says what was observed and why the live claim is unreachable (round 1, claude). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
58 lines
3.6 KiB
Markdown
58 lines
3.6 KiB
Markdown
# 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's one lib delta: #226's best-shaped selection | `test/ruling.test.sh` in the `test` job at this head, plus claude-bot's independent reproduction in the #234 review round | green — suite coverage, **not** live dogfood; see below |
|
||
|
||
Probe 5 makes no live-exercise claim, and the reason is stated so the next
|
||
reader does not restore one: the post-merge sweeps (`30811983604`,
|
||
`30812172095`, both at `0ac3a6f`) do run the candidate's `lib/ruling.sh` on
|
||
the dogfood path, but every #226 call site sits inside `reconcile_ruling`,
|
||
whose single caller is behind the `needs-ruling` flag check
|
||
(`labels-reconcile.sh:865–866`), and this board has no `needs-ruling` item,
|
||
standing or historical — so not one line of the delta this tag carries has
|
||
executed live here. Its coverage at this candidate is `test/ruling.test.sh`
|
||
(107 checks, including the crew#293 replay and the six regression proofs
|
||
named in PR #234) and the #234 round's independent re-run of that proof.
|
||
Per drills/README.md — the record is the evidence — and #135's defect
|
||
class, a smaller true probe stands where a larger unobserved one would not.
|
||
|
||
## 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.
|