The conversation now reads chat_shells on mount and after a reconnect, and
the client serializes requests, so the deep-link and reconnect fixtures
must answer that snapshot before the history page can leave the queue.
Review 139 found the selected task's output page unbounded, overflowing a
phone-height conversation. The bar now keeps half the viewport and scrolls
its own body, the output pane is capped at twelve scaled lines, row labels
elide instead of overflowing, and a reply without a page reads as
unavailable rather than empty.
The run detail now offers the web's "Schedule this run" action when the
run names a positive pipeline and pinned version. It opens the existing
create editor seeded from the run and sends nothing until Save.
The seed preserves every field the browser's scheduleDraft({ run })
copies: title (following the title_source rule), all input keys with
prompt kept editable, pinned version, workspace, notify mode, write
paths, tool access, model, stage models and output format. build() emits
the same conditional payload as serializeSchedule.
One request key is minted per editor opening so a refused save retries
without duplicating the schedule. Advanced options are seed-only for
now: the editor has no controls for them yet.
Mark the run's recorded current stage on the run graph while it executes. The
halo is a foreground painter outside the node box, so it adds no size, hit
target or semantics, and it is derived only from RunGraphState.activeStage,
which is non-null only while the run reports executing. Reduced motion keeps a
still ring instead of animating.
Widget tests cover the sole active node, a finished run with no halo or ticker,
reduced motion, toggling it at runtime and unchanged node extents.
Transcripts pin to the newest end while following, release on the operator's upward scroll, and offer a native Jump to latest control carrying the count of messages that arrived meanwhile. The chat destination keeps each conversation's saved position so reopening restores it.
The conversation reads the session's recorded chat_shells snapshot and folds
pushed shell frames, so only tasks the server still reports as running appear.
The list is capped at three visible rows and scrolls beyond, and a task that
exits leaves it.
Selecting a task opens its recorded command, identity and running status plus
one bounded chat_shell_output page (cursor 0, 64 KiB). Empty, unavailable and
refused reads are reported with native Retry/Refresh controls, and a refused
snapshot is shown with its reason instead of claiming there are no tasks.
Both reads carry the session id, linking every task to its conversation.
A retired or unknown field hit now selects the plain Summary instead of
leaving an open visit pane in place, matching the browser's searchFieldTab
and Android. The resolved target is a sealed Summary/visit value, so the
field mapping lives in one place.
An unapplied request is dropped when the shell leaves the run it names, so
Backing out of a loading detail no longer replays the selection on a later,
unrelated visit. Search/Templates/Schedules pages above the run keep it.
The run-wide header, note, filter and matched-path counter still describe
every visit; below them Previous/Next move through the recorded visits in
run order without wrapping, and the shown visit keeps its own stage and
Visit N heading. A single recorded visit renders no pager.
A leading slash opens the recorded command palette above the composer,
filtered by name prefix and driven by Up/Down, Enter, tap and Escape.
Slash drafts never reach the prompt path: a recorded command reports
locally that its action is not implemented yet, and an unknown word takes
the web client's no-send report with an explicit Send as message offer.
Enter and the primary control share that route.
Adds the chat commands domain vocabulary, the palette widget, composer
wiring and regression tests; notes/C9-commands.md records behaviour and
the remaining command-action gap.
Follow the web chat layout on both hosts without changing request shapes or
bubble/composer behaviour.
- Session rows (Material and Cupertino): title with trailing relative
recency, muted `directory · model` line with the `New`/`Closed` word at
the trailing edge. Shared row content keeps one arrangement; native tiles
keep their own padding, separators and subtitle size. The state word keeps
its intrinsic width and the metadata ellipsises first, so it is never
clipped at 320px/2x.
- Thread header: one row of compact icon-only Back, ellipsised title,
bounded model control and Chat information. Back keeps the destination as
its accessible name and both hosts share `Key('chat-back')`.
- Share the epoch-millis parser as `chatSessionMillis`, and match the web's
relative-time words, including `Sept`.
- Cover the row content, status word at narrow widths, header layout and
Back accessibility in widget tests; update existing tests for the
separate trailing status word.
Group each Settings section under one compact title, tighten the page to the
web's 8/16 spacing and 20/16/32 page insets, and make field labels secondary so
only the section title carries emphasis. Drop the duplicate Notifications
heading now that the permission tile draws its own title.
Adds a rendered-geometry regression for the centred 720px column, the title and
section gaps, the secondary label role on both platforms, and the single
Notifications heading.
Put the page summary and the recorded capture notes on one scrolling
header, style Material section headings as muted titleSmall, and draw a
hairline between Material rows only. Share the selection-facts hierarchy
between the sheet and the viewer and order the sheet actions Close,
Copy link, Open on both hosts.
The header now rides inside the artifact list's scroll view, so many
partial visits or a large text scale scroll with the rows instead of
overflowing the page and collapsing the list.
Tests cover per-host headings, dividers, notes, sheet order, and the
constrained 2x large-text layouts.