/* base.css — reset, document typography, focus, motion, print, layout utilities, and the site chrome. Ported from the signed-off Phase B prototype (docs/prototype/assets/css/base.css, frozen reference). Everything above the chrome is byte-identical to it except this header and the language → face scheme marked below. THE CHROME IS NOT A PORT ANY MORE, and its class names say so. Up to CP-C1-4 this file carried the prototype's nav rules verbatim, under class names that carried the prototype's own prefix, and kept them so the port stayed diffable against docs/prototype/. That era ended on 2026-08-29: the owner called the ported header "too bare for production" and picked a different design — masthead + tool rail, with the rail folding into a disclosure on a phone (Option B + Option C's collapse, docs/design/2026-08-29-header-options/index.html). There is nothing left to diff, so the rules below are `.site-*` and are written against that design rather than against the prototype's. The prototype keeps its own green chrome; it is a frozen record of what was signed off, not a source this file re-reads. Rules: tokens only (no literal colours), logical properties only — never left/right/top/bottom, margin-left, text-align: left, etc.; the one exception is the select chevron's background-position (no logical form exists), mirrored by an explicit [dir="rtl"] override. Arabic RTL depends on it. ┌─ BANNED: element-wide `:lang(xx) { font-family: … }` ───────────────────────────┐ │ `:lang(ar)` is a (0,1,0) selector and it matches EVERY element inside an Arabic │ │ page, not just . A font-family on it therefore outranks the (0,0,1) rules │ │ for `code`, `kbd`, `samp`, `pre` and `h1…h6` and silently reaches things it was │ │ never meant to touch. The prototype hit this twice (rulings R32 and R35) and had │ │ to buy each one back with a more specific counter-rule — a debt that grows with │ │ every element rule anyone adds later. │ │ │ │ THE ONLY SANCTIONED MECHANISM is the custom-property scheme below: the language │ │ picks a VALUE (--font-current / --lh-current), and TWO rules read that value │ │ into font-family — `body` and `[lang]`. Custom properties inherit without │ │ competing on specificity, so nothing is outranked and nothing has to be bought │ │ back. │ │ │ │ THE SANCTIONED READERS — the only four selectors in this file that may declare │ │ a font-family at all, written here exactly as they are written below: │ │ │ │ body reads --font-current (the scheme) │ │ [lang] reads --font-current (the scheme) │ │ code, kbd, samp, pre the monospace stack, ruling R32 │ │ code[lang], kbd[lang], samp[lang], pre[lang] the same, over `[lang]` (R32) │ │ │ │ Four declare a font-family; two of those read --font-current. A fifth reader │ │ re-opens the specificity war this scheme exists to end, so it has to be argued │ │ for HERE before it is added. │ │ │ │ ENFORCEMENT — app/qa/sweeps.ts holds the machine copy of that list │ │ (`SANCTIONED_READERS`), and the two are one contract: change this box and that │ │ array in the same commit, or the build fails. The sweeps fail on `:lang(` and a │ │ face declaration in one rule, on any reader outside the four, AND on any of the │ │ four that has DISAPPEARED. "A face declaration" is `font-family:` or a `font:` │ │ shorthand that is not exactly `inherit` — the shorthand sets a family too, and │ │ `input, button, select, textarea { font: inherit }` below is the one legitimate │ │ use of it. Do not add a banned rule, not even "just for this page". │ └──────────────────────────────────────────────────────────────────────────────────┘ */ /* ── reset ───────────────────────────────────────────────────────────── */ *, *::before, *::after { box-sizing: border-box; } html { -webkit-text-size-adjust: 100%; } body, h1, h2, h3, h4, h5, h6, p, figure, blockquote, dl, dd, fieldset, legend { margin: 0; padding: 0; } /* A list you styled is a list of things, not prose: it loses its markers and indent. A bare