# Web client — parity checklist The browser client's acceptance gate. **The target is the Android app's feature set** (`android/`), rendered for the web. A row is only `done` when the feature works in the browser against a live server **and** a review stage captured the rendered result through `test/ui-smoke.mjs` (or an extension of it). A green unit test, or a code change without a capture, is `partial` at best. Status legend: `todo` · `partial` (some of it works) · `done` (working + captured). ## Transport and connection | # | Feature (Android counterpart) | Protocol | Status | | --- | --- | --- | --- | | T1 | Server-URL entry + validation rules (`data/transport/ServerUrl.kt`) | — | done | | T2 | One reused socket, id matching, request timeout, not-connected guard (`PipelinesClient.kt`) | — | done | | T3 | Connect / disconnect / manual reconnect | `ping` | done — connection now lives only in the Settings Connection section (L2–L4 moved it out of the chrome). `Connect` is connect-only, `Disconnect` closes the shared socket, and `Reconnect` re-opens the validated endpoint immediately, resetting the client's attempt/backoff; all three drive the page's one client. Captured 2026-10-19: `captures/84-shell-settings-connection-1440x900.png` (the connected status card and the Disconnect/Connect pair) and `captures/L1-settings-idle.png` (idle: Connect + Reconnect). The shell's rail/dock dot+word control mirrors the state and is a Settings shortcut (`captures/85-shell-status-indicator-1440x900.png`); the old header URL field, Connect/Disconnect button and state badge are gone | | T4 | Backoff recovery + foreground reconnect after sleep/blur (`ConnectionRecovery.kt`, `ForegroundReconnector.kt`) | — | done — the client's capped backoff is surfaced honestly rather than rewritten: `captures/29-disconnected-banner.png` shows the Settings status card `Disconnected` / `Connection closed (1006)` / `Retrying with backoff…`, while the shell's compact indicator reads `Disconnected`. The attempt number is named only while Connecting (`Connecting (attempt N)…`), matching `ConnectionBanner.kt`; the disconnected card deliberately omits it rather than diverging from Android's wording. The foreground-reconnect **decision** (`foregroundAction`) is unit-tested in `test/connection.test.mjs` (Idle→LeaveAlone; Connecting/Disconnected→Reconnect; Connected→`confirmedAlive ? LeaveAlone : Reconnect`); the **rendered recovery** is captured in `captures/30-reconnect-recovered.png`, where the page (asserted still `Disconnected`) is pointed back at the live server and the browser's own `online` event drives it to a green Connected. The browser uses its `online`/`visibilitychange` event as the liveness signal, so a still-Connected socket is left alone (no in-page positive ping probe is needed; a documented deviation from `ForegroundReconnector`'s positive ping) | | T5 | Connection status + live badge; build/protocol mismatch warning | `pong` build/protocol | done — the full status card lives in Settings (never overlaying content): green `Connected` + `Server build …` + `Server time …` (`captures/84-shell-settings-connection-1440x900.png`), `Disconnected` + the server's message + `Retrying with backoff…` (`captures/L1-settings-disconnected.png`), `Connecting (attempt N)…` (`captures/L1-settings-connecting.png`) and idle `Not connected` (`captures/L1-settings-idle.png`). The shell keeps only a compact dot+word indicator (connected / connecting / disconnected / not connected / not configured) in the rail footer and the narrow bar; it is never colour-only. The protocol-mismatch warning is rendered in the same Settings Connection section (and remains unit-tested via `protocolMismatch`); no live mismatch is expected because the server reports protocol 1. A minimal dot+word live badge still marks the run stream in the runs list/detail (`live` / `reconnecting` / `not live`, per `LiveBadge.kt`/`RunStream.kt`). The build line comes from the `pong` in `SettingsScreen.kt`'s own shape, `Server build {version} ({commit})`; a dirty tree is already marked in `version` by `internal/buildinfo` (`-dirty`), so no duplicate `+dirty` marker is added | | T6 | Artifact URL resolution against the configured server (`resolveArtifactUrl`) | `GET /artifacts/…` | done (URL only) | ## Pipelines | # | Feature | Protocol | Status | | --- | --- | --- | --- | | P1 | Pipeline list | `list_pipelines` | done — row: name; `id {id} · v{version} · {N stages}`; `updated d MMM HH:mm`; last-run line joined from `list_runs` (status chip + `{ago} · {duration} · run {id}`, or `no runs recorded`) | | P2 | Filter + sort (status/name/updated) | client-side | done — Filter menu (name contains, Runs Any/Has runs/No runs, Last run status over the 7 server states, Clear filters) + Sort menu (Server order default, Name A–Z/Z–A, Most recent run, Fewest/Most stages, Reset); server order preserved | | P3 | Pipeline detail: stages, graph, versions, last run, content hash | `get_pipeline` | done — Summary/Graph/Source tabs; Summary shows content hash (monospace), latest version (`v{n}` or blank), created/updated, and a collapsed-by-default Versions section. Graph tab shows the browser guidance note plus the rendered workflow graph (P6) | | P4 | Templates gallery + template detail | `list_templates`, `validate` | done | | P5 | Create pipeline from a template (validate then submit) | `validate`, `submit` | done — a template detail offers the action `Create pipeline from this template`; its dialog's title is `Create from {name}` (a blank name falling back to the template key), it has one required field labelled `New pipeline name (required)`, the note `Creates a new draft pipeline on the server from this template's source; it is not run.`, and Create/Cancel buttons (Cancel reads `Close` after a success). Create is disabled while the name is blank (whitespace counts) or while sending, and the field locks while sending and after a success. Submitting validates the template's source first (`validate`); a validation refusal shows the server's own error in the still-open dialog and sends no `submit`. A passing validate submits exactly `{type:'submit',name:,source: