feat(scaling): ceiling cards and guardrails

[0x00101010]

Summary

Why

The ladder shows only the binding ceiling. Readers also need each bottleneck's ceiling, how it was derived, and which guardrails hold, without implying that a breached SLO means saturation.

What

• CeilingCards: four cards in a fixed order (DA, execution, state, networking) with value or —, tag, a Binding badge on the deriveBinding result, the formula, inputs as name · value unit · status · asOf, the reason when present, and an Info popover. One column on phones, two from 640 px, four from 1024 px.
• Guardrails: a table of label, value, threshold with comparator and unit (≤ 80 %), a Provisional/Unset tag and owner, and a status dot that is grey for unknown. Footnote: breached SLOs are not attributed to saturation until triaged.
• Tag: shared dashed pill, also used by the ladder's unplaced rungs.
• Both mount under the ladder; sections and the work list are unchanged.

Notes

• Stacked on feat(scaling): first screen with ladder, ceilings, guardrails and progress #196 (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).
• Card titles link to /scaling/<area>, which lands in a later PR; until then they 404.
• At 360 px the guardrail table scrolls horizontally to reach the status column.

Screenshots

/scaling on the internal build with invented fixtures (none of these numbers describe a real network).

Committed synthetic fixture, 1280 px (DA binds):

Same fixture with the execution ceiling at 90 Mgas/s measured, 1280 px (badge moves to execution):

360 px, both fixtures:

Test plan

• npm test, npm run typecheck, npm run lint, npm run build, npm run build:internal, npm run llms -- --check
• firstScreen.test.tsx: fixed card order with tags, binding badge moves when a lower ceiling is measured, null-value card shows —, reason and pending inputs; guardrail comparators, tags, owner, and no green/red for unknown.
• Rendered at 360 px and 1280 px with both fixtures: 1 and 4 columns, badge on DA then execution, null-threshold row grey, all 14 Info triggers reached by Tab.

[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:20pm UTC

[0x00101010]

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