Agent run status chips follow your theme
The status chips on agent runs used fixed light colours. Running, Paused, Succeeded, Failed and Stopped, along with the delivery and review chips beside them, were written with the same kind of hardcoded pale palette that made the Stop button's border look wrong in dark themes. In a dark theme their borders read as bright outlines and their fills as light blocks, none of which belonged to the surrounding surface. They now use the same theme-defined colours as the rest of the app, so every chip is legible and in keeping whichever theme you run.
The three places that show these chips, the Activity runs tab, the Agent runs panel, and the run history on a task, each carried their own copy of the colour list. Those copies had already started to diverge: two used one text shade and the third another, so the same run could look subtly different depending on where you saw it. There is now one definition, which means a chip cannot drift between surfaces again and a future state or a re-themed colour lands everywhere at once. The Retry chip in run history and the Pause and Resume buttons sitting either side of Stop got the same treatment, so a run card no longer mixes themed and unthemed controls.
Meaning is preserved throughout. A stopped run stays visually distinct from a failed one, because cancelling a run is not the same as it crashing, and a delivered result still reads differently from one that needs attention. New checks assert that no run chip can reintroduce a fixed palette, that every chip defines its border, fill and text rather than inheriting one from the surface behind it, and that the three surfaces continue to agree.
Highlights
- Agent run status, delivery, and review chips use theme colours instead of fixed light ones.
- No chip shows a near-white border in dark themes any more.
- The Activity tab, Agent runs panel, and task run history now share one colour definition and can no longer drift apart.
- The Retry chip and the Pause and Resume buttons beside Stop are themed to match.
- A stopped run stays visually distinct from a failed one.
- Tests prevent a fixed palette returning and require every chip to define its own border, fill, and text.