Commit Graph

10 Commits

Author SHA1 Message Date
alan cc094fc06d feat(web): copy original run prompt 2026-10-21 12:19:26 +01:00
alan d130615fae web: put the work first and the audit evidence behind a door
- Turn files (input/memory/output/session) are system artifacts now: they are
  never tiles in the run or stage galleries. Shared public files are attributed
  to the visit that first recorded them, so a run counts 3 stage artifacts, not
  one copy of each per later stage.
- Audit & debug opens a dialog with vertical Input / Output / Memory / Session /
  Definition tabs, for a visit from the stage pane or the run Summary.
- Run tabs are Summary / Graph / Timeline; Input and Output are Summary sections
  with Artifacts, Files changed and Audit. Each stage pane gains Files changed.
- Artifacts gain a gallery/list switch (remembered) and full-name wrapping; the
  copy/share actions are hover-or-focus icon buttons.
- Status badge above the run title; no live badges on the run surfaces. The runs
  list leads with the pipeline name and the stored task title beneath it.
- Chat rows: title + coloured status word only, then directory, then model; no
  operator or closed chips, no dot. The more/star cluster is a hover/focus
  overlay so the title uses the row's width, and an open menu stacks above rows.
  Closed chats collapse behind a chevron. Sessions can be starred locally and
  sort in a Starred group. The chat header no longer repeats status/dir/model.
- A visible rail divider separates Search from the destinations; the page has a
  real favicon/apple-touch icon and the rail brand wears it.
- Smoke updated: no live badges, 3 detail tabs, field hits open Summary sections,
  closed chats expand for checks, the fixture viewer uses shot.png/missing.txt
  and the audit for markdown.
2026-10-20 01:00:01 +01:00
alan 793b62f53e web: render a turn's input and output as their markdown bodies
The stage pane stringified the step's single-key {markdown} map, so a turn's
output appeared under a literal "markdown:" line inside a code card. The pane now
shows that body as the document it is, with "(no output)" for an empty turn; an
ordinary value map still shows its keys.
2026-10-19 23:32:51 +01:00
alan 5682aadfaa web: open searched documents in the viewer and name the run's pipeline
A markdown/text artifact hit now opens the artifact viewer (with its Open run
action) instead of a raw browser tab, and the run Summary's Pipeline row shows
the pipeline's name beside its id and version, all in the link to the definition.
2026-10-19 23:10:13 +01:00
alan 64e40f0b88 web: link artifacts and runs back to their sources
- The run Summary's Pipeline value is a button that opens that pipeline version.
- The artifact viewer carries an Open run button (the search viewer passes the
  artifact's run id), so the evidence always leads back to the run.
- Search artifact rows show the image itself as a thumbnail; other artifacts get
  a type tile (MD/TXT/JSON/CSV/GO/PDF/...), and every artifact row offers an
  Open run action next to its own navigation.
2026-10-19 23:07:04 +01:00
alan 6c0c813c2c web: render markdown stage bodies as prose
The turn protocol writes a markdown body; the run detail now renders a field as
markdown when it has markdown structure (heading, fence, list, table) and keeps
the honest monospace block for historical plain-text fields. Pure helper with
tests.
2026-10-19 21:41:41 +01:00
alan ff70b3796f web: run-detail polish — bigger graph, artifact counts, tighter stage pane
- the run Graph tab drops the guidance paragraph and the graph fills ~70vh;
- the Artifacts collapsible carries the visit's count in its title (the body keeps
  the reason line only when there is nothing to show);
- the stage panel's section padding and gaps are reduced.
2026-10-19 20:05:47 +01:00
alan b011f4ada4 web: show per-visit changes and last-visit summary
Each visit's This run pane reports its own recorded capture: the File
changes status line (with skipped/omitted counts and diagnostic) and its
Changed files list with parseable stats. The Summary aggregate now keeps
each path's last recorded step rather than summing visits, and is only
rendered for a succeeded run; a failed run keeps its evidence in the
visit panes. This is a deliberate divergence from Android, noted in R4.
2026-10-19 18:27:39 +01:00
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
alan 06965933f4 web: tabbed run detail with summary, IO fields and timeline (R3/R6/R7)
The browser run detail becomes a tab strip — Summary, Input, Output,
Timeline — over the selected tab's body, with the Graph tab key reserved
for the R5 item.

- Summary: run label, status chip + outcome, the run identity line, the
  key/value rows (Pipeline, Stage, waiting-for-resource line, Workspace,
  content hash, Started, Finished, live Duration, Retry of, Diagnostic)
  and the collapsed run artifacts gallery.
- Input / Output: one collapsed section per recorded map entry, the value
  as a monospace block; empty states match the app.
- Timeline: one row per visit with the stage-outcome glyph, `{stage} ·
  visit {n}`, an outcome chip, a paperclip when artifacts were recorded,
  the duration and the description; a row opens the per-visit stage pane.
- Stage pane: headline rows, the Verdict block with inline artifact links
  and the Artifacts / Session / Output / Input / This run / Stage
  definition sections, all closable with Escape.

All new logic is the pure, DOM-free src/runDetail.js ported from the
Android sources; app.js keeps only the wiring and every server string is
set with textContent.

PARITY.md: R3, R6 and R7 marked done with their captures.
2026-10-19 03:32:32 +01:00