/* ============================================================ THE PHONE SCALE — phone.css Loaded by index.html on EVERY product, and inert everywhere it does not apply: every rule is inside `@media (max-width: 900px) and (pointer: coarse)`. IT USED TO BE GATED ON `html.has-phone-nav`, WHICH WAS WRONG. That class means "this product armed the bottom bar", and the Nova Assistant session made the argument that settles it: their product has no rail and five gated routes, the chat's own sidebar IS the chrome, and arming a tab bar on a chat app purely to inherit a type scale is the tail wagging the dog. A scale is not a navigation. It belongs to the POINTER, which is what `(pointer: coarse)` asks about — so a phone browser gets it too, not only the three apps, and every product improves at once. The thing that does still belong to the bar — `--hn-clear`, what a bottom-anchored control has to clear — lives in homenav.css with the bar itself, and is 0px wherever the bar is not mounted. WHY A SCALE AND NOT A LIST OF FIXES A live sweep of all 40 Nova OS routes at 375pt (mobile/os/scripts/parity-sweep.mjs) measured interactive controls at 26, 27, 30, 33, 34, 36 and 38 pixels tall. Fixing them view by view would be forty edits and a fortieth-first the next time somebody adds a chip. Almost none of those controls set their own height. They inherit --ctl-h-sm / --ctl-h-md / --ctl-h-lg from tokens.css, which are designed for a mouse. So the lever is the TOKENS: raise them here and every button, chip, field and select in the product grows at once, in the proportions its designer chose. Same for type. This is the same argument the native bridge makes about 200 fetch sites: the fix belongs at the one place the value is born. THE FLOOR IS NOT THE TARGET. Apple's 44×44 is a minimum, and the brief was "bigger and way easier for mobile", so the default button lands at 48 rather than 44 and the primary at 52. A thumb is about 45–57px of contact; designing to the legal minimum means every tap is a near miss. ============================================================ */ /* WHY SO MANY SELECTORS START WITH `:root`. They used to start with `html.has-phone-nav`, which was carrying TWO jobs: scoping (only products with the bottom bar) and specificity (0,2,0). Removing it fixed the scoping — a scale belongs to the pointer, not to a nav bar — and silently dropped the specificity to (0,1,0), which TIES with a view's own rule for the same class. A view's CSS is injected into a