@import url('https://fonts.googleapis.com/css2?family=Geist:wght@100;200;300;400;500;600;700&display=swap');

/* ==========================================================================
   RDVS STUDIOS — Minimalist Design Language
   Design Benchmark: Minimalissimo (https://minimalissimo.com/)
   ========================================================================== */

:root {
  /* Minimalissimo Exact Color Tokens — Dark (Default) */
  --background: #000000;
  --foreground: #ffffff;
  --text-secondary: #888888;
  --text-tertiary: #555555;
  --border-color: rgba(255, 255, 255, 0.12);
  --border-hairline: rgba(255, 255, 255, 0.08);
  --surface-subtle: #0d0d0f;
  --header-bg: rgba(0, 0, 0, 0.75);
  /* The drawer is fully opaque. At 0.95 the page behind it still printed through, and on the
     homepage the welcome message occupies the same band as the drawer's first three rows
     (welcome top = --header-height + 16 = 72px, row 1 = 80px), so the sentence landed on top of
     the top link. scratch/_drawer_overlap_probe.cjs measures the collision. */
  --mobile-nav-bg: #000000;
  --search-bg: rgba(255, 255, 255, 0.04);
  --search-bg-focus: rgba(255, 255, 255, 0.08);
  --hover-bg: rgba(255, 255, 255, 0.06);
  --drawer-bg: #000000;
  --spec-backdrop: rgba(0, 0, 0, 0.5);
  --lightbox-bg: rgba(5, 5, 5, 0.96);
  --input-bg: rgba(255, 255, 255, 0.03);
  /* The same tint, flattened onto --background. A <select>'s popup is painted by the OS, so a
     translucent fill cannot travel into it; this is the opaque colour the control must carry. */
  --input-bg-solid: #080808;
  --brand-blue: #4288e7;
  --brand-blue-hover: #5da0fa;
  /* The quiet INK.  Not --border-hairline and not --text-secondary multiplied by an opacity: the site
     used both of those to dim separators and carets, and both put the result under WCAG AA -- a hairline
     border token used as a text colour measures 1.14:1 on the dark page and 1.20:1 on the light one, and
     --text-secondary at 55% measures 2.40:1 and 2.30:1.  This value is chosen from the two grounds a
     quiet row can actually stand on in this theme, the page and the subtle surface: #7a7a7a is 4.89:1 on
     --background #000000 and 4.52:1 on --surface-subtle #0d0d0f, so it clears 4.5 on both. */
  --text-quiet: #7a7a7a;
  /* Two inks for two grounds, because the hero re-pins the text tokens and the band at its foot is not
     media.  var() inside a custom property is substituted on the element that DECLARES it, so declaring
     these aliases here -- on <html>, where the cascade has already resolved [data-theme] -- freezes the
     page's own colours as literal values that no descendant re-pin can reach.  That is how the hero band
     gets its theme back while the slide above it keeps white type. */
  --ink-page: var(--foreground);
  /* And the ink for the ground that has no theme: a photograph.  The secondary is the caption's existing
     white at 78%.  Measured in the pixels that are actually on screen (scratch/_ink_pixels.cjs, both
     themes, the rows that use it): 4.17:1 at its worst of the frames sampled -- a phone frame whose
     lightest pixel is rgb(133,108,61) -- and 6.16 to 13.99:1 on every other one.  The arithmetic floor is
     worse than the best of those: 78% white over a blown-out sky that the scrim has only dimmed to 40%
     black is 2.34:1, which is why the caption's legibility is the scrim's business and is recorded as the
     one residual this layer cannot fix. */
  --ink-media: #ffffff;
  --ink-media-secondary: rgba(255, 255, 255, 0.78);
  /* Quiet ink standing on a TRANSLUCENT theme panel -- the hero band, which paints --header-bg OVER A
     PHOTOGRAPH, so its ground is not the flat token the cascade implies.  Measured in pixels by
     scratch/_ink_pixels.cjs on 2026-11-03: the light band reads rgb(220,222,222) to rgb(224,224,225) on
     the frames sampled and rgb(208,207,202) at its brightest; the dark band reads rgb(3,3,3) to
     rgb(13,11,8).  Against those measured grounds the light theme's own --text-secondary, #666666,
     computes to 3.68:1 -- still under AA -- and the white ink this replaces was 1.34:1, which is why the
     band needs an ink of its own rather than the page's quiet grey.
     Eighty-six percent of the page's ink composites to rgb(44,44,44) on the light band and rgb(222,222,222)
     on the dark one, and measures 9.89 to 14.30:1 in the light theme and 14.5 to 19.2:1 in the dark, in the
     pixels the browser actually painted.  The alpha is a floor, not a taste: scratch/_guard_theme_ink.py
     recomputes it against the whole 0..255 picture range in both themes, so a thinner value fails there
     before it can ship. */
  --ink-panel-quiet: rgba(255, 255, 255, 0.86);
  color-scheme: dark;

  /* Minimalissimo Exact Typography */
  --font-sans: 'Geist', ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif;
  --font-mono: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, monospace;

  /* Stripped to Minimalissimo Standard: 100 thin, 400 normal, 1.4 line-height */
  --font-weight-thin: 100;
  --font-weight-extralight: 200;
  --font-weight-light: 300;
  --font-weight-normal: 400;
  --font-weight-bold: 700;
  --line-height-base: 1.4;
  --line-height-heading: 1.25;

  /* Minimalissimo Spatial Grid */
  --grid-margin: 24px;
  --grid-gutter: 16px;
  --header-height: 56px;
  --max-width: 2000px;

  /* Minimalissimo 150ms standard transition */
  --transition-speed: 150ms;
  --transition-ease: ease;
}

[data-theme="light"] {
  /* Minimalissimo Exact Color Tokens — Light Mode */
  --background: #ffffff;
  --foreground: #111111;
  --text-secondary: #666666;
  --text-tertiary: #8e8e93;
  --border-color: rgba(0, 0, 0, 0.12);
  --border-hairline: rgba(0, 0, 0, 0.08);
  --surface-subtle: #f5f5f7;
  --header-bg: rgba(255, 255, 255, 0.85);
  /* Opaque for the reason given in the dark block above. */
  --mobile-nav-bg: #ffffff;
  --search-bg: rgba(0, 0, 0, 0.04);
  --search-bg-focus: rgba(0, 0, 0, 0.08);
  --hover-bg: rgba(0, 0, 0, 0.05);
  --drawer-bg: #ffffff;
  --spec-backdrop: rgba(0, 0, 0, 0.35);
  --lightbox-bg: rgba(255, 255, 255, 0.98);
  --input-bg: rgba(0, 0, 0, 0.03);
  --input-bg-solid: #f7f7f7;
  --brand-blue: #1d6fdc;
  --brand-blue-hover: #1558b0;
  /* The quiet INK, light theme: 5.10:1 on --background #ffffff and 4.68:1 on --surface-subtle #f5f5f7.
     --ink-page, --ink-media and their secondaries are NOT re-declared here -- they are var() aliases
     resolved once on <html>, so this block's own --foreground/--text-secondary/--text-quiet values are
     what they freeze. */
  --text-quiet: #6e6e6e;
  /* rgba(17,17,17,.86) is --foreground at 86%: the quiet ink for the hero band, which paints
     --header-bg translucently over a photograph and therefore is rgb(208,207,202)-ish on a bright frame
     rather than the #ffffff the token alone suggests.  See the note on --ink-panel-quiet in :root. */
  --ink-panel-quiet: rgba(17, 17, 17, 0.86);
  color-scheme: light;
}

/* Global Reset */
*, *::before, *::after {
  box-sizing: border-box;
  margin: 0;
  padding: 0;
}

html, body {
  width: 100%;
  height: 100%;
  background-color: var(--background);
  color: var(--foreground);
  font-family: var(--font-sans);
  font-weight: var(--font-weight-normal);
  line-height: var(--line-height-base);
  font-size: 16px;
  -webkit-font-smoothing: antialiased;
  -moz-osx-font-smoothing: grayscale;
  overflow-x: hidden;
}

/* Strip all heading weights and set line-height to 1.25 - 1.4 */
h1, h2, h3, h4, h5, h6 {
  font-family: var(--font-sans);
  font-weight: var(--font-weight-normal);
  line-height: var(--line-height-heading);
  letter-spacing: -0.01em;
}

p, span, a, button, input, label, li, textarea, select {
  font-family: var(--font-sans);
  font-weight: var(--font-weight-normal);
  line-height: var(--line-height-base);
  letter-spacing: normal;
}

a {
  color: inherit;
  text-decoration: none;
  transition: color var(--transition-speed) var(--transition-ease);
}

button {
  background: none;
  border: none;
  color: inherit;
  font-family: inherit;
  font-size: inherit;
  font-weight: var(--font-weight-normal);
  line-height: var(--line-height-base);
  cursor: pointer;
  padding: 0;
  transition: color var(--transition-speed) var(--transition-ease);
}

/* ==========================================================================
   Header (Minimalissimo Structure)
   Left:  "RDVS", and RDVSchool centred in the empty region beside it
   Right: Work, About, News, Expertise, Contact, then Search + theme toggle,
          and Archive at the far right END of the bar.
   Owner markup, 2026-10-22: two red "MOVE HERE" arrows moved RDVSchool out of the link group into
   the gap left of Work, and Archive out of the position before the search field to the very end of
   the bar; the blue "SHIFT TO THE LEFT A BIT HERE" covered Contact + Search, which is what giving
   the end of the bar up to Archive does to them.
   Both links STAY inside <nav class="primary-nav"> in the markup and are moved by position only, so
   the mobile drawer (which IS that element), the active-link loop in js/nav.js and the nav-drift
   reader in scratch/_nav_audit.py keep seeing all seven links. The hook classes are written by
   scratch/_nav_relocate.py.
   ========================================================================== */
.site-header {
  position: fixed;
  top: 0;
  left: 0;
  right: 0;
  height: var(--header-height);
  z-index: 50;
  background: var(--header-bg);
  backdrop-filter: blur(12px);
  -webkit-backdrop-filter: blur(12px);
  border-bottom: 1px solid var(--border-hairline);
  transition: background-color var(--transition-speed) var(--transition-ease), border-color var(--transition-speed) var(--transition-ease);
}

.header-container {
  max-width: var(--max-width);
  height: 100%;
  margin: 0 auto;
  padding: 0 var(--grid-margin);
  display: flex;
  align-items: center;
  justify-content: space-between;
  /* Container positioning context for out-of-flow .nav-school caption-datum anchor. */
  position: relative;
}

/* Studio Brand Link — strictly "RDVS" */
.brand-link {
  font-size: 1rem;
  font-weight: var(--font-weight-bold, 700);
  color: var(--brand-blue);
  flex-shrink: 0;
  letter-spacing: -0.01em;
  transition: color var(--transition-speed) var(--transition-ease), opacity var(--transition-speed) var(--transition-ease);
}

.brand-link:hover {
  color: var(--brand-blue-hover);
  opacity: 0.9;
}

/* Right-aligned Navigation & Search Group */
.header-right {
  display: flex;
  align-items: center;
  gap: 24px;
  margin-left: auto;
}

/* Core Navigation Links: Our Process, Work, About, Expertise, RDVSchool, Contact */
.primary-nav {
  display: flex;
  align-items: center;
  gap: 22px;
  /* The link group owns every pixel between the wordmark and the utility cluster, which is what
     lets RDVSchool's auto margins centre it in the leftover space at ANY viewport width instead of
     at a typed-out x coordinate. */
  flex: 1 1 auto;
  min-width: 0;
}

.nav-link {
  font-size: 0.9375rem;
  font-weight: var(--font-weight-normal);
  color: var(--text-secondary);
}

.nav-link:hover,
.nav-link.active {
  color: var(--foreground);
}

/* RDVSchool stays pinned on the homepage caption column datum on desktop (> 992px). Below 993px
   it rejoins normal drawer flow in DOM order. */
@media (min-width: 993px) {
  .header-right {
    flex: 1 1 auto;
    justify-content: flex-end;
    margin-right: 0;
  }

  .nav-school {
    position: absolute;
    left: calc(50% - 329px);
    top: 50%;
    transform: translateY(-50%);
    margin: 0;
  }

  .primary-nav {
    justify-content: flex-end;
  }

  .primary-nav a[href="our-process.html"] {
    /* Pulls Our Process toward the left without colliding with .nav-school at narrower desktop widths */
    margin-right: clamp(0px, calc(50vw - 420px), 200px);
  }
}

/* RDVSchool's animated band -- REMOVED on the owner's instruction, 2026-10-24 00:35
   (Screenshot 2026-10-24 003553.png: "GET RID OF SVG ANIMATED BACKGROUND", boxed round the wordmark).
   It landed in commit b79e7c5 as two blurred, radial-masked gradient layers on .nav-school's
   pseudo-elements, drifting against each other on school-drift-a / school-drift-b, with five
   --school-glow-* variables in each theme behind them.  All of it is out: the layers, the keyframes,
   the position/z-index the label needed for them, and the variables nothing else reads.  The label's
   place in the bar is unchanged, because the band was painted entirely on negative-inset
   pseudo-elements and never added a box of its own -- which is also why the homepage caption can still
   treat .nav-school's left edge as its column law (scratch/_hero_band_probe.cjs measures it).
   The work is not lost, only unhired: git show b79e7c5 has the whole block with its reasoning. */

/* Minimalist Search: input with clickable search icon button outside to the right */
.search-form {
  display: flex;
  align-items: center;
  gap: 6px;
}

.search-input {
  background: var(--search-bg);
  border: 1px solid var(--border-hairline);
  padding: 4px 10px;
  border-radius: 3px;
  font-size: 0.8125rem;
  line-height: var(--line-height-base);
  color: var(--foreground);
  font-family: inherit;
  font-weight: var(--font-weight-normal);
  width: 105px;
  outline: none;
  transition: width 0.2s ease, border-color var(--transition-speed) var(--transition-ease), background-color var(--transition-speed) var(--transition-ease);
}

.search-input::placeholder {
  color: var(--text-secondary);
}

.search-input:focus {
  width: 145px;
  border-color: var(--text-secondary);
  background: var(--search-bg-focus);
}

/* Clickable Search Icon button outside the text input */
.search-submit-btn {
  background: none;
  border: none;
  padding: 4px;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  color: var(--text-secondary);
  cursor: pointer;
  border-radius: 3px;
  transition: color var(--transition-speed) var(--transition-ease), background-color var(--transition-speed) var(--transition-ease);
}

.search-submit-btn:hover {
  color: var(--foreground);
  background: var(--hover-bg);
}

.search-submit-btn svg {
  width: 15px;
  height: 15px;
  display: block;
}

/* Minimalist Theme Toggle Button */
.theme-toggle-btn {
  background: none;
  border: none;
  padding: 4px;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  color: var(--text-secondary);
  cursor: pointer;
  border-radius: 3px;
  transition: color var(--transition-speed) var(--transition-ease), background-color var(--transition-speed) var(--transition-ease), transform var(--transition-speed) var(--transition-ease);
}

.theme-toggle-btn:hover {
  color: var(--foreground);
  background: var(--hover-bg);
}

.theme-toggle-btn:active {
  transform: scale(0.92);
}

.theme-toggle-btn svg {
  width: 15px;
  height: 15px;
  display: block;
}

/* Theme Icon Visibility (Zero layout-shift via CSS) */
:root .theme-icon-light {
  display: none !important;
}
:root .theme-icon-dark {
  display: block !important;
}

[data-theme="light"] .theme-icon-light {
  display: block !important;
}
[data-theme="light"] .theme-icon-dark {
  display: none !important;
}

/* Mobile Toggle */
.mobile-toggle {
  display: none;
  font-size: 0.9375rem;
  color: var(--text-secondary);
  cursor: pointer;
}

.mobile-toggle:hover {
  color: var(--foreground);
}

/* ==========================================================================
   Hero Viewport & Photographic Canvas (Homepage)
   ========================================================================== */
.hero-viewport {
  position: relative;
  width: 100vw;
  height: 100vh;
  height: 100dvh;
  background-color: var(--background);
  overflow: hidden;
  /* Hero is a permanent dark-media zone -- pin the text tokens to the MEDIA ink so a slide's overlays
     stay legible whatever the theme.  The values are tokens now rather than literals because the band at
     the hero's foot is not media, and the two pins have to say so separately (see .hero-footer-container
     and the desktop block below).
     --text-secondary was #888888: a THEME colour, painted over a photograph.  A page's quiet grey has no
     meaning on a frame -- there is no token ground to composite it against -- and the audit's own rule for
     type over media is white on the scrim, so the caption family now has one media value.  Measured in
     pixels by scratch/_ink_pixels.cjs on the rows that use it (the category line, the slide counter),
     white at 78% reads 4.17:1 at its worst -- a phone frame whose lightest pixel is rgb(133,108,61) -- and
     6.16 to 13.99:1 on every other frame sampled, in both themes.
     What that instrument also found, and what this rule cannot fix, is the slide TITLE: pure white over a
     frame that is bright where the title stands reads 1.51 to 1.78:1 (Enda - Accra Mall, SMSGH, Baobab).
     That is the scrim's job, not the ink's, and raising the scrim costs the render -- see the A/B pair in
     scratch/_scrim_ab.cjs and the owner's decision recorded in the handoff. */
  --foreground: var(--ink-media);
  --text-secondary: var(--ink-media-secondary);
  --text-tertiary: #555555;
}

.hero-slider {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
}

.slide {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  opacity: 0;
  visibility: hidden;
  transition: opacity 0.8s ease, visibility 0.8s ease;
}

.slide.active {
  opacity: 1;
  visibility: visible;
  z-index: 2;
}

.slide-media {
  background-color: #000000;
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  display: flex;
  align-items: center;
  justify-content: center;
  overflow: hidden;
}

.slide-picture {
  width: 100%;
  height: 100%;
  display: flex;
  align-items: center;
  justify-content: center;
}

.slide-picture img,
.slide-img,
.slide-video,
.slide-media video {
  width: 100%;
  height: 100%;
  object-fit: cover;
  /* Still the same fill-the-screen law -- only the vertical anchor can move. A portrait render whose
     subject sits low in the frame (the DYV media screens, Macord's night figures) would otherwise have
     that subject run off the bottom, so a slide may name its own desktop anchor through
     --slide-desktop-pos, which js/main.js sets from the pool entry's `desktopPosition`. Every slide that
     says nothing keeps `center`, and no slide is ever scaled down or cropped by this. */
  object-position: var(--slide-desktop-pos, center);
  display: block;
  filter: brightness(0.95);
  transform: none;
}

/* One phone framing law for both kinds of slide media (owner, 2026-11-03, on Ahero's film: "make sure
   we capture the right half of the video... so don't center this video like the other videos"). The
   stills already read --slide-mobile-pos here; the video pair used to re-pin `center` on top of it,
   which made the pool's `mobilePosition` field decorative for every film on the deck. The desktop rule
   above still says `object-position: center`, so this only ever changes what a phone sees, and a film
   whose entry says nothing is still centred -- `center` is the fallback in the var() and the value in
   25 of the deck's 26 film entries, counted by scratch/_guard_ahero_mobile_pos.py through the deck's own
   pool parser. */
@media (max-width: 1023px) {
  .slide-picture img,
  .slide-img,
  .slide-video,
  .slide-media video {
    object-position: var(--slide-mobile-pos, center);
  }

  /* Mobile datum line (owner markup 2026-11-09): caption rests on bottom datum line directly above controls/pagination row */
  .caption-wrapper {
    margin-bottom: 8px;
  }
}

/* The phone counterpart of the contain law, for the few WIDE plates a phone cannot show whole under
   cover (owner, 2026-11-06: "we are going to implement a mobile only rule for selected wide images
   that we can't see fully on mobile of this screen real estate. The idea is to see the full image
   with black or white at the bottom and top of the image after positioning per the theme. The image
   shouldn't go below the base like I have marked up"). The slide media no longer spans the window:
   it runs from under the nav bar down to the caption block, so the plate is centred in exactly the
   space the owner boxed, never reaching the caption. `js/main.js` measures the caption block's top
   and writes it as --mobile-contain-base; the 30% fallback is only the pre-JS frame.
   `scale-down` is the same never-upscale value the desktop law uses, and the box takes the page's
   ground, so the bands are black in the dark theme and white in the light one. */
@media (max-width: 1023px) {
  .slide-media-mobile-contain {
    /* Maintain spacing between welcome message and non-cover images */
    top: var(--mobile-contain-top, 212px);
    bottom: var(--mobile-contain-base, 30%);
    /* Owner markup 2026-11-06, a phone frame of Brownie's Place with two red guides drawn the full height
       of the screen at x=16 and x=width-16 -- the page's own margins, the lines the header, the caption
       and the footer already stand on: "let's update the datum guides for our wide treatment for mobile
       slide pool images". The box therefore sits between those two datums instead of bleeding to the
       screen edges, and the plate plus its theme ground never touch the sides. The guide lines measured
       13 and 441 on a 457px frame, i.e. the 16px column to within a hand-drawn pixel.
       width:auto is load-bearing: the base rule pins width:100%, and an absolutely placed box that is
       over-constrained ignores `right`. */
    left: var(--grid-margin);
    right: var(--grid-margin);
    width: auto;
    height: auto;
    background: var(--background);
    /* Mobile contain datum (owner markup 2026-11-09): 30px distance between media and caption */
    bottom: calc(var(--mobile-contain-base, 30%) + var(--slide-mobile-gap, 0px) + 30px);
  }

  .slide-media-mobile-contain .slide-picture img,
  .slide-media-mobile-contain .slide-img {
    object-fit: scale-down;
    object-position: center bottom !important;
  }

  /* Wide stills take the owner's datum rule (markup 2026-11-11, an 831x793 landscape window with the
     plate boxed from the left datum to the right datum and sitting on the bottom one: "constrained to
     the left, right and bottom datums and then proportionally scales upwards depending on the height of
     the image"). The box stops being pinned to a top edge -- it spans the two side datums, sits on the
     bottom datum, and the plate is drawn at the full width between them with its height from its own
     aspect, growing upward. That is the law the wide films above already follow, and it is why the box
     is no longer the thing that decides the size. The max-height is the band the top datum and the
     caption leave behind, so a plate tall enough to climb over the welcome message gives up width
     instead of overlap; at 1.5:1 or wider the cap never binds. `crop` slides keep the boxed law on
     purpose -- they are asked to FILL the band, not to hug a datum -- and films are left to their own
     rule above, because a portrait film still has to cover the window. */
  .slide-media-mobile-contain:not(.slide-media-mobile-crop):not(:has(video)),
  .slide-media-mobile-contain:not(.slide-media-mobile-crop):not(:has(video)) .slide-picture {
    top: auto;
    height: auto;
  }

  .slide-media-mobile-contain:not(.slide-media-mobile-crop):not(:has(video)) .slide-picture,
  .slide-media-mobile-contain:not(.slide-media-mobile-crop):not(:has(video)) .slide-picture img,
  .slide-media-mobile-contain:not(.slide-media-mobile-crop):not(:has(video)) .slide-img {
    width: 100% !important;
    height: auto !important;
    /* `max-width: none` and `transform: none` are for the plates that also carry the desktop boxed law
       (`slide-media-boxed`, a 1200px container shifted right onto the caption datum). Below 1024 they
       belong to the phone band, and measured before this, a 2944x1472 boxed plate sat at 124..1076 in a
       1000px window -- 100px past the right datum. The owner's 2026-11-06 law already says the desktop
       portrait positioning starts at 1024 and below it the phone law rules. */
    max-width: none !important;
    transform: none !important;
    max-height: calc(100vh - var(--contain-ceiling, var(--mobile-contain-top, 212px)) - var(--mobile-contain-base, 30%) - var(--slide-mobile-gap, 0px) - 30px);
  }

  .slide-media-mobile-contain:not(.slide-media-mobile-crop):not(:has(video)) .slide-picture img,
  .slide-media-mobile-contain:not(.slide-media-mobile-crop):not(:has(video)) .slide-img {
    object-fit: contain;
  }

  /* Wide videos on mobile (Owner request 2026-11-09):
     "Don't constrain wide videos in a square when serving/positioning them on mobile.
      Position so that we can see 100% of the wide video so that the full width is stretched/contained
      between the datumns on the left and right and the full height is proportionally scaled upwards
      from the datumn at the bottom of the frame for the video when delivering this on mobile." */
  .slide-media-mobile-contain.slide-media-mobile-wide-video,
  .slide-media-mobile-contain:has(video:not(.is-portrait-video):not(.slide-video-cover)) {
    top: auto !important;
    bottom: calc(var(--mobile-contain-base, 30%) + var(--slide-mobile-gap, 0px) + 30px) !important;
    left: var(--grid-margin) !important;
    right: var(--grid-margin) !important;
    width: auto !important;
    height: auto !important;
    background: transparent !important;
    display: flex !important;
    flex-direction: column !important;
    justify-content: flex-end !important;
  }

  .slide-media-mobile-contain.slide-media-mobile-wide-video video,
  .slide-media-mobile-contain.slide-media-mobile-wide-video .slide-video,
  .slide-media-mobile-contain video:not(.is-portrait-video):not(.slide-video-cover),
  .slide-media-mobile-contain .slide-video:not(.is-portrait-video):not(.slide-video-cover) {
    width: 100% !important;
    height: auto !important;
    max-height: none !important;
    object-fit: contain !important;
    object-position: center bottom !important;
    display: block !important;
  }

  /* `mobileFit: 'crop'` keeps the box above but lets the plate fill it, so the overflow goes to the
     anchor in `mobilePosition` instead of to a theme-ground band. Paired with `mobileGap`, which lifts
     the bottom edge off the caption, the same plate reads larger on the screen and gives up the part of
     the frame the owner does not want -- for Macord's night entrance at 390x844, a 118px gap costs 40px
     of dusk sky off the top and puts 118px of ground between the road and the caption. Under 769 px the
     contain rule pins `object-position: center`, which is why the anchor has to be re-read here. */
  .slide-media-mobile-crop .slide-picture img,
  .slide-media-mobile-crop .slide-img,
  .slide-media-mobile-crop video {
    object-fit: cover;
    object-position: var(--slide-mobile-pos, center bottom);
  }
}

/* Homepage slideshow video orientation law (Owner specification 2026-11-09):
   "All portrait videos should get the cover treatment on mobile in the homepage slideshow.
    This means when a video is portrait resolution it should stretch to cover the full screen"
   On screens >= 769px (desktop & tablet), portrait videos follow the desktop portrait contain / datum rule. */
@media (max-width: 768px) {
  .slide-media.slide-media-portrait-cover,
  .slide-media.is-portrait-video,
  .slide-media:has(> video.is-portrait-video),
  .slide-media:has(> video.slide-video-cover),
  .slide-media:has(> video[src*="villa-aggregate"]) {
    top: 0 !important;
    bottom: 0 !important;
    left: 0 !important;
    right: 0 !important;
    width: 100% !important;
    height: 100% !important;
    background: #000000 !important;
  }

  .slide-media.slide-media-portrait-cover video,
  .slide-media video.is-portrait-video,
  .slide-media video.slide-video-cover,
  .slide-media video[src*="villa-aggregate"] {
    width: 100% !important;
    height: 100% !important;
    min-width: 100% !important;
    min-height: 100% !important;
    object-fit: cover !important;
    object-position: center center !important;
    transform: none !important;
  }
}

/* A slide may ask to be shown whole rather than cropped to the window (owner, 2026-11-05: Kuma
   Residence and 3AAP — "show the image at 100% of its resolution and then fill the space around it
   with black or white per the theme color"). `scale-down` is the one object-fit that never upscales:
   a 978 px study is painted at 978 px, and contain would blow it up to the viewport. The empty window
   takes the page's own ground, so the bars are black in the dark theme and white in the light one.
   The whole treatment is desktop-only, and the owner set the floor on 2026-11-06: "implement the
   portrait positioning only on desktops from 1024 pixels wide and above. For any screen less than
   that width ... have the images fill the whole screen like before" -- below 1024 px a contained
   slide simply obeys the cover law above and crops to fill. The earlier floor was 769 px, which left
   a tablet in the 769-1023 band with theme ground at the sides instead of a full-bleed picture. */
@media (min-width: 769px) {
  .slide-media-contain,
  .slide-media:has(> video.slide-video-contain),
  .slide-media:has(> video[src*="villa-aggregate"]) {
    background: var(--background);
  }

  .slide-media-contain .slide-picture,
  .slide-media-contain video.slide-video-contain,
  .slide-media video.slide-video-contain,
  .slide-media video[src*="villa-aggregate"] {
    transform: translate(var(--slide-boxed-shift-x, 0px), var(--slide-boxed-shift-y, 0px));
  }

  /* The cover law above is written as `.slide-picture img` (0,1,1), so a bare `.slide-img-contain`
     (0,1,0) lost the cascade and every contain slide still computed `cover`. Match the picture
     context to win on specificity, and keep the bare class for any img rendered outside a <picture>. */
  .slide-picture img.slide-img-contain,
  .slide-img-contain,
  .slide-media-contain video,
  .slide-media-contain .slide-video,
  .slide-media video.slide-video-contain,
  .slide-video-contain,
  .slide-media video[src*="villa-aggregate"] {
    object-fit: scale-down !important;
    /* Owner, 2026-11-05: a plate shown whole no longer floats in the middle of the window -- its left
       edge starts on the caption's own column ("the left edge of the image is in line with the text
       like this and the rest of the image shifts slightly to the right and not dead center"), so the
       caption's text stands on the plate's edge and the theme ground gathers as one band at the right.
       Owner, 2026-11-06: that datum moved one --header-height (56px) further left, so the text stood
       just inside the plate's edge, then the same day back to half of it (28px) on
       portrait-position-adjustment-2.PNG -- the guide he drew sits 26-28 px left of the caption column,
       so the text now stands a half-bar inside the plate. js/main.js measures the plate against the
       window and writes --slide-contain-shift only where there is free space to move through: a landscape
       plate already spans the width. A portrait or square plate joins the datum at its own size too,
       which is what BFA's squares needed on a window taller than they are -- centred there, the caption
       fell inside the image. */
    object-position: calc(50% + var(--slide-contain-shift, 0px)) var(--slide-contain-y, 50%) !important;
    /* The vertical nudge (owner, 2026-11-05, on the Kuma Residence study: "shift upwards slightly")
       is a pool-entry value written as --slide-contain-y; a plate that says nothing stays centred. */
  }

  /* Boxed desktop slides: Hot Gossip is constrained to a 900px wide container with proportional height, surrounded by theme ground */
  .slide-media-contain.slide-media-boxed .slide-picture {
    width: var(--slide-desktop-width, 1200px);
    max-width: var(--slide-desktop-width, 1200px);
    height: auto;
    aspect-ratio: auto;
    display: flex;
    align-items: center;
    justify-content: center;
    transform: translate(var(--slide-boxed-shift-x, 0px), var(--slide-boxed-shift-y, 0px));
  }

  .slide-media-contain.slide-media-boxed .slide-picture img.slide-img-contain,
  .slide-media-contain.slide-media-boxed .slide-picture img {
    width: 100%;
    height: auto;
    object-fit: contain;
    object-position: center;
  }
}

/* Portrait and square media on the landscape tablet band (owner, 2026-11-11, on an 831x793 window:
   "all the portrait and square images/gifs/videos get the full screen/cover treatment"), and from the
   same day the wide plates that cannot stand at full width in the datum box ("when the image is taller
   than the [room] for it to give it the wide image treatment, give it the cover treatment instead").
   js/main.js puts .slide-media-tablet-cover on the active slide inside this band only, reading the shape
   off the media's own pixels, so the rule does not have to know which shape it is serving -- it only has
   to undo the contain treatment and paint the frame edge to edge. Same values as the portrait cover floor
   at <=768px, so the two bands cannot disagree.
   It sits HERE, after the desktop contain block above, on purpose: that block pins
   `object-fit: scale-down !important` and a shifted `object-position !important` on every contain
   plate from 769px up, and at equal weight the later rule wins -- measured before the move, a
   2800x3267 portrait plate carried the class and still painted 679x793 with 76px of ground at each
   side. The `.slide-picture img` form is what outranks it on specificity. */
@media (min-width: 769px) and (max-width: 1024px) and (orientation: landscape) {
  .slide-media.slide-media-tablet-cover {
    top: 0 !important;
    bottom: 0 !important;
    left: 0 !important;
    right: 0 !important;
    width: 100% !important;
    height: 100% !important;
    background: #000000 !important;
  }

  .slide-media.slide-media-tablet-cover .slide-picture,
  .slide-media.slide-media-tablet-cover .slide-picture img,
  .slide-media.slide-media-tablet-cover .slide-picture video,
  .slide-media.slide-media-tablet-cover img,
  .slide-media.slide-media-tablet-cover video {
    width: 100% !important;
    height: 100% !important;
    max-width: none !important;
    max-height: none !important;
    object-fit: cover !important;
    object-position: center center !important;
    transform: none !important;
  }

  /* A WIDE plate sent to cover has to beat the phone datum rule above on `height` as well, or it keeps
     `height: auto` and letterboxes inside this box's black ground: measured at 839x779 a 2048x1331 plate
     painted 839x545 in the 839x779 box. The datum rule's `.slide-media-mobile-contain:not(...):not(...)
     .slide-picture img` form carries three classes and two types, which outranks the four-class, one-type
     selectors above, so this rule takes the extra class and wins. Portrait and square plates never showed
     the problem because their auto height is already taller than the band, so the box crops them and the
     result reads as cover either way. */
  .slide-media.slide-media-mobile-contain.slide-media-tablet-cover .slide-picture,
  .slide-media.slide-media-mobile-contain.slide-media-tablet-cover .slide-picture img,
  .slide-media.slide-media-mobile-contain.slide-media-tablet-cover .slide-picture video,
  .slide-media.slide-media-mobile-contain.slide-media-tablet-cover img,
  .slide-media.slide-media-mobile-contain.slide-media-tablet-cover video {
    height: 100% !important;
    max-height: none !important;
  }
}

/* That cover rule has no opt-out (owner, 2026-10-23: "make sure the video for the news slide fills the
   screen like all the other slides"). The intro film on the news slide used to letterbox itself with a class
   of its own, which drew black bars whenever the window's aspect differed from the rendition it was served.
   The class, the rule and the entry key the builder read are all gone, so the deck has one framing rule and a
   slide cannot opt out of it -- the ladder in js/main.js is what protects that film now, by matching its
   aspect to the device it plays on, and scratch/_news_slide_fill.py is what reports the crop that remains.
   The retired class is not named in this file on purpose: its occurrence count across js/ and css/ is the
   machine-checkable statement that the mechanism is gone rather than parked, and a comment would break it. */

.slide.active .slide-img,
.slide.active .slide-picture img {
  transform: none;
}

.hero-scrim {
  position: absolute;
  inset: 0;
  pointer-events: none;
  z-index: 3;
  background: linear-gradient(180deg, rgba(0, 0, 0, 0.4) 0%, transparent 20%, transparent 65%, rgba(0, 0, 0, 0.75) 100%);
  transition: opacity 0.8s ease;
}

/* Owner, 2026-11-06: "when we implement wide treatment on a mobile slide or portrait treatment on a
   desktop slide positioning, let's not add drop shadow from the top or bottom band of the homepage",
   asked again minutes later with "for portrait or square images" added. The gradient above only ever
   paints the top fifth and the bottom third of the window, which on a contained slide are theme
   ground, so in the light theme the white band read as a grey drop shadow (0.4 alpha over white =
   rgb(153,153,153)). js/main.js raises this flag wherever the treatment is actually in force -- phone
   contain at <=768 px, portrait contain at >=1024 px -- so every cover slide and the 769-1023 band
   that renders under the cover law keep the scrim exactly as it was. The first pass also required the
   plate to leave a real band, which exempted a contain plate tall enough to run the window's full
   height; the owner's second ask, naming portrait and square plates, dropped that exemption. The fade
   matches the slides' own 0.8 s cross-fade. */
.hero-viewport.is-contain-slide .hero-scrim {
  opacity: 0;
}

.hero-footer {
  position: absolute;
  bottom: 0;
  left: 0;
  right: 0;
  z-index: 10;
  padding: 0 var(--grid-margin) var(--grid-margin) var(--grid-margin);
}

.hero-footer-container {
  position: relative;
  /* Two numbers drive the desktop hero band, both explained at the block that reads them:
     --hero-caption-inset is the column the caption is aligned to, --hero-caption-min is how far
     left it may ever go.  They live here because this box is the containing block for the caption's
     percentage margin and for the two absolutely placed parts of the band. */
  --hero-caption-inset: 330px;
  --hero-caption-min: 288px;
  /* One lift, three readers.  The caption's margin-bottom raises the title so its bottom edge lands on
     a hero fraction, and the two caption lines that live in the band are written as distances from THAT
     edge -- so the lift cancels out of them and they stay on the band's rows whatever the title does.
     25dvh - grid-margin is the three-quarter line, which is where the markup of 01:10 moved the title
     to; 50dvh - grid-margin was the mid-line it came from.  The vh/dvh pair is the same fallback the
     site uses everywhere else that reads a viewport height. */
  --hero-caption-lift: calc(25vh - var(--grid-margin));
  --hero-caption-lift: calc(25dvh - var(--grid-margin));
  /* The header's Work column, as a distance back from the header's own content-box right edge --
     measured 602.3px at 1200, 1365, 1440 and 1920 by scratch/_hero_lines_geom.cjs.  Above a 2048px
     viewport the two containers part company by exactly --grid-margin, because the header keeps its
     padding inside the 2000px cap while the hero footer's padding sits outside it; the /2 term below
     pays that back so the column is still exact at 2560.  1952px = --max-width - 2 * --grid-margin. */
  --hero-social-inset: 602.3px;
  --hero-social-cap: 1952px;
  /* Owner markup 2026-10-27: the bottom strip (socials row + "Website by RDVS")
     gets a theme-colored background like the fixed nav bar at the top.  Owner markup 2026-11-03 (a phone
     screenshot with the band's top edge drawn in and the words "MAKE SAME BLACK/WHITE BACKGROUND LIKE
     NAVIGATION AREA PER THEME"): that bar has to reach the TOP of the controls block, not stop under it.
     Measured before the change, the counter row and the hairline bars sat on the raw slide because the bar
     topped below them -- 35px uncovered at 390x844, 24px at 804x742, 7px at 1276x796.
     One ::before bar on THIS box (it alone spans the full width at every tier -- below 1200
     .hero-meta-controls is a right-packed flex item), full-bleed to the viewport edges, painted above the
     slide (inside .hero-footer's stacking context) but below the caption.  --hero-strip-height is
     DERIVED, not typed, from the rows the bar is meant to carry.
     Owner markup 2026-11-03 again (the same drawing, an arrow onto this band's top edge at the caption
     cluster, "REDUCE HEIGHT ON DESKTOP"): the desktop bar was too tall.  It was 63px because it was
     derived off the CONTROLS BLOCK's box (31 + 24 floor + 8 air), and the block's box is 31px of mostly
     empty column -- the counter line is lifted 14.9px out of it by the markup of 2026-10-27, so the ink
     that actually needed carrying topped at 32.4px above the viewport bottom while the bar topped at 63.
     The extra 30px is what he is pointing at, and the edge did not even clear the type: measured at every
     desktop tier from 1200 to 2560, the counter row's ink box runs 55.9..69.9 and the category line's
     57.0..73.8, so a 63px bar cut through both of them.
     The bar is therefore derived off the ink it carries, not off a box: the topmost row it owns is the
     links/socials/credit line at 32.4px above the viewport bottom, plus the same 8px of air = 40px.  That
     puts its top edge in the 30.9px gap the two markups already left between the hairline bars and the
     counter line -- 7.6px above the ink it covers, 15.9px below the ink it does not -- so the band is 23px
     shorter (36%) and no edge runs through any text.  The two lower tiers keep the 2026-11-03 law as
     drawn: their controls block really is one tall stack (76px at 641-1199, 89px at <=640), so those
     bars stay at 108 and 113. */
  --hero-strip-height: 40px;
  /* THE BAND IS NOT MEDIA.  Its ::before paints --header-bg -- the owner's markup of 2026-11-03 asked
     for "same black/white background like navigation area per theme" -- so the ink standing on it has to
     follow the theme too, and the hero's dark-media pin above it has to be undone here.
     What that pin was doing, measured two ways on 2026-11-03.  scratch/_theme_contrast.cjs composites the
     token chain and filed the credit and the social row as #888888 on the panel's own colour (3.54:1), and
     "View project", "Details" and the active slide number as #ffffff on it (1.00:1).  scratch/_ink_pixels.cjs
     then measured the panel as the browser paints it -- rgb(220,222,222) to rgb(224,224,225) over the frames
     sampled -- and the same two inks are 2.30:1 and 1.34:1 on that ground.  Both instruments say the same
     thing in different units: the light theme's footer was white type on a milky panel.  The aliases resolve
     on <html>, where the cascade has already picked the theme, so they are the page's own colours in a form
     this subtree cannot re-pin.
     The rows that rise ABOVE the band's top edge are back on the slide and take the media ink again --
     and WHICH rows those are is a measurement, not a breakpoint: at 1440x900 it is the counter and the
     category and the title, at 390x844 it is the whole caption cluster (category, title, links) with the
     counter still inside the band, and at 1024x768 nothing but the picture is above it while at 641x900
     the cluster is.  The [data-hero-ground] block at the foot of this file states the two inks and
     assignHeroGrounds() in js/main.js decides per row, per window, which one it wears. */
  --foreground: var(--ink-page);
  --text-secondary: var(--ink-panel-quiet);
  max-width: var(--max-width);
  margin: 0 auto;
  display: flex;
  align-items: flex-end;
  justify-content: space-between;
  gap: 32px;
}

.hero-footer-container::before {
  content: '';
  position: absolute;
  left: calc((100% - 100vw) / 2);
  right: calc((100% - 100vw) / 2);
  height: var(--hero-strip-height);
  bottom: calc(-1 * var(--grid-margin));
  background: var(--header-bg);
  backdrop-filter: blur(12px);
  -webkit-backdrop-filter: blur(12px);
  border-top: 1px solid var(--border-hairline);
  transition: background-color var(--transition-speed) var(--transition-ease), border-color var(--transition-speed) var(--transition-ease);
  z-index: -1;
  pointer-events: none;
}

.caption-wrapper {
  max-width: 620px;
}

.caption-card {
  display: none;
  opacity: 0;
  transform: translateY(6px);
  transition: opacity 0.35s ease, transform 0.35s ease;
}

.caption-card.active {
  display: block;
  opacity: 1;
  transform: translateY(0);
}


.caption-card .project-desc {
  display: none !important;
}

/* Very thin service name on homepage slides */
.caption-card .project-service,
.caption-card .project-category,
.caption-card .service-name,
.project-category,
.project-service {
  font-weight: 100 !important;
  letter-spacing: 0.03em;
  -webkit-font-smoothing: antialiased;
  -moz-osx-font-smoothing: grayscale;
}

.project-category {
  font-size: 0.75rem;
  line-height: var(--line-height-base);
  color: var(--text-secondary);
  margin-bottom: 5px;
}

/* "INCREASE FONT HEIGHT TO 200% CURRENT HEIGHT" -- Screenshot 2026-10-24 001708.png boxes the slide
   title at y 277-319 against the title's own 299-317.5: twice the height, sharing the bottom edge and
   opening upward.  Every arm of the clamp doubles so the ratio holds at every width, not just the one
   he screenshotted.  Nothing else has to move: the band rule in the 1200px block below pins this box's
   bottom edge to the hero's mid-line, so the type grows up from the line exactly as drawn.
   The class is the homepage caption's alone -- index.html's fifteen slides and js/main.js's caption
   builder, nowhere else on the site -- so a project page cannot pick this size up. */
.project-title {
  font-size: clamp(1.35rem, 2.5vw, 1.85rem);
  /* "REDUCE FONT WEIGHT TO HAIRLINE" -- Screenshot 2026-10-24 003553.png, the same sheet that asked for
     twice the height, and asked again on 2026-10-24 when the glass came off: "make the weight of the
     font hairline".  --font-weight-thin is 100 and the css2 menu serves 100 on all 231 pages, so this
     is the real Geist hairline and not a synthesis; it is also the weight the caption's category line
     already carries in the legibility block at the foot of this file, which is what the two lines
     share.  Nothing in the deleted plate raised it -- that was a background, not a weight. */
  font-weight: var(--font-weight-thin);
  line-height: var(--line-height-heading);
  color: var(--foreground);
  margin-bottom: 6px;
}

/* The milky-glass plate and its left-to-right sweep -- REMOVED on the owner's instruction,
   2026-10-24, one sheet after the band's twelfth markup put them in ("MILKY GLASS BACKGROUND",
   "SWIPE").  What went: the `.project-title::before` layer (fill, border, radius, backdrop-filter),
   the `hero-title-sheen` keyframes, and the `position: relative; isolation: isolate;` rule that
   existed only to give that pseudo-element a containing block and a stacking context.  What stayed:
   the title is still a link to its own project page, still hairline, still 37.0px of line box.
   `scratch/_verify_title_live.py` asserts the ABSENCE of all three plate shapes over the wire, and
   `scratch/_title_flat_probe.cjs` proves it in the parsed cascade and in pixels -- its control re-injects
   this exact plate out of git and requires the crop to CHANGE, so "identical crops" cannot mean a blind
   crop. `scratch/_hero_band_probe.cjs` still measures the geometry the plate was built around (346/346 at
   21 viewports after the removal): the plate used negative insets, so taking it away moves nothing. */
/* The title is a link now, so it answers a hover the way the caption's other link does.  The
   global `a { color: inherit }` at the head of this file already carries the white; this is the
   affordance, not the colour.  line-height: inherit is not cosmetic -- a rule near the top of this
   file gives every bare `a` the body's --line-height-base, and that taller line box inside the
   heading grew the title from 37.0px to 41.4px, which is the one number the hero band measures.
   font-weight: inherit is the same trap's other arm, and it is why the hairline was asked for three
   times.  The heading above does say 100, and Geist 100 does load, but the visible glyphs are inside
   this anchor, and the site-wide `p, span, a, button, … { font-weight: var(--font-weight-normal) }`
   rule at the head of this file sets 400 on the anchor DIRECTLY -- a declaration on the element beats
   inheritance from its parent, so the heading's hairline never reached the type.  Measured on the
   deployed page at 1600x1000 before this line: heading 100, anchor 400. */
.project-title-link {
  line-height: inherit;
  font-weight: inherit;
  transition: opacity var(--transition-speed) var(--transition-ease);
}

.project-title-link:hover {
  opacity: 0.72;
}

.project-desc {
  font-size: 0.9375rem;
  line-height: var(--line-height-base);
  color: var(--text-secondary);
  max-width: 540px;
  margin-bottom: 14px;
}

.project-links {
  display: flex;
  align-items: center;
  gap: 16px;
}

.project-action-link {
  font-size: 0.75rem;
  line-height: var(--line-height-base);
  color: var(--foreground);
  display: inline-flex;
  align-items: center;
  gap: 5px;
}

.project-action-link:hover {
  color: var(--text-secondary);
}

.project-spec-trigger {
  font-size: 0.75rem;
  line-height: var(--line-height-base);
  color: var(--text-secondary);
  background: none;
  border: none;
  cursor: pointer;
  padding: 0;
  text-decoration: underline;
  text-underline-offset: 2px;
  transition: color var(--transition-speed) var(--transition-ease);
}

.project-spec-trigger:hover {
  color: var(--foreground);
}

.hero-meta-controls {
  position: relative;
  display: flex;
  flex-direction: column;
  align-items: flex-end;
  gap: 12px;
  flex-shrink: 0;
}

/* ==========================================================================
   Minimalist Video Volume Controls
   Benchmark: Minimalissimo (Quiet, hairline, refined)
   ========================================================================== */
.minimal-volume-control {
  display: inline-flex;
  align-items: center;
  gap: 8px;
  background: rgba(0, 0, 0, 0.65);
  border: 1px solid rgba(255, 255, 255, 0.14);
  backdrop-filter: blur(12px);
  -webkit-backdrop-filter: blur(12px);
  padding: 5px 10px;
  border-radius: 20px;
  user-select: none;
  z-index: 25;
  transition: opacity 0.25s ease, visibility 0.25s ease, border-color var(--transition-speed) var(--transition-ease), background-color var(--transition-speed) var(--transition-ease);
}

.hero-volume-control {
  position: relative;
  display: none;
  align-items: center;
  /* Two thirds of the size, per the owner's markup of 2026-10-22, which boxes the volume pill
     together with the slide counter and reads "REDUCE TO 2/3RDS OF SIZE". Measured at 1440 px
     the pill was 106 x 28 and the counter 54 x 21, so every value below is the old one x 2/3:
     gap 8 -> 5, padding 4/10 -> 2.5/7, radius 20 -> 13, and the descendants under it. The
     1 px border and the 1 px hairline idiom stay as they are -- the site's rules do not scale. */
  gap: 5px;
  background: rgba(0, 0, 0, 0.65);
  border: 1px solid rgba(255, 255, 255, 0.14);
  backdrop-filter: blur(12px);
  -webkit-backdrop-filter: blur(12px);
  padding: 2.5px 7px;
  border-radius: 13px;
  user-select: none;
  z-index: 25;
  transition: border-color var(--transition-speed) var(--transition-ease), background-color var(--transition-speed) var(--transition-ease);
}

.hero-volume-control.visible {
  display: inline-flex;
}

/* Scoped to the hero on purpose: main.js builds the same .volume-toggle-btn /
   .volume-slider markup into a .video-volume-overlay on every project-page film, and that
   one keeps its original size. */
.hero-volume-control .volume-toggle-btn {
  width: 12px;
  height: 12px;
}

.hero-volume-control .volume-toggle-btn svg {
  width: 10px;
  height: 10px;
}

.hero-volume-control .volume-slider-container {
  width: 39px;
  height: 9px;
}

.hero-volume-control .volume-slider {
  height: 1.33px;
}

.hero-volume-control .volume-slider::-webkit-slider-thumb {
  width: 5px;
  height: 5px;
}

.hero-volume-control .volume-slider::-moz-range-thumb {
  width: 5px;
  height: 5px;
}

.hero-status-row {
  display: flex;
  align-items: center;
  justify-content: flex-end;
  gap: 16px;
}

.minimal-volume-control:hover {
  border-color: rgba(255, 255, 255, 0.35);
  background: rgba(0, 0, 0, 0.82);
}

.volume-toggle-btn {
  background: none;
  border: none;
  /* Sits on dark media control surface in both themes — keep white */
  color: #ffffff;
  opacity: 0.85;
  cursor: pointer;
  padding: 0;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 18px;
  height: 18px;
  transition: opacity var(--transition-speed) var(--transition-ease), transform var(--transition-speed) var(--transition-ease);
}

.volume-toggle-btn:hover {
  opacity: 1;
  transform: scale(1.08);
}

.volume-toggle-btn svg {
  width: 15px;
  height: 15px;
  stroke: currentColor;
  fill: none;
  stroke-width: 1.5;
  stroke-linecap: round;
  stroke-linejoin: round;
}

.volume-slider-container {
  display: flex;
  align-items: center;
  position: relative;
  width: 58px;
  height: 14px;
}

.volume-slider {
  -webkit-appearance: none;
  appearance: none;
  width: 100%;
  height: 2px;
  background: rgba(255, 255, 255, 0.2);
  border-radius: 1px;
  outline: none;
  cursor: pointer;
  margin: 0;
  transition: background var(--transition-speed) var(--transition-ease);
}

.volume-slider::-webkit-slider-thumb {
  -webkit-appearance: none;
  appearance: none;
  width: 8px;
  height: 8px;
  border-radius: 50%;
  background: #ffffff;
  cursor: pointer;
  box-shadow: 0 0 3px rgba(0, 0, 0, 0.6);
  transition: transform 0.15s ease;
}

.volume-slider::-webkit-slider-thumb:hover {
  transform: scale(1.25);
}

.volume-slider::-moz-range-thumb {
  width: 8px;
  height: 8px;
  border-radius: 50%;
  background: #ffffff;
  border: none;
  cursor: pointer;
  box-shadow: 0 0 3px rgba(0, 0, 0, 0.6);
  transition: transform 0.15s ease;
}

.volume-slider::-moz-range-thumb:hover {
  transform: scale(1.25);
}

.volume-slider::-moz-range-track {
  height: 2px;
  background: transparent;
  border-radius: 1px;
}

/* Standalone video volume overlay for any video on the site */
.video-volume-overlay {
  position: absolute;
  bottom: 16px;
  right: 16px;
  z-index: 10;
}

.slide-status {
  display: flex;
  align-items: baseline;
  /* 0.9375rem -> 0.625rem and 6px -> 4px: the counter shares the boxed cluster with the
     volume pill, and the owner's markup asks that cluster for two thirds of its size. */
  gap: 4px;
  font-size: 0.625rem;
  color: var(--text-secondary);
}

.status-active {
  color: var(--foreground);
}

.pagination-bars {
  display: flex;
  align-items: center;
  gap: 4px;
}

.pagination-bar {
  width: 12px;
  height: 1px;
  /* A control, not text, so its bar is WCAG 1.4.11 -- 3:1 against the ground it sits on.  These dashes
     are on the hero band at every tier, and the band now follows the theme, so they read the quiet INK
     (4.89:1 on the dark theme's panel, 3.83:1 on the light theme's worst-case panel) instead of
     --text-tertiary, which is 2.82:1 on the dark page -- under even the 3:1 bar. */
  background-color: var(--text-quiet);
  cursor: pointer;
  position: relative;
  transition: background-color var(--transition-speed) var(--transition-ease), width var(--transition-speed) var(--transition-ease);
}

.pagination-bar:hover {
  background-color: var(--text-secondary);
}

.pagination-bar.active {
  width: 22px;
  /* Was rgba(255,255,255,.4): a 40% white dash is the one thing a light-theme band cannot show at all
     (1.05:1 against the milky panel).  The active dash takes the band's own full ink, which is white on
     the dark theme and near-black on the light one, and stays the brightest mark on the line either
     way. */
  background-color: var(--foreground);
}

.pagination-fill {
  position: absolute;
  top: 0;
  left: 0;
  height: 100%;
  width: 0%;
  background-color: var(--foreground);
}

/* ==========================================================================
   Hero edge step arrows
   The owner's markup of 2026-10-22 deleted the Previous/Next text pair from the hairline row and drew
   a chevron at each edge of the media instead, annotated "ADD ARROWS, ONLY VISIBLE ON MOUSE OVER"; the
   follow-up the same day settled what "mouse over" means: *"Keep each of the arrows invisible until the
   left or right side of slide. On mouse over on the left section of the slide reveal the left arrow and
   on mouse over on the right side of the image reveal the right arrow."* So each arrow belongs to one
   SIDE of the slide -- the whole band is its own hover target and its own click target, and it is the
   only thing that lights up when the pointer is in it. No halo either: the chevron is bare line.
   Keyboard users get the arrow on focus. A touch device (hover: none, pointer: coarse) gets the arrows
   AT REST -- it has no hover to wait for, so hiding them there left a phone with no arrows at all, and the
   owner asked for them back on 2026-10-23; the block at the end of this section is the treatment. The
   hairline bars and the arrow keys stay usable everywhere, and the footer's z-index keeps every caption,
   bar, pill and link above the bands.
   Class names stay .step-btn.prev / .step-btn.next because js/main.js binds exactly those selectors.
   ========================================================================== */
.hero-step-nav {
  position: absolute;
  inset: 0;
  /* Above the scrim, BELOW .hero-footer (10), so the caption, the hairline bars, the volume pill and
     the social links all win the hit test where they overlap the bands. */
  z-index: 9;
  /* The layer spans the hero only so the bands can be placed from its edges. It takes no hits itself --
     measured: with this line removed the middle of the slide hit `div.hero-step-nav` instead of the
     media, because the two bands are children of a full-inset box. */
  pointer-events: none;
  /* One number to tune: how much of the slide counts as "the left side" / "the right side". */
  --step-zone: 16%;
}

.step-btn {
  position: absolute;
  top: 0;
  bottom: 0;
  display: inline-flex;
  align-items: center;
  padding: 0;
  border: none;
  background: none;
  /* Sits on dark media in both themes, same as the volume pill and the hairline bars. */
  color: #ffffff;
  cursor: pointer;
  pointer-events: auto;
  opacity: 0;
  transition: opacity var(--transition-speed) var(--transition-ease);
}

/* The band is the zone; the glyph stays where the drawing put it, one grid margin from the edge. */
.step-btn.prev {
  left: 0;
  width: var(--step-zone);
  justify-content: flex-start;
  padding-left: var(--grid-margin);
}

.step-btn.next {
  right: 0;
  width: var(--step-zone);
  justify-content: flex-end;
  padding-right: var(--grid-margin);
}

.step-btn:hover,
.step-btn:focus-visible {
  opacity: 1;
  outline: none;
}

.step-btn svg {
  width: 22px;
  height: 44px;
  stroke: currentColor;
  fill: none;
  stroke-width: 1.5;
  stroke-linecap: round;
  stroke-linejoin: round;
}

/* Owner order, 2026-11-08: when serving 100% resolution on desktop and the left and right
   of image or video are empty and showing white in the light theme, make the hover color
   of the previous and next arrows dark grey. */
@media (min-width: 1024px) {
  [data-theme="light"] .hero-viewport.is-contain-slide .step-btn {
    color: #666666;
  }
  [data-theme="light"] .hero-viewport.is-contain-slide .step-btn:hover,
  [data-theme="light"] .hero-viewport.is-contain-slide .step-btn:focus-visible,
  [data-theme="light"] .hero-viewport.is-contain-slide .step-btn:active {
    color: #666666;
  }
}

/* A touch screen has no hover to wait for, so an arrow that only appears under a pointer never appears
   at all (owner, 2026-10-23: "let's have the arrows for the slideshow on mobile screen too"). They rested
   at 55% until the owner changed the rule on 2026-11-06: "Even on touch screen on mobile, hide arrow icons
   for previous and next slides until user touches the screen. On screen touch, show for 3 seconds and then
   hide again until another touch." So the rest state is now hidden, and js/main.js adds `is-revealed` to
   .hero-step-nav on every touchstart and takes it off three seconds later. The 16% side bands and their
   tap target are unchanged, so a first tap inside a band still reveals and still steps. `:active` keeps the
   glyph at full strength under the finger that is pressing it. */
@media (hover: none) and (pointer: coarse) {
  .step-btn {
    opacity: 0;
  }

  .hero-step-nav.is-revealed .step-btn {
    opacity: .55;
  }

  .hero-step-nav.is-revealed .step-btn:active {
    opacity: 1;
  }
}

/* Base Social Navigation Links */
.hero-controls-row {
  display: flex;
  flex-direction: column;
  align-items: flex-end;
  gap: 12px;
}

/* Owner markup 2026-11-06, on a phone slide of The Fitzgerald: the social row boxed with an arrow down
   onto the studio credit -- "MOVE SOCIAL MEDIA LINKS TO THE LINE BELOW IN LINE WITH WEBSITE BY RDVS".
   The wrapper is inert everywhere the band lays out its own columns: display:contents leaves the nav and
   the credit as direct participants in .hero-footer-container, so the >=1200px absolute pins and the
   641-1199 stack read exactly as they did before the wrapper existed. Only the phone tier below turns it
   into the row. */
.hero-credit-row {
  display: contents;
}

.hero-social-links {
  display: flex;
  align-items: center;
  gap: 16px;
  margin-top: 4px;
}

.hero-social-link {
  font-size: 0.75rem;
  letter-spacing: 0.04em;
  color: var(--text-secondary);
  text-decoration: none;
  transition: color var(--transition-speed) var(--transition-ease);
  white-space: nowrap;
}

.hero-social-link:hover,
.hero-social-link:focus-visible {
  color: var(--foreground);
}

/* The studio credit the owner's markup of 2026-10-23 asked for at the bottom-right of the hero:
   "WEBSITE BY RDVS", plain text, no link, on the type scale of the social row it sits beside.
   It is the last child of the controls block, where the block's own alignment puts it at that
   block's right edge -- under the social row on a phone or a tablet.  At desktop widths the swap
   block below stretches the controls block across the band and pins the credit to its far end. */
.hero-credit {
  text-align: right;
  font-size: 0.75rem;
  letter-spacing: 0.04em;
  color: var(--text-secondary);
  white-space: nowrap;
}

/* ==========================================================================
   The hero band at desktop widths -- the swap
   The owner's fifth and sixth drawings of 2026-10-23 put the caption and the controls block in each
   other's place ("CHANGE POSITIONS", two curl arrows between them), and asked that the block be
   "LEFT ALIGNED" to a line drawn under the header's RDVSchool wordmark.  Measured 1:1 against the
   live page at 1440, 1920 and 2560 that line is a law, not an estimate: the wordmark's left edge
   sits at vw/2 - 330px.  This container is centred with the same max-width as the header, so 50% of
   it is the same vertical line, and a percentage margin of calc(50% - 330px) lands the caption on
   the wordmark at every viewport -- until the floor below takes over.
   Order after the swap, two columns on one bottom line:
     the controls block, pinned to the container's left edge, three lines tall -- pill and counter,
       hairline bars, social row -- every line starting at that edge;
     the caption, in the wordmark's column;
     the credit, pinned to the right edge.
   --hero-caption-min is the floor, and it is the controls block's own width: its widest line is the
   social row at 256px (the bars are 246px, the pill and counter together 121px) plus the 32px the two
   columns want between them.  So below 1284px of viewport the caption stops at the floor instead of
   sliding under the block, and above it the caption tracks the column exactly -- which is the whole
   point of stacking the block: at 1365px the column sits at 352 and the 415px floor this replaced was
   shunting the caption 87px past it.  The credit needs the same arithmetic on the right: caption 620
   + credit ~120 + block 256 + two gaps 64 = 1060, so the band closes at 1108px of viewport; the
   breakpoint stays at 1200px, where it has room to spare.
   ========================================================================== */
/* The mid band (641-1199) stacks the strip's rows taller than the desktop
   floor-line pair.  Owner markup 2026-11-03 asks the theme bar to cover the whole controls block here
   too: measured at 700, 1000 and 1150 the block is 76px tall and stands on 24px of floor padding, so the
   bar is 76 + 24 + 8 of air = 108px.  Its top edge lands at 634 in an 804x742 window, which is 12px above
   the caption's category line -- at this tier the caption and the controls share the band's rows, so the
   category now sits on the same background the title and the links already did. */
@media (max-width: 1199px) {
  .hero-footer-container {
    --hero-strip-height: 108px;
  }
}

/* The band's top edge, 8px higher on the 1024-1199 tier (owner, 2026-11-11, the same
   Capture-res-002.PNG: a blue rule drawn along the plate's foot at image y 865 with the words "MOVE EDGE
   UP BY 8PX"). The bar's rows are bottom-anchored, so the extra height is all taken off the top edge and
   nothing in the band moves. Measured at 1165x803: the edge was at 695 CSS, the markup's line at 692. */
@media (min-width: 1024px) and (max-width: 1199px) {
  .hero-footer-container {
    --hero-strip-height: 116px;
  }
}

@media (min-width: 1200px) {
  /* Out of the flex flow, so the caption is the only in-flow item and its percentage margin is the
     whole story.  The box spans the band left to right -- it is transparent, and .hero-footer
     already keeps this strip off the slide for clicks -- so the credit inside it can be pinned to
     the band's right edge without becoming a third child of the container, which at narrower
     widths would have joined the space-between row and moved the controls block to the centre. */
  .hero-meta-controls {
    position: absolute;
    left: 0;
    right: 0;
    bottom: 0;
    align-items: flex-start;
  }

  /* Every row of the block starts at the block's left edge instead of ending at its right. */
  .hero-controls-row {
    align-items: flex-start;
  }

  /* The owner's markup of the swap gives the bars the far-left slot and lifts the pill and the
     counter out of it.  They cannot share a line, so the row wraps: the pill and the counter keep
     the first line at order 0, and the bars take a line to themselves below. */
  .hero-status-row {
    justify-content: flex-start;
    /* A wrapping flex container sized by its content adds its items up -- 386px of one-line
       arithmetic, which would drag the bars' stretched box past the caption.  min-content of a
       multi-line container is its LARGEST item instead: 246px of hairlines, so the row is exactly as
       wide as the widest thing it actually draws. */
    width: min-content;
    flex-wrap: wrap;
    /* 16px is the gap the block already uses between its second line and its third -- the controls
       row's 12px plus the social row's own 4px margin-top.  The three lines share one rhythm. */
    row-gap: 16px;
  }

  .hero-status-row .pagination-bars {
    order: 3;
    /* A full basis is what puts it on its own line once the row wraps. */
    flex-basis: 100%;
    /* The hairline rides with the text line it crosses, so it takes that line's move: the line's box
       centre sits 20px above the band's floor and the bars' own untransformed centre sits 24.5px, so
       4.5px DOWN puts the hairline through the middle of the social row wherever the owner's law puts
       that row. Before the band-relative correction of 2026-11-05 this was -4.5px, which tracked the
       old 3.9px sink. */
    transform: translateY(4.5px);
  }

  /* "MOVE UP INLINE WITH →" -- the owner's fifteenth markup (2026-10-27) boxes the volume pill and
     the slide counter in red and draws the arrow to the caption's category line.  Measured on the
     drawing at 1365x635: the category line's bottom edge sits 33px above the band's floor, the
     counter's row sat 16px above the hairline bars' row with the counter's own ink ~17px tall, so
     the counter's bottom edge needed 14.9px of lift to land inline with the category line's bottom
     edge.  A transform keeps the lift off the flex row's rhythm -- moving bottom would change the
     gap to the bars below, which the drawing never touches.  Bars and socials are not in the drawn
     box and do not move. */
  .hero-status-row .hero-volume-control,
  .hero-status-row .slide-status {
    transform: translateY(-14.9px);
  }

  .caption-wrapper {
    margin-left: max(calc(50% - var(--hero-caption-inset)), var(--hero-caption-min));
    /* "MOVE HERE" -- Screenshot 2026-10-23 225318.png boxes the title at image y 568-596 and draws
       its destination at y 293-325, in the empty middle of the hero.  The next markup
       (232651.png) moved the caption's other two lines away and left the title exactly there, so the
       drawn box is now the law on its own terms: the title's BOTTOM edge on the hero's mid-line puts
       it at 290.5-318.5 in a 1365x635 window, against the 293-325 he drew.
       The footer is bottom-anchored, so margin-bottom does all the lifting -- 50dvh minus the grid
       margin, which puts the title's bottom edge on the hero's mid-line and holds at 1365, 1440 and
       2560 as measured by scratch/_hero_lines_geom.cjs.  No transform on this box: the card inside it
       already carries one, and the two lines below are measured against that card. */
    margin-bottom: var(--hero-caption-lift);
    /* "FIX LINKS" -- Capture.PNG, 2026-10-24 13:58, an arrow from those two words to "View project ->"
       and "Details".  Both were painted and pointed at the right page but neither could be clicked:
       the controls block above is `position:absolute; left:0; right:0`, a transparent strip the whole
       width of the band, and it is the container's LAST child, so it painted over the caption's links
       line, which closes on the same floor.  Hit-testing the deployed page at 1600x1000 returned
       DIV.hero-meta-controls at the centre of both links.  A flex item takes z-index without becoming
       positioned, so this lifts the caption's column over the strip and moves nothing: the strip's own
       children -- counter and bars at x 24-270, socials at 973-1229, credit at 1473-1576 -- are all
       outside the caption's x 470-619, so no click the block needed is lost. */
    z-index: 1;
  }

  /* The caption's other two lines, moved down into the controls block's band by the owner's markup of
     23:26 ("move text line 1 and 2 down per the arrows") and then dropped one row by his markup of
     00:17 ("MOVE ONE LINE DOWN").

     They resolve against the active .caption-card, not against the footer container: that card keeps
     `transform: translateY(0)` from its entrance animation, and a non-none transform makes an element
     the containing block for its absolutely positioned descendants even when it is itself position:
     static.  Measured, not assumed -- scratch/_hero_lines_geom.cjs prints the card's computed transform
     and shows these two bottoms landing on the card's edge.  The card is the better anchor because it
     is already where the caption is: its left edge is the RDVSchool column and its bottom edge is the
     hero's mid-line, so `left: 0` stands the category, the title and the links on one vertical line by
     construction, and the band is reached by the same 50dvh - grid-margin the caption was lifted by.
     Should that transform ever be removed the anchor silently moves to the container, ~300px lower;
     scratch/_hero_band_probe.cjs asserts the transform and the two bottoms together so it cannot move
     quietly.

     max-content is not decoration: an absolutely positioned box sizes to what the containing block has
     left, and the card is only as wide as the title -- 45.9px at 1365, which is what wrapped the
     category line into four.  These lines are one line each, whatever the title happens to be.

     Bottom edges, from the band's floor: the category line closes on the hairline bars at 33px --
     17px of social row + 16px gap + the 1px hairline, which measures 32.8px of ink because the social
     row's line box is 16.8px.  It sat at 50px, on the counter's row, until the markup of 00:17 boxed
     it and drew an arrow one row down ("MOVE ONE LINE DOWN"); the counter's row held alone until the
     markup of 2026-10-27 lifted the counter off it inline with this line (see the transform rule
     above).  The links line closed on the social row at 0 and the category→links gap was 16px, both
     until the fifteenth markup's blue box sank the strip 8.4px -- the links line now closes at
     −8.4px and the gap measures 24.4px. */
  .project-category,
  .project-links {
    position: absolute;
    left: 0;
    width: max-content;
    margin: 0;
  }

  .project-category {
    bottom: calc(33px - var(--hero-caption-lift));
  }

  .project-links {
    /* The band's bottom line -- links, socials, credit -- sits MIDWAY THROUGH THE BAND ITSELF: the gap
       from the band's top edge down to this line's top edge equals the gap from the line's bottom edge
       down to the band's bottom edge (owner, 2026-11-05, correcting the reading of their drawing: "the
       text should be centered vertically through the midpoint of the height of the text and the black
       band that serves as its background's midpoint point through its height, so that the space above
       the text and the top edge of the band is the same as the space between the bottom of the text and
       the edge of the bottom of the band").  The two references are the band's own edges, NOT the
       category line above and the hero's bottom edge below -- which is what the earlier 3.9px sink
       solved for and why it looked wrong: the band is `.hero-footer-container::before`, 40px tall
       (--hero-strip-height) with its bottom edge on the viewport floor, while this line's box is 16.8px,
       so both gaps are 11.6px when the box bottom sits 11.6px above the floor.  The floor the rule is
       written against is 24px (--grid-margin) above the viewport bottom, hence the 12.4px sink.
       Constant at every window height, because both the band and the line are pinned to the floor.
       Nothing clips it: neither .hero-footer nor its container carries overflow.  Re-pinned in
       scratch/_hero_band_probe.cjs. */
    bottom: calc(-12.4px - var(--hero-caption-lift));
  }

  /* The title's 6px bottom margin is dead space now that the links line is placed by the band, and
     it sits between the title and the hero's mid-line -- which is the line this rule is measured to. */
  .project-title {
    margin-bottom: 0;
  }

  /* Out of the block's column and onto the band's floor, under the header's Work label.  The row was
     the block's third line; the markup of 01:01 boxed it and ran an arrow right to a line drawn
     straight down from that label, and boxed the counter's row and the bars' row together with an
     arrow one row down -- which is what happens here for free: with the socials out of the flow the
     block is only its two rows, and it is bottom-anchored, so the bars land on the floor and the
     counter on the category line. */
  .hero-social-links {
    position: absolute;
    /* The bottom line's 12.4px sink, same as .project-links above. */
    bottom: -12.4px;
    left: calc(100% - var(--hero-social-inset)
               - max(0px, (100% - var(--hero-social-cap)) / 2));
  }

  .hero-credit {
    position: absolute;
    right: 0;
    /* The bottom line's 12.4px sink, same as .project-links above. */
    bottom: -12.4px;
  }
}

/* ==========================================================================
   Slide-Over Specifications Drawer
   ========================================================================== */
.spec-drawer {
  position: fixed;
  top: 0;
  right: 0;
  width: min(440px, 90vw);
  height: 100vh;
  height: 100dvh;
  background: var(--drawer-bg);
  border-left: 1px solid var(--border-color);
  z-index: 100;
  padding: 32px var(--grid-margin);
  display: flex;
  flex-direction: column;
  justify-content: space-between;
  transform: translateX(100%);
  transition: transform 0.3s cubic-bezier(0.16, 1, 0.3, 1), background-color var(--transition-speed) var(--transition-ease);
}

.spec-drawer.open {
  transform: translateX(0);
}

.drawer-backdrop {
  position: fixed;
  inset: 0;
  background: var(--spec-backdrop);
  backdrop-filter: blur(4px);
  z-index: 99;
  opacity: 0;
  pointer-events: none;
  transition: opacity 0.3s ease;
}

.drawer-backdrop.open {
  opacity: 1;
  pointer-events: auto;
}

.drawer-header {
  display: flex;
  align-items: center;
  justify-content: space-between;
  margin-bottom: 32px;
  padding-bottom: 16px;
  border-bottom: 1px solid var(--border-hairline);
}

.drawer-tag {
  font-size: 0.875rem;
  color: var(--text-secondary);
}

.drawer-close-btn {
  font-size: 0.875rem;
  color: var(--text-secondary);
}

.drawer-close-btn:hover {
  color: var(--foreground);
}

.drawer-content {
  flex: 1;
  overflow-y: auto;
}

.drawer-project-name {
  font-size: 1.25rem;
  font-weight: var(--font-weight-normal);
  line-height: var(--line-height-heading);
  color: var(--foreground);
  margin-bottom: 24px;
}

.spec-list {
  display: flex;
  flex-direction: column;
  gap: 18px;
}

.spec-row {
  display: flex;
  flex-direction: column;
  gap: 3px;
}

.spec-label {
  font-size: 0.8125rem;
  color: var(--text-secondary);
}

.spec-value {
  font-size: 0.9375rem;
  color: var(--foreground);
}

.spec-disciplines {
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  margin-top: 6px;
}

.spec-discipline-item {
  font-size: 0.8125rem;
  color: var(--text-secondary);
  border: 1px solid var(--border-hairline);
  padding: 3px 8px;
}

/* ==========================================================================
   Subpage Standard Layout (Minimalissimo Mirror)
   ========================================================================== */
.page-container {
  max-width: var(--max-width);
  margin: 0 auto;
  padding: calc(var(--header-height) + 36px) var(--grid-margin) 80px var(--grid-margin);
}

.page-header {
  margin-bottom: 40px;
  display: flex;
  flex-direction: column;
  gap: 12px;
}

.page-header:has(+ .work-toolbar) {
  margin-bottom: 24px;
}

.page-title {
  font-size: clamp(1.5rem, 3vw, 2.25rem);
  font-weight: var(--font-weight-normal);
  line-height: var(--line-height-heading);
  color: var(--foreground);
}

.page-subtitle {
  font-size: 1rem;
  line-height: var(--line-height-base);
  color: var(--text-secondary);
  max-width: 680px;
}

/* Minimalist Sticky Filter & Sort Toolbar for Work */
.work-toolbar {
  position: sticky;
  top: var(--header-height);
  z-index: 40;
  display: flex;
  align-items: center;
  justify-content: space-between;
  flex-wrap: wrap;
  gap: 12px 24px;
  background: var(--header-bg);
  backdrop-filter: blur(16px);
  -webkit-backdrop-filter: blur(16px);
  margin-left: calc(-1 * var(--grid-margin));
  margin-right: calc(-1 * var(--grid-margin));
  padding-left: var(--grid-margin);
  padding-right: var(--grid-margin);
  padding-top: 12px;
  padding-bottom: 12px;
  margin-top: 0;
  margin-bottom: 32px;
  border-bottom: 1px solid var(--border-hairline);
  transition: background-color var(--transition-speed) var(--transition-ease), border-color var(--transition-speed) var(--transition-ease);
}

.filter-nav {
  display: flex;
  align-items: center;
  gap: 10px 18px;
  flex-wrap: wrap;
}

.toolbar-label {
  font-size: 0.75rem;
  color: var(--text-secondary);
    letter-spacing: 0.06em;
  margin-right: 2px;
  flex-shrink: 0;
}

.filter-btn {
  font-size: 0.875rem;
  color: var(--text-secondary);
  background: none;
  border: none;
  cursor: pointer;
  padding: 0;
  white-space: nowrap;
  flex-shrink: 0;
  transition: color var(--transition-speed) var(--transition-ease);
}

.filter-btn:hover,
.filter-btn.active {
  color: var(--foreground);
}

/* Service groups — the parent button is both the filter and the disclosure toggle */
.filter-group {
  position: relative;
  display: inline-flex;
}

.filter-group-btn.group-active {
  color: var(--foreground);
}

.filter-caret {
  display: inline-block;
  margin-left: 6px;
  border-left: 3.5px solid transparent;
  border-right: 3.5px solid transparent;
  border-top: 4px solid currentColor;
  opacity: 0.55;
  vertical-align: 2px;
  transition: transform var(--transition-speed) var(--transition-ease);
}

.filter-group.open .filter-caret {
  transform: rotate(180deg);
}

.filter-dropdown {
  position: absolute;
  top: calc(100% + 14px);
  left: 0;
  z-index: 50;
  display: flex;
  flex-direction: column;
  align-items: flex-start;
  gap: 11px;
  min-width: 232px;
  padding: 18px;
  background: var(--surface-subtle);
  border: 1px solid var(--border-hairline);
  border-radius: 10px;
  opacity: 0;
  visibility: hidden;
  transform: translateY(-6px);
  transition: opacity var(--transition-speed) var(--transition-ease),
              transform var(--transition-speed) var(--transition-ease),
              visibility var(--transition-speed) var(--transition-ease);
}

.filter-group.open .filter-dropdown {
  opacity: 1;
  visibility: visible;
  transform: translateY(0);
}

.filter-subbtn {
  text-align: left;
  font-size: 0.82rem;
}

/* Sort Controls */
.sort-nav {
  display: flex;
  align-items: center;
  gap: 14px;
  flex-wrap: wrap;
  margin-left: auto;
  flex-shrink: 0;
}

.sort-group {
  display: flex;
  align-items: center;
  gap: 16px;
  flex-shrink: 0;
}

.sort-btn {
  font-size: 0.875rem;
  color: var(--text-secondary);
  background: none;
  border: none;
  cursor: pointer;
  padding: 0;
  display: inline-flex;
  align-items: center;
  gap: 4px;
  white-space: nowrap;
  flex-shrink: 0;
  transition: color var(--transition-speed) var(--transition-ease);
}

.sort-btn:hover,
.sort-btn.active {
  color: var(--foreground);
}

.sort-indicator {
  font-size: 0.6875rem;
  opacity: 0.7;
}

/* Responsive Minimal Grid: 1 col on mobile phones, 2 cols on tablet/phablet, 3 on desktop, 4 on wide */
.minimal-grid {
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: 28px var(--grid-gutter);
  align-items: start;
  width: 100%;
}

@media (max-width: 560px) {
  .minimal-grid {
    grid-template-columns: 1fr;
    gap: 32px var(--grid-gutter);
  }
}

@media (min-width: 768px) {
  .minimal-grid {
    grid-template-columns: repeat(3, minmax(0, 1fr));
    gap: 32px var(--grid-gutter);
  }
}

@media (min-width: 1200px) {
  .minimal-grid {
    grid-template-columns: repeat(4, minmax(0, 1fr));
    gap: 40px var(--grid-gutter);
  }
}

/* Varied-size work tiles. The grid script draws each card into one of four tiers on every
   load, and dense flow backfills the holes the larger tiers leave. Width is measured in grid
   columns against a single-column card, so the smallest tile is about a sixth of a feature
   tile's area and the page reads as an editorial layout rather than a stamp sheet. Tiering
   only means something from 768px up — below that a fraction of one column is just a shrunken
   card — so phones and narrow tablets keep the uniform grid.
   #projectGrid holds both layouts the work page renders: year rows and the flat All view. */
@media (min-width: 768px) {
  #projectGrid .minimal-grid {
    grid-auto-flow: row dense;
  }

  /* Centred rather than flush left: the gap the card leaves belongs to the layout, not to
     a missing image. */
  #projectGrid .grid-card.tile-small {
    width: 68%;
    margin-inline: auto;
  }

  #projectGrid .grid-card.tile-wide {
    grid-column: span 2;
  }

  #projectGrid .grid-card.tile-feature {
    grid-column: span 2;
  }
}

/* Four columns is the only width where three columns of artwork still leaves a neighbour
   beside it; at three columns a feature would be a full-bleed banner. */
@media (min-width: 1200px) {
  #projectGrid .grid-card.tile-feature {
    grid-column: span 3;
  }
}

/* Project / Article Card */
.grid-card {
  display: block;
  min-width: 0;
  width: 100%;
  transition: opacity 0.25s ease;
}

.grid-card:hover {
  opacity: 0.85;
}

.card-media-wrapper {
  position: relative;
  width: 100%;
  overflow: hidden;
  background-color: var(--surface-subtle);
  margin-bottom: 12px;
}

.card-media-wrapper picture {
  display: block;
  width: 100%;
}

.card-img {
  width: 100%;
  height: auto;
  max-width: 100%;
  display: block;
  transition: transform 0.5s ease;
}

.grid-card:hover .card-img {
  transform: scale(1.02);
}

.card-meta {
  display: flex;
  flex-direction: column;
  gap: 4px;
  min-width: 0;
  width: 100%;
}

.card-meta-main {
  display: flex;
  align-items: baseline;
  justify-content: space-between;
  gap: 12px;
  min-width: 0;
  width: 100%;
}

.card-title {
  font-size: 0.9375rem;
  font-weight: var(--font-weight-normal);
  line-height: var(--line-height-base);
  color: var(--foreground);
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
  min-width: 0;
  flex: 1;
}

.card-year {
  font-size: 0.8125rem;
  color: var(--text-secondary);
  flex-shrink: 0;
  font-feature-settings: "tnum";
}

.card-meta-sub {
  display: flex;
  align-items: center;
  gap: 6px;
  font-size: 0.8125rem;
  color: var(--text-secondary);
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
  min-width: 0;
}

.meta-sep {
  /* Was var(--border-hairline) -- a 8%-alpha border token used as TEXT ink.  Composited it paints
     rgb(20,20,20) on the dark page and rgb(235,235,235) on the light one: 1.14:1 and 1.20:1, measured by
     scratch/_theme_contrast.cjs over all 233 pages on 2026-11-03.  A separator is still a word-sized
     mark a visitor has to resolve, so it gets the quiet INK, not the quiet BORDER. */
  color: var(--text-quiet);
}

.card-category {
  font-size: 0.8125rem;
  color: var(--text-secondary);
  flex-shrink: 0;
}

/* ==========================================================================
   Editorial Content Layout (About / Expertise / News Article)
   ========================================================================== */
.editorial-grid {
  display: grid;
  grid-template-columns: 1fr;
  gap: 48px;
}

@media (min-width: 900px) {
  .editorial-grid {
    grid-template-columns: 1.2fr 1fr;
    align-items: start;
    gap: 64px;
  }
}

.editorial-text {
  display: flex;
  flex-direction: column;
  gap: 24px;
}

.editorial-lead {
  font-size: 1.25rem;
  line-height: 1.5;
  color: var(--foreground);
}

.editorial-body {
  font-size: 1rem;
  line-height: 1.6;
  color: var(--text-secondary);
}

.editorial-body p {
  margin-bottom: 16px;
}

.editorial-media {
  width: 100%;
}

.editorial-img {
  width: 100%;
  aspect-ratio: 4/3;
  object-fit: cover;
}

/* The caption under the about page's editorial plate. Its project name is a link, and the owner
   wants it treated like a navigation link (2026-10-31): no underline, the same inherited colour
   as the sentence around it, warming to the foreground on hover/focus -- exactly `.nav-link`'s
   treatment. The global `a` rule already supplies `color: inherit`, no decoration and the colour
   transition, so only the hover step is declared here. */
.about-media-credit a:hover,
.about-media-credit a:focus-visible {
  color: var(--foreground);
}

/* Expertise List */
.expertise-list {
  display: flex;
  flex-direction: column;
  gap: 36px;
}

.expertise-row {
  display: grid;
  grid-template-columns: 1fr;
  gap: 16px;
  padding-bottom: 32px;
  border-bottom: 1px solid var(--border-hairline);
}

@media (min-width: 768px) {
  .expertise-row {
    grid-template-columns: 240px 1fr;
    gap: 32px;
  }
}

.expertise-name {
  font-size: 1.15rem;
  font-weight: var(--font-weight-normal);
  color: var(--foreground);
}

.expertise-desc {
  font-size: 1rem;
  line-height: 1.6;
  color: var(--text-secondary);
}

.expertise-link {
  color: var(--foreground);
  transition: color var(--transition-speed) var(--transition-ease);
}

.expertise-link:hover {
  color: var(--text-secondary);
}

.expertise-view-link {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  font-size: 0.875rem;
  color: var(--text-secondary);
  margin-top: 14px;
  transition: color var(--transition-speed) var(--transition-ease);
}

.expertise-view-link:hover {
  color: var(--foreground);
}

/* Design carries its six disciplines as indented sub-rows */
.expertise-subrow {
  margin-top: 22px;
  padding-left: 16px;
  border-left: 1px solid var(--border-hairline);
}

.expertise-subname {
  font-size: 0.9375rem;
  font-weight: 500;
  line-height: 1.4;
  margin-bottom: 6px;
}

.expertise-subrow p {
  font-size: 0.9375rem;
}

.expertise-subservices {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 6px 8px;
  margin-top: 12px;
  font-size: 0.8125rem;
  line-height: 1.5;
  color: var(--text-secondary);
}

.subservice-label {
  font-weight: 500;
  color: var(--foreground);
    letter-spacing: 0.05em;
  font-size: 0.75rem;
  margin-right: 4px;
}

.subservice-item {
  color: var(--text-secondary);
}

a.subservice-item {
  text-decoration: none;
  transition: color var(--transition-speed) var(--transition-ease);
}

a.subservice-item:hover {
  color: var(--foreground);
  text-decoration: underline;
}

.subservice-sep {
  /* Same correction as .meta-sep: this is the same "/" drawn in a border token (1.14:1 dark, 1.20:1
     light).  The expertise page draws one per service pair, so 8 of the site's 625 AA failures were
     these marks alone. */
  color: var(--text-quiet);
  user-select: none;
}

/* Contact Form */
.contact-grid {
  display: grid;
  grid-template-columns: 1fr;
  gap: 48px;
}

@media (min-width: 900px) {
  .contact-grid {
    grid-template-columns: 1fr 1fr;
    gap: 64px;
  }
}

.contact-form {
  display: flex;
  flex-direction: column;
  gap: 20px;
}

.form-group {
  display: flex;
  flex-direction: column;
  gap: 6px;
}

.form-label {
  font-size: 0.8125rem;
  color: var(--text-secondary);
}

.form-input, .form-textarea, .form-select {
  background: var(--input-bg);
  border: 1px solid var(--border-hairline);
  padding: 10px 14px;
  color: var(--foreground);
  font-size: 0.9375rem;
  border-radius: 2px;
  outline: none;
  transition: border-color var(--transition-speed) var(--transition-ease), background-color var(--transition-speed) var(--transition-ease);
}

.form-input:focus, .form-textarea:focus, .form-select:focus {
  border-color: var(--text-secondary);
}

/* The Area of Interest dropdown is the only control whose POPUP this sheet does not paint.
   The rule above fills it with a 3%-white TINT, which is transparent by design: the closed control
   reads on the page's own black, but every <option> row inherits `color: #fff` with NO background of
   its own, so wherever the OS draws a light sheet behind those rows (Firefox on Windows, an Android
   picker, a light-mode popup) the menu is white on white. Give the control the OPAQUE colour that tint
   composites to, and repeat it on the rows and the group labels, so the menu is the same black panel
   with hairline separators in either theme. `--input-bg-solid` is that exact colour (#080808 on black,
   #f7f7f7 on white), so the closed control does not move a pixel on the page.
   The unselected state is a placeholder -- "Choose an area of interest" -- so it takes the secondary
   ink the field labels use instead of reading as an answered field; it turns white/black the moment a
   real area is picked. */
.form-select {
  background-color: var(--input-bg-solid);
}

.form-select option,
.form-select optgroup {
  background-color: var(--input-bg-solid);
  color: var(--foreground);
}

.form-select optgroup {
  color: var(--text-secondary);
}

.form-select:has(option[value=""]:checked) {
  color: var(--text-secondary);
}

/* Phone legibility for the site's only form (contact.html): the block above sets controls at 0.9375rem,
   which measures 15px, and iOS Safari answers a 15px focusable control by ZOOMING the whole page to the
   caret -- measured at 390x844 as `select 358x43 at 15px` in scratch/_contact_probe.cjs. 16px is the
   threshold the WebKit heuristic uses, so every control the visitor can focus is lifted to exactly that on
   a touch device and on anything narrow enough to be one. Desktop keeps its 15px: the ask was the Contact
   page's facts and dropdown, not a retype of the form. */
@media (max-width: 767px), (pointer: coarse) {
  .form-input, .form-textarea, .form-select, .form-submit-btn {
    font-size: 1rem;
  }
}

.form-textarea {
  min-height: 120px;
  resize: vertical;
}

.form-submit-btn {
  align-self: flex-start;
  padding: 10px 24px;
  border: 1px solid var(--border-color);
  color: var(--foreground);
  font-size: 0.9375rem;
  margin-top: 8px;
  transition: all var(--transition-speed) var(--transition-ease);
}

.form-submit-btn:hover {
  background: var(--foreground);
  color: var(--background);
}

.page-sublinks {
  font-size: 0.875rem;
  color: var(--text-secondary);
  margin-top: 12px;
  display: flex;
  flex-wrap: wrap;
  gap: 8px 12px;
  align-items: center;
}

.page-sublinks a {
  color: var(--text-secondary);
  transition: color var(--transition-speed) var(--transition-ease);
}

.page-sublinks a:hover,
.page-sublinks a:focus-visible {
  color: var(--foreground);
}

.form-row {
  display: grid;
  grid-template-columns: 1fr;
  gap: 16px;
}

@media (min-width: 600px) {
  .form-row {
    grid-template-columns: 1fr 1fr;
  }
}

.first-call-box {
  border: 1px solid var(--border-hairline);
  background: var(--input-bg);
  border-radius: 2px;
  padding: 14px 16px;
  display: flex;
  flex-direction: column;
  gap: 14px;
}

.first-call-toggle {
  display: flex;
  align-items: flex-start;
  gap: 10px;
  cursor: pointer;
  font-size: 0.9375rem;
  color: var(--foreground);
}

.first-call-toggle input[type="checkbox"] {
  margin-top: 4px;
  width: 16px;
  height: 16px;
  accent-color: var(--brand-blue);
  cursor: pointer;
  flex-shrink: 0;
}

.first-call-subnote {
  display: block;
  font-size: 0.8125rem;
  color: var(--text-secondary);
  margin-top: 2px;
}

.first-call-fields {
  display: flex;
  flex-direction: column;
  gap: 14px;
  padding-top: 12px;
  border-top: 1px solid var(--border-hairline);
}

.first-call-fields[hidden] {
  display: none;
}

.contact-direct-actions {
  border: 1px solid var(--border-hairline);
  background: var(--input-bg);
  border-radius: 2px;
  padding: 20px;
}

.contact-direct-actions h2 {
  font-size: 1rem;
  color: var(--foreground);
  margin-bottom: 8px;
}

.contact-direct-actions p {
  font-size: 0.875rem;
  color: var(--text-secondary);
  line-height: 1.55;
  margin-bottom: 14px;
}

.contact-action-links {
  display: flex;
  flex-direction: column;
  gap: 8px;
  font-size: 0.9375rem;
}

.contact-action-links a {
  color: var(--brand-blue);
  align-self: flex-start;
}

.contact-action-links a:hover,
.contact-action-links a:focus-visible {
  color: var(--brand-blue-hover);
  text-decoration: underline;
}

/* Preserve flex/grid/aspect layout when <img> is wrapped in <picture> (hero .slide-picture excluded) */
.card-media-wrapper picture,
.project-hero-media picture,
.gallery-item picture,
.project-nav-thumb picture,
.editorial-media picture {
  display: contents;
}

/* ==========================================================================
   Individual Project Page Layout (Minimalissimo Architecture)
   Product pages use the project detail layout, so they share these rules.
   ========================================================================== */
.project-detail-container {
  max-width: var(--max-width);
  margin: 0 auto;
  padding: calc(var(--header-height) + 32px) var(--grid-margin) 96px var(--grid-margin);
}

.project-back-link {
  display: inline-flex;
  align-items: center;
  gap: 8px;
  font-size: 0.875rem;
  color: var(--text-secondary);
  margin-bottom: 28px;
}

.project-back-link:hover {
  color: var(--foreground);
}

.project-hero-header {
  margin-bottom: 36px;
  display: flex;
  flex-direction: column;
  gap: 8px;
}

.project-meta-line {
  font-size: 0.9375rem;
  color: var(--text-secondary);
}

/* One title class. .product-page-title existed only to keep the seven in-house MIG pages out
   of the harness census, which read .project-page-title as "this is a studio work, so work.html
   must card it". The owner moved the MIG pieces onto work.html on 2026-10-21, so the split is
   gone -- and a page that is carded is allowed to say it is a work. */
.project-page-title {
  font-size: clamp(1.75rem, 3.5vw, 2.75rem);
  font-weight: var(--font-weight-normal);
  line-height: var(--line-height-heading);
  color: var(--foreground);
  margin-top: 4px;
}

/* Project Hero Media — Fills the entire space designated for the header image */
.project-hero-media {
  width: 100%;
  aspect-ratio: 16/10;
  max-height: 78vh;
  overflow: hidden;
  background-color: var(--surface-subtle);
  margin-bottom: 48px;
  position: relative;
}

.project-hero-img {
  width: 100%;
  height: 100%;
  object-fit: cover;
  object-position: center;
  display: block;
  cursor: default;
}

/* For sheets whose content is stacked from the top (brand blocks, title blocks,
   credit lines): the 16/10 cover crop would otherwise shave the first of them. */
.project-hero-media.hero-fit-top .project-hero-img {
  object-position: center top;
}

/* Product heroes are the plates themselves, not crops made for a header: a piece
   that is square or tall would lose its top and bottom to the 16/10 cover, so it
   keeps its own ratio and is letterboxed inside the panel instead. */
.project-hero-media.hero-fit-natural {
  aspect-ratio: auto;
  max-height: none;
}

.project-hero-media.hero-fit-natural .project-hero-img {
  width: auto;
  height: auto;
  max-width: 100%;
  max-height: 78vh;
  margin: 0 auto;
  display: block;
}

/* Project Hero Video Support */
.project-hero-media.has-video,
.project-hero-media:has(.project-hero-video) {
  aspect-ratio: 16/9;
  background-color: #000;
}

.project-hero-video {
  width: 100%;
  height: 100%;
  object-fit: contain;
  background-color: #000;
  display: block;
}

/* A header panel that declares its own ratio wraps the media it holds: the film or the plate spans the
   whole width of the header space, scaled proportionally, with nothing cut. The ratio is written onto the
   panel from the file's own measured size (scratch/_hero_fit.py owns the rule, scratch/_apply_hero_fit.py
   writes `style="aspect-ratio: W/H"`), and this class exists to lift the 78vh clamp -- a clamp shorter than
   the media's own height would send the crop straight back, which is the whole thing being avoided.
   `.project-hero-media` is otherwise a fixed 16/10 box (16/9 when it holds a film) with `object-fit: cover`,
   which crops every plate wider than 16/10 at the sides and letterboxes any film that is not exactly 16/9.
   This rule sits AFTER the film block above on purpose: `.project-hero-media.has-video` is also two classes,
   so at equal specificity it is source order that decides. Guarded by scratch/_hero_fit_contract.py. */
.project-hero-media.hero-fit-wide {
  max-height: none;
}

/* Gallery Section Headings & Storyboard Dividers */
.gallery-section-divider {
  grid-column: 1 / -1;
  margin-top: 40px;
  margin-bottom: 8px;
  padding-bottom: 12px;
  border-bottom: 1px solid var(--border-hairline);
}

/* Gallery sub-headings render in the case they are written in the page markup
   ("Approach + Dressing", "Bar + Lounge") with no forced capitals. */
.gallery-section-title {
  font-size: 1.125rem;
  font-weight: 500;
  letter-spacing: 0.05em;
  color: var(--foreground);
}

.gallery-section-subtitle {
  font-size: 0.875rem;
  color: var(--text-secondary);
  margin-top: 4px;
}

.gallery-item-full {
  grid-column: 1 / -1;
}

.project-content-grid {
  display: grid;
  grid-template-columns: 1fr;
  gap: 48px;
  margin-bottom: 64px;
}

@media (min-width: 900px) {
  .project-content-grid {
    grid-template-columns: 1.4fr 1fr;
    gap: 72px;
  }
}

.project-story {
  display: flex;
  flex-direction: column;
  gap: 20px;
}

.project-lead-text {
  font-size: 1.2rem;
  line-height: 1.5;
  color: var(--foreground);
}

.project-body-text {
  font-size: 1rem;
  line-height: 1.6;
  color: var(--text-secondary);
}

.project-body-text p {
  margin-bottom: 16px;
}

.project-body-text a {
  text-decoration: underline;
  text-underline-offset: 2px;
}

.project-specs-panel {
  border-top: 1px solid var(--border-hairline);
  padding-top: 24px;
}

@media (min-width: 900px) {
  .project-specs-panel {
    border-top: none;
    border-left: 1px solid var(--border-hairline);
    padding-top: 0;
    padding-left: 48px;
  }
}

.project-specs-grid {
  display: flex;
  flex-direction: column;
  gap: 20px;
}

.project-spec-item {
  display: flex;
  flex-direction: column;
  gap: 4px;
}

.project-spec-label {
  font-size: 0.8125rem;
  color: var(--text-secondary);
}

.project-spec-val {
  font-size: 0.9375rem;
  color: var(--foreground);
}


/* A credited partner whose name links out, in a project's specification panel. The owner asked for
   it to be treated like the navigation links (2026-11-01, NPA's Interior Design row), and what that
   treatment is, measured off `.nav-link` itself, is two steps of colour and no underline:
   --text-secondary at rest, --foreground on hover/focus. The global anchor rule already carries
   `color: inherit`, `text-decoration: none` and the colour transition, so only the two colour steps
   are declared here. Scoped to a class rather than to every anchor inside a specification value, so
   the two bare credit links dyv.html already carries keep the colour they have. */
.project-spec-credit {
  color: var(--text-secondary);
}

.project-spec-credit:hover,
.project-spec-credit:focus-visible {
  color: var(--foreground);
}

/* Service tags — one link per service the project is tagged under on work.html */
.project-services {
  display: flex;
  flex-wrap: wrap;
  align-items: baseline;
  gap: 6px;
}

.project-service {
  color: var(--foreground);
  text-decoration: none;
  border-bottom: 1px solid var(--border-hairline);
  padding-bottom: 1px;
  transition: border-color var(--transition-speed) var(--transition-ease);
}

.project-service:hover {
  border-bottom-color: var(--foreground);
}

.project-service-sep {
  /* The separator in a project page's Services row -- 132 pages carry it, and at 388 measured rows it is
     the largest single group of the site's AA failures.  It was --text-secondary painted at 55% opacity,
     which composites to rgb(75,75,75) on the dark page (2.40:1) and rgb(171,171,171) on the light one
     (2.30:1): the same quiet colour in both themes, because an opacity multiply pulls a light ink DOWN
     and a dark ink UP and lands both of them in the middle, where nothing is legible.  The token gives
     each theme its own quiet ink and clears 4.5 on both of its grounds. */
  color: var(--text-quiet);
}

/* Gallery Grid — Uncropped & Natural Proportions */
.project-gallery-grid {
  display: grid;
  grid-template-columns: 1fr;
  gap: 32px;
  margin-bottom: 64px;
}

@media (min-width: 768px) {
  .project-gallery-grid {
    grid-template-columns: repeat(2, 1fr);
    align-items: start;
  }
}

.gallery-item {
  width: 100%;
  background-color: var(--surface-subtle);
  border: 1px solid var(--border-hairline);
  display: flex;
  justify-content: center;
  align-items: center;
  position: relative;   /* anchors .lightbox-film-expand */
}

.gallery-img {
  width: 100%;
  height: auto;
  object-fit: contain;
  display: block;
  cursor: zoom-in;
  transition: opacity var(--transition-speed) var(--transition-ease);
}

.gallery-img:hover {
  opacity: 0.96;
}

.gallery-video,
.gallery-item video {
  width: 100%;
  height: auto;
  display: block;
}

/* js/lightbox.js adds an expand affordance to every gallery film so it can join the fullscreen
   deck without stealing the click-to-play gesture from the player's own controls. */
.lightbox-film-expand {
  position: absolute;
  top: 10px;
  right: 10px;
  width: 34px;
  height: 34px;
  display: flex;
  align-items: center;
  justify-content: center;
  color: var(--text-secondary);
  background: var(--input-bg);
  border: 1px solid var(--border-hairline);
  border-radius: 50%;
  cursor: pointer;
  opacity: 0.72;
  transition: opacity var(--transition-speed) var(--transition-ease), color var(--transition-speed) var(--transition-ease), border-color var(--transition-speed) var(--transition-ease);
}

.lightbox-film-expand:hover,
.lightbox-film-expand:focus-visible {
  opacity: 1;
  color: var(--foreground);
  border-color: var(--foreground);
}

.lightbox-film-expand svg {
  width: 15px;
  height: 15px;
}

/* Gallery items that contain a video stack vertically so any caption
   header sits above the player instead of beside it */
.gallery-item:has(video) {
  flex-direction: column;
  align-items: stretch;
}

/* ==========================================================================
   Desktop detail-image sizing — nothing below the project facts runs the full
   page width. Half the container is the ceiling, and every frame keeps its own
   proportions: media is sized by width:auto plus a height ceiling, so a tall
   portrait reaches the height limit first and ends up narrower than a wide
   landscape frame rather than being stretched or cropped to fit a column.
   Phones and tablets keep the existing full-width / two-up behaviour.
   ========================================================================== */
@media (min-width: 1024px) {
  .project-gallery-grid {
    display: flex;
    flex-wrap: wrap;
    align-items: flex-start;
    gap: 32px;
  }

  /* A section heading still breaks the run of images across the full measure. */
  .gallery-section-divider {
    flex: 0 0 100%;
    width: 100%;
  }

  .gallery-item,
  .gallery-item-full {
    flex: 0 1 auto;
    width: auto;
    max-width: calc(50% - 16px);
  }

  .gallery-img,
  .gallery-video,
  .gallery-item video {
    width: auto;
    max-width: 100%;
    max-height: 78vh;
    height: auto;
  }

  /* A video item carries its own caption, so its box keeps a measured width
     instead of shrink-wrapping to the player. */
  .gallery-item:has(video) {
    width: calc(50% - 16px);
    align-items: stretch;
  }

  .gallery-item:has(video) video,
  .gallery-item:has(video) .gallery-video {
    width: 100%;
  }
}

/* ==========================================================================
   Minimalist Lightbox (Fullscreen Uncropped Viewer)
   ========================================================================== */
.minimal-lightbox {
  position: fixed;
  inset: 0;
  z-index: 9999;
  background-color: var(--lightbox-bg);
  backdrop-filter: blur(20px);
  -webkit-backdrop-filter: blur(20px);
  display: flex;
  flex-direction: column;
  justify-content: space-between;
  opacity: 0;
  visibility: hidden;
  transition: opacity 0.25s ease, visibility 0.25s ease, background-color var(--transition-speed) var(--transition-ease);
  padding: 24px var(--grid-margin);
}

.minimal-lightbox.open {
  opacity: 1;
  visibility: visible;
}

.lightbox-header {
  display: flex;
  align-items: center;
  justify-content: space-between;
  width: 100%;
  max-width: var(--max-width);
  margin: 0 auto;
  z-index: 10;
}

.lightbox-meta {
  display: flex;
  align-items: center;
  gap: 12px;
  font-size: 0.875rem;
  color: var(--text-secondary);
}

.lightbox-counter {
  font-variant-numeric: tabular-nums;
  color: var(--foreground);
}

.lightbox-title {
  color: var(--text-secondary);
}

.lightbox-close-btn {
  font-size: 0.875rem;
  color: var(--text-secondary);
  background: none;
  border: 1px solid var(--border-hairline);
  cursor: pointer;
  padding: 6px 14px;
  border-radius: 3px;
  transition: color var(--transition-speed) var(--transition-ease), border-color var(--transition-speed) var(--transition-ease);
}

.lightbox-close-btn:hover {
  color: var(--foreground);
  border-color: var(--foreground);
}

.lightbox-stage {
  flex: 1;
  display: flex;
  align-items: center;
  justify-content: space-between;
  position: relative;
  width: 100%;
  max-width: var(--max-width);
  margin: 0 auto;
  gap: 16px;
  overflow: hidden;
  padding: 16px 0;
}

.lightbox-media-container {
  flex: 1;
  height: 100%;
  display: flex;
  align-items: center;
  justify-content: center;
  cursor: zoom-out;
}

.lightbox-active-img {
  max-width: 90vw;
  max-height: 75vh;
  width: auto;
  height: auto;
  object-fit: contain;
  display: block;
  user-select: none;
  -webkit-user-drag: none;
  transition: transform 0.2s ease, opacity 0.2s ease;
}

/* A gallery film opens in the same stage as a still, so it inherits the same containment.
   The script flips display, so the player is only ever laid out while it is the live slide. */
.lightbox-active-video {
  max-width: 90vw;
  max-height: 75vh;
  width: auto;
  height: auto;
  object-fit: contain;
  display: none;
  background: #000;
  border-radius: 4px;
  cursor: default;
  transition: opacity 0.2s ease;
}

.lightbox-arrow {
  width: 44px;
  height: 44px;
  display: flex;
  align-items: center;
  justify-content: center;
  color: var(--text-secondary);
  background: var(--input-bg);
  border: 1px solid var(--border-hairline);
  border-radius: 50%;
  cursor: pointer;
  z-index: 10;
  flex-shrink: 0;
  transition: color var(--transition-speed) var(--transition-ease), border-color var(--transition-speed) var(--transition-ease), background-color var(--transition-speed) var(--transition-ease);
}

.lightbox-arrow:hover {
  color: var(--foreground);
  border-color: var(--foreground);
  background: var(--hover-bg);
}

.lightbox-arrow svg {
  width: 20px;
  height: 20px;
}

.lightbox-footer {
  width: 100%;
  max-width: var(--max-width);
  margin: 0 auto;
  display: flex;
  align-items: center;
  justify-content: space-between;
  font-size: 0.8125rem;
  color: var(--text-secondary);
  padding-top: 14px;
  border-top: 1px solid var(--border-hairline);
  z-index: 10;
}

.lightbox-caption-text {
  color: var(--foreground);
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
}

.lightbox-hint {
  font-size: 0.75rem;
  /* A render-time audit cannot walk an overlay that is display:none until a visitor opens it, so this
     one was read off the rule instead of off the screen: it was --text-secondary at 60% opacity, which
     on the light theme's near-white --lightbox-bg is rgb(166,166,166) on rgb(250,250,250) -- about
     2.1:1.  The quiet INK token, which is AA on both themes' grounds, replaces the dimmer. */
  color: var(--text-quiet);
}

@media (max-width: 768px) {
  .minimal-lightbox {
    padding: 16px var(--grid-margin);
  }

  .lightbox-stage {
    position: relative;
    padding: 8px 0;
  }

  .lightbox-arrow {
    position: absolute;
    top: 50%;
    transform: translateY(-50%);
    width: 38px;
    height: 38px;
    background: rgba(0, 0, 0, 0.65);
    border: 1px solid rgba(255, 255, 255, 0.25);
    backdrop-filter: blur(8px);
    -webkit-backdrop-filter: blur(8px);
    z-index: 25;
  }

  .lightbox-arrow.prev {
    left: 4px;
  }

  .lightbox-arrow.next {
    right: 4px;
  }

  .lightbox-hint {
    display: none;
  }

  .lightbox-media-container {
    width: 100%;
  }

  .lightbox-active-img {
    max-width: 100%;
    max-height: 72vh;
  }

  .lightbox-active-video {
    max-width: 100%;
    max-height: 72vh;
  }
}

/* One pager class for every work, live or archived. .product-nav-footer used to chain the seven
   MIG pages to each other instead of into the work walk; they joined the live service rings on
   2026-10-21, so their separate class went with product.html. */
.project-nav-footer {
  display: flex;
  align-items: center;
  justify-content: space-between;
  padding: 32px 0;
  border-top: 1px solid var(--border-hairline);
  border-bottom: 1px solid var(--border-hairline);
  margin-top: 32px;
}

.project-nav-link {
  font-size: 0.9375rem;
  color: var(--text-secondary);
}

.project-nav-link:hover {
  color: var(--foreground);
}

/* Pager thumbnails. Each arrow carries the neighbour's own card thumbnail above its label, so the walk reads
   as "more work in this service" instead of "the next name in the alphabet". The image is decorative (alt="")
   because the label under it already names the project and says which way it goes, and the thumbnail link is
   aria-hidden + tabindex="-1" so the pair is one tab stop and one accessible name, not two. */
.project-nav-item {
  display: flex;
  flex-direction: column;
  gap: 10px;
  max-width: 42%;
  /* min-width:0 is the shrink guard. A flex item's default min-width:auto means "never narrower than the
     content", and the content here is a whole project title, so on a narrow phone the two arrows would rather
     overflow the row than wrap. With it, 42% is a real cap and the label breaks instead. */
  min-width: 0;
}

/* Two thumbs must start at the same height, so the row is top-aligned when it carries them. Scoped through
   :has so the flat archived pagers keep the vertical centring they have always had. */
.project-nav-footer:has(.project-nav-item) {
  align-items: flex-start;
}

.project-nav-item:last-child {
  align-items: flex-end;
  text-align: right;
}

.project-nav-thumb {
  display: block;
  width: 100%;
  max-width: 320px;
  overflow: hidden;
  border: 1px solid var(--border-hairline);
  background-color: var(--surface-subtle);
  transition: border-color 0.25s ease;
}

.project-nav-thumb img {
  display: block;
  width: 100%;
  height: auto;
  transition: transform 0.5s ease;
}

.project-nav-thumb:hover {
  border-color: var(--foreground);
}

.project-nav-thumb:hover img,
.project-nav-item:hover .project-nav-thumb img {
  transform: scale(1.02);
}

/* Project-page conversation CTA (owner, 2026-10-27): the Contact page's inquiry form, offered after
   the prev/next pager so a visitor who has just walked a project can open the same conversation
   without leaving the page. The form fields reuse .contact-form's classes wholesale; only the section
   frame, the number line under the heading and the column cap are new. 640px keeps the measure at the
   Contact page's single-column reading width on desktop and leaves the phone layout untouched. */
.project-cta {
  margin-top: 48px;
  max-width: 640px;
}

.project-cta-heading {
  font-size: 1.125rem;
  font-weight: 500;
  letter-spacing: 0.05em;
  color: var(--foreground);
  margin-bottom: 8px;
}

/* The number line, which the owner's sheet of 2026-10-28 moved from under the heading to UNDER THE
   FORM, so it is the section's last block: read the form, and if you would rather not fill it in,
   here is the way out. Its spacing is now a top margin -- the form has no bottom margin of its own
   (the global reset zeroes every margin, and `.contact-form` spaces its children with `gap`), so
   20px is the same step the form uses between its own fields.
   Site anchors are `color: inherit` with no underline, so inside this secondary-colour
   paragraph a link would read as plain text. The owner's follow-up (2026-10-28) puts the wordmark's own
   blue on it -- the same --brand-blue the header's RDVS is written in, and the same hover pair it
   lifts to -- so the two most actionable words on the page carry the brand's colour. The underline on
   hover stays: blue alone is not an affordance a visitor who has never seen the page can be trusted to
   read. */
.project-cta-intro {
  font-size: 0.9375rem;
  color: var(--text-secondary);
  line-height: 1.6;
  margin-top: 20px;
}

.project-cta-intro a {
  color: var(--brand-blue);
}

.project-cta-intro a:hover {
  color: var(--brand-blue-hover);
  text-decoration: underline;
}

@media (max-width: 640px) {
  .project-nav-item {
    gap: 8px;
  }

  .project-nav-thumb {
    max-width: 168px;
  }
}

/* Base wordmark — the owner's drawn "design . visualize . make", set as lowercase
   SVG type above the footer hairline on every page that carries a footer. The
   thinnest Helvetica with the tightest kerning, centred and stretching edge to
   edge across the page grid at every viewport (textLength pins the line to the
   grid's content width). "Helvetica Neue" resolves to its Thin cut (weight 100)
   where the platform ships one; where it does not (Windows has no thin Helvetica),
   the site's own loaded Geist 100 is the first fallback so the line still sets
   hairline-thin rather than dropping to a regular weight. One word at a time
   takes the brand blue and hands over every minute (180 s cycle).
   The owner's 1.2x drawing (2026-10-31) stretches the line vertically and grows
   it UPWARD: the transform's origin sits on the baseline edge, so the footer and
   the hairline above it do not move and no sibling reflows -- only the glyph box
   gets taller (1872-wide probe: ink 185 -> 222 px, footer still at 265.59).
   transform is a paint of the same geometry, so the 1872 px textLength span that
   pins the line to the grid is untouched. */
.site-tagline {
  display: block;
  width: calc(100% - (var(--grid-margin) * 2));
  max-width: calc(var(--max-width) - (var(--grid-margin) * 2));
  margin: 96px auto 0;
  height: auto;
  overflow: visible;
  font-family: "Helvetica Neue", 'Geist', Helvetica, Arial, sans-serif;
  font-weight: 100;
  font-size: 142px;
  letter-spacing: -0.045em;
  color: var(--foreground);
  text-rendering: geometricPrecision;
  transform: scaleY(1.2);
  transform-origin: 50% 100%;
}

.site-tagline text {
  font: inherit;
  fill: var(--foreground);
}

.site-tagline .st-w {
  animation: st-word-hold 180s linear infinite;
}

.site-tagline .st-w2 {
  animation-delay: -120s;
}

.site-tagline .st-w3 {
  animation-delay: -60s;
}

@keyframes st-word-hold {
  0%, 33.3333% {
    fill: var(--brand-blue);
  }
  33.3334%, 100% {
    fill: var(--foreground);
  }
}

@media (prefers-reduced-motion: reduce) {
  .site-tagline .st-w {
    animation: none;
  }
  .site-tagline .st-w1 {
    fill: var(--brand-blue);
  }
}

.site-tagline + .site-footer {
  margin-top: 0;
}

/* Minimal Footer */
.site-footer {
  border-top: 1px solid var(--border-hairline);
  padding: 32px var(--grid-margin);
  margin-top: 64px;
}

.footer-container {
  max-width: var(--max-width);
  margin: 0 auto;
  display: flex;
  align-items: center;
  justify-content: space-between;
  flex-wrap: wrap;
  gap: 16px;
  font-size: 0.875rem;
  color: var(--text-secondary);
}

.footer-right {
  display: flex;
  align-items: center;
  gap: 28px;
  flex-wrap: wrap;
}

.footer-social-links {
  display: flex;
  align-items: center;
  gap: 16px;
  flex-wrap: wrap;
}

.footer-social-links a {
  font-size: 0.8125rem;
  color: var(--text-secondary);
  text-decoration: none;
  transition: color var(--transition-speed) var(--transition-ease);
  white-space: nowrap;
}

.footer-social-links a:hover,
.footer-social-links a:focus-visible {
  color: var(--foreground);
}

.footer-links {
  display: flex;
  align-items: center;
  gap: 20px;
}

/* ==========================================================================
   Responsive Adaptations
   ========================================================================== */
@media (max-width: 992px) {
  .header-right {
    gap: 14px;
  }

  .primary-nav {
    display: none;
  }
  
  .primary-nav.mobile-active {
    display: flex;
    flex-direction: column;
    position: absolute;
    top: var(--header-height);
    left: 0;
    right: 0;
    background: var(--mobile-nav-bg);
    backdrop-filter: blur(16px);
    -webkit-backdrop-filter: blur(16px);
    border-bottom: 1px solid var(--border-hairline);
    padding: 24px var(--grid-margin);
    gap: 18px;
    align-items: flex-start;
    transition: background-color var(--transition-speed) var(--transition-ease);
  }

  .mobile-toggle {
    display: block;
  }

  .search-input {
    width: 75px;
  }
  .search-input:focus {
    width: 105px;
  }

  .work-toolbar {
    flex-direction: column;
    align-items: stretch;
    gap: 10px;
    padding-top: 10px;
    padding-bottom: 10px;
    margin-bottom: 24px;
  }

  .filter-nav {
    display: flex;
    align-items: center;
    gap: 14px;
    overflow-x: auto;
    flex-wrap: nowrap;
    -webkit-overflow-scrolling: touch;
    scrollbar-width: none;
    -ms-overflow-style: none;
    max-width: 100%;
    width: 100%;
    padding-bottom: 2px;
    /* Reserve horizontal gestures for the slide-to-scroll behavior; vertical pans and pinch-zoom stay native */
    touch-action: pan-y pinch-zoom;
    overscroll-behavior-x: contain;
    -webkit-user-select: none;
    user-select: none;
  }

  .filter-nav::-webkit-scrollbar {
    display: none;
  }

  .filter-nav::after {
    content: '';
    flex-shrink: 0;
    width: 12px;
  }

  /* .filter-nav scrolls horizontally here, which would clip an absolutely
     positioned panel — so the sub-services expand inline in the same row. */
  .filter-group {
    display: flex;
    align-items: center;
    gap: 14px;
    flex-shrink: 0;
  }

  .filter-dropdown {
    position: static;
    display: none;
    flex-direction: row;
    gap: 14px;
    min-width: 0;
    padding: 0;
    background: none;
    border: none;
    border-radius: 0;
    opacity: 1;
    transform: none;
  }

  .filter-group.open .filter-dropdown {
    display: flex;
  }

  .sort-nav {
    display: flex;
    align-items: center;
    gap: 12px;
    overflow-x: auto;
    flex-wrap: nowrap;
    -webkit-overflow-scrolling: touch;
    scrollbar-width: none;
    -ms-overflow-style: none;
    max-width: 100%;
    width: 100%;
    margin-left: 0;
    padding-bottom: 2px;
    /* Reserve horizontal gestures for the slide-to-scroll behavior; vertical pans and pinch-zoom stay native */
    touch-action: pan-y pinch-zoom;
    overscroll-behavior-x: contain;
    -webkit-user-select: none;
    user-select: none;
  }

  .sort-nav::-webkit-scrollbar {
    display: none;
  }
}

@media (max-width: 640px) {
  :root {
    --grid-margin: 16px;
  }

  .secondary-nav .contact-link {
    display: none;
  }
  
  .hero-footer-container {
    flex-direction: column;
    align-items: flex-start;
    gap: 16px;
  }

  /* The phone drawing of 2026-10-23 boxes the caption where it is and draws it up into the empty
     space above.  The footer is bottom-anchored, so margin-bottom is what lifts the caption without
     moving the controls block below it.  Measured against the drawing's own window (510x646): the
     caption's bottom edge at 403px and the block's top at 589px, which this reproduces as
     403 / 587 -- and the clamp keeps the lift proportional from a 280px-wide phone to a 640px one
     instead of pinning it to one device.
     "for mobile", 2026-10-24 (third sheet): the caption is that same single block again.  The first
     two sheets dropped the links line and then the category out of it onto the band floor; the third
     boxes both where they now stack and draws one arrow up to the title, so they are back in the flow
     in their markup order -- eyebrow above the title, actions under it.  Nothing about the lift had to
     change to put them back.  Measured after the rejoin at 507x606 / 390x844 / 320x568: the links'
     bottom edge sits `lift` clear of the controls block (339.9 / 522.4 / 318.1 against 513.4 / 757.8 /
     481.8) and the title 22.8px above it.
     The fifth sheet of the same day (MLKY, at 390x844 -- the crop is 452 of the hero's 844 px tall,
     and the band rows in it land within 1px of that frame's measured geometry) boxes the whole
     caption and draws one arrow down onto a line in the empty space, saying MOVE HERE.  The line is
     103px above the controls block's top edge, so the caption's bottom edge is asked to sit there:
     the lift drops from 26vh to a floor of 88px, which at 844 is 10.4vh.  The proportion is gone on
     purpose -- at this coefficient 10.5vh does not reach 88px until the viewport is 838px tall, so
     every common phone gets the distance the drawing measures and only a tablet-tall window drifts
     upward.  That does NOT reproduce the 2026-10-23 drawing's 403 / 587 line on a short screen (its
     26vh came from a 646px window, where this rule now gives 88px instead of 170); the newer sheet
     wins and the conflict is filed in scratch/_handoff_s34.md.  What the earlier sheets marked and
     did NOT retract is kept: the pill and the slide counter lead the pagination line at the left
     edge, and "Website by RDVS" is left-aligned.
     The sixth sheet of the same day (1981, a 279x453 crop of a 280x653 window: the band's three rows
     land within 1px of that frame's measured geometry) boxes the pill and the counter where the fourth
     sheet put them and draws one arrow up onto "MOVE HERE".  The pair leaves the dashes line and takes
     a line of its own above it -- the arrangement the >=1200px swap block already runs.  That row is
     bottom-anchored, so the 17px it grows by (16 of row-gap plus the 1px hairline the dashes' own line
     is) lifts its top edge, which is the caption's datum, by exactly that much.  Subtracting it here is
     what keeps the fifth sheet's drawn line: the caption does not move, and the only things that change
     place are the boxed pair, which rises 17px, and the dashes, which drop 9 to lead their own line the
     way they do on the desktop band. */
  /* Mobile datum line (owner markup 2026-11-09): caption moves down to bottom datum directly above controls/pagination row */
  .caption-wrapper {
    margin-bottom: 8px;
  }

  /* Owner, 2026-11-06: "the text position for project name etc appears to shift for some slides but
     they shouldn't.  They should be consistently positioned on mobile for every slide."  The caption
     is bottom-anchored, so a title that wraps to a second line at a slim width grew the block upward
     and carried the eyebrow, and the footer's top edge with it -- which is also the phone contain
     base.  Measured at 280x653: four of the twenty titles took two lines, and their category stood at
     364.3 while every one-line title stood at 391.2, a 26.9px step per slide.  Reserving the second
     line on the title box gives every caption the same height, so the category, the title's first
     line and the links all land on one set of rows and the contain base stops moving too.  At this
     tier the title's clamp is pinned to its 1.35rem floor (2.5vw is still under it at 640), and
     --line-height-heading is 1.25, so the reserved box is the 54px two-line title the markup's
     bottom edge already assumes. */
  .project-title {
    min-height: calc(1.35rem * var(--line-height-heading) * 2);
  }

  .hero-footer-container {
    /* Phone geometry (390x844), owner markup of 2026-11-03: the controls block -- the counter's row, the
       hairline bars, the socials and the credit -- is 87px tall at 360 and 430 and 89px at 640, and it
       stands on 16px of floor padding, so the bar is 89 + 16 + 8 of air = 113px.  Before this it was
       68px, which left the counter row and the bars -- 35px of ink at 390x844 -- sitting on the raw slide
       with the bar's edge drawn straight through the band, which is the line the drawing marks.
       The owner's 2026-11-06 markup then put the socials and the credit on ONE line (see
       .hero-credit-row below), which removes a 16.8px type line and the 16px gap that separated it, so
       the same derivation gives 113 - 32.8 = 80.  Measured after the merge, the ink runs 799.2..859 at
       507x875 and the 80px bar tops at 795 -- the same 4px of air the 113px bar left above the counter
       row there. */
    --hero-strip-height: 80px;
  }

  .hero-meta-controls {
    align-items: stretch;
    width: 100%;
    flex-direction: column;
    justify-content: flex-start;
    gap: 12px;
  }

  .hero-controls-row {
    display: flex;
    flex-direction: column;
    align-items: stretch;
    width: 100%;
    gap: 10px;
  }

  .hero-status-row {
    display: flex;
    flex-direction: row;
    align-items: center;
    /* "for mobile", 2026-10-24: the sheet boxes the volume pill and the 05 / 15 counter and runs one
       long line back to the pagination dashes, ending in two arrowheads that drop onto that line.
       Two boxed things, two arrowheads, one destination: both controls leave the far end of this row
       and join the bars at the left edge, so the row reads bars, pill, counter from x=16.
       flex-start rather than an order swap because that is already the DOM order.
       The fourth sheet of the same day boxes that pair again and runs one arrow left along the dashes
       to the container's edge -- the same mark that moved the social row and the credit, whose lines
       were already left-packed.  Here the line is left-packed but the pair is not first: the dashes
       hold x=16 and the pair sits after them at 134.  So the pair leads the line and the bars follow;
       the order moves the one element that has no mark on the sheet. */
    justify-content: flex-start;
    width: 100%;
    gap: 8px;
    /* Three controls share this row (the Previous/Next pair is gone -- the edge chevrons took over, and
       they live over the media, not in this row).  Wrapping started as the valve for the 280 px tier,
       where the counter would otherwise have pushed the document wide; the sixth sheet of 2026-10-24
       made it the arrangement, with the dashes taking the second line on purpose. */
    flex-wrap: wrap;
    /* The sixth sheet's arrow is what puts the two lines here, so the gap between them is the gap the
       >=1200px swap block uses for the same split -- 16px, not the 10px that only ever had to separate a
       counter that had been pushed onto a second line by a too-narrow tier. */
    row-gap: 16px;
    /* Owner markup 2026-11-10 (media_1794314466664_58b15388.jpg): "MOVE DOWN 8PX ON MOBILE" */
    transform: translateY(8px);
  }

  /* Owner markup 2026-11-07: move volume pill and slide counter down by 12px on mobile */
  .hero-status-row .hero-volume-control,
  .hero-status-row .slide-status {
    transform: translateY(12px);
  }

  .hero-social-links {
    /* "MOVE HERE, LEFT ALIGNED" -- the phone drawing's blue box round the social row, with an arrow
       onto the container's left edge.  The row is already full width, so this is the whole change. */
    justify-content: flex-start;
    gap: 16px;
    margin-top: 0;
  }

  /* The last mark on the same sheet: a box round "Website by RDVS" with an arrow running left along
     the bottom edge.  The paragraph is already the block's full width (its column stretches it), so
     the credit's right alignment is the only thing holding it off the edge. */
  .hero-credit {
    text-align: left;
  }

  /* Owner markup 2026-11-06 (The Fitzgerald, phone): the socials leave their own row and join the
     credit's line, so both start at the container's left edge on one baseline -- "MOVE SOCIAL MEDIA
     LINKS TO THE LINE BELOW IN LINE WITH WEBSITE BY RDVS". Baseline alignment, not centre, because the
     two runs share a type size and the drawing lines them up on the written line. The row wraps rather
     than overflows: at 390 the four links plus the credit come to ~357px against 358 of usable width,
     and anything narrower (320, 280) drops the credit to a second line at the same left edge. */
  /* Mobile footer hairline repetition (owner markup 2026-11-09, media_1794231385903_fd94201a.jpg:
     "REPEAT THIS LINE HERE" - repeats header bottom hairline across full width above social links and credit) */
  .hero-footer-container::before {
    border-top: none;
  }

  .hero-credit-row {
    display: flex;
    align-items: baseline;
    justify-content: flex-start;
    flex-wrap: wrap;
    column-gap: 16px;
    row-gap: 2px;
    position: relative;
    padding-top: 10px;
    margin-top: 8px;
    width: calc(100% + 2 * var(--grid-margin, 16px));
    margin-left: calc(-1 * var(--grid-margin, 16px));
    margin-right: calc(-1 * var(--grid-margin, 16px));
    padding-left: var(--grid-margin, 16px);
    padding-right: var(--grid-margin, 16px);
    border-top: 1px solid var(--border-hairline);
  }

  .pagination-bars {
    gap: 3px;
    /* The fourth sheet's left arrow: the dashes give up the head of the line to the pill and the
       counter.  Painted order becomes pill, counter, bars; the DOM and tab order stay as authored.
       The sixth sheet then lifts that pair off this line, and a full basis is what keeps the dashes on
       a line of their own -- the same lever the >=1200px swap block pulls with `flex-basis: 100%`.
       Left-packed, so they start at the container edge now that nothing sits before them. */
    order: 1;
    flex-basis: 100%;
  }

  .pagination-bar {
    width: 6px;
  }

  .pagination-bar.active {
    width: 14px;
  }
}

@media (max-width: 480px) {
  :root {
    --grid-margin: 16px;
    --grid-gutter: 12px;
  }

  .search-input {
    width: 64px;
  }
  .search-input:focus {
    width: 90px;
  }

  .header-right {
    gap: 10px;
  }

  .card-meta-main {
    flex-direction: column;
    align-items: flex-start;
    gap: 2px;
  }

  .card-title {
    white-space: normal;
    display: -webkit-box;
    -webkit-line-clamp: 2;
    -webkit-box-orient: vertical;
    overflow: hidden;
    line-height: 1.35;
  }

  .card-year {
    font-size: 0.75rem;
  }

  .card-meta-sub {
    flex-wrap: wrap;
    white-space: normal;
  }

  .hero-social-links {
    gap: 12px;
  }

  .hero-social-link {
    font-size: 0.6875rem;
  }

  .pagination-bars {
    gap: 2px;
  }

  .pagination-bar {
    width: 5px;
  }

  .pagination-bar.active {
    width: 12px;
  }

  .footer-right {
    flex-direction: column;
    align-items: flex-start;
    gap: 14px;
  }

  .page-container {
    padding-top: calc(var(--header-height) + 24px);
    padding-bottom: 56px;
  }

  .project-detail-container {
    padding-top: calc(var(--header-height) + 20px);
    padding-bottom: 64px;
  }

  .project-gallery-grid {
    gap: 20px;
  }
}

/* Below 376px of viewport the phone row of socials + credit no longer fits on one line -- measured at the
   11px link size, 226.4 of links + 16 of gap + 102.2 of credit = 344.6 against the viewport minus its two
   16px margins -- so the credit wraps under the socials and the block grows by that second line. The strip
   pays for the line rather than leave the counter row outside the band: 97 = 80 + 17. Measured at
   320x653, the ink tops at 559.8 against a band top of 556, the same ~4px of air as the wider phones. */
@media (max-width: 380px) {
  .hero-footer-container {
    --hero-strip-height: 97px;
  }
}

@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
  }
}

/* ==========================================================================
   Work Page Row-by-Row Layout System
   ========================================================================== */
.grouped-rows-layout {
  display: flex !important;
  flex-direction: column !important;
  gap: 72px;
  width: 100%;
}

@media (max-width: 560px) {
  .grouped-rows-layout {
    gap: 48px;
  }
}

.work-group-row {
  display: flex;
  flex-direction: column;
  gap: 24px;
  width: 100%;
}

.work-group-header {
  display: flex;
  justify-content: space-between;
  align-items: baseline;
  border-bottom: 1px solid var(--border-hairline);
  padding-bottom: 12px;
}

.work-group-title {
  font-size: clamp(1.35rem, 2.5vw, 1.75rem);
  font-weight: 400;
  letter-spacing: -0.01em;
  color: var(--foreground);
  margin: 0;
}

.work-group-count {
  font-size: 0.8125rem;
  color: var(--text-secondary);
  font-feature-settings: "tnum";
}

/* ==========================================================================
   INTERACTIVE 360° SPHERICAL MEDIA VIEWER
   ========================================================================== */
.vr-360-container {
  position: relative;
  width: 100%;
  height: 100%;
  overflow: hidden;
  background: #050505;
  cursor: grab;
  user-select: none;
  touch-action: none;
}

.vr-360-container.is-dragging {
  cursor: grabbing !important;
}

.vr-360-canvas {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  display: block;
  z-index: 1;
}

.vr-360-overlay {
  position: absolute;
  inset: 0;
  pointer-events: none;
  z-index: 5;
  display: flex;
  flex-direction: column;
  justify-content: space-between;
  padding: 24px;
}

/* 360 Panoramic Badge */
.vr-360-badge {
  display: inline-flex;
  align-items: center;
  gap: 8px;
  padding: 6px 14px;
  background: rgba(12, 12, 12, 0.65);
  backdrop-filter: blur(16px);
  -webkit-backdrop-filter: blur(16px);
  border: 1px solid rgba(255, 255, 255, 0.12);
  border-radius: 20px;
  font-size: 0.6875rem;
  font-weight: 500;
  letter-spacing: 0.1em;
    color: #fff;
  width: fit-content;
  pointer-events: auto;
  box-shadow: 0 4px 20px rgba(0, 0, 0, 0.3);
}

.vr-badge-icon {
  animation: vr-spin 16s linear infinite;
}

@keyframes vr-spin {
  from { transform: rotate(0deg); }
  to { transform: rotate(360deg); }
}

/* Center Drag Hint */
.vr-drag-hint {
  position: absolute;
  top: 50%;
  left: 50%;
  transform: translate(-50%, -50%);
  display: inline-flex;
  align-items: center;
  gap: 10px;
  padding: 10px 20px;
  background: rgba(10, 10, 10, 0.75);
  backdrop-filter: blur(16px);
  -webkit-backdrop-filter: blur(16px);
  border: 1px solid rgba(255, 255, 255, 0.18);
  border-radius: 30px;
  font-size: 0.75rem;
  letter-spacing: 0.08em;
    color: #ffffff;
  pointer-events: none;
  box-shadow: 0 8px 32px rgba(0, 0, 0, 0.4);
  transition: opacity 0.5s cubic-bezier(0.16, 1, 0.3, 1), transform 0.5s cubic-bezier(0.16, 1, 0.3, 1);
  opacity: 1;
}

.vr-drag-hint.dismissed {
  opacity: 0;
  transform: translate(-50%, -40%);
}

/* Look-Around D-Pad (Compass Widget) */
.vr-look-controls {
  position: absolute;
  bottom: 74px;
  right: 24px;
  left: auto;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 4px;
  pointer-events: auto;
  background: rgba(10, 10, 10, 0.55);
  backdrop-filter: blur(16px);
  -webkit-backdrop-filter: blur(16px);
  padding: 6px;
  border-radius: 8px;
  border: 1px solid rgba(255, 255, 255, 0.1);
  box-shadow: 0 4px 20px rgba(0, 0, 0, 0.3);
}

.vr-btn-row {
  display: flex;
  align-items: center;
  gap: 4px;
}

.vr-btn {
  width: 32px;
  height: 32px;
  border-radius: 4px;
  border: 1px solid rgba(255, 255, 255, 0.1);
  background: rgba(25, 25, 25, 0.65);
  color: #ffffff;
  display: flex;
  align-items: center;
  justify-content: center;
  cursor: pointer;
  padding: 0;
  transition: all 0.2s cubic-bezier(0.16, 1, 0.3, 1);
  touch-action: manipulation;
}

.vr-btn:hover {
  background: rgba(255, 255, 255, 0.2);
  border-color: rgba(255, 255, 255, 0.35);
  transform: scale(1.05);
}

.vr-btn:active {
  transform: scale(0.95);
  background: rgba(255, 255, 255, 0.3);
}

.vr-btn-center {
  background: rgba(40, 40, 40, 0.7);
}

/* Secondary Controls (Zoom + Fullscreen) */
.vr-secondary-controls {
  position: absolute;
  bottom: 24px;
  right: 24px;
  display: flex;
  align-items: center;
  gap: 8px;
  pointer-events: auto;
}

.vr-zoom-group {
  display: flex;
  background: rgba(10, 10, 10, 0.55);
  backdrop-filter: blur(16px);
  -webkit-backdrop-filter: blur(16px);
  padding: 4px;
  border-radius: 6px;
  border: 1px solid rgba(255, 255, 255, 0.1);
  gap: 4px;
}

.vr-btn-fullscreen {
  background: rgba(10, 10, 10, 0.55);
  backdrop-filter: blur(16px);
  -webkit-backdrop-filter: blur(16px);
}

/* Slideshow Hero integration adjustments */
.slide .vr-360-container {
  width: 100%;
  height: 100%;
}

.slide .vr-look-controls {
  bottom: 172px;
  right: 32px;
  left: auto;
}

.slide .vr-secondary-controls {
  bottom: 120px;
  right: 32px;
}

@media (max-width: 768px) {
  .slide .vr-look-controls {
    bottom: 190px;
    right: 16px;
    left: auto;
    transform: scale(0.9);
    transform-origin: bottom right;
  }
  .slide .vr-secondary-controls {
    bottom: 140px;
    right: 16px;
    transform: scale(0.9);
    transform-origin: bottom right;
  }
}

/* Minimalist Playback Bar for dedicated 360 video pages */
/* The hero wrapper sizes itself to its content here: .project-hero-media's 16/10
   aspect ratio and 78vh cap would clip the viewer plus the bar below it. */
.vr-hero-media {
  position: relative;
  display: flex;
  flex-direction: column;
  gap: 12px;
  width: 100%;
  aspect-ratio: auto;
  max-height: none;
  overflow: visible;
  background-color: transparent;
}

.vr-playback-bar {
  display: flex;
  align-items: center;
  gap: 16px;
  padding: 12px 18px;
  background: rgba(14, 14, 14, 0.75);
  backdrop-filter: blur(16px);
  -webkit-backdrop-filter: blur(16px);
  border: 1px solid rgba(255, 255, 255, 0.1);
  border-radius: 6px;
}

.vr-play-pause-btn,
.vr-mute-btn {
  background: none;
  border: none;
  color: #ffffff;
  cursor: pointer;
  padding: 4px;
  display: flex;
  align-items: center;
  justify-content: center;
  transition: opacity 0.2s ease, transform 0.2s ease;
}

.vr-play-pause-btn:hover,
.vr-mute-btn:hover {
  opacity: 0.75;
  transform: scale(1.08);
}

.vr-progress-track {
  flex: 1;
  height: 4px;
  background: rgba(255, 255, 255, 0.15);
  border-radius: 2px;
  cursor: pointer;
  position: relative;
  overflow: hidden;
  transition: height 0.15s ease;
}

.vr-progress-track:hover {
  height: 6px;
}

.vr-progress-fill {
  height: 100%;
  background: #ffffff;
  border-radius: 2px;
  width: 0%;
  transition: width 0.1s linear;
}

.vr-time-display {
  font-size: 0.75rem;
  color: rgba(255, 255, 255, 0.65);
  font-feature-settings: "tnum";
  letter-spacing: 0.04em;
  white-space: nowrap;
}

/* Homepage hero ink: two grounds, two laws, and the GROUND DECIDES.  Rewritten 2026-11-03 on the
   theme-consistency order ("check the theme for consistency throughout the site to make sure words are
   readable when themes are changes"), and rewritten again the same evening by the instrument that measures
   the pixels a letter stands on (scratch/_ink_pixels.cjs) rather than the cascade.
   GROUND 1, the slide: a photograph has no theme, so type on it is media ink -- white -- in both themes.
   GROUND 2, the band: it paints --header-bg by the owner's drawing of 2026-11-03, so type on it follows
   the theme.  .hero-footer-container already hands its subtree the band's ink; what is left here is the
   rows that are NOT on the band.
   WHICH ROWS those are is a measurement, not a breakpoint.  scratch/_hero_ground_map.cjs walked 11
   viewports x 2 themes on 2026-11-03 (360x740, 480x800, 640x900, 641x900, 820x1180, 1024x768, 1199x800,
   1200x800, 1440x900, 1920x1080, 2560x1440) and the answer is not a function of width:
     >=1200    band 40px.  Category tops 73.8 above the floor, counter 69.9, title 237..397  -> PICTURE;
               links 32.4, bars 25, socials 32.4, credit 32.4                              -> BAND.
     <=640     band 113px. Category 261.8..274.7, title 240..252.9, links 207..219.9        -> PICTURE;
               counter 103.2..107.1, bars 73.2..74.6, socials 60.2, credit 32.8             -> BAND.
     641-1199  band 108px -- and this tier disagrees with itself: at 1024x768 the category tops at 100.6
               and the title at 78.8 (BAND), at 641x900 they top at 183.1 and 161.3 (PICTURE).
   The caption is lifted by a fraction of the viewport while the band is a fixed number of pixels, so no
   list of rows per media query can hold: the first such list, drawn from a desktop-only drawing, painted
   "View project" 1.08:1 on the photograph at 390x844 in the light theme and the title 1.28:1 on the milky
   band at 1024x768.  Both are measured, and both are why the boundary moved into js/main.js.
   So: CSS states the two inks; assignHeroGrounds() in js/main.js compares each row's box with the band's
   top edge and puts the answer on the row as data-hero-ground; it re-runs on resize, on every slide cut
   and whenever the caption's text changes height. */
.hero-footer-container [data-hero-ground="band"] {
  --foreground: var(--ink-page);
  --text-secondary: var(--ink-panel-quiet);
}

.hero-footer-container [data-hero-ground="media"] {
  --foreground: var(--ink-media);
  --text-secondary: var(--ink-media-secondary);
}

/* THE NO-JS FALLBACK.  index.html bakes the first slide's caption and the deck needs js/main.js to move
   it, so these rules only govern a visitor with scripting off -- and, for the first 6.9 s, everybody.
   They are the two tiers where the measurement is uniform, copied from the numbers above; the 641-1199
   tier gets nothing because it has no single answer, and the container's own band ink is the safer of its
   two wrongs (dark type on a panel is legible; dark type on a photograph is not).
   EVERY selector here is conditioned with :not([data-hero-ground]) -- and that is not decoration.  The two
   rules above are `.hero-footer-container [data-hero-ground="x"]` at specificity (0,2,0) and these were
   `.hero-footer-container .project-title` at the same (0,2,0), so the cascade handed the win to whichever
   came LATER in the file -- these did.  A row the script had just measured and pinned to the band would
   still have been painted with media ink by the fallback, which is the white-on-milk-panel 1.00:1 bug again,
   reachable on a short or landscape phone window where the caption does fall inside the 113px band.  With the
   `:not()` the fallback fires only on a row the script has NOT classified, which is exactly what a no-JS
   fallback is for, and the ordering stops mattering.  `scratch/_hero_ground_map.cjs` measures 640x360 for
   that case, and scratch/_guard_theme_ink.py asserts every fallback selector carries the condition.
   The title is a plain `color: var(--foreground)` at its own rule, so handing the row the ground's
   --foreground is enough -- no !important, which is what the previous revision needed only because its
   pin was unconditional and had to beat the tier it got wrong. */
@media (min-width: 1200px) {
  .hero-footer-container .project-category:not([data-hero-ground]),
  .hero-footer-container .project-title:not([data-hero-ground]),
  .hero-footer-container .slide-status:not([data-hero-ground]) {
    --foreground: var(--ink-media);
    --text-secondary: var(--ink-media-secondary);
  }
}

@media (max-width: 640px) {
  .hero-footer-container .project-category:not([data-hero-ground]),
  .hero-footer-container .project-title:not([data-hero-ground]),
  .hero-footer-container .project-links:not([data-hero-ground]) {
    --foreground: var(--ink-media);
    --text-secondary: var(--ink-media-secondary);
  }
}

.hero-volume-control {
  /* Deliberately NOT a classified row.  The pill paints its own ground -- rgba(0,0,0,.65) in both themes,
     line 821 above -- so its glyph and label are white-on-dark wherever the pill happens to sit: over the
     light theme's panel that composite is rgb(85,85,85) and over a bright frame it is no worse, which is
     6.6:1 or better either way.  Following the band here would be the bug: white on the panel is 1.00:1. */
  --foreground: var(--ink-media);
  --text-secondary: var(--ink-media-secondary);
}

/* ==========================================================================
   Product — the MIG line (retired 2026-10-21)
   The seven product-*.html pages are ordinary works now: cards on work.html, rows
   on archive.html, .project-* classes, and they inherit every rule above with no
   class of their own. product.html and the nav link that opened it are deleted, so
   the only thing left here is the record of why nothing is.
   ========================================================================== */


/* RDVS-INTRO:BEGIN generated by scratch/_apply_intro.py */
/* The overlay is set in the site's own face, so the intro reads as RDVS and not as a
   Helvetica fallback. Colour is deliberately NOT bound: the veil is a blue field held to
   brand blue #1236FF's luminance with white ink in both themes, and --foreground is
   #111111 in light mode, which would put near-black type on blue. --rdvs-blue, --rdvs-ink
   and the mask's --rdvs-mid-* keep the artifact's own fallbacks. */
.rdvs-intro-veil .rdvs-intro {
  --rdvs-font: var(--font-sans);
}

/* The once-per-session suppression, opt-OUT: a visitor with JavaScript switched off gets the
   opening, because nothing here can set data-intro. */
html[data-intro="done"] .rdvs-intro-veil {
  display: none;
}
/* RDVS-INTRO:END */


/* Owner update 2026-11-07: On mobile for wide treatment (.is-contain-slide under 769px),
   the project title and date are black on the light theme's white ground, while the
   service name stays dark grey (--text-secondary). In dark theme, they take white. */
@media (max-width: 768px) {
  .hero-viewport.is-contain-slide .caption-card.active .project-title,
  .hero-viewport.is-contain-slide .caption-card.active .project-title a,
  .hero-viewport.is-contain-slide .caption-card.active .project-date {
    color: #000000;
  }
  [data-theme="dark"] .hero-viewport.is-contain-slide .caption-card.active .project-title,
  [data-theme="dark"] .hero-viewport.is-contain-slide .caption-card.active .project-title a,
  [data-theme="dark"] .hero-viewport.is-contain-slide .caption-card.active .project-date {
    color: #ffffff;
  }
}


/* Homepage Welcome Message */
.homepage-welcome-message {
  display: none;
}

/* Mobile Phone & Portrait Screens (<=992px, or <=1024px in portrait):
   Positioned at top datum line between header and media (owner markup media_1794225954109_2dc3b357.jpg:
   "MOVE TO DATUMN AND INCREASE FONT HEIGHT TO 150% FOR THIS SIZE AND/OR PROPORTION OF MOBILE SCREEN") */
@media (max-width: 992px), (max-width: 1024px) and (orientation: portrait) {
  .homepage-welcome-message {
    display: flex;
    flex-direction: column;
    position: absolute;
    top: calc(var(--header-height, 56px) + 16px);
    bottom: auto;
    /* Aligned with left margin datum line */
    left: var(--grid-margin, 16px);
    right: var(--grid-margin, 16px);
    z-index: 25;
    pointer-events: none;
    font-family: var(--font-sans, "Geist", "Helvetica Neue", Helvetica, Arial, sans-serif);
    /* Font height increased to 150% per user markup */
    font-size: clamp(24px, 5vw, 32px);
    font-weight: 400;
    line-height: 1.25;
    letter-spacing: -0.02em;
    -webkit-font-smoothing: antialiased;
    -moz-osx-font-smoothing: grayscale;
    /* Dark grey when not on an image */
    color: #333333;
    opacity: 1;
    visibility: visible;
    transition: opacity 0.45s cubic-bezier(0.16, 1, 0.3, 1), visibility 0.45s ease, color 0.3s ease;
  }

  [data-theme="dark"] .homepage-welcome-message:not(.on-media) {
    color: #ffffff;
  }

  /* Always white when falling over image or video */
  .homepage-welcome-message.on-media {
    color: #ffffff !important;
  }

  .homepage-welcome-message.is-hidden {
    opacity: 0;
    visibility: hidden;
  }
}

/* Landscape Tablet Displays (769px - 1024px in landscape):
   Aligned with margin datum line, positioned at bottom: 25dvh */
@media (min-width: 769px) and (max-width: 1024px) and (orientation: landscape) {
  .homepage-welcome-message {
    display: flex;
    flex-direction: column;
    position: absolute;
    bottom: 25dvh;
    /* Aligned with vertical margin datum line */
    left: max(var(--grid-margin, 24px), calc((100vw - var(--max-width, 2000px)) / 2 + var(--grid-margin, 24px)));
    max-width: calc(max(calc(50% - var(--hero-caption-inset, 330px)), var(--hero-caption-min, 288px)) - var(--grid-margin, 24px) - 20px);
    z-index: 25;
    pointer-events: none;
    font-family: var(--font-sans, "Geist", "Helvetica Neue", Helvetica, Arial, sans-serif);
    font-size: clamp(24px, 2.6vw, 32px);
    font-weight: 400;
    line-height: 1.2;
    letter-spacing: -0.04em;
    -webkit-font-smoothing: antialiased;
    -moz-osx-font-smoothing: grayscale;
    color: #ffffff;
    opacity: 1;
    visibility: visible;
    transition: opacity 0.45s cubic-bezier(0.16, 1, 0.3, 1), visibility 0.45s ease, color 0.3s ease;
  }

  .hero-viewport.is-contain-slide .homepage-welcome-message {
    color: #333333;
  }

  [data-theme="dark"] .hero-viewport.is-contain-slide .homepage-welcome-message {
    color: #ffffff;
  }

  .homepage-welcome-message.on-media,
  .hero-viewport.is-contain-slide .homepage-welcome-message.on-media {
    color: #ffffff !important;
  }

  .homepage-welcome-message.is-hidden {
    opacity: 0;
    visibility: hidden;
  }
}

/* The welcome message, up on the top datum in the 993-1024 landscape band (owner, 2026-11-11, markup
   Capture-fix.PNG: a ~1000x966 window with the plate boxed from the left datum to the right datum and up
   to just under the header, and an arrow drawn from the welcome to the top reading "MOVE WELCOME MESSAGE
   UP"). From 993px the phone rule stops applying and the landscape block above places the welcome by
   `bottom: 25dvh` alone, so its text sat at 610..725 -- in the middle of the space the plate is asked to
   fill. On the phone's own top datum (header + 16) the whole band is free again, which is also why the
   contain ceiling can stay the welcome rather than the header. This sits AFTER that block because both
   set `bottom` on the same selector and the later one wins. Measured at 1000x966: the last line ends at
   181, `--mobile-contain-top` 206 (was 750), and a 1920x1080 plate now paints 952x536 sitting on 828. */
@media (min-width: 993px) and (max-width: 1024px) and (orientation: landscape) {
  .homepage-welcome-message {
    top: calc(var(--header-height, 56px) + 16px);
    bottom: auto;
  }
}

/* Desktop (> 1024px): REVERTED per user specification ("not for desktops. Please redo and revert.")
   - Indented +100px from margin datum
   - Font size: clamp(16px, 1.35vw, 22px)
   - Font weight: 300
   - Font family: "Helvetica Neue", Helvetica, Arial, sans-serif
*/
.welcome-title-hairline {
  display: none;
}

@media (min-width: 1024px) {
  /* Hairline connector between welcome message full stop and active project title (slides 1 to 19) */
  .welcome-title-hairline {
    display: block;
    position: absolute;
    left: calc(100% + 14px);
    right: auto;
    height: 1px;
    background-color: #ffffff;
    z-index: 25;
    pointer-events: none;
    opacity: 1;
    visibility: visible;
    transform: translateY(-50%);
    transform-origin: left center;
    box-shadow: 0 0 1px rgba(0, 0, 0, 0.45);
    /* Elastic stretch toward project title: left endpoint is rigidly locked 14px from welcome message full stop */
    transition: width 0.75s cubic-bezier(0.34, 1.56, 0.64, 1),
                top 0.4s ease,
                opacity 0.35s ease,
                visibility 0.35s ease;
  }

  .hero-viewport.is-contain-slide .welcome-title-hairline {
    background-color: #333333;
  }

  [data-theme="dark"] .welcome-title-hairline,
  [data-theme="dark"] .hero-viewport.is-contain-slide .welcome-title-hairline,
  .welcome-title-hairline.on-media {
    background-color: #ffffff;
    box-shadow: none;
  }

  .welcome-title-hairline.is-hidden {
    opacity: 0;
    visibility: hidden;
    pointer-events: none;
    width: 0 !important;
  }

  .homepage-welcome-message {
    display: flex;
    flex-direction: column;
    position: absolute;
    /* Aligned with horizontal caption baseline datum (25dvh from bottom) and vertical datum line (100px right of margin datum) */
    bottom: 25dvh;
    right: calc(100vw - (max(calc(50vw - var(--hero-caption-inset, 330px)), var(--hero-caption-min, 288px)) + var(--grid-margin, 24px) - 88px));
    left: auto;
    max-width: calc(max(calc(50vw - var(--hero-caption-inset, 330px)), var(--hero-caption-min, 288px)) - 88px);
    z-index: 25;
    pointer-events: none;
    font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
    align-items: flex-end;
    text-align: right;
    font-size: clamp(19.2px, 1.62vw, 26.4px);
    font-weight: 400;
    line-height: 1.25;
    letter-spacing: -0.04em;
    -webkit-font-smoothing: antialiased;
    -moz-osx-font-smoothing: grayscale;
    color: #ffffff;
    opacity: 1;
    visibility: visible;
    /* Elastic spring transition for horizontal movement from right to left / left to right */
    transition: right 0.75s cubic-bezier(0.34, 1.56, 0.64, 1),
                max-width 0.75s cubic-bezier(0.34, 1.56, 0.64, 1),
                opacity 0.45s cubic-bezier(0.16, 1, 0.3, 1),
                visibility 0.45s ease,
                color 0.3s ease;
  }

  /* Dark grey on blank theme background in light mode */
  .hero-viewport.is-contain-slide .homepage-welcome-message {
    color: #333333;
  }

  [data-theme="dark"] .hero-viewport.is-contain-slide .homepage-welcome-message {
    color: #ffffff;
  }

  /* User rule: The text color of the welcome message should always be white when it falls on image or video */
  .homepage-welcome-message.on-media,
  .hero-viewport.is-contain-slide .homepage-welcome-message.on-media {
    color: #ffffff !important;
  }

  .homepage-welcome-message.is-hidden {
    opacity: 0;
    visibility: hidden;
  }
}

/* The welcome, up on the top datum in the 1024-1199 tier too (owner, 2026-11-11, markup
   Capture-res-002.PNG: a ~1165x803 window on Protea Hotel, plate 13/20, with the sentence boxed at
   630..740 and an arrow drawn from it to the header reading "MOVE WELCOME MESSAGE UP"). From 1024px the
   desktop block above anchors the welcome by `bottom: 25dvh`, which at this tier drops it into the middle
   of the plate. Below 1200 the caption cluster lives in the footer band instead of being lifted onto the
   welcome's line, so there is nothing up here for it to sit beside; the sentence goes to the same top
   datum every other band uses (header + 16) and keeps its horizontal placement. This sits AFTER that block
   because both set `bottom` on the same selector and the later rule wins. */
@media (min-width: 1024px) and (max-width: 1199px) {
  .homepage-welcome-message {
    top: calc(var(--header-height, 56px) + 16px);
    bottom: auto;
  }
}

.homepage-welcome-message .welcome-line-wrapper {
  text-align: inherit;
  display: block;
  overflow: hidden;
  line-height: 1.2;
}

.homepage-welcome-message .welcome-line-text {
  display: inline-block;
  font-weight: inherit;
  transform: translateY(0);
  will-change: transform;
  white-space: nowrap;
}

.homepage-welcome-message.is-animating .welcome-line-text {
  animation: welcome-line-rise 1.1s cubic-bezier(0.16, 1, 0.3, 1) both;
}

@keyframes welcome-line-rise {
  from {
    transform: translateY(115%);
  }
  to {
    transform: translateY(0);
  }
}
