Integrates eight commits of reviewed chat work: the Chat destination with
several conversations, markdown transcripts, tool-call chips with an expandable
INPUT/OUTPUT panel, edit diff cards, the composer's stop control, and approval
cards. The automated resolver failed on this merge repeatedly (its own stages kept
dying on the malformed-result defect), so it was integrated by hand.
Integration decisions:
- Pill geometry: main's tokens win. lane-app2 carried private duplicates of
DESTINATION_ITEM_SIZE/GAP and a private DESTINATION_PILL_RESERVE, added before the
geometry-token migration; those duplicates are dropped in favour of the theme
tokens main already exports.
- IME mode: kept lane-app2's adjustResize for the window, because the chat composer
and the search field both raise the keyboard and the chat UI was reviewed with it.
- Protocol and view-model constants: both sides' independent additions are kept.
- ChatScreen now passes the compactLabel main's SlidingPaneStack gained, and the
literals lane-app2 introduced before the token discipline are converted to five
new named tokens (HAIRLINE_DP, ICON_BUTTON_SMALL_DP, TOOL_PANEL_MAX_WIDTH_DP,
CHAT_TITLE_MAX_WIDTH_DP, CHAT_BUBBLE_MAX_WIDTH_DP) rather than allow-listed.
Verified: assembleDebug plus the full Android unit suite (409 tests) pass,
including the geometry enforcement test.
Add the fourth Search destination to the floating bottom container and
morph that container into the omni-search field.
- PipelinesApp: the destination pill gains a Search icon; tapping it
animates the icons out and turns the same Surface into a focused text
field whose size and position derive from the pill's own layout and the
window insets rather than fixed pill sizes. Back, the back gesture and a
scrim tap play the reverse and restore the pill with its previous
destination still selected. The open field covers the content behind a
scrim and shows a results panel above it.
- OmniSearch: pure state model (open/focused/query) with the open, dismiss,
focus and query transitions and a Bundle-able Saver, so an open field
survives a saved-state round trip.
- OmniSearchResults / SearchResultsPanel: map the typed search reply to
rows and render the ranked results, keeping the last accepted results
while a newer query loads and reporting a failure without blanking.
- AppViewModel / PipelinesRepository: drive queries over the existing
transport with debounce and reply ordering; the server search command
arrives in a later item, so a reply is classified by envelope type and a
non-search_results reply is reported with a clear message instead of
being mis-parsed, never a crash.
- Message: SEARCH / SEARCH_RESULTS constants and the SearchRequest,
SearchResponse and per-kind result payloads.
- AndroidManifest: adjustNothing so the app reads the IME from Compose
window insets and the field is not cleared twice by a window resize.
- Dimens: spacing for the search surface.
- Unit tests for the state model (pill, opening, focused, dismissed and
restored after the Saver round trip) and for the result-row mapping.
Entry point: the floating destination pill gains a Chat icon between Runs and
Settings; it stays a single non-wrapping Row of 48dp targets using the named
DESTINATION_ITEM_SIZE/DESTINATION_ITEM_GAP tokens, clear of the existing 88dp
reserve, so it stays narrow however many destinations it holds.
Protocol/transport: new data/protocol/Chat.kt mirrors the brokered chat wire
shapes; Message gains the optional chat_* payloads, PipelinesClient forwards
unsolicited frames (chat_event/chat_permission) to a new events flow instead of
dropping them, and PipelinesRepository exposes the typed chat calls (sessions,
create, messages, prompt, interrupt, reply).
State: ui/chat/ChatStore.kt is an Android-free multi-chat holder; every open
chat keeps its own conversation, running flag, composer draft and scroll
position, open/activate report when history must be re-synced so a running
session refreshes on return instead of showing a stale copy, and busy/read-only
sessions refuse writes.
Surface: ui/chat/ChatScreen.kt lists the server's sessions with running/busy/
read-only status and an open-chat strip to switch between conversations (chip X
closes only that chat); the conversation is a bottom-anchored transcript of user
bubbles, reasoning, assistant text and tool-call chips that expand to INPUT
(pretty JSON)/OUTPUT (monospace), edit-family calls render a diff card derived
from oldString/newString, and pending chat_permission frames surface an approval
bar answered via chat_reply. New chat creates and opens a session. The manifest
sets windowSoftInputMode=adjustResize for the composer.
Tests: ChatProtocolTest, ChatFormatTest and MultiChatStateTest cover the wire
shapes, formatting and the multi-chat model (switching preserves each
conversation, a running session re-syncs on return, per-chat drafts/scroll,
busy read-only, background events land on their chat). README documents the
slice and its evidence.
Give each gallery image cell and each per-visit file row its own share
control: a 48dp IconButton with an accurate "Share <name>" content
description drawn as a sibling of the item's tap handler, so sharing
never opens the image or the item.
Sharing fetches the artifact through the existing client into a scoped
cache file (cache/shared-artifacts/), exposed via a non-exported
FileProvider declared with the new res/xml/file_paths.xml, and sends it
through ACTION_SEND. When the fetch returns nothing the action falls
back to sharing the resolved link as text. Cache files are named
deterministically per artifact so re-sharing overwrites instead of
growing without bound, and a failed or unreachable fetch cannot crash.
The artifact-to-file naming, mime/extension table and the file-vs-link
fallback decision are factored into ArtifactSharing.kt and covered by
the new ArtifactSharingTest.kt. The existing open and copy-link actions
are unchanged; the viewer's action scrim alpha is shared as
ARTIFACT_ACTION_SCRIM_ALPHA. android/README.md documents the provider
and the share flow. No new dependency is added.
Turn the stage detail into the rightmost pane of a bounded three-level
stack and show every run artifact in a summary gallery.
- The stage detail opens as a real level-2 pane from both entry points (a
Timeline row and a graph node). StageDetailPane is wrapped in the same
Scaffold/TopAppBar with a back arrow as the other panes, and its
identity/result facts (status, outcome, target, duration, visit, model
target) render outside any collapsible so a fresh pane is never empty.
StageDetailSheet, ModalBottomSheet and RightSlidingPanel are removed.
- SlidingPaneStack replaces SlidingMasterDetail: pane 0 fills the host,
panes 1 and 2 overlay at peek*level, each covered pane keeps one
tappable peek strip, and MasterPane/backStep/popTo/MAX_PANE_DEPTH are
the pure model. The peek tap, the pane back arrow, the system Back
button and the predictive-back gesture all pop exactly one level.
- New pure runArtifactGroups(steps) groups a run's artifacts by stage and
visit (stable order, duplicates kept, empty run -> empty) and
artifactsEmptyMessage distinguishes the running "capture pending" case.
ArtifactGallery renders image thumbnails (tap opens full size) and
non-image rows with name, size, content type and open/copy; urls resolve
through ServerUrl, never a hardcoded host.
- Run Summary shows the run gallery and the stage pane shows that visit's
group, keeping the existing per-visit artifacts summary and notes.
- Tests updated/added (PaneStateTest, SlidingPaneStackTest,
ArtifactGroupsTest, ArtifactGalleryTest, StageDetailSheetTest, refreshed
DetailTabsTest/PipelinesNavTest, CollapseRemovalTest kept green) and
android/README.md records the pass, evidence and not-verified list.
Kotlin and Jetpack Compose Material 3 client that speaks the existing WebSocket
protocol: settings requiring an explicit server URL and workspace, pipeline list and
detail with the workflow graph, run history, run detail and evidence, start and
cancel run, reconnect, and the loading/empty/error/disconnected states. It stores no
credentials and keeps execution, definitions and run history on the server.
Verified on the host: :app:compileDebugKotlin and :app:assembleDebug succeed and
:app:testDebugUnitTest passes 19 tests. Ignore Gradle outputs and re-include the
net.awan.pipelines.data package, which the repository runtime data/ rule would
otherwise exclude.