toga-ai 1.0.510 → 1.0.512

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

@@ -2,7 +2,7 @@
 
 | Doc | Summary | Files |
 |-----|---------|-------|
-| [Tools (1.0 Internal-Tools App) Architecture](architecture.md) | **Tools** is a standalone 1.0 (`App_`) application that houses many small internal tools behind simple interfaces, gated by Client_True staff persona. | tools/index.php, tools/_/app/framework.php, tools/_/app/frameworkindex.php, tools/assets/img/favicon/favicon.ico, tools/assets/img/favicon/favicon-32x32.png, tools/assets/img/favicon/favicon-16x16.png, tools/assets/img/favicon/apple-touch-icon.png, tools/_/app/auth.php, tools/_/app/nav.php, tools/common/header.php, tools/common/footer.php, tools/mvc/get.php, tools/mvc/_TEMPLATE/get.php, tools/docs/ADDING_A_TOOL.md |
+| [Tools (1.0 Internal-Tools App) Architecture](architecture.md) | **Tools** is a standalone 1.0 (`App_`) application that houses many small internal tools behind simple interfaces, gated by Client_True staff persona. | tools/index.php, tools/_/app/framework.php, tools/_/app/frameworkindex.php, tools/assets/img/favicon/favicon.ico, tools/assets/img/favicon/favicon-32x32.png, tools/assets/img/favicon/favicon-16x16.png, tools/assets/img/favicon/apple-touch-icon.png, tools/_/app/auth.php, tools/_/app/nav.php, tools/common/header.php, tools/common/footer.php, tools/mvc/get.php, tools/mvc/_TEMPLATE/get.php, tools/docs/ADDING_A_TOOL.md, tools/assets/css/theme.css, tools/assets/js/theme.js |
 | [ClickUp Sprint Dashboard (tools /clickup/react)](features/clickup-sprint-dashboard.md) | A native **ClickUp sprint dashboard** in the 1.0 `tools` app at route `/clickup/react`, built for a wall-mounted **TV display** ("TOGa IQ" internal sprint metri | tools/_/app/clickup/sprint.php, tools/v2/sprints/tile/index.php, tools/v2/sprints/current/index.php, tools/v2/sprints/status-breakdown/index.php, tools/v2/sprints/worktype-breakdown/index.php, tools/v2/sprints/points-by-dev/index.php, tools/v2/sprints/burndown/index.php, tools/assets/clickup/sprint-dashboard.html, tools/mvc/clickup/react/get.php, tools/mvc/login/get.php, tools/_/app/nav.php |
 | [CloudFront Client Setup](features/cloudfront-client-setup.md) | An SSO-gated admin tool at **`/devops/cloudfront-clients`** in the Tools 1.0 app that onboards a client onto **CloudFront + Route 53 across multiple AWS account | tools/_/app/devops/cloudfront.php, tools/mvc/devops/cloudfront-clients/get.php, tools/mvc/devops/cloudfront-clients/post.php, tools/assets/js/cloudfront-clients.js, tools/assets/css/cloudfront-clients.css, tools/_/app/nav.php, tools/_/app/frameworkindex.php, tools/config.production.ini |
 | [Design Demo Admin](features/design-demo-admin.md) | A self-serve admin UI at **`/design`** in the SSO-protected **Tools** app that lets the design team publish self-contained "Claude Design" HTML exports as **ver | tools/_/app/design/github.php, tools/mvc/design/get.php, tools/mvc/design/post.php, tools/assets/css/design.css, tools/assets/js/design.js, tools/_/app/frameworkindex.php, tools/_/app/nav.php, tools/composer.json |
@@ -14,4 +14,5 @@
 | [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 |
 | [Talos Pricing UI (Contracts, Pricing Dashboard, Usage, Settings + Estimator)](features/talos-pricing-ui.md) | The 1.0 (tools app) face of the **Talos Pricing Platform** — a "Talos Pricing" nav folder with four pages plus the estimate engine. | tools/_/app/nav.php, tools/_/app/talos/estimator.php, tools/_/app/talos/usage.php, tools/mvc/talos/contracts/get.php, tools/mvc/talos/contracts/post.php, tools/mvc/talos/pricing/get.php, tools/mvc/talos/usage/get.php, tools/mvc/talos/settings/get.php, tools/mvc/talos/settings/post.php, tools/assets/css/style.css |
+| [App-Wide Colour Theme (light / dark / auto)](features/theme-light-dark.md) | A **light / dark / auto** colour theme for the *entire* Tools app, built as a single semantic-token layer (`assets/css/theme.css`) rather than per-page edits. | tools/assets/css/theme.css, tools/assets/js/theme.js, tools/_/app/frameworkindex.php, tools/_/app/nav.php, tools/common/header.php, tools/mvc/login/get.php, tools/assets/css/style.css, tools/assets/css/design.css, tools/assets/css/login.css, tools/assets/css/cloudfront-clients.css, tools/assets/css/gchart.css, tools/mvc/talos/usage/get.php, tools/mvc/talos/pricing/get.php, tools/mvc/talos/contracts/get.php, tools/mvc/clickup/dashboard/get.php, tools/mvc/email-migration/notify/post.php |
 | [Deploying Tools to Elastic Beanstalk (PHP 8.5 / Amazon Linux 2023)](workflows/deploy-to-elastic-beanstalk-al2023.md) | How the **Tools** 1.0 app boots on Elastic Beanstalk running `PHP 8.5 on 64bit Amazon Linux 2023/4.13.1 (aarch64)`. | tools/.ebextensions/004_http_to_https.config, tools/.ebextensions/006_mount-s3fs.config, tools/.ebextensions/007_setup_export_cache_folders.config, tools/.ebextensions/008_setup_ldap.config, tools/.ebextensions/009_setup_phpini.config, tools/.ebextensions/020_setup_git_libraries.config, tools/.ebextensions/050_register_instance_to_shared_application_load_balancer.config, tools/ebs/git.json, tools/ebs/setup_export_cache_folders.php, tools/_/app/frameworkindex.php |

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

@@ -6,7 +6,7 @@ project: Tools
 client: shared
 type: architecture
 status: active
-updated: 2026-07-24
+updated: 2026-08-04
 owners: [jcardinal]
 files:
   - tools/index.php
@@ -23,7 +23,10 @@ files:
   - tools/mvc/get.php
   - tools/mvc/_TEMPLATE/get.php
   - tools/docs/ADDING_A_TOOL.md
+  - tools/assets/css/theme.css
+  - tools/assets/js/theme.js
 related:
+  - ./features/theme-light-dark.md
   - ./features/saml-sso-auth.md
   - ./features/persona-gated-navigation.md
   - ./features/developer-tools.md
@@ -47,7 +50,13 @@ double-gated (`[internal] dev_mode` AND `App_Registry::inDevMode()`). `config.*.
 (incl. `config.prod.ini`) is committed with plaintext production secrets that were **publicly
 web-readable** until the front-controller deny blocks added 2026-07-24 (see Known issues);
 rotation of every exposed secret is still owed. Never add more secrets, and keep config files
-denied at the front controller / out of the web root.
+denied at the front controller / out of the web root. New CSS must use `--c-*` tokens from
+`assets/css/theme.css`, never raw colour literals. **`assets/css/style.scss` is DEAD — edit
+`style.css` directly** (the `.css` has drifted ~450 lines ahead; there is no sass binary or
+`package.json`, so recompiling the SCSS would silently revert shipped work).
+`App_FrameworkIndex::setHeaderCode()` is the **only** hook for markup in `<head>`, and it
+**SETS rather than appends** — the theme bootstrap is its sole caller, so a second call
+silently clobbers it.
 
 ## Boot & structure
 
@@ -72,6 +81,14 @@ sibling apps. A fixed left two-column shell: dark left sidebar (`.app-nav`) with
 persona-filtered nav in the middle, pinned footer with the user's name + a ghost "Log out"
 button; content area on the right. **No top header bar** (see Critical rules).
 
+**All colour comes from a semantic token layer, `assets/css/theme.css`**, registered **first**
+in `App_FrameworkIndex_Tools::__construct()` so every other sheet resolves through it. The app
+supports light / dark / auto; the resolved theme is stamped on `<html>` as `data-theme` by an
+inline pre-paint script and the user's choice lives in `localStorage` (`toga-tools-theme`) —
+**not** the DB. The left sidebar and public header stay dark in **both** themes, which is why
+`toga-brandmark-white.png` still works everywhere. Login shows `toga-horizontal-colored.png` in
+light and `toga-horizontal-white.png` in dark. See `features/theme-light-dark.md`.
+
 ## Home route
 
 `/` (`mvc/get.php`) renders a persona-filtered dashboard of available tools (tiles grouped by
@@ -106,6 +123,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-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
+  header dark in both themes. Recorded that `style.scss` is dead and `setHeaderCode()`
+  sets-not-appends. Not committed to `tools` yet (jcardinal)
 - 2026-07-24 — Fixed the config-file web-root exposure: `config.*.ini` was publicly readable via
   the `!-f`-only front controller (`GET /config.production.ini` served it verbatim); added
   `<FilesMatch>` deny blocks referencing the new 1.0 back-end security standard. Softened the

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

@@ -6,8 +6,8 @@ project: Tools
 client: shared
 type: feature
 status: active
-updated: 2026-07-29
-owners: [kyalamarthi]
+updated: 2026-08-04
+owners: [kyalamarthi, jcardinal]
 files:
   - tools/_/app/clickup/sprint.php
   - tools/v2/sprints/tile/index.php
@@ -24,6 +24,7 @@ related:
   - ./persona-gated-navigation.md
   - ./saml-sso-auth.md
   - ./mvc-data-access-patterns.md
+  - ./theme-light-dark.md
   - ../architecture.md
   - ../../../2.0/apps/worker2/features/team-sprint-management.md
 ---
@@ -138,5 +139,15 @@ the React dashboard supersedes it.
   passed by reference", which the E_ALL error handler promotes to a fatal 500. Assign first:
   `$res = App_Database::query(...); buildArrayOfRows($res, false);`.
 
+- **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
+  embedded Power BI report canvas so nothing flashes white while the iframe loads. Themed
+  surfaces there would reintroduce the flash in one theme or the other. Everything else on the
+  page was tokenised for the app-wide theme — see
+  [App-Wide Colour Theme](./theme-light-dark.md).
+
 ## Change history
+- 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)
 - 2026-07-29 — Built `/clickup/react` as a native tools feature (data engine, `/v2/sprints/*` routes, CDN-React TV UI, iframe embed, "Dashboard/Clickup" nav); removed the old `/clickup/dashboard` Power BI nav entry; documented two reusable 1.0 gotchas (queryLogging preflight on Defaults-less DBs, buildArrayOfRows by-ref). (kyalamarthi)

package/knowledge/1.0/apps/tools/features/design-demo-admin.md

@@ -208,5 +208,4 @@ None — internal/shared design-team tool.
 - [Tools Architecture](../architecture.md)
 - [Static Demo Hosting](../../../standalone/apps/forward/features/static-demo-hosting.md)
 - [Deploying Tools to Elastic Beanstalk (AL2023)](../workflows/deploy-to-elastic-beanstalk-al2023.md)
-</content>
-</invoke>
+

package/knowledge/1.0/apps/tools/features/legacy-email-notifier.md

@@ -6,14 +6,15 @@ project: Tools
 client: shared
 type: feature
 status: active
-updated: 2026-08-03
-owners: [bala]
+updated: 2026-08-04
+owners: [bala, jcardinal]
 files:
   - tools/mvc/email-migration/notify/get.php
   - tools/mvc/email-migration/notify/post.php
   - tools/_/app/nav.php
 related:
   - ./mvc-data-access-patterns.md
+  - ./theme-light-dark.md
   - ../workflows/deploy-to-elastic-beanstalk-al2023.md
   - ../architecture.md
 ---
@@ -104,7 +105,19 @@ endpoint that swallows non-fatal diagnostics (returns `true`) for the duration o
 fatals and thrown exceptions still reach the `catch`. The framework mechanism is documented in
 [mvc-data-access-patterns](./mvc-data-access-patterns.md).
 
+## Gotcha — the colour literals in `post.php` are EMAIL HTML; never tokenise them
+
+`post.php` builds the digest **email** body. Email clients cannot resolve CSS custom
+properties, so its colour literals must stay hard-coded — a `var(--c-…)` there renders as no
+colour at all. This is easy to get wrong because the on-screen `get.php` in the same folder
+*was* tokenised for the app-wide theme (see
+[App-Wide Colour Theme](./theme-light-dark.md)). Rule: styles that leave the browser are not
+themed.
+
 ## Change history
+- 2026-08-04 — Tokenised the on-screen `get.php` page styles for the app-wide light/dark theme
+  and recorded that `post.php`'s email-HTML colour literals must stay hard-coded (email clients
+  cannot resolve CSS custom properties). Not committed. (jcardinal)
 - 2026-08-03 — Built the Legacy Email Notifier: multi-file xlsx merge via vendored PhpSpreadsheet,
   legacy-domain filter, `Client_True.Users` local-part resolution with always-domain-swap
   (never-skip), one digest per person per legacy domain, and chunked (25/batch) browser-driven

package/knowledge/1.0/apps/tools/features/talos-pricing-ui.md

@@ -20,6 +20,7 @@ files:
   - tools/mvc/talos/settings/post.php
   - tools/assets/css/style.css
 related:
+  - ./theme-light-dark.md
   - ./persona-gated-navigation.md
   - ./mvc-data-access-patterns.md
   - ../architecture.md
@@ -97,6 +98,20 @@ about cost; cost is driven by tool-call **intensity** via the profile
 - **Voice multipliers (0.25 / 0.50) are UNVALIDATED** — supplied second-hand, never measured,
   and possibly inverted. Flagged in the UI. **Do not quote voice from them.**
 - **`db_team`** is read/write on Contracts and Settings, read-only on the dashboards.
+- **Chart.js colours must come from theme tokens, and a live theme switch needs
+  `chart.update()`.** These pages now read series/axis/tick/gridline colours via
+  `TogaTheme.color('--c-…')` inside a `paint()` registered with `TogaTheme.onChange(paint)`,
+  then call `chart.update()` — `update()` clears Chart.js's resolver cache, so without it a
+  `Chart.defaults` change does not reach charts that already exist. Chart.js otherwise defaults
+  axis/tick text to a dark colour that is unreadable in dark mode. See
+  [App-Wide Colour Theme](./theme-light-dark.md).
+- **These pages keep an explicit `--c-bs-*` token group** because they were authored against
+  Bootstrap's palette (`#0d6efd`, `#6c757d`, `#495057`, `#dc3545`, `#198754`…), which is close
+  to but not the TOGA brand palette — folding them into `--c-primary` visibly restyles them.
+- **Open (dark mode):** the error toast measures ~2.4:1 (white on `--c-danger`) and likely
+  wants a fixed dark fill; the Pricing Dashboard target-band dataset never had a
+  `backgroundColor` (pre-existing authoring slip) so the band shades rather than tints; the
+  three chart pages cannot be statically proven light-identical and still need a browser pass.
 
 ## Security
 - `config.*.ini` carries committed plaintext secrets (team-accepted, see architecture Known
@@ -104,5 +119,10 @@ about cost; cost is driven by tool-call **intensity** via the profile
   (`[api] talos_backend_url` / `talos_backend_key`); no values recorded. Do not add secrets.
 
 ## Change history
+- 2026-08-04 — Tokenised these pages for the new app-wide light/dark theme: page-local styles
+  now use `--c-*` tokens (Talos pages keep their own `--c-bs-*` Bootstrap ramp), and the three
+  Chart.js pages read colours via `TogaTheme.color()` + repaint on `TogaTheme.onChange()` with
+  `chart.update()`. Recorded the dark-mode open items (error-toast contrast, missing
+  target-band `backgroundColor`). Not committed. (jcardinal)
 - 2026-08-04 — Restructured to **Contracts / Pricing Dashboard / Usage / Pricing Settings**. New Contracts pages replace Onboarding with a real PROSPECT/ACTIVE/CHURNED lifecycle (signed contracts churn, never hard-delete — `TalosPricingBands` cascades; post-signature edits append to `TalosContractAmendments`), plus actual-vs-estimate variance, month history chart and one-click apply-recommended-org-fee. Settings replaces the Cost Factors editor with measured rows read-only (`UPDATE ... AND isDerived = 0`). Benchmarks page deleted. Pricing Dashboard rebuilt for sales leadership. Fixed `usage.php clientOptions()` reading an always-empty `TalosClients` (selector rendered empty) → `GET /api/usage/clients` with Team-DB fallback; added cost-intensity panel. Estimator moved to token unit price + workload profiles. Wrote the missing `.app-content:has(.tool--wide)` rule and consolidated Talos CSS into `style.css`. (jcardinal)
 - 2026-06-29 — Built the Talos Pricing UI: nav folder + 4 pages (Onboarding w/ live JS estimate and contract-signing that locks the band schedule into `TalosClients`+`TalosPricingBands` in one txn; read-only Pricing Dashboard + Usage Benchmarks; technical-only Cost Factors editor) and `App_Talos_Estimator` (reads `TalosCostFactors`, derives conversations/user so sales need not enter it). Reads Team DB via new `db_team` connection. Offerings CHAT/VOICE_TO_VOICE/NATURAL_VOICE = 1.0/0.25/0.50 (voice ambiguous, deferred). (jcardinal)

package/knowledge/1.0/apps/tools/features/theme-light-dark.md

@@ -0,0 +1,209 @@
+---
+title: App-Wide Colour Theme (light / dark / auto)
+framework: "1.0"
+repo: tools
+project: Tools
+client: shared
+type: feature
+status: active
+updated: 2026-08-04
+owners: [jcardinal]
+files:
+  - tools/assets/css/theme.css
+  - tools/assets/js/theme.js
+  - tools/_/app/frameworkindex.php
+  - tools/_/app/nav.php
+  - tools/common/header.php
+  - tools/mvc/login/get.php
+  - tools/assets/css/style.css
+  - tools/assets/css/design.css
+  - tools/assets/css/login.css
+  - tools/assets/css/cloudfront-clients.css
+  - tools/assets/css/gchart.css
+  - tools/mvc/talos/usage/get.php
+  - tools/mvc/talos/pricing/get.php
+  - tools/mvc/talos/contracts/get.php
+  - tools/mvc/clickup/dashboard/get.php
+  - tools/mvc/email-migration/notify/post.php
+related:
+  - ../architecture.md
+  - ./persona-gated-navigation.md
+  - ./talos-pricing-ui.md
+  - ./clickup-sprint-dashboard.md
+  - ./legacy-email-notifier.md
+  - ./design-demo-admin.md
+  - ../../../standards/frontend.md
+---
+
+## Summary
+
+A **light / dark / auto** colour theme for the *entire* Tools app, built as a single
+semantic-token layer (`assets/css/theme.css`) rather than per-page edits. The user's choice
+is a three-way switcher rendered next to their name in the left-nav footer, persisted in
+**`localStorage` (`toga-tools-theme`) — deliberately not a DB column**, and applied
+**before first paint** by an inline bootstrap script so there is no flash of the wrong theme.
+
+**Light mode is a hard constraint: pixel-identical to before the change**, verified
+mechanically (see [Verification](#verification-how-to-prove-light-mode-did-not-change)).
+Any new page or stylesheet in this app should consume `--c-*` tokens and will then theme for
+free.
+
+> **Status (2026-08-04): NOT COMMITTED.** All of this lives in the working tree of the local
+> `tools` checkout, which is on `_production` — it needs a feature branch before it lands.
+> Verified **statically only**: resolver diffs, contrast maths, `php -l` on the 14 changed PHP
+> files, `node --check` on `theme.js`. **No browser check and no specialist-reviewer pass has
+> been run.** See [Open items](#open-items).
+
+## How it works
+
+### 1. The token layer — `assets/css/theme.css`
+
+~142 semantic CSS custom properties are declared on `:root` **with the original light
+values**, and overridden in a `:root[data-theme="dark"]` block. It is registered **first** in
+`App_FrameworkIndex_Tools::__construct()` so every other stylesheet resolves through it.
+
+Token groups and their meaning:
+
+| Group | Meaning |
+| --- | --- |
+| `--c-surface*` | fills |
+| `--c-text*` | foregrounds |
+| `--c-border*` | borders |
+| `--c-primary*` | brand (`-tNN` = alpha tint) |
+| `--c-nav-*` | left nav / public header — **dark in BOTH themes** |
+| `--c-on-accent`, `--c-on-dark-tNN` | white in BOTH themes; content sitting on a permanently dark/coloured fill |
+| `--c-slate-*`, `--c-indigo-*`, `--c-green-*`, `--c-red-*` | secondary ramp used by `design.css` + `cloudfront-clients.css` |
+| `--c-bs-*` | legacy Bootstrap ramp, Talos pages only (see gotchas) |
+| `--c-code-bg`, `--c-code-fg` | fixed dark code slab (not themed) |
+
+`color-scheme` is itself tokenised as `--c-color-scheme` so native scrollbars and form
+controls follow the theme. Note `style.css` previously hard-coded `color-scheme: light` on
+`html, body`, which beat the `:root` token — that had to be removed.
+
+### 2. Pre-paint application (no flash)
+
+`App_FrameworkIndex_Tools::themeBootstrapScript()` returns a tiny inline `<script>` injected
+with `App_FrameworkIndex::setHeaderCode()`; `library` echoes it inside `<head>` **after** the
+CSS/JS includes. It reads `localStorage` and stamps `data-theme` + `data-theme-pref` onto
+`<html>` before the first paint. **An external JS file cannot do this** — it runs too late and
+you get a flash of the wrong theme.
+
+### 3. Runtime API — `assets/js/theme.js` (`window.TogaTheme`)
+
+- `get()` → `'light' | 'dark'` (resolved theme)
+- `getPreference()` → `'light' | 'dark' | 'system'`
+- `set(pref)` — persists + applies
+- `onChange(fn)` — **fires immediately with the current theme**, then on every change, so a
+  caller has one code path for both "colour yourself now" and "recolour"
+- `color('--token')` — read a themed colour out of CSS for JS-driven visuals
+
+Persistence: `localStorage` key **`toga-tools-theme`**, values `light|dark|system`. Every
+access is `try`/`catch`ed — Safari private mode *throws* rather than returning `null`.
+`system` follows the OS live via a `matchMedia('(prefers-color-scheme: dark)')` change
+listener (with the `addListener` fallback for Safari <14), and a `storage` event listener keeps
+multiple open tabs in agreement.
+
+### 4. The switcher (server-rendered)
+
+Rendered in `common/header.php` inside `.app-nav-footer` — next to the signed-in user's name,
+above **Log out** — as a `role="radiogroup"` of three buttons carrying
+`data-theme-choice="light|dark|system"` (labelled **Light / Dark / Auto**). `theme.js` manages
+`aria-checked` + a roving `tabindex` and supports arrow keys. Icons come from a new
+`App_Nav::themeIcon($theme)` that returns **inline SVG** from a fixed 3-key allowlist — inline
+so the glyph inherits `currentColor`.
+
+### 5. Login-page wordmark
+
+Two `<img>` wordmarks are in the markup and CSS shows one per theme
+(`.login-logo--light` / `.login-logo--dark`, keyed off `:root[data-theme="dark"]`):
+`toga-horizontal-colored.png` in light, `toga-horizontal-white.png` in dark.
+
+Chosen over swapping `src` in JS or using `<picture>`: CSS honours an **explicit** Light/Dark
+choice, whereas a `<picture>` media query only sees `prefers-color-scheme` and would ignore a
+forced override — and CSS cannot flash the wrong logo. Both PNGs are 3610×700 so there is no
+reflow. Tradeoff: the browser downloads both (~49 KB extra).
+
+### 6. Chart.js pages
+
+`talos/usage`, `talos/pricing` and `talos/contracts` read series/axis/tick/gridline colours
+from tokens via `TogaTheme.color()` inside a `paint()` function registered with
+`TogaTheme.onChange(paint)`, followed by `chart.update()`. **`chart.update()` is required** —
+it clears Chart.js's resolver cache so `Chart.defaults` changes take effect on charts that
+already exist. Without this, Chart.js defaults axis/tick text to a dark colour that is
+unreadable on a dark background.
+
+## Decisions
+
+- **Left nav and public header stay dark in BOTH themes** (deepened for dark). Preserves the
+  app's identity, guarantees zero light-mode regression there, and keeps the existing white
+  brandmark PNG usable in both themes.
+- **Preference is browser-local (`localStorage`), not a DB column** — explicit developer
+  requirement.
+- **Light mode must be pixel-identical**, proven mechanically rather than by eye.
+- **`assets/css/style.scss` left untouched** — neither revived nor deleted (out of scope; that
+  is already the status quo — see gotcha below).
+
+## Verification (how to prove light mode did not change)
+
+1. **Resolver diff.** Resolve every `var(--c-*)` back through the `:root` (light) block and
+   diff the result against the pre-change file. Identical output = light mode unchanged.
+2. **Dark-coverage assert.** Every `:root` token must have a `[data-theme="dark"]` override
+   unless it is intentionally fixed.
+3. **Per-file colour multiset vs. `git HEAD`.** Compare the *multiset* of resolved colour
+   values per file, not a line-by-line diff — an index/line-based diff is useless once lines
+   are inserted, whereas a multiset comparison is immune to line-number shifts.
+
+## Gotchas
+
+- **`assets/css/style.scss` is DEAD in this repo — edit `style.css` directly.** Many recent
+  commits touch the `.css` while the `.scss` was last touched in an old ticket; the `.css` has
+  drifted ~450 lines ahead. There is no sass binary and no `package.json`. "Helpfully"
+  recompiling the SCSS would **silently revert a large amount of shipped work**.
+- **`App_FrameworkIndex::setHeaderCode()` is the only hook for injecting markup into `<head>`
+  in 1.0** (library echoes `$this->headerCode` inside `<head>` after the CSS/JS includes). It
+  **SETS rather than appends**, and before this feature it was unused anywhere in tools — so a
+  **second caller silently clobbers the first**. If another feature needs head markup, refactor
+  to compose both strings; do not add a second `setHeaderCode()` call.
+- **A colour literal used as both a foreground and a background must be split into two
+  tokens**, or dark mode inverts it the wrong way. Real cases in tools: `#10113A` (body text
+  *and* nav/public-header background), `#20242c` (text-strong *and* a dark chip fill), `#999`
+  (text grey *and* a badge fill), `#eef0f4` (border *and* badge fill), `#0f172a` (design.css
+  `--d-ink` text *and* the code-block background). Detect these **mechanically** — collect, per
+  candidate token, the set of CSS properties it appears with (background vs. colour/border).
+  Do not eyeball it.
+- **A brand colour needs TWO tokens in a dark theme.** `--c-primary` (text/borders on a panel)
+  is **lightened** in dark for legibility; `--c-primary-fill` (a fill behind white text) is
+  kept **dark enough** in dark mode to preserve contrast. The roles pull in opposite
+  directions — one token makes white-on-brand buttons fail contrast.
+- **The Talos admin pages keep their own `--c-bs-*` group.** They were authored against
+  Bootstrap's palette (`#0d6efd`, `#6c757d`, `#495057`, `#dc3545`, `#198754`…), which is close
+  to but **not** the TOGA brand palette; folding them into `--c-primary` visibly restyles those
+  pages. Only map a literal onto a token whose light value is **identical**.
+- **`mvc/email-migration/notify/post.php` generates EMAIL HTML — its colour literals must stay
+  hard-coded.** Email clients cannot resolve CSS custom properties. It is the same file family
+  as the on-screen page, so it is easy to tokenise by mistake.
+- **`mvc/clickup/dashboard/get.php` keeps ~6 fixed literals on purpose.** Its card/frame colour
+  `#0b1020` matches the embedded Power BI report canvas so nothing flashes white while the
+  iframe loads. Do not theme those.
+
+## Open items
+
+- The three Chart.js pages **cannot** be statically proven light-identical — their colours are
+  now generated at runtime. Needs a browser pass.
+- The Talos error toast measures ~2.4:1 in dark (white text on `--c-danger`) and probably wants
+  a fixed dark fill.
+- `talos/pricing`'s target-band dataset never had a `backgroundColor` (a pre-existing authoring
+  slip), so its band renders as a faint darkening rather than a green tint.
+- A few Talos overlay shadows shifted from black-based to slate-based (imperceptible but real),
+  and 7 imperceptible colour substitutions were accepted on Talos pages (largest:
+  `#f8f9fa` → `#f8f9fb`).
+
+## Change history
+- 2026-08-04 — Built the app-wide light/dark/auto theme: `assets/css/theme.css` (~142 `--c-*`
+  tokens on `:root` + a `[data-theme="dark"]` override, registered first in
+  `App_FrameworkIndex_Tools`), `assets/js/theme.js` (`window.TogaTheme`), a pre-paint inline
+  bootstrap via `setHeaderCode()`, a Light/Dark/Auto radiogroup in the nav footer
+  (`App_Nav::themeIcon()`), per-theme login wordmarks, and token-driven Chart.js repaint on the
+  three Talos chart pages. Preference in `localStorage` (`toga-tools-theme`), no DB column; nav
+  + public header stay dark in both themes; light mode proven unchanged by resolver diff.
+  **Not committed — working tree on `_production`, no browser verification yet.** (jcardinal)

package/knowledge/1.0/standards/frontend.md

@@ -5,12 +5,13 @@ project: Library
 client: shared
 type: standard
 status: active
-updated: 2026-07-30
+updated: 2026-08-04
 owners: [jcardinal]
 files: []
 related:
   - ./backend-php.md
   - ./framework-rules.md
+  - ../apps/tools/features/theme-light-dark.md
   - ../apps/tools/features/design-demo-admin.md
   - ../apps/tools/features/talos-kb-documents-admin.md
 ---
@@ -66,10 +67,48 @@ Each round trip adds a level. Equality comparisons then fail too, because a fres
 - `tools/_/app/design/github.php` — `App_Design_Github::decodeEntities()` applied to tab
   names and project titles on both the storage-read and request-read sides.
 
+## Tokenising an existing stylesheet for a second theme
+
+When retrofitting light/dark onto a legacy sheet, four rules turn a guessing game into a
+mechanical exercise.
+
+**1. Split any literal used as both a foreground and a background into two tokens.** A single
+token inverts the wrong way in the second theme. Detect these **mechanically** — collect, per
+candidate token, the set of CSS properties it appears with (`background*` vs.
+`color`/`border*`) — do not eyeball it. Real cases in `tools`: `#10113A` (body text *and* nav
+background), `#20242c`, `#999`, `#eef0f4`, `#0f172a`.
+
+**2. A brand colour needs TWO tokens.** `--c-primary` (text/borders on a panel) must be
+**lightened** in dark for legibility; `--c-primary-fill` (a fill behind white text) must stay
+**dark enough** in dark to preserve contrast. The roles pull in opposite directions; one token
+makes white-on-brand buttons fail contrast.
+
+**3. Only map a literal onto a token whose light value is IDENTICAL.** Measure perceptual
+distance before accepting a "close enough" substitution — a near-match silently restyles the
+page. Legacy pages authored against a *different* palette (the Talos admin pages use
+Bootstrap's `#0d6efd`/`#6c757d`/`#dc3545`/`#198754`) keep their own token group with their
+exact original values rather than being folded into the brand tokens.
+
+**4. Prove the original theme is unchanged, mechanically.** (a) Resolve every `var(--…)` back
+through the `:root` block and diff against the pre-change file; (b) assert every `:root` token
+has a second-theme override unless intentionally fixed; (c) compare the per-file **multiset**
+of resolved colour values against `git HEAD` — a line-index diff is useless once lines are
+inserted, a multiset comparison is immune to line shifts.
+
+Two things are **never** tokenised: HTML destined for an **email** (email clients cannot
+resolve custom properties) and colours deliberately matched to third-party embedded content
+(e.g. an iframe's canvas colour, to prevent a white flash on load).
+
+Reference implementation:
+[tools App-Wide Colour Theme](../apps/tools/features/theme-light-dark.md).
+
 ## Change history
 
+- 2026-08-04 — Added "Tokenising an existing stylesheet for a second theme": split
+  dual-role colour literals, two tokens per brand colour, identical-value-only substitutions,
+  and the mechanical proof that the original theme is unchanged; plus the never-tokenise cases
+  (email HTML, colours matched to third-party embeds). Drawn from the `tools` light/dark
+  build. (jcardinal)
 - 2026-07-30 — Created. Establishes the escape-once/plain-text-storage invariant after a
   second independent occurrence in `tools` (Design Demo Admin, following the Talos
   vocabulary tool). (jcardinal)
-</content>
-</invoke>

package/knowledge/2.0/apps/_underscore/features/error-reporting-issue-event.md

@@ -364,6 +364,18 @@ in `_underscore` and `library` in the **same** release, and the `/errors` consol
   `dbchanges2/Logs_Client/2026-08-01a - Drop Error table.sql`. Do not reintroduce it.
 - **Shared-schema migration collision.** Because these tables live in the *shared* Core Logs
   DB, only **one** migration may `CREATE` them; later migrations only `ALTER`.
+- **The `dbchanges2/Logs/` migration files LAG the deployed schema — read the live cluster, not the
+  migrations.** `dbchanges2/Logs/2026-07-30a - Error reporting Issues and Events.sql` does **not**
+  describe the live `Logs.Issue`: notably the identity column is **`issueKey` (varchar 128)**, not
+  `code`. Live columns include `reference`, `dtLastOccurred`, `isManaged`, `urgency`,
+  `minimumUrgency`, `consecutiveQuietWindows`, `subject`, `errorMessage`, `occurrences`,
+  `totalOccurrences`, `recurrenceCount`, `dtLastNotified`, `notificationCount`, `dtAcknowledged`,
+  `dtMutedUntil`, `createsClickupTask`, `clickupPriority`, `clickupAssigneeId`. Query
+  `information_schema` (or `SHOW TABLES` / `SHOW COLUMNS`) against the live Logs cluster **before**
+  writing any SQL against this feature — reading the migrations instead produced confidently wrong
+  conclusions twice on 2026-08-04. Same trap for the **singular** table names
+  (`Issue`/`Event`/`IssueFingerprint`/`IssueAreaOwner`/`IssueClickupTask`/`IssueEmailAddress`,
+  renamed by `2026-08-01a` and confirmed applied in prod).
 - **Pre-existing committed secrets in this area (not fixed — out of scope, report only).**
   A ClickUp API token at `_underscore/Component/Api/Clickup/Clickup.php:5`; SES SMTP
   credentials at `_underscore/Email.php:11-12`; a named individual's Sentry personal access
@@ -418,6 +430,12 @@ clientUserId). **Neither was built.** As built instead:
 
 ## Change history
 
+- 2026-08-04 — **Correction/diagnostic:** recorded that the `dbchanges2/Logs/` migration files lag
+  the deployed schema — `2026-07-30a` describes a `code` identity column, but live `Logs.Issue` is
+  keyed on **`issueKey` (varchar 128)** — and listed the live column set. Query
+  `information_schema` against the live Logs cluster before writing SQL here; trusting the
+  migrations (and forgetting the applied singular rename) produced two confidently wrong
+  conclusions in one session. No code change. (dfranks)
 - 2026-08-04 (later, **uncommitted/undeployed** at time of writing) — **Reference encoding reworked
   to base 32** over `'0123456789ACDEFGHJKMNPQRSTUVWXYZ'` (all digits kept; `O`/`I`/`L`/`B` dropped
   as impersonators of `0`/`1`/`1`/`8`), replacing the base-26 decimal-counter+letter scheme, with

package/knowledge/2.0/apps/worker2/features/error-escalation-cron.md

@@ -7,7 +7,7 @@ client: shared
 type: feature
 status: active
 updated: 2026-08-04
-owners: ["jcardinal"]
+owners: ["jcardinal", "dfranks"]
 files:
   - worker2/Worker/Infrastructure/Errors.php
   - worker2/Worker/Notification/Email.php
@@ -28,6 +28,7 @@ related:
   - ./clickup-project-routing.md
   - ./notification-email.md
   - ./notification-email-template.md
+  - ../../../clients/compass-usa/features/mits-sales-order-transmission-alerting.md
 ---
 
 ## Summary
@@ -263,6 +264,22 @@ this controller needs the same treatment.**
   issue gets a **neutral** subject rather than another client's raw error text.
 - **`IssueEmailAddress.clientId = 0` means "all clients"** and requires an explicit
   confirmation flag in the Tools console; list views render it as **"ALL CLIENTS"**.
+- **A recipient scoped to a specific `clientId` delivers NOTHING for occurrences recorded without
+  client attribution.** `loadRecentClientIds()` maps an occurrence whose `clientId` is NULL to
+  **`0`**, and `resolveRecipientsForClient()` resolves scope `0` **plus** the erroring client. So
+  the rule is: scope to **`0`** when the `issueKey` is raised from a **single client-specific code
+  path** (a Compass-only cron, say); **never** scope to `0` for an `issueKey` raised from shared
+  code, which would leak one client's alerts to another's recipients.
+- **Configuring a recipient is never retroactive.** `shouldNotify()` notifies on first occurrence
+  (`notificationCount` 0), on escalation, or when the backed-off reminder interval has elapsed —
+  and returns **false when the current window has zero events**. The first email therefore lands on
+  the **next live occurrence**, not on the backlog. Do not read silence right after a config change
+  as a failure.
+- **Adding a business recipient is purely additive — it cannot switch ClickUp ticketing off.**
+  Routing is **both**, not either: `if ($recipients !== null)` emails the business recipients and
+  `if ($issue->createsClickupTask)` tickets the dev team, evaluated **independently**. The in-code
+  comment marking this records the earlier `elseif` form, where adding one recipient silently
+  disabled an issue's dev-team ticket.
 - **The ClickUp webhook has no HMAC signature verification** (pre-existing, unfixed). A forged
   POST can mark issues acknowledged — freezing the neglect axis — or resolve episodes. That is
   alert suppression against the error-reporting system itself. Fix before relying on this
@@ -273,6 +290,15 @@ this controller needs the same treatment.**
 
 ## Change history
 
+- 2026-08-04 (verified against `origin/_production` + the prod Logs cluster) — Recorded the
+  **recipient-routing semantics** a developer needs before configuring a business alert: routing is
+  **both** business email and dev-team ClickUp, evaluated independently (adding a recipient is
+  purely additive); `IssueEmailAddress.clientId` scoping means a client-scoped row delivers nothing
+  for occurrences with NULL `clientId` (mapped to `0`), so single-client `issueKey`s scope to `0`
+  and shared-code `issueKey`s never do; and `shouldNotify()` makes configuration
+  **non-retroactive** — the first email lands on the next live occurrence. Also noted that prod
+  `Logs.IssueEmailAddress` was still empty, making Compass's MITS rejection the platform's first
+  business-routed issue. No code change. (dfranks)
 - 2026-08-04 (later, **uncommitted/undeployed** at time of writing) — **Fixed: escalation email had
   never been sent, ever**, for two independent reasons. (A) `processTechnicalIssue()` returned early
   when the ClickUp task would read identically, and that return sat *above* the `if ($shouldNotify)`

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) — 2 doc(s) → [1.0/apps/toga/INDEX.md](1.0/apps/toga/INDEX.md)
-- **tools** (Tools) — 13 doc(s) → [1.0/apps/tools/INDEX.md](1.0/apps/tools/INDEX.md)
+- **tools** (Tools) — 14 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) — 4 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) — 3 doc(s) → [standalone/apps/claude/INDEX.md](standalone/apps/claude/INDEX.md)
+- **claude** (Claude Harness) — 4 doc(s) → [standalone/apps/claude/INDEX.md](standalone/apps/claude/INDEX.md)
 
 ## Clients
 

package/knowledge/clients/compass-usa/INDEX.md

@@ -8,6 +8,7 @@
 | [Compass: Item-Fulfillment TableViews (for-sales-order-items & for-sales-orders, tracking via bridge)](features/item-fulfillment-tracking-tableview.md) | 2.0 | Two sibling Compass TableViews in `Client_Compass` display fulfilled items in toga2-supply, both driven by `TableViews` / `TableViewJoins` / `TableViewFields` c | dbchanges2/Client_Compass/2026-06-10 - ItemFulfillmentsForSalesOrderItemsTableView.sql, dbchanges2/Client_Compass/2026-06-11 - ItemFulfillmentsForSalesOrdersTableView.sql, dbchanges2/Client_Compass/2026-06-15a - FixItemFulfillmentTrackingNumberJoins.sql, dbchanges2/Client/2026-07-15a - ExcludeFeeItemsFromItemFulfillmentsForSalesOrdersView.sql |
 | [Compass MITS PO → SO Item Linking](features/mits-po-to-so-item-linking.md) | 2.0 | MITS sends Compass inbound Purchase Orders (`POST /v2/purchase-orders`) against a Sales Order (`mitsSalesOrder`). | _underscore/Model/Compass/PurchaseOrder.php, worker/crons/toga2/compass/workflow/3a_import_office_depot_purchase_orders.php |
 | [Compass MITS PO Transmission to Vendors](features/mits-po-transmission-to-vendors.md) | 2.0 | The 1.0 worker cron `2_transmit_mits_purchase_orders_to_vendors.php` transmits Compass PurchaseOrders to their vendors (Office Depot, Strategic Systems, Compass | worker/crons/toga2/compass/workflow/2_transmit_mits_purchase_orders_to_vendors.php, worker/crons/toga2/compasscanada/workflow/2_transmit_mits_purchase_orders_to_vendors.php, library/app/client/compass.php |
+| [Compass MITS Sales-Order Transmission — Rejection Alerting (Issue/Event, not email-in-cron)](features/mits-sales-order-transmission-alerting.md) | 2.0 | When MITS **rejects** a Compass sales order transmitted by the 1.0 cron `1_transmit_compass_sales_orders_to_mits.php`, the alert is no longer an email built ins | worker/crons/toga2/compass/workflow/1_transmit_compass_sales_orders_to_mits.php, worker2/Worker/Infrastructure/Errors.php, _underscore/Model/Core/Logs/Issue.php, _underscore/Model/Core/Logs/IssueEmailAddress.php, dbchanges2/Logs/2026-08-04a - MITS rejection business recipients.sql |
 | [Compass MR/MA Order Auto-Approval & Status Gate](features/mr-ma-order-approval-and-status.md) | 2.0 | Compass **MR** and **MA** sales orders are system-generated from the MITS / Office Depot EDI pipeline (they do not originate as user-entered SA orders) and must | _underscore/Model/Compass/SalesOrder.php, _underscore/Model/Compass/PurchaseOrder.php, worker/crons/toga2/compass/workflow/3a_import_office_depot_purchase_orders.php |
 | [Compass USA](profile.md) | 2.0 | Compass USA is a TOGA client running a multi-tier supply-chain commerce operation. |  |
 | [Compass Cross-Kit Bundle Corruption — Detection & Repair](workflows/cross-kit-bundle-corruption.md) | 2.0 | A frontend regression in `toga2-commerce`'s edit-order bundle submission mis-attributed bundle (kit) line items and **fees/warranties** to the **wrong kit**, pe | src/api/syncSalesOrderItemsFromLocalStorageCartToApi.ts |

package/knowledge/clients/compass-usa/features/mits-sales-order-transmission-alerting.md

@@ -0,0 +1,89 @@
+---
+title: Compass MITS Sales-Order Transmission — Rejection Alerting (Issue/Event, not email-in-cron)
+framework: "2.0"
+project: _Underscore
+client: compass-usa
+type: client-feature
+status: active
+updated: 2026-08-04
+owners: ["dfranks"]
+files:
+  - worker/crons/toga2/compass/workflow/1_transmit_compass_sales_orders_to_mits.php
+  - worker2/Worker/Infrastructure/Errors.php
+  - _underscore/Model/Core/Logs/Issue.php
+  - _underscore/Model/Core/Logs/IssueEmailAddress.php
+  - dbchanges2/Logs/2026-08-04a - MITS rejection business recipients.sql
+related:
+  - mits-po-transmission-to-vendors.md
+  - ../../../2.0/apps/worker2/features/error-escalation-cron.md
+  - ../../../2.0/apps/_underscore/features/error-reporting-issue-event.md
+  - ../../../1.0/apps/library/features/error-capture-1-0.md
+---
+
+## Summary
+
+When MITS **rejects** a Compass sales order transmitted by the 1.0 cron
+`1_transmit_compass_sales_orders_to_mits.php`, the alert is no longer an email built inside the
+cron. It is a **business exception** raised into the shared Logs Issue/Event pipeline, and its
+recipients are **rows in `Logs.IssueEmailAddress`**.
+
+**Consequence for anyone handed a ticket like "add <person> to the MITS error emails": there is
+no PHP to change.** It is a one-row data change delivered as a `dbchanges2/Logs/` migration.
+
+## How it works
+
+- The cron raises
+  `throw new App_Exception_Business('COMPASS_SALES_ORDER_MITS_TRANSMIT_REJECTED', …, URGENCY_HIGH)`
+  on a MITS rejection. (Before 2026-08-03 this block was a hardcoded `new App_Email_Agilant()`
+  with `addTo('devteam@togatech.com')`.)
+- Capture creates/dedupes a `Logs.Issue` keyed on the `issueKey`, and the worker2
+  `Infrastructure/Errors/Escalate` cron does all outbound notification — business email to the
+  configured recipients **and**, independently, the dev-team ClickUp task. See
+  [error-escalation-cron](../../../2.0/apps/worker2/features/error-escalation-cron.md).
+- Recipients live in `Logs.IssueEmailAddress` (FK `issueId` → `Logs.Issue`), scoped by
+  `clientId` (`0` = all clients).
+
+### Adding a recipient (the correct pattern)
+
+Write a `dbchanges2/Logs/YYYY-MM-DD<letter>` migration that:
+
+1. **Looks the issue up by `issueKey`**, never by its `id`. The id is assigned on the issue's
+   **first occurrence** and is therefore not stable across environments.
+2. Uses **`clientId = 0`**. This `issueKey` is raised from a Compass-only code path, and an
+   occurrence recorded without client attribution resolves against scope `0` only — a row scoped
+   to the Compass `clientId` can deliver nothing. (Never use `0` for an `issueKey` raised from
+   shared code — that is a cross-tenant leak.)
+3. Is **idempotent** via `INSERT … WHERE NOT EXISTS`, mirroring the unique key
+   `uq_issue_client_address_type`.
+
+Configuration is **never retroactive**: `shouldNotify()` fires on the first occurrence, on
+escalation, or when the backed-off reminder interval elapses, and returns false for a window with
+zero events. The first email lands on the **next live rejection**, not on existing history.
+
+## Gotchas / known issues
+
+- **Do not "modernize" this alert back into the cron.** Migrating it to
+  `_Model_Client_EmailTemplate::send` (or any in-cron email) reverts the move to the Issue/Event
+  pipeline and removes the recipient configuration surface entirely.
+- **Never re-introduce the payload dump into the alert.** The original email included the
+  transmission payload, which carries ship-to addressee, attention line, street address and phone
+  number. The Issue message is stored in a table **shared across every client**, displayed to
+  internal staff in the Tools `/errors` console, pushed to ClickUp, and emailed — so the payload
+  was deliberately removed. Alerts here name the order, not the person.
+- **The MITS cron holds its API credentials inline in the file.** Treat that file as
+  secret-bearing when copying snippets anywhere (tickets, PR bodies, knowledge docs).
+- **Adding a recipient does not turn ClickUp ticketing off.** Routing is both-and, not
+  either-or — see the escalation-cron doc for the `elseif` bug this used to be.
+- As of 2026-08-04 prod `Logs.IssueEmailAddress` is empty, so this is the **first business-routed
+  issue on the platform**: `processBusinessIssue()` will execute in production for the first time
+  when this issue next fires. Watch that run rather than assuming it works.
+
+## Change history
+- 2026-08-04 — Documented that MITS rejection alerting moved (worker `5521854b`, 2026-08-03) from a
+  hardcoded in-cron `App_Email_Agilant` to `App_Exception_Business` +
+  `Logs.IssueEmailAddress` recipients, so adding an alert recipient is a data change, not a code
+  change. Recorded the deliberate removal of the PII-bearing payload dump from the alert, the
+  look-up-by-`issueKey` / `clientId = 0` / `NOT EXISTS` migration pattern, and that recipient
+  configuration only takes effect on the next live occurrence. (dfranks)
+</content>
+</invoke>

package/knowledge/clients/compass-usa/profile.md

@@ -16,10 +16,11 @@ project: _Underscore
 client: compass-usa
 type: profile
 status: active
-updated: 2026-07-16
-owners: [jcardinal, bala, tcox, apeterson]
+updated: 2026-08-04
+owners: [jcardinal, bala, tcox, apeterson, dfranks]
 files: []
 related:
+  - features/mits-sales-order-transmission-alerting.md
   - features/asn-to-item-fulfillment.md
   - features/cost-centers.md
   - features/approval-decision-flow.md
@@ -75,6 +76,10 @@ separate, related client (see its own profile).
   `worker/crons/toga2/compass/workflow/3b_import_strategic_systems_advance_shipping_notices.php`.
 
 ## Key features (this client)
+- [MITS Sales-Order Transmission — Rejection Alerting](features/mits-sales-order-transmission-alerting.md)
+  — MITS rejection alerts are `App_Exception_Business` Issues with recipients in
+  `Logs.IssueEmailAddress`, **not** an email in the cron: adding an alert recipient is a
+  `dbchanges2/Logs/` data change with no PHP.
 - [Compass ASN → ItemFulfillment Auto-Creation](features/asn-to-item-fulfillment.md) — the
   `_Model_Compass_AdvanceShippingNotice::postPost` handler.
 - [Cost Centers (Unit Locations, numeric-only)](features/cost-centers.md) — what a Compass

package/knowledge/standalone/apps/claude/INDEX.md

@@ -5,3 +5,4 @@
 | [Harness Distribution — How a knowledge.js Fix Reaches Teammates](workflows/harness-distribution.md) | There are **two copies** of `knowledge.js` on a developer's machine, and the skills use only one of them. | claude/scripts/install.js, claude/knowledge.js |
 | [Knowledge Base Publish / Push Pipeline](workflows/knowledge-publish-pipeline.md) | How `/capture` and `/session-save` get knowledge docs from your working tree into `agilantsolutions/claude` on `_main`. | claude/knowledge.js |
 | [MCP Tool Usage — "Talos" Means the Internal Knowledge Base, and Run Your Own SELECTs](workflows/mcp-tool-usage.md) | Two MCP connections are available in every session, and **Claude is expected to reach for them on its own judgement — nobody should have to say the word "MCP".* | claude/.claude/skills/kickoff/SKILL.md, claude/.claude/skills/capture/SKILL.md |
+| [Ticket-Branch Creation Safety — How /work-ticket Armed Pushes to Production Branches](workflows/ticket-branch-creation-safety.md) | For roughly a month, `/work-ticket` created ticket branches whose **git upstream was the production branch**. | claude/skills/work-ticket/SKILL.md |

package/knowledge/standalone/apps/claude/workflows/ticket-branch-creation-safety.md

@@ -0,0 +1,91 @@
+---
+title: Ticket-Branch Creation Safety — How /work-ticket Armed Pushes to Production Branches
+framework: "standalone"
+repo: claude
+project: Claude Harness
+client: shared
+type: workflow
+status: active
+updated: 2026-08-04
+owners: ["dfranks"]
+files:
+  - claude/skills/work-ticket/SKILL.md
+related:
+  - ./harness-distribution.md
+  - ../../../2.0/apps/worker2/workflows/ticket-to-pseudocode-planning.md
+---
+
+## Summary
+
+For roughly a month, `/work-ticket` created ticket branches whose **git upstream was the
+production branch**. Claude's own pushes were unaffected, but a developer using VS Code's
+**Commit + Sync** mid-session pushed ticket code straight to `_main`/`_production` — no PR, no
+review. Two such pushes landed in two days before it was found.
+
+The mechanism is generic git behavior, so it is worth understanding beyond this one skill.
+
+## Root cause
+
+Branch creation was `git checkout -b TRUE-XXXX "origin/$DEFAULT"`. Git's
+**`branch.autoSetupMerge` defaults to `true`**, so branching from a *remote-tracking ref* adopts
+that ref as the new branch's **upstream**. The ticket branch therefore tracked
+`origin/_main` / `origin/_production` until the skill's later `git push -u` re-pointed it.
+
+**Trigger asymmetry is why it hid.** Claude pushes with `git push -u origin <TICKET>` — an
+explicit refspec, which ignores the upstream and was always safe. VS Code's Commit + Sync resolves
+the destination **from the upstream**, so any developer commit made before the skill's first push
+went to the production branch.
+
+**A safety fix created the exposure.** Commit `6d155f7` (2026-07-09) moved branch creation from
+*after* implementation to *before* any code is written — itself a genuine fix, because a stale
+local `_production` 12 commits behind nearly reverted upstream work. But it turned a seconds-long
+armed window into the **entire implementation phase**. Correctness fixes can lengthen an existing
+window; check what else depends on the timing you moved.
+
+## The fixes
+
+1. **Skill:** branch creation uses **`--no-track`** *and* publishes the empty branch immediately
+   (`git push -u origin TRUE-XXXX`), so the branch has a correct upstream before any code exists.
+   The later push is a plain `git push origin <TICKET>`.
+2. **Global git config:** `branch.autoSetupMerge=simple` (a checkout can no longer adopt a
+   production upstream, even outside the skill) plus `push.autoSetupRemote=true`.
+3. **`pre-push` hook** in each app repo rejecting
+   `refs/heads/(_main|_production|_beta|_alpha|master)`, override `ALLOW_PROD_PUSH=1`. This also
+   catches Claude, because Claude shells out to real `git`.
+4. **Deny rules** in `.claude/settings.json`.
+5. Existing branches still tracking a production branch were **disarmed** individually.
+
+`rework-ticket` was never affected — it checks out an existing remote branch.
+
+## Recovery: getting an unreviewed commit off an unprotected default branch
+
+Do **not** force-push. Instead:
+
+1. **Revert via PR** on the default branch.
+2. **Rebuild the ticket branch as a NEW commit** on the post-revert base.
+
+> **The revert-remerge trap:** if you keep the original commit and merge that branch later, the
+> original commit is already an **ancestor** of the default branch, so the merge is a silent no-op
+> and the change **never comes back**. The revert wins and nothing warns you.
+
+## Gotchas / known issues
+
+- **Everything installed here is local and does not survive a fresh clone.** Hooks and git config
+  are per-machine; a teammate or a new laptop is unprotected until they redo it.
+- **Standing exposure (not fixed):** `dbchanges2/_main`, `worker/_production`,
+  `worker2/_production` and `api2/_production` have **no branch protection and no rulesets**.
+  Server-side protection is the only durable fix and needs an admin GitHub account.
+- **Diagnosing this class of incident:** `git reflog` on the remote-tracking branch shows
+  `update by push` entries — that is how both incidents were confirmed and how the other four
+  repos were cleared. Pre-existing `_beta` pushes are normal manual practice; check dates before
+  calling something an incident.
+- Auditing "did this ever happen elsewhere?" requires sweeping **every** repo the skill touches,
+  not just the one that surfaced the bug.
+
+## Change history
+- 2026-08-04 — Documented the `branch.autoSetupMerge` root cause, the Claude-vs-VS-Code trigger
+  asymmetry that hid it for a month, and the fixes (`--no-track` + immediate branch publish,
+  global `autoSetupMerge=simple`, per-repo `pre-push` hook, settings deny rules). Recorded the
+  revert-then-rebuild recovery pattern and its revert-remerge no-op trap, plus the standing lack
+  of server-side branch protection on four app repos. (dfranks)
+</content>

package/package.json

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