utah-0.5gb and sydney are pinned to CHANNEL=hold on the boxes, but the inventory still declared them canary and stable. Tooling reads the inventory, not the box — so check-fleet-rollout counted utah-0.5gb in the canary cohort and reported "waiting-repo" indefinitely for a relay we had deliberately held, and a future stable promotion would have looked like it should sweep sydney in. This is the declared-vs-actual drift the capability audit flagged as R-3, in its mildest form: nothing was broken, but the fleet's own description of itself was wrong, which is how the utah-8gb backwards-convergence hazard also went unnoticed. Canary cohort is now utah and bern (bern is a provider outage). Same change applied to the gitignored relays.local.json. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>