The two scope passages said the opposite of merged behaviour: a reviewer's registry was 'the org itself' and 'no repo filter may gate' a request. duty-review.sh implements repos.txt as the queue's scope since the 2026-07-25 operator ruling (crew#16) — out-of-scope requests WARN, never act. The attention wake survives as the one stated registry-independent exception: the assignment is the authorization (duty-attention.sh). Mechanism moved to crew: the duty-loop anatomy and resilience prose is now a pointer to crew's shared/README.md, folding the two drifted facts (cron runs tick.sh; hygiene self-schedules inside the duty tick). Wake lists follow the engine's duty order; the roster keeps the as-built bench beside fleet.roster's target with the delta stated; stamp updated to crew@01fb49c. Closes #187 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 167.md | ||
| 173.md | ||
| 175.md | ||
| 178.md | ||
| 180.md | ||
| 182.md | ||
| 184.md | ||
| 187.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).