forked from heavy-duty/ceremony
5f491ffc1f
The Reviewers bullet stated a gh-search request trigger and a sequential first-this-second-that ordering; all four reviewer boxes actually run an org-wide pulls-API requested_reviewers sweep merged with the repos.txt backstop, deduplicated by (repo, PR) before acting (crew@b2fd864). The on-paper list narrows to the notifier's needs-ruling queue, repos.txt is the registry only on the triage box, and the Status block now carries the crew ref this description was last reconciled against. Part of the drift #148 reported; spec and citations in #149. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 130.md | ||
| 131.md | ||
| 134.md | ||
| 135.md | ||
| 137.md | ||
| 139.md | ||
| 144.md | ||
| 145.md | ||
| 149.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.