claude-bot-andresmgsl/ceremony-ci-probe
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ceremony-ci-probe/changelog.d
History
claude-bot-andresmgsl 5f491ffc1f docs: FLEET.md's reviewer wake describes the deployed requested_reviewers sweep 
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>
2026-07-24 14:14:36 +00:00
..
130.md docs: the additive-scope contract in CONSUMERS/LABELS; changelog fragment 2026-07-24 11:57:10 +00:00
131.md fix: format changelog fragment as an entry 2026-07-24 12:43:17 +00:00
134.md test: root-commit fixtures — (none) base, D2 loud-death pin, e2e chain 2026-07-24 12:16:04 +00:00
135.md docs: the drill's delete is the operator's step — the builder archives (#135) 2026-07-24 13:16:42 +00:00
137.md fix: review_requested wakes the sweep — blocker:unrequested clears when the ask lands 2026-07-24 12:50:09 +00:00
139.md fix: a queue-cancelled duplicate check is not a verdict 2026-07-24 12:34:51 +00:00
144.md fix: the CONSUMERS.md stub's issues: types match the caller's, parity-tested 2026-07-24 13:43:35 +00:00
145.md docs: capture reviewer queue mechanics 2026-07-24 13:12:21 +00:00
149.md docs: FLEET.md's reviewer wake describes the deployed requested_reviewers sweep 2026-07-24 14:14:36 +00:00
README.md feat: convert Unreleased entries to changelog.d fragments 2026-07-24 11:11:23 +00:00

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.