A native foreground service keeps an authenticated websocket to the
connected server (handed over by the app on every connect), subscribes with
a replay cursor, shows each notification with kind-based channels and
grouping, opens pipelines:// links on tap, and clears taps, dismissals and
cross-device clears. It starts at boot and app launch, backs off and follows
network changes. Settings gains the delivery switch, status, notification
and battery-exemption actions, and the server's optional ntfy_enabled
toggle.
Settings leaves the tab bar (Pipelines, Runs, Chat, Search) and opens as a
page from a gear in the Pipelines bar, keeping /settings, its keys and a Back
to Pipelines (also the system Back). Every floating tab bar shows icons only,
named for assistive technology. On wide windows the shell's tab bar stays at
the bottom right; a split detail learns its height plus a 12px gap, so its
tabs or the chat composer float above it, and pages the detail opens (the
stage page) stay in its pane through its own navigator.
- SegmentedBar.titleWidget (and ShellBar/ShellBarSpec titleWidget,
backgroundColor): a bar's main pill can be an input in place of the title;
Search uses it so the field fills the bar with Kind and info, capped at the
result column width so field and results share edges on wide windows.
- Templates page/frame drop the top SafeArea again (BelowTopBar gate,
TopBarNotices banners); Cupertino uses the grouped background.
- Settings on Cupertino in the shell publishes the grouped background so the
bar scrim matches the page (no white band or seam).
- TopGlassStrip: the run detail header (status, actions, decision, notices)
and the Schedules search/filter toolbar float as glass under the bar; tabs
and lists scroll behind both.
- Stage page: stage title and Visit/Run subtitle in the bar, facts lead the
Summary scroll, sections scroll behind the bar under floating tabs.
- Tests for content-behind-bar on each page and the title-widget bar mode;
notes/chrome-gaps-fixes.md.
- Top-bar clearance helpers (withTopBarClearance, withBarClearance,
SliverTopBarClearance, BelowTopBar, TopBarNotices); shell, DetailPane and
the runs/pipelines/templates/artifacts/stage definition/filter/usage pages
drop their top SafeArea and pad their own lists, pinned headers pin at the
inset.
- Wide windows: the shell bar narrows to the list pane (ShellPaneSplit) and
the open item's bar shares its row; item tabs float at the pane's top
(PageTabsEdge) instead of stacking on the shell's tab bar; the floating
tab pill no longer swells over leftover media padding.
- Pipeline detail is a DetailPane on wide too; Run/Runs move from FABs into
the bar's actions; name and identity live in the title pill.
- Run detail title pill shows the real title with Run N, pipeline and
version (the pill links to the pipeline); the body keeps only status,
actions and notices; standalone detail draws the same segmented bar.
- One Runs tab badge: attention outranks running.
- Tests for content-behind-bar padding and the no-stacking wide layout;
notes/app-chrome-fixes.md.
- Search: field, compact Kind menu and syntax help in the bar's actions pill;
bounds shown only when truncated; rows with bold title, kind tag and one
muted line; results run behind the bar in a start-aligned 840 column.
- AppSearchField: one search field per platform (Search, Schedules, Runs filter).
- BarIconButton: whole 44pt/48dp bar actions; Runs, bell and Pipelines icons
use the same 44pt targets on Cupertino.
- Templates and Schedules pages put Refresh in the bar and use the shared
round SegmentedBackButton; Templates shows one Back at a time.
- PipelineBackButton is the round segmented Back.
- notes/pages-fixes.md records the batch, tests and evidence.
Extract the chat's segmented bar into lib/ui/adaptive (SegmentedBar,
GlassPill, SegmentedBarOverlay) and use it for the shell bar, DetailPane
and every page-level bar. Pieces are frosted glass over a fading scrim;
only pills take taps. Actions keep their natural width so the title gives
way before a model name. The chat transcript scrolls behind its header.
The app routes pipelines://chat/<id> to that chat, alongside the
existing pipelines://run/<id>, and Android registers the chat host so a
tapped ntfy notification opens the app on it.
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.
A /runs/:id?action=decide route now opens the landed decision prompt once the named detail loads, and only when that detail genuinely awaits a person. A non-waiting run consumes the request without inventing a prompt, and dismissing the prompt leaves the loaded detail. The route flag is forwarded through the existing destination seam; submission, refusal wording and the bounded re-read are shared with the detail's Decide button.
The route `/pipelines/:id[/:version]/stage/:key` now opens the pipeline
detail's Graph tab with the named stage selected and its authored
definition pane for the pinned version. A key the pinned definition does
not declare opens the Graph tab with nothing selected and no pane; no key
keeps the ordinary Summary tab.
The request is scoped to the pipeline and version the URL names, consumed
once the named pin's first reply is shown, and never replayed by a re-read,
a later version switch or a different pipeline. A route change from a pin
to latest re-reads latest, matching the web's requested-version rule.