toga-ai 1.0.585 → 1.0.586

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

@@ -7,7 +7,7 @@ client: shared
 type: feature
 status: active
 updated: 2026-08-14
-owners: [kyalamarthi]
+owners: [kyalamarthi, jcardinal]
 files:
   - tools/assets/clickup/sprint-dashboard.html
   - tools/mvc/clickup/react/get.php
@@ -168,12 +168,22 @@ stays on the **base** hue, so the dashboard underneath stays readable instead of
 bright layer is written `var(--alert-bright, var(--alert-color))` so it **degrades to the base
 colour** if the property never reaches the element.
 
-Standing and blinking differ only in intensity, which is what keeps "steady = still broken"
-distinguishable from "pulsing = something just changed":
+Standing and blinking differ in intensity **and in animation tempo**, which is what keeps
+"still broken" distinguishable from "something just changed":
 
-- `.alert-flash` (standing) — 12px rim, `opacity: .85`, no animation. It may sit on screen for
-  hours.
-- `.alert-flash.is-blinking` (event) — 20px rim, `opacity: 1`, plus the 0.7s pulse.
+- `.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.
+- `.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.
+
+The base `.alert-flash { opacity: .85 }` is the **reduced-motion fallback**, not the animated
+default — see the `prefers-reduced-motion` gotcha. It is deliberately non-zero so a
+reduced-motion viewer never lands on a fully-invisible (opacity 0) glow.
 
 ## Gotchas
 
@@ -192,7 +202,9 @@ distinguishable from "pulsing = something just changed":
   Once the blink moved to `.alert-flash.is-blinking` (specificity 0,2,0), a reduced-motion rule
   on `.alert-flash` alone (0,1,0) **could no longer override it** and the screen kept pulsing.
   The rule must list both: `.alert-flash, .alert-flash.is-blinking { animation: none; }`. Any
-  future state/modifier CSS split has the same trap.
+  future state/modifier CSS split has the same trap. Because it already names `.alert-flash`,
+  this same rule **also covers the new slow `alert-breathe` breathe** — a reduced-motion viewer
+  falls back to the static `opacity: .85` glow with **no separate rule needed**.
 - **A parse failure currently looks calmer than an outage** (known issue, not fixed). If the
   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
@@ -219,6 +231,13 @@ summary, and caches ~5s. Rationale:
   alerting really wants (today the baseline resets every time a tab reloads).
 
 ## Change history
+- 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
+  out-specifies it, keeping "just changed" (fast) distinct from "still broken" (slow breathe);
+  tempo tuned with the developer (0.5→0.92/10s too subtle, 0→1/10s too slow → 0→1/7s). The
+  existing `prefers-reduced-motion` compound-selector rule already covers the new animation, so
+  reduced-motion falls back to the deliberately non-zero static `opacity: .85` glow. (jcardinal)
 - 2026-08-14 — Built the monitor status column on `/clickup/react` (split layout, solid status
   circle + legend + degraded/offline card) as components in the same document rather than a
   nested iframe, sharing one 5s poll; documented the OneUptime public status-page overview API

package/package.json

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