- 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.
Settings drew a sun because the sprite was a circle with rays; it is a cog now.
Search is a modal, so it leads the rail (and the narrow dock) instead of sitting
under the destinations, which leaves Settings last. The section strip reads as a
tab bar: flush cells on a bar, the selected tab filled with the panel surface and
underlined, no chip borders.
The successful retry in TestDefaultRetriesAndTimeoutResetEachAttempt was
racing its own 20ms deadline when the full suite ran in parallel. Keep the
two-attempt behavior and give the retry realistic headroom.
Each model visit now gets <run>/stages/<seq>-<stage>/ with input.md,
memory.md, output.md, private/ and a shared run-level public/. The model
reads the two input files, follows the stage's instructions verbatim and
returns complete markdown; only the # outcome section is parsed.
- add internal/turn layout, render and output parsing
- write input.md/memory.md before a visit and output.md from the final
message; inventory all turn files as stage artifacts
- accumulate completed turns and system-written public file additions in
memory, including across retries and resume
- remove the JSON envelope, strict field validation, line format and the
repair ladder for model stages
- republish pipeline authoring prompts and docs in the new style
Checks: go build ./..., go vet ./..., go test -count=1 ./..., gofmt -l .
Drop the resource allocation feature end to end: store tables and migration, runner scheduling and cleanup, protocol types and commands, CLI commands, TUI screens, tests and docs. Existing databases open cleanly and definitions carrying a retired resources block still validate.
- Gaps between stages are sized from the widest straight-route label, so a chip
never reaches into either box; a source's forward routes fan across its side
instead of sharing a 20px band.
- A label prefers the widest horizontal run that can hold it; when only a stub
exists the chip moves onto the edge's longest run and sits beside a vertical
one, keeping clear of both the box and the neighbouring label.
- Hovering a wire or its chip highlights the route and dims the rest.
- System-added routes (the parser's implicit error fallback) draw dotted with a
legend entry, distinct from declared routes and executed state.
- Lanes are 34px apart, so a dense definition no longer doubles the canvas height.
- The graph opens expanded by default and remembers a collapse (graphPrefs.js).
The section list lived in the destination rail, next to Pipelines/Runs/Chat, which
read as navigation rather than as the current detail's view. On a wide screen the
sections are now a tab row at the top of the detail pane and the rail keeps only
destinations; narrow keeps the thumb-zone strip at the bottom.
Every stage declares error/blocked/retry outcomes, so a run graph labelled all of
them and the chips buried the nodes. In run mode only routes that actually
happened are labelled; a pipeline definition (no run state) still labels every
route.
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.
Palette: bg #0a0a0b, surfaces #121214/#17171a, elevated #1d1d21, neutral borders,
text #e8e8ea, muted #9a9aa2, restrained cool accent (#8fa8c8) — the green cast is
gone; the run-status palette is unchanged. Contrast is AA or better (text 16.2:1,
muted 7.1:1, border 4.3:1). Padding tightened across lists, headers, settings,
tabs, chat, stage panels and artifact tiles on the 8px grid; radii 10/8.
The suite's run-history sections assumed older failures/day groups that the
operator has since wiped; those checks now skip honestly when the fixture history
is not there.
The full-screen viewer now opens markdown/text artifacts (text/markdown,
text/plain, .md/.markdown/.txt) through the resolved artifact URL and renders
them with the page's own DOM markdown renderer, with an honest failure message
and an external fallback. ArrowLeft/ArrowRight page the shared media+document
list, and a backdrop click closes the viewer while panel clicks do not.
The run gallery and per-visit artifacts present input.md, memory.md and
output.md as ordinary Document tiles with a drawn glyph and open the viewer.
Adds isMarkdownArtifact/isViewerArtifact with unit coverage, deterministic
viewer fixtures, and ui-smoke assertions/captures for rendered markdown,
keyboard paging, the honest 404 and backdrop dismissal.
- the attention sheet is managed imperatively, so closing it now tells the
controller; without that it stayed on the stack and left the app root inert,
which silently swallowed every real click (found by the suite: the Settings
Templates card stopped working after the sheet had been used);
- the sheet returns focus to the bell after the repaint that replaces it;
- opening a chat row's menu at the bottom edge now scrolls the row into view, not
just flips the panel, so the items are actually reachable.
- Sticky sections: a run/pipeline/template keeps the section you chose when you
open another one, and the choice persists across reloads (localStorage per
destination). A stage deep link still opens the Graph.
- Search is a Spotlight: a modal overlay opened with Ctrl+/ (Cmd+/ too), arrow keys
move the selected result, Enter opens it, the query/kind/sort/selection resume on
the next open, and an artifact result opens the artifact itself (media in the
viewer, anything else in a tab) instead of the run's visit pane.
- Live sync: the server only emits a user frame for prompts sent through it, so a
message typed in the OpenCode UI appeared only after a refresh. When a frame for
an unknown turn arrives, the open conversation now reads the newest history once,
which brings the user message in live.
The layout smoke still asserted the guidance paragraph the operator asked to
remove; assert its absence and a graph viewport of at least half the window, and
keep the pipeline graph's own note check.
The a11y work made the chat row a container with its control inside, so Back
focused a non-focusable div and keyboard focus fell to the body. Focus the first
focusable descendant instead (generic for chat, runs, pipelines and templates).
Take main's newer smoke behaviour where they met: the binary capture is run 449
(opened through openRunDetail), and a running run must show no aggregate Changes
section. Keep the layout's shell-aware checks and its L2-L4 rows; L7 stays todo
with the view-level fixes recorded.
- 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.
The layout item's work plus the two defects its review found:
- the wide grid sized the list track from its MAX, so at 600-759px the detail pane
was clipped to 40-199px; cap the list below 900px and narrow the rail there
(measured now: detail 232px at 600, 332 at 700, 340 at 900, 880 at 1440);
- the shell said 'Not connected' on a fresh page because the prefilled proxy URL
validated; the status now reflects a SAVED endpoint ('Not configured' until then)
and refreshes as the draft changes.
Includes the rail + bottom dock, connection moved into Settings, viewport-only
scrolling with panes that scroll themselves, tab semantics, skip link, h1 per
route, and the design tokens.
The merged main branch names the attention dismiss and chat actions
controls for their rows. Assert those prefixes instead of the old bare
words so the live smoke exercises the current labels.
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.
The page resolves artifact URLs against the configured server. In a proxied
deployment that is the page's own origin, and serve.mjs only proxied /connect, so
every artifact request 404'd: broken gallery thumbnails, a blank viewer and no
session.html. Forward GET/HEAD /artifacts/ to the same upstream and stream the
reply (status, headers, body). Verified: 10/10 thumbnails load on run 430 and the
viewer's image has naturalWidth > 0.
The previous section can leave the operator's thread marked running from a
replayed frame; C8 tests the composer's default state, so it settles once through
the page's own fold instead of asserting against leftover state. Found by the
post-split gate (the split itself was correct: a fresh open shows Send, no Stop).
Role-named tokens (colour, 8px spacing, radii, type scale, elevation, focus,
state tints, motion) with a styleguide built from the app's real components and a
short application guide, including what to remove from the current CSS.
Pure move, behaviour unchanged: app.js is now the shell (boot, state, client wiring, connection/banner, navigation and routes, render dispatch, header). Views live under src/views with shared DOM and format helpers. client.js stays DOM-free; no circular imports; every server-derived string still uses textContent.
Pure move, behaviour unchanged: every rule is carried verbatim into one of base, lists, run-detail, chat, graph, dialogs or settings, linked in a fixed order from index.html. No @import and no build step.
The layout prototype shows the operator's target shell: a left destination rail
(Pipelines/Runs/Chat/Settings) with the detail sections grouped in the rail, list
and detail panes, a status dot in the rail footer and no top connection chrome.
The spec's DOM sketch still mentions the old connection banner; the implementation
brief supersedes that (connection lives in Settings only).
The audit records 9 must-fix, 12 should-fix and 15 notes from real DOM and
accessibility-tree inspection, with file:line for each finding.
Add an opt-in --decide smoke mode that reuses or submits a human-only pipeline, starts two runs in throwaway workspaces, and presses the real card, sheet and Confirm for the feedback and no-feedback shapes. Record R11 as done with the live captures.
The created chat loads its history asynchronously; reading the DOM once raced the
load (worse when the OpenCode endpoint is busy), reporting a permanent 'Loading
conversation...' that the app never showed.
--compare BEFORE AFTER fails when a capture is missing or unexpected and lists
pixel drift for manual review; live durations make byte equality the wrong gate.
Describes what the client is, how to run and test it (OS-assigned smoke port,
gitignored captures), the module areas, and keeps the 403/proxy explanation that
justifies serving the page from serve.mjs.
Integration fixes found by the full suite:
- drop the dead 1 Hz run poll helpers still referencing R10-removed state (they
threw on every route apply, so the first connection never rendered a list);
- keep this tab's ephemeral verification chats across a reload (sessionStorage),
so a chat the server intentionally hides stays usable in the tab that made it;
- the smoke marks only the throwaway ephemeral, clears the marker after /new, and
tolerates a stale page banner plus a re-rendered row menu;
- the nav no longer claims a false Pipelines (0) before that list has loaded, and
the Runs destination preloads it once per connection.
Full suite: 580 unit tests green, UI SMOKE PASS.