/* SR-2 Tailwind dark-mode compatibility layer — v1 * ============================================================================ * THE PROBLEM * 383+ SR-2 templates use raw Tailwind utility colors (bg-white, text-gray-600, * bg-slate-100, border-gray-300, hover:bg-gray-50, chip strips, etc.). SR-2's * dark mode is the scott_common shell flipping `data-theme="dark"` on * (see scott_common/css/tokens.css [data-theme="dark"] block). That flips the * shell's SURFACE/TEXT *tokens* (--bg, --card-bg, --text...), turning the page * background dark — but the hardcoded Tailwind utilities bypass those tokens * entirely. So `text-gray-700` stays dark-gray on a now-dark surface * (invisible), `bg-white` cards stay white islands, `bg-slate-100 text-slate-700` * buttons collapse, inactive chips (`bg-white border text-gray-700`) vanish. * * v0.88 (scott_common) + sr2_brand.css already fixed Bootstrap `.btn-*` and * saturated `bg--500/600/700 text-white` buttons. This layer fixes the * remaining NEUTRAL/low-contrast Tailwind utilities only. * * SCOPE / SAFETY * - EVERY rule below is scoped under `[data-theme="dark"]` ONLY. Light mode is * byte-for-byte untouched — none of these selectors match in light mode. * - We remap only NEUTRAL utilities that collapse in dark mode. Saturated * buttons (bg-blue-600/emerald-600/red-600 + text-white) are left ALONE — * they are legible in both modes and sr2_brand.css already backs them. * - Values reuse the scott_common dark tokens (tokens.css [data-theme="dark"]) * so the look stays consistent with the shell's own dark surfaces: * --card-bg #1e293b (slate-800), --bg #0f172a (slate-900), * --card-border #334155 (slate-700), --text #f1f5f9, --text-muted #94a3b8, * --text-soft #cbd5e1. * - Specificity: `[data-theme="dark"] .bg-white` (0,2,0) beats Tailwind's * `.bg-white` (0,1,0) regardless of source order, so this WINS even though * the Tailwind Play CDN injects its