feat(webui): add context budget controls - #276
Conversation
|
LGTM — approved at Visual (Aaron's bar): all three renders reviewed — 1600px table, 800px two-column cards, 390px single-column; no horizontal overflow; Config Center idiom held; provenance chips with clamp expiry; honest activation copy. Every displayed derivation checked against the exact integer math: spark 205,002 / 5.4+terra 1,271,257 / 5.4-mini 550,365 / 5.5 570,002 / overridden luna 800K→1,095,000 / clamped sol 300K→575,000 — all exact, all server-served. Mutation verification, four load-bearing gates: (M-A) dropping Contract checks: browser renders Independent gates at Merging to the campaign branch. |
Summary
Final build phase of the context-budget campaign (plan §12):
POST /api/context/windows/clearGET /api/context/windows; the browser never recomputes targetsui/distValidation
npm run check: passed, including templates, template bindings, UI race/save-boundary gates, and byte-current dist buildgit diff --check: cleanVisual verification
Authenticated-shape mock navigation and interaction were rendered at 1600, 800, and 390 CSS-pixel widths. Each viewport showed seven canonical models, no document or panel horizontal overflow, responsive cards below 900px, backend-derived values, override and temporary-clamp provenance, expiry copy, and the account-scoped clear action.
No deployment or release pipeline was run.