45934b54a2
Refs #189 — the post-merge, triage-owned task, now reachable: heavy-duty/crew#64 merged at 4da17c49594c2d86bd3793fa3567846cbca38e90. #190 wrote the ci-red wake into FLEET.md deliberately marked on paper, per this file's convention for a spec that is not yet running, and left the reconciliation stamp at crew@01fb49c because advancing it to a SHA that did not carry the wake would be the drift #187 exists to remove. crew#64 has merged, so both halves flip: - The stamp advances to crew@4da17c4, and every crew permalink in the file with it. A stamp and its evidence links naming different trees is worse than no stamp: the reader diffs the wrong engine and finds no drift because the tree they were pointed at is the one the prose was written against. - The four on-paper markers go: the duty-order caveat, the ci-red bullet's parenthetical, the Build bullet's "once ci-red deploys", and the closing paper inventory — which now names one remaining paper wake, the notifier's needs-ruling queue, not two. The Build bullet is not a pure marker removal. crew#64's last review round changed what it has to say: the operator ruled the round gate a whitelist, so the wake admits a green head OR one with no checks configured, and holds a red head AND one whose check has not finished. Copying the old "never a round at a red head" through the flip would have shipped a fresh inaccuracy on the same commit that claims the file is reconciled. The ci-red bullet gains the matching sentence from the other side: an unfinished check is not a red head and wakes nothing, because nothing has failed yet. Verified at the stamped SHA rather than assumed: duty.sh's header carries attention → … → resume → ci-red → build (and says it is what this file is reconciled against), shared/README.md's duty order matches, and notify.sh's only label filter is still state:needs-human — which is what keeps the remaining paper claim true. 18/18 test files pass; changelog_fragment_problem OK (it caught a 387-char entry against the 300 bound, now split); shellcheck, actionlint self-ref and git diff --check clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
Changed
BUILDER.mdgates both review-request points on a green check at the head, carries crew#45's argued exception for failures outside the PR, and states the ruled classification: cancelled and stale are not a green head; skipped and neutral are (#189).BUILDER.mddocuments CI-red recovery in pickup precedence: a red head of your own PR is picked up before claiming another issue, is never a parked claim, and follows crew#17's recovery path (#189).FLEET.mdwrites the ci-red wake into the duty order between resume and build, now as deployed engine rather than on paper: the reconciliation stamp advances to the crew SHA carrying crew#64 (#189).FLEET.mddescribes the build wake's check gate as the engine implements it: a green head, or one with no checks configured, opens a round; a red head and an unfinished one are held and reported separately (#189).BUILDER.mdre-requests by head, not by verdict: a push while answering a round stales every approval, so every panelist is re-requested; only an unchanged head re-requests the non-approvers alone (#190).