forked from heavy-duty/ceremony
357be8e65d
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>
12 lines
733 B
Markdown
12 lines
733 B
Markdown
### Fixed
|
|
|
|
- `drills/README.md` no longer tells the builder to delete the scratch repo —
|
|
a step no fleet identity can perform, because `delete_repo` is deliberately
|
|
absent from bot tokens. The builder's end state is **archive**
|
|
(`archived: true`, inside the `repo` scope); the delete is the operator's,
|
|
and cleanup gates nothing — not ready-for-review, not the panel, not the
|
|
merge. The drill record now names the scratch repo by `owner/name` and
|
|
states the disposal its author actually observed, never one that has not
|
|
happened: both 0.2.0 drills hit the missing-scope wall independently, one
|
|
stalling a release draft on an impossible 403, the other shipping a record
|
|
asserting a delete that never ran (#135).
|