/* ══════════════════════════════════════════════════════════════════════════ sf-gate.css — VANTA'S AGE GATE, dressed to the client's reference (owner brief, 2026-08-24: "an age gate similar to this reference with my client's branding" — refinedbiolabs.com, which is voice.references[0] in client.json and which the dev notes call his number one reference). WHAT THIS IS. `age-gate.js` is a PROTECTED ENGINE FILE — a front end never ships its own copy and never edits this one (engine/FRONTEND-CONTRACT.md §B). It is dressed instead through the seam documented in engine/AGE-GATE-THEMING.md: `--lag-*` custom properties plus `data-lag-*` copy slots. This file is that dressing. Not one line of age-gate.js changes, and the two attestation statements — the record the visitor affirms — are untouched, unmerged, both still unticked, and still the only thing that wakes the Confirm button. Those are not slots and this file does not try to make them one. §1 IS PURE TOKENS and is the bulk of the look. §2 is a small, deliberate override block for the four things the token set genuinely cannot reach: full-viewport bleed, which side the image lands on, the panel ratio, and the photograph's treatment. The theming doc says override CSS is not REQUIRED — it is not forbidden, and a card that must become an edge-to-edge interstitial needs it. Every rule there is scoped under `#lag-root`, because the engine appends its own