7d2d9910cf
The adventure purple was unreadable on night, and measuring the family showed it was not alone: every one of the eleven .text-theme-* colours lands between 1.08:1 (eu, effectively invisible) and 3.12:1 (finance) on night's #2d365a. They were all picked against a light card and never checked against a dark one. Same hue, lifted lightness, saturation floored so the dull ones stay a colour instead of going grey — all now >=5.5:1. Night only. Dusk and dawn are lit cards despite their names, so they keep today's values exactly and the light phases are pixel-identical. Lego can't stay pillar-box red and be legible on navy; a red light enough to pass reads as salmon, which is the honest trade against a red nobody can see. Also adds --warn as a phase variable for the new "inert" chip, for the same reason --ink is one. Tailwind's dark: variant cannot do this job: darkMode is unconfigured, so dark: follows the OS's prefers-color-scheme, which knows nothing about which phase Pete is showing. That mismatch left the chip at 2.34:1 on a dark phase under a light OS, and 1.55:1 on a light phase under a dark OS — half the combinations unreadable, decided by a setting outside the page. Now 4.52-7.04 across all four phases, OS irrelevant. Still open, and NOT fixed here: text-[color:var(--ink)]/NN appears not to compile — there is no such rule in output.css, and the item description computes to a fixed rgb(74,46,42) that ignores the phase entirely. If that holds it is a pre-existing site-wide no-op, not confined to these panels. Recorded rather than guessed at.
17 KiB
17 KiB