Port the web markdown subset to a pure Dart parser and a native
Material/Cupertino block renderer, with a caller seam for assistant text
parts and safe http(s) link activation.
- parser: entities, paragraphs, H1-H6, fenced code, quotes, lists, tables,
rules, inline code/emphasis/links; entity overflow stays literal
- renderer: host text roles, inline/fenced code fills, table header fill,
heading level and list/columnHeader semantics, horizontal code/table
scrolling, native selection
- tests cover parser safety, both hosts, the seam and real taps
- probe plus note record the web evidence and remaining limits
Conflicts: app/lib/features/runs/ui/run_detail_actions.dart.
Keep main's recorded-artifacts action and the retry branch's spaced,
render-gated Wrap: Rename, Retry, Cancel, then Recorded artifacts.
Render Retry beside Rename on a stopped failed run under both native
hosts, send only {run_id, request_key} for resume and add
retry_mode=restart for a fresh start, and open the run the accepted
reply names. Keep hidden actions out of the Wrap so native 8/4 dp
spacing is not doubled, and use a literal 2^32 entropy bound because
dart2js evaluates 1 << 32 as 0.
Adds wiring, guard and layout tests, a browser-only key regression and
the retry probe; notes/R2c-wire.md records the checks and limits.
Main's Runs detail now requires the shared gateway, but three inherited
call sites (two Changes tests and the diff wiring probe) still constructed
it without one, and the Cupertino 2x detail test tapped Output before the
reveal scroll had been pumped. Pass the existing fake gateway at each call
site and settle after scrollUntilVisible. No production behaviour changes.
Validate the template source first, then submit the typed name create-only,
matching the browser's P5 flow and wording. Refusals keep the prompt and the
typed name; the accepted detail is reported once through the callback. The
labelled field, visible feedback and native Material/Cupertino controls are
covered by focused widget tests and a loopback browser probe.
Render one transcriptRows row with native controls: role-labelled user and
agent messages, verbatim user text, client and attachment names (own name,
URI basename, else file), ordered agent parts, and collapsed reasoning, tool
and unknown-part bodies using ExpansionTile or a Cupertino disclosure.
Blank known parts draw nothing so they no longer fall through to the
unknown-part disclosure; closed bodies build lazily. Adds focused widget
tests, the fixture probe pair and the C2 evidence note.
Register the landed PipelinesScreen at /pipelines through AppSession, with
an honest first-connection gate, a native reconnect banner that retains the
open list and detail, and an in-place refresh on reconnect. Move the shared
connection chrome out of RunsDestination so both destinations use one
implementation and one wording.
Add destination, registration and reconnect coverage plus an isolated
loopback Chrome probe that drives the real runPipelinesApp() composition.
Expose the existing RunTitleAction from the real run detail under both native hosts and fold the server's accepted run_detail into the open detail and the matching list row through RunsController, mirroring the web applyRunTitle path. Adds focused wiring/controller tests, a real-composition browser probe and an evidence note. Mobile remains unverified.
Read-only Pipelines screen for the Flutter client:
- list_pipelines and list_runs with a last-run join, plus get_pipeline
with an explicit version (0 = latest); no mutation requests.
- Name, run-presence, last-run-status and schedule filters; six sort
orders; clear filters; truthful loading, empty and error states.
- Detail Summary, selectable Source and version history with selection
and return to latest.
- Sequenced list/detail requests so stale replies cannot replace a newer
selection or open a cleared one; refresh keeps the selected pipeline
and version.
- Material controls on Android/desktop and Cupertino on iOS; a
per-label segmented tab row at narrow widths and scaled text, with the
native control kept wherever an equal share fits.
- Fixture probe entry and Chrome scripts for the rendered evidence;
widget tests cover filters, sorting, formatting, sequencing, layout
and the tab row.
Graph rendering remains P2: the Graph tab states that it is pending and
exposes a host hook. PipelinesScreen is not yet registered in the shell.
Evidence and limits: app/notes/P1.md.
The fixture had no darkTheme, so its Material "dark" captures were the
default light theme. Supply the stock dark theme and themeMode.system, rerun
the probe in both schemes, and correct the note's test counts, capture names
and branch state.