The admin portal grew from a single index.html into a four-page liquid-glass
console (dashboard, models, decisions, controls) but README.md still described
it as a 'small management UI' pointing only at index.html.
- README.md: rewrite the admin section to describe each of the four pages,
embed current screenshots (captured against the live service at :8080) under
assets/screenshots/, add a Features bullet and TOC entry for the portal, add
admin.py to the Modules table and test_admin_frontend.py to the test matrix,
and correct the test count 731 -> 733.
- CLAUDE.md: correct the tests count 731 -> 733.
- AGENTS.md: correct the stale stack-snapshot and post-change test counts
(562 -> 733).
The 562/568/673 figures in code_reviews/*.md are left untouched - those are
point-in-time audit records, not live counts.
Formalize how to touch the admin portal so results transfer to the next page:
- code_plans/admin-work-framework.md: the 5-move method distilled from the
controls relayout (c22bbae) — surface diagnosis, grammar-first rule
extraction, S1-S5 survival re-verification, the pytest + Playwright-1400/800
+ REFRESH_MS-idle evidence bar, and writing the commit as a standalone
learning input.
- code_plans/admin-design-standards.md: add the settings-row and card-level
layout grammar as transferable rules (one CSS-grid row key|meta|176px;
never restate a control's own value; single-line button strip goes full
width in .card-actions) so the Controls layout becomes apply-able, not just
described.
- AGENTS.md: point admin editors at the framework alongside the standards.
Working artifacts accumulated during the admin frontend uplift: the
facelift plan, the layout/viewport QA captures taken while iterating, and
two code_reviews docs (TUI panel polish plan, verdict-bar label review).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VRQXz5SYZYVWscxS1QqF6U
The page had three distinct layout problems, all visible at a glance:
- Operational Triggers is a single line of buttons but sat in a col-xl-6
next to the much taller Runtime Knobs, so half that row was permanently
empty. No align-items value fixes that; the card is now a full-width
strip with its buttons in .card-actions.
- Both settings panels used a 5/3/4 Bootstrap grid, which put the control
mid-row at three different widths and spent a whole trailing column
restating the value the control already displays (true / true / 0.1).
Both now use one CSS-grid row -- key | meta | 176px control -- so every
switch, input and select lands on the same right edge.
- Rows alternated switches and text inputs, which differ ~10px in natural
height and read as ragged. Fixed at min-height 38px.
The freed meta column now carries only what a control cannot show: the
kWh unit on the two energy keys, and an amber `file: <value>` badge when a
runtime knob disagrees with config.yaml.
Two consistency fixes alongside: persisted-config booleans were bare
checkboxes while the runtime knobs were switches, and dotted keys now dim
the scope so the leaf reads first.
Persisted Config also stopped being a blind save -- edits mark the row and
the button counts them (`Save 2 changes`, disabled at zero), and only
dirty rows are written rather than every allowlisted key on every click.
The frontend test asserted on that button's literal text, which is now
rendered from the dirty count, so it asserts on the element id instead.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VRQXz5SYZYVWscxS1QqF6U
circuit_breaker was the one runtime knob with no toggle switch, silently
falling through to plain text. Root cause: GET /admin/api/runtime reported
it as a nested {"enabled": ...} object while every other knob (including
its own POST key, circuit_breaker_enabled) is a flat bool -- an
inconsistency with no functional reason, introduced when the knob was
added. Flattened to match; the frontend's existing boolean-detection logic
picks it up automatically, no JS special-casing needed. Updated the one
test asserting the old nested shape.
default_flex_preference (Runtime Knobs) and routing.default_flex_preference
+ logging.level (Persisted Config) were free-text inputs for values that
are actually closed 4-way enums on the backend (FlexPreference; logging's
own field_validator). Now <select> dropdowns sourced from those legal
values, shared between both panels via one ENUM_VALUES table instead of
duplicating the list.
Also: Operational Triggers no longer stretches to match Runtime Knobs'
height (row-level align-items-start), which was leaving a slab of dead
space under its four buttons.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VRQXz5SYZYVWscxS1QqF6U
Decisions page: 50/100/250-per-page pagination with Prev/Next and a page
indicator (fetch bumped to 1000 rows to have enough to paginate through);
category/source get the same colored-badge treatment kind already had
(tier reverted back to plain colored text -- a filled pill was overkill);
capability flags (tools/images/json-mode/streamed) as compact on-only
chips in a new Flags column; row padding and font-size tightened for a
noticeably denser scan.
Fixes:
- Category Breakdown label truncation ("tool_use_ag...", "coding_refac...")
-- it was reusing Verdict Mix's 88px label column, sized for short verdict
words, not task_category names. Split into its own 128px .cat-label.
- Controls page: Operational Triggers was stretching to match Runtime
Knobs' height (Bootstrap row default align-items:stretch) and sitting on
a pile of dead space below its own content. align-items-start on that
row only; the full-width Persisted Config row below is unaffected.
AGENTS.md/CLAUDE.md: admin portal doc updates from the parallel opencode
session, plus code_plans/admin-design-standards.md it now links to as the
one design-system reference for admin/frontend/*.html.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VRQXz5SYZYVWscxS1QqF6U
Standalone pages for Models and the new Decisions log (filter/search over
route_decisions, live via SSE), full page/page-wrapper/page-header/page-body
shell on Dashboard/Controls/Models/Decisions, and a glass-effect pass
(translucent blurred navbar/cards/buttons/badges/progress bars) over the
previously flat Tabler skin.
Dashboard reshuffle: Quota Meter and Warnings cards replaced by a header
capsule chip (click -> popup, also links out to the NeuralWatt dashboard)
and a navbar bell with a dismissible dropdown; Category Breakdown gets real
bars instead of bare dots; Per-Model Usage is a responsive grid with a
Calls/Cost/Energy sort toggle; Recent Decisions moved to the bottom with a
link to the full log.
Fixes bundled in along the way:
- objective.max_energy_per_request: Persisted Config was sending the
literal string "null" instead of JSON null, so every save 422'd. Null
fields now render empty with a placeholder and save as real null.
- Category Breakdown's counts were unreadable: bg-secondary badge text
color was too close to its own background.
- Logo lost its color/face: the filter:none override lost the cascade to
Tabler's [data-bs-theme=dark] .navbar-brand-autodark rule (higher
specificity); needed !important. controls.html was missing the fix,
the favicon link, and the 36px (now 45px) sizing entirely.
- Persistent left-edge gap at wide viewports: this Chrome/Linux build
reports a phantom left margin on <html> equal to the scrollbar's width
whenever <html> itself is the scrolling element. Moved the scroll
context down to <body>.
- Warnings dropdown rendered behind the quota chip: backdrop-filter on
header.navbar creates a stacking context, and the later-in-DOM .page
element (whose quota chip also has backdrop-filter) painted on top of
it regardless of the dropdown's own z-index. Pinned the navbar's
stacking context above it explicitly.
- Admin pages had no Cache-Control, so browsers served stale pages after
every edit during iteration; now explicitly no-cache.
AGENTS.md: manual/dev instances now bind :8081 instead of a bare 8080,
with an explicit warning not to pkill/kill anything matching
uvicorn/dispatcher/8080 -- that's the systemd-managed production
instance (opencode's own model traffic runs through it), and killing it
by pattern match was today's actual cause of the router's "flaky
restarts" incident, documented in CLAUDE.md.
config.yaml: circuit_breaker, session_cache, pinch, and pinch.relevance
flipped to enabled -- deliberate, to start collecting real-traffic signal
on knobs that shipped off by design.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VRQXz5SYZYVWscxS1QqF6U
Cosmetic only: 0.10 -> 0.1, null -> blank scalar, and block-list re-indentation produced by the ruamel.yaml round-trip write path (no semantic value changes). Harmless, and shows what an allowlisted /admin/api/config write produces.
Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)
Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Add the admin web portal section to README (dashboards, triggers, runtime toggles, config edits, availability overrides) and document admin.py/admin_schema.sql/admin/frontend in CLAUDE.md. Update the test count to the verified 731 tests across 40 files.
Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)
Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Mount the admin portal at /admin via build_router(cfg, _db, root), extend the startup migration to ensure admin tables (renaming _ensure_route_decisions_table -> _ensure_tables), and feed model deprecation overrides into the routing hard filters through _admin_deprecated_models(). Pin ruamel.yaml==0.18.10 (comment-preserving writes) for the /admin/api/config persisted-config editor.
Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)
Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
