- 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.
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.
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.
One content-sized stage node as an ordinary native control. Material uses
stock Card.outlined/Card.filled inside an InkWell; Cupertino uses
CupertinoButton.tinted/filled. onSelected reports the definition key
verbatim, one merged button semantics node carries the exact label and
selected state, recorded status is shown only when the caller supplies it,
and invisible U+200B break opportunities reproduce the web's anywhere
wrapping. Painted-boundary and painted-surface tests cover the UI-review
2x outline and Cupertino container defects.