/* ==========================================================================
   shell.css — the CHROME of both portals (Phase E, E3)

   ⚠ WHY THIS FILE EXISTS. Until E3 these 323 lines lived in two <style> blocks,
   in layouts/app.php and layouts/auth.php — and app.php argued against exactly
   that in the comment immediately above its own block:

       "Module component CSS lives in a FILE, not a <style> block … an inline
        block would force style-src 'unsafe-inline' on any future CSP, which is
        the concession that makes a CSP worthless."

   The reasoning was right and had been applied to one of the three stylesheets.
   PHASE_E §E3 Finding 1. With this file the product ships NO inline CSS at all,
   so a Content-Security-Policy needs no style-src exemption.

   ⚠ WHAT BELONGS HERE, AND WHAT DOES NOT. This is CHROME — the frame a screen
   hangs in: topbar, branch chip, account block, nav, main, footer, and the auth
   card. Components live in module.css and tokens in theme.css. A rule that
   describes a REUSABLE THING is in the wrong file if it is here.

   ⚠ AND THE AUTH LAYOUT NO LONGER CARRIES ITS OWN COMPONENTS. It used to define
   .vz-input, .vz-btn, .vz-alert, .vz-field, .vz-label and .vz-hint — a parallel
   vocabulary for the app's .vz-control, .vz-action, .vz-callout and friends
   (§E3 Finding 2). Nothing broke at runtime because the two never loaded
   together, which is why it survived; but a token change landed on one set and a
   component change on the other, and the first screen every user sees was the one
   not sharing the system. auth.php now loads module.css and uses its vocabulary.
   ========================================================================== */

/* --- Operator app shell ------------------------------------------------- */
.vz-shell { min-height: 100vh; display: flex; flex-direction: column; }

/* ⚠ THE HORIZONTAL PADDING IS A `max()` BECAUSE OF `viewport-fit=cover` (E6+ item 3).
   Both layouts now declare it, so the page extends UNDER the notch and the rounded
   corners instead of being laid out inside them — which is the only thing that makes
   `env(safe-area-inset-bottom)` non-zero for E21's bottom bar. The cost is that a phone
   held in landscape puts the camera housing over the left edge of whatever paints
   there, and in this shell that is the brand lockup. `max()` keeps the design's 20px
   everywhere it is enough and gives way to the inset where it is not. Every strip that
   paints to a page edge carries one: the topbar, the sidebar, the content column, the
   footer and the tab bar. */
.vz-topbar {
  display: flex;
  align-items: center;
  gap: var(--vz-space-4);
  padding: var(--vz-space-3) max(var(--vz-space-5), env(safe-area-inset-right, 0px))
           var(--vz-space-3) max(var(--vz-space-5), env(safe-area-inset-left, 0px));
  background: var(--vz-surface);
  border-bottom: 1px solid var(--vz-border);
  flex-wrap: wrap;
  /* 🔴 ⚠ `position: relative` IS FOR THE BELL'S PHONE SHEET AND CHANGES NOTHING TODAY
     (`§Q-R12`). Below 30rem `.vz-bell` goes `position: static` so its panel can pin to both
     edges of this bar rather than hanging off a trigger the flex wrap may have put anywhere —
     see the bell section at the foot of this file for the measurement.
     ⚠ AND IT MOVES NO EXISTING DROPDOWN, WHICH WAS CHECKED RATHER THAN ASSUMED: every other
     panel in this bar sits inside a host that is itself `position: relative`
     (`.vz-branch-switch`, `.vz-account-menu`), so each already resolves against its own host
     and never walks up to this one. ⛔ Declaring it only inside the media query would be a
     positioning context that appears and disappears with the viewport, which is the harder
     thing to reason about of the two. */
  position: relative;
}
/* ⚠ NOT --vz-primary-deep. Used as text that token measured 1.73:1 and was effectively
   invisible — found by the Phase A audit, 2026-08-24, back when it was a dark-mode
   SURFACE tone whose own comment read "headings on tint", meaning on a green tint rather
   than on the page background.

   ⚠ THE ORIGINAL SECOND HALF OF THIS COMMENT IS NO LONGER TRUE, AND THE DECISION IT
   JUSTIFIED STILL IS. It read "no green in the palette clears 4.5 on BOTH themes (best is
   primary-strong at 4.34)". E5a moved `--vz-primary-strong` to 5.20 and E13 left one
   theme, so a green here would now pass — E12 put exactly that green on the `b` two rules
   below. **"Vazhai" stays ink because the lockup is ink-plus-green by design**, which is
   Finance's structure and what makes it read as one word rather than two, not because a
   green would be illegible. Corrected in E13's audit rather than left to justify a
   decision with a measurement that has moved. */
.vz-brand { gap: var(--vz-space-2);
  display: inline-flex;
  align-items: center;
  min-height: var(--vz-tap-min);
  font-weight: var(--vz-fw-bold);
  color: var(--vz-ink);
  font-size: var(--vz-fs-md);
  text-decoration: none;
}
.vz-brand:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: 2px; }

/* ⚠ THE E2 COMMENT THAT SAT HERE IS DELETED, NOT AMENDED. It described the wordmark as an
   inlined SVG filled with `currentColor` so the lockup could follow `--vz-ink` "through
   BOTH theme mechanisms — the OS preference and an explicit [data-theme]". **E5 replaced
   that SVG with HTML text** and **E13 removed both theme mechanisms**, so every noun in it
   had stopped referring to something. The block below supersedes it and the reasoning it
   carried is kept in `partials/brand.php`, which is where the markup decision lives. */
/* ⚠ FINANCE'S LOCKUP, MATCHED EXACTLY (E5). `vazhai-finance` renders a 32px tile beside
   HTML text at `--vz-fs-h1` / `--vz-fw-medium`. The previous version drew the wordmark as
   SVG text at weight 800, which read visibly heavier than "Vazhai Tech" does at 500 — the
   reported difference. Both halves of the word use the SAME weight in Finance; only the
   colour changes, which is what makes it read as one word rather than two. */
.vz-brand-mark { display: block; width: 32px; height: 32px; border-radius: var(--vz-radius-sm); }
.vz-brand-word { font-size: var(--vz-fs-h1); font-weight: var(--vz-fw-medium); color: var(--vz-ink); }
/* 🐛 ⚠ `--vz-primary-strong`, NOT `--vz-primary` (owner, 2026-09-01). The accent measured
   **2.59** here — 18px normal-weight text on `--vz-surface`, on every screen in the
   product — and `ThemeContrastTest` had no assertion about `--vz-primary` at all, because
   the accent is deliberately held to a NON-TEXT floor: borders, focus rings, active nav.
   Nothing was wrong with the token; what was wrong was a stylesheet putting a word in it.
   `--vz-primary-strong` is the half of the pair that carries text, and it measures
   **5.20**. `testEveryTokenAStylesheetPaintsTextWithClearsTheFloor` now asks the
   stylesheets which tokens they paint text with, so the next one fails the suite instead
   of shipping. `PHASE_E §E12`. */
/* 🔴 ⚠ AND `--vz-wordmark` SINCE `§8a` ROW 7, WHICH IS THE SAME VALUE FOR A DIFFERENT
   REASON (owner, 2026-09-06 — `§7` item 25, option B). `--vz-primary-strong` is in
   `BrandPalette::TOKENS`, so an operator's brand colour rewrote it — and *"Vazhai
   **Chit**"* came out in the operator's hue beside a tile carrying Vazhai's green, which
   is two brands in one lockup. **The product's own name is not an operator's to recolour**;
   their mark goes on the statutory documents THEY produce, not on our chrome. The token
   holds the identical `#437a1f`, so nothing about this word changes for an unbranded org
   — E12's 5.20 is preserved rather than re-chosen, because re-choosing it by eye is
   exactly how item 27 came back. ⛔ Do not point this rule back at a `BrandPalette` token:
   `BrandPaletteTest` fails if `--vz-wordmark` ever joins that list, and this comment is
   the reason it is a test rather than a note. */
.vz-brand-word b { color: var(--vz-wordmark); font-weight: var(--vz-fw-medium); }
@media (max-width: 40rem) { .vz-brand-mark { width: 28px; height: 28px; } }

/* 🔴 THE OPERATOR'S OWN MARK ON THE MEMBER PORTAL (owner, 2026-09-28).
   `BRANDING §5`: operators white-label member-facing surfaces and *"their logo replaces the
   lockup on member surfaces"*.

   ⚠ **`object-fit: contain`, AND IT IS THE WHOLE RULE.** The Vazhai icon is a square drawn
   to fill 32×32; an operator's logo is a WORDMARK far more often than a badge —
   `BrandLogoWriter` says so and scales rather than crops for that reason. Forcing one into
   a 32px square would squash it, and `ImageRendition`'s deliberate no-crop would be undone
   by the stylesheet at the last step.

   ⚠ **AND IT MAY BE WIDER THAN IT IS TALL.** `width: auto` with a max lets a wordmark take
   the room it needs; 160px is where the brand stops competing with the branch chip beside
   it, measured against the longest operator name the fixture carries. */
.vz-brand-mark--operator {
  width: auto;
  max-width: 160px;
  height: 32px;
  object-fit: contain;
  border-radius: 0;
}
@media (max-width: 40rem) {
  .vz-brand-mark--operator { max-width: 110px; height: 28px; }
}

.vz-topbar-spacer { flex: 1 1 auto; }

/* --- Footer ------------------------------------------------------------- */
/* `margin-top: auto` inside the `flex-direction: column` shell pins it to the
   bottom of the viewport on a short page and lets it sit after the content on a
   long one — without `position: fixed`, which would cover rows on a phone. */
/* ⚠ SMALLER MEANS LESS PADDING, AND THE 44px ANCHOR IS NOT WHAT GIVES (owner, E6+
   item 4). `--vz-tap-min` is a floor; the rule below this one carries a hard-won comment
   about why that anchor is `inline-flex` at all, and shrinking it to win a strip of
   height would put a third control on `OPERATING_MODE §7` item 20's list. So the
   vertical padding drops 16px → 4px and the bar goes 77px → 53px with the target
   untouched.

   ⚠ AND `flex-end`, BECAUSE THE BAR HAS ONE CHILD NOW. The copyright left the signed-in
   shell with this change (`layouts/app.php` says why); `space-between` with a single item
   pins it LEFT, which is the opposite of "moved right".

   ⚠ THE AUTH FOOTER IS UNAFFECTED, AND NOT BECAUSE IT OVERRIDES THIS. `.vz-footer--auth`
   sets `flex-direction: column`, which makes `justify-content` the BLOCK axis there — and
   a single caption in an auto-height column cannot move along it. Checked rather than
   assumed: `§E5`'s centred copyright renders identically before and after. */
.vz-footer {
  margin-top: auto;
  padding: var(--vz-space-1) max(var(--vz-space-5), env(safe-area-inset-right, 0px))
           var(--vz-space-1) max(var(--vz-space-5), env(safe-area-inset-left, 0px));
  border-top: 1px solid var(--vz-border);
  background: var(--vz-surface);
  display: flex;
  flex-wrap: wrap;
  gap: var(--vz-space-1) var(--vz-space-4);
  align-items: center;
  justify-content: flex-end;
  font-size: var(--vz-fs-xs);
  color: var(--vz-subtle);
}
.vz-footer p { margin: 0; }
/* ⚠ THE TAP TARGET IS `align-items`, NOT `line-height`. Setting a 44px line-height made
   the anchor a 44px line BOX, so the 16px mark inside it sat on that box's baseline and
   broke onto its own row above the words. Inline-flex gives the same 44px target and
   keeps the mark on the text line. */
.vz-footer a {
  color: var(--vz-primary-strong);
  font-weight: var(--vz-fw-medium);
  display: inline-flex;
  align-items: center;
  min-height: var(--vz-tap-min);
}
@media (max-width: 40rem) {
  .vz-footer {
    padding: 0 max(var(--vz-space-4), env(safe-area-inset-right, 0px))
             0 max(var(--vz-space-4), env(safe-area-inset-left, 0px));
  }
}

/* The branch chip. Bordered and tinted rather than plain text: it is state, and
   state that changes what every screen shows should not read as a caption. */
.vz-branch {
  display: inline-flex;
  align-items: center;
  gap: var(--vz-space-2);
  padding: var(--vz-space-1) var(--vz-space-3);
  border: 1px solid var(--vz-border-strong);
  border-radius: var(--vz-radius-pill);
  background: var(--vz-surface-2);
  font-size: var(--vz-fs-sm);
  color: var(--vz-ink);
}
.vz-branch-label {
  color: var(--vz-subtle);
  font-size: var(--vz-fs-xs);
  text-transform: uppercase;
  letter-spacing: 0.06em;
}
/* ⚠ **THIS ONCE CITED `.vz-linkbtn` AS THE SAME REASONING AND NO LONGER CAN** — that rule
   went GREEN on 2026-10-13, on the measurement below. ▶ What keeps THIS one ink is its own
   argument, stated here, and it is unaffected. ⚠ THE MEASUREMENT THIS ONCE
   CITED HAS MOVED — it read "no green reaches 4.5 on both themes", and since E5a
   `--vz-primary-strong` clears it on every surface (5.20 / 4.79 / 4.58). What keeps this
   ink is that the branch chip is CHROME rather than brand: colouring it green would make
   the topbar two greens competing for the eye. Underlined so it still reads as a link at
   this size. */
.vz-branch a {
  color: var(--vz-ink);
  font-size: var(--vz-fs-xs);
  text-decoration: underline;
  display: inline-flex;
  align-items: center;
  min-height: var(--vz-tap-min);
}
.vz-branch a:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: 2px; }

/* --- Topbar menus: the branch switcher and the user menu (E22) ------------ */

/* ⚠ BOTH ARE `<details>`, LIKE E21'S DRAWER. No script: focusable, Enter and Space,
   and the expanded state announced by the platform. The two share `.vz-menu`, because
   a dropdown that looks like one thing under the branch and another under the name is
   two components to learn. */
.vz-branch-switch,
.vz-account-menu { position: relative; }

/* `<summary>` draws a disclosure triangle in every browser; these are chips. */
.vz-branch-switch > summary,
.vz-account-menu > summary { list-style: none; cursor: pointer; }
.vz-branch-switch > summary::-webkit-details-marker,
.vz-account-menu > summary::-webkit-details-marker { display: none; }

.vz-branch-switch > summary:focus-visible,
.vz-account-menu > summary:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: 2px; }

/* The caret does not animate its rotation — E13 fixed the motion layer as colour only. */
.vz-branch-caret { width: 16px; height: 16px; flex: none; color: var(--vz-subtle); }
.vz-branch-switch[open] > summary .vz-branch-caret,
.vz-account-menu[open] > summary .vz-branch-caret { transform: rotate(180deg); }

/* The account name is a chip now rather than bare text, so it reads as operable. */
.vz-account-menu > summary {
  display: inline-flex;
  align-items: center;
  gap: var(--vz-space-2);
  min-height: var(--vz-tap-min);
  padding: 0 var(--vz-space-2);
  color: var(--vz-muted);
  font-size: var(--vz-fs-sm);
}
.vz-account-menu > summary:hover { color: var(--vz-ink); }

/* ⚠ THE AVATAR IS A CONTRAST PAIR AND IT REUSES THE BUTTON'S (E6+ item 5). Letters on a
   filled disc are TEXT on a background: `--vz-primary-button` under
   `--vz-primary-contrast` is the pair `ThemeContrastTest` measures at 4.96 and
   re-measures for every hue `BrandPalette::derive()` can produce from an operator's own
   colour. A NEW pair here would be a new thing to prove, and `§E12` is what happens when
   a stylesheet paints text in a token nobody measured for it.

   ⚠ 32px MATCHES `.vz-brand-mark`, so the two ends of the topbar agree — and the disc is
   not a target: the whole `<summary>` around it already carries `--vz-tap-min`. */
.vz-avatar {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  flex: 0 0 auto;
  width: 32px;
  height: 32px;
  border-radius: 50%;
  overflow: hidden;
  background: var(--vz-primary-button);
  color: var(--vz-primary-contrast);
  font-size: var(--vz-fs-xs);
  font-weight: var(--vz-fw-bold);
  letter-spacing: 0.02em;
  line-height: 1;
  text-transform: none;
}

/* A real photo fills the disc rather than letterboxing inside it. Unreachable until
   something writes `avatar_path` — `partials/avatar.php` says so out loud. */
.vz-avatar--photo { object-fit: cover; }

/* No initials at all: a glyph rather than an empty circle, which would read as an image
   that failed to load. The fill goes with it — an anonymous disc should not be the
   loudest thing in the chrome. */
.vz-avatar--anon {
  background: var(--vz-surface-2);
  color: var(--vz-muted);
}

.vz-avatar--anon svg { width: 18px; height: 18px; }

/* The glyphs the two dropdowns gained (E6+ item 5). Both are `aria-hidden`; each sits
   beside the word it illustrates, so they are decoration in the strict sense and are
   sized and toned to stay that way. */
.vz-branch-icon { width: 16px; height: 16px; flex: none; color: var(--vz-subtle); }
.vz-menu-icon   { width: 18px; height: 18px; flex: none; color: var(--vz-subtle); }
.vz-menu-item:hover .vz-menu-icon { color: var(--vz-ink); }

.vz-menu {
  position: absolute;
  top: calc(100% + 4px);
  /* ⚠ RIGHT-ALIGNED, BECAUSE BOTH TRIGGERS SIT IN THE RIGHT HALF OF THE BAR. Dropping
     from the left edge would push a wide menu off the viewport on a narrow screen. */
  right: 0;
  z-index: 1000;
  min-width: 12rem;
  max-height: 60vh;
  overflow-y: auto;
  padding: var(--vz-space-1);
  background: var(--vz-surface);
  border: 1px solid var(--vz-border-strong);
  border-radius: var(--vz-radius-md);
  box-shadow: var(--vz-shadow-md);
}

/* The branch switcher hangs off the LEFT trigger, so it opens the other way. */
.vz-branch-switch .vz-menu { right: auto; left: 0; }

.vz-menu-heading {
  padding: var(--vz-space-2) var(--vz-space-3);
  font-size: var(--vz-fs-xs);
  text-transform: uppercase;
  letter-spacing: 0.06em;
  color: var(--vz-subtle);
}

/* Every BRANCH option is a submit button — see the layout for why a branch switch may
   not be a link. They are styled as menu rows rather than as buttons so the menu reads
   as a menu.

   ⚠ SINCE E5b THE USER MENU ALSO CARRIES AN `<a>` (Change password), so this rule has
   to draw a link and a button identically. `text-decoration: none` and the inherited
   `color` are what a browser would otherwise put back — and a menu with one underlined
   blue row and one ink row reads as two kinds of thing.

   🐛 ⚠ AND `box-sizing` WAS LOAD-BEARING AND MISSING (E5b). This file declares the
   property per component rather than in a universal reset, and this rule never did —
   which was invisible for as long as every item was a `<button>`, because browsers
   default form controls to `border-box` themselves. The `<a>` inherited `content-box`,
   so `width: 100%` meant 100% PLUS `space-3` on each side: MEASURED at 216px inside a
   192px menu, and the dropdown grew its own horizontal scrollbar. `.vz-action` already
   states the property for exactly this reason. */
.vz-menu-item {
  display: flex;
  align-items: center;
  gap: var(--vz-space-2);
  box-sizing: border-box;
  width: 100%;
  min-height: var(--vz-tap-min);
  padding: 0 var(--vz-space-3);
  border: 0;
  border-radius: var(--vz-radius-sm);
  background: none;
  color: var(--vz-ink);
  font-family: var(--vz-font-sans);
  font-size: var(--vz-fs-sm);
  text-align: left;
  text-decoration: none;
  cursor: pointer;
}

.vz-menu-item:hover { background: var(--vz-surface-2); }
.vz-menu-item:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: -2px; }

/* The branch you are already in. State is the weight AND the tick, never colour alone. */
.vz-menu-item[aria-current="true"] {
  font-weight: var(--vz-fw-medium);
  color: var(--vz-primary-strong);
}
.vz-menu-item[aria-current="true"]::after {
  content: '';
  margin-left: auto;
  width: 8px;
  height: 8px;
  border-radius: 50%;
  background: currentColor;
}

.vz-account { display: flex; align-items: center; gap: var(--vz-space-3); }
.vz-account-name { font-size: var(--vz-fs-sm); color: var(--vz-muted); }
/* 🔴 **IT READS LIKE THE FORGOT-PASSWORD LINK, BECAUSE IT IS THE SAME KIND OF THING.**
   Owner, 2026-10-13: *"the signout link is too small and faint. Use the same style like we have
   for forgot password"*. ▶ That link is `.vz-auth-note a` — `--vz-primary-strong` at
   `--vz-fw-medium` — and this now matches it, so the one control a locked reader needs on a
   shared branch terminal stops looking like an afterthought under the unlock button.

   🐛 **THIS RULE WAS INK BECAUSE OF A MEASUREMENT THAT HAD ALREADY MOVED.** It read *"at 13px
   this needs 4.5:1 and primary-strong measures 4.41 — a near miss that is still a miss"*. ⚠
   `.vz-branch a` two hundred lines up records the correction at E5a, and computing it from the
   tokens settles it: `#437a1f` is **5.20:1 on `--vz-surface`** and **4.58:1 on `--vz-surface-2`**.
   Both clear the floor. ⛔ What keeps `.vz-branch a` ink is a different argument entirely — the
   branch chip is chrome rather than brand — and that one still holds.

   ⚠ **THE UNDERLINE STAYS, AND IT IS NOT DECORATION.** This is a `<button>` because signing out
   is a POST, so it gets no underline from the user agent the way an `<a>` does; colour alone
   would be the only affordance, and colour alone is not one.

   ⚠ **THE SIZE IS UNCHANGED AT `--vz-fs-sm` (13px) — THE SAME AS THE FORGOT LINK**, which is
   what "the same style" means. If it still reads small, the thing to change is `.vz-auth-note`
   for both screens, which is a decision about the sign-in page too. */
.vz-linkbtn {
  background: none;
  border: 0;
  padding: 0 var(--vz-space-2);
  min-height: var(--vz-tap-min);
  /* ⚠ **NO `font-size` OF ITS OWN — IT INHERITS FROM `.vz-auth-note`.** It used to pin
     `--vz-fs-sm` here, after `font: inherit`, so raising the note's size would have grown the
     forgot-password LINK and left this BUTTON behind: the opposite of the complaint that
     produced the change. ▶ Inheriting is also what makes "the same style as forgot password"
     stay true without anybody maintaining two numbers. */
  font: inherit;
  font-weight: var(--vz-fw-medium);
  color: var(--vz-primary-strong);
  cursor: pointer;
  text-decoration: underline;
}
.vz-linkbtn:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: 2px; }

.vz-body { display: flex; flex: 1 1 auto; align-items: stretch; }

.vz-nav {
  width: 15rem;
  flex: 0 0 15rem;
  /* The left page edge in landscape — see `.vz-topbar` (E6+ item 3). `box-sizing` is
     declared because this rule now sets a width AND pads it, which is the question
     `testEveryRuleThatSizesAndPadsSaysWhichBoxItMeans` asks of every such rule. */
  box-sizing: border-box;
  padding-left: env(safe-area-inset-left, 0px);
  background: var(--vz-surface);
  border-right: 1px solid var(--vz-border);
  padding: var(--vz-space-4) 0;
}
/* ===========================================================================
   THE COLLAPSED SIDEBAR (§Q-R9)
   ---------------------------------------------------------------------------
   Owner, 2026-09-15: "Why no collapse menu feature?" Icons-only when collapsed,
   never hidden — `.vz-nav-icon` already renders beside every label, so
   navigation survives the collapse rather than disappearing into a menu.

   🔴 EVERY RULE BELOW IS SCOPED `.vz-body > .vz-nav` — BY POSITION, NOT BY NAME.
   The phone drawer's sheet wears `.vz-nav` too, deliberately, so that it
   inherits every nav rule (both layouts carry a comment saying so, and the
   `display: none` rule at 48rem is already scoped this way for exactly this
   reason). A rule on `.vz-nav` alone would collapse the drawer — which is only
   ever open on a phone, where there is no sidebar to collapse.

   ⚠ THE ATTRIBUTE IS ON `documentElement` because `nav-state.js` sets it from
   inside `<head>`, before `<body>` exists. That is what makes the restore
   paint-free: there is no expanded frame to reflow away from.
   =========================================================================== */
[data-vz-nav="collapsed"] .vz-body > .vz-nav {
  /* 4.5rem = the 20px glyph plus `--vz-space-5` either side, which is what the
     row already pads to. Printed back from the measured cell rather than
     guessed: §6's L4, "print the measured width, never the value you typed." */
  width: 4.5rem;
  flex: 0 0 4.5rem;
}

/* ⛔ `.vz-sr-only`'s TREATMENT, NOT `display: none`. Hiding the label outright
   removes it from the accessibility tree and leaves every nav link an icon with
   NO ACCESSIBLE NAME — a nav that reads as a column of blank links. This keeps
   it announced and takes it out of the visual flow, which is the whole point of
   that pattern. `app.js` adds `title` for the sighted equivalent. */
[data-vz-nav="collapsed"] .vz-body > .vz-nav li > a > span,
[data-vz-nav="collapsed"] .vz-body > .vz-nav li > span > span {
  position: absolute;
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip: rect(0, 0, 0, 0);
  white-space: nowrap;
  border: 0;
}

/* The glyph takes the whole row, so the icons form one column rather than
   sitting left of empty space. */
[data-vz-nav="collapsed"] .vz-body > .vz-nav li > a,
[data-vz-nav="collapsed"] .vz-body > .vz-nav li > span {
  justify-content: center;
  padding-left: var(--vz-space-2);
  padding-right: var(--vz-space-2);
}

/* ⚠ THE GROUP HEADING GOES, AND IT IS THE ONE THING THAT CANNOT SURVIVE.
   "Chit operations" has no glyph and no abbreviation that means anything at
   56px. `visibility: hidden` would keep its box and leave a gap the reader
   cannot explain, so the heading is removed from the layout entirely and the
   groups read as icon clusters separated by their existing margin. */
[data-vz-nav="collapsed"] .vz-body > .vz-nav .vz-nav-heading { display: none; }

/* ⛔ AND THE 'NOT BUILT' DOT GOES WITH THE LABEL IT QUALIFIED. `li > span::after`
   renders a `·` meaning "this module has no screen yet" — beside a bare glyph it
   is a mark with nothing to attach to, and `layouts/app.php` records that the
   dot's whole job is telling the truth about a LABEL. The muted colour on the
   icon still distinguishes an unbuilt module. */
[data-vz-nav="collapsed"] .vz-body > .vz-nav li > span::after { content: none; }

/* The toggle itself. ⚠ It ships `hidden` and `nav-state.js` reveals it, so a
   reader with no JavaScript is never offered a control that cannot work —
   `app.js`'s standing rule that deleting it leaves a working product. */
.vz-nav-toggle {
  display: flex;
  align-items: center;
  gap: var(--vz-space-3);
  width: calc(100% - var(--vz-space-5) * 2);
  margin: 0 var(--vz-space-5) var(--vz-space-4);
  padding: var(--vz-space-2);
  min-height: var(--vz-tap-min);
  box-sizing: border-box;
  background: none;
  border: 1px solid var(--vz-border);
  border-radius: var(--vz-radius-sm, 4px);
  color: var(--vz-muted);
  font: inherit;
  font-size: var(--vz-fs-sm);
  cursor: pointer;
}

.vz-nav-toggle:hover { background: var(--vz-surface-2); color: var(--vz-ink); }
.vz-nav-toggle:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: 2px; }

.vz-nav-toggle-icon { width: 20px; height: 20px; flex: none; }

[data-vz-nav="collapsed"] .vz-nav-toggle {
  justify-content: center;
  width: calc(100% - var(--vz-space-2) * 2);
  margin-left: var(--vz-space-2);
  margin-right: var(--vz-space-2);
}

/* ⚠ TWO LABELS IN THE MARKUP, ONE SHOWN PER STATE — AND THAT IS AN i18n
   DECISION RATHER THAN A CSS TRICK. The button's accessible name has to stay
   truthful in both states ("Collapse menu" announced while the menu is already
   collapsed is worse than no name), and the alternative — having `app.js` swap
   the text — would put two user-facing English strings inside a JavaScript file,
   where no locale catalogue can reach them. `DECISIONS_LOG`: no user-facing
   string in this product is ever hard-coded. So both live in `app.php` /
   `admin.php` and the stylesheet chooses. */
/* ⚠ THE LABEL IS THE PART THAT GIVES, SO THE GLYPH NEVER DOES. `.vz-nav-toggle-icon`
   is `flex: none`; without a `min-width: 0` here a long translated label would refuse
   to shrink below its min-content width and push the button past the collapsed
   column. `§6`'s step 7 names the case out loud: Malayalam's compound words stress a
   narrow column harder than English ever does, and this button is the narrowest thing
   in the shell. Ellipsis rather than a wrap, because a two-line control in a fixed-
   height row is `§E6e`'s stacked-actions defect one component along. */
.vz-nav-toggle-label {
  min-width: 0;
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
}

.vz-nav-toggle-label--expand { display: none; }

[data-vz-nav="collapsed"] .vz-nav-toggle-label--collapse { display: none; }
[data-vz-nav="collapsed"] .vz-nav-toggle-label--expand { display: inline; }

/* The visible label goes; the announced one stays. Same `.vz-sr-only` treatment
   the nav's own labels take, and for the same reason. */
[data-vz-nav="collapsed"] .vz-nav-toggle-label--expand {
  position: absolute;
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip: rect(0, 0, 0, 0);
  white-space: nowrap;
  border: 0;
}

.vz-nav-group { margin-bottom: var(--vz-space-5); }
.vz-nav-heading {
  padding: 0 var(--vz-space-5) var(--vz-space-2);
  font-size: var(--vz-fs-xs);
  text-transform: uppercase;
  letter-spacing: 0.08em;
  color: var(--vz-subtle);
  font-weight: var(--vz-fw-bold);
}
.vz-nav ul { list-style: none; margin: 0; padding: 0; }
/* ⚠ A ROW, NOT A BLOCK, SINCE E23 — the label now sits beside a glyph. `display: block`
   would leave the icon on its own line, and `.vz-nav li span` (an UNBUILT module, which
   is not a link) has to lay out the same way or the built and unbuilt entries in one
   list would not line up with each other. */
/* 🐛 ⚠ DIRECT CHILDREN ONLY, SINCE E23. The label is now wrapped in its own `<span>` so
   it can sit beside the glyph — and `.vz-nav li span` matched THAT too, giving every
   label a second nav row's worth of padding, min-height and transparent left border
   inside the first. Caught by looking at the rendered nav, where it showed as a stray
   mark after each word. `>` is what confines the rule to the row itself. */
.vz-nav li > a,
.vz-nav li > span {
  display: flex;
  align-items: center;
  gap: var(--vz-space-3);
  padding: var(--vz-space-2) var(--vz-space-5);
  color: var(--vz-muted);
  text-decoration: none;
  font-size: var(--vz-fs-sm);
  border-left: 3px solid transparent;
  min-height: var(--vz-tap-min);
  box-sizing: border-box;
  line-height: 1.6;
}
/* ⚠ THE GLYPH IS 20px AND `flex: none` — it must not shrink when a long module name
   wraps, and `.vz-icon`'s default `1.15em` would make it track the 13px label down to
   15px, which is under the size these were drawn to read at. */
.vz-nav-icon { width: 20px; height: 20px; flex: none; }

.vz-nav li > a:hover { background: var(--vz-surface-2); color: var(--vz-ink); }
.vz-nav li > a:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: -2px; }
/* The current page. State is carried by the BORDER and the weight, not by colour alone
   (WCAG 1.4.1) — which is the part that matters and has not changed.
   ⚠ THE SECOND CLAUSE USED TO READ "no green in the palette reaches 4.5:1 on both
   themes", and it is no longer the reason: since E5a `--vz-primary-strong` clears 4.5 on
   every surface. The text stays ink because **the border is already carrying the state**,
   and colouring the label as well would make "current" mean two things at once — which is
   what `1.4.1` is about in the first place. */
.vz-nav li > a[aria-current="page"] {
  border-left-color: var(--vz-primary);
  color: var(--vz-ink);
  background: var(--vz-surface-2);
  font-weight: var(--vz-fw-bold);
}
/* A module the user may read but whose screens are not built yet. Muted and
   non-interactive, so the nav tells the truth about what exists rather than
   offering links that 404. */
/* 🐛 ⚠ DIRECT CHILD, AND THIS ONE WAS NOT COSMETIC. The `·` is the marker that says a
   module has no screen yet — `layouts/app.php` records that *"a link means BUILT; a
   label means NOT YET"*, and the nav telling the truth about what exists is the whole
   reason `ModuleRoutes` is a single map a test walks. E23 wrapped every label in its own
   `<span>`, which `.vz-nav li span` matched — so **all eleven BUILT modules grew the
   'not built' dot**. Found by rendering the shell with every module readable and looking
   at it; nothing would have failed. */
.vz-nav li > span { color: var(--vz-subtle); cursor: default; }
.vz-nav li > span::after {
  content: "·";
  margin-left: var(--vz-space-2);
  color: var(--vz-border-strong);
}

.vz-main {
  flex: 1 1 auto;
  /* The right page edge in landscape — see `.vz-topbar` (E6+ item 3). The LEFT side is
     the sidebar's, above 48rem; below it the sidebar is gone and the media query at the
     end of this file gives this column both. */
  padding: var(--vz-space-6) max(var(--vz-space-5), env(safe-area-inset-right, 0px))
           var(--vz-space-6) var(--vz-space-5);
  max-width: 60rem;
  /* 🐛 ⚠ `min-width: 0` IS THE FIX FOR THE BAND BETWEEN THE BREAKPOINTS (E25 finding
     10). A flex item defaults to `min-width: auto`, so this one refused to shrink
     below the widest thing inside it and pushed the whole page sideways instead —
     from 769px (where the sidebar comes back) up to 940 on the members list and 1090
     on the chit wizard, by as much as 326px. The two check widths that bracket the
     band both measure clean, which is why it survived every measurement this phase
     has taken: at 768 the sidebar is gone and main has the screen to itself, and at
     1440 there is room for both.

     ⚠ IT IS ALSO WHAT MAKES THE EXISTING OVERFLOW FIXES WORK. `.vz-steps` has carried
     `overflow-x: auto` since the wizard was built and could never take effect: a
     scroll container cannot scroll content its own parent has already been widened
     to fit. With this, the steps rail scrolls inside itself as it was always meant
     to (measured 504px wide over 800px of content, at an 800px viewport). */
  min-width: 0;
}

/* ⚠ THE OLD MOBILE NAV WAS THIS, AND E21 REPLACED IT. `.vz-body` stacked, so the
   sidebar became a full-width block ABOVE the content: 830px of menu at 375, every
   screen. The bar below is what replaces it. */
@media (max-width: 48rem) {
  .vz-body { flex-direction: column; }

  /* ⚠ THE SIDEBAR IS HIDDEN HERE, SO THE CONTENT COLUMN INHERITS THE LEFT EDGE (E6+
     item 3). Without this the landscape notch would sit over the first character of
     every page title on a phone — the defect `viewport-fit=cover` introduces and
     `max()` is what pays for. */
  .vz-main {
    padding-left: max(var(--vz-space-5), env(safe-area-inset-left, 0px));
  }
}
/* ===========================================================================
   The phone's bottom bar and its drawer (E21)
   ---------------------------------------------------------------------------
   ⚠ MEASURED BEFORE IT WAS BUILT: at 375×812 the sidebar was 830px tall — taller
   than the screen — and content started 1,049px down, on every screen, every time.

   ⚠ BOTH NAVIGATIONS ARE IN THE DOM AND EXACTLY ONE IS DISPLAYED. `display: none`
   removes an element from the accessibility tree, so there are never two navigation
   landmarks at once — which is why they can safely carry different labels rather
   than one being hidden with `aria-hidden` and going stale.
   =========================================================================== */
.vz-tabbar { display: none; }

@media (max-width: 48rem) {
  /* ⚠ THE SIDEBAR INSTANCE, BY POSITION — not `.vz-nav` by name. The drawer sheet
     wears the same class so it inherits every nav rule, and hiding the name would
     hide the drawer with it. */
  .vz-body > .vz-nav { display: none; }

  .vz-tabbar {
    display: flex;
    position: fixed;
    inset: auto 0 0 0;
    /* ⚠ BELOW THE COMBO PANEL (1100) AND THE PROGRESS BAR (2000), ABOVE THE PAGE.
       A dropdown opened near the bottom of the screen must render OVER the bar, or
       its last options are unreachable on the device where the bar exists. */
    z-index: 900;
    background: var(--vz-surface);
    border-top: 1px solid var(--vz-border);
    /* The home indicator on a modern phone sits inside the viewport. Without this the
       last 34px of the bar is under it and the tabs are hard to hit.

       🐛 ⚠ AND UNTIL E6+ IT RESOLVED TO `0px` ON EVERY DEVICE, because neither layout
       declared `viewport-fit=cover` — without which the browser lays the page out INSIDE
       the safe area and every `env()` inset is zero by definition. The rule was correct
       and had never once fired. `layouts/app.php` carries the finding. */
    padding-bottom: env(safe-area-inset-bottom, 0px);
    padding-left: env(safe-area-inset-left, 0px);
    padding-right: env(safe-area-inset-right, 0px);
  }

  .vz-tab {
    flex: 1 1 0;
    min-width: 0;
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: center;
    gap: 2px;
    min-height: var(--vz-tap-min);
    padding: var(--vz-space-2) var(--vz-space-1);
    color: var(--vz-muted);
    text-decoration: none;
    font-size: var(--vz-fs-xs);
    /* `<summary>` draws a disclosure triangle in every browser; the More tab is a tab. */
    list-style: none;
    cursor: pointer;
  }

  .vz-tab::-webkit-details-marker { display: none; }
  .vz-tab-icon { width: 22px; height: 22px; flex: none; }

  /* ⚠ THE LABEL MUST NOT WRAP OR THE BAR'S ROWS STOP LINING UP. At 375 a fifth of the
     width is ~71px, and "Settlements" does not fit — it is truncated rather than
     wrapped, because a two-line tab beside four one-line tabs is a bar that looks
     broken. The full word is one tap away in the drawer. */
  .vz-tab-label {
    max-width: 100%;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
  }

  /* State is the ink AND the weight, never colour alone (WCAG 1.4.1) — the same rule
     the sidebar's left border follows. */
  .vz-tab[aria-current="page"] {
    color: var(--vz-primary-strong);
    font-weight: var(--vz-fw-medium);
  }

  .vz-tab:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: -2px; }

  .vz-tabbar-more { flex: 1 1 0; min-width: 0; display: flex; }
  .vz-tabbar-more > summary { flex: 1 1 auto; }

  /* The open drawer's chevron points the other way — the control says what the next
     tap does. No transition: E13 fixed the motion layer as colour only. */
  .vz-tabbar-more[open] > summary .vz-tab-icon { transform: rotate(180deg); }

  /* 🐛 THE DRAWER COVERED THE ONLY CONTROL THAT CLOSES IT (owner's phone, 2026-11-04). The
     scrim sat over the bar, so More could not be tapped and a page link was the only way
     out. Lifting the summary above the drawer closes it with no script at all, which is
     this bar's standing rule; `app.js` adds a tap on the scrim on top of that. */
  .vz-tabbar-more[open] > summary {
    position: relative;
    z-index: 951;
    background: var(--vz-surface);
  }

  /* The scrim. `<details>` has no "click outside to close" of its own. */
  .vz-drawer {
    position: fixed;
    inset: 0;
    z-index: 950;
    background: rgba(15, 20, 14, 0.45);
    display: flex;
    align-items: flex-end;
  }

  .vz-drawer-sheet {
    /* Inherited from `.vz-nav`: a 15rem fixed column with a right border. */
    flex: none;
    border-right: 0;
    width: 100%;
    max-height: 70vh;
    overflow-y: auto;
    background: var(--vz-surface);
    border-top-left-radius: var(--vz-radius-lg);
    border-top-right-radius: var(--vz-radius-lg);
    padding: var(--vz-space-5) 0 calc(var(--vz-tap-min) + env(safe-area-inset-bottom, 0px));
    box-shadow: var(--vz-shadow-md);
  }

  /* 🐛 ⚠ WITHOUT THIS THE LAST ROW OF EVERY LIST SITS UNDER THE BAR. A fixed element is
     out of flow, so the page does not know it is there — and the failure is invisible to
     an overflow check because nothing overflows: the content is simply covered. It is the
     single most likely way this row could have shipped broken. */
  .vz-main {
    padding: var(--vz-space-5) var(--vz-space-4);
    padding-bottom: calc(var(--vz-tap-min) + var(--vz-space-5) + env(safe-area-inset-bottom, 0px));
  }
}


/* --- The navigation progress bar (E19) ------------------------------------ */

/* ⚠ IT EXISTS BECAUSE A SERVER-RENDERED PAGE HAS NO OTHER WAY TO SAY "WORKING".
   Every screen in this product is a full page load; between the click and the
   next paint the browser shows only its own tab spinner, which on a phone is
   somewhere the user is not looking. `app.js` builds this element — nothing
   renders it server-side. */
.vz-progress {
  position: fixed;
  inset: 0 0 auto 0;
  height: 3px;
  z-index: 2000;          /* above the topbar and the combo panel; dialogs are
                             in the browser's top layer and stay above it */
  overflow: hidden;
  pointer-events: none;
  opacity: 0;
  transition: opacity var(--vz-transition);
}

.vz-progress.is-active { opacity: 1; }

.vz-progress-bar {
  height: 100%;
  width: 35%;
  border-radius: 0 var(--vz-radius-pill) var(--vz-radius-pill) 0;
  background: var(--vz-primary);
  animation: vz-progress-slide 1.1s ease-in-out infinite;
}

@keyframes vz-progress-slide {
  from { transform: translateX(-120%); }
  to   { transform: translateX(320%); }
}

/* 🐛 ⚠ WITHOUT THIS, REDUCED MOTION MEANS NO FEEDBACK AT ALL — AND THAT IS THIS
   PRODUCT'S OWN RULE BITING A NEW COMPONENT. `module.css` honours
   `prefers-reduced-motion` globally by forcing every animation to `0.01ms` with
   `animation-iteration-count: 1`, which is right for a decorative flourish and
   wrong for a looping indicator: the bar would run once, instantly, and come to
   rest at `translateX(320%)` — off the screen. A user who asked for less motion
   would click Save and see nothing whatsoever.

   Finance solves it by slowing its animation to 2.2s. That is not available here,
   because the global rule is `!important`, and it should not be: the answer is not
   slower movement, it is **no movement and the same information**. A static
   full-width bar says "working" without moving anything. */
@media (prefers-reduced-motion: reduce) {
  .vz-progress-bar {
    width: 100%;
    transform: none;
    animation: none;
  }
}

/* --- Auth screens: the card, and nothing that is a component ------------- */
.vz-auth-wrap {
  min-height: 100vh;
  display: flex;
  /* ⚠ COLUMN SINCE E2. It centred a single card when it was a row; it now stacks the
     lockup, the card and the footer, and leaving it a row would have laid all three
     out side by side. */
  flex-direction: column;
  align-items: center;
  justify-content: center;
  padding: var(--vz-space-5);
  box-sizing: border-box;
}
/* The lockup above the card (E2). `color` is the wordmark — see partials/brand.php. */
/* ⚠ FINANCE'S `.vz-auth__brand`: INSIDE THE CARD, CENTRED (E14). It used to sit above the
   card, at 40px, on the argument that *"the card is the form; the mark is the product"* —
   and side by side with the finance portal that reads as a different application rather
   than a considered difference. Finance puts the lockup at the top of the card at its
   normal 32px with `space-5` beneath it, and every screen in that product does the same. */
/* ⚠ THE `gap` IS LOAD-BEARING HERE AND NOT IN THE APP SHELL. `partials/brand.php` emits a
   bare `<img>` + `<span>` with no wrapper of its own, so whatever contains it supplies the
   spacing: in `layouts/app.php` that is `<a class="vz-brand">`, which has the gap. This
   container has to carry its own, and the first version of this rule dropped it — the tile
   and the wordmark rendered touching, as "₹Vazhai Chit". Caught by looking at the page. */
.vz-auth-brand {
  display: flex;
  justify-content: center;
  align-items: center;
  gap: var(--vz-space-2);
  margin-bottom: var(--vz-space-5);
  color: var(--vz-ink);
}

/* ⚠ THE AUTH FOOTER CARRIES ITS OWN RULES BECAUSE THIS LAYOUT DOES NOT LOAD
   `module.css` — see `PHASE_E §E3` Finding 2, which is the row that resolves that
   split. Until it does, duplicating five declarations here is the honest cost of the
   divide, and it is recorded rather than hidden. */
/* ⚠ THE AUTH FOOTER IS NOT A BAR, IT IS A CAPTION. The base `.vz-footer` is chrome
   that CLOSES a full-width page — surface background, top border, page padding. Below a
   360px centred card that reads as a second, narrower card floating under the first,
   which is what it looked like the moment auth started sharing this vocabulary. The
   modifier strips the frame and keeps only the type. */
.vz-footer--auth {
  background: none;
  border-top: 0;
  padding: 0;
  margin-top: var(--vz-space-5);
  display: flex;
  flex-direction: column;
  gap: var(--vz-space-1);
  font-size: var(--vz-fs-xs);
  color: var(--vz-subtle);
  text-align: center;
}
.vz-footer--auth p { margin: 0; }
.vz-footer--auth a {
  color: var(--vz-primary-strong);
  font-weight: var(--vz-fw-medium);
  display: inline-flex;
  align-items: center;
  min-height: var(--vz-tap-min);
}

.vz-auth-card {
  width: 100%;
  max-width: 24rem;
  background: var(--vz-surface);
  border: 1px solid var(--vz-border);
  border-radius: var(--vz-radius-lg);
  box-shadow: var(--vz-shadow-md);
  padding: var(--vz-space-6);
  box-sizing: border-box;
}
/* ⚠ FINANCE'S `.vz-auth__title` / `.vz-auth__subtitle`, MATCHED (E14). Three things were
   different and all three were reported: the size (`--vz-fs-h1` 18px against Finance's
   `--vz-fs-display` 22px), the COLOUR (green against ink), and the ALIGNMENT (left
   against centred). The finance portal centres a 22px ink heading over a centred
   secondary subtitle, which is what makes its card read as a door rather than as a form
   somebody started filling in. */
/* 🔴 WHICH DOOR THIS IS (`§7` 39's F20). Sits above the heading, because a reader deciding
   whether they are in the right place should not have to read a heading and a subtitle first.
   ⚠ It borrows `.vz-branch`'s VOCABULARY — quiet, uppercase, letter-spaced, muted — rather
   than the class itself: the chrome's chip is a flex control with a caret and a switcher
   behind it, and none of that exists on a door nobody has come through yet. Same voice,
   without pretending to be the same control.

   ⛔ AND THE CLASS MAY NOT CONTAIN THE WORD "PORTAL". `LoginFlowTest` asserts that string
   appears nowhere in a sign-in response, so that a credential valid at the other door returns
   the generic refusal rather than confirming the account exists. `.vz-auth-portal` was the
   first spelling and it leaked the word through a class attribute. */
.vz-auth-scope {
  margin: 0 0 var(--vz-space-2);
  color: var(--vz-muted);
  font-size: var(--vz-fs-xs);
  font-weight: var(--vz-fw-medium);
  letter-spacing: .08em;
  text-transform: uppercase;
  text-align: center;
}

.vz-auth-title {
  margin: 0;
  font-size: var(--vz-fs-display);
  font-weight: var(--vz-fw-bold);
  color: var(--vz-ink);
  line-height: var(--vz-lh-tight);
  text-align: center;
}
.vz-auth-sub {
  margin: var(--vz-space-2) 0 var(--vz-space-5);
  color: var(--vz-muted);
  font-size: var(--vz-fs-sm);
  text-align: center;
}

/* ⚠ FIELD SPACING INSIDE THE AUTH CARD, AND ONLY THERE (E3).
   `module.css`'s `.vz-field` is a bare flex column with no outer margin, because in the
   app every field sits in a `.vz-form-grid` whose `gap` does the spacing. The auth card
   is a single narrow column with no grid, so the rhythm the old `.vz-alert`-era rule
   provided (`margin-bottom: var(--vz-space-4)`) has to come from somewhere — here,
   scoped to the card, rather than by giving every `.vz-field` in the product a margin
   that the grid would then have to cancel. */
.vz-auth-card .vz-field + .vz-field,
.vz-auth-card .vz-field { margin-bottom: var(--vz-space-4); }
.vz-auth-card .vz-field:last-of-type { margin-bottom: var(--vz-space-5); }

/* The callout inside the card carries the same rhythm as a field. */
.vz-auth-card .vz-callout { margin-bottom: var(--vz-space-4); }

/* WHOSE session is locked (E16) — the one line on an auth card that names a person.
   ⚠ CENTRED, BECAUSE EVERYTHING ELSE ON THIS CARD IS. It was a left-aligned paragraph
   between a centred title and a centred subtitle, carried by a `style` attribute, and
   it read as a stray rather than as part of the lockup — `.vz-auth-note` records the
   same argument for the line under the button. Ink and medium weight because it is the
   answer to "is this still me?", which is the whole reason the lock screen shows it. */
.vz-auth-who {
  margin: 0 0 var(--vz-space-4);
  text-align: center;
  font-weight: var(--vz-fw-medium);
  color: var(--vz-ink);
}

/* The Vazhai house mark beside the word in the footer attribution (E2, revised).
   Inline-flex with a baseline-ish gap so the 16px tile sits ON the text line rather than
   above it, and the whole thing stays one 44px tap target. */
.vz-footer-mark {
  display: inline-flex;
  align-items: center;
  gap: var(--vz-space-1);
}
.vz-footer-mark img { display: block; border-radius: 3px; width: 18px; height: 18px; }

/* The line under the form — the reset link, the "ask your administrator" note (E14), or
   since E16 the sign-out `<form>` on the lock and forced-change screens, whose control is
   `layouts/app.php`'s own `.vz-linkbtn`. Both of those were six inline declarations each
   describing a link-shaped button this product already had a class for.
   ⚠ IT REPLACES TWO INLINE `style` ATTRIBUTES, which is `OPERATING_MODE §7` item 24
   shrinking by two rather than growing. Centred, because in the finance portal everything
   under the button is centred and a left-aligned trailing line reads as a stray. */
/* 🔴 **ORDINARY TEXT, NOT FINE PRINT** (owner, 2026-10-13: *"make the auth-note bigger"*).
   This was `--vz-fs-sm` (13px) against a `body` of `--vz-fs-base` (14px) — one step BELOW the
   body, which is what made the lock screen's sign-out read as small however it was coloured.
   ▶ Matching the body size is what "not too small" means structurally.

   ⚠ **THIRTEEN SCREENS, NOT TWO** — every signed-out surface: the two login pages, the lock
   screen, both forgot flows, set-password and its done and invalid states, the branch picker
   and the offline page. ⛔ `--vz-fs-md` (16px) was the other candidate and is wrong: a secondary
   note larger than the copy it sits under inverts the hierarchy, thirteen times. */
.vz-auth-note {
  margin: var(--vz-space-4) 0 0;
  text-align: center;
  color: var(--vz-muted);
  font-size: var(--vz-fs-base);
}

/* ── PASSKEY SIGN-IN ABOVE THE MEMBER FORM (2026-11-18) ──────────────────────────────
   The passkey button, a status line for "that did not complete", and an "or" rule that
   separates it from the code-and-password form. The rule is two hairlines either side of the
   word, so it reads as a choice between two ways in rather than as a section break. */
/* ⚠ `:not([hidden])`: the block ships hidden and `app.js` reveals it. A bare `display: grid`
   would outrank the browser's own `[hidden] { display: none }` and show a passkey button on
   a browser that cannot use one — `layouts/portal.php` records the same trap on the nav
   toggle. */
.vz-passkey-sign-in:not([hidden]),
.vz-passkey-panel:not([hidden]) {
  display: grid;
  gap: var(--vz-space-2);
}

.vz-passkey-sign-in .vz-field-hint:empty,
.vz-passkey-panel .vz-field-hint:empty {
  display: none;
}

/* The profile's set-up form: the question, its hint and the button each need air between them
   (found driving, 2026-11-18: the legend sat flush under "You have not set up a passkey" and
   the button touched the hint). `start` keeps the button its own width, not the panel's. */
.vz-passkey-panel {
  margin-top: var(--vz-space-4);
}

.vz-passkey-panel form {
  display: grid;
  gap: var(--vz-space-3);
  justify-items: start;
}

.vz-passkey-panel .vz-choices {
  justify-self: stretch;
}

/* Staff Account security's add form (found driving, 2026-11-18): the question, its hint, the
   password and the button are siblings across the form's edge — the password box sits OUTSIDE
   the form on purpose — so one grid spaces all of them alike. Without it the choices kept their
   own bottom margin on top of the gap, and the password label sat flush under the hint. */
.vz-passkey-add-body {
  display: grid;
  gap: var(--vz-space-3);
  margin-top: var(--vz-space-3);
}

.vz-passkey-add-body form {
  justify-items: stretch;
}

.vz-passkey-add-body .vz-choices,
.vz-passkey-add-body .vz-field {
  margin: 0;
}

/* "Where do you want to keep this passkey?" (`partials/passkey-place`, owner 2026-11-18). Each
   choice is a title, what it is for, and — for the chosen one only — what the browser shows
   next, so the dialog that follows is expected rather than a surprise. The radio sits against
   the title, not the middle of three lines. */
.vz-passkey-places .vz-choice { align-items: flex-start; }
.vz-passkey-places .vz-choice .vz-check-input { margin-top: 2px; }
.vz-passkey-places .vz-choice-label { display: grid; gap: 2px; min-width: 0; }
.vz-passkey-place-note { font-size: var(--vz-fs-xs); color: var(--vz-muted); }
.vz-passkey-place-next { font-size: var(--vz-fs-xs); color: var(--vz-ink); }
.vz-passkey-places .vz-choice:not(:has(:checked)) .vz-passkey-place-next { display: none; }

/* What went wrong, in red (`partials/passkey-feedback`, owner 2026-11-18: "error is not clearly
   visible"). ⚠ `.vz-callout` sets `display`, which beats the browser's own `[hidden]`. */
.vz-passkey-feedback { margin: 0; }
.vz-passkey-feedback[hidden] { display: none; }

/* "Is your passkey on your phone?" under a passkey button (`partials/passkey-phone-help`). One
   quiet line until opened. ⚠ NOT ON A TOUCH SCREEN: there the passkey is on the device in hand
   and there is no QR code to scan. */
.vz-passkey-phone-help { font-size: var(--vz-fs-sm); color: var(--vz-muted); }
.vz-passkey-phone-help > summary { cursor: pointer; color: var(--vz-primary-strong); }
.vz-passkey-phone-help > ol { margin: var(--vz-space-2) 0 var(--vz-space-1); padding-left: var(--vz-space-5); }
.vz-passkey-phone-help > ol > li + li { margin-top: var(--vz-space-1); }
.vz-passkey-phone-help > p { margin: 0; }

@media (hover: none) and (pointer: coarse) {
  .vz-passkey-phone-help { display: none; }
}

.vz-auth-divider {
  display: flex;
  align-items: center;
  gap: var(--vz-space-3);
  margin: var(--vz-space-3) 0 var(--vz-space-4);
  color: var(--vz-muted);
  font-size: var(--vz-fs-sm);
}

.vz-auth-divider::before,
.vz-auth-divider::after {
  content: "";
  flex: 1;
  min-width: 0;
  border-top: 1px solid var(--vz-border);
}

.vz-auth-note a {
  color: var(--vz-primary-strong);
  font-weight: var(--vz-fw-medium);
  display: inline-flex;
  align-items: center;
  min-height: var(--vz-tap-min);
}

/* ===========================================================================
   The notification bell (§Q-R12, OPERATING_MODE §7 item 81)
   ---------------------------------------------------------------------------
   `SCHEMA_MASTER §11` has asked for "every operator app's notification center"
   since S3e and this topbar had no bell until 2026-09-15.

   ⚠ IT IS A `<details>`, LIKE THE BRANCH SWITCHER AND THE USER MENU, and it
   REUSES `.vz-menu` for the panel rather than growing a third dropdown. Those
   two share that class because "a dropdown that looks like one thing under the
   branch and another under the name is two components to learn"; a third one
   that looked like neither would be the same argument ignored.
   =========================================================================== */

.vz-bell { position: relative; }

/* `<summary>` draws a disclosure triangle in every browser; this is an icon button. */
.vz-bell > summary { list-style: none; cursor: pointer; }
.vz-bell > summary::-webkit-details-marker { display: none; }
.vz-bell > summary:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: 2px; }

/* ⚠ THE WHOLE SUMMARY IS THE TARGET AND IT IS SQUARE AT `--vz-tap-min`. `OPERATING_MODE §7`
   item 20 is two controls under that floor already (`.vz-help-toggle` at 26px and
   `.vz-c-name a` at 25px); a 20px bell glyph with no box around it would have been the
   third, on the one control that appears on EVERY screen in the product. */
.vz-bell-btn {
  position: relative;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-width: var(--vz-tap-min);
  min-height: var(--vz-tap-min);
  color: var(--vz-muted);
}

.vz-bell-btn:hover { color: var(--vz-ink); }
.vz-bell-icon { width: 20px; height: 20px; flex: none; }

/* 🔴 THE CONTEXTUAL HELP ICON (`§7` item 107), AND IT REUSES THE BELL'S BOX DELIBERATELY.
   Two icon-only controls sitting beside each other in one bar have to be the same size or
   the row reads as a mistake — and `--vz-tap-min` is the floor the responsive pass measures
   every control against, so a second set of numbers here would be a second thing to prove.
   ⚠ IT IS AN `<a>` RATHER THAN A `<summary>`: the guide is a page, not a disclosure, so
   there is nothing to open in place. */
.vz-topbar-help {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-width: var(--vz-tap-min);
  min-height: var(--vz-tap-min);
  color: var(--vz-muted);
}

.vz-topbar-help:hover { color: var(--vz-ink); }

/* ⚠ THE RING IS EXPLICIT BECAUSE AN ICON-ONLY LINK HAS NO TEXT FOR A DEFAULT OUTLINE TO
   HUG. The bell's `<summary>` inherits one from `.vz-topbar details > summary`; an anchor
   here does not, and E16's rule is that every focusable control in this product shows where
   focus is. */
.vz-topbar-help:focus-visible {
  outline: 2px solid var(--vz-primary);
  outline-offset: 2px;
  border-radius: var(--vz-radius-sm);
}

.vz-topbar-help-icon { width: 20px; height: 20px; flex: none; }

/* 🔴 THE CALENDAR ICON (owner, 2026-11-19), THE SAME BOX AS THE HELP ICON AND THE BELL — three
   icon-only controls in one row must be one size. */
.vz-topbar-cal {
  position: relative;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-width: var(--vz-tap-min);
  min-height: var(--vz-tap-min);
  color: var(--vz-muted);
}

.vz-topbar-cal:hover { color: var(--vz-ink); }

.vz-topbar-cal:focus-visible {
  outline: 2px solid var(--vz-primary);
  outline-offset: 2px;
  border-radius: var(--vz-radius-sm);
}

/* ⚠ THE PRIMARY BUTTON'S MEASURED PAIR, NOT A NEW ONE — a count of today's work is not an
   alarm, so it is green rather than the bell's red. `box-sizing` for the bell's reason. */
.vz-topbar-cal-count {
  position: absolute;
  top: 4px;
  right: 2px;
  box-sizing: border-box;
  min-width: 18px;
  padding: 0 var(--vz-space-1);
  border-radius: var(--vz-radius-pill);
  background: var(--vz-primary-button);
  color: var(--vz-primary-contrast);
  font-size: var(--vz-fs-xs);
  font-weight: var(--vz-fw-bold);
  line-height: 18px;
  text-align: center;
}

/* ⚠ THE ICON ROW SITS CLOSER THAN THE REST OF THE BAR (owner, 2026-11-19). Each control is a
   44px box around a 20px glyph, so the bar's 16px gap read as three separate islands; 4px
   keeps them a group while every box stays at the tap floor. */
.vz-topbar-help + .vz-topbar-cal,
.vz-topbar-help + .vz-bell,
.vz-topbar-cal + .vz-bell {
  margin-left: calc(var(--vz-space-1) - var(--vz-space-4));
}

/* 🔴 THE COUNT, AND IT IS A MEASURED CONTRAST PAIR RATHER THAN A CHOSEN ONE.
   `--vz-danger-button` under `--vz-primary-contrast` is what `.vz-action--danger-solid`
   already paints and `ThemeContrastTest::testEveryFilledComponentThatCarriesTextIsAMeasuredPair`
   already measures — including for every hue `BrandPalette::derive()` can produce from an
   operator's own colour. A NEW pair here would be a new thing to prove, and `§E12` is what
   happens when a stylesheet paints text in a token nobody measured for it.

   ⚠ `box-sizing` IS LOAD-BEARING: a min-width plus horizontal padding is exactly the pair
   `StylesheetStaticTest::testEveryRuleThatSizesAndPadsSaysWhichBoxItMeans` exists for, and
   without it a two-digit count is 18px PLUS 10px rather than at least 18px.

   ⚠ AND IT IS `aria-hidden` IN THE MARKUP, with the number in the summary's own label — a
   bare numeral announced after "Notifications" is two unrelated things to a screen reader. */
.vz-bell-count {
  position: absolute;
  top: 4px;
  right: 2px;
  box-sizing: border-box;
  min-width: 18px;
  padding: 0 var(--vz-space-1);
  border-radius: var(--vz-radius-pill);
  background: var(--vz-danger-button);
  color: var(--vz-primary-contrast);
  font-size: var(--vz-fs-xs);
  font-weight: var(--vz-fw-bold);
  line-height: 18px;
  text-align: center;
}

/* ⚠ WIDER THAN `.vz-menu`'s 12rem, BECAUSE THESE ROWS CARRY A SENTENCE RATHER THAN A WORD.
   `min()` against the viewport is what keeps that honest at 320: a fixed 22rem panel hanging
   off a right-aligned trigger would push the page sideways on the narrowest phone, which is
   `§E6+` item 1's defect in a dropdown. */
.vz-bell-menu {
  box-sizing: border-box;
  min-width: min(22rem, calc(100vw - var(--vz-space-5) * 2));
  max-width: calc(100vw - var(--vz-space-4));
}

/* A row is two lines — the title and its marks — so it is a grid rather than `.vz-menu-item`'s
   single-line flex. `text-decoration: none` and the inherited colour are what a browser would
   otherwise put back, and a panel with one underlined blue row reads as two kinds of thing. */
.vz-bell-item {
  display: block;
  padding: var(--vz-space-2) var(--vz-space-3);
  border-radius: var(--vz-radius-sm);
  color: inherit;
  text-decoration: none;
}

.vz-bell-item:hover { background: var(--vz-surface-2); }
.vz-bell-item:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: 2px; }

/* ⚠ CLAMPED TO TWO LINES RATHER THAN ELLIPSED ON ONE. `announcement_translations.title` is
   VARCHAR(200) and a maintenance notice routinely uses most of it; one line plus an ellipsis
   would truncate at about five words, and `§P5`'s `.vz-combo-label` finding is that a silent
   truncation reads as a shorter title rather than as a cut one. */
.vz-bell-title {
  display: -webkit-box;
  -webkit-line-clamp: 2;
  -webkit-box-orient: vertical;
  overflow: hidden;
  font-weight: var(--vz-fw-medium);
  line-height: var(--vz-lh-tight);
}

.vz-bell-meta {
  display: block;
  margin-top: 2px;
  color: var(--vz-muted);
  font-size: var(--vz-fs-xs);
}

/* An empty dropdown reads as a control that failed to load, so it says so instead. */
.vz-bell-empty {
  margin: 0;
  padding: var(--vz-space-2) var(--vz-space-3);
  color: var(--vz-muted);
  font-size: var(--vz-fs-sm);
}

/* ⚠ RENDERED EVEN WHEN THE LIST IS EMPTY. The bell shows what is still showing; everything
   dismissed, acknowledged, archived or expired is on that page under *Earlier*. */
.vz-bell-more {
  display: flex;
  align-items: center;
  min-height: var(--vz-tap-min);
  margin-top: var(--vz-space-1);
  padding: 0 var(--vz-space-3);
  border-top: 1px solid var(--vz-border);
  color: var(--vz-primary-strong);
  font-size: var(--vz-fs-sm);
  font-weight: var(--vz-fw-medium);
  text-decoration: none;
}

.vz-bell-more:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: 2px; }

/* 🐛🔴 THE DEFECT THE `§E6` SWEEP FOUND, AND IT READ AS **ZERO PAGE OVERFLOW** THE WHOLE TIME.
   Measured at 320 with every `<details>` forced open: the bell's panel sat at
   **left: -220px, right: 60px** — 220px of it off the left edge of the screen, unreachable —
   while `documentElement.scrollWidth - clientWidth` read **0 at every width from 320 to 1440**.
   ▶ **A box that overflows to the LEFT does not extend `scrollWidth`**, so the page sweep is
   blind to it by construction. This is `§E6`'s "a sweep reading zero is not the same as the
   screen being right" in its cheapest-to-miss form.

   ⚠ THE CAUSE IS NOT THE WIDTH — IT IS WHERE THE TRIGGER LANDS. `.vz-topbar` is
   `flex-wrap: wrap`, and at 320 it wraps: the bell ends up at the FAR LEFT of a second row
   (host right edge at x=60) with a panel right-aligned to it. Any panel wider than 60px hangs
   off the screen from there.

   ✅ AND THE CONTROL IS WHAT PROVED IT WAS MINE. `.vz-account-menu`'s panel at the same width
   measured **left: 24, width: 202** — inside the viewport — because its host lands at x=226
   and its `min-width` is 12rem. **It is safe by accident of where it lands**, not by design,
   which is why the fix below anchors to the VIEWPORT rather than shrinking a number until the
   symptom goes.

   ▶ SO BELOW 30rem THE PANEL STOPS HANGING OFF ITS TRIGGER AND SPANS THE TOPBAR: `.vz-bell`
   goes `position: static`, which hands the containing block to `.vz-topbar`, and the panel
   pins to both edges of it. That is the standard phone sheet, and it cannot depend on where
   the flex row happened to put the bell.

   ⚠ THE BRANCH LABEL IS WHAT GIVES AT THIS BREAKPOINT AND THE BELL IS NOT, which is the order
   this topbar already argues: the branch chip keeps its NAME (somebody who has forgotten which
   branch they are in is one click from a wrong receipt) and loses the word "Branch"; the bell
   is a single square and has nothing left to drop. */
@media (max-width: 30rem) {
  .vz-bell { position: static; }

  .vz-bell-menu {
    left: var(--vz-space-2);
    right: var(--vz-space-2);
    min-width: 0;
    max-width: none;
  }

  .vz-bell-btn { min-width: 40px; }
}

/* 🐛🔴 `OPERATING_MODE §7` ITEM 87 — THE USER MENU HUNG OFF THE LEFT EDGE OF THE SCREEN, AND
   IT HAD DONE SINCE `§E22`. Same mechanism as the bell's above, on a control that is on **every
   authenticated screen in BOTH portals**: this bar is `flex-wrap: wrap`, so on a narrow screen
   the account chip wraps to a row of its own and lands at x≈20, and `.vz-menu` is
   `position: absolute; right: 0` of that chip — so a 202px panel is drawn from **x = −35**.

   🔴 **AND THE PAGE SWEEP IS BLIND TO IT BY CONSTRUCTION**: a box overflowing to the LEFT does
   not extend `scrollWidth`, so `documentElement.scrollWidth - clientWidth` read **0 at every
   width from 320 to 1440** while 35px of the menu was unreachable. Item 87 was raised by
   `§Q-R12`, which found the same shape on its own new bell and proved the account menu's was
   **pre-existing** by removing the bell from the DOM and re-measuring.

   ⚠ **40rem IS A MEASURED BOUNDARY, NOT A ROUND NUMBER PICKED BY EYE.** Stepping 320→900 one
   pixel at a time: the panel is off-screen up to **620** and clean from **621**, because that is
   where this bar stops wrapping. 40rem (640) is the next breakpoint this file already uses
   (`.vz-brand-mark`), so no new one is invented; the 621–640 band gets the sheet it does not
   strictly need, which is a dropdown pinned to the bar's edges rather than to a chip. */
@media (max-width: 40rem) {
  .vz-account-menu { position: static; }

  .vz-account-menu .vz-menu {
    left: var(--vz-space-2);
    right: var(--vz-space-2);
    min-width: 0;
  }
}

/* 🐛 THE MEMBER PORTAL READS ITS ROWS ACROSS THE OPERATOR'S COLUMN WIDTH
   (owner, 2026-09-28: *"landing page … the design wants his eye"*).

   `.vz-main` is `max-width: 60rem` — 960px — and that number is the OPERATOR's: a branch
   machine rendering nineteen-column registers. ⛔ **The member portal renders two-column
   rows**, and at 960 the `space-between` that puts the figure on the right leaves the
   reader crossing an empty page to pair a pill with the group it is about. **Measured at
   1440:**

       Kovai Monthly 1 Lakh  →  "Nothing due"          670px of nothing between them
       Kovai Monthly 1 Lakh  →  "₹4,250.00"            673
       Kovai Monthly 50K     →  "19 of 20 seats left"  585

   ▶ **AT 45rem THOSE HALVE** — 430, 433, 345 — and the two halves of a row read as one row.

   ── 🔴 45rem IS A FLOOR THAT WAS MEASURED, NOT A TASTE ────────────────────
   The widest thing this portal draws is the passbook's ledger table, and it is what sets
   the number. Measured on `/p/…/passbook/{id}` at a 1440 viewport:

       960px column  →  table 916px, wrap scroll 0
       720px column  →  table 676px, wrap scroll 0      ◀ shipped
       640px column  →  table 645px, wrap scroll 49px   ⛔ the passbook scrolls sideways

   ⚠ **A NARROWER COLUMN LOOKS BETTER ON THE LANDING SCREEN AND BREAKS THE PASSBOOK**, which
   is the whole reason this was driven across screens rather than tuned on the one that was
   reported. ▶ `a-fix-that-stops-one-element-short`.

   ⛔ **SCOPED TO `.vz-portal`. The operator app keeps its 60rem** — its registers need every
   pixel, and `F41`/`F82`'s band measurements were all taken against that number. */
.vz-portal .vz-main { max-width: 45rem; }

/* ===========================================================================
   THE MEMBER PORTAL'S NAVIGATION — REMOVED 2026-09-28, AND THAT IS THE RECORD
   ---------------------------------------------------------------------------
   ⛔ `.vz-portal-nav` AND ITS SIX RULES ARE GONE. The portal now renders the
   OPERATOR'S structure — `.vz-nav` rail above 48rem, `.vz-tabbar` below it —
   on the owner's request (*"Why the menu structure not changes like
   operator?"*), so every one of those rules matched nothing.

   ⚠ **DELETED RATHER THAN LEFT.** `F89` filed dead symbols as a finding in row
   17 of this same audit, and a stylesheet keeping rules for markup no view
   emits is the same defect in CSS. ▶ `StylesheetReachTest` would not have
   caught it: that guard asks whether every class a view renders HAS a rule,
   not whether every rule has a class — the arrow only points one way.

   🔴 AND THE ARGUMENT IT CARRIED IS WORTH KEEPING, BECAUSE HALF OF IT WAS THE
   MISTAKE. It read: *"`.vz-nav` is hidden below 48rem behind a JAVASCRIPT
   drawer … ▶ WHICH ALSO MEANS IT WORKS WITH JAVASCRIPT OFF"* — the whole case
   for a separate component. ⛔ **The operator's phone navigation is a
   `<details>` bottom bar and needs no script at all**; only the DESKTOP
   collapse is scripted, and without it the rail is simply always expanded.
   ▶ A component was built, styled and carried for two phases on a constraint
   that did not exist. `a-constant-is-not-a-symptom`, applied to a comment.
   =========================================================================== */

/* 🐛 THE MEMBER'S TAB LABELS WRAP; THE OPERATOR'S TRUNCATE. ONE RULE, AND THE REASON IS
   THAT THE PORTAL HAS NO DRAWER.

   `.vz-tab-label` is `white-space: nowrap` + ellipsis, and `layouts/app.php` states the
   mitigation at that rule: *"a two-line tab beside four one-line tabs is a bar that looks
   broken. **The full word is one tap away in the drawer.**"*

   ⛔ **THE PORTAL HAS NO DRAWER** — five destinations all fit in the bar, so there is no
   `.vz-tabbar-more` — and a truncated label here therefore has **nowhere to be read in
   full**. Measured at 320: four of five labels overflowed their box, "Auction results" by
   23px. The operator's escape hatch simply does not exist on this surface.

   ⚠ **AND THE "BAR LOOKS BROKEN" ARGUMENT DOES NOT APPLY EITHER**, which is why wrapping is
   available here and was not there. `.vz-tab` is `flex: 1 1 0` in a row, so every tab takes
   the row's height whatever its own label does: measured **68px on all five** at 320 and at
   375, with one-line and two-line labels side by side. The operator's own layout already
   guaranteed the thing its comment was worried about.

   🔴 **`overflow-wrap: normal` IS THE WHOLE CARE HERE.** With `break-word` or `anywhere`,
   "Notifications" — one unbreakable word in a 67px box — renders as **"Notificatio / ns"**,
   which is worse than a truncation because it looks like a rendering fault rather than an
   abbreviation. ▶ So words stay whole and the labels wrap and read in full.

   🐛 **AND A TAB IS NEVER NARROWER THAN ITS LONGEST WORD** (owner's drive, 2026-11-03: the
   bottom bar cut "Notifications" at 375px). `flex: 1 1 0` shares the row out equally, which
   left that one unbreakable word 67px in a box it needed more of, and the ellipsis was the
   only thing left. `min-width: min-content` lets the tab take what the word needs from its
   neighbours, whose labels wrap and can spare it. */
@media (max-width: 48rem) {
  .vz-portal .vz-tab {
    min-width: min-content;
  }

  .vz-portal .vz-tab-label {
    white-space: normal;
    overflow-wrap: normal;
    word-break: normal;
    line-height: 1.15;
    text-align: center;
  }
}

/* ===========================================================================
   The two-section sign-in door (owner, 2026-10-08) — `partials/auth-aside`
   ===========================================================================
   ⛔ EVERYTHING HERE IS SCOPED UNDER `.vz-auth-wrap--split`, WHICH ONLY A CONTROLLER
   THAT PASSED `$aside` PRODUCES. `/admin/login`, the lock screen, the branch picker and
   every reset step render `.vz-auth-wrap` unmodified and are untouched by this block —
   not by a rule that excludes them, but by never matching one.

   ⚠ NO CLASS NAME HERE MAY CONTAIN THE VENDOR-NEUTRAL WORD THE SUITE FORBIDS.
   `LoginFlowTest::testTheWrongPortalMessageIsTheGenericOne` asserts a certain word appears
   NOWHERE in a sign-in response body, and a class attribute is part of the body. The first
   spelling of the scope chip carried it, turned every login page into an account-
   enumeration hint, and nothing about the rendered screen looked wrong. */

.vz-auth-wrap--split {
  padding: 0;
  justify-content: flex-start;
  background: var(--vz-bg);
}

/* ── one section below 900px, two above ─────────────────────────────────
   900px clears the 768–950 band `OPERATING_MODE §7` item 63 already has trouble with,
   and leaves the form a comfortable measure rather than a squeezed one. */
@media (min-width: 56.25rem) {
  .vz-auth-wrap--split { flex-direction: row; align-items: stretch; }
}

/* --- the welcome section ------------------------------------------------- */

.vz-auth-aside {
  position: relative;
  overflow: hidden;
  box-sizing: border-box;
  display: flex;
  flex-direction: column;
  background: #35691f;
  color: #fff;
  /* ⚠ `max()` AGAINST THE SAFE-AREA INSETS, because the layout declares
     `viewport-fit=cover`: a full-bleed panel runs under the notch in landscape without
     this, and the lockup lands beneath the camera housing. */
  padding: var(--vz-space-5) max(var(--vz-space-5), env(safe-area-inset-left))
           var(--vz-space-5) max(var(--vz-space-5), env(safe-area-inset-left));
}

@media (min-width: 56.25rem) {
  .vz-auth-aside {
    box-sizing: border-box;
    flex: 0 0 52%;
    max-width: 660px;
    padding: var(--vz-space-7) var(--vz-space-7) var(--vz-space-6);
  }
}

.vz-auth-aside-brand { position: relative; z-index: 1; }

/* 🔴 THE WHITE PLATE, AND IT IS LOAD-BEARING RATHER THAN DECORATIVE.
   An operator mark renders `object-fit: contain` with `border-radius: 0` and NO background
   of its own, and `ImageRendition` keeps "PNG stays PNG and JPEG stays JPEG". On a dark
   panel that is two failures: a dark transparent PNG is nearly invisible, and a JPEG
   carries an opaque white rectangle with hard corners. The plate gives the first the white
   paper it was drawn for, and absorbs the second into itself.
   ▶ It is why nobody has to supply a "dark version" of a logo they will not have. */
.vz-auth-plate {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-height: 52px;
  padding: 10px 14px;
  box-sizing: border-box;
  background: #fff;
  border-radius: 10px;
}

/* The Vazhai lockup follows the same rule, and it is the REAL asset rather than a
   re-drawing: `partials/brand` emits an <img>-loaded SVG that cannot take a CSS variable,
   so on a green panel it was green on green. On the plate it is simply correct.
   ⚠ The wordmark is INK here, not white: it sits on the plate, not on the panel. */
.vz-auth-plate--mark { gap: var(--vz-space-2); }
.vz-auth-plate--mark .vz-brand-word { color: var(--vz-ink); font-weight: 650; }

.vz-auth-aside-where {
  position: relative;
  z-index: 1;
  margin: var(--vz-space-2) 0 0;
  font-size: 13px;
  color: #cbe2b8;
}

.vz-auth-tagline {
  position: relative;
  z-index: 1;
  margin: var(--vz-space-2) 0 0;
  font-size: 14px;
  font-weight: 600;
  color: #f3d59a;
}

.vz-auth-aside-say { position: relative; z-index: 1; margin-top: var(--vz-space-6); }

.vz-auth-aside-title {
  margin: 0 0 var(--vz-space-3);
  max-width: 26ch;
  font-size: clamp(1.6rem, 1.1rem + 1.6vw, 2.55rem);
  line-height: 1.12;
  letter-spacing: -0.025em;
  font-weight: 680;
}

.vz-auth-aside-lede {
  margin: 0 0 var(--vz-space-5);
  max-width: 44ch;
  font-size: 17px;
  line-height: 1.5;
  color: #cbe2b8;
}


/* --- the form side ------------------------------------------------------- */

.vz-auth-pane {
  flex: 1 1 auto;
  /* E25 finding 10: a growable flex item that cannot shrink below its own content
     pushes the whole page sideways. StylesheetStaticTest caught this one. */
  min-width: 0;
  box-sizing: border-box;
  display: flex;
  flex-direction: column;
  padding: var(--vz-space-5) max(var(--vz-space-5), env(safe-area-inset-right))
           var(--vz-space-4) max(var(--vz-space-5), env(safe-area-inset-right));
}

/* ⚠ THE CARD KEEPS ITS OWN RULES AND GAINS A GROUND. A border drawn on white has nothing
   to separate; the wrap takes `--vz-bg` so the card is figure against ground, which is
   what makes the outline do any work at all. */
.vz-auth-wrap--split .vz-auth-card {
  margin: auto;
  max-width: 440px;
}

.vz-auth-wrap--split .vz-footer--auth { margin-top: var(--vz-space-4); }

/* The terms sentence, directly above the button it describes. */
.vz-auth-terms {
  margin: 0 0 var(--vz-space-3);
  text-align: center;
  font-size: 13px;
  line-height: 1.55;
  color: var(--vz-muted);
}


/* --- owner review, 2026-10-08 ------------------------------------------- */

/* 🔴 **FIFTY/FIFTY, BECAUSE "WHY ARE THE TWO SIDES DIFFERENT SIZES" HAD A REAL ANSWER.**
   The panel was `flex: 0 0 52%` with `max-width: 660px`, so past ~1270px the cap bit and
   the panel stopped growing while the form side kept going: at 1916px it was 660 against
   1256, which reads as a mistake because it is one. A split door is a split door. */
.vz-auth-wrap--split .vz-auth-aside {
  flex: 0 0 50%;
  max-width: none;
}

/* ⚠ **THE HEADING AND THE WINDOW ARE ONE BLOCK, ANCHORED LOW.**
   `space-between` was right while the panel held three things; once the help card
   moved beside the form it was spreading brand / heading / window across the full
   height and opening TWO 175px holes — measured on a 1440x900 door, not guessed.
   The mark stays at the top, and everything it introduces sits together at the
   bottom, which is the composition the panel reads as. */
.vz-auth-aside { justify-content: flex-start; }

/* The operator name when they have uploaded no logo — the common case, and the one that
   was showing somebody else's lockup. */
.vz-auth-aside-name {
  position: relative;
  z-index: 1;
  margin: 0;
  font-size: 21px;
  font-weight: 680;
  letter-spacing: -0.015em;
  color: #fff;
}


/* --- the field glyphs, which the mockup had and the first build did not --- */
/* ⚠ SCOPED TO `--iconed`, so the sixteen other call sites of `partials/password-field`
   render exactly the markup they rendered yesterday. */
.vz-control-group--iconed .vz-control { padding-left: 44px; }

.vz-control-lead {
  position: absolute;
  left: 14px;
  top: 50%;
  transform: translateY(-50%);
  width: 19px;
  height: 19px;
  color: var(--vz-muted);
  pointer-events: none;
}

/* --- the scope chip as a pill, on the split doors only -------------------- */
/* It stays plain uppercase text on every unsplit screen; inside the card it reads as a
   label for the card rather than a line floating above the heading. */
.vz-auth-wrap--split .vz-auth-scope {
  display: inline-block;
  margin-bottom: var(--vz-space-3);
  padding: 6px 12px;
  border-radius: 999px;
  background: var(--vz-primary-tint);
  color: var(--vz-primary-strong);
  text-align: left;
}

/* ⚠ The card's own heading block is left-aligned on a split door: a centred heading over
   left-aligned labels is the shape the finance card has because it has no labels above
   its fields. This one does. */
.vz-auth-wrap--split .vz-auth-title,
.vz-auth-wrap--split .vz-auth-sub { text-align: left; }


/* ===========================================================================
   The product, landing — Act 3 of the marketing hero (owner, 2026-10-08)
   ===========================================================================
   `vazhai-chit-website/src/components/HeroStory.astro` runs 26s in three acts: the
   paper mess 0–7.6s, the brand 7.3–11.5s, the calm app 11.2–24.6s. **A sign-in takes
   about five seconds**, so the whole story on a door would show a paying operator the
   pile of paper every morning and sign them in before the product appeared. This is
   the resolution only, in the same motion language, at ~2.5s.

   ⚠ NO JAVASCRIPT. The hero uses an IntersectionObserver and a play/pause button;
   `layouts/auth.php` treats `app.js` as optional, so a panel needing script to make
   sense would break that contract before anything else on the page did. */

.vz-auth-story {
  position: relative;
  z-index: 1;
  margin-top: var(--vz-space-5);
  max-width: 460px;
  background: var(--vz-surface);
  border-radius: 16px;
  box-shadow: 0 18px 40px rgba(0, 0, 0, .22);
  overflow: hidden;
  opacity: 0;
  animation: vz-auth-win .55s cubic-bezier(.2, .7, .3, 1) .1s forwards;
}

@keyframes vz-auth-win { from { opacity: 0; transform: translateY(14px); } to { opacity: 1; transform: none; } }

.vz-auth-story-bar {
  display: flex;
  align-items: center;
  gap: 8px;
  padding: 11px 15px;
  background: var(--vz-surface-2);
  border-bottom: 1px solid var(--vz-line, #E4E8E1);
}

.vz-auth-story-dot   { width: 9px; height: 9px; border-radius: 50%; background: #D9DCD6; }
.vz-auth-story-where { margin-left: 6px; font-size: 12.5px; font-weight: 600; color: var(--vz-muted); }
.vz-auth-story-live  { margin-left: auto; display: inline-flex; align-items: center; gap: 6px; font-size: 11.5px; font-weight: 650; color: var(--vz-primary-strong); }

/* ⚠ THE ONLY THING THAT KEEPS GOING. The hero loops because a visitor is browsing;
   here somebody is typing a password, and a panel that replays behind them is a
   distraction with no second thing to say. The pip says "live" without repeating. */
.vz-auth-story-pip { width: 7px; height: 7px; border-radius: 50%; background: var(--vz-primary); animation: vz-auth-pip 2.6s ease-in-out infinite; }
@keyframes vz-auth-pip { 0%, 100% { opacity: 1; } 50% { opacity: .35; } }

.vz-auth-story-rows { list-style: none; margin: 0; padding: 6px 0; }

.vz-auth-story-row {
  display: flex;
  align-items: center;
  gap: 12px;
  padding: 10px 15px;
  opacity: 0;
  animation: vz-auth-row .45s cubic-bezier(.2, .7, .3, 1) forwards;
}

/* ⚠ 650ms apart, not 400 (owner, 2026-10-08). At the tighter spacing the rows read
   as one block appearing rather than a month being worked through, which is the whole
   point of borrowing the hero. The last row still lands inside 3.5s. */
.vz-auth-story-row--1 { animation-delay: .55s; }
.vz-auth-story-row--2 { animation-delay: 1.20s; }
.vz-auth-story-row--3 { animation-delay: 1.85s; }
.vz-auth-story-row--4 { animation-delay: 2.50s; }
.vz-auth-story-row--5 { animation-delay: 3.15s; }

@keyframes vz-auth-row { from { opacity: 0; transform: translateY(8px); } to { opacity: 1; transform: none; } }

.vz-auth-story-icon {
  flex: 0 0 auto;
  width: 32px;
  height: 32px;
  border-radius: 9px;
  display: inline-flex;
  align-items: center;
  justify-content: center;
}

.vz-auth-story-icon svg { width: 16px; height: 16px; }

.vz-auth-story-icon--ok   { background: var(--vz-primary-tint); color: var(--vz-primary-strong); }
.vz-auth-story-icon--note { background: var(--vz-warning-tint); color: var(--vz-warning-text); }
.vz-auth-story-icon--flat { background: var(--vz-surface-2);    color: var(--vz-muted); }

.vz-auth-story-said        { flex: 1 1 auto; min-width: 0; }
.vz-auth-story-said b      { display: block; font-size: 13.5px; font-weight: 650; color: var(--vz-ink); }
.vz-auth-story-said small  { display: block; font-size: 12px; color: var(--vz-muted); }

.vz-auth-story-tag {
  flex: 0 0 auto;
  font-size: 11px;
  font-weight: 650;
  border-radius: 999px;
  padding: 4px 9px;
}

.vz-auth-story-tag--ok   { color: var(--vz-success-text); background: var(--vz-success-tint); }
.vz-auth-story-tag--note { color: var(--vz-warning-text); background: var(--vz-warning-tint); }
.vz-auth-story-tag--flat { color: #3F4742;                background: var(--vz-surface-2); }

/* ⛔ Below 900px the window goes with the points before it: the fold is the budget,
   and the submit button has to stay above it. */
@media (max-width: 56.1875rem) {
  .vz-auth-story { display: none; }
}

@media (prefers-reduced-motion: reduce) {
  .vz-auth-story,
  .vz-auth-story-row { animation: none; opacity: 1; transform: none; }
  .vz-auth-story-pip { animation: none; }
}

/* --- the ground, not more content (owner, 2026-10-08) -------------------- */
/* Three rounds tried to fill this panel by adding things to read. A field of flat
   colour looks empty; a field with shapes in it does not, and nothing here asks to be
   read. ⚠ It is `aria-hidden` and `pointer-events: none`: it says nothing and it must
   never intercept a click meant for the form behind it at a narrow width. */

.vz-auth-field {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  z-index: 0;
  pointer-events: none;
}

.vz-auth-field-ring { fill: none; stroke: #fff; stroke-opacity: .055; stroke-width: 1.5; }
.vz-auth-field-disc { fill: #fff; fill-opacity: .035; }
.vz-auth-field-pip  { fill: #fff; fill-opacity: .10; }

/* --- two-step sign-in: setup and recovery codes (owner, 2026-11-03) ----------------
   ⚠ THE QR BOX IS WHITE IN BOTH THEMES, ON PURPOSE. A scanner needs dark squares on a light
   ground, so the box does not take `--vz-surface`: in the dark theme that token is dark, and a
   black-on-dark code would not scan. The squares are black `fill` attributes from `MfaQrCode`.
   ⚠ The secret and the recovery codes are monospaced and selectable — they are typed or
   copied, and a proportional face makes 0/O and 1/l harder to tell apart. */
.vz-mfa-steps {
  margin: 0 0 var(--vz-space-4);
  padding-left: var(--vz-space-5);
  font-size: var(--vz-fs-sm);
  color: var(--vz-muted);
}

.vz-mfa-steps li + li { margin-top: var(--vz-space-1); }

.vz-mfa-qr {
  box-sizing: border-box;
  width: 220px;
  max-width: 100%;
  margin: 0 auto var(--vz-space-4);
  padding: var(--vz-space-2);
  background: #ffffff;
  border: 1px solid var(--vz-border);
  border-radius: var(--vz-radius-md);
}

.vz-mfa-qr-svg {
  display: block;
  width: 100%;
  height: auto;
}

.vz-mfa-secret-label {
  margin: 0;
  font-size: var(--vz-fs-sm);
  color: var(--vz-muted);
  text-align: center;
}

.vz-mfa-secret {
  margin: var(--vz-space-1) 0 var(--vz-space-5);
  text-align: center;
  overflow-wrap: anywhere;
}

.vz-mfa-secret code,
.vz-mfa-codes code {
  font-family: var(--vz-font-mono);
  font-size: var(--vz-fs-sm);
  letter-spacing: .03em;
  user-select: all;
}

.vz-mfa-codes {
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: var(--vz-space-2) var(--vz-space-4);
  margin: 0 0 var(--vz-space-4);
  padding: var(--vz-space-3) var(--vz-space-3) var(--vz-space-3) var(--vz-space-6);
  background: var(--vz-surface-2);
  border-radius: var(--vz-radius-md);
}

/* --- the six-digit code as six boxes (owner, 2026-11-04) ----------------------------
   ⚠ THE BOXES ARE DRAWN, THE FIELD IS REAL: `.is-boxes` stretches the one input over the cells and
   makes it invisible, so clicks, typing, paste and autofill all still land in that input. See
   `partials/code-field.php`. Everything is scoped under `.is-boxes`, which only `app.js` adds, so
   without the script this is an ordinary `.vz-control`. */
.vz-code-entry { position: relative; }
.vz-code-cells { display: none; }

.vz-code-entry.is-boxes .vz-code-cells {
  display: grid;
  grid-template-columns: repeat(6, minmax(0, 1fr));
  gap: var(--vz-space-2);
}

.vz-code-entry.is-boxes .vz-control {
  position: absolute;
  inset: 0;
  height: 100%;
  padding: 0;
  border: 0;
  background: transparent;
  box-shadow: none;
  color: transparent;
  -webkit-text-fill-color: transparent;
  caret-color: transparent;
}

.vz-code-entry.is-boxes .vz-control::selection { background: transparent; }

.vz-code-cell {
  display: flex;
  align-items: center;
  justify-content: center;
  min-height: 3rem;
  box-sizing: border-box;
  border: 1px solid var(--vz-border-strong);
  border-radius: var(--vz-radius-md);
  background: var(--vz-surface);
  color: var(--vz-ink);
  font-family: var(--vz-font-mono);
  font-size: var(--vz-fs-lg);
  font-variant-numeric: tabular-nums lining-nums;
  transition: border-color .15s ease, box-shadow .15s ease;
}

/* `.vz-control:focus`'s own ring, on the box the next digit goes in.
   ⚠ `:focus-within`, NOT A CLASS THE SCRIPT TOGGLES ON FOCUS: `autofocus` can land with no focus
   event (measured after a refused code), which left the field focused and no box marked. */
.vz-code-entry:focus-within .vz-code-cell.is-next {
  border-color: var(--vz-primary);
  box-shadow: 0 0 0 3px var(--vz-primary-tint);
}

/* A recovery code, set the way it is printed. The height is the boxes', so changing from one to
   the other does not move the rest of the card. */
.vz-code-entry.is-recovery .vz-control {
  min-height: 3rem;
  font-size: var(--vz-fs-lg);
  text-align: center;
  letter-spacing: .16em;
}

.vz-code-switch { margin-top: var(--vz-space-2); }
.vz-code-switch[hidden],
.vz-field-hint[hidden],
.vz-check[hidden] { display: none; }

/* --- a person's own sign-in security: the account page (owner, 2026-11-03) ----------
   Short sections, divided by a rule, each a heading, what is true today and one act. ONE
   COLUMN, passkeys first (owner, 2026-11-18: the two columns of 2026-11-04 were *"a bit
   clumsy"* — adding a passkey sat beside the recovery codes). The wide card is wider than the
   24rem sign-in card only so a passkey's name and dates fit on one line each. */
.vz-auth-card--wide { max-width: 36rem; }

.vz-mfa-section {
  margin-top: var(--vz-space-5);
  padding-top: var(--vz-space-4);
  border-top: 1px solid var(--vz-border);
}

/* The authenticator app's two folded acts, one under the other. */
.vz-mfa-acts { display: grid; gap: var(--vz-space-2); }
.vz-mfa-acts > .vz-mfa-note { margin: 0; }

.vz-mfa-fold > form { margin-top: var(--vz-space-3); }
.vz-mfa-fold > summary { justify-content: center; }

.vz-mfa-heading {
  margin: 0 0 var(--vz-space-2);
  font-size: var(--vz-fs-md);
  font-weight: var(--vz-fw-medium);
  color: var(--vz-ink);
}

.vz-mfa-note {
  display: block;
  margin: 0 0 var(--vz-space-3);
  font-size: var(--vz-fs-sm);
  color: var(--vz-muted);
}

/* ⚠ `display: block` above beats the browser's own `[hidden]` — found driving (2026-11-18): the
   passkey panel's "this browser cannot make a passkey" note showed beside the working button. */
.vz-mfa-note[hidden] { display: none; }

.vz-mfa-browsers {
  display: grid;
  gap: var(--vz-space-3);
  margin: 0 0 var(--vz-space-3);
  padding: 0;
  list-style: none;
}

.vz-mfa-browsers li {
  display: flex;
  align-items: center;
  gap: var(--vz-space-3);
  padding: var(--vz-space-3);
  border: 1px solid var(--vz-border);
  border-radius: var(--vz-radius-md);
}

.vz-mfa-browser-icon {
  flex: none;
  display: flex;
  align-items: center;
  justify-content: center;
  width: 2.25rem;
  height: 2.25rem;
  border-radius: var(--vz-radius-md);
  background: var(--vz-primary-tint);
  color: var(--vz-primary-strong);
}

/* On a phone the name already says what it is, and the width buys one line per date. */
@media (max-width: 29.99rem) {
  .vz-mfa-browser-icon { display: none; }
}

/* Its own edge, not `.vz-linkbtn`'s padding: it sits under the list and lines up with it. */
.vz-mfa-remove-all { padding-left: 0; padding-right: 0; }

.vz-mfa-browser-text { flex: 1 1 auto; min-width: 0; }
.vz-mfa-browser-text strong { display: block; color: var(--vz-ink); font-weight: var(--vz-fw-medium); }
.vz-mfa-browsers .vz-mfa-note { margin: 0; }

/* An icon, so it carries the 44px target itself. Muted until it is aimed at: on a list of five it
   should not outshout the names. */
.vz-mfa-remove {
  display: flex;
  align-items: center;
  justify-content: center;
  width: var(--vz-tap-min);
  height: var(--vz-tap-min);
  padding: 0;
  border: 0;
  border-radius: var(--vz-radius-md);
  background: none;
  color: var(--vz-muted);
  cursor: pointer;
}

.vz-mfa-remove:hover { color: var(--vz-danger); }
.vz-mfa-remove:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: 2px; }

/* Copy and download for the recovery codes (owner, 2026-11-03). Two equal buttons side by side
   and the result said beneath them; on a phone they wrap rather than squeeze. */
.vz-mfa-codes-actions {
  display: flex;
  flex-wrap: wrap;
  gap: var(--vz-space-2);
  margin: 0 0 var(--vz-space-4);
}

.vz-mfa-codes-actions .vz-action { flex: 1 1 10rem; min-width: 0; }

.vz-mfa-codes-feedback {
  flex-basis: 100%;
  margin: 0;
  min-height: 1.25em;
  font-size: var(--vz-fs-sm);
  color: var(--vz-muted);
  text-align: center;
}

/* The Install card under a door's sign-in box (owner, 2026-11-04): its own card, so the form
   above it stays what the page is for. `partials/install-card` starts `hidden`, and `display`
   on a class beats the attribute, so each element that sets one says so. */
.vz-install {
  width: 100%;
  max-width: 24rem;
  margin-top: var(--vz-space-3);
  box-sizing: border-box;
  background: var(--vz-surface);
  border: 1px solid var(--vz-border);
  border-radius: var(--vz-radius-lg);
  box-shadow: var(--vz-shadow-md);
}

.vz-auth-wrap--split .vz-install {
  margin: var(--vz-space-3) auto auto;
  max-width: 440px;
}

/* The sign-in box centres itself with `margin: auto`, which would leave the spare height between
   it and this card on a computer. Only while the card shows, so a hidden one moves nothing. */
.vz-auth-wrap--split .vz-auth-card:has(+ .vz-install:not([hidden])) { margin-bottom: 0; }

.vz-install[hidden],
.vz-install-steps[hidden] { display: none; }

.vz-install-open {
  display: flex;
  align-items: center;
  gap: var(--vz-space-3);
  width: 100%;
  min-height: var(--vz-tap-min);
  padding: var(--vz-space-3);
  box-sizing: border-box;
  border: 0;
  border-radius: var(--vz-radius-lg);
  background: none;
  color: var(--vz-ink);
  font: inherit;
  text-align: left;
  cursor: pointer;
}

.vz-install-open:focus-visible { outline: 2px solid var(--vz-primary); outline-offset: 2px; }

.vz-install-icon { flex: none; border-radius: var(--vz-radius-md); }

.vz-install-text { flex: 1 1 auto; min-width: 0; }

.vz-install-title {
  display: block;
  font-size: var(--vz-fs-base);
  font-weight: var(--vz-fw-bold);
  overflow-wrap: anywhere;
}

.vz-install-sub {
  display: block;
  font-size: var(--vz-fs-sm);
  color: var(--vz-muted);
}

.vz-install-go {
  flex: none;
  display: flex;
  align-items: center;
  justify-content: center;
  width: 2.625rem;
  height: 2.625rem;
  border-radius: 50%;
  background: var(--vz-primary-button);
  color: var(--vz-primary-contrast);
}

.vz-install-open:hover .vz-install-go { background: var(--vz-primary-hover); }

.vz-install-steps {
  margin: 0;
  padding: var(--vz-space-3) var(--vz-space-4) var(--vz-space-3) var(--vz-space-6);
  border-top: 1px solid var(--vz-border);
  font-size: var(--vz-fs-sm);
  color: var(--vz-ink);
}
