feat(scaling): detail pages and unified run index

[0x00101010]

Summary

Why

The guardrail strip on the first screen hides each guardrail's help behind a popover, and outcomes metrics had no permanent home. A guardrails page gives both a home. The first screen's snapshot loading and as-of header move into a shared helper so detail pages show the same freshness warning.

What

• loadSnapshot.tsx: snapshot loading, the unconfigured/invalid states and the as-of/stale header (optional breadcrumb back to /scaling), used by /scaling and the new page.
• /scaling/guardrails: every guardrail with value, threshold, tag, owner, status and inline help, then the outcomes section as a table (metric and note, value, status, window with range, query, source) plus its gaps.
• First-screen guardrail heading becomes a Guardrails → link.
• The validator rejects a sections[].id outside da, execution, state, networking, outcomes, so a section cannot exist without a page.
• /scaling/guardrails 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 → this PR.
• Internal-only through the existing scaling surface; the public build returns 404 for /scaling/guardrails, and the generated public docs do not list it.

Screenshots

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

/scaling/guardrails at 1280 px:

/scaling/guardrails at 360 px (tables scroll horizontally inside their card):

/scaling at 1280 px with the Guardrails → link:

Test plan

• npm test, npm run typecheck, npm run lint, npm run build, npm run build:internal, npm run llms -- --check
• page.test.tsx: guardrails page shows the breadcrumb, as-of header, each guardrail's help and the outcomes row with query and window; first screen links to it.
• snapshot.test.ts: an unknown section id fails validation.
• Rendered /scaling and /scaling/guardrails at 360 px and 1280 px with the synthetic fixture; external dev server returns 404 for both.

Consolidated

This PR now also carries #200 (per-area detail pages) and #201 (unified /scaling/runs index; run data layer moved from app/benchmark). Base is now feat/scaling-ladder (#196). Commits are unchanged; review them in order. Stack: #194 → #196 → #199.

[vercel]

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

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

[cb-heimdall]

✅ Heimdall Review Status

Requirement	Status	More Info
Reviews	✅ 1/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1