b3b9830700
Merging #143 auto-closed #137 with a post-merge criterion unmet: the PR carried Closes #137 as doctrine required, the criterion could only be checked after the merge, and the contract was silent on the disagreement between GitHub's keyword and the pipeline's close authority — the same disagreement the cross-repo carve-out already resolved, one case over. BUILDER.md gains the second exception beside the first: when the issue body marks a criterion post-merge, the same-repo PR uses Refs #N and triage closes by hand on the evidence. TRIAGE.md makes the criterion carry its own mechanism; REVIEWER.md lists Refs #N as a spec pointer and stops treating the reference-only PR as a defect; CONTRIBUTING.md points at the one home instead of restating. No machinery, no label (#151 D5). Closes #151 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 130.md | ||
| 131.md | ||
| 134.md | ||
| 135.md | ||
| 137.md | ||
| 139.md | ||
| 145.md | ||
| 151.md | ||
| README.md | ||
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.