feat(scaling): add ceilings and guardrails to the snapshot

[0x00101010]

Summary

Why

The scorecard needs to say which bottleneck caps throughput and whether the charter guardrails hold. Today the snapshot has no place for a per-area ceiling with its formula and inputs, nor for a guardrail with its threshold, and nothing stops a hand-edited status from contradicting the numbers beside it.

What

• ceilings[]: one entry per area (da, execution, state, networking, all required) with a tagged value in Mgas/s, the formula, dated inputs (observed / configured / provisional / pending; null exactly when pending), an optional reason, and help.
• deriveBinding(ceilings): the lowest measured or modeled ceiling; estimates and unmodeled areas never bind, and the binding area is never stored.
• guardrails[]: value, threshold, comparator, thresholdTag (unset exactly when the threshold is null), owner, date, help. status must be unknown without both numbers and must match value <comparator> threshold otherwise; ids are unique.
• Synthetic fixture and tests cover every tag, each rule, and binding derivation; scaling:check prints the binding ceiling and guardrail count.

Notes

• No page changes: the page validates and ignores both arrays.

Screenshots

N/A (no visual changes)

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 prints binding ceiling da 95 Mgas/s, 4 guardrails

[vercel]

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

Project	Deployment	Actions	Updated
omni-ui	Ready	Preview	Oct 16, 2026 5:36am UTC

[0x00101010]

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