Files
certctl/web
shankar0123 700c399367 chore(web): remove darkMode: 'class' from tailwind config — Phase 7 retired
Operator decision 2026-05-14: "no dark mode and no future dark mode
wiring to maintain." The originally-optional Phase 7 (the rebuild path
that would have superseded Phase 0's rip-out if customer signal materialized)
is formally retired in the frontend-design-audit.html banner stack +
Phase 7 H3 header.

Phase 0's closure rationale ("leave `darkMode: 'class'` in tailwind
config for the eventual Phase 7 rebuild") is now superseded — keeping
that line set would resurface as the same half-wired-hook pattern that
drove the original FE-H1 finding, just at the config layer instead of
the HTML layer. Phase 0 removed `class="dark"` from <html> + the body
`bg-slate-900`; this commit closes the loop by also removing the
tailwind config option that pointed at a future feature that won't
arrive.

If the decision ever reverses, this line restores in a one-diff revert
+ a full re-audit of every primitive and page for `dark:` variants
(see the retired Phase 7 executable prompt for the rules: ship complete
or not at all; piecemeal dark-mode is exactly the original finding).

Verification:
  • npx tsc --noEmit — exits 0
  • npx vite build — ✓ built in 3.20s (Tailwind doesn't need
    darkMode set to compile; output is identical because there are
    zero `dark:` classes in src/ to gate behind anything)
  • Audit HTML (workspace-only, not repo-tracked) updated with:
      - Phase 7 RETIRED banner at top of banner stack (amber accent)
      - Phase 7 H3 header flipped to "✗ Retired 2026-05-14"
      - FE-H1 row note extended with the lock-in decision
      - Phase 0's "Do NOT delete darkMode: 'class'" guidance struck
        through + marked SUPERSEDED with a pointer to the new banner
2026-05-14 17:16:40 +00:00
..