/* ══════════════════════════════════════════════════════════════════════ age-gate.css — the age gate's checkboxes are LIGHT, and you can see them. THE DEFECT (owner, 2026-08-26): "the checkboxes on the age gate are too dark - make them more light so you can see them." MEASURED ON THE LIVE SITE (iPhone 390x844, corechainresearch.com, before this sheet). The visible control is not the — that is `.lag-cb{opacity:0;width:0;height:0}` — it is the sibling ``, and its unchecked state resolved to: modal surface rgb(20, 34, 53) #142235 (--sf-elevated) box fill rgb(20, 34, 53) #142235 → 1.00:1 against it box border rgba(166,186,203,.20) over that ground = rgb(49, 64, 83) → 1.52:1 A fill at 1.00:1 is not "hard to see", it is the same colour as the thing it sits on: the control was one 1.5px hairline at 1.52:1, well under the 3:1 WCAG 1.4.11 floor for a non-text UI control. It is not a mistake in the gate either — `.lag-box` paints `var(--lag-surface, var(--sf-elevated, #ffffff))`, which is deliberately THE SAME TOKEN AS THE MODAL so that on a light client you get the familiar white box on a white card, read by its grey outline. On a dark client that identity is the bug. WHY THE FIX IS NOT `--lag-surface`. That custom property is the gate's own designed escape hatch and it is the wrong lever here, because ONE token paints three things: `.lag-modal` background, `.lag-box` background and the disabled `.lag-btn-primary` mix. Re-pointing it to a light value would repaint the whole modal. The box needs its own colour, so the box gets its own rule. THE CASCADE TRAP, and it is the whole difficulty of this lane. None of the gate's CSS is in a stylesheet. age-gate.js BUILDS IT AS A STRING and appends `