Show running and failed run counts independently

Give the Runs tab separate activity and failure indicators so neither suppresses the other. Reuse known summaries and pushed updates, keep failed states separate from decisions and dismissal counts, and update across tabs even when total attention is unchanged.
This commit is contained in:
2026-11-11 22:10:37 +00:00
parent 9551eceaed
commit efca56e4e4
13 changed files with 415 additions and 99 deletions
+22
View File
@@ -0,0 +1,22 @@
# Independent Runs tab indicators
The Runs tab now shows the executing count at the lower edge in the primary
theme colour and the failed count at the upper edge in the error colour.
Neither suppresses the other. Zero hides its indicator; the failed label caps
at 99+ while the tooltip and accessible label retain the actual count.
Counts use known, unfiltered server summaries and update from existing pushed
frames without extra polling. Failed status is independent of notification
dismissals and the daily attention window. Terminal statuses override a stale
execution flag. Older summaries without that flag can still name running work.
Waiting decisions remain announced by the attention label and available in the
Needs you bell; they are not mislabelled as failed runs.
The app-level observer now republishes status changes even when total
attention is unchanged (for example a waiting run becoming failed). Standalone
Runs lists also publish both counts through the existing shell registry.
Focused validation: 24 tests passed, covering both colours/positions in light
and dark at narrow/wide widths, zero states, live updates from another tab,
unchanged-attention transitions, and terminal/older status summaries. Analysis
was clean. Full-suite and rendered checks follow this focused pass.