1589ea42099d7fe0e0c4ff1c3164e0add6ca4ee4
docs/06 §5 has said "≥ 4.5:1 in both themes (tokens chosen accordingly)" since the spec was written. Nothing enforced it, and the tokens were not chosen accordingly. Measured: white on dark --accent 3.67:1 (fixed in Phase 4) white on dark --danger 2.74:1 Button/ConfirmDialog .danger light --warn on --bg-raised 3.40:1 WarningList summary light --success " " 3.26:1 TreePreviewNode badge, DuplicatePanel light --danger " " 4.27:1 DuplicatePanel count dark --accent " " 4.40:1 links inside raised panels Adds --danger-fg, which like --accent-fg must be redefined in the dark block in the OPPOSITE direction: dark mode lightens the colour for contrast against the page, and that is exactly what breaks white ink sitting on it. The light status colours are now darker than an eyeball would pick, because all three are rendered as text on --bg-raised. Adjustments preserve hue and were solved for numerically rather than guessed; each clears 4.5 with margin. The real deliverable is tests/unit/styles/contrast.test.ts, which parses tokens.css and fails on any text pair below 4.5:1 — verified to actually fail by restoring the old --warn and watching it report 3.40:1. It also pins the two dark blocks (explicit override and prefers-color-scheme) against each other, because they already drifted once when --accent-fg was added to only one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Languages
TypeScript
75.8%
Svelte
14.5%
JavaScript
9.2%
CSS
0.4%