ui(alerts): clarify Acknowledge vs Resolve #9

Merged
steve merged 2 commits from alerts-ack-resolve-clarity into main 2026-05-04 23:25:35 +01:00

2 Commits

Author SHA1 Message Date
steve fc58e57598 ui(alerts): drop 'Severity / kind' header — column shows kind only
CI / Lint (pull_request) Successful in 37s
CI / Build (windows/amd64) (pull_request) Successful in 47s
CI / Build (linux/amd64) (pull_request) Successful in 23s
CI / Test (linux/amd64) (pull_request) Successful in 1m27s
CI / Build (linux/arm64) (pull_request) Successful in 46s
The text in that column is the kind chip (backup_failed, etc).
Severity is encoded entirely in colour: severity dot, left-border
accent, and the chip's tint. The header promised both but only one
made it into text, which read as if the severity word should
appear too.

Header now reads 'Kind'. Colour does the severity work, as it
already did.
2026-05-04 23:22:44 +01:00
steve c446ca072e ui(alerts): make Acknowledge vs Resolve distinction visible
CI / Build (windows/amd64) (pull_request) Successful in 22s
CI / Lint (pull_request) Successful in 37s
CI / Build (linux/amd64) (pull_request) Successful in 22s
CI / Build (linux/arm64) (pull_request) Successful in 23s
CI / Test (linux/amd64) (pull_request) Successful in 3m55s
Both buttons make the row leave the Open tab, so on a quiet system
they look identical. The behavioural difference only manifests next
time the underlying condition fires:

  - Acknowledge silences fan-out while the problem persists; the
    alert parks on the Acknowledged tab and recurrences just touch
    last_seen_at without re-notifying.
  - Resolve closes the alert. If the same condition fires again
    later, a fresh alert with a new id raises and the channels
    fan out as if it were the first time.

Add a one-line legend under the page header explaining both, and
title= tooltips on each button covering the same ground for keyboard
and assistive tech.
2026-05-04 23:11:46 +01:00