forked from heavy-duty/ceremony
The trigger comments, CONSUMERS stub, changelog, and reusable labels.yml comment said "events carry every real state change in seconds; the cron only backstops a forgotten handoff." That is backwards: no subscribed event wakes this sweep for a review verdict landing (no pull_request_review trigger), blocker:ci-red set/cleared, blocker:conflict when another PR merges, or the time-based stale/48h-reclaim. The hourly cron is the sole discovery path for those four classes, not a forgotten-handoff net — so the comments now name them and warn against deleting the cron (AC5). codex-2 / kimi-2 (both blocking, round 2 @0a812c4b). |
||
|---|---|---|
| .. | ||
| 167.md | ||
| 173.md | ||
| 175.md | ||
| 178.md | ||
| 180.md | ||
| 182.md | ||
| 184.md | ||
| 187.md | ||
| 189.md | ||
| 192.md | ||
| 193.md | ||
| 199.md | ||
| README.md | ||
| shape | ||
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. The shape sentinel beside it declares the set's shape —
grouped here, so every fragment carries ### headings (#182).