# 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). ### Artifact browser hand-off (2026-10-20) Artifact opens now use one validated navigation helper across gallery/list, verdict, audit/session/repair, search, viewer and chat links. Android standalone apps request an explicit browser-family VIEW intent: an implicit HTTPS intent or `_blank` alone can be captured by the current WebAPK. Browser packages are fixed by the known browser family, never supplied by artifact/model text; other environments retain native `_blank` links with external/noopener/noreferrer. Copy/Share keep ordinary HTTP(S) URLs. No code replaces the app's own location. Markdown root-relative artifact links are clickable; executable/local URLs remain unlinked. The viewer has an explicit **Open in browser** link and wrapping mobile actions. All file types open in the browser by default; **Preview in app** is an explicit secondary gallery/list action for media and Markdown/text. On touch screens these actions are visible, separate from Open, and at least 44px. `test/artifact-browser-probe.mjs` verifies an actual new browser target while the app URL/history remain unchanged, then inspects Android standalone hand-offs for tiles (HTML/Markdown/image), list, search, chat, session and viewer controls. Copy retains HTTP, unsafe links stay inert, and actions fit at 390/420px. Captures are in the approved OpenCode temporary `artifact-browser-captures/` directory. **Android's actual OS/browser launch and Back behavior require the user's phone check**; the desktop test does not claim to reproduce an installed Android WebAPK. Shell cache version is bumped so the new navigation modules refresh on the next app reload. ### List miniature follow-up (2026-10-20) Workflow and run miniatures now share the existing graph layout, right-aligned inside their SVG as well as their row, with a 6px extra trailing inset. Run LIST nodes now use each stage's last visit: success green, failure red, running accent, waiting amber and queued a distinct muted tint. Unvisited/unknown nodes are neutral hollow/dashed; **no aggregate run-status tint is inherited**. Taken edges use recorded outcome/target routes, including loops and branches. The additive `graph_evidence` summary projection reads only five routing/status fields from `run_steps`, compacts repeated loops, and batches 100 run IDs per query (not N detail fetches). Subscribe snapshots seed the same evidence; coalesced live frames preserve every changed visit in `graph_visits` and the client maintains last-stage/distinct-route evidence without a detail fetch. Older summaries remain honestly unknown. Topology comes from the run's own graph, an exact-version pipeline summary, or one cached `get_pipeline(id, version)` read per endpoint/version (never `get_run` per row, never a fallback to latest). Unavailable graphs stay absent. No schema migration or new private input/output/transcript payload is needed. Scratch browser extension `test/miniatures-browser.mjs` verifies 390/420/1100px alignment, two successful stages before failure plus never-visited branches, waiting/running/queued states, legacy unknown evidence, wrapped titles, separate applied filters and no document overflow; captures and `geometry.json` are in `/private/var/folders/jp/q0qvjyg54fl_c5vhhk1ylz2m0000gn/T/opencode/per-stage-run-miniatures-captures/`. These are deterministic fixture captures, not a new live-server parity claim. Collapsed desktop navigation additionally gives Expand its own 40px flow slot above the Pipelines brand instead of overlaying it. The same scratch browser extension asserts non-overlap with brand and first destination, expands again through the real button at 1100px, and checks the rail remains hidden at 390/420px. Captures: `rail-collapsed-1100.png`, `rail-expanded-1100.png` in the directory above. Mobile and the expanded rail are unchanged. ### Stage definition popup follow-up (2026-10-20) P6/R5 follow-up: **partial** against the live-server parity gate; verified with the scratch-only `node test/ui-stage-definition.mjs ../.ui-stage-definition` browser extension. Clicking a stage in either graph now opens the managed audit popup, without replacing the current pane or changing its route. Timeline visit panes remain available, and their Audit & debug Definition tab shares the viewer. Rendered uses the existing Markdown/code renderer; Raw is the exact authored stage source slice (including whitespace, custom blocks and shorthand), not a serialization of the normalized graph. Run definitions request `get_pipeline` with the recorded pipeline id/version, never latest. Missing source and load errors are explicit; terminal nodes have no authored stage definition. Scratch captures: `.ui-stage-definition/01-run-definition-rendered.png`, `02-run-definition-raw.png`, `03-pipeline-definition-rendered.png`, `04-visit-definition-nested.png`, `05-definition-missing-source.png`, `06-definition-load-failed.png`, `07-definition-terminal.png`, and `08-definition-narrow.png`, `09-definition-loading.png`, and `10-definition-missing-version.png`. Real browser assertions cover exact source, pinned version, unchanged route, nested-pane preservation, Tab trapping and Escape/focus restoration. No deployed service, live workflow or device was used. ### Chat audit follow-up (2026-10-20, partial — fresh UI captures pending) Composer fit and vertical alignment follow-up (2026-10-20): attachment, Send and Stop controls (44px square; 48px with a coarse pointer) are vertically centered on the textarea, including multiline drafts. The single-line input matches their height, and six complete auto-grown text lines fit before scrolling. Send remains available while running; its adjacent Stop slot is reserved even while idle so state changes do not rewrap a draft. Monochrome CSS SVG masks replace the platform-dependent button glyph rendering, preserving existing accessible names. Back/title, protocol and keyboard geometry are untouched. The visible placeholder is shortened to `Message the agent…` so an empty field stays one aligned line; the full slash-command hint remains its accessible name. `node test/composer-fit-browser.mjs ../.ui-composer-fit-after` verifies the real chat view and input handlers using deterministic fixtures at 390/420/1100px: empty, single/multiline, running, six/ten-line drafts, attachments and simulated keyboard geometry. `--before` serves HEAD's CSS for comparison (run before committing, or on the parent revision). Captures and `geometry.json` are in `.ui-composer-fit-before/` and `.ui-composer-fit-after/` in the isolated composer worktree. This is scratch-browser evidence, not a live-server parity upgrade; real iOS/Android keyboards were not tested. Integration additionally captured 28 states under the approved OpenCode temporary `final-composer-fit/` directory, including browser-emulated coarse pointers at 390/420px: empty input and buttons are exactly 48px, and adding Stop does not shift the input. Normal-pointer empty fields and controls are exactly 44px. These are not real-phone keyboard claims. Codex model follow-up (partial, fixture-tested; fresh UI captures pending): model controls now include Codex, using the app-server `model/list` catalog and current `thread/read`/`thread/list` model metadata. Selecting a model saves a per-chat Pipelines registry choice, explicitly labelled **next turn**, and adds the verified `model` override to the next user-initiated `turn/start`, including after a Pipelines restart. This does not call `thread/resume`, start a goal, edit Codex configuration, or claim the remote thread changed before a turn is sent. Versioned protocol evidence and synthetic fixtures: `internal/codex/testdata/`. The following supersedes older C8/B18 implementation details below: - Web attachments are limited to **1 MiB total and eight files**, matching the server. Unsupported harnesses reject attachments before upload storage/queueing. - Uploads live in a private durable `~/.pipelines-chat-attachments` directory (override: `PIPELINES_CHAT_ATTACHMENT_DIR`, must already have a parent and be private). Storage is capped at 64 MiB/512 files; the next upload collects unleased files older than seven days. Queued/in-flight uploads are leased, never collected. Restart retains files, but not in-memory leases or the existing prompt queue. - OpenCode provider-step ends are intermediate progress; foreground completion is read from V2 `/api/session/active`. Failed readback does not advance a queue. - Create replies report `instruction_status` as `applied`, `unsupported`, `failed` or `not_requested`; the UI shows applied/unsupported/failed as chat notices. - The model picker uses the shared modal manager for focus trapping and Escape. Unit/HTTP-fixture regressions cover these changes. No live workflow or deployed service was used; new rendered-state captures are **not yet available**. Audit additions (2026-10-20): **partial** — explicit run Report format selector (`output_format`, HTML/Markdown/no requirement), and session export empty/failed/partial explanations. Unit-tested; browser captures missing under the audit's no-live-runs constraint. Existing captured states below are unchanged. Automatic session export recovery additionally shows pending/running/complete/ exhausted job status and its bounded attempt count in the visit pane. Backend recovery is fixture-tested; this new status line remains **partial**, without a browser capture (no live runs were authorized). ## 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: