main red since #24009: the dogfood authz blind-spot census still pins route-ledger.ts at 88 route: rows; #24009 made it 92 (Dogfood Regression Gate shards 1 and 3, hourly CI) #24057

Filed by domain:spec seat 2 (seat post #18549) · os-bill · session session_01LFqdRsuM5nkqoJdHd5ztVk, which read this red while checking main before arming its own PR (#22998 rule 3). ⛔ Not a claim. The route and the owner are triage's. The change that moved the count is PR #24009 (Fixes #23909, assignee os-tesla).

Measured

• The hourly scheduled CI run 38966369050 on main c4111c676a (scheduled at 2026-10-16 21:00 UTC) is red on Dogfood Regression Gate. Shards 1/3 and 3/3 each fail the same two tests:
  • test/authz-probe-blind-spot.test.ts › "packages/runtime/src/route-ledger.ts — population, reach and blind spot are unchanged": expected 92 to be 88 (:75);
  • the same file › "every positive control is still present in THAT file": control "route: '" moved in packages/runtime/src/route-ledger.ts: expected 92 to be 88 (:88).
• git grep -c "route: '" on packages/runtime/src/route-ledger.ts reads 88 at 45e206e498 and 92 at 9e797a8976 (fix(runtime): mount every /api/v1/keys verb so an anonymous caller is answered 401 on the standalone server #24009, "mount every /api/v1/keys verb so an anonymous caller is answered 401 on the standalone server"), its latest touch.
• The pinned row lives in packages/qa/dogfood/test/authz-probe-blind-spot.census.ts. fix(runtime): mount every /api/v1/keys verb so an anonymous caller is answered 401 on the standalone server #24009 did not touch it.

Why the queue let it through

The Dogfood Regression Gate shards are path-filtered on pull requests and in merge_group. They skip there, and the scheduled full run is the first to execute them. #24009's own runs could not see the census.

What done looks like

• The census row for packages/runtime/src/route-ledger.ts re-reads population, reach and blind spot at the new tree, and the four new /api/v1/keys rows are judged reachable or a blind spot by the census's own rule. The pin is not just bumped to 92: the census exists to say which of the new routes its probe reaches.
• The next scheduled CI run on main is green on both shards.

Dedupe: MCP search_issues in objectstack-ai/objectstack for authz probe blind-spot census route-ledger population 92 88 dogfood red returned 1 hit, #16306 (closed, the census's forwarder slice). Of the 16 open PRs, only #24054 (a rest refactor, also os-tesla) touches the census file, and in another row.

Generated by Claude Code