Files
pipelines/web/PARITY.md
T
alan 94d4ff02d3 web: run detail Graph tab with executed styling and stage panes (R5)
Add the run detail's Graph tab (between Summary and Input), reusing the
shared src/graph.js renderer (P6) rather than a second renderer. In run
mode a visited stage is executed (solid fill + border), an unvisited one
hollow with a dashed muted border; a terminal is executed only when a
visit resolved to it; a route is executed only when a recorded visit
produced that outcome (solid with an arrowhead, success first, error
last, others alphabetical, `error*` for the fallback). The Executed /
Not executed legend shows only for a run. While the run executes the
current stage carries a pulsing halo (static under prefers-reduced-motion)
and a ticking elapsed badge; a finished run shows neither. Clicking a
stage opens the existing visit pane at that stage's latest visit, and
Back/Escape return focus. The empty state is the exact
"This server did not include the run graph."

extend src/graph.js with the run-mode inputs (runState-driven executed
styling, legend, active halo/elapsed badge); keep app.js to wiring.
Extend graph.test.mjs with focused run-mode unit tests and ui-smoke.mjs
with the run 438 / run 440 / live-run captures. Mark R5 done in
web/PARITY.md.

Checks: node --check on every touched file; cd web && node --test test/
(178 pass, 0 fail); cd web && node test/ui-smoke.mjs --out captures
(UI SMOKE PASS, captures 28-31).
2026-10-19 04:05:37 +01:00

10 KiB
Raw Blame History

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 partial (connect works; no reconnect UI)
T4 Backoff recovery + foreground reconnect after sleep/blur (ConnectionRecovery.kt, ForegroundReconnector.kt) — todo
T5 Connection banner + live badge; build/protocol mismatch warning pong build/protocol todo
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 todo
P6 Workflow graph rendering (nodes, edges, stage panes) get_pipeline done (captured 2026-10-19: nodes + labelled outcome edges + success/failure terminals, an opened stage definition pane and the expanded view — captures/08-pipeline-graph.png, captures/08a-pipeline-graph-stage-pane.png, captures/08b-pipeline-graph-expanded.png). Reusable src/graph.js (mount + pure helpers: layout, edges, error*, lanes, fit/clamp/zoom, hit-test, stage-definition fields); the definition view (every route executed, no legend) plus, since R5, a run-mode view driven by runState (executed/not-executed stages and routes, the Executed / Not executed legend, the live halo/elapsed badge). Pane labels match the app's own vocabulary (Outcomes, Tools) rather than the checklist's category words

Runs

# Feature Protocol Status
R1 Run history list with status roll-up list_runs done
R2 Filter by status, sort, "needs you" markers client-side partial (status/pipeline/time filter + sort implemented and captured; the per-row "needs you" mark has no Android counterpart and its wording is deferred to R15, still todo)
R3 Run detail: run fields, steps/visits, targets, sessions get_run done — tabbed Summary / Graph / Input / Output / Timeline; the Timeline opens a per-visit stage pane with the headline rows (Status, Outcome, Duration, Visit {v} / {max}, Model target, Target, Session), the Verdict block (option chip + reason with inline artifact links) and the visit sections Artifacts / Session / Output / Input / This run / Stage definition. Captured 2026-10-19: captures/20-run-430-summary.png, captures/23-run-430-timeline.png, captures/24-run-430-stage-artifacts.png, captures/25-run-440-verdict.png
R4 Summary tab incl. collapsible Changes viewer (raw + rendered diff) get_run file changes todo
R5 Graph tab (per-stage panes, verdicts) get_run done — the run detail's Graph tab (between Summary and Input) mounts the shared src/graph.js renderer in run mode with the app's run note: a visited stage is executed (solid fill + border), an unvisited one hollow with a dashed muted border, a terminal executed only when a visit resolved to it, a route executed only when a visit produced that outcome (solid with an arrowhead; success first, error last, others alphabetical, error* for a fallback error route), the Executed / Not executed legend (runs only, never the definition view), and — while executing — the current stage's pulsing halo + elapsed badge (a static ring under prefers-reduced-motion; nothing for a finished run). Clicking a stage opens the existing visit pane at that stage's latest visit with its Verdict; Back/Escape close it and restore focus. The empty state is the exact This server did not include the run graph. (unit-tested; no live run currently carries a graph-less payload). Captured 2026-10-19: captures/28-run-438-graph.png (finished run 438: legend + executed styling + dashed untaken routes), captures/29-run-438-graph-pane.png (a graph-opened stage pane showing a Verdict), captures/30-run-440-graph.png (failed run 440: hollow/dashed not-executed stages)
R6 Input / Output field sections per stage get_run done — one collapsed section per recorded entry, expanded as a monospace block (primitives verbatim, arrays , -joined, objects k=v , -joined), empty states "No input recorded." / "No output recorded.". Captured 2026-10-19: captures/21-run-430-input.png, captures/22-run-430-output.png, captures/27-run-output-empty.png
R7 Timeline get_run done — one compact row per visit ({stage} · visit {n}, stage-outcome chip, paperclip when artifacts recorded, duration, description = first non-blank diagnostic line else → {target}); empty state "No visits recorded.". Captured 2026-10-19: captures/23-run-430-timeline.png, captures/26-run-428-timeline-empty.png
R8 Artifacts gallery + full-screen viewer (images inline, others download/open) GET /artifacts/… done (captured 2026-10-19: captures/04-run-430-artifacts.png, captures/05-artifact-viewer.png)
R9 Session export link (read-only session.html) GET /artifacts/… done (captured 2026-10-19: captures/06-session-export-link.png)
R10 Live run updates: subscribe/unsubscribe + event fold subscribe, unsubscribe, run_event todo
R11 Human decision sheet: prompt, options, feedback decide_run todo
R12 Cancel run cancel_run todo
R13 Retry failed stage (resume) / restart from start retry_run todo
R14 Rename a run set_run_title todo
R15 Attention / "Needs you" surface: counts, open, individual dismiss, clear all derived from list_runs + run events todo

Two wording decisions in R3's stage pane, recorded here as the app-authoritative choice: the visit's exported session is titled Session (the item text said "Session export"; Android's STAGE_SESSION_TITLE is Session), and the step's session_id renders as a headline row (Status, Outcome, Duration, Visit, Model target, Target, Session), so it is not repeated in the "This run" evidence section. R5's Graph tab now renders that same shared graph in run mode (see the row above), reusing the visit pane this section describes.

# Feature Protocol Status
S1 Omni-search across pipelines, versions, runs, steps, fields, artifacts search todo
S2 Result routing (open the pipeline, run, stage, artifact) — todo

Chat

# Feature Protocol Status
C1 Session list (operator sessions, closed grouped as history) chat_sessions todo
C2 Create a chat (directory picker) chat_directories, chat_create todo
C3 Open / close / reopen a session chat_close, chat_reopen todo
C4 History with paging / "load older" chat_messages todo
C5 Live transcript: user/assistant text, one reply = one turn chat_subscribe, chat_event todo
C6 Reasoning block + tool calls with name/input for the whole lifecycle chat_event todo
C7 Markdown rendering + code blocks — todo
C8 Composer: send, stop, attachments, draft chat_prompt, chat_interrupt todo
C9 Slash commands client-side todo
C10 Permission/approval cards (allow once/always/reject) chat_permission, chat_reply todo
C11 Background tasks bar: running shells only, capped + scrollable, bounded output page chat_shells, chat_shell_output todo
C12 Human-decision notices inside chat + dismiss chat_event todo
C13 Local rename/hide, seen state, persistence to localStorage client-side todo
C14 Scroll behaviour: follow newest, "jump to newest", restored position client-side todo

Settings, layout, platform

# Feature Protocol Status
L1 Settings: server URL, workspace — todo
L2 Wide layout: left rail + two panes client-side todo
L3 Narrow layout: bottom section strip + bottom navigation client-side todo
L4 Responsive switch by viewport width (no hardcoded device) WindowSize.kt analogue todo
L5 Notifications for failed/waiting runs (browser Notification API; HTTPS/localhost only) derived todo
L6 Deep links to a run (pipelines://run/… analogue → URL route) — todo
L7 Accessibility: focus order, labels, keyboard operation — todo

Deliberately out of scope

  • Operator-only transport — inspect_resource, reconcile_resource, inspect_resource_pool, configure_resource_pool are loopback-only and must not be exposed by a browser client.
  • Device/ADB features — the Android app's device work is the UI reviewer's lease-based work, not a client feature.