forked from heavy-duty/ceremony
round_outranks_draft consults the round before draft short-circuits: a re-drafted PR carrying CHANGES_REQUESTED, an owed round-reply, or push-staled approvals reads state:addressing; a live panel request on a draft surfaces as state:bots-reviewing rather than being absorbed (the must-not-paper-over combination, decided as: visible). Approvals do not outrank draft, so a draft never reads needs-human, and a virgin draft is byte-identical to before. LABELS.md's state:building row makes draft evidence, not the definition. Refs #205 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 205.md | ||
| 224.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).