forked from heavy-duty/ceremony
b5ec236b42
`blocker:unrequested` is the one blocker that names an act the author must perform, and it never knew whether performing it was permitted. BUILDER.md's review round requires a green check at the head before requesting, so a builder waiting out a pending run is complying — and the blocker fired on compliance (crew#318 ~12:44Z, ceremony#235 12:30Z, both 2026-08-03). Gate the branch on CHECKS ∈ SUCCESS | NONE (D1): PENDING is CI's move, which state:addressing already says, and FAILURE belongs to blocker:ci-red rather than to a second label on the same stall. Then require the supporting facts — the head's own date and the round's newest submitted review — to have stood for RECONCILE_UNREQUESTED_GRACE (default 300s, D2), measured off those timestamps because this sweep is stateless per pass. A timestamp that cannot be read refuses the blocker. Refs #236 |
||
|---|---|---|
| .. | ||
| changelog-armed | ||
| changelog-assembled | ||
| changelog-monotonic | ||
| docs-sync | ||
| drill-recorded | ||
| issueflow-reconcile | ||
| labels-reconcile | ||
| labels-scope | ||
| runner-isolated | ||
| .gitkeep | ||