/* ═══════════════════════════════════════════════════════════════════════
   register-v23-chrome.css - the masthead and colophon, on v23's tokens.

   ⛔ WHY THIS EXISTS. register-v23-interior.css covered the <main> content
   classes and nothing else, and exhibit.css was removed at the same time.
   The 34 interior pages carry the EXHIBIT chrome markup, so .mast-brand,
   .mast-nav, .mast-util, .ubtn, .colophon and every .col-* class lost
   their styling in one step.

   Measured consequence, harness/diagnose-regressions.py: every page
   reported `controls under 44px ['Marcella h=26', ' h=19', ' h=34']` at
   both phone and desktop. Those three are the brand link and the two icon
   buttons, collapsed to their unstyled intrinsic height.

   v23 styles its OWN masthead (.brand, .mast-in) and has no colophon at
   all. This maps the exhibit chrome onto the same tokens so both sets of
   markup wear one design.

   Every control below carries an explicit 44px minimum, because that is
   the rule that broke and WCAG 2.5.8 is not negotiable on a nav.
   ═══════════════════════════════════════════════════════════════════════ */

/* ── skip link ───────────────────────────────────────────────────────── */
.skip-link{position:absolute;left:-9999px;top:0;z-index:99;
 background:var(--accent);color:var(--deep);padding:12px 18px;
 font-family:var(--sans);font-weight:700;min-height:44px;
 display:inline-flex;align-items:center}
.skip-link:focus{left:0}

/* ── masthead ────────────────────────────────────────────────────────── */
.mast{background:var(--deep);color:var(--on-deep);
 border-bottom:3px solid var(--accent)}
.mast-in{max-width:var(--max);margin:0 auto;
 padding:14px var(--gut);display:flex;flex-wrap:wrap;align-items:center;
 gap:12px 26px;width:100%}
.mast-brand,.mast .brand{display:flex;align-items:center;gap:10px;
 min-height:44px;text-decoration:none;color:inherit;margin-right:auto;
 border:none}
.mast-name,.mast .brand b{font-family:var(--serif);font-weight:600;
 font-size:1.3rem;letter-spacing:-.02em;color:var(--on-deep)}
.mast-sub,.tagline{font-family:var(--sans);font-size:12px;font-weight:500;
 letter-spacing:.01em;color:var(--on-deep-muted);margin:0}
/* The three dots are the logo lockup, and they are DATA coloured. */
.mast-triage,.dots{display:inline-flex;gap:4px;align-items:center}
.mast-triage i,.dots i{width:7px;height:7px;border-radius:50%;
 display:block}
.t-g,.d-g{background:var(--green)}
.t-y,.d-y{background:var(--yellow)}
.t-r,.d-r{background:var(--red)}

.mast-nav,.mast nav{display:flex;flex-wrap:wrap;gap:0 20px}
.mast-nav a,.mast nav a{font-family:var(--sans);font-size:14px;
 font-weight:600;color:var(--on-deep-muted);text-decoration:none;
 min-height:44px;display:inline-flex;align-items:center;
 border-bottom:2px solid transparent}
.mast-nav a:hover,.mast nav a:hover,.mast nav a[aria-current]{
 color:var(--on-deep);border-bottom-color:var(--accent)}

.mast-util{display:flex;align-items:center;gap:6px}
/* ⛔ 44x44. These two icon buttons are what measured h=19 and h=34. */
.ubtn{min-width:44px;min-height:44px;display:inline-flex;
 align-items:center;justify-content:center;background:transparent;
 border:1px solid rgba(255,255,255,.18);border-radius:var(--r-control);
 color:var(--on-deep-muted);cursor:pointer;padding:0}
.ubtn:hover{color:var(--on-deep);border-color:var(--accent)}
.ubtn svg{width:19px;height:19px;fill:none;stroke:currentColor;
 stroke-width:1.8;stroke-linecap:round;stroke-linejoin:round}
.i-sun{display:none}
:root[data-theme="dark"] .i-sun{display:block}
:root[data-theme="dark"] .i-moon{display:none}

/* the search field, where the page carries one */
.seek{display:flex;align-items:center;gap:8px}
.seek label{position:absolute;left:-9999px}
.seek input{min-height:44px;padding:0 14px;border-radius:var(--r-control);
 border:1px solid rgba(255,255,255,.2);background:rgba(255,255,255,.06);
 color:var(--on-deep);font-family:var(--sans);font-size:15px}
.seek input::placeholder{color:var(--on-deep-dim)}
.seek button{min-height:44px;padding:0 18px;border-radius:var(--r-pill);
 border:1px solid var(--accent);background:var(--accent);
 color:var(--deep);font-family:var(--sans);font-weight:700;cursor:pointer}
@media(max-width:620px){.seek{display:none}}

/* ── colophon ────────────────────────────────────────────────────────── */
.colophon,footer.colo{background:var(--deep);color:var(--on-deep);
 padding:clamp(40px,6vw,72px) 0 30px;margin-top:0}
.colophon-in,footer.colo .wrap{max-width:var(--max);margin:0 auto;
 padding-left:var(--gut);padding-right:var(--gut);display:grid;
 grid-template-columns:minmax(0,1fr);gap:32px;width:100%}
@media(min-width:900px){
  .colophon-in{grid-template-columns:minmax(0,4fr) minmax(0,8fr)}
}
.colophon .mast-name{color:var(--on-deep)}
.colophon .mast-sub{opacity:.78;margin-top:6px}
.col-h{font-family:var(--sans);font-size:13px;font-weight:700;
 letter-spacing:.06em;text-transform:uppercase;color:var(--on-deep-dim);
 margin:0 0 10px}
.colophon a,footer.colo a{font-family:var(--sans);font-size:15px;
 color:var(--on-deep-muted);text-decoration:none;min-height:44px;
 display:inline-flex;align-items:center;border-bottom:1px solid transparent}
.colophon a:hover,footer.colo a:hover{color:var(--on-deep);
 border-bottom-color:var(--accent)}
/* ⛔ TWO COLUMNS ON A PHONE, NOT ONE. JT, 2026-10-31: "Fix the footer on
   mobile, its being cut off."
   MEASURED at 390px before: footer 1,324px tall on an 844px viewport, so it
   ran 1.6 screens and read as clipped. `.col-cols` alone was 967px of that,
   as ONE 350px column of link groups. Nothing was clipped by CSS: it was
   simply longer than the screen, which is the same thing to a reader.
   Two columns halves it, and the link groups are short lists that read fine
   side by side. The 3-column desktop rule is untouched. */
.col-cols{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));
  gap:18px 20px}
@media(max-width:359px){
  /* Below 360 two columns of link text start hyphenating; one is kinder. */
  .col-cols{grid-template-columns:minmax(0,1fr)}
}
@media(min-width:620px){
  .col-cols{grid-template-columns:repeat(3,minmax(0,1fr))}
}
.col-cols>div{display:flex;flex-direction:column}

/* ⛔ ICON ROW, BRAND-COLOURED. Five stacked 44px text links were 220px of
   that footer; as one row of icons they are 48px.
   The 44px target is kept: the <svg> is 22px and the padding makes up the
   rest. gyi-content-persona counts EVERY interactive control, not just the
   primary CTA, and an icon link is the easiest place to end up with a 22px
   target by accident. */
.col-social{display:flex;flex-wrap:wrap;gap:4px 6px;margin-top:6px}
/* ⛔ THE FOOTER HAS TO PAINT ABOVE THE DECORATIVE BACKDROP.
   MEASURED 2026-11-02 on the live site from JT's phone and reproduced at
   375x667: the social icons were sitting on a WHITE ground, not the footer's
   rgb(4,20,36). The paint stack under an icon's centre was

       a.soc  ->  img (position:relative, z-index:1)  ->  footer background

   That image is /assets/backdrop-2-billing.webp inside div.stage-bg, which
   is position:sticky and one viewport tall. It spans document y 8118..8786
   while the footer starts at 8475, so it covers the first 311px OF THE
   FOOTER and the social row sits 78px inside that overlap.

   Measured glyph contrast on that white ground:
       X          1.16:1     invisible, and that is literally what the
                             screenshot shows: a white X on white
       Instagram  2.88:1     under the 3:1 bar for a UI component
       LinkedIn   3.02:1     Facebook 3.10:1   YouTube 3.24:1
   On the footer's own ground the worst of the five is 5.68:1.

   The backdrop is intentional, the overlap is not: the section above
   deliberately layers a dark panel over that console. So the footer is
   lifted above it rather than the backdrop being changed. */
footer.colophon{position:relative;z-index:2}

/* ⛔ AND THE ICONS CARRY THEIR OWN GROUND, so they survive a regression.
   An opaque chip means the glyph contrast no longer depends on what happens
   to be painted behind the row. Worst of the five on this chip is 5.00:1
   against the 3:1 that WCAG 1.4.11 asks of a non-text UI component, so the
   design target and the gate threshold are deliberately different numbers.
   A gate set to the value the component was built to hit is satisfied by
   construction and measures nothing.
   It also makes the row scannable, which is the other half of the report:
   people scroll to the bottom looking for social links. */
.col-social a.soc{display:inline-flex;align-items:center;
  justify-content:center;width:44px;height:44px;border-radius:10px;
  color:var(--on-deep,#e9eef6);opacity:.92;
  background:#0b2136;border:1px solid rgba(233,238,246,.28);
  transition:opacity .12s ease,background-color .12s ease}
.col-social a.soc:hover{opacity:1;background:#14314e}
.col-social a.soc:focus-visible{outline:2px solid var(--accent,#f59e0b);
  outline-offset:2px}
.col-social a.soc svg{display:block}
/* The accessible name. An icon-only link with no name is announced as
   "link". Clipped rather than display:none so it stays in the a11y tree
   and in the copy buffer. */
.col-social .vh{position:absolute;width:1px;height:1px;padding:0;margin:-1px;
  overflow:hidden;clip:rect(0 0 0 0);white-space:nowrap;border:0}
/* ⛔ flex-wrap, both here and in register-v23.css. A legal-link row that
   cannot wrap puts a hard ceiling on how many legal pages the site may
   have, and adding /dmca/ and /support/ to it pushed the document 218px
   sideways on a phone the last time this was missed. */
.col-foot{grid-column:1/-1;border-top:1px solid rgba(255,255,255,.2);
 margin-top:12px;padding-top:18px;display:flex;flex-wrap:wrap;
 gap:8px 20px;align-items:center}
.col-foot span{font-family:var(--sans);font-size:12px;
 color:var(--on-deep-dim)}
.col-foot nav{display:flex;flex-wrap:wrap;gap:0 20px}
.col-foot nav a{font-size:12px}

/* ── THE BRAND LOCKUP WAS RENDERING UNSTYLED ──────────────────────────────
   JT, 2026-10-26: "no marecella logos or branding."

   Not a missing asset. register-v23.css styles the lockup as .brand / .brand
   b / .dots / .dots i / .brand .tagline / .d-g .d-y .d-r, and the shipped
   masthead emits .mast-brand / .mast-name / .mast-triage / .t-g .t-y .t-r /
   .mast-sub. Different names for the same elements, so v23's ENTIRE brand
   rule set matched nothing and the wordmark fell back to default anchor
   text with three unstyled spans next to it.

   Aliasing rather than renaming the markup: the class names appear in 34
   built pages plus the three private diagram apps, and a rename is a
   find-and-replace across all of them that the gates cannot verify. An
   alias is additive and reversible, which is the right shape for a fix
   found at the end of a long day.

   The lockup v23 specifies: wordmark in the serif at 26px, the three
   treatment dots CENTRED BENEATH it, tagline under that, whole thing a
   vertical flex column. The dots are the product mark, so they carry the
   green/amber/red triage colours DESIGN-LOCK calls data, never decoration. */
.mast-brand{display:inline-flex;flex-direction:column;align-items:center;
 gap:3px;text-decoration:none;padding:8px 0;min-height:44px}
.mast-brand .mast-name{font-family:var(--serif);font-weight:600;
 font-size:26px;line-height:1;letter-spacing:-.012em;color:var(--on-deep)}
.mast-triage{display:inline-flex;gap:5px}
.mast-triage i{width:7px;height:7px;border-radius:50%;display:block}
.t-g{background:var(--green)}
.t-y{background:var(--yellow)}
.t-r{background:var(--red)}
.mast-sub{font-family:var(--serif);font-size:12px;line-height:1.2;
 color:var(--on-deep-muted);letter-spacing:.01em;white-space:nowrap;
 margin:0}
/* The colophon reuses the same lockup on the dark footer. */
.colo .mast-brand .mast-name,.colo-foot .mast-name{color:var(--on-deep)}

/* ── DESKTOP WAS STACKING WHAT v23 SETS SIDE BY SIDE ──────────────────────
   JT: "the desktop is sized incorrectly."

   .band-media .band-in was grid-template-columns:minmax(0,1fr) at EVERY
   width, so the copy sat above the figure on a 1320px canvas and each
   media band ran the full width of the page as two stacked blocks. That is
   the mobile layout shown on a desktop, which is why it read as sized
   wrong rather than merely plain.

   Two columns from 860px up, copy first, and the --flip variant puts the
   figure first. minmax(0,1fr) on both tracks, not 1fr: a bare 1fr floors
   at min-content and a wide figure or a long unbroken citation pushes the
   track past its share, which is the same class of overflow that cost
   three runs tonight. */
@media(min-width:860px){
  .band-media .band-in{grid-template-columns:minmax(0,1fr) minmax(0,1.08fr);
   align-items:center;gap:clamp(28px,3.4vw,56px)}
  .band-media--flip .band-in>*:first-child{order:2}
  .band-media--flip .band-in>.band-media-fig{order:1}
}

/* ═══════════════════════════════════════════════════════════════════════
   MOTION, ported from what deloitte.com actually does
   harness/probe-deloitte-motion.py, 2026-10-26, three pages JT named.

   THE HEADLINE FINDING: they load NO motion library. No GSAP, no Lottie,
   no Swiper, no ScrollMagic, on any of the three. Every effect is CSS
   transition or a short @keyframes, triggered by a class the page adds on
   scroll. So all of it is reproducible here with zero third-party request,
   which matters because the CSP in .htaccess refuses outside script hosts.

   What they actually run, measured off the live CSSOM:

     [data-aos^="fade"], [data-aos^="zoom"]   transition opacity, transform
     .img-lazy-show                           transition opacity 1s
     .animate-underline::before               transition width, opacity .3s
     @keyframes fade-in                       drives opacity
     @keyframes slide-in-right                drives transform, opacity
     durations                                .3s small, .5s slide, 1s image
     prefers-reduced-motion blocks            2 on every page

   And the three pages differ by DENSITY, not by mechanism:

                            pre-hidden   video   transformed   height
     static-reference            18        0           4       3,464px
     about, "image motion"       21        1          14       9,007px
     private-equity, "graphic"   40        1           7       5,364px

   So this file carries one system and three densities, assigned per page
   archetype by harness/apply-motion.py.

   ⛔ CONTENT IS VISIBLE UNLESS JAVASCRIPT IS PROVEN TO BE RUNNING.
   Deloitte puts opacity:0 in the stylesheet, which means a JS failure
   leaves the copy permanently invisible. We do not copy that. The reveal
   styles are scoped under html.js-motion, and register.js adds that class
   as its FIRST action. No JS, no class, no hiding: every word renders.
   A fail-open path must never hide the content.
   ═══════════════════════════════════════════════════════════════════════ */

@keyframes mo-fade{from{opacity:0}to{opacity:1}}
@keyframes mo-rise{from{opacity:0;transform:translateY(18px)}
                   to{opacity:1;transform:none}}
@keyframes mo-slide-r{from{opacity:0;transform:translateX(26px)}
                      to{opacity:1;transform:none}}
@keyframes mo-slide-l{from{opacity:0;transform:translateX(-26px)}
                      to{opacity:1;transform:none}}
@keyframes mo-zoom{from{opacity:0;transform:scale(.965)}
                   to{opacity:1;transform:none}}

/* The whole system is gated on the user NOT asking for less motion, and on
   JS having run. Outside this block nothing is hidden and nothing moves. */
@media (prefers-reduced-motion:no-preference){
  html.js-motion [data-reveal]{opacity:0;will-change:opacity,transform}
  html.js-motion [data-reveal].is-in{animation-duration:.52s;
   animation-timing-function:cubic-bezier(.22,.61,.36,1);
   animation-fill-mode:both;will-change:auto}
  html.js-motion [data-reveal="fade"].is-in{animation-name:mo-fade}
  html.js-motion [data-reveal="rise"].is-in{animation-name:mo-rise}
  html.js-motion [data-reveal="right"].is-in{animation-name:mo-slide-r}
  html.js-motion [data-reveal="left"].is-in{animation-name:mo-slide-l}
  html.js-motion [data-reveal="zoom"].is-in{animation-name:mo-zoom;
   animation-duration:.72s}

  /* Staggering is what makes a card grid read as composed rather than as a
     page that blinked. Deloitte's own decks arrive in sequence. */
  html.js-motion [data-reveal][data-delay="1"].is-in{animation-delay:.07s}
  html.js-motion [data-reveal][data-delay="2"].is-in{animation-delay:.14s}
  html.js-motion [data-reveal][data-delay="3"].is-in{animation-delay:.21s}
  html.js-motion [data-reveal][data-delay="4"].is-in{animation-delay:.28s}
  html.js-motion [data-reveal][data-delay="5"].is-in{animation-delay:.35s}

  /* "motion of the images": a full 1s opacity ramp as each image decodes.
     Theirs is .img-lazy-show. Ours keys off the img's own load event so a
     cached image does not flash. */
  html.js-motion img.mo-img{opacity:0;transition:opacity 1s ease}
  html.js-motion img.mo-img.mo-ready{opacity:1}

  /* The slow drift behind a pinned stage. 18s, 1.04 scale: far enough to
     read as alive, small enough that nobody catches it moving. */
  html.js-motion .stage-bg img{animation:mo-drift 18s ease-in-out infinite
   alternate}
  @keyframes mo-drift{from{transform:scale(1)}to{transform:scale(1.045)}}
}

/* Hover polish, which is not motion-gated because it is user-initiated and
   instantaneous in intent. Their .animate-underline, same .3s. */
.mo-ul{position:relative;text-decoration:none}
.mo-ul::before{content:"";position:absolute;left:0;bottom:-3px;height:2px;
 width:0;opacity:0;background:currentColor;
 transition:width .3s ease,opacity .3s ease}
.mo-ul:hover::before,.mo-ul:focus-visible::before{width:100%;opacity:1}

/* A figure that lifts slightly on hover reads as interactive without
   promising a click target it does not have. */
@media (prefers-reduced-motion:no-preference) and (hover:hover){
  .band-media-fig img{transition:transform .5s cubic-bezier(.22,.61,.36,1)}
  .band-media-fig:hover img{transform:scale(1.018)}
}
