toga-ai 1.0.769 → 1.0.770

package/knowledge/2.0/standards/frontend.md

@@ -709,17 +709,21 @@ non-deterministic, and **can write real data**. Two consequences worth internali
 
 **MUST — every new test is SEEN TO FAIL before it is allowed to pass.** A test written straight to
 green has proven nothing; on a stubbed harness a test can easily pass for the wrong reason. Break
-the thing under test on purpose, watch the test go red, then restore it. Two worked examples from
-the reference implementation:
-
-1. **Intercept matching.** Revert one intercept from `{ pathname: apiPath("domains") }` to the URL
-   glob `**/v2/domains*` and re-run: the fall-through guard **must** fail and print the URL.
-   (Real query strings contain a slash — `…SelfDomains.domain:like:http://compass%2Etogasupply)…` —
-   and minimatch's `*` does not cross `/`, so the glob silently never matches and the catch-all
-   answers instead.) If the suite stays green, the guard is not wired.
-2. **Config drift canary.** Delete the `isBloxLinked` branch from the component-test Vite config
-   and re-run the canary spec: it **must** go red with "Invalid hook call" or "No QueryClient set"
-   (a second copy of React / react-query). If it stays green, the canary is not asserting anything.
+the thing under test on purpose, watch the test go red, then restore it. The two mutations actually
+run against the reference implementation on 2026-09-03, both of which produced the expected red:
+
+1. **Break the config the test reads.** The tenant registry was edited to claim `QUAD` is granted
+   `transfer-orders` while its surface fixture still withheld it. The nav test failed with
+   `Expected to find element: a[href="/transfer-orders"], but never found it.` — proving the test
+   reads the real resolved nav, not the registry it was seeded from.
+2. **Break the app code the test covers.** `getUserFieldsForClient` was forced to always return the
+   `DEFAULT` field list, dropping every role flag. The user-fields test failed with
+   `expected 'firstName,lastName,email,uuid' to include '_isAdmin'` — proving it would catch a real
+   regression that silently demotes every admin to `USER`.
+
+Mutate **the thing under test**, not the harness. Verifying a *guardrail* (e.g. reverting an
+intercept to a URL glob to confirm the fall-through check fires) is a separate and also worthwhile
+exercise, but it proves the guard works — not that any test does.
 
 **MUST — every config file is type-checked.** A config that no `tsconfig` includes is compiled by
 **nothing** and is green by default — the same false-green class as running bare `npx tsc --noEmit`
@@ -781,6 +785,11 @@ Copy from there rather than reinventing.
 
 ## Change history
 
+- 2026-09-03 — §23 correction: replaced the two "seen to fail" worked examples. The first pass
+  listed a guardrail check plus an **unverified** component-config mutation; both are now the two
+  mutations that were actually run and observed red (a registry/fixture nav mismatch, and forcing
+  the `DEFAULT` user field list). Added the distinction that mutating the harness verifies a
+  **guard**, not a **test**. (apeterson)
 - 2026-09-03 — **Front-end testing promoted from an open item to §23 (MUST/SHOULD).** Settles the
   layering: Vitest + RTL for logic, Cypress **component** tests for the tenant x role x feature
   matrix (**not** e2e), e2e for a few real journeys only, with the rule of thumb "no URL or page

package/package.json

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