toga-ai 1.0.577 → 1.0.579

package/.claude-plugin/marketplace.json

@@ -43,6 +43,11 @@
         "name": "harness-audit",
         "command": "/harness-audit",
         "description": "Audit knowledge base and harness health, score 0-100."
+      },
+      {
+        "name": "migrate-github-org",
+        "command": "/migrate-github-org",
+        "description": "Repoint local git remotes from the old GitHub org to the new org across every repo in the developer's workspace."
       }
     ],
     "agents": [

package/knowledge/1.0/apps/tools/INDEX.md

@@ -10,6 +10,7 @@
 | [/errors Curation Console (Tools → shared Core Logs DB)](features/errors-curation-console.md) | Internal-only triage/curation screen for the 2.0 Issue/Event error-reporting pipeline, built as a 1.0 Tools MVC page reading the **shared Core Logs DB** through | tools/mvc/errors/get.php, tools/mvc/errors/post.php, tools/mvc/errors/issue/get.php, tools/assets/css/style.css, tools/_/app/nav.php, tools/config.production.ini |
 | [Legacy Email Notifier (tools /email-migration/notify)](features/legacy-email-notifier.md) | An SSO-gated admin tool at **`/email-migration/notify`** (nav group **Email Migration** > **Legacy Notifier**, personas `['TOGa Technology','Development Team']` | tools/mvc/email-migration/notify/get.php, tools/mvc/email-migration/notify/post.php, tools/_/app/nav.php |
 | [Tools MVC — Routing, CSRF & App_Database Access Patterns](features/mvc-data-access-patterns.md) | The load-bearing 1.0 (`App_`) framework conventions a developer needs when adding a page to the Tools app — URL routing, CSRF, and DB access through `App_Databa | tools/_/app/nav.php, tools/mvc/get.php, library/app/error.php, library/app/database.php |
+| [OneUptime Monitor Status Panel & Outage Alerting (tools /clickup/react)](features/oneuptime-monitor-status-panel.md) | A live **operational monitor column** on the wall-display dashboard at `/clickup/react`. | tools/assets/clickup/sprint-dashboard.html, tools/mvc/clickup/react/get.php |
 | [Tools Persona-Gated Navigation (App_Nav)](features/persona-gated-navigation.md) | `App_Nav` is the Tools app's two-level, **persona-gated** navigation. | tools/_/app/nav.php, tools/mvc/get.php |
 | [Tools SAML SSO Consumer & Persona-Gated Auth (App_Auth)](features/saml-sso-auth.md) | `App_Auth` is the Tools app's authentication layer: it consumes the SAML gateway `?saml=` handoff (see the 2.0 SAML downstream integration contract), establishe | tools/_/app/auth.php, tools/mvc/sso/initiate/get.php, tools/mvc/sso/get.php, tools/mvc/login/get.php, tools/mvc/login/post.php, tools/mvc/logout/get.php, tools/mvc/get.php, tools/config.production.ini, tools/config.local.ini |
 | [Talos Knowledge Base Admin UI (KB Documents + Vocabulary)](features/talos-kb-documents-admin.md) | > **PER-AI-MODEL, DATA-DRIVEN SCOPING (2026-07-29).** The KB-documents and Vocabulary admin > UIs were refactored from a single hard-coded **"development-team"* | tools/mvc/talos/kb-documents/get.php, tools/mvc/talos/kb-documents/post.php, tools/mvc/talos/knowledge-bases/get.php, tools/mvc/talos/knowledge-bases/post.php, tools/mvc/talos/vocabulary/get.php, tools/mvc/talos/vocabulary/post.php, tools/_/app/talos/s3.php, tools/_/app/talos/bedrock.php, tools/_/app/pg.php, tools/_/app/model/true/aimodels.php, tools/_/app/model/true/vectorindexes.php, tools/_/app/model/true/aimodels_vectorindexes.php, tools/_/app/worker.php, tools/_/app/nav.php, tools/config.production.ini, tools/config.alpha.ini, tools/.platform/httpd/conf.d/timeouts.conf, tools/.platform/hooks/prebuild/01-install-php-pgsql.sh, tools/.platform/hooks/postdeploy/01-restart-php.sh |

package/knowledge/1.0/apps/tools/architecture.md

@@ -6,8 +6,8 @@ project: Tools
 client: shared
 type: architecture
 status: active
-updated: 2026-08-04
-owners: [jcardinal]
+updated: 2026-08-14
+owners: [jcardinal, kyalamarthi]
 files:
   - tools/index.php
   - tools/_/app/framework.php
@@ -30,6 +30,7 @@ related:
   - ./features/saml-sso-auth.md
   - ./features/persona-gated-navigation.md
   - ./features/developer-tools.md
+  - ./features/oneuptime-monitor-status-panel.md
   - ../library/architecture.md
   - ../library/features/mvc-page-pattern-and-app-skeleton.md
 ---
@@ -97,6 +98,24 @@ routes to `/login` (one-step SSO sign-in — no intermediate welcome card). A pe
 authenticated user gets the dashboard's explicit empty-state (see
 `features/persona-gated-navigation.md`).
 
+## Wall-display routes & third-party browser dependencies
+
+Tools is no longer only a click-through internal-tool shell: `/clickup/react` is an
+**unattended wall display** that holds a full-screen colour state **indefinitely** — an ambient,
+always-on status surface rather than a page someone visits (see
+`features/clickup-sprint-dashboard.md` and `features/oneuptime-monitor-status-panel.md`). Two
+architectural consequences:
+
+- **One cross-origin browser dependency.** Every other fetch in this app is same-origin and
+  authenticated by the SSO session cookie. The monitor column is the sole exception: the browser
+  POSTs directly to the OneUptime **public** status-page API on another host (CORS-open, no
+  credentials, raw JSON — not the api2 envelope). Nothing proxies it server-side today, so an
+  upstream CORS or availability change breaks that panel in the browser with no server-side signal.
+- **Iframed pages carry their own permission policy.** `mvc/clickup/react/get.php` embeds its
+  asset in an iframe, and browser autoplay policy is scoped **per-iframe** — an iframed page that
+  must play audio needs `allow="… autoplay"` on the frame or it is blocked silently. Unattended
+  displays additionally never receive the user gesture browsers require before audio plays.
+
 ## Adding a tool
 
 Create `mvc/<folder>/<tool>/get.php` (copy `mvc/_TEMPLATE/get.php`), add one entry to
@@ -115,6 +134,11 @@ Create `mvc/<folder>/<tool>/get.php` (copy `mvc/_TEMPLATE/get.php`), add one ent
   **Action still owed:** rotate every secret in `config.production.ini` — the file was
   reachable, so treat all of it as compromised. (Location only — no values recorded here.)
 - **SSO initiation + replay defense are open items** — see `features/saml-sso-auth.md`.
+- **Unproxied third-party polling from the browser (`/clickup/react`).** The monitor column pulls
+  ~250 KB from OneUptime every 5s — ~3 MB/min **per open tab** — to render about six numbers, and
+  hardcodes the status-page ID in the HTML asset. Recommended fix: a small server-side endpoint
+  (e.g. `/v2/monitors/status/`) that fetches, reduces and caches ~5s, moving the ID into config and
+  removing the cross-origin dependency. Advisory, not scheduled.
 - **Framework-level Sentry error reporting is an open gap.** Prod printed "Sentry is not
   installed" because `sentry/sentry` was missing from `composer.json` (added `^4.10`; sibling
   apps use `^4.10`/`^4.19`). But even with Sentry in `vendor/`, the 1.0 framework does **not**
@@ -123,6 +147,11 @@ Create `mvc/<folder>/<tool>/get.php` (copy `mvc/_TEMPLATE/get.php`), add one ent
   composer package must `require_once` the autoloader itself.
 
 ## Change history
+- 2026-08-14 — Recorded that `/clickup/react` is now an unattended wall display holding a
+  full-screen colour state indefinitely, carrying the app's only cross-origin browser dependency
+  (OneUptime public status-page API) plus per-iframe permission policy
+  (`allow="fullscreen; autoplay"`), and logged the unproxied ~3 MB/min poll + hardcoded
+  status-page ID as a known issue with a server-side-proxy fix. (kyalamarthi)
 - 2026-08-04 — Added the app-wide light/dark/auto theme: `assets/css/theme.css` token layer
   registered first in `App_FrameworkIndex_Tools`, pre-paint `data-theme` stamping via the
   one-and-only `setHeaderCode()` hook, `localStorage` preference (no DB column), nav/public

package/knowledge/1.0/apps/tools/features/clickup-sprint-dashboard.md

@@ -6,7 +6,7 @@ project: Tools
 client: shared
 type: feature
 status: active
-updated: 2026-08-04
+updated: 2026-08-14
 owners: [kyalamarthi, jcardinal]
 files:
   - tools/_/app/clickup/sprint.php
@@ -21,6 +21,7 @@ files:
   - tools/mvc/login/get.php
   - tools/_/app/nav.php
 related:
+  - ./oneuptime-monitor-status-panel.md
   - ./persona-gated-navigation.md
   - ./saml-sso-auth.md
   - ./mvc-data-access-patterns.md
@@ -36,6 +37,12 @@ built for a wall-mounted **TV display** ("TOGa IQ" internal sprint metrics). It
 standalone Node/Express prototype from a prior session, folding the dashboard into `tools`
 so it runs on the existing App\_ framework + SSO with no separate service.
 
+The page is now a **two-column split**: this sprint board at 80%, and an operational
+**monitor status column** filling the rest — documented separately in
+[OneUptime Monitor Status Panel](./oneuptime-monitor-status-panel.md). The sprint board itself
+was left byte-for-byte unchanged when that landed (its component was renamed `SprintBoard` and
+wrapped in a two-line `Dashboard`).
+
 It reads the **same Team DB** and reproduces the **same Power BI-parity metric definitions**
 already documented for worker2 — see
 [team-sprint-management](../../../2.0/apps/worker2/features/team-sprint-management.md). This
@@ -80,11 +87,39 @@ Babel-standalone from CDN, JSX inside a `<script type="text/babel">`. **No build
 npm, no bundler.** It fetches `/v2/sprints/*` **same-origin**, so the SSO session cookie
 authenticates the calls automatically. Do not mistake this for a bundled React app.
 
+### Retiring a work type or a departed developer — filter client-side, not in the mock
+
+Two `ALL_CAPS` constants near the top of the HTML drop rows from the **live** API responses,
+both matched case-insensitively and trimmed:
+
+- **`RETIRED_WORK_TYPES`** — applied to the `worktype-breakdown` response. Currently `STRETCH`,
+  retired because the team no longer plans stretch work. The STRETCH **KPI tile** (which called
+  `/v2/sprints/tile/?category=stretch`), its colour mapping and its Work Type slice were removed
+  outright.
+- **`FORMER_DEVS`** — applied to the `points-by-dev` response, to keep a departed developer off
+  "Sprint Points By Dev".
+
+**Editing the `USE_MOCK` fixtures does nothing.** `USE_MOCK` is `false` and the live API drives
+the page, so a name or category only disappears when it is filtered out of the **response**.
+Verified against live sprint 84: the departed developer was still returned by
+`/v2/sprints/points-by-dev/` with 33 points (In Review 29, Complete 4), while the API had
+already stopped returning STRETCH — so that filter now matters only for historical sprints.
+See [Gotchas](#gotchas) for the historical-sprint caveat these filters carry.
+
+### Sprint Burndown series
+
+Burndown is **Target** (grey dashed) + **Committed** (red) only. The blue **"All"** series was
+dropped alongside STRETCH — with that category retired it tracked "Committed" too closely to
+earn a second line. The legend derives from the `BURNDOWN_SERIES` constant, so it updated
+itself; add or remove a line there rather than editing the legend.
+
 ### Embed page — `mvc/clickup/react/get.php`
 
-A PHP MVC view that `requireAuth`s, then embeds `sprint-dashboard.html` in an
-`<iframe allowfullscreen>` (cache-busted by `filemtime`). Heading "Clickup Dashboard",
-subtitle notes the data is "…refreshed every 5 min."
+A PHP MVC view that `requireAuth`s, then embeds `sprint-dashboard.html` in an iframe
+(cache-busted by `filemtime`). Heading "Clickup Dashboard", subtitle notes the data is
+"…refreshed every 5 min." The frame is `allow="fullscreen; autoplay"` — **autoplay is
+load-bearing**, not decorative: it is what lets the monitor column's outage beeps sound (see
+[the monitor panel doc](./oneuptime-monitor-status-panel.md)).
 
 ### Nav — `_/app/nav.php`
 
@@ -121,6 +156,16 @@ the React dashboard supersedes it.
   `cd tools && ENVIRONMENT=dev-local php -d "include_path=.;C:/www/library" -S localhost:8000 router.php`.
   The `App_` framework + `_.php` bootstrap load from the separate `library` repo via
   `include_path`; `router.php` reproduces the `.htaccess` rewrite for PHP's built-in server.
+  The dev server binds to **localhost only**.
+- **Reach the dashboard through `/clickup/react`, never the raw asset.** The `/v2/sprints/*`
+  endpoints are same-origin PHP authenticated by the Tools **SSO session cookie**. Opening
+  `/assets/clickup/sprint-dashboard.html` directly in an unauthenticated tab makes **every**
+  `/v2` call return **HTTP 401** and the page renders empty — the route, not the file, is what
+  carries the session.
+- **Expected local-only console noise.** Twelve `ERR_CONNECTION_REFUSED` for
+  `http://localhost/resources/*` (the shared 1.0 jquery / fontawesome / `library.css` /
+  `library.js` are expected on port 80) and a resulting `preloaderExit is not defined`. Both are
+  pre-existing and local-only — not symptoms of anything in this feature.
 
 > Credentials note: DB creds and the `dev_mode` / `dev_autologin` flags live in the
 > git-ignored `config.dev-local.ini` — never commit values.
@@ -138,6 +183,17 @@ the React dashboard supersedes it.
   `buildArrayOfRows(App_Database::query($sql,$db), false)` raises "Only variables should be
   passed by reference", which the E_ALL error handler promotes to a fatal 500. Assign first:
   `$res = App_Database::query(...); buildArrayOfRows($res, false);`.
+- **`RETIRED_WORK_TYPES` / `FORMER_DEVS` are client-side and unconditional, so historical
+  sprints under-report.** Browsing a past sprint that genuinely had stretch work, or that
+  developer's points, silently shows lower numbers than the API returned — the filter does not
+  know which sprint is on screen. Acceptable for a wall display pinned to the current sprint;
+  the correct long-term fix is to filter in `App_Clickup_Sprint` (server-side) or to scope the
+  filter to the current sprint only.
+- **`StatusChart`'s `USE_MOCK` fixture is broken (dev-only, unfixed).** The fixture supplies
+  `{label, count}` but the code reads `b.points`, so every value is `undefined`, gets filtered
+  out, and the Status panel renders **blank** whenever `USE_MOCK = true`. Production is
+  unaffected — the live API returns `points`. One-word fix (`count:` → `points:`) if anyone
+  needs the mock; deliberately left alone as out of scope.
 
 - **The old Power BI embed page (`mvc/clickup/dashboard/get.php`) keeps ~6 fixed colour
   literals on purpose — do NOT theme them.** Its card/frame colour `#0b1020` is matched to the
@@ -147,6 +203,14 @@ the React dashboard supersedes it.
   [App-Wide Colour Theme](./theme-light-dark.md).
 
 ## Change history
+- 2026-08-14 — Retired the **STRETCH** work type (KPI tile, colour, Work Type slice) and removed
+  the blue **"All"** burndown series, leaving Target + Committed; added the client-side
+  `RETIRED_WORK_TYPES` / `FORMER_DEVS` response filters (editing the `USE_MOCK` fixtures does
+  nothing — the live API drives the page) and recorded their historical-sprint under-reporting
+  caveat. Embed iframe is now `allow="fullscreen; autoplay"` for the new
+  [monitor status column](./oneuptime-monitor-status-panel.md), which shares this document.
+  Documented the raw-asset **401** trap and expected local console noise, plus the broken
+  `StatusChart` mock fixture. (kyalamarthi)
 - 2026-08-04 — Tokenised the `/clickup/dashboard` page-local styles for the app-wide light/dark
   theme, keeping ~6 deliberate fixed literals (incl. the `#0b1020` frame that matches the
   embedded Power BI canvas so the iframe load does not flash white). Not committed. (jcardinal)

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

@@ -0,0 +1,232 @@
+---
+title: OneUptime Monitor Status Panel & Outage Alerting (tools /clickup/react)
+framework: "1.0"
+repo: tools
+project: Tools
+client: shared
+type: feature
+status: active
+updated: 2026-08-14
+owners: [kyalamarthi]
+files:
+  - tools/assets/clickup/sprint-dashboard.html
+  - tools/mvc/clickup/react/get.php
+related:
+  - ./clickup-sprint-dashboard.md
+  - ../architecture.md
+  - ../../worker/features/oneuptime-worker-uptime-monitoring.md
+  - ../../../../2.0/apps/worker2/features/oneuptime-worker2-monitoring.md
+---
+
+## Summary
+
+A live **operational monitor column** on the wall-display dashboard at `/clickup/react`. The
+page is a two-column split — the ClickUp sprint board at 80%, the monitor column filling the
+rest, each a bordered rounded card. The column shows an overall status pill, a **single solid
+status circle** carrying the whole system's state, a per-status legend (count + %), and a
+"Degraded and offline" card listing name / group / status / how long it has been in that state.
+
+The display is designed to be read **from across a room**: when a monitor changes to a bad state
+it **beeps, pops up and blinks**, and for as long as anything is still down the **screen edges
+hold a standing colour tint**.
+
+It reads the **OneUptime public status-page overview API** directly from the browser. This is
+the **read/consumer** side of OneUptime and is unrelated to the push-heartbeat monitors the
+worker tiers report *into* — see
+[OneUptime push-metric monitors for 2.0 workers](../../../../2.0/apps/worker2/features/oneuptime-worker2-monitoring.md)
+and [OneUptime external uptime monitoring for 1.0 workers](../../worker/features/oneuptime-worker-uptime-monitoring.md)
+for that side. Those docs define what *creates* the statuses this panel renders.
+
+## How it works
+
+### One document, not a nested iframe
+
+The panel is implemented as React components **in the same `sprint-dashboard.html` document**
+as the sprint board. It is deliberately **not** a nested iframe: `mvc/clickup/react/get.php`
+already iframes this page, so nesting a second frame would load a **second React runtime** and
+run a **duplicate ~250 KB poll**.
+
+The existing sprint board was left byte-for-byte unchanged — its component was renamed
+`SprintBoard` and a two-line `Dashboard` wrapper added around it plus the monitor column. The
+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`.
+
+### Upstream contract — OneUptime public status-page overview API
+
+Reusable for any future status display. Endpoint:
+
+```
+POST https://oneuptime.com/status-page-api/overview/<statusPageId>
+body: {}
+```
+
+- **It is a POST, not a GET**, and it returns **raw JSON** — **not** the api2
+  `{isSuccess, data, messages}` envelope used everywhere else in TOGA. The payload **is** the
+  data. Do not unwrap a `.data` that isn't there.
+- A **public** status page needs **no auth** and answers with `Access-Control-Allow-Origin: *`,
+  so the browser can call it cross-origin with **no proxy and no credentials**. This is the one
+  cross-origin call on a page whose every other fetch is same-origin `/v2/*`.
+- The response is **~250 KB**.
+- Values arrive as **typed envelopes** — `{_type: "ObjectID" | "DateTime" | "Color", value: …}`
+  — so read `.value`, never the object. Dates are ISO-8601 UTC with a trailing `Z`.
+- A monitor's **current** state is `statusPageResources[].monitor.currentMonitorStatusId`,
+  resolved against the `monitorStatuses[]` list.
+- In `monitorStatusTimelines[]`, the entry with **`endsAt: null`** is the **open** interval —
+  i.e. when the current state began. That is what drives "in this state for X".
+
+The status page ID is currently a hardcoded constant (`MONITOR_STATUS_PAGE_ID`) in the HTML;
+moving it to config is part of the recommended next step below. (Identifier location only — no
+value recorded here.)
+
+### Status bucketing is derived, never hardcoded
+
+Buckets are computed from the status list itself, not from a hardcoded set of status names:
+
+- `isOperationalState` → **good**
+- the **worst-priority non-operational** status → **offline / critical**
+- anything in between → **degraded**
+
+So a renamed status, or a newly added one, still lands in the right bucket without a code
+change.
+
+### The status circle — the colour is the message
+
+`MonitorCircle` is **one filled circle** whose colour is the whole system's state: green
+all-clear, amber if anything is degraded, red if anything is offline, **red winning when both**.
+It draws **nothing inside it** — no total, no label.
+
+That is deliberate, and it replaced a `MonitorDonut` (a segmented ring showing per-status
+proportions with the total in the centre) which was **deleted**. From across a room the colour is
+what carries; the legend directly beneath still gives the exact per-status counts, so no
+information is lost. The SVG keeps an `aria-label` listing the counts, so screen readers still
+get the numbers that came off the face of the circle.
+
+The circle's colour comes from the **same `standingRole()`** that drives the screen-edge tint, so
+the circle and the edges can never disagree about severity.
+
+### Alerting — edge-triggered events over a level-triggered state
+
+**The distinction to carry to any future alerting surface.** Two separate mechanisms, and mixing
+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. |
+| **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
+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).
+- 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
+  numerically (`SEVERITY[new] > SEVERITY[old]`), which silently suppressed **offline → degraded**
+  because that is a severity *decrease*. That transition is news, so it is now announced and the
+  now-unused `SEVERITY` map was deleted.
+
+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.
+- **Blink** — the tint element gains `.is-blinking` for the 5s pulse, then the colour **holds**.
+
+**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
+non-null, so a full recovery clears it.
+
+Note the two can legitimately show different colours at once: the tint always reflects
+**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
+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`.
+
+### Two colour pairs: meaning vs. legibility
+
+`MON_COLOR` is the **validated status palette** and drives everything that **carries meaning** —
+icons, legend, popup border, status text, and the status circle. `MON_COLOR_BRIGHT`
+(`good:#25d825, warning:#ffd633, critical:#ff4d4d`) is used **only** for the full-screen edge rim,
+where nothing depends on its exact value and the only job is legibility from across a room. Do
+not let the bright pair leak into anything semantic.
+
+Both reach the overlay as CSS custom properties — `--alert-color` and `--alert-bright`. The rim is
+a **three-layer `box-shadow`**: solid hot rim + tight bright bloom + a deep haze that deliberately
+stays on the **base** hue, so the dashboard underneath stays readable instead of washing out. Each
+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":
+
+- `.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.
+
+## Gotchas
+
+- **The embedding iframe needs `allow="autoplay"` or the alert sound is silently blocked.**
+  Browser autoplay policy is scoped **per-iframe**. `mvc/clickup/react/get.php` embedded the
+  dashboard with `allow="fullscreen"`, so Web Audio inside the frame was policy-blocked and the
+  beeps would never have sounded in the Tools app — with no error. It is now
+  `allow="fullscreen; autoplay"`. Any future iframed page that makes sound needs the same.
+- **Permission is not enough — browsers still require one user gesture per session.** The page
+  unlocks the `AudioContext` on the first click/keypress, and if an alert fires while audio is
+  still blocked the popup **says so** rather than failing silently. On an **unattended wall
+  display nobody ever clicks**, so alerts stay visual-only. For kiosk use, launch Chrome with
+  `--autoplay-policy=no-user-gesture-required`.
+- **The `prefers-reduced-motion` override needs the compound selector.** Blinking is a
+  vestibular risk, so the reduced-motion rule kills the animation and holds the colour steady.
+  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.
+- **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
+  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
+  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
+  state**, not a healthy one.
+
+## Recommended next step (advisory — not built)
+
+Replace the direct browser → OneUptime poll with a small **server-side proxy endpoint** in the
+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
+  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.
+- The status page ID moves into **config** instead of hardcoded HTML.
+- It gives a natural home for **server-side transition history**, which is what edge-triggered
+  alerting really wants (today the baseline resets every time a tab reloads).
+
+## Change history
+- 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
+  contract (POST, raw JSON not the api2 envelope, CORS-open, typed `{_type,value}` envelopes,
+  `endsAt: null` = open interval) and derived status bucketing. Alerting splits **edge-triggered
+  events** (beeps / popup / 5s blink, now firing on any non-operational change incl.
+  offline → degraded) from a **level-triggered standing tint** driven by `standingRole()`, which
+  also colours the circle so the two can never disagree; added the `MON_COLOR_BRIGHT` rim-only
+  palette. Fixed the iframe `allow="fullscreen; autoplay"` autoplay block and recorded the
+  user-gesture/kiosk caveat, the `prefers-reduced-motion` specificity trap, the malformed-body
+  "all 0 monitors operational" gap, and the server-side-proxy recommendation. (kyalamarthi)

package/knowledge/INDEX.md

@@ -14,7 +14,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 - **walmarttechservices** (Walmart Tech Services) — 1 doc(s) → [1.0/apps/walmarttechservices/INDEX.md](1.0/apps/walmarttechservices/INDEX.md)
 - **test** (Test) — 14 doc(s) → [1.0/apps/test/INDEX.md](1.0/apps/test/INDEX.md)
 - **toga** (TOGa) — 3 doc(s) → [1.0/apps/toga/INDEX.md](1.0/apps/toga/INDEX.md)
-- **tools** (Tools) — 14 doc(s) → [1.0/apps/tools/INDEX.md](1.0/apps/tools/INDEX.md)
+- **tools** (Tools) — 15 doc(s) → [1.0/apps/tools/INDEX.md](1.0/apps/tools/INDEX.md)
 
 ## 2.0 framework
 
@@ -39,7 +39,7 @@ _Auto-generated by `knowledge.js index`. Do not hand-edit._
 - **togatech** (TOGA Technology Website) — 6 doc(s) → [standalone/apps/togatech/INDEX.md](standalone/apps/togatech/INDEX.md)
 - **websocket** (WebSocket Server) — 2 doc(s) → [standalone/apps/websocket/INDEX.md](standalone/apps/websocket/INDEX.md)
 - **forward** (Forwarder) — 3 doc(s) → [standalone/apps/forward/INDEX.md](standalone/apps/forward/INDEX.md)
-- **claude** (Claude Harness) — 7 doc(s) → [standalone/apps/claude/INDEX.md](standalone/apps/claude/INDEX.md)
+- **claude** (Claude Harness) — 8 doc(s) → [standalone/apps/claude/INDEX.md](standalone/apps/claude/INDEX.md)
 
 ## Clients
 

package/package.json

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

package/skills/migrate-github-org/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: migrate-github-org
+description: Repoints local git remotes from the old GitHub org (agilantsolutions) to the new org (togatech) across every repo in the developer's workspace, without touching SSH keys, tokens, or repo names. Trigger when the user says "migrate-github-org", "update my github remotes", "switch to the new github org", "point my repos at togatech", or asks how to update their local setup after the org transfer.
+---
+
+# Migrate GitHub Org — repoint local remotes after the org transfer
+
+TOGA is moving its repos from the `agilantsolutions` GitHub org to `togatech`. The
+org-level transfer (repo Settings → Transfer ownership) is done once by an admin.
+**This skill is the per-developer follow-up** — it updates each developer's local
+git remotes so `git`/GitHub Desktop keep working against the new org.
+
+## Before running this
+
+Confirm with the developer:
+1. **Has the org transfer already happened?** If repos don't exist at
+   `github.com/togatech/<repo>` yet, do not run this — the local remote would point
+   at a repo that doesn't resolve. Ask them to check with the admin first.
+2. **Is their GitHub account a member of `togatech`?** If not, pushes/pulls will
+   fail with a 403 or "repository not found" regardless of remote URL — this is
+   an org-membership issue, not something this script fixes.
+
+If either is unconfirmed, tell the developer to check before proceeding, but still
+offer to run the script if they want to prepare ahead of time — it's safe to run
+against repos still on the old org (it just does nothing until the org changes).
+
+## Step 1 — Locate the script
+
+The script lives next to this SKILL.md in the team repo:
+
+```bash
+for d in claude ../claude; do [ -f "$d/skills/migrate-github-org/migrate-github-org.sh" ] && REPO="$d" && break; done
+echo "${REPO:-NOT_FOUND}"
+```
+
+If `NOT_FOUND`, tell the user to run `/sync-team-skills` first (or clone
+`https://github.com/TOGATechnology/claude`), then retry.
+
+## Step 2 — Run it against their workspace
+
+Run from the developer's actual project/workspace root (the folder containing
+their repo checkouts as subfolders — e.g. `www`, `2.0`, whatever they call it):
+
+```bash
+bash "$REPO/skills/migrate-github-org/migrate-github-org.sh" .
+```
+
+If the user is running this from inside VS Code with the workspace folder already
+open, `.` is correct — no path argument needed.
+
+## Step 3 — Report results
+
+Relay the script's own summary output verbatim (updated / skipped / no-origin
+counts and the list of repos changed) — do not re-summarize or drop detail.
+
+Then tell the developer:
+- If any repos were **updated**: restart GitHub Desktop (or close/reopen the repo
+  in it) so it picks up the new remote URL.
+- The **first push or pull** after this may prompt for re-authentication if their
+  GitHub account doesn't yet have access to `togatech` — that's expected, not a
+  bug in the script. They should sign in / re-authorize when prompted.
+- No SSH keys or manually-generated tokens are needed for this step — GitHub
+  Desktop handles HTTPS auth via its own sign-in. A token only matters for
+  someone with a manually configured PAT used outside Desktop (CI scripts,
+  `composer.json` VCS repos, deploy hooks) — those need separate re-scoping to
+  `togatech` and are out of scope for this skill.
+
+## What this does NOT do
+
+- Does not transfer repos on GitHub itself (that's the admin's one-time step).
+- Does not touch SSH remotes, deploy keys, CI secrets, or hardcoded org
+  references in code/config (ebextensions, composer.json, etc.) — those need
+  a separate sweep.
+- Does not grant org membership or repo permissions.
+
+## Self-updating anomaly log
+
+If you hit an error, permission issue, or unexpected behavior not already
+documented above — even if you worked around it — record it here so the next
+developer doesn't hit it blind.
+
+### Known anomalies
+
+(none yet)

package/skills/migrate-github-org/migrate-github-org.sh

@@ -0,0 +1,77 @@
+#!/usr/bin/env bash
+#
+# migrate-github-org.sh
+#
+# Scans a workspace directory for git repos and repoints any remote that
+# points at OLD_ORG on github.com to NEW_ORG, keeping the repo name and
+# the HTTPS protocol (what GitHub Desktop uses) unchanged.
+#
+# Usage:
+#   ./migrate-github-org.sh [workspace-dir]
+#
+#   workspace-dir defaults to the current directory.
+#
+# Safe to re-run: repos already pointing at NEW_ORG, or at any org other
+# than OLD_ORG, are left untouched and reported as skipped.
+
+set -euo pipefail
+
+OLD_ORG="agilantsolutions"
+NEW_ORG="togatech"
+
+WORKSPACE="${1:-.}"
+
+if [ ! -d "$WORKSPACE" ]; then
+    echo "Error: workspace directory not found: $WORKSPACE" >&2
+    exit 1
+fi
+
+updated=0
+skipped=0
+not_git=0
+
+echo "Scanning $WORKSPACE for git repositories..."
+echo "Renaming remotes: github.com/$OLD_ORG/<repo> -> github.com/$NEW_ORG/<repo>"
+echo
+
+# Only descend one level into WORKSPACE — each subfolder is treated as a
+# candidate repo. Adjust maxdepth if your repos are nested deeper.
+while IFS= read -r -d '' gitdir; do
+    repo_path="$(dirname "$gitdir")"
+    repo_name="$(basename "$repo_path")"
+
+    remote_url="$(git -C "$repo_path" remote get-url origin 2>/dev/null || true)"
+
+    if [ -z "$remote_url" ]; then
+        echo "  [no origin]  $repo_name"
+        not_git=$((not_git + 1))
+        continue
+    fi
+
+    case "$remote_url" in
+        *"github.com/$OLD_ORG/"*|*"github.com:$OLD_ORG/"*)
+            new_url="${remote_url/$OLD_ORG/$NEW_ORG}"
+            git -C "$repo_path" remote set-url origin "$new_url"
+            echo "  [updated]    $repo_name"
+            echo "               $remote_url"
+            echo "            -> $new_url"
+            updated=$((updated + 1))
+            ;;
+        *)
+            echo "  [skipped]    $repo_name  ($remote_url)"
+            skipped=$((skipped + 1))
+            ;;
+    esac
+done < <(find "$WORKSPACE" -mindepth 2 -maxdepth 2 -type d -name ".git" -print0)
+
+echo
+echo "Done. Updated: $updated, skipped (not $OLD_ORG): $skipped, no origin: $not_git"
+
+if [ "$updated" -gt 0 ]; then
+    echo
+    echo "Next steps for each updated repo:"
+    echo "  - If you use GitHub Desktop, close and reopen the repo (or restart Desktop)"
+    echo "    so it picks up the new remote URL."
+    echo "  - The first push/pull against the new org may prompt you to re-authenticate"
+    echo "    if your GitHub account/token doesn't already have access to $NEW_ORG."
+fi