This is open, and it is Ted's call. Two of the three cannot be fixed from the code side: flag red is the exact 태극기 value and §2.1 forbids moving it, so only the container could change — and the container is what was approved by eye on 2026-08-05. What was done instead of quietly changing either the tokens or the test: the tokens stay exactly as chosen, the test asserts the 3:1 UI floor so none of the three may drift further down, and the numbers are written here. Tightening the test to 4.5 is not a code change; it is a palette change and it needs Ted. Three ways out if he wants one — darken the soft containers slightly, reserve these pairs for ≥16px/700 text where 3:1 is the correct floor, or accept them as recorded deviations.

Colour is never the only signal. Urgent rows carry a red border and a deadline in words and a red action tag. Danger red is the strictest case of this and not an exception to it: every reddened subject is the same silhouette it was drawn as flat, named in real text beside it. The tightest pair in the app is danger red on dark surface_2 at 3.01:1 — over the 3:1 painted-shape floor by 0.01, asserted in both modes so darkening surface_2 fails the build. Text over a photograph always sits on a gradient veil, never directly on the image; contrast against an arbitrary photograph is unprovable otherwise. All user-visible text is selectable. §9, §9.1.