6634a517bc
BUILDER.md's review round assumed ready-throughout, so a builder or reviewer meeting a mid-round draft found behaviour the doctrine never described. Three points, doctrine not mechanism: the draft phase stays the builder's through a fix round, ready-for-review is the builder's own act and no engine's, and where the draft suppressed CI green is proven at the flip with the request following it — step 1's rule at a stated moment, not a second rule. REVIEWER.md gains the reading that keeps a reviewer from misfiling it: a draft carrying state:addressing is a fix round in progress. Refs #258 |
||
|---|---|---|
| .. | ||
| 218.md | ||
| 230.md | ||
| 231.md | ||
| 232.md | ||
| 236.md | ||
| 241.md | ||
| 242.md | ||
| 247.md | ||
| 248.md | ||
| 252.md | ||
| 258.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).