Pre-run configuration is implemented in draft !128:
The PR updates panel=, triage-actors=, the matching CONTRIBUTING.md roster,…
@andres — #125 can be closed as completed by merged !114 (a3ec471, merge commit 12803b2).
I checked each acceptance criterion against current origin/main:
- Forgejo recovery is emitted…
Approved a3ec47113ad7ee86be32447b410101cc8a5ed8ba.
Approved 1c9a245595fcc8fbcf2c8ba533a10c68b97a0e10.
Correction to my comment 3699: the claim that exact hand-created labels would become drift the bootstrap must undo was wrong. The pinned bootstrap_labels uses gh label create --force, so exact…
Superseding my approval on ec73c86de7a38eab72b61c7f8912bc55ba166ac2 with REQUEST_CHANGES after reproducing a newly identified defect from #125.
@andres — concurrent filing produced duplicates after your exception:
- #115 and #117 both cover the absent repository Actions runner.
- #116 covers the two coupled labels-workflow inputs split…
@andres — under your explicit exception in !114 comment 3664, I created the two buildable Ceremony-support issues exposed by this round:
- #115 — register a repository-scoped Forgejo Actions…
Approved on ec73c86de7a38eab72b61c7f8912bc55ba166ac2.
Request changes on 24abfbdb79ce35f7d78f8b255e162fcb9e9ce8f6.
@andres — I re-read this against main at 90cbfe0 and measured the Forgejo endpoints anonymously today. The prerequisite in the body is now satisfied: the repo web/API/archive endpoints all…
@andres — merge and closure are already complete: !113 merged as 90cbfe0, and #112 closed at 2026-07-29T13:37:34Z.
I cannot mint the labels follow-up from this session without breaking the…
I independently confirm both corrections and amend my earlier guidance:
- Seven ceremony-core rows are absent, not four:
attention,claimed,epic,needs-ruling,needs-triage,…
@andres — verified directly against ceremony 0.3.0: not fixed, and merging !113 alone will not create those labels. But do not copy ready / claimed / needs-triage / epic into…