feat(scaling): per-area detail pages

[0x00101010]

Summary

Why

Detailed metrics sat in collapsed panels under the first screen, and the ceiling cards linked to routes that did not exist. Each bottleneck area now has its own page, so the first screen ends at progress and links down to five detail pages (four areas plus guardrails) with no metric row lost.

What

• /scaling/[area] for da, execution, state, networking: breadcrumb to /scaling, the shared as-of header, the area's ceiling card under a Ceiling · Mgas/s heading, the matching sections[] entry as a table with its gaps (or "No detailed metrics yet"), and an empty "Related runs" slot. Unknown areas call notFound().
• CeilingCard is extracted from CeilingCards so the first screen and the area page render the same card.
• The collapsed detail panels leave the first screen; every row now lives on its area page or, for outcomes, on /scaling/guardrails.
• /scaling/da is added to the CI check that internal-only routes 404 on the public build.

Notes

• Stack: feat(scaling): snapshot schema v2 with ladder, ceilings and guardrails #194 → feat(scaling): add ceilings and guardrails to the snapshot #195 → feat(scaling): first screen with ladder, ceilings, guardrails and progress #196 → feat(scaling): ceiling cards and guardrails #197 → feat(scaling): progress from Linear and collapsed detail sections #198 → feat(scaling): detail pages and unified run index #199 → this PR.
• On the internal build /scaling/bogus renders the not-found page with HTTP 200, because app/loading.tsx streams every page (same as /benchmark/run/<bogus>; proxy.ts documents this). The public build hard-404s all /scaling/* in proxy.ts.

Screenshots

Internal build with the committed synthetic fixture (invented numbers, not a real network).

/scaling at 1280 px, ending at progress with no collapsed panels:

/scaling/da at 1280 px:

/scaling/networking at 1280 px (no section in the snapshot):

/scaling/execution at 360 px:

Test plan

• npm test, npm run typecheck, npm run lint, npm run build, npm run build:internal, npm run llms -- --check
• page.test.tsx: first screen links to all five pages and lists no metric rows; every fixture metric appears on its detail page; the DA page shows breadcrumb, as-of header, unit heading, dated inputs, query, gaps and runs slot; networking shows its ceiling and the empty state; bogus throws the 404 notFound().
• Rendered all six routes at 360 px and 1280 px with the synthetic fixture; external dev server returns 404 for /scaling/*.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
omni-ui	Ready	Preview	Oct 16, 2026 12:46pm UTC

[0x00101010]

GitHub marked this merged because its commits were fast-forwarded into the branch of #199 (consolidating 8 PRs into 3). Nothing reached main; review continues on #199.