/** * Legacy Tailwind Dark-Mode Shim (2026-09 dark theme audit) * * Most of the app is still "unconverted legacy views" per CLAUDE.md: raw * Tailwind CDN utility classes (bg-gray-100, text-red-800, border-indigo-500, * etc.) with literal light-mode hex values baked in by the CDN's JIT compiler. * Tailwind's default dark strategy is `media` (prefers-color-scheme), so it * never reacts to this app's own toggle - the * utility classes just sit there unchanged. Result: a light card background * (e.g. bg-indigo-50) paired with this app's dark-mode body text color * (near-white, inherited from tokens.css) reads as near-white text on a * near-white background. That is the deck discussion-prompt bug reported * 2026-09-02, and the same pattern recurs anywhere a legacy view combines a * light Tailwind background/text utility with the app's dark theme. * * Rather than hand-converting ~120 legacy view files to ui/ classes (a much * larger, separate redesign effort), this file re-tones the Tailwind color * utilities actually used in the codebase when dark mode is active, using * the same Material tokens from tokens.css. The mapping preserves each * utility's ROLE, not its literal shade: * - light background shades (50-300ish) -> dark surface/container tokens * - dark/medium text shades (500-900) -> light on-surface/accent tokens * - borders, rings, divides -> outline / accent tokens * Because backgrounds and texts are remapped independently by role, any * light-bg/dark-text pairing self-corrects into a dark-bg/light-text pairing * regardless of which hues a given view happened to combine. * * Solid, already-vivid utilities meant to carry white text (bg-blue-600 * buttons, bg-green-700 badges, etc.) and already-dark utilities (bg-gray-800 * headers, bg-black overlays) are intentionally left alone: they already * contrast correctly against white OR dark surrounding content. * * Load this AFTER the Tailwind CDN