Tasks are weighted JSON files; triage reads them (plus lightweight carryover todos) and picks this cycle’s scope. The two integrity rules, both new this week:
a9949f92): the post-ship step writes a landing note; the inbox mover refuses to mark an item consumed without one. Bookkeeping follows the ground truth of main.56bb8649): the new go/internal/ciwatch package fetches GitHub Actions status for the pushed commit into release preflight and the dossier. Local green is a claim; remote green is the verification.Consumed-without-landing. A top-priority defect (weight 0.96 — the token-resolver wiring) vanished: marked consumed, fix never landed. It was rediscovered only because a dependent task failed three times in a row. The same week, a carryover audit found ~70 stale "review this failure" todos squatting with P0 labels — captured signals that nothing ever aged, escalated, or retired. Both are one disease: bookkeeping drifting from ground truth.
Trusting local green. A past release shipped while GitHub CI was red — nothing watched the remote after push. Same shape, one level up.
Sibling case study: token telemetry — the lost-item incident is what provoked cycle 752. And the still-failing fleet-lane-provisioning-split (4 identical graduation-guard failures) is the queue’s next lesson: when an item keeps failing identically, repair the item’s acceptance criteria; don’t re-dispatch it blind.