Files
pipelines/web/PARITY.md
T
alan 9d1745da1d web: run Summary Changes section with rendered/raw diff viewer (R4)
Add a collapsed-by-default Changes section to the run Summary tab and a
full-screen diff viewer, ported from the Android RunChanges/ChangeDiffViewer
wording. Pure aggregation and unified-patch parsing live in src/changes.js;
app.js wires the section/viewer and sets every server string with textContent.
Unit tests cover the header variants, kind merge, stat sums and hunk parsing;
ui-smoke captures the collapsed/expanded section, rendered and raw viewer,
paging, Escape/backdrop close, binary, truncated and a running run's header.
2026-10-19 04:06:44 +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); definition view only, so R5's run-detail Graph tab stays todo. 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 / 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 done — a collapsed-by-default Changes section in the Summary tab ({N} file(s) changed · ±stat · partial capture; the empty variants read Changes · capture unavailable / capture pending / partial capture / not recorded for this run / capture incomplete / no changes observed) whose rows open a full-screen diff viewer with Rendered (each @@ hunk header on a raised surface, old/new gutter numbers, the shared +/-/space line language) and Raw patch forms, Previous/Next file paging (disabled at the ends), a raw-patch copy control, Escape/backdrop/Close close, and honest binary/truncated/no-patch messages instead of a fabricated diff. Pure logic in src/changes.js. Captured 2026-10-19: captures/28-run-438-changes-collapsed.png, captures/29-run-438-changes-expanded.png, captures/30-run-438-changes-diff-rendered.png, captures/31-run-438-changes-diff-raw.png, captures/32-run-442-changes-binary.png, captures/33-run-450-changes-truncated.png, captures/34-run-455-changes-pending.png
R5 Graph tab (per-stage panes, verdicts) get_run todo
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 (Graph tab) deliberately leaves the tab's body unimplemented.

One wording decision from R4, recorded here as the app-authoritative choice: the Changes disclosure's title is runChangesHeader, so a run that recorded files reads {N} file(s) changed · ±stat · … with no Changes · prefix — only the empty-capture variants carry the Changes · prefix — while the expanded body's own summary line repeats the count and stat. The header is rendered verbatim, not re-composed.

# 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.