/* Shared "ink/paper" palette — the de facto standard :root block that Phase 3's variance audit (REFACTOR_PLAN.md) found duplicated byte-identical across dozens of tools, and, since Path 5 P1, the native dark theme for those same tools. 74 live pages link this file. ───────────────────────────────────────────────────────────────────────── THE DECISION (Path 5 P1, 2026-09-03) ───────────────────────────────────────────────────────────────────────── `_shared/a11y.js` owns theme, site-wide. It is the only thing that reads or writes theme state (`gvb-a11y-prefs`) and the only thing that sets `data-theme` on . `_shared/theme-toggle.js` — a second, parallel toggle on its own `gvb-tools-theme` key, loaded by zero live pages — was deleted in the same change; a11y.js still migrates that old key once. a11y.js gives a page dark one of two ways, never both: native the page sets `window.A11Y_NATIVE_THEME = true` before loading a11y.js. a11y.js sets `data-theme` on and stops; the page's own CSS — for the tools here, the block below — does the work. Real colours, so canvases, photos and QR codes survive. filter the page does not opt in. a11y.js also puts `.a11y-filter-dark` on and a11y.css inverts the whole page. Every hue shifts; this is the fallback, not the goal. So the dark block below is gated on `:not(.a11y-filter-dark)`. An ink-paper tool that has not opted in keeps the filter and the unchanged light values — this file changes nothing for the tools still waiting on the Path 5 P3 rollout. ───────────────────────────────────────────────────────────────────────── ADOPTING (Path 5 P3) — the flag alone is not enough ───────────────────────────────────────────────────────────────────────── Every one of these 74 tools hardcodes light colours in its own