/* ============================================================ Emerald Bay OS — Design Tokens. THE single source; nothing else in the app may declare a custom property. 2026-07-27 — token sources unified. base.html carried its own complete :root + [data-theme="dark"] block, and because that out-specified this file's :root, THAT block was what actually rendered in dark mode while this file governed light. The two themes were running two different palettes out of two different files. The dark values below are the ones base.html was really producing — a slate/emerald palette, not the pure-black Vercel palette this file used to claim. They were folded in verbatim so the merge changed nothing visually. The prose in docs/design-system/ and docs/atlas/ that describes the app as "pure-black Vercel" describes the intended direction, not the current render; retargeting the values to that direction is a deliberate restyle scheduled for after the Aug 1 warehouse cutover. 2026-08-07 — overnight overhaul, base+skin split (5 themes). Two independent attributes now live on , both written by static/js/theme.js's applyTheme() (and mirrored, inline, by the pre-paint boot snippet at the top of base.html/login.html/ change_password.html so there is no FOUC): data-theme one of dark | light | muted-corporate | hardman | glass data-theme-base dark | light — which GROUND that theme sits on Every theme that is NOT literally "light" inherits the dark ground declared in :root below unless it sets data-theme-base="light" (only muted-corporate does). This is why the ground block further down keys off the attribute pair below rather than repeating ~90 declarations per skin — see routes/profile.py's VALID_THEMES for the canonical theme name list; it must stay in sync with the THEMES array in static/js/theme.js and the skin blocks in this file. The theme-picker in the sidebar profile popover (base.html) previews each theme with three small colour bars sampled from THAT theme's own tokens — those bars are necessarily hardcoded (a var() there would resolve to the CURRENTLY active theme, not the one being previewed), so if you change a value below, update the matching .theme-swatch-- rule in base.html's