Document the design guard as it now stands

Plan step 41 review: README and the development skill describe the API
that exists after the review, briefly — what scan() reads, the family
table with the M3 spacing step and 1.x utilities, missingStylesheets()
reading imports only, forbidColours() on the 2.0.0 vocabulary — and
UPGRADE.md lists the removed checks and methods and the retargeted
forbidColours() (the user, 2026-09-15).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9

UPGRADE.md

@@ -156,8 +156,18 @@ the contrast toggle (`<x-theme-toggle mode="contrast">`) and the Standard motion
 
 ### 8. Tests and guards
 
-Add `DesignGuard`'s new checks to the application's design test (`forbidOpacityInk()` and
-`forbidAbsolutes()` are opt-in). Browser tests that assert widths switch at 640/1024/1280 now
+`DesignGuard` changes with the stack:
+
+- **Removed:** the maryUI tag and daisyUI class checks, `forbidAbsolutes()` and `forbidOpacityInk()`.
+  Every Tailwind utility now compiles to nothing and is reported with its replacement, so
+  `bg-white` and `text-on-surface/60` still are.
+- **Retargeted:** `forbidColours([...])` keeps its signature and reports a left-out role where 2.0.0
+  writes one: `var(--md-sys-color-…)` in CSS or an inline `style`, an `md-ink-*` class, a
+  component's `color`/`tone` prop.
+- **New:** `missingStylesheets($cssEntry)` names each `@import` the views need; a `.css` file passed
+  to `scan()` is checked for literal values and off-scale media queries.
+
+Browser tests that assert widths switch at 640/1024/1280 now
 switch at 600/840/1200; tests that read `role="alert"` on an alert, `aria-pressed` on the time
 picker's period buttons or `data-theme-option` need the new hooks above.