Usage is the spend page — daily, by assistant, AI vs run cost.
PR 2 proposal on top of the Billing simplification — Usage as its own nav destination:
shipped BillingUsage.tsx restyled, plus proposed month picker, expandable
per-assistant rows, and an explicit empty state.
The widths drawn here are samples of a fluid
continuum, not the only states that exist — content (spacing, type, gaps, card/column widths)
scales continuously between them, each clamp reading a named container. Structure (rail,
row↔stack, grid columns) steps only at sm 640 · md 768 ·
lg 1024; radius, hairlines, and pills never scale. Kit: design-canon.md U8.
Reading order in this document: § Desktop
journey first — every desktop frame, full flow, journey order — then § Mobile
journey — 375 below it — every mobile frame, same order, laid out side by side as a
wrapping grid (never a tall single-file column of phone screens). Two sections, never
interleaved — a review-document convention only (this repo's design-canon.md §
Mockup review reading order). Mobile 375px is still designed and scored FIRST in the /design
ritual (kit canon U5/U8) — the two rules never conflate.
BillingUsage.tsx restyled + PR 2 proposals
MetricStatCard), daily/monthly/yearly toggle, "AI vs run cost" split bar + legend wording, external-apps notice.surface-hairline boxes; KPI values pinned to the 26px/500 tier lock (T1124).Button group in BillingUsage.tsx), restyled to a pill segment.position:absolute, z-index above the KPI cards, page beneath unchanged..kpi hairline-row shape as Billing — never a squeezed 3-up grid at 375px..length > 0 and silently don't render.