@media (min-width:1280px){
      .duo-grid{
        /* The network column LEADS. 1.06fr against 1fr is the operator's
           "slightly larger and wider" as a number rather than a feeling: at
           1440 it moves the split from 600.8/600.8 to 618.3/583.3, so the
           diagram gains 17.5px and the assistant gives up the same. 1.06 is
           the ceiling, not a first guess -- the pair has to stay READABLE as
           two columns of one section rather than as a main and a sidebar, and
           the assistant's own frame is the constraint that sets it: at the
           1280 hinge 1.06 leaves the chat 551.7px, and the explorer's reply
           tables start wrapping their second column under ~540px.
           The floor below still applies to the LEFT track, which is now the
           wider of the two -- so the sideways collapse gets MORE headroom over
           the diagram's 560px stacking threshold than it had at parity
           (584.7px at the hinge, up from 568.2px), not less. */
        grid-template-columns:minmax(0,1.06fr) minmax(0,1fr);
        /* ONE row. The stacked base declares `1fr auto` for its collapsing row
           track; left in place beside a second column it would put a phantom
           second track under the pair and charge the section a row-gap for it. */
        grid-template-rows:auto;
        /* Bottoms level: both columns take the row's height, and the flex chain
           below passes that height down to the assistant frame. */
        align-items:stretch;
        /* Engaging collapses a COLUMN here, not a row -- so the animated
           property changes with the axis. Both endpoints are <flex> values
           (1fr -> 0fr) because `auto -> 0fr` is not interpolable and snaps in a
           single frame, and the gap is animated alongside the track or the
           assistant stops 26px short of the edge it just won. */
        transition:grid-template-columns 420ms var(--e-out),
                   column-gap 420ms var(--e-out);
      }
      /* THE FLOOR THAT MAKES A SIDEWAYS COLLAPSE SAFE.
         The diagram measures ITSELF and posts its height to this page. Squeeze
         its frame toward zero width and it re-measures against nothing: at the
         560px threshold its quadrants stack one-per-row and it reports 1251px
         for 546px of content (measured on staging). The old two-column build
         hit that on every engage and patched it downstream, in the message
         handler.
         Pinning the resting width of the network column's own children fixes it
         upstream instead: the track animates 601px -> 0 and clips them
         (`.duo-col--net` is `overflow:hidden`), while the frame inside never
         goes under 561px and so never crosses its own breakpoint. Sampled frame
         by frame through a collapse, the iframe held 561px wide and 700px tall
         throughout. It also stops the standfirst re-wrapping on its way out,
         which used to change the height of the row both columns share.
         `minmax(0,1fr)` on the tracks above is what keeps this floor from
         inflating the grid: a `1fr` track would otherwise take its minimum from
         its content's min-width. */
      .duo-col--net > .duo-head,
      .duo-col--net > iframe{ min-width:561px; }

      /* THE HEADINGS, NOT JUST THE BOXES.
         `align-items:stretch` already starts both columns on the same line --
         measured, `.duo-head` and `.stg-explorer-card` share a top to within
         0.0px. What it cannot do is start their TEXT on the same line, because
         only one of them is a padded panel: the assistant's first ink sits
         below the card's 2px transparent border and its own block padding,
         while the network's h2 begins immediately. Measured on master that was
         61.6 against 83.6 at 1440 -- 22px of visible misalignment between two
         boxes a harness happily called level, and the operator's "including
         their headings".
         The offset is therefore DERIVED from the card rather than eyeballed:
         `.stg-card` ships `border:2px solid transparent` and this file gives it
         `padding:clamp(14px,1.5vw,20px)` in the block direction, so those two
         terms ARE the distance. Restating them keeps the two sides bound
         together -- retune the card's padding and the heading follows it, which
         a hard-coded 22px would not do. Checked as a number by
         network_layout_check.py (`headingRowDelta`), not by eye. */
      /* The desktop skeleton. Two columns is the one composition where the
         diagram is taller than the 700px the base rule assumes -- the enlarged
         quadrant cards settle it at ~745px at the hinge and ~760px at 1600 --
         and it is also the composition where being wrong costs the most, since
         the assistant now takes ITS height from this column. Overriding here
         rather than on the base rule leaves every stacked width (a 1024 frame
         still settles at 658px) with the skeleton that actually fits it. */
      .duo-col--net > iframe{ height:750px; }

      .duo-col--net > .duo-head{
        padding-top:calc(2px + clamp(14px,1.5vw,20px));
        /* And the space it costs is taken back on the other side. 18px between
           the standfirst and the diagram was tuned for the stacked composition
           where the block below is the full page wide; beside the assistant it
           is one of the "unnecessary empty space" gaps the operator named.
           13px still reads as a deliberate break rather than a collision, and
           the pair nets out 5px taller, not 22px. */
        margin-bottom:clamp(10px,1vw,13px);
      }

      /* The assistant is the shorter column, so it is the one that stretches.
         `align-items:stretch` only sizes the COLUMN; without this chain the
         card keeps its content height and the difference reads as dead white
         space inside a full-height box -- the exact artefact the shared subgrid
         row used to exist to remove. The subgrid does NOT come back: it needed
         a header in BOTH columns to have something to align, and the right-hand
         header was deleted on operator request. A flex chain needs no second
         header and leaves no empty one behind.
         `flex:1 0 auto` on the frame keeps the embed's own clamp as the basis
         and lets it GROW into the extra height -- it may never shrink below the
         height it asks for. */
      .duo-col--eco{ display:flex; }
      .duo-col--eco > .stg-network{ display:flex; flex-direction:column;
                                    flex:1 1 auto; min-width:0; }
      .duo-col--eco .stg-explorer-card{ display:flex; flex-direction:column;
                                        flex:1 1 auto; }
      .duo-col--eco .stg-frame{ display:flex; flex-direction:column; flex:1 1 auto; }
      /* WHY THIS IS NOT `flex:1 0 auto` ANY MORE.
         `height:clamp(560px,64vh,700px)` on the base rule is a VIEWPORT-driven
         number, and as a flex basis it decides how tall the assistant column
         WANTS to be. The diagram's height is CONTENT-driven and effectively
         constant across the desktop band (~751px at 1440). Two columns sized by
         two unrelated quantities can only agree by coincidence, and they do:
         they agree at ~900px of viewport height and nowhere else. Measured at
         1440: the bottoms are 9.4px apart on a 900-tall window, and 133px apart
         on a 1400-tall one, because 64vh saturates at the 700px cap while the
         diagram has not moved. That second number is the state the operator
         screenshotted, and the reason the existing harness never caught it is
         that it only ever samples 860/900-tall viewports.
         Dropping the viewport out of the basis fixes it at the source. With
         `height:auto` the basis is the iframe's intrinsic size, the floor below
         is what keeps the conversation usable if the diagram ever shrinks, and
         `flex-grow:1` takes the frame to whatever the row actually is. The
         NETWORK column therefore sets the row at every viewport height and the
         assistant lands exactly on its bottom edge -- which is the whole of
         "vertically aligned and visually balanced on desktop".
         A BASIS, NOT A FLOOR, and that distinction is the one thing this
         rule may not get wrong. `test_the_assistant_is_no_longer_floored_
         against_a_diagram_it_shares_a_row_with` forbids a `min-height` on the
         idle frame outright, and it is right to: a min-height the diagram
         cannot reach stops behaving like a floor and becomes the row height
         instead, which is exactly how `clamp(360px,42vh,440px)` once held the
         row open past the end of a shortened diagram and put 125px of dead
         white space under it at 1440. A flex BASIS cannot do that -- it is
         where the frame starts before growing, not a size it insists on.
         420px, flat, is chosen for headroom rather than for looks, because
         nothing here ever renders at 420: the column's max-content is
         420 + ~201px of card chrome = ~621px against a network column of
         ~830px at the hinge, so the assistant has 200px of margin before it
         could become the taller of the two and reopen that artefact from the
         other direction. What the reader actually sees is the row: ~633px at
         1440, comfortably inside the 560-700px band the stacked rule uses.
         Engaged (`.duo.eco-active .stg-network .stg-embed`, (0,3,0)) and
         popped-out (`body.npe-popout ... .stg-embed`, (0,4,1)) both outrank
         this rule, so neither state changes. */
      .duo-col--eco .stg-embed{
        flex:1 1 auto; height:420px !important; max-height:none;
      }

      /* Engaged: the left track closes and the gap closes with it, so the
         assistant ends up owning the whole content width rather than stopping
         one gap short of it. The row track is restated because the stacked
         `grid-template-rows:0fr auto` sets a declaration nothing here would
         otherwise replace, and this rule can only replace it by SOURCE ORDER:
         both selectors are `.duo.eco-active .duo-grid`, i.e. (0,3,0), and a
         media query contributes no specificity of its own. Move this block
         above 8B and the desktop grid silently collapses on the row axis
         instead of the column one.
         Deliberately NOT here: `max-height:0` on the block or `height:0` on its
         children. Either one lands the network at nothing on frame one and
         there is no animation left to watch -- the track closing IS the
         animation, and the floor above is what keeps the clipped content
         honest while it happens.
         The price of leaving them out is worth writing down: the collapsed
         column keeps its content height behind `overflow:hidden`, so it still
         sizes the row both columns share. Where the engaged assistant is the
         SHORTER of the two -- a short viewport, where `clamp(620px,82vh,860px)`
         floors at 620px while the diagram is still ~760px -- the difference
         reads as dead space under the card. `align-self:stretch` on the engaged
         column would close it -- by growing the chat frame past the "engaged
         frame is more than 0.92 of the viewport" ceiling npe_host_check.py
         calls "something is inflating the row", which is the other half of the
         original report. The gap is the deliberate side of that trade, not an
         oversight. */
      .duo.eco-active .duo-grid{
        grid-template-columns:minmax(0,0fr) minmax(0,1fr);
        grid-template-rows:auto; column-gap:0;
      }
    }

    @media (prefers-reduced-motion: reduce){
      .duo-grid, .duo-col--net,
      .duo.eco-active .duo-grid, .duo.eco-active .duo-col--net{ transition:none; }
      /* grid-template-rows is what animates now; naming it explicitly keeps
         this escape hatch honest if the property changes again. */
      .duo.eco-active .eco-restore{ animation:none; }
      /* The page-wide reduced-motion rule only shortens transition-DURATION; it
         never cancels a hover transform, so the lift still ran here. */
      .stg-network .stg-card, .stg-network .stg-card:hover{
        transition:none !important; transform:none !important;
      }
    }

    /* Pop-out. The iframe is NEVER moved or cloned: only the wrapper it already
       lives in is promoted to a fixed layer, so the conversation, the open SSE
       stream and the microphone permission all survive opening and closing. */
    body.npe-popout{ overflow:hidden; }
    .npe-scrim{
      display:none; position:fixed; inset:0; z-index:9998;
      background:rgba(9,35,61,.55); backdrop-filter:blur(2px);
    }
    body.npe-popout .npe-scrim{ display:block; }
    body.npe-popout .duo-col--eco .stg-frame{
      position:fixed; z-index:9999; inset:clamp(12px,3vh,40px) clamp(12px,3vw,56px);
      display:flex; flex-direction:column; border-radius:14px; overflow:hidden;
      box-shadow:0 24px 70px rgba(9,35,61,.35); background:#fff;
    }
    body.npe-popout .duo-col--eco .stg-frame .stg-embed{
      flex:1; height:auto !important; min-height:0 !important; max-height:none !important;
    }
    body.npe-popout .duo-col--eco .stg-frame .stg-fallback{ display:none; }

    /* ---------- 9. SCENE 4 - THE FIELD (#expertise) ---------- */
    .field{ background:transparent; padding-block:var(--scene-py);
            scroll-margin-top:calc(var(--nav-h) + 8px); }
    .film{
      position:relative; width:100%; aspect-ratio:21/9; overflow:hidden;
      background:var(--paper-edge); border-radius:var(--r-chip);
      margin-bottom:clamp(40px,5vw,86px);
    }
    .film video, .film img{
      position:absolute; inset:0; width:100%; height:100%;
      object-fit:cover; object-position:50% 58%;
    }
    .film video{ z-index:1; opacity:0; transition:opacity 900ms var(--e-out); }
    .film video.playing{ opacity:1; }
    @media (prefers-reduced-motion: reduce){ .film video{ transition:none; } }
    .film-note{
      position:absolute; left:0; bottom:0; z-index:3;
      display:flex; align-items:center; gap:14px;
      background:var(--navy); color:var(--on-navy);
      padding:12px clamp(16px,2vw,26px);
      font-family:var(--f-display); font-size:var(--fs-micro); font-weight:500;
      letter-spacing:.17em; text-transform:uppercase;
    }
    .film-note b{ color:var(--sky-soft); font-weight:500; }

    .field-head{
      display:grid; grid-template-columns:minmax(0,1fr) minmax(0,1fr);
      gap:clamp(20px,3vw,64px); align-items:end;
      margin-bottom:clamp(36px,4.4vw,72px);
      background:var(--paper);
    }
    .field-head h2{ font-size:var(--fs-h2); letter-spacing:-.03em; }
    .field-head p{ color:var(--ink-2); font-size:var(--fs-small); padding-bottom:6px; }

    .values{ border-top:1px solid var(--line-2); }
    .value{
      display:grid; grid-template-columns:64px minmax(0,1.05fr) minmax(0,1.35fr);
      gap:clamp(16px,2.4vw,44px); align-items:start;
      padding:clamp(24px,2.9vw,42px) 0;
      border-bottom:1px solid var(--line);
      transition:background var(--d2) var(--e-out);
      background-color:var(--paper);
    }
    .value .vn{
      font-family:var(--f-display); font-size:var(--fs-meta); font-weight:500;
      letter-spacing:.14em; color:var(--ink-3); padding-top:5px;
      transition:color var(--d2) var(--e-out);
    }
    .value h3{ font-size:var(--fs-h3); letter-spacing:-.02em;
               display:flex; align-items:center; gap:14px; }
    .value p{ color:var(--ink-2); max-width:46ch; }
    @media (pointer:fine){
      .value:hover .vn{ color:var(--brand); }
    }

    /* ---------- 10. HELP BAND ---------- */
    .help{ background:transparent; padding-block:clamp(26px,2.6vw,44px); }
    .help-inner{
      display:grid; grid-template-columns:minmax(0,1fr) auto;
      gap:clamp(22px,3vw,56px); align-items:center;
      background:var(--paper-white);
    }
    .help h2{
      font-family:var(--f-display); font-size:var(--fs-label); font-weight:500;
      letter-spacing:.19em; text-transform:uppercase; color:var(--ink-2);
      margin-bottom:12px;
    }
    .help p{ font-size:var(--fs-lead); color:var(--ink); max-width:42ch;
             font-family:var(--f-display); font-weight:400; letter-spacing:-.012em; }
    .mail{
      display:inline-flex; align-items:center; gap:12px; min-height:52px;
      font-family:var(--f-display); font-size:var(--fs-h3);
      font-weight:500; letter-spacing:-.02em; color:var(--brand);
      border-bottom:1px solid rgba(0,76,151,.3); padding-bottom:2px;
      transition:border-color var(--d2) var(--e-out);
    }
    @media (pointer:fine){ .mail:hover{ border-color:var(--brand); } }

    /* ---------- 13. FOOTER - the single earned dark passage ---------- */
    .site-footer{ background:var(--navy); color:var(--on-navy-2);
                  padding-block:clamp(56px,6.4vw,104px) clamp(36px,4vw,64px); }
    .footer-grid{
      display:grid; grid-template-columns:minmax(0,1.6fr) minmax(0,1fr) minmax(0,.7fr) minmax(0,.7fr);
      gap:clamp(28px,3.4vw,64px);
    }
    .footer-logo img{ height:44px; width:auto; margin-bottom:22px; filter:brightness(0) invert(1); }
    .footer-tagline{ color:var(--on-navy-2); font-size:var(--fs-small); max-width:42ch; }
    .site-footer h4{
      font-family:var(--f-display); font-size:var(--fs-label); font-weight:500;
      letter-spacing:.18em; text-transform:uppercase; color:var(--sky-soft);
      margin-bottom:18px;
    }
    .footer-social-icons{ display:flex; gap:10px; }
    .footer-social-icons a{
      width:44px; height:44px; display:inline-flex; align-items:center; justify-content:center;
      border:1px solid rgba(255,255,255,.22); border-radius:var(--r-btn);
      color:var(--on-navy);
      transition:background var(--d2) var(--e-out), border-color var(--d2) var(--e-out);
    }
    .footer-social-icons .ico{ width:16px; height:16px; display:block; }
    @media (pointer:fine){
      .footer-social-icons a:hover{ background:rgba(255,255,255,.12);
                                    border-color:var(--sky-soft); }
    }
    .footer-contact-info a,
    .footer-links a, .footer-bottom-links a{
      display:inline-flex; align-items:center; min-height:44px;
      color:var(--on-navy-2); font-size:var(--fs-small);
      transition:color var(--d2) var(--e-out);
    }
    .footer-contact-info p{ margin:0; }
    .footer-links, .footer-bottom-links{ display:flex; flex-direction:column; }
    @media (pointer:fine){
      .footer-contact-info a:hover,
      .footer-links a:hover, .footer-bottom-links a:hover{ color:#fff; }
    }
    .footer-rule{ height:1px; background:rgba(255,255,255,.14);
                  margin:clamp(38px,4.4vw,72px) 0 22px; }
    .footer-base{
      display:flex; flex-wrap:wrap; gap:12px 26px; justify-content:space-between;
      font-family:var(--f-display); font-size:var(--fs-micro); letter-spacing:.14em;
      text-transform:uppercase; color:rgba(255,255,255,.62);
    }

    /* ---------- 14. RESPONSIVE ---------- */
    @media (max-width:1200px){
      .stage-body{ grid-template-columns:138px minmax(0,1fr) minmax(260px,330px); }
    }

    /* --- tablet & below: nav becomes a drawer --- */
    @media (max-width:1024px){
      :root{ --nav-h:62px; }
      .nav-toggle{ display:inline-flex; }
      .header-nav{ display:none; }
      .header-nav.open{
        display:flex; flex-direction:column; align-items:stretch; gap:0;
        position:absolute; left:0; right:0; top:var(--nav-h);
        background:var(--paper-white); border-bottom:1px solid var(--line);
        box-shadow:0 18px 40px -24px rgba(14,42,66,.35);
        padding:6px var(--gutter) 14px;
      }
      .header-nav.open a{ min-height:52px; border-bottom:1px solid var(--line); }
      .header-nav.open a::after{ display:none; }
      /* Six rows now, not five. On a short or landscape phone the drawer is
         taller than the viewport, and opening it locks body scroll -- so the
         last items (Our App, Contact) were unreachable. Bounded height plus
         its own scroller; invisible at ordinary portrait heights, where the
         drawer is far shorter than this ceiling. */
      .header-nav.open{ max-height:calc(100vh - var(--nav-h) - 44px);
                        overflow-y:auto; overscroll-behavior:contain;
                        -webkit-overflow-scrolling:touch; }

      .hero-foot{ grid-template-columns:1fr; gap:clamp(26px,4vw,40px); }
      /* stacked: the CTA shares the copy's left edge again */
      .hero-cta{ justify-content:flex-start; align-self:start; }
      /* full width once stacked: centred content-width buttons leave the
         long second label one word per line on a narrow phone */
      .hero-cta, .hero-cta-stack{ width:100%; }
      .hero-cta-stack{ align-items:stretch; }
      .hero-cta-stack .btn{ justify-content:center; }
      .caps{ grid-template-columns:repeat(3,minmax(0,1fr)); gap:18px; }

      .field-head{ grid-template-columns:1fr; align-items:start; gap:14px; }
      .value{ grid-template-columns:44px minmax(0,1fr); gap:14px 18px; }
      .value p{ grid-column:2; max-width:52ch; }
      .help-inner{ grid-template-columns:1fr; gap:22px; align-items:start; }
      .footer-grid{ grid-template-columns:repeat(2,minmax(0,1fr)); }
    }

    @media (max-width:760px){
      .caps{ grid-template-columns:1fr; gap:26px; }
      .film{ aspect-ratio:16/10; }
      .footer-grid{ grid-template-columns:1fr; gap:34px; }
    }

    @media (max-width:480px){
      :root{ --nav-h:58px; }
      body{ line-height:1.6; }
      .admin-bar{ min-height:44px; font-size:var(--fs-meta); }
      .admin-bar span{ min-height:44px; }
      .admin-bar a{ min-height:44px; }
      .hero{ --band-h:clamp(132px,20vh,190px); }
      .hero-title{ line-height:1.0; letter-spacing:-.03em; }
      .hero-band-note{ font-size:var(--fs-micro); letter-spacing:.14em; }
      .btn{ min-height:48px; width:100%; justify-content:space-between; }
      .hero-cta .btn{ max-width:340px; }
      .value{ grid-template-columns:1fr; gap:10px; }
      .value .vn{ padding-top:0; }
      .value p{ grid-column:1; }
      .zone-btn{ min-height:56px; }
      .footer-social-icons a{ width:46px; height:46px; }
      .mail{ font-size:var(--fs-lead); }
    }


    /* ---------- 14b. ULTRAWIDE - keep editorial measure, grow the stage ---------- */
    @media (min-width:1600px){
      :root{
        /* 1400px is the ceiling: past it the cards and copy read as
           disconnected islands on a 2560px monitor (operator, 2026-09-03). */
        --maxw: 1400px;
        --gutter: clamp(32px, 4.2vw, 104px);
      }
      .hero-lede p{ max-width:50ch; }
      .value p{ max-width:40ch; }
      .help p{ max-width:40ch; }
      .footer-tagline{ max-width:40ch; }
    }

    /* ---------- 15. REDUCED MOTION - the page must be complete with zero motion ---------- */
    @media (prefers-reduced-motion: reduce){
      html{ scroll-behavior:auto; }
      .js .rv{ opacity:1 !important; transform:none !important;
               transition:none !important; will-change:auto !important; filter:none !important; }
      *,*::before,*::after{
        animation-duration:.001ms !important;
        animation-iteration-count:1 !important;
        transition-duration:.001ms !important;
        scroll-behavior:auto !important;
      }
      .btn:hover .arw,
    }
    
    /* PAGE WEBBING - one continuous lattice backdrop behind the whole page,
       the same motif and settings the Projects page already uses. It is
       `fixed` so the webbing does not restart or stop at section seams as the
       reader scrolls; `pointer-events:none` so it never intercepts a click. */
    .page-field{ position:fixed; inset:0; z-index:0; opacity:.62; pointer-events:none; }
    /* .62 not .5 -- operator asked for the webbing a little more present
       2026-09-03. Still a backdrop: the lines land ~0.031 alpha over the
       paper, and it stays behind every card because .site-header/main/
       .site-footer sit in their own z-index:1 layer. */
    /* Its own compositor layer. A full-viewport position:fixed canvas is
       repainted on every scroll frame otherwise, which is what made the page
       judder: dropped frames went from ~0% to ~5% while scrolling Projects. */
    .page-field{ will-change:transform; transform:translateZ(0);
                 backface-visibility:hidden; contain:layout paint; }
    .page-field canvas{ display:block; width:100%; height:100%; }
    /* A fixed z-index:0 backdrop is a POSITIONED element, so it paints after
       every ordinary in-flow background -- the webbing was landing on top of
       cards, images and even the header logo. Lifting the three page regions
       into their own layer puts the field strictly behind the content, where
       the containers' own backgrounds mask it. */
    .site-header, main, .site-footer{ position:relative; z-index:1; }
    /* ...but they must not all land on the SAME level. `main` comes later in
       the DOM, so at an equal z-index it paints OVER the header -- and the
       mobile drawer is absolutely positioned inside the header. Measured
       2026-09-04 at 390px: elementFromPoint at the centre of every drawer row
       returned page content (SECTION.app-scene, H1.app-title, P.app-lead), so
       not one nav link was clickable on a phone. The header's own rule already
       asked for 50; restore just the z-index -- deliberately NOT `position`,
       which would re-stick five shipped pages. 50 keeps it under the
       z-index:60 admin bar and over the z-index:0 webbing field. */
    .site-header{ z-index:50; }
