toga-ai 1.0.587 → 1.0.588

package/knowledge/1.0/apps/tools/features/oneuptime-monitor-status-panel.md

@@ -123,7 +123,8 @@ poll's:
 - The **first successful poll is the baseline**, so opening the page mid-outage is **silent**
   (the standing tint, being level-triggered, still shows immediately).
 - A state that simply persists never re-alarms.
-- A full recovery to operational is **silent** (the monitor drops out of the row set entirely).
+- A full recovery to operational is **visually silent** (no popup, no tint) but now plays a
+  distinct **recovery chime** — see the recovery event below.
 - It fires on **any change of non-operational state** — `r.role !== previous.get(r.key)`, where
   the row set only ever holds non-operational monitors, so good→degraded, good→offline,
   degraded→offline **and offline→degraded** all alert. An earlier version compared severity
@@ -134,11 +135,30 @@ poll's:
 The event presentation, held for `ALERT_HOLD_MS` (5s):
 
 - **Sound** — Web Audio beeps, synthesised at runtime, so there is **no audio asset to ship**.
-  **1 beep @ 720 Hz** degraded, **2 beeps @ 990 Hz** offline. The beep count describes the state
-  the monitor is in **now**, so an offline → degraded change beeps **once**. Pitch differs too,
-  so severity is recognisable across a room without counting.
-- **Popup** — a centre overlay naming each affected monitor.
+  Each role's sound is defined in a single `ALERT_SOUND` table keyed by role, read by a
+  generalised `playBeeps(role)` (signature unchanged: role → bool). Each entry carries a beep
+  **count**, base **freq** (Hz), a per-beep **step** (Hz added to each successive beep — `0` =
+  flat, positive = a rising chime), duration/gap/volume, and a **wave** shape. Current tuned
+  values: **warning (degraded) = 3× square @ 720 Hz** (flat), **critical (offline) = 4× square
+  @ 410 Hz** (flat), **recovered = 3× square rising chime 620 → 800 → 980 Hz** (freq 620,
+  step 180). Distinct count, pitch and the rising vs. flat contour make each event
+  recognisable across a room without looking. The three sounds were tuned by ear in a
+  throwaway standalone "Monitor Sound Lab" browser page and the final numbers ported in — the
+  lab is not part of the repo.
+- **Popup** — a centre overlay naming each affected monitor. **Bad-state events only** —
+  recovery fires no popup.
 - **Blink** — the tint element gains `.is-blinking` for the 5s pulse, then the colour **holds**.
+  **Bad-state events only** — recovery fires no blink and no tint.
+
+**Recovery event — audio-only, by design.** `useMonitorAlerts` also computes `recovered` = keys
+that were non-operational in the previous poll and have **dropped out of `model.rows`** this poll,
+and calls `playBeeps('recovered')` (the rising chime) for them. It deliberately fires **no popup
+and no screen tint**: the level-triggered standing tint already clears itself when a row leaves
+the set, and a green "all clear" popup/flash would fight the "the board only shouts when something
+is wrong" design. So recovery is silent **visually** but audible. Two edge rules: the **first
+poll is still the baseline** (opening the page mid-outage does not chime), and if a bad-state
+change and a recovery land in the **same 5s poll the bad-state alert wins** that tick, avoiding
+overlapping sounds (simultaneous transitions are rare).
 
 **State — `standingRole(model)`** returns `critical` if any row is offline, else `warning` if any
 is degraded, else `null` (no tint). The tint element only renders while `standingRole` is
@@ -148,8 +168,10 @@ Note the two can legitimately show different colours at once: the tint always re
 **worst-current** state while the popup reflects **the event**, so a degraded-event popup can sit
 on a red screen because something else is still offline. That is correct, not a bug.
 
-Verified across full cycles: beep sequence 720 / 990 990 / 720, silent on unchanged and on
-recovery, popup held 4982 ms and 4955 ms against the 5s spec; amber standing → red when offline
+Verified across full cycles (against the original 1-beep-720 / 2-beep-990 tuning; the current
+values are 3×720 / 4×410 / recovered 620→800→980): distinct sounds per event, silent on
+unchanged, recovery now chimes but stays visually silent, popup held 4982 ms and 4955 ms against
+the 5s spec; amber standing → red when offline
 joined (priority) → amber when offline cleared → no tint on full recovery, with the blink
 stopping after 5s and the colour held. Circle verified against the DOM: `#0ca30c` all-clear,
 `#fab219` degraded only, `#d03b3b` with 1 degraded + 1 offline, and `textNodesInSvg = 0`.
@@ -209,8 +231,9 @@ reduced-motion viewer never lands on a fully-invisible (opacity 0) glow.
   OneUptime call returns HTTP 200 with a malformed or empty body, `buildMonitorModel` yields
   total 0, empty buckets and empty rows. The status pill correctly degrades to "Unknown", but
   the affected-list card still reads **"All 0 monitors are operational"**, and any
-  previously-degraded monitor silently disappears **with no alert** (recovery is silent by
-  design, and an empty row set is indistinguishable from a full recovery). Since the standing
+  previously-degraded monitor silently disappears — and, worse now that recovery is audible,
+  the mass drop-out is **indistinguishable from a full recovery**, so the panel plays the happy
+  **recovery chime** for every vanished monitor on a parse failure. Since the standing
   tint and the status circle are both driven by that same empty row set, a parse failure also
   **clears a standing red screen back to green** — the most reassuring possible display of a
   total loss of visibility. Recommended fix: treat "zero resources parsed" as an **error
@@ -231,6 +254,18 @@ summary, and caches ~5s. Rationale:
   alerting really wants (today the baseline resets every time a tab reloads).
 
 ## Change history
+- 2026-08-14 — Generalised alert-sound synthesis and added a **recovery chime**. The old
+  `BEEP_COUNT`/`BEEP_HZ`/`BEEP_MS`/`BEEP_GAP_MS`/`BEEP_VOLUME` constants and the square-wave-only
+  `playBeeps` were replaced by a single per-role `ALERT_SOUND` table (count / freq / per-beep
+  `step` / duration / gap / volume / `wave`) read by a generalised `playBeeps(role)` (signature
+  unchanged). Retuned to degraded 3×square@720, offline 4×square@410 (was degraded 1×@720,
+  offline 2×@990). Recovery — a monitor dropping out of the non-operational row set — now plays
+  a distinct rising chime (620→800→980, freq 620/step 180) and is **audio-only by design**: no
+  popup, no tint (the standing tint already self-clears; a green "all clear" flash would fight
+  the "only shouts when wrong" design). First poll stays the silent baseline; a bad-state change
+  and a recovery in the same tick let the bad-state alert win. Sounds were tuned by ear in a
+  throwaway standalone browser "Sound Lab" (not a repo file) and ported in. Corrects the prior
+  "recovery is silent" and old beep-count/pitch documentation. (jcardinal)
 - 2026-08-14 — The standing (level-triggered) edge tint now **slowly breathes** its opacity
   0→1→0 on a 7s ease-in-out loop (`@keyframes alert-breathe`) instead of holding a static tint,
   so a still-broken screen draws a distant eye. The fast 0.7s `.is-blinking` event pulse still

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.587",
+  "version": "1.0.588",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",