# Browser instrument dashboard

The browser dashboard uses one restrained monochrome component system across
Chat, Agent, Voice, Generate, Projects, Dashboard, Activity, Discover, Settings,
and their dialogs and forms. The user's instrument styleguide supplies fine
rules, deliberate readings, and sharp corners; the tracker reference supplies
workspace hierarchy and responsive navigation. This is the real browser
application, implemented with its existing HTML, CSS, and JavaScript.

The canvas is black with white/gray text, or its white/black light counterpart.
System appearance follows the browser preference. Existing saved theme aliases
and server preferences feed the same theme store. Actual media keeps its own
pixels. Keyboard focus and selected controls use inverse contrast, while
warnings and errors retain readable text rather than relying on color.

`packages/cli/src/api/web-instrument-style.ts` replaces the accumulated theme
layers. It covers the shell, responsive route grids, navigation, forms,
telemetry, conversation, code, workspace picker, menus, dialogs, and media.
Phone controls have at least 44px touch targets; panes stack instead of reducing
controls to tiny text. No framework or dependency was added.

The composer has a labeled, square Send control with explicit neutral hover,
focus and disabled states. Desktop navigation resizes by dragging its divider;
dragging closed retains a thin arrow handle. Clicking the handle, dragging right,
or using Enter/arrow keys restores navigation. The divider supports Home/End and
retains the previous expanded width. Mobile uses its existing drawer, independently
of the saved desktop collapse state. Navigation and session lists scroll within
their own areas so Settings and media remain reachable in short windows.

Generate separates mode selection, generation parameters, results, and the
library. Model storage is collapsed by default. Image, video, and audio previews
use authenticated daemon file validation before acquiring blobs. Result
downloads remain disabled until that validation succeeds. Service events do not
claim to describe the current request's progress. Media behavior and its own
focused tests are documented in the separate media runtime verification.

Direct route activation now waits for route state initialization. A configured
same-origin UI prefix survives navigation, history, and session queries, while a
root-mounted UI can still use a separate API prefix. Initial route state is
seeded before store subscribers can rewrite its URL.

Verification uses `node scripts/test-web-instrument-live.mjs --run --out PATH`
after rebuilding the CLI. It serves the compiled production HTML from an
isolated local fixture and launches existing Chromium with GPU rendering
disabled. All nonfixture HTTP requests are blocked. It never connects to the
running daemon, starts inference, loads a model, or changes a real service.
Every supplied media item is explicitly marked DEMO.

The live check covers nine direct prefixed routes at widths 360, 768, and 1440 in
both themes, rendered neutral colors and square controls, horizontal overflow,
decoded image/video/audio previews, authenticated exact-byte downloads, gallery
dialog keyboard access and focus restoration, and theme persistence. It records
navigation timings and observed main-thread long tasks as local fixture
observations, not as a general performance guarantee. The recorded HTML/CSS
sizes likewise describe payload size rather than perceived responsiveness.

The mandatory daemon transport gate remains:

```sh
cd packages/cli
pnpm exec vitest run tests/web-chat-transport-lifecycle.test.ts \
  tests/web-ui-client-runtime.test.ts tests/web-ui-script.test.ts
```

These tests preserve split SSE frames, delayed and subprocess failures,
authenticated events, session reattachment, daemon-owned Stop, and validated
external/file link controls. Additional presentation and route tests are in
`web-ui-instrument-style.test.ts`, `web-ui-observability-layout.test.ts`, and
`web-ui-route-base.test.ts`.

The durable browser receipt and selected screenshots are in
`docs/work-orders/evidence/web-instrument-dashboard-live-20261016.json` and the
adjacent `web-instrument-*-20261016.png` files. The receipt clearly distinguishes
the compiled production HTML from the fixture's API-base/DEMO annotations.
Optional existing external syntax assets are blocked during the check; the
dashboard continues to work with its plain code fallback.

The fixture checks left the running daemon unchanged. After the operator asked
for the live URL, the verified package was installed and the daemon restarted.
The [deployment receipt](evidence/interface-daemon-deployment-20261016.json)
confirms the exact tested HTML is served at `http://127.0.0.1:11435/` and saved
sessions and configuration are preserved.

The Send/sidebar follow-up passed 56 focused browser and transport tests plus
[18 actual Chromium interaction checks](evidence/web-sidebar-send-repair-20261016.json)
in both themes. Those checks cover real pointer capture, drag/click/keyboard
reopening, draft and cursor retention, all nine navigation destinations in a
short window with 1,106 fixture sessions, mobile drawers and reload persistence.
The [package check](evidence/browser-controls-package-verification-20261016.json)
and [live deployment receipt](evidence/browser-controls-deployment-20261016.json)
bind that repair to the exact HTML served by the running daemon.
