/* ============================================================================ Turtle Shell Home Protection — the dark theme, made the default ---------------------------------------------------------------------------- design.css already carries a complete dark theme, but it is written as `@media (prefers-color-scheme:dark)`: it reaches only the visitors whose operating system asks for it. The client wants the dark site for everyone. design.css is a vendor file and stays byte-identical, so the switch is made here instead: every declaration from that block, restated unconditionally. This file is linked LAST in the head — after design.css, swatches.css, social.css and any page-specific sheet — so it wins every tie at equal specificity without a single !important. Two halves: 1. THE BLOCK, transcribed. Lines 577-631 of design.css, verbatim apart from losing one level of indentation. Its comments come with it, because the reasoning behind #6fdc84 and --primary is the reasoning here too. 2. WHAT THE OPT-IN BLOCK NEVER HAD TO COVER. A theme nobody could reach without changing an OS setting was never walked end to end, and it has gaps. Each one below is a rule that renders unreadably once dark is the default, with the measurement that says so. `data-theme` on says "dark" now and is the single source of truth the scripts read; nothing in this file keys off it, because there is no light theme left to switch back to. ============================================================================ */ /* ---- 1. design.css's dark block, unconditional ---------------------------- */ /* color-scheme is NOT in the block it came from — under a media query the browser already knew the visitor wanted dark and styled the scrollbars, the