/* OV home page stylesheet.
   Derived from the approved reference orders/WEB-1/ov.css (WEBSITE Director,
   2026-10-29). Visual values - colour, type, spacing, breakpoints - are carried
   over unchanged. Two kinds of change were made, both deliberate:

   1. Image rules became *slot boxes*. The reference sized several images by their
      intrinsic dimensions (width:240px;height:auto). OV has no image files yet, so
      an intrinsic height would be zero and the layout would shift the day the
      Architect supplies a file. Every image site therefore declares its own box
      here, and the image or the placeholder fills it. See ov/slots.py.
   2. The reference's inline style attributes became classes (.section-paper,
      .lead-dim, .h-edit, .dl-meta, .ftr-blurb, .section-flush-top). Same computed
      values.
*/
/* WEB-38 §3b, WEB-47 §1. THE FROZEN STACK, in one number.

       --ov-stack-h = --ov-bar-h + --ov-header-h

   --ov-header-h is the red header. --ov-bar-h is whatever sits above it,
   and on the public site nothing does -- so it is 0 here, the stack is the
   header alone, and not one rule below has to know about it.

   Preview, a separate application the public never passes through, sets
   --ov-bar-h to its own bar's height from outside and pads the page by it.
   Everything frozen then clears the bar as well as the header with nothing
   here changed. That one custom property is the whole of the seam between
   the website and Preview.

   Everything that must clear the stack reads --ov-stack-h and nothing
   else: the mobile panel's top and max-height, a heading's
   scroll-margin-top, the hero's offset. A number repeated in nine places
   is nine places to get wrong the next time the header changes height. */
:root{
  --ov-header-h:56px;
  --ov-bar-h:0px;
  --ov-stack-h:calc(var(--ov-bar-h) + var(--ov-header-h));
  --ink:#0A0A0B; --ink-2:#131315; --ink-3:#1C1C1F;
  --line-d:rgba(255,255,255,.12); --line-l:#E3E2DF;
  --paper:#F5F4F1; --white:#FFFFFF;
  --text-d:#F2F2F2; --mute-d:#A9A9AE; --text-l:#111113; --mute-l:#55555C;
  --red:#FF0000; --red-ui:#FF0000; --red-text:#FF0000;
  /* WEB-11 B1. The red stays #FF0000 (Architect, 22:56). White lettering ON
     red gets a dark halo instead: a thin, even outline, not a drop shadow.
     #5A0000 behind white measures 14.64:1. Automated checkers ignore
     text-shadow and will go on reporting these pairs as 4.0:1 -- both numbers
     are in the report, because quoting only the flattering one would be
     choosing the measurement that suits the answer. */
  /* WEB-11 C2: the blurred form was measured, not assumed. At 13 px a
     0 0 1px / 0 0 2px blur spreads so thin that the halo it PAINTS has a
     median colour of rgb(195,37,37) -- white against it is 5.81:1, not the
     14.64:1 the token's nominal #5A0000 would give. The Architect's named
     fallback paints at full strength because it has no blur to dilute:
     measured 10.69:1 at the median ring pixel, 14.74:1 at the darkest.
     verify/web11_halo_pixels.py, screenshots/WEB-11/ab-*.png. */
  --halo-on-red: 1px 0 #5A0000, -1px 0 #5A0000, 0 1px #5A0000, 0 -1px #5A0000;
  --f-display:"Archivo",system-ui,sans-serif;
  --f-body:"IBM Plex Sans",system-ui,sans-serif;
  --f-mono:"IBM Plex Mono",ui-monospace,monospace;
  --wrap:1280px; --gut:40px;
}
body{margin:0}
*{box-sizing:border-box}
/* overflow-x: CLIP, not hidden. `hidden` makes this element a scroll
   container, which silently disables `position: sticky` on everything inside
   it -- including .pf, which had been declared sticky since WEB-8 and had never
   once stuck. `clip` stops the same horizontal scrolling without creating a
   scroll container. Measured: with `hidden` a stuck header reads top:-1500 at
   scrollY 1500; with `clip` it reads top:0. */
.ov{font-family:var(--f-body);color:var(--text-l);background:var(--white);font-size:16px;line-height:1.55;-webkit-font-smoothing:antialiased;overflow-x:clip}
.ov img{display:block;max-width:100%}
.ov a{color:inherit;text-decoration:none}
.wrap{max-width:var(--wrap);margin:0 auto;padding:0 var(--gut)}
.mono{font-family:var(--f-mono);font-size:12px;letter-spacing:.12em;text-transform:uppercase}
.eyebrow{font-family:var(--f-mono);font-size:12px;letter-spacing:.14em;text-transform:uppercase;color:var(--red-text);display:flex;align-items:center;gap:10px;margin:0 0 16px}
.eyebrow::before{content:"";width:8px;height:8px;background:var(--red);display:inline-block}
.dark .eyebrow{color:var(--red)}
.h-display{font-family:var(--f-display);font-stretch:118%;font-weight:800;letter-spacing:-.01em;line-height:1.02;margin:0;text-transform:uppercase}
.h2{font-size:48px}
.h-edit{font-size:40px}
.lead{font-size:19px;line-height:1.6;color:var(--mute-l);max-width:720px;margin:20px 0 0}
.lead-dim{color:#D4D4D8}
.dark{background:var(--ink);color:var(--text-d)}
.dark .lead{color:var(--mute-d)}
.section{padding:112px 0;position:relative;z-index:1;background:var(--white)}
.section.dark{background:var(--ink)}
.section.section-paper{background:#F5F4F1}
/* Everything after the hero must be opaque and sit above the fixed hero media,
   or the video shows through it. .proof and .ftr are not .section elements, so
   they need saying separately. */
.proof,.ftr{position:relative;z-index:1;background:var(--ink-2)}
.ftr{background:#000}
.section-flush-top{padding-top:0}
.sec-head{display:flex;justify-content:space-between;align-items:flex-end;gap:32px;flex-wrap:wrap;margin-bottom:48px}
.dots{position:absolute;inset:0;pointer-events:none;background-image:radial-gradient(rgba(255,255,255,.16) 1px,transparent 1.4px);background-size:6px 6px;mix-blend-mode:overlay}

/* ---------- image slots ----------
   The box is sized here; the content fills it. An <img> and a placeholder occupy
   exactly the same box, so a missing file cannot move anything on the page. */
.sl{position:relative;display:block;overflow:hidden}
.sl>img{display:block;width:100%;height:100%}
.sl--cover>img{object-fit:cover}
.sl--contain>img{object-fit:contain}
/* WEB-39 §6d: Houdini's ring is 722 x 448 and that is all there is of it, so
   it is never drawn wider than 722 CSS px. `contain` would scale it UP to
   fill a wider frame; `scale-down` is `contain` that never enlarges, so the
   picture "sits at its own size in the frame rather than stretching" --
   §6d's words. One slot, by the name the slot system already writes into
   the markup, so no other image is touched. */
[data-slot="houdini-ring.png"]>img{object-fit:scale-down}
.sl-ph{position:absolute;inset:0;display:flex;align-items:center;justify-content:center;padding:4px;background:repeating-linear-gradient(45deg,#ECEBE8 0 10px,#F4F3F0 10px 20px);border:1px dashed #BDBCB8}
.sl-ph--dark{background:repeating-linear-gradient(45deg,#1C1C1F 0 10px,#232327 10px 20px);border-color:rgba(255,255,255,.26)}
.sl-ph-l{font-family:var(--f-mono);font-size:9.5px;line-height:1.3;letter-spacing:.03em;text-align:center;color:var(--mute-l);word-break:break-word;overflow:hidden;max-height:100%}
.sl-ph--dark .sl-ph-l{color:var(--mute-d)}

/* buttons */
.btn{display:inline-flex;align-items:center;gap:10px;min-height:48px;padding:0 22px;font-family:var(--f-display);font-stretch:110%;font-weight:700;font-size:14px;letter-spacing:.06em;text-transform:uppercase;border:1px solid transparent;cursor:pointer}
/* `.ov a{color:inherit}` (0,1,1) outranks `.btn-red` (0,1,0), so every anchor
   styled as a red button inherited its surroundings' colour instead of white.
   Invisible on the home page, where all of them sit inside .dark and inherit
   #F2F2F2; visible on a light section, where the text came out dark on red.
   Measured before fixing: every <a class=btn-red> computed rgb(242,242,242). */
.btn-red,.ov .btn-red{background:var(--red-ui);color:#fff}
.btn-red:hover{background:#000;color:#fff}
.btn-ghost{border-color:rgba(255,255,255,.4);color:#fff;background:transparent}
.btn-ghost:hover{border-color:#fff}
.btn-line{border-color:var(--text-l);color:var(--text-l);background:transparent}
.link-arrow{font-family:var(--f-display);font-stretch:110%;font-weight:700;font-size:13px;letter-spacing:.08em;text-transform:uppercase;color:var(--red-text);display:inline-flex;align-items:center;gap:8px;min-height:24px}
.dark .link-arrow{color:var(--red)}

/* header */
.hdr{background:#FF0000;position:sticky;top:0;z-index:5}
/* WEB-20 §4b: the links from "Why Vanguard" to "Contact Us" are CENTERED
   horizontally, sitewide. The logo stays left and search stays right.

   A three-column grid, 1fr auto 1fr, so the middle column is the nav and it
   is centred in the bar whatever the logo's width. `--hdr-pad` is the bar's
   own side padding as a token, because the search button is pinned to it and
   the padding changes twice on the way down to a phone; before it was a
   token the button and the padding could disagree.

   The burger is pinned to column 3 explicitly. Below the menu breakpoint the
   nav is display:none and leaves the grid, and auto-placement would otherwise
   put the burger in the MIDDLE of the bar. */
.hdr-in{--hdr-pad:65px;display:grid;grid-template-columns:1fr auto 1fr;
  align-items:center;height:56px;padding:0 var(--hdr-pad);
  position:relative}
.hdr-in > .hdr-logo{grid-column:1;justify-self:start}
.hdr-in > .nav{grid-column:2;justify-self:center}
.hdr-in > .mob{grid-column:3;justify-self:end}
/* WEB-25a §11: the magnifier is now a form's submit button, so the FORM
   takes the place the button used to hold -- pinned to the right of the bar,
   out of the grid, so it cannot push the centred nav off centre.

   The field is closed until it is wanted. Closed, the control is exactly the
   44px magnifier it has always been, and clicking it opens /search/, which
   has a full-width field of its own -- so the control is never a dead end
   for a mouse. Hovering or tabbing into it opens the field in place. All of
   that is :focus-within and :hover; there is no script anywhere near it. */
.nav .hdr-search{position:absolute;right:var(--hdr-pad);top:50%;
  transform:translateY(-50%);margin:0;display:flex;align-items:center;
  gap:0}
.nav .hdr-search input{width:0;min-width:0;padding:0;border:0;outline:0;
  background:rgba(0,0,0,.28);color:#fff;font:inherit;font-size:13px;
  height:30px;border-radius:999px;
  transition:width .18s ease,padding .18s ease}
.nav .hdr-search input::placeholder{color:rgba(255,255,255,.65)}
.nav .hdr-search:hover input,
.nav .hdr-search:focus-within input{width:168px;padding:0 14px}
.nav .hdr-search input:focus{box-shadow:0 0 0 2px #fff inset}
.nav .search-btn{margin:0}
.logo{width:240px}
/* WEB-17 B3: --nav-lbl-pad is the label's own side padding, and the
   dropdown panel's left offset is the SAME token, so the panel can never
   drift away from the text it belongs to. The gap between items is wider
   than the gap from a label to its chevron -- at 2 px each the chevron sat
   as close to the next item's text as to its own. */
.nav{display:flex;gap:12px;align-items:center;
  --nav-lbl-pad:8px;font-family:"Poppins",var(--f-body)}
.nav a{color:#fff;font-size:13px;font-weight:400;
  padding:0 var(--nav-lbl-pad);height:40px;display:inline-flex;
  align-items:center;gap:6px}
.nav a:hover{text-decoration:underline;text-underline-offset:4px}
.nav .nav-pill{background:#000;border-radius:999px;padding:0 14px;margin-left:4px}
.nav .nav-pill:hover{text-decoration:none;background:#1C1C1F}
.search-btn{width:44px;height:44px;margin-left:16px;display:inline-flex;align-items:center;justify-content:center;background:transparent;border:0;color:#fff;cursor:pointer}
/* ---------- WEB-16 B1: the header at every width ----------------------------

   The breakpoint is measured, not chosen. A1 laid the bar out unconstrained and
   added up the parts: logo 240 + nav + two 24 px gaps + 130 px of padding. The
   figure below is that measurement plus 16 px, and it is re-measured by
   verify/web16_header.py whenever the bar's contents change -- which they did
   in this very order, when Products gained a separate chevron.

   Below it the three-line button shows and the full menu does not. There is no
   width where both show, and none where neither does. */
/* 974 px is what the bar measures with everything on one line -- logo 240,
   nav 580, two 24 px gaps, 130 px of padding -- so the menu gives way at 990.
   Re-measure with verify/web16_header.py whenever the bar's contents change;
   this number went from 966 to 974 inside this order, when Products gained its
   chevron. No type was shrunk and no padding tightened: 990 is already well
   under the 1024 the Director capped it at. */
.mob{display:none;position:relative}
@media (max-width:990px){
  .nav{display:none}
  .mob{display:block}
}

/* the label-plus-chevron pair that replaced a single <summary> */
.nav-dd-wrap{position:relative;display:flex;align-items:center;gap:4px}
/* The label's own padding, keyed on .nav-lbl and NOT on the element type.
   `.nav a{padding:0 var(--nav-lbl-pad)}` reaches two of the three labels:
   Military/TAA is a <span>, because it has no hub page to link to, so it had
   no left padding, its text started at its box edge, and its panel -- offset by
   the same token -- landed 8 px to the right of it while the other two were
   exact. The same shape as F12 and F43: a rule that names a tag rather than
   the thing.
   Right padding goes, so the 4 px gap to the chevron is 4 px of air rather
   than 4 px plus 8 px of padding. */
.nav > .nav-dd-wrap > .nav-lbl{padding-left:var(--nav-lbl-pad);padding-right:0}
.nav-lbl{color:#fff;font-size:13px;white-space:nowrap;display:flex;
  align-items:center;min-height:24px}
.nav-dd>summary{list-style:none;cursor:pointer;display:flex;align-items:center;
  color:#fff;min-height:24px;padding:0 2px}
.nav-dd>summary::-webkit-details-marker{display:none}
.nav-dd>summary:focus-visible{outline:2px solid #fff;outline-offset:3px}
.nav-dd[open]>summary svg{transform:rotate(180deg)}

/* a category row inside the Products menu, with its fly-out */
.nav-fly-row{display:flex;align-items:center;justify-content:space-between;
  gap:8px;padding:0 18px}
.nav-fly-row>a{flex:1;padding:4px 0;min-height:32px;display:flex;
  align-items:center;color:#fff;font-size:13px;white-space:nowrap}
.nav-has-fly{position:relative}
/* rotate(90deg), not -90: the down-chevron turns to point LEFT, which is the
   way the fly-out now opens. The direction is owned here, on the summary, so
   a second rule on the inner svg would only fight this one. */
.nav-fly>summary{list-style:none;cursor:pointer;display:flex;align-items:center;
  justify-content:center;width:28px;min-height:28px;color:#fff;
  transform:rotate(90deg)}
.nav-fly>summary::-webkit-details-marker{display:none}
.nav-fly>summary:focus-visible{outline:2px solid #fff;outline-offset:2px}
/* The fly-out opens to the LEFT, over its own dropdown, not outward to the
   right. At left:100% it started at the dropdown's right edge and ran 83 px
   past the right edge of the window at EVERY width the full menu shows -- 1313
   to 1523 in a 1440 px viewport -- and because .ov is overflow-x: clip that
   produced no scrollbar and no warning: the right-hand end of every series
   name was simply cut off. The nav sits at the right of the header, so there
   is always room on the left. */
.nav-fly-menu{position:absolute;right:100%;top:-9px;z-index:70;margin:0;
  padding:8px 0;list-style:none;background:#17171A;border:1px solid #2A2A2F;
  min-width:210px;box-shadow:0 12px 32px rgba(0,0,0,.4)}
.nav-fly-menu a,.nav-fly-menu .nav-soon{display:flex;align-items:center;
  min-height:32px;padding:4px 18px;color:#fff;font-size:13px;white-space:nowrap}
.nav-fly-menu a:hover,.nav-fly-menu a:focus-visible{background:#FF0000;
  text-shadow:var(--halo-on-red)}
.nav-soon{color:var(--mute-d);gap:8px}
.nav-soon em{font-family:var(--f-mono);font-style:normal;font-size:10px;
  letter-spacing:.08em;text-transform:uppercase;color:#fff;background:#111113;
  padding:2px 6px}

/* ---------- the menu button's panel ---------- */
/* WEB-21 §3g: a text button, not a glyph. White text in a white outline on
   the red header. The touch target is at least 44 px in both directions --
   44 high, and min-width 44 so the box can never be smaller than that even
   though the words make it wider. */
.mob>summary{list-style:none;cursor:pointer;min-width:44px;height:44px;
  display:flex;align-items:center;justify-content:center;color:#fff;
  padding:0 14px;border:2px solid #fff;
  font-family:var(--f-mono);font-size:13px;font-weight:500;
  letter-spacing:.12em;text-transform:uppercase}
.mob>summary:hover{background:rgba(255,255,255,.14)}
.mob>summary::-webkit-details-marker{display:none}
.mob>summary:focus-visible{outline:2px solid #fff;outline-offset:2px}
.burger-close{display:none}
.mob[open]>summary .burger-open{display:none}
.mob[open]>summary .burger-close{display:flex}
.mob-panel{position:fixed;left:0;right:0;
  top:var(--ov-stack-h);
  max-height:calc(100vh - var(--ov-stack-h));
  overflow-y:auto;overscroll-behavior:contain;
  background:#111113;border-top:1px solid #2A2A2F;z-index:65;padding:8px 0 24px}
.mob-list,.mob-sub{list-style:none;margin:0;padding:0}
.mob-row{display:flex;align-items:center;justify-content:space-between;gap:8px}
.mob-lbl,.mob-row>a{flex:1;display:flex;align-items:center;min-height:48px;
  padding:0 20px;color:#fff;font-size:15px}
/* The same trap as .btn-red above, in the narrow menu. `.ov a{color:inherit}`
   is (0,1,1) and `.mob-lbl` is (0,1,0), so every plain link in the panel --
   FAQ, Blogs, Contact Us, All products, each series name, Special
   configurations, Downloads -- inherited the body colour and computed
   rgb(17,17,19) on the panel's #111113 ground: black on black. The rows that
   looked right were the ones that also matched `.mob-row>a`, which is (0,2,1)
   and does outrank it. Measured before fixing. One rule for the whole panel,
   so a link that gains or loses a .mob-row cannot go dark again. */
.ov .mob-panel a,.ov .mob-panel .mob-lbl{color:#fff}
.mob-dd>summary{list-style:none;cursor:pointer;width:48px;min-height:48px;
  display:flex;align-items:center;justify-content:center;color:#fff}
.mob-dd>summary::-webkit-details-marker{display:none}
.mob-dd>summary:focus-visible{outline:2px solid #fff;outline-offset:-2px}
.mob-dd[open]>summary svg{transform:rotate(180deg)}
.mob-sub{display:none;background:#17171A}
/* The sub-list is a sibling of its row, so its open state comes from that
   row's <details> rather than from sitting inside it. */
li:has(> .mob-row > .mob-dd[open]) > .mob-sub{display:block}
.mob-sub .mob-row>a,.mob-sub>li>a{padding-left:36px;font-size:14px;min-height:44px}
.mob-sub .mob-sub .mob-row>a,.mob-sub .mob-sub>li>a{padding-left:52px}
.mob-sub .nav-soon{padding:8px 20px 8px 52px;min-height:44px}
/* WEB-21 §3g (22:35): Contact Us in the open menu was #000 on the panel's
   own #111113 -- black on near-black, the one item meant to stand out and the
   one you could not see. Red, with white text. */
.mob-pill{background:#FF0000;color:#fff;margin:8px 20px 0;min-height:48px;
  justify-content:center;border-radius:999px;flex:none}
.mob-pill:hover{background:#D60000;color:#fff}
/* WEB-25a §11: in the menu panel there is room, so the field is simply
   there -- full width, above the fold of the panel, 48px tall for a thumb. */
.mob-searchli{padding:8px 20px 0}
.mob-search{display:flex;align-items:stretch;gap:8px;width:100%}
.mob-search input{flex:1 1 auto;min-width:0;min-height:48px;padding:0 14px;
  border:1px solid rgba(255,255,255,.45);border-radius:6px;
  background:rgba(0,0,0,.25);color:#fff;font:inherit;font-size:15px}
.mob-search input::placeholder{color:rgba(255,255,255,.6)}
.mob-search button{display:inline-flex;align-items:center;gap:8px;
  min-height:48px;padding:0 14px;background:#FF0000;border:0;border-radius:6px;
  color:#fff;font:inherit;font-size:15px;cursor:pointer;flex:none}
.mob-search button:hover{background:#D60000}


/* hero */
/* The hero is as tall as the viewport below the 56px header, not a fixed 844px.
   At 1440x900 that is exactly 844px, so the approved look is unchanged; on a
   short viewport it shrinks with the screen instead of pushing the buttons below
   the fold (WEB-4 ruling). min-height, not height, so content can never be clipped. */
.hero{position:relative;min-height:844px;min-height:calc(100svh - 56px);display:flex;align-items:center;justify-content:center;text-align:center;z-index:0}
/* WEB-26 §6: the hero's media is position:fixed, so it paints the
   VIEWPORT and stops there. Any part of the hero below the fold had no
   background at all and showed the page's white: 46px of it at 1440,
   which has been there since the hero was built, and 15px at 375 once
   §6.2's tagline made the hero content-height. The hero now paints its
   own ink behind the media, which covers it everywhere the media
   reaches, so nothing above the fold changes by a pixel. */
.hero.dark{background:var(--ink,#0A0A0B)}
/* Fixed to the viewport: holds still while the page scrolls over it. Everything
   after the hero is opaque and sits at z-index 1, so the media is only ever seen
   through the hero. */
.hero-media{position:fixed;inset:0;z-index:0;overflow:hidden;background:var(--ink);pointer-events:none}
.hero-poster{position:absolute;inset:0;width:100%;height:100%}
.hero-poster>img{filter:saturate(.85)}
.hero-video{position:absolute;inset:0;width:100%;height:100%;object-fit:cover;filter:saturate(.85)}
/* Reduced motion: the poster underneath is all that shows. No script involved. */
@media (prefers-reduced-motion: reduce){.hero-video{display:none}}
/* Phones get the poster only, not a 7.3 MB download on a metered connection. The
   <source media> attribute is what stops the request; this rule is the fallback. */
@media (max-width:720px){.hero-video{display:none}}
.hero-shade{position:absolute;inset:0;background:radial-gradient(ellipse at 50% 45%,rgba(10,10,11,.72) 0%,rgba(10,10,11,.88) 70%),linear-gradient(0deg,rgba(10,10,11,.95) 0%,rgba(10,10,11,0) 40%)}
.hero-in{position:relative;z-index:1;max-width:1180px;padding:24px 40px;display:flex;flex-direction:column;align-items:center}
/* WEB-27 §3b: the live site's sizes. Its logo is a ::before on the
   centred block, width 1000px with margin:0 auto, and the block itself is
   position:absolute with top:calc(50% - 70px) AND transform:translateY(-50%)
   -- so what sits 70px above the middle is the block's CENTRE, which is
   what §3b says. OV's hero flex-centres the block already, so the same
   place is reached by shifting it 70px up; `top` on a relatively
   positioned child moves it without disturbing anything else's layout. */
/* WEB-28 §3 (the Architect, 17:45): mimic what the live site RENDERS.
   Its override declares width:1000px !important and never cancels the
   base rule's max-width:80%, so the logo is always 80% of its column --
   and its column is a fixed-step container, not a percentage of the
   window. Measured on the live site at five widths:

       1024, 1100, 1152  ->  column 930,  logo 744  (0.80 x 930)
       1200, 1280, 1440,
       1920              ->  column 1110, logo 888  (0.80 x 1110)

   OV's own hero column is 1000px, so copying the 80% literally would
   give 800 at every desktop width and match nothing. The two rendered
   figures are written here instead, with the step where the live site
   puts it. max-width keeps the logo inside OV's column if it is ever
   narrower than the figure. */
/* WEB-29 §5a: the logo is wrapped in an h1 so the home page has a
   heading again, and the wrap must change NOTHING a person can see.
   Three things had to be undone for that:
     - an h1 brings a browser's own 21.44px margins and a line box,
       which pushed the logo 43px down the hero;
     - as a shrink-to-fit flex item it became the logo's containing
       block, so the logo's max-width:85% started resolving against the
       h1 instead of .hero-in and the logo lost 45px at 390;
     - full width, it would left-align the logo, so it centres it.
   Proved identical to WEB 28's hero at 1440 and 390. */
.hero-h1{margin:0;line-height:0;font-size:inherit;font-weight:inherit;
  width:100%;display:flex;justify-content:center}
.hero-logo{width:744px;max-width:100%}
@media (min-width:1200px){
  .hero-logo{width:888px}
}
@media (min-width:1024px){
  .hero-in{position:relative;top:-70px}
}
/* WEB-27 §3a: .hero h1, .hero h1 em, .hero-sub and .hero-ctas are gone
   with the elements they styled -- the headline, its red words, the line
   under it and the two buttons. The hero is the logo and the tagline now.
   The rules are removed rather than left dead, so the next person reading
   this file is not told the hero has a headline. */
.hero-awards{position:absolute;left:20px;top:50%;transform:translateY(-50%);width:56px;z-index:1}
.hero-taa{position:absolute;right:28px;top:28px;width:84px;z-index:1}

/* proof */
.proof{background:var(--ink-2);color:var(--text-d);border-top:1px solid var(--line-d)}
.proof-grid{display:grid;grid-template-columns:repeat(4,minmax(0,1fr))}
.proof-item{padding:40px 32px;border-right:1px solid var(--line-d);display:flex;flex-direction:column;gap:18px}
.proof-item:first-child{padding-left:0}
.proof-item:last-child{border-right:0}
.proof-item .proof-t{font-family:var(--f-display);font-stretch:112%;font-weight:700;font-size:17px;letter-spacing:.03em;text-transform:uppercase;line-height:1.3;margin:0}
.proof-ico{width:40px;height:40px;color:var(--red)}
.counts{display:grid;grid-template-columns:repeat(var(--n,4),minmax(0,1fr));border-top:1px solid var(--line-d)}
/* WEB-34 §3a (the Architect, 10:01): the number and its label are centred in
   their column. The first column's padding-left:0 came from the proof row
   above, where the items are left-aligned; with centred text it pulled the
   first counter off the middle of its own column, so the padding is even. */
.count{padding:36px 32px 44px;border-right:1px solid var(--line-d);text-align:center}
.count:last-child{border-right:0}
.count b{display:block;font-family:var(--f-display);font-stretch:125%;font-weight:800;font-size:56px;line-height:1;color:#fff}
.count span{display:block;margin-top:10px;color:var(--mute-d)}

/* TAA */
.taa.section{background:var(--ink)}
.taa{position:relative;color:#fff;overflow:hidden;border-top:6px solid #FF0000}
.taa::after{content:"";position:absolute;inset:0;background:radial-gradient(ellipse at 85% 50%,rgba(255,0,0,.22),transparent 60%);pointer-events:none}
.taa .wrap{position:relative;z-index:1}
.taa-grid{display:grid;grid-template-columns:minmax(0,1.1fr) minmax(0,1fr);gap:72px;align-items:center}
.taa h2{font-size:64px}
.taa-links{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:1px;background:rgba(255,255,255,.14);margin-top:40px;border:1px solid rgba(255,255,255,.14)}
.taa-links a{background:var(--ink-2);padding:22px 24px;display:flex;justify-content:space-between;align-items:center;font-family:var(--f-display);font-stretch:110%;font-weight:700;font-size:15px;letter-spacing:.04em;text-transform:uppercase;min-height:64px}
.taa-links a:hover{background:#FF0000}
.taa-media{position:relative}
.taa-ph{width:100%;aspect-ratio:1/1}
.taa-cat{position:absolute;left:-40px;bottom:-40px;background:#fff;color:var(--text-l);padding:20px;display:flex;gap:18px;align-items:center;width:340px;box-shadow:0 24px 48px rgba(0,0,0,.45)}
.taa-cat-img{width:84px;flex:0 0 auto}
.taa-cat strong{display:block;font-family:var(--f-display);font-stretch:110%;font-size:16px;text-transform:uppercase;margin-bottom:8px}

/* spotlight */
.spot-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:24px}
.spot{background:var(--ink-2);border:1px solid var(--line-d);display:grid;grid-template-rows:280px auto;overflow:hidden}
.spot-img{width:100%;height:280px;background:#000}
.spot-body{padding:36px}
.spot h3{font-family:var(--f-display);font-stretch:112%;font-weight:800;font-size:30px;line-height:1.1;margin:0 0 24px;text-transform:uppercase}
.feat{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:22px 28px;margin:0 0 28px;padding:0;list-style:none}
.feat li{border-top:1px solid var(--line-d);padding-top:14px}
.feat b{display:block;font-family:var(--f-display);font-stretch:108%;font-size:15px;text-transform:uppercase;letter-spacing:.03em;color:#fff;margin-bottom:6px}
.feat span{color:var(--mute-d);font-size:14.5px;line-height:1.5}

/* products */
.fams{display:grid;grid-template-columns:repeat(7,minmax(0,1fr));border-top:2px solid var(--text-l);margin-bottom:56px}
.fam{padding:18px 16px 18px 0;border-right:1px solid var(--line-l);margin-right:16px;display:flex;flex-direction:column;gap:8px}
.fam:last-child{border-right:0;margin-right:0}
.fam b{font-family:var(--f-display);font-stretch:112%;font-size:15px;text-transform:uppercase;letter-spacing:.02em}
.fam span{font-size:13px;line-height:1.45;color:var(--mute-l)}
.prod-grid{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:24px}
.prod{background:var(--white);border:1px solid var(--line-l);display:flex;flex-direction:column}
.prod:hover{border-color:var(--text-l)}
.prod-media{background:#FFFFFF;height:260px;display:flex;align-items:center;justify-content:center;padding:44px 24px 20px;border-bottom:1px solid var(--line-l);position:relative}
.prod-img{width:100%;height:100%}
.prod-tag{position:absolute;left:16px;top:16px;color:var(--mute-l);z-index:1}
.prod-body{padding:24px;display:flex;flex-direction:column;gap:10px;flex:1}
.prod h3{font-family:var(--f-display);font-stretch:118%;font-weight:800;font-size:26px;text-transform:uppercase;margin:0;line-height:1.05}
.prod p{margin:0;color:var(--mute-l);flex:1}

/* configs */
.cfg-grid{display:grid;grid-template-columns:repeat(5,minmax(0,1fr));gap:1px;background:var(--line-d);border:1px solid var(--line-d)}
.cfg{background:var(--ink);padding:32px 26px 36px;display:flex;flex-direction:column;gap:14px;min-height:280px}
.cfg:hover{background:var(--ink-3)}
.cfg .num{color:var(--mute-d)}
.cfg h3{font-family:var(--f-display);font-stretch:118%;font-weight:800;font-size:24px;text-transform:uppercase;margin:28px 0 0;line-height:1.05}
.cfg p{margin:0;color:var(--mute-d);font-size:15px}
.cfg-bar{height:4px;width:36px;background:var(--red)}

/* markets */
.mkt-grid{display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:16px}
.mkt{position:relative;aspect-ratio:4/3;overflow:hidden;background:#000;display:block}
.mkt-img{position:absolute;inset:0;width:100%;height:100%;opacity:.78;transition:transform .4s ease,opacity .3s}
.mkt:hover .mkt-img{transform:scale(1.04);opacity:.9}
.mkt::after{content:"";position:absolute;inset:0;background:linear-gradient(0deg,rgba(0,0,0,.85),rgba(0,0,0,0) 60%)}
.mkt span.sl{position:absolute}
.mkt > span:not(.sl){position:absolute;left:18px;right:18px;bottom:16px;z-index:1;color:#fff;font-family:var(--f-display);font-stretch:112%;font-weight:700;font-size:17px;text-transform:uppercase;letter-spacing:.02em;line-height:1.2}

/* gallery */
.gal-grid{display:grid;grid-template-columns:2fr minmax(0,1fr) minmax(0,1fr);grid-template-rows:240px 240px;gap:16px}
.gal-grid > *:first-child{grid-row:span 2}
.gal-img{width:100%;height:100%}

/* testimonials */
.tst-grid{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:24px}
.tst{border-top:3px solid var(--red);padding:28px 0 0;margin:0}
.tst blockquote{margin:0 0 24px;font-size:18px;line-height:1.6}
.tst figcaption b{display:block;font-family:var(--f-display);font-stretch:110%;text-transform:uppercase;font-size:15px}
.tst figcaption span{color:var(--mute-l);font-size:14px}
.clients{display:flex;flex-wrap:wrap;align-items:center;justify-content:space-between;gap:28px;margin-top:72px;padding-top:36px;border-top:1px solid var(--line-l)}
.client-img{height:56px;width:auto;min-width:0;filter:grayscale(1);opacity:.75;flex:0 0 auto}
.client-img:hover{filter:none;opacity:1}

/* awards */
.awards.section{background:var(--paper)}
.awards .wrap{display:grid;grid-template-columns:minmax(0,1fr) minmax(0,1.3fr);gap:56px;align-items:center}
.awards h2{font-size:44px}
.awards-img{width:100%}

/* downloads */
.dl-grid{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:24px}
.dl{display:grid;grid-template-columns:120px minmax(0,1fr);gap:22px;align-items:center;border:1px solid var(--line-d);padding:20px;background:var(--ink-2)}
.dl-img{width:120px;box-shadow:0 10px 24px rgba(0,0,0,.5)}
.dl-meta{color:#A9A9AE}
.dl h3{font-family:var(--f-display);font-stretch:112%;font-weight:800;font-size:20px;text-transform:uppercase;margin:6px 0 16px;line-height:1.1}

/* editorial */
.edit-grid{display:grid;grid-template-columns:minmax(0,1fr) minmax(0,1.6fr);gap:72px}
.edit-body h3{font-family:var(--f-display);font-stretch:110%;font-weight:700;font-size:19px;text-transform:uppercase;margin:36px 0 10px}
.edit-body h3:first-child{margin-top:0}
.edit-body p{margin:0 0 14px;color:var(--mute-l)}
.edit-list{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:24px;margin-top:8px}
.edit-list div{border-top:1px solid var(--line-l);padding-top:14px}
.edit-list b{display:block;margin-bottom:6px}

/* contact */
.ct-grid{display:grid;grid-template-columns:minmax(0,1fr) minmax(0,1.2fr);gap:72px}
.ct-phone{font-family:var(--f-display);font-stretch:118%;font-weight:800;font-size:40px;color:#fff;display:block;margin:28px 0 8px}
.ct-note{font-size:14px;color:var(--mute-d);border-left:0;margin-top:28px;padding:16px;background:var(--ink-3)}
.form{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:18px}
.form .full{grid-column:1/-1}
.field{display:flex;flex-direction:column;gap:8px}
/* WEB-12 B0. The field style was written for section.dark and WEB-10's generic
   blk-form block renders the same markup on the white page body, so ten pages
   had white text in an invisible box (WEB-11 C2). The light style is now the
   DEFAULT, because .section's own background is white, and the dark style is
   scoped to .dark -- keyed by the background a field sits on, not by page.
   Palette: the Director's, 2026-11-02; every colour already on the site. */
.field label{font-family:var(--f-mono);font-size:12px;letter-spacing:.1em;text-transform:uppercase;color:#55555C}
.field input,.field textarea{background:#FFFFFF;border:1px solid #8A8A90;color:#111113;font:inherit;padding:14px;min-height:50px}
.field input::placeholder,.field textarea::placeholder{color:#75757C;opacity:1}
/* WEB-15: the focus indicator is a 2px #111113 ring drawn INSIDE the field's
   edge, not a thicker border. Same colour, same thickness, same look, and two
   things better: an outline cannot shift the layout at all, so no padding has
   to be given back; and `outline:none` with a border change is invisible to
   every tool that looks for a focus ring -- verify/web9_keyboard.py reported
   "5 focused elements with no visible ring" on three pages for exactly that
   reason, from WEB-12 until now. */
.field input:focus-visible,.field textarea:focus-visible{
  outline:2px solid #111113;outline-offset:-2px}
.dark .field label{color:var(--mute-d)}
/* WEB-13 B4: .28 composited to rgb(79,79,79) over the contact section's ink
   and measured 2.42:1, below the 3:1 WCAG asks of a field edge and below
   what the light border was specified to meet. .34 reaches 3.10:1. */
.dark .field input,.dark .field textarea{background:transparent;border:1px solid rgba(255,255,255,.34);color:#fff}
.dark .field input::placeholder,.dark .field textarea::placeholder{color:var(--mute-d)}
.dark .field input:focus-visible,.dark .field textarea:focus-visible{
  outline:2px solid #fff;outline-offset:-2px}
.field textarea{min-height:140px;resize:vertical}

/* WEB-15 B1: nothing jumped to may land under the frozen stack. One value,
   derived from the stack's own height, applied to everything anything on
   this site jumps to.

   WEB-38 §4c: the selector is now [id], not a list of seven tag names. The
   list was written from a measurement of what existed in WEB-15 and it had
   already fallen behind: the blog library's year markers are
   <div class="arch" id="y2026">, no tag in the list matches a div, and
   every "2024" in its rail landed under the header. scroll-margin-top does
   nothing at all to an element nobody scrolls to, so naming every id costs
   nothing and cannot fall behind again. */
[id]{scroll-margin-top:calc(var(--ov-stack-h) + 16px)}

/* footer */
.ftr{background:#000;color:var(--mute-d);padding:80px 0 0;font-size:15px}
.ftr-grid{display:grid;grid-template-columns:1.4fr minmax(0,1fr) minmax(0,1fr) 1.2fr;gap:48px}
.ftr .ftr-h{font-family:var(--f-mono);font-size:12px;letter-spacing:.14em;text-transform:uppercase;color:#fff;margin:0 0 18px;font-weight:500}
.ftr ul{list-style:none;margin:0;padding:0;display:flex;flex-direction:column;gap:10px}
.ftr a:hover{color:#fff}
.ftr-logo{width:170px;margin-bottom:22px}
.ftr-blurb{margin:0;max-width:340px}
.socials{display:flex;gap:10px;margin-top:24px}
.socials a{width:44px;height:44px;border:1px solid var(--line-d);display:inline-flex;align-items:center;justify-content:center;color:#fff}
.ftr-bot{border-top:1px solid var(--line-d);margin-top:64px;padding:22px 0;display:flex;justify-content:space-between;gap:16px;flex-wrap:wrap;font-size:13px}

/* ---------- short viewports: keep the hero's buttons above the fold ----------
   Scoped so that 1440x900 and 390x844 are untouched; only genuinely short screens
   (1366x657, 360x640) get the compact treatment. */
@media (min-width:721px) and (max-height:780px){
  /* WEB-27: the headline, the sub-line and the buttons are gone, so
     only the logo is sized here. */
  .hero-in{padding:16px 40px}
}
@media (max-width:720px) and (max-height:760px){
  /* WEB-27: as above. */
  .hero-in{padding:10px 12px}
  .hero-taa{width:44px;right:10px;top:10px}
}

/* ---------- tablet ---------- */
@media (max-width:1100px){
  :root{--gut:28px}
  .hdr-in{--hdr-pad:28px}
  .fams{grid-template-columns:repeat(4,minmax(0,1fr));row-gap:8px}
  .fam:nth-child(4){border-right:0}
  .cfg-grid{grid-template-columns:repeat(3,minmax(0,1fr))}
  .mkt-grid{grid-template-columns:repeat(3,minmax(0,1fr))}
  .ftr-grid{grid-template-columns:minmax(0,1fr) minmax(0,1fr)}
}
/* ---------- phone ---------- */
@media (max-width:720px){
  :root{--gut:16px}
  .section{padding:72px 0}
  .h2{font-size:34px}
  .lead{font-size:17px}
  .hdr-in{--hdr-pad:8px;padding-left:16px}
  .logo{width:170px}
  .hero{min-height:calc(100svh - 56px)}
  .hero-in{padding:16px}
  .ov .hero-awards{display:none}
  .hero-taa{width:52px;right:14px;top:14px}
  .proof-grid{grid-template-columns:repeat(2,minmax(0,1fr))}
  /* WEB-32 §8d: an ODD number of counters stacks on a phone rather
     than leaving a half-empty second row. Four still pair up. */
  .counts{grid-template-columns:repeat(2,minmax(0,1fr))}
  .counts:has(.count:nth-child(3):last-child){grid-template-columns:1fr}
  .proof-item,.count{padding:28px 16px;border-bottom:1px solid var(--line-d)}
  .proof-item:nth-child(2n),.count:nth-child(2n){border-right:0}
  .proof-item:first-child{padding-left:16px}
  .proof-item .proof-t{font-size:14px}
  .count b{font-size:38px}
  .taa h2{font-size:40px}
  .taa-grid{grid-template-columns:minmax(0,1fr);gap:56px}
  .taa-links{grid-template-columns:minmax(0,1fr)}
  .taa-cat{position:relative;left:auto;bottom:auto;width:auto;margin-top:-48px;margin-left:16px;margin-right:16px}
  .spot-grid{grid-template-columns:minmax(0,1fr)}
  .spot{grid-template-rows:200px auto}.spot-img{height:200px}
  .spot-body{padding:24px}
  .spot h3{font-size:24px}
  .feat{grid-template-columns:minmax(0,1fr)}
  .fams{grid-template-columns:repeat(2,minmax(0,1fr))}
  .fam{border-right:0;margin-right:0;border-bottom:1px solid var(--line-l)}
  .prod-grid{grid-template-columns:minmax(0,1fr)}
  .prod-media{height:220px}
  .cfg-grid{grid-template-columns:minmax(0,1fr)}
  .cfg{min-height:0}
  .cfg h3{margin-top:8px}
  .mkt-grid{grid-template-columns:repeat(2,minmax(0,1fr));gap:10px}
  .mkt > span:not(.sl){font-size:13px;left:12px;bottom:10px}
  .gal-grid{grid-template-columns:minmax(0,1fr) minmax(0,1fr);grid-template-rows:200px 140px 140px}
  .gal-grid > *:first-child{grid-column:span 2;grid-row:auto}
  .tst-grid{grid-template-columns:minmax(0,1fr);gap:40px}
  .clients{justify-content:flex-start;gap:20px}
  .client-img{height:44px}
  .awards .wrap{grid-template-columns:minmax(0,1fr);gap:32px}
  .awards h2{font-size:30px}
  .dl-grid{grid-template-columns:minmax(0,1fr)}
  .edit-grid,.ct-grid{grid-template-columns:minmax(0,1fr);gap:40px}
  .edit-list{grid-template-columns:minmax(0,1fr)}
  .ct-phone{font-size:30px}
  .form{grid-template-columns:minmax(0,1fr)}
  .ftr-grid{grid-template-columns:minmax(0,1fr);gap:36px}
}

/* The "In short" line on an FAQ answer. Rendered on series pages and on the
   FAQ page, so it lives in the stylesheet both of them load. */
.fq-tldr{background:#F5F4F1;border-left:3px solid #FF0000;padding:10px 14px}
.fq-tldr b{display:block;font-size:10px;color:var(--mute-l);margin-bottom:4px}

/* Skip link: off-screen until focused, then the first thing on the page.
   A keyboard user must be able to pass the 7-item nav in one keystroke. */
.skip{position:absolute;left:-9999px;top:0;z-index:100;background:#111113;color:#fff;
 padding:12px 18px;font-family:var(--f-mono);font-size:13px;text-decoration:underline}
.skip:focus{left:0}

/* "Last updated", in the footer band. Small, factual, on every page. */
.ftr-updated{font-family:var(--f-mono);font-size:12px;color:var(--mute-d,#8B8B92)}

/* The 404 page's routes back into the site. */
.nf-links{list-style:none;margin:28px 0 0;padding:0;display:flex;flex-wrap:wrap;gap:12px 28px}
.nf-links a{font-family:var(--f-display);font-stretch:110%;font-weight:700;font-size:15px;
 letter-spacing:.06em;text-transform:uppercase;color:var(--red-text);text-decoration:underline;
 text-underline-offset:4px;display:inline-flex;align-items:center;min-height:24px}

/* WEB-11 B2: the "Vanguard LED Displays ·" eyebrow prefix is gone (Architect,
   20:50: titles and eyebrows lead with the page's own unique value). The
   flex-wrap stays -- a long eyebrow still has to wrap rather than overflow. */
.eyebrow{flex-wrap:wrap}

/* Header dropdowns: <details>/<summary>, no script (WEB-10 B5). The summary
   looks and sits exactly like the plain nav links beside it. */
/* static, not relative: the panel's containing block must be
   .nav-dd-wrap, whose left edge is the label's left edge. Positioned
   against .nav-dd -- the chevron -- the panel opened 62 to 101 px to the
   right of the label it belongs to (WEB-17 A3). */
.nav-dd{position:static}
.nav-dd>summary{list-style:none;cursor:pointer;display:flex;align-items:center;gap:6px;
 color:#fff;font-size:13px;white-space:nowrap;min-height:24px}
.nav-dd>summary::-webkit-details-marker{display:none}
.nav-dd>summary:focus-visible{outline:2px solid #fff;outline-offset:3px}
.nav-dd[open]>summary svg{transform:rotate(180deg)}
.nav-menu{position:absolute;top:calc(100% + 10px);left:var(--nav-lbl-pad);z-index:60;margin:0;
 padding:8px 0;list-style:none;background:#111113;border:1px solid #2A2A2F;min-width:232px;
 box-shadow:0 12px 32px rgba(0,0,0,.36)}
.nav-menu li{margin:0}
.nav-menu a{display:flex;align-items:center;min-height:32px;padding:4px 18px;
 color:#fff;font-size:13px;white-space:nowrap}
.nav-menu a:hover,.nav-menu a:focus-visible{background:#FF0000;color:#fff}
/* WEB-16: the rule that used to live here -- @media (max-width:1100px)
   .nav-menu{position:static} -- is gone. It was written when the full menu gave
   way at 1100 and the narrow menu reused .nav-menu as an in-flow sub-list.
   WEB-16 moved the breakpoint to 990 and gave the narrow menu its own markup
   (.mob-panel, .mob-row, .mob-sub), so from 990 to 1100 the rule applied to the
   DESKTOP nav instead: the fly-out laid out in flow, the nav grew from 44 px to
   352, and the header's own contents were pushed to y = -148 -- off the top of
   the screen. Measured at 1100, 1024 and 1000; correct at 1440.

   C1 did not catch it because C1 only ever measured the header CLOSED. A menu
   that is only wrong once you open it needs the check to open it. */

/* WEB-15 B2: the panels open on hover, with no script.

   CSS cannot set a <details>'s `open` attribute, and nothing applied to the
   panel element reveals it either -- display, content-visibility and
   visibility were all measured against a closed panel and none of them
   painted it, because the UA hides the content at the slot. ::details-content
   is the one handle CSS has on that slot, and both engines here support it
   (CSS.supports('selector(::details-content)') is true in Chromium 156 and
   Firefox 157). So the markup does not change: tap still toggles `open`, the
   keyboard still works exactly as it did at WEB-10 and WEB-11, and hover adds
   a second, independent way in.

   Desktop pointers only. A touch screen reports (hover: none) and keeps
   tap-to-open, which is the only thing that makes sense when there is no
   pointer to hover with. */
@media (hover:hover) and (pointer:fine){
  /* Opens on hover. Stays open while focus is inside the PANEL -- which is what
     :focus-within is for here: a pointer that opened a panel and then left it
     while the reader was tabbing through its links must not close it.
     Deliberately NOT `.nav-dd:focus-within`, which would also match the summary
     and so open the panel merely because Tab reached it. That would put the
     panel's links into the tab order and change the keyboard path, which WEB-10
     and WEB-11 settled and this order says to keep. Measured both ways: with
     the narrow rule the walk gives 0 tab stops inside a panel, as before. */
  /* WEB-16: the hover target is the WRAPPER, not the <details>. The label is a
     link beside the chevron now, so hovering "Products" puts the pointer over
     .nav-dd-wrap and never over .nav-dd -- keying on .nav-dd meant the panel
     stopped opening on hover the moment the label was split out. Measured: it
     did. */
  .nav-dd-wrap:hover>.nav-dd::details-content,
  .nav-dd-wrap:has(.nav-menu:focus-within)>.nav-dd::details-content{
    content-visibility:visible; transition-delay:0s}
  .nav-dd-wrap:hover>.nav-dd>summary svg,
  .nav-dd-wrap:has(.nav-menu:focus-within)>.nav-dd>summary svg{
    transform:rotate(180deg)}

  /* the fly-outs, the same rule one level down */
  .nav-has-fly:hover>.nav-fly-row>.nav-fly::details-content,
  .nav-has-fly:has(.nav-fly-menu:focus-within)>.nav-fly-row>.nav-fly::details-content{
    content-visibility:visible; transition-delay:0s}
  .nav-fly::details-content{transition:content-visibility 0s 150ms;
    transition-behavior:allow-discrete}

  /* The bridge. The panel sits 10px below the item, and a pointer crossing
     that gap would otherwise leave the item, close the panel, and never
     arrive. ::before fills the gap as part of the panel's own hover area, so
     there is no gap to fall through. */
  .nav-dd .nav-menu::before{content:"";position:absolute;left:0;right:0;
    top:-12px;height:12px}
  /* the fly-out's bridge runs sideways, across the gap to its parent row */
  .nav-fly-menu::before{content:"";position:absolute;top:0;bottom:0;
    right:-14px;width:14px}

  /* A short delay on CLOSING, so a pointer that clips the edge of the item on
     its way somewhere else does not snap the panel shut. The delay belongs on
     the resting rule and is cancelled in the open states above; put on both and
     it delays opening too, which measured as a 150 ms lag before the panel
     appeared. content-visibility is a discrete property, so the transition
     needs allow-discrete to delay at all. */
  .nav-dd::details-content{transition:content-visibility 0s 150ms;
    transition-behavior:allow-discrete}
}

/* WEB-11 B1: every component that puts white lettering on #FF0000 wears the
   halo. One token, applied here, never per page. */
/* WEB-17 B3: every TOP-LEVEL label, whatever its tag. This selector used to
   be `.hdr .nav > a:not(.nav-pill)` alone, which named direct <a> children of
   .nav -- every nav item at WEB-11. WEB-16 B1 moved the three dropdown labels
   inside .nav-dd-wrap, so they stopped being direct children and silently lost
   the halo, while FAQ and Blogs kept it. That is why two items looked outlined
   and four did not. Named by what they ARE now, not by where they sit.
   The pill stays out: it is white on BLACK, not on red, so the halo rule does
   not apply to it. */
.hdr .nav > a:not(.nav-pill),
.hdr .nav > .nav-dd-wrap > .nav-lbl,
.nav-dd > summary,
.btn-red,
/* WEB-21 §3g: the menu's Contact Us is white on #FF0000 now, which is every
   other red-on-white element on the site -- so it takes the same WEB-11 halo
   they do. Without it the glyphs measure 4.0:1 against the red; inside it
   they measure against #5A0000. */
.mob-pill,
.taa-links a:hover,
.nav-menu a:hover,
.nav-menu a:focus-visible{text-shadow:var(--halo-on-red)}

/* ---------- WEB-16 B2: the configuration icons ----------------------------
   The icon carries the weight the "01"-"05" number used to, so it is sized to
   that: about 64 px tall at 1440, smaller on phones. The colour is chosen by
   the SURFACE the component sits on -- white on the home page's dark tiles,
   black on the configuration page's paper section -- and never by which page
   it is. Alt text is empty on both: the tile's heading and the section's h2
   already name the configuration, and a second announcement is noise. */
.cfg-ico{display:block;margin:0 0 14px}
.cfg-ico-box{display:block;width:64px;height:64px}
.cfg-icon{margin:0 0 18px}
.cfg-icon-box{display:block;width:64px;height:64px}
@media (max-width:720px){
  .cfg-ico-box,.cfg-icon-box{width:48px;height:48px}
}

/* ---------- WEB-16 B5: cards for pages that are not built yet -------------
   One rule set, keyed on the card's own has-a-page test rather than on a list
   of names: a card WITH a page is an <a>, a card without is a <div>, and has
   been since WEB-11. So `div.pc` and `.ser--nolink` are exactly the cards the
   Architect means, on the hub, the family pages, the markets and the
   configurations alike, and a series that gains a page loses its badge with no
   edit anywhere.

   The badge is decoration; the screen-reader line "Page coming soon" inside the
   card is the real announcement, which is why the badge's text lives in CSS
   content and is not read twice. */
div.pc .pc-media,.ser--nolink .ser-media{position:relative}
div.pc .pc-media .sl,.ser--nolink .ser-media .sl{opacity:.55}
div.pc .pc-media::after,.ser--nolink .ser-media::after{
  content:"Coming soon";position:absolute;left:0;top:0;z-index:2;
  font-family:var(--f-mono);font-size:10px;letter-spacing:.12em;
  text-transform:uppercase;color:#fff;background:#111113;padding:5px 9px;
  pointer-events:none}

/* ---------- WEB-16 B3/B4: carousels, with no script ----------------------
   Every carousel on the site -- the family heroes, the series galleries, the
   Military installation slideshow -- runs on this one mechanism.

   The honest limit first, because the Director asked for it up front. CSS can
   auto-advance and CSS can hold a manually chosen slide, but it cannot know
   which the reader wants once both are in play. So: **auto-advance runs while
   nothing has been chosen, and the first manual choice stops it for good.**
   That is the fallback the Director named, and it is reached by making the
   default state have NO radio checked -- slide one shows because nothing is
   checked, not because a radio says so -- so `:has(input:checked)` means
   exactly "the reader has chosen" and nothing else.

   Five seconds a slide. Paused while the pointer is over the carousel or focus
   is inside it. Under prefers-reduced-motion there is no auto-advance at all
   and the manual controls are the only way through, which is the right answer
   rather than a degraded one. */
@keyframes car2{0%{opacity:1;visibility:visible}48.8000%{opacity:1;visibility:visible}50.0000%{opacity:0;visibility:hidden}100%{opacity:0;visibility:hidden}}
@keyframes car3{0%{opacity:1;visibility:visible}32.1333%{opacity:1;visibility:visible}33.3333%{opacity:0;visibility:hidden}100%{opacity:0;visibility:hidden}}
@keyframes car4{0%{opacity:1;visibility:visible}23.8000%{opacity:1;visibility:visible}25.0000%{opacity:0;visibility:hidden}100%{opacity:0;visibility:hidden}}
@keyframes car5{0%{opacity:1;visibility:visible}18.8000%{opacity:1;visibility:visible}20.0000%{opacity:0;visibility:hidden}100%{opacity:0;visibility:hidden}}
@keyframes car6{0%{opacity:1;visibility:visible}15.4667%{opacity:1;visibility:visible}16.6667%{opacity:0;visibility:hidden}100%{opacity:0;visibility:hidden}}
@keyframes car7{0%{opacity:1;visibility:visible}13.0857%{opacity:1;visibility:visible}14.2857%{opacity:0;visibility:hidden}100%{opacity:0;visibility:hidden}}
@keyframes car8{0%{opacity:1;visibility:visible}11.3000%{opacity:1;visibility:visible}12.5000%{opacity:0;visibility:hidden}100%{opacity:0;visibility:hidden}}

.car,.gal{--car-step:5s}
/* nothing chosen yet: the slides cycle */
.gal:not(:has(.galsel:checked)) .gal-main>.gal-slide,
.car:not(:has(.carsel:checked)) .car-main>.car-slide{
  opacity:0;visibility:hidden;animation-timing-function:ease;
  animation-iteration-count:infinite;
  /* fill-mode NONE, deliberately. With `both` the 0% frame -- which is the
     visible one -- is applied during the delay, so every slide showed at once
     until its turn came to disappear. Measured: at t=0 all six were visible.
     With `none` a slide keeps its resting style (hidden) until its delay has
     elapsed, which is what a delay is for. */
  animation-fill-mode:none}
.gal[data-n="2"]:not(:has(.galsel:checked)) .gal-main>.gal-slide,
.car[data-n="2"]:not(:has(.carsel:checked)) .car-main>.car-slide{animation-name:car2;animation-duration:10s}
.gal[data-n="3"]:not(:has(.galsel:checked)) .gal-main>.gal-slide,
.car[data-n="3"]:not(:has(.carsel:checked)) .car-main>.car-slide{animation-name:car3;animation-duration:15s}
.gal[data-n="4"]:not(:has(.galsel:checked)) .gal-main>.gal-slide,
.car[data-n="4"]:not(:has(.carsel:checked)) .car-main>.car-slide{animation-name:car4;animation-duration:20s}
.gal[data-n="5"]:not(:has(.galsel:checked)) .gal-main>.gal-slide,
.car[data-n="5"]:not(:has(.carsel:checked)) .car-main>.car-slide{animation-name:car5;animation-duration:25s}
.gal[data-n="6"]:not(:has(.galsel:checked)) .gal-main>.gal-slide,
.car[data-n="6"]:not(:has(.carsel:checked)) .car-main>.car-slide{animation-name:car6;animation-duration:30s}
.gal[data-n="7"]:not(:has(.galsel:checked)) .gal-main>.gal-slide,
.car[data-n="7"]:not(:has(.carsel:checked)) .car-main>.car-slide{animation-name:car7;animation-duration:35s}
.gal[data-n="8"]:not(:has(.galsel:checked)) .gal-main>.gal-slide,
.car[data-n="8"]:not(:has(.carsel:checked)) .car-main>.car-slide{animation-name:car8;animation-duration:40s}

/* paused under the pointer, and while a keyboard is inside */
.gal-main>.gal-slide:nth-of-type(1),.car-main>.car-slide:nth-of-type(1){animation-delay:0s}
.gal-main>.gal-slide:nth-of-type(2),.car-main>.car-slide:nth-of-type(2){animation-delay:5s}
.gal-main>.gal-slide:nth-of-type(3),.car-main>.car-slide:nth-of-type(3){animation-delay:10s}
.gal-main>.gal-slide:nth-of-type(4),.car-main>.car-slide:nth-of-type(4){animation-delay:15s}
.gal-main>.gal-slide:nth-of-type(5),.car-main>.car-slide:nth-of-type(5){animation-delay:20s}
.gal-main>.gal-slide:nth-of-type(6),.car-main>.car-slide:nth-of-type(6){animation-delay:25s}
.gal-main>.gal-slide:nth-of-type(7),.car-main>.car-slide:nth-of-type(7){animation-delay:30s}
.gal-main>.gal-slide:nth-of-type(8),.car-main>.car-slide:nth-of-type(8){animation-delay:35s}

.gal:hover .gal-slide,.gal:focus-within .gal-slide,
.car:hover .car-slide,.car:focus-within .car-slide{animation-play-state:paused}

@media (prefers-reduced-motion:reduce){
  .gal .gal-slide,.car .car-slide{animation:none !important}
  .gal:not(:has(.galsel:checked)) .gal-main>.gal-slide:first-of-type,
  .car:not(:has(.carsel:checked)) .car-main>.car-slide:first-of-type{
    opacity:1;visibility:visible}
}

/* ---------- the family hero carousel (B3) ---------- */
.car{position:relative}
.carsel{position:absolute;width:1px;height:1px;opacity:0;margin:0;pointer-events:none}
.car-main{position:relative;aspect-ratio:16/9;overflow:hidden;background:var(--ink-2)}
.car-slide{position:absolute;inset:0;opacity:0;visibility:hidden}
.car-slide .sl{width:100%;height:100%}
.car-dots{display:flex;gap:8px;justify-content:center;margin-top:12px}
.car-dots label{cursor:pointer}
.carsel:nth-of-type(1):checked ~ .car-dots label:nth-of-type(1),
.carsel:nth-of-type(2):checked ~ .car-dots label:nth-of-type(2),
.carsel:nth-of-type(3):checked ~ .car-dots label:nth-of-type(3),
.carsel:nth-of-type(4):checked ~ .car-dots label:nth-of-type(4),
.carsel:nth-of-type(5):checked ~ .car-dots label:nth-of-type(5),
.carsel:nth-of-type(6):checked ~ .car-dots label:nth-of-type(6){background:#FF0000}
.carsel:focus-visible ~ .car-dots label{outline:2px solid #111113;outline-offset:2px}
.carsel:nth-of-type(1):checked ~ .car-main > .car-slide:nth-of-type(1),
.carsel:nth-of-type(2):checked ~ .car-main > .car-slide:nth-of-type(2),
.carsel:nth-of-type(3):checked ~ .car-main > .car-slide:nth-of-type(3),
.carsel:nth-of-type(4):checked ~ .car-main > .car-slide:nth-of-type(4),
.carsel:nth-of-type(5):checked ~ .car-main > .car-slide:nth-of-type(5),
.carsel:nth-of-type(6):checked ~ .car-main > .car-slide:nth-of-type(6){
  opacity:1;visibility:visible}

/* ---------- WEB-16 B11: the awards ----------------------------------------
   One row, all six the same height, fitted so none is cropped, wrapping to two
   rows of three on a phone. The old set was ten 96 px files painted up to 474
   px wide -- "horrible, and too large" (Architect) -- and every one of them is
   gone. */
.awards-row{list-style:none;margin:0;padding:0;display:flex;flex-wrap:wrap;
  gap:28px;align-items:center}
.awards-row .award-img{display:block;height:120px;width:auto;max-width:150px}
/* WEB-18 §3b: the six awards sit centred on /testimonials/, where they are now
   the only awards on the page. Scoped to that page -- the home page's row was
   not part of the ruling and is unchanged. */
.pg-testi .awards-row{justify-content:center}
.awards-row--v{flex-direction:column;gap:14px;align-items:flex-start}
.awards-row--v .award-img{height:56px;max-width:84px}
@media (max-width:720px){
  .awards-row{gap:16px;justify-content:center}
  .awards-row>li{flex:0 0 calc(33.333% - 11px)}
  .awards-row .award-img{height:72px;max-width:100%}
  .awards-row--v>li{flex:none}
}

/* ---------- WEB-16 B14: Upcoming / Past shows ---------- */
.evt-tabs{position:relative}
.evt-sel{position:absolute;width:1px;height:1px;opacity:0;margin:0;pointer-events:none}
.evt-bar{display:flex;gap:0;border-bottom:1px solid var(--line-l);margin-bottom:28px}
.evt-bar label{cursor:pointer;padding:14px 20px;font-family:var(--f-display);
  font-stretch:110%;font-weight:700;font-size:15px;text-transform:uppercase;
  letter-spacing:.04em;color:var(--mute-l);border-bottom:3px solid transparent;
  min-height:24px;display:flex;align-items:center;gap:8px}
.evt-bar label .mono{font-size:12px;color:var(--mute-l)}
.evt-pane{display:none}
/* Named panes, not counted ones. `:nth-of-type` counts among siblings of the
   same ELEMENT type, and .evt-tabs' div children are .evt-bar, then the two
   panes -- so .evt-pane:nth-of-type(1) named the BAR and matched nothing,
   and :nth-of-type(2) named the Upcoming pane. The result: with the default
   Upcoming radio checked both panes were display:none and the page showed no
   events at all, and choosing "Past shows" revealed the Upcoming pane.
   Measured. A class per pane cannot drift when a sibling is added. */
.evt-sel:nth-of-type(1):checked ~ .evt-pane--up,
.evt-sel:nth-of-type(2):checked ~ .evt-pane--past{display:block}
.evt-sel:nth-of-type(1):checked ~ .evt-bar label:nth-of-type(1),
.evt-sel:nth-of-type(2):checked ~ .evt-bar label:nth-of-type(2){
  color:var(--text-l);border-bottom-color:#FF0000}
.evt-sel:focus-visible ~ .evt-bar label{outline:2px solid #111113;outline-offset:-2px}
.evt-none{color:var(--mute-l)}

/* ---------- WEB-16 B10: About Us ------------------------------------------
   Each photo about half the content width, beside its paragraph, alternating
   sides from 1024 up and stacked on a phone. Never wider than the file can
   fill at 1.75x, which is why the aging-test photo sits narrower -- it is
   573 px and that is the honest limit until a bigger one arrives. */
@media (min-width:1024px){
  .pg-about .blk-prose + .blk-imgs,
  .pg-about .blk-imgs{float:right;width:48%;margin:0 0 24px 32px}
  .pg-about .blk-imgs:nth-of-type(even){float:left;margin:0 32px 24px 0}
  .pg-about .blk-imgs::after{content:"";display:block;clear:both}
  .pg-about .blk-prose{overflow:hidden}
}
.pg-about .blk-img-box{width:100%;height:auto;max-height:none}

/* ---------- WEB-16: a heading never wider than its column ------------------
   The Director's finding, and the correction to my own test: comparing BOXES
   finds nothing, because the box is 260 px wide while "EINSTEINIUM" inside it
   is 387. scrollWidth against clientWidth finds it.

   The fix is by rule, not per heading. Each heading carries --lw, the length
   in characters of its longest unbreakable run, set from the record by the
   longest_run filter. Its container is a query container, so 100cqi is the
   column's own width at whatever viewport, and the font-size is the smaller of
   the design size and the size at which that run still fits.

   0.75em per character is the measured advance, and the first attempt used
   0.58 and did not fix anything: the probe set the face with the `font`
   shorthand, which drops font-stretch, and this display face runs at 118%. The
   real figure came from the rendered line box -- "EINSTEINIUM" is 319 px at
   39.5 px, which is 0.733 em a character. A single factor cannot be exact,
   because letters differ: "TRANSPORTATION" measures 0.806 em a character in
   the same face. 0.88 is the worst observed plus headroom, which is the only
   honest way to use one number for every word. The 0.97
   leaves room for the last glyph's side bearing.

   No hyphenation and no word breaking: the heading gets smaller, it never
   gets cut. */
/* .h-display.h-fit, not .h-fit: products.css loads after ov.css and sets
   .pg-title{font-size:40px}, which beat a single-class rule on equal
   specificity and left the market h1 at its full size while carrying the
   class, the variable and a working container. Two classes settle it wherever
   the sheet sits in the order. */
.h-display.h-fit{font-size:min(var(--h-fit-base,48px),
  calc(100cqi * 0.97 / (var(--lw,8) * 0.88)))}
/* The query container must be the element the heading actually fills. First
   attempt put it on .pp, which is full-bleed, so 100cqi came back as the whole
   viewport (390) instead of the padded column (358) and the heading was sized
   for a box bigger than it had. .wrap IS that box. .spec-side is the series
   page's own 260 px column. */
/* The container is the heading's OWN parent, selected with :has(). Putting it
   on .wrap was still wrong: a heading often sits in a grid cell inside .wrap,
   so 100cqi came back as the full 944 px row while the heading had 345. The
   parent of the heading is the only box that is always the right one. */
:has(> .h-fit){container-type:inline-size}
.spec-side{container-type:inline-size}
.h-display.pg-title.h-fit{--h-fit-base:64px}
.h-display.h2.h-fit{--h-fit-base:48px}
.h-display.h-edit.h-fit{--h-fit-base:40px}
/* WEB-20: .mt-title and .ch-title name their own base, in their own sheets
   (the Architect's 80 px and 96 px). This catch-all is three :not()s deep and
   so outranks a three-class rule; excluding them here keeps ONE place
   deciding the default instead of an escalating specificity fight. */
.h-display.h-fit:not(.h2):not(.pg-title):not(.h-edit):not(.mt-title):not(.ch-title):not(.cf-title){--h-fit-base:64px}
/* the configuration tiles' headings: the display face, uppercase, 24px */
.cfg-title.h-fit{--h-fit-base:24px;font-size:min(24px,
  calc(100cqi * 0.97 / (var(--lw,8) * 0.88)))}
/* The download card titles are not .h-display, so they take their own base
   AND their own factor: this is the body face, not the 118%-stretched display
   one. 0.62 left "CONTROLLERS" 2 px over; measured 0.794 for "CATALOGUE"
   once the real font had loaded, so 0.85. Every figure before this one came
   from a run that measured before document.fonts.ready and was therefore
   measuring the fallback face. */
.dl-title.h-fit{--h-fit-base:20px;font-size:min(20px,
  calc(100cqi * 0.97 / (var(--lw,8) * 0.85)))}
@media (max-width:720px){
  .h-display.pg-title.h-fit{--h-fit-base:40px}
  .h-display.h2.h-fit{--h-fit-base:34px}
}


/* ---------- WEB-21 §3e: carousel dots ------------------------------------
   Round, 9 px, the current slide's dot #FF0000 and the rest #C9C8C4, centred
   below the photograph. They replace the 28 x 4 px dashes.

   THE DIRECTOR'S QUESTION -- can a dot track a no-script carousel without
   drifting? Yes, and not by luck. The slides are a pure CSS animation: N
   slides, 5 s each, duration N x 5 s, slide i delayed i x 5 s. Each dot is
   given THE SAME animation-duration and THE SAME animation-delay as the slide
   it belongs to, with keyframes whose breakpoints are the same percentages.
   Two animations with identical timing on one document timeline advance
   together by definition -- there is no second clock to drift against. The
   pause-on-hover rule below names the dots and the slides in one selector for
   the same reason, and prefers-reduced-motion stops both and leaves the first
   of each showing.

   The percentages are generated from the same arithmetic as the slide
   keyframes rather than typed again. */
@keyframes dot2{0%{background:#FF0000}48.8000%{background:#FF0000}50.0000%{background:#C9C8C4}100%{background:#C9C8C4}}
@keyframes dot3{0%{background:#FF0000}32.1333%{background:#FF0000}33.3333%{background:#C9C8C4}100%{background:#C9C8C4}}
@keyframes dot4{0%{background:#FF0000}23.8000%{background:#FF0000}25.0000%{background:#C9C8C4}100%{background:#C9C8C4}}
@keyframes dot5{0%{background:#FF0000}18.8000%{background:#FF0000}20.0000%{background:#C9C8C4}100%{background:#C9C8C4}}
@keyframes dot6{0%{background:#FF0000}15.4667%{background:#FF0000}16.6667%{background:#C9C8C4}100%{background:#C9C8C4}}
@keyframes dot7{0%{background:#FF0000}13.0857%{background:#FF0000}14.2857%{background:#C9C8C4}100%{background:#C9C8C4}}
@keyframes dot8{0%{background:#FF0000}11.3000%{background:#FF0000}12.5000%{background:#C9C8C4}100%{background:#C9C8C4}}

.car-dots label{width:9px;height:9px;border-radius:50%;background:#C9C8C4}
.car-dots label:hover{background:var(--mute-l)}
.car:not(:has(.carsel:checked)) .car-dots label{
  animation-timing-function:step-end;animation-iteration-count:infinite;
  animation-fill-mode:none}
.car[data-n="2"]:not(:has(.carsel:checked)) .car-dots label{animation-name:dot2;animation-duration:10s}
.car[data-n="3"]:not(:has(.carsel:checked)) .car-dots label{animation-name:dot3;animation-duration:15s}
.car[data-n="4"]:not(:has(.carsel:checked)) .car-dots label{animation-name:dot4;animation-duration:20s}
.car[data-n="5"]:not(:has(.carsel:checked)) .car-dots label{animation-name:dot5;animation-duration:25s}
.car[data-n="6"]:not(:has(.carsel:checked)) .car-dots label{animation-name:dot6;animation-duration:30s}
.car[data-n="7"]:not(:has(.carsel:checked)) .car-dots label{animation-name:dot7;animation-duration:35s}
.car[data-n="8"]:not(:has(.carsel:checked)) .car-dots label{animation-name:dot8;animation-duration:40s}

.car-dots label:nth-of-type(1){animation-delay:0s}
.car-dots label:nth-of-type(2){animation-delay:5s}
.car-dots label:nth-of-type(3){animation-delay:10s}
.car-dots label:nth-of-type(4){animation-delay:15s}
.car-dots label:nth-of-type(5){animation-delay:20s}
.car-dots label:nth-of-type(6){animation-delay:25s}
.car-dots label:nth-of-type(7){animation-delay:30s}
.car-dots label:nth-of-type(8){animation-delay:35s}

/* the dots pause with the slides, in one selector, so they cannot pause
   separately */
.car:hover .car-dots label,.car:focus-within .car-dots label{
  animation-play-state:paused}
@media (prefers-reduced-motion:reduce){
  .car .car-dots label{animation:none !important}
  .car:not(:has(.carsel:checked)) .car-dots label:first-of-type{background:#FF0000}
}


/* ---------- WEB-21 §3f: ONE icon-grid treatment, defined once -------------
   `.icg` was in controllers.css, which only the Controllers pages load, while
   the All-In-One pages ran a second grid of their own (`.bi-grid`) that did
   the same job with different numbers. One treatment, in the shared sheet, so
   every page that shows a row of feature icons shows the same thing.

   Bordered cells on WHITE, 80 px red line icons, titles in BLACK.

   The black title is the fix for 22:25. `.ic` has always painted its cell
   white, but `.ic h3` named no colour, so in a `section dark` it inherited
   the section's white and the heading was white on white -- invisible on
   Infinity ULTRA, Sentinel and the Fiber card. Naming the colour makes the
   grid self-contained: it looks the same whichever section it is dropped in,
   which is the point of defining it once. */
.icg{display:grid;border-top:1px solid var(--line-l);
  border-left:1px solid var(--line-l)}
.icg.c2{grid-template-columns:repeat(2,minmax(0,1fr))}
.icg.c3{grid-template-columns:repeat(3,minmax(0,1fr))}
.icg.c4{grid-template-columns:repeat(4,minmax(0,1fr))}
.ic{border-right:1px solid var(--line-l);border-bottom:1px solid var(--line-l);
  padding:40px 32px 44px;display:flex;flex-direction:column;gap:16px;
  background:#fff}
.ic svg{color:#FF0000;margin-bottom:8px;width:80px;height:80px}
.ic h3{font-family:var(--f-display);font-stretch:112%;font-weight:800;
  font-size:22px;text-transform:uppercase;margin:0;line-height:1.15;
  color:#111113}
.ic p{margin:0;color:var(--mute-l);font-size:16px;line-height:1.6}
/* "160 WORKSTATIONS" is one long word in a four-column cell (WEB-20 §5) */
.icg.c4 .ic h3{font-size:clamp(18px,1.4vw,21px)}
@media (max-width:1023px){.icg.c4{grid-template-columns:repeat(2,minmax(0,1fr))}}
@media (max-width:600px){
  .icg.c2,.icg.c3,.icg.c4{grid-template-columns:1fr}
  .ic{padding:28px 20px 32px}
}
/* ---------- WEB-24 §4: the contact form's own state --------------------
   The honeypot is off-screen rather than display:none -- a bot skips what is
   hidden and fills what it can see in the markup -- and out of the tab order
   and the accessibility tree, so no person meets it. */
.hp{position:absolute;left:-9999px;width:1px;height:1px;overflow:hidden}
/* Errors are written into the page by the server; nothing here needs a
   script to be read aloud. */
.form-errs{background:#5A0000;border:2px solid #FF0000;padding:14px 16px;margin:0 0 6px}
.form-errs p{margin:0 0 8px;color:#fff;font-size:15px}
.form-errs ul{margin:0;padding-left:20px}
.form-errs li{color:#fff;font-size:14px;line-height:1.6}
.form-errs a{color:#fff;text-decoration:underline}
.field--bad input,.field--bad textarea{border-color:#FF0000;outline:2px solid #FF0000;outline-offset:-2px}
.field-err{margin:6px 0 0;font-size:13px;color:#FF6B6B}
.req{color:#FF0000}
.form-note{margin:4px 0 0;font-size:13px;color:var(--mute-d)}
.form-note a{text-decoration:underline}

/* ---------- WEB-47 §1: the reviewers' bar is not here ------------------
   It left with the rest of Preview -- the bar, the notes layer, the change
   list, the login page -- into a separate application that the public
   never passes through. What is left is the header the public sees, which
   is exactly what WEB-25's version of this comment said it would leave.

   THE SEAM, and what replaces WEB-38's answer to it. WEB-38 froze the bar
   and the header as ONE position:fixed box, because two independently
   positioned bars can round apart by a fraction at 80% or 67% zoom and
   let a hairline of the page show between them. That was measured, not
   guessed. The single box cannot exist now: the bar above belongs to
   another application and this stylesheet does not own it. Preview takes
   the other available answer and OVERLAPS them -- it pulls the header two
   pixels up under its own opaque bar, so there is no gap for a rounding
   error to open. preview/inject.py is where that is written, and
   VanguardPreview/verify/web47_vm.py measures it at three
   zooms, at rest and with the header stuck. */


@media (max-width:600px){
  /* the two words go, the NAME stays: one line, 46px, at every width */

}

/* WEB-25a §11: the search field's label. Read aloud, never drawn. It lived
   only in series.css, which the header does not depend on. */
.vh{position:absolute;width:1px;height:1px;margin:-1px;padding:0;
  overflow:hidden;clip:rect(0 0 0 0);white-space:nowrap;border:0}

/* ===== WEB-26 §6: the top of the home page ================================
   The Architect rebuilt the top of the live home page on 5 November and OV
   follows it. Three things changed and nothing else: the awards column left
   the hero, a values tagline arrived in it, and a black band carrying the
   product banner, the "broadest range" paragraph and the awards now sits
   directly below the hero.

   The figures below are the ones measured off the live site at 1440, 768
   and 375 and written into the order. OV's hero keeps its own height --
   §6.1 says the hero is "as OV has it today" -- so only the tagline's
   placement is taken from the live CSS. */

/* -- the values tagline ---------------------------------------------------
   One element, two placements. At 1024 and wider it is positioned over the
   hero, 6vh above its bottom edge. Below that the hero is no longer a full
   screen, so the tagline drops into the normal flow under the logo. There
   is no script: the breakpoint does all of it. */
/* WEB-27 §3b: the live site's two smaller sizes, by width, as it has
   them -- 420px capped at 70% below 1024, and 300px capped at 85% below
   600. OV's older rules shrank the logo on SHORT screens as well, to make
   room for a headline and two buttons that no longer exist. */
@media (max-width:1023px){
  .hero-logo{width:420px;max-width:70%}
}
@media (max-width:599px){
  .hero-logo{width:300px;max-width:85%}
}

.hero-values{position:absolute;left:50%;bottom:6vh;transform:translateX(-50%);
  width:min(800px,65vw);z-index:1;pointer-events:none}
.hero-values-img{width:100%}
/* WEB-26 lifted the hero's content to clear the tagline from the buttons.
   WEB-27 §3a removed the buttons, the headline and the sub-line, so there
   is nothing left to clear and §3c says take the lift out. Removed; the
   tagline has not moved and is still 6vh above the hero's bottom edge. */

@media (max-width:1023px){
  /* in the flow, under the logo. `order` puts it there without moving it
     in the markup, where it has to stay last so the hero's own copy is
     read first. */
  .hero{display:block;min-height:0;padding:48px 0 56px}
  .hero-values{position:static;transform:none;width:60%;max-width:560px;
    margin:0 auto 32px}
  .hero-in{margin:0 auto}
}
@media (max-width:599px){
  .hero-values{width:92%}
}

/* -- the black band -------------------------------------------------------
   One background, running from the top of the banner to 40px below the
   awards, so the banner, the paragraph and the awards read as one block
   rather than three stripes. */
.hometop{position:relative;z-index:1;background:var(--ink,#0A0A0B);
  padding:0 0 40px}
/* WEB-43 §3: the strip of eight, built on the page.
   It matches the bitmap it replaces: the same black ground, the same eight
   in the same order, a picture in each cell sitting on ONE shared baseline,
   the name under it and the short line under that.

   The baseline is the whole trick. In the bitmap every product was drawn
   bottom-aligned on y=549 whatever its shape -- Houdini's is short and wide,
   AiO Mobile's is tall and narrow. Here each picture box is the same height
   and `object-position: bottom` sits the artwork on the floor of it, so the
   row reads as one line of products rather than eight boxes.

   Three rows per cell, all the same height across the row, so the names
   line up and the lines line up: subgrid would say that in one word, and
   this says it with a nested grid, which every browser the Architect's
   reviewers use already has. */
/* Sentence case and 31px, which is what the bitmap drew: its heading is
   56px in a 2560-wide image, and the image is painted 1440 wide on a laptop
   -- 56 x 1440/2560 = 31.5. Deliberately NOT .h-display, which would put it
   in capitals; the bitmap's is not. */
.ht-h{color:#fff;text-align:center;font-family:var(--f-display);
  font-stretch:110%;font-weight:700;font-size:31px;line-height:1.15;
  letter-spacing:-.01em;margin:0;padding:44px 20px 0;text-transform:none}
/* the short red rule the bitmap drew under the heading */
.ht-h::after{content:"";display:block;width:78px;height:3px;
  background:var(--red);margin:14px auto 0}
.ht-strip{list-style:none;margin:30px auto 0;padding:0 24px;display:grid;
  grid-template-columns:repeat(8,minmax(0,1fr));gap:0 10px;
  align-items:end;max-width:1520px}
.ht-cell{display:grid;grid-row:span 3;grid-template-rows:subgrid}
@supports not (grid-template-rows: subgrid){
  /* no subgrid: the picture box's fixed height keeps the baseline, and the
     name block gets a floor so the lines still start level */
  .ht-cell{display:block}
  .ht-name{min-height:2.4em}
}
.ht-card{display:grid;grid-row:span 3;grid-template-rows:subgrid;
  text-align:center;color:#fff;text-decoration:none;padding:0 4px 8px}
@supports not (grid-template-rows: subgrid){ .ht-card{display:block} }
/* WEB-45 §4: every picture is vertically centred on ONE line. The box is
   the same height in every cell and the artwork is centred inside it, so
   the centres coincide to the pixel whatever each product's shape. WEB-43
   sat them on a shared FLOOR instead, which is what the bitmap drew; the
   Architect asked for the centre line (14:51). The names still start on
   one shared line under the pictures, because the box's height is fixed
   and the grid row is sized by it. */
.ht-pic{display:block;align-self:center}
/* 359px is the tallest product in the bitmap, at 1440 that is 202px.
   The box is a fixed-height stage and the picture is centred in it, so
   every picture's centre lands on the same line. The IMG is sized to its
   own aspect rather than stretched to the box -- `.sl>img` sets
   width:100% height:100% for every other slot on the site, and that is
   overridden here -- so the element IS the painted picture. That is what
   lets the stroke below hug the photograph instead of boxing the stage. */
.ht-pic-box{width:100%;height:202px;display:flex;
  align-items:center;justify-content:center}
.ht-pic-box>img{width:auto;height:auto;max-width:100%;max-height:100%;
  object-fit:contain}

/* WEB-45 §3b: the stroke, in ONE place.
   A full-frame photograph has its own rectangular ground and reads as a
   picture pasted on the black; a 1px keyline is what separates it from
   the band. Sidewinder's photograph carried exactly such a line baked
   into it -- one pixel of white round all four sides -- and that is the
   stroke the Architect saw and asked the others to match. The baked line
   has been trimmed off its derivative, so all four now get the same thing
   from this rule and no cell is a pixel heavier than another.

   box-shadow, not border: a border would take a pixel out of the picture
   box and shift the centre line by half a pixel on four cells of eight.

   Cutouts get nothing. A product standing on transparency has no edge for
   a keyline to follow, and a box drawn round it would be a box round
   nothing. Which is which is decided by the image itself -- see
   ops/build_assets.py's framed(). */
.ht-framed .ht-pic-box>img{box-shadow:0 0 0 1px rgba(255,255,255,.92)}
.ht-name{display:block;font-family:var(--f-display);font-stretch:110%;
  font-weight:700;font-size:21px;line-height:1.15;margin:12px 0 0;
  color:#fff;align-self:start}
.ht-line{display:block;font-size:14.5px;line-height:1.4;margin:9px 0 0;
  color:#D8D8DC;align-self:start}
.ht-card:hover .ht-name{color:var(--red)}
.ht-card:hover .ht-pic-box>img{transform:translateY(-3px)}
.ht-pic-box>img{transition:transform .14s ease}
.ht-card:focus-visible{outline:2px solid #fff;outline-offset:3px}
.ht-wrap{padding-top:40px}
/* §6.4: white on the same black. */
/* WEB-39 §3a: the brand red, not white (the Architect, 09:13). Measured
   against this band's own background #0A0A0B: 4.95:1, which clears
   WCAG AA for body text (4.5:1), so the brand red itself is used and no
   lighter substitute was needed. */
.ht-lede{color:var(--red-text);font-size:19px;line-height:1.6;max-width:980px;
  margin:0 auto;text-align:center}
/* §6.5: 643 x 93, centred, never wider than 90% of the column. */
.ht-awards{margin:36px auto 0;width:min(643px,90%)}
.ht-awards-img{width:100%;aspect-ratio:643/93}

@media (max-width:1023px){
  /* WEB-43 §3e: TWO COLUMNS below 1024, which is what the bitmap's own
     phone version did -- 1080x2700, two columns of four. Eight cells in a
     row would be 45px wide on a 390 phone, and a row that scrolls sideways
     hides half the products behind a gesture nobody is told about. Two
     columns keep all eight reachable by scrolling the page, which is the
     one gesture every reader already makes. */
  .ht-strip{grid-template-columns:repeat(2,minmax(0,1fr));gap:26px 18px;
    max-width:640px;margin-left:auto;margin-right:auto;padding:0 20px}
  .ht-cell{grid-row:span 3}
  /* a shorter picture box on two columns: 202px was sized for a row of
     eight, and on a phone it left a hand's width of black above the
     shorter products */
  .ht-pic-box{height:150px}
  .ht-name{font-size:19px}
  .ht-h{font-size:30px;padding-top:40px}
  .ht-wrap{padding-top:32px}
  .ht-lede{font-size:17px}
}
@media (max-width:599px){
  .ht-lede{font-size:16px}
  .ht-awards{margin-top:28px}
}

/* ---------- WEB-29 §7d: tap targets on phones -------------------------
   WEB-28's check measured four controls shorter than the 44 px a finger
   needs: the header logo at 35.8, the skip link at 41, the download links
   at 16.8 and 33.6, and the FAQ product links at 17.1.

   Below 600 px only -- the phone breakpoint this stylesheet already uses --
   each gets 44 px of height. Three of the four are inline anchors, where
   min-height does nothing at all, so each also becomes a flex box with its
   text centred: that way the box grows around the words instead of pushing
   them down, and nothing moves on the page. The header logo is centred in a
   56 px bar by `align-items:center`, so growing its link from 35.8 to 44
   keeps the same centre line and the mark itself does not shift -- proved
   by screenshot, not assumed.

   The selectors match the specificity of the rules they extend
   (.fq-list .fq-link sets display:inline-block, which a bare .fq-link
   could not override). Nothing here applies above 600 px. */
@media (max-width:600px){
  .hdr-in > .hdr-logo{min-height:44px;display:flex;align-items:center}
  .skip{min-height:44px;display:flex;align-items:center}
  .dl-link,
  .dl-shelf .dl-link{min-height:44px;display:flex;align-items:center}
  .fq-link,
  .fq-sec h3 .fq-link,
  .fq-list .fq-link{min-height:44px;display:inline-flex;align-items:center}
}

/* ---------- WEB-32 §9: the imperial half of a figure --------------------
   "Include both metric and imperial, with the latter being italicized"
   (the Architect, 17:18). One class, applied by ov/imperial.py to the
   finished HTML so it cannot drift from template to template. Metric
   still comes first everywhere and no figure changes -- only how the
   imperial half is set. */
.imp{font-style:italic}


