toga-ai 1.0.599 → 1.0.600

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

@@ -6,7 +6,7 @@ project: Tools
 client: shared
 type: feature
 status: active
-updated: 2026-08-14
+updated: 2026-08-18
 owners: [kyalamarthi, jcardinal]
 files:
   - tools/assets/clickup/sprint-dashboard.html
@@ -51,8 +51,9 @@ The existing sprint board was left byte-for-byte unchanged — its component was
 monitor poll is lifted into `Dashboard` and passed **down as props**, so the status panel and
 the alert watcher share **one** fetch loop rather than polling twice.
 
-Only the monitor fetch runs at `MONITOR_REFRESH_MS` (5s); sprint data stays on the page's
-existing 5-minute `AUTO_REFRESH_MS`.
+Only the monitor fetch runs at `MONITOR_REFRESH_MS` (15s); sprint data stays on the page's
+existing 5-minute `AUTO_REFRESH_MS`. At 15s, outage detection (beep/popup/blink) reacts within
+~15s, and the ~250 KB cross-origin poll costs ~1 MB/min per open tab.
 
 ### Upstream contract — OneUptime public status-page overview API
 
@@ -114,7 +115,7 @@ them up is the bug:
 
 | | Trigger | Drives | Why |
 |---|---|---|---|
-| **Event** | **Edge** — fires on the transition | beeps, popup, 5s blink | A level-triggered *event* re-alarms every 5s poll for a monitor that has been offline an hour, and the wall display becomes a siren nobody can silence. |
+| **Event** | **Edge** — fires on the transition | beeps, popup, 5s blink | A level-triggered *event* re-alarms every 15s poll for a monitor that has been offline an hour, and the wall display becomes a siren nobody can silence. |
 | **State** | **Level** — follows current state | standing edge tint, status circle | An edge-triggered *state* would show a clean screen when you open the page during an existing outage. **The board must never look healthy while it isn't.** |
 
 **Event — `useMonitorAlerts`** compares each poll's non-operational rows against the previous
@@ -157,7 +158,7 @@ and no screen tint**: the level-triggered standing tint already clears itself wh
 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
+change and a recovery land in the **same 15s 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
@@ -194,11 +195,10 @@ Standing and blinking differ in intensity **and in animation tempo**, which is w
 "still broken" distinguishable from "something just changed":
 
 - `.alert-flash` (standing) — 12px rim, **slowly breathes** its opacity 0 → 1 → 0 on a
-  **7-second ease-in-out loop** (`@keyframes alert-breathe { 0%,100% { opacity: 0 } 50% {
-  opacity: 1 } }`, applied `animation: alert-breathe 7s ease-in-out infinite`). It may sit on
-  screen for hours, so the gentle 7s breathe draws a distant eye without reading as urgent. The
-  tempo is deliberately slow: the values were tuned with the developer (0.5→0.92 over 10s was
-  too subtle, full 0→1 over 10s too slow) to settle on full 0→1 over 7s.
+  **4-second ease-in-out loop** (`@keyframes alert-breathe { 0%,100% { opacity: 0 } 50% {
+  opacity: 1 } }`, applied `animation: alert-breathe 4s ease-in-out infinite` — a 4s cycle =
+  2s fade-in / 2s fade-out). It may sit on screen for hours, so the gentle breathe draws a
+  distant eye without reading as urgent. The tempo was tuned with the developer.
 - `.alert-flash.is-blinking` (event) — 20px rim, `opacity: 1`, plus the fast **0.7s** pulse.
   Its compound selector (0,2,0) out-specifies the standing breathe (0,1,0), so a just-changed
   monitor shows the urgent fast blink, not the slow breathe.
@@ -245,7 +245,7 @@ Replace the direct browser → OneUptime poll with a small **server-side proxy e
 Tools app (e.g. `/v2/monitors/status/`) that fetches upstream, reduces the payload to the
 summary, and caches ~5s. Rationale:
 
-- The browser currently pulls **~250 KB every 5s (~3 MB/min per open tab)** to display about
+- The browser currently pulls **~250 KB every 15s (~1 MB/min per open tab)** to display about
   six numbers; a proxy makes it ~1 KB.
 - One upstream fetch is shared across **all** open displays instead of one per tab.
 - It removes the cross-origin dependency, and therefore the CORS/autoplay coupling above.
@@ -254,6 +254,12 @@ summary, and caches ~5s. Rationale:
   alerting really wants (today the baseline resets every time a tab reloads).
 
 ## Change history
+- 2026-08-18 — Wall-display cadence tuning. The standing edge-tint breathe cycle changed from
+  5s to **4s** (`animation: alert-breathe 4s …` — 2s fade-in / 2s fade-out), and
+  `MONITOR_REFRESH_MS` changed from 5s to **15s**, so outage detection now reacts within ~15s
+  (was ~5s) and the ~250 KB cross-origin poll drops from ~3 MB/min to ~1 MB/min per open tab.
+  Also corrects prior doc drift: the breathe cycle had been documented as 7s but the code was
+  actually 5s. (jcardinal)
 - 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

package/package.json

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