ui(alerts): make Acknowledge vs Resolve distinction visible

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:04:10 +01:00
parent 84814b1386
commit c446ca072e
2 changed files with 13 additions and 3 deletions
@@ -28,6 +28,13 @@
    </div>
  </div>

+  {{/* triage legend — Acknowledge vs Resolve looks identical on screen
+       (both leave the Open tab) so the difference needs spelling out. */}}
+  <div class="text-ink-mute mt-2 leading-[1.55]" style="font-size: 11.5px; max-width: 760px;">
+    <span class="text-ink-mid">Acknowledge</span> silences fan-out while the underlying problem is still happening — the alert moves to the Acknowledged tab.
+    <span class="text-ink-mid">Resolve</span> closes the alert; the next failure raises a fresh one with a new notification.
+  </div>
+
  {{/* filter strip */}}
  <div class="panel mt-4 px-4 py-3 rounded-[7px]"
       style="display: grid; grid-template-columns: auto auto auto 1fr; gap: 14px; align-items: center;">