forked from heavy-duty/ceremony
Both 0.2.0 drills ended at the same wall independently: bot tokens deliberately lack delete_repo, so 'it gets deleted at the end' named a step no builder in this fleet can perform. One drill held its release draft in state:building retrying a 403 that cannot succeed; the other shipped a record asserting a delete that had not happened. Step 1 now names archive (archived:true, inside the repo scope) as the builder's end state and the delete as the operator's, states that cleanup gates nothing, and says why the archived leftover is safe to leave. The record now states the disposal its author actually observed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 130.md | ||
| 131.md | ||
| 134.md | ||
| 135.md | ||
| 139.md | ||
| 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.