feat(scaling): snapshot schema v2 with ladder, ceilings and guardrails

[0x00101010]

Summary

Why

The scorecard snapshot's headline row cannot express what the scaling page needs to show next: where mainnet runs today against its operating point, configured limit and the highest rate a qualified run has sustained, each with its own confidence. Progress entries also have no place for a realized effect or the evidence behind it.

What

• schemaVersion: 2: headline becomes ladder (observed p50/p99, operating point, configured limit, qualified), each a rung with a measured / modeled / estimated / not-measured / not-modeled / not-established tag; values are null under the three non-measured tags, never 0.
• translations (gasPerPayment, gasPerSwap) and new work fields area, expected, realized, evidence, linear; realized requires evidence, linear.progress must be in [0, 1].
• Version 1 files are rejected with a message naming the migration; isStale(collectedAt, now, days = 10) is exported and drives the page's stale banner.
• app/scaling/fixtures/synthetic.v2.json: invented values covering every tag, used by the tests and by npm run scaling:check.
• The page maps the four ladder rungs into the existing headline cards and shows expected / realized impact with the evidence link on work cards; no new UI.

Notes

• The stale banner threshold moves from 7 to 10 days to match the shared helper's default.
• help strings (short explanations per rung) are stored but not rendered yet.

Screenshots

/scaling on the internal build, rendering app/scaling/fixtures/synthetic.v2.json (invented values):

Test plan

• npm test, npm run typecheck, npm run lint, npm run build, npm run build:internal, npm run llms -- --check
• npm run scaling:check -- app/scaling/fixtures/synthetic.v2.json passes; a schemaVersion: 1 file fails with the migration message
• /scaling rendered from the fixture on the internal build

Consolidated

This PR now also carries #195 (ceilings, deriveBinding, guardrails, stricter validator rules). Commits are unchanged; review them in order.

[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

[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