/* NIX — the shell: the rail and the panel ══════════════════════════════════════════════════════════════════════════ THE SITE HAS TWO STATES AND ONE CLASS SAYS WHICH. `is-nav` on means the rail is out. It is restored before first paint by views/partials/head.xml from localStorage, so a rail that was open stays open across a navigation — which is the whole reason the rail exists rather than a menu. Four arrangements, and every rule in this file belongs to one of them: SHUT, desktop the rail's grid track is 0 and the page has the window. The panel has no ground and no corners: it IS the page. The ring sits at the left edge. OPEN, desktop the track becomes --rail-w and the page gives that width back. The panel takes --nix-panel and a radius, so it reads as a second panel beside the rail. The ring travels out to the rail's far edge, in step with it. SHUT, phone identical to shut on a desktop. Nothing to do. OPEN, phone the rail COVERS instead of pushing: two columns of 260 and whatever is left is a corridor, not a room. The shell keeps its single column, the rail goes fixed over the page, and the panel gives up its ground and corners with the gutter that made them read. THE ANIMATION IS THE COLUMN TRACK ITSELF, not a transform and not a slide. A fixed rail sliding over the page would cover the left of it; a transform would leave the page's own width unchanged, and every full-bleed band on it would still be measuring the whole window and running off the side. That is also why so much of this file is `body.is-nav `: a band that reaches to the window's edges has to stop doing that the moment the window stops being the box it is in. Those rules are collected here rather than left in each page's sheet, because they are all one mistake and they should all stop being it in one place. Cross-document view transitions are here too: with the rail open the panel is the only thing that changes, so it fades and the rail holds still; with it shut nothing is named except the ring, so the whole page crosses. ══════════════════════════════════════════════════════════════════════════ */ /* ── The nav shell ────────────────────────────────────────────────────────── The rail and the page, side by side, in the arrangement the marketplace uses — so opening the menu turns this page into the same room rather than dropping a screen over it. THE ANIMATION IS THE COLUMN TRACK ITSELF. Closed, the rail's column is 0 wide and the page has the window; open, the track becomes 260 and the page gives that width back. Sliding a fixed rail over the page instead would cover the left of it, and pushing with a transform would leave the page's own width unchanged — its full-bleed bands would still be measuring the whole window and would run off the side. The gutter and the gap animate with it. At rest they are zero, which is what keeps the closed page edge to edge exactly as it was. */ /* ══ TWO WAYS TO ARRIVE ═════════════════════════════════════════════════════ These pages are separate documents and always will be — each one carries a preloader, a three.js scene or a wizard in its own