/*
 * The public site.
 *
 * Hand-written, per CLAUDE.md §9: the brand is the product, and templated
 * styling undercuts it. Every value here comes from the design handoff in
 * `design_handoff_homepage_desktop_and_mobile/` — the numbers are theirs, the
 * structure is ours.
 *
 * ---
 *
 * **One stylesheet, not one per page.** The whole file is about 10 KB before
 * compression, which is less than a single photograph on the homepage. Split
 * into per-page files it would cost a request each and gain nothing.
 *
 * **No build step.** The admin has Vite because it is an application; this is
 * a stylesheet. Adding a bundler here would mean the public site could not be
 * edited without running a toolchain, which is a bad trade for a site whose
 * whole point is that it works as plain HTML.
 *
 * **Two breakpoints, both designed.** 1440 (desktop) and 390 (mobile) are the
 * two the design specifies. Nothing is designed for tablet: the mobile layout
 * holds up to roughly 900px and the desktop one takes over above it, which is
 * what the handoff asks for.
 */

/* ---- Tokens -------------------------------------------------------------
   Named after what they are, not what they look like: `--ink` rather than
   `--near-black`, so a colour can change without every name becoming a lie. */

:root {
  /* The two grounds. The page alternates between them in bands. */
  --dark: #0e0d0b;
  --light: #f2ede6;

  /* Raised surfaces on the dark ground — cards, the booking panel. */
  --dark-raised: #1a1714;
  --dark-raised-hover: #221d19;

  /* Text. `--ink` on light, `--paper` on dark. */
  --ink: #1b1815;
  --ink-soft: #5c554d;
  --ink-faint: #9b948b;
  --paper: #f2ede6;
  /* Dimmed paper, as rgba so it works over any dark surface. */
  --paper-soft: rgba(242, 237, 230, 0.62);
  --paper-faint: rgba(242, 237, 230, 0.38);

  /* The record dot on Field Recording's action card — the one warm red in
     the palette, and used for nothing else. */
  --record: #e8735b;

  /* The accent. Used for every call to action and every active state. */
  --gold: #ffd897;
  --gold-dim: rgba(255, 216, 151, 0.14);
  --gold-edge: rgba(255, 216, 151, 0.4);

  /* The rust band. The sticky contact bar, the section eyebrows, and the
     first service card on the hub — the design footnotes it #8C3C1F, which
     is this. */
  --rust: #8c3c1f;

  /* The second and third service cards. One palette warming as it goes down
     the page: rust, then clay, then a brown that is nearly the background.
     Only the services hub uses these two — see design 14a. */
  --clay: #8c543f;
  --clay-deep: #6b4030;

  /* Hairlines. Two, because a line on dark and a line on light are different
     colours at the same opacity. */
  --line-on-dark: rgba(242, 237, 230, 0.12);
  --line-on-light: rgba(27, 24, 21, 0.1);

  /* Type. One family — the variable font covers 100–900 in a single file, so
     asking for 800 costs no extra download. */
  --font: "Raleway", system-ui, -apple-system, "Segoe UI", sans-serif;

  /* Technical labels: timecodes, spec keys, eyebrows on the About page.
     The system stack rather than a webfont — these are 9–10px strings of
     digits and capitals, and downloading a face for them would cost more
     than the whole page's text. Added 13-09-2026 with the About page,
     which is the first design to ask for one. */
  --font-mono: ui-monospace, SFMono-Regular, Menlo, "Cascadia Mono", monospace;

  /* The page gutter, and the one value that changes between breakpoints.
     Everything that spans the page reads this rather than repeating 44px. */
  --gutter: 44px;

  --radius: 16px;
  --radius-lg: 20px;
  --radius-pill: 999px;

  /* Depth. The design's panels float; these are its exact shadows. */
  --shadow-card: 0 14px 34px rgba(0, 0, 0, 0.45);
  --shadow-panel: 0 30px 70px rgba(27, 24, 21, 0.22);

  /* One duration for everything. The design asks for short and subtle;
     a single value is what keeps it consistent. */
  --quick: 0.18s ease;
}

@media (max-width: 900px) {
  :root {
    --gutter: 20px;
  }
}

/* ---- Reset --------------------------------------------------------------
   Only what is needed. A full reset undoes browser defaults that are correct
   and then re-adds them, which is a lot of CSS to end up where you started. */

*,
*::before,
*::after {
  box-sizing: border-box;
}

body {
  margin: 0;
  background: var(--dark);
  color: var(--paper);
  font-family: var(--font);
  font-size: 15.5px;
  line-height: 1.65;
  /* Kerning and ligatures are on by default in most browsers; this makes it
     explicit rather than depending on it. */
  text-rendering: optimizeLegibility;
  -webkit-font-smoothing: antialiased;

  /* **The type is the size the design says, on a phone too.**

     Mobile Safari and Chrome inflate text they judge too small for a narrow
     column — a heuristic from the days of desktop pages pinch-zoomed on a
     phone. It scales the *type* and leaves padding and borders alone, so the
     small uppercase labels this design uses everywhere came out several
     times their size inside boxes that had not grown: the pair chips read as
     bloated and loosely spaced while their CSS matched the reference
     exactly.

     Safe to switch off only because the layout is genuinely responsive: the
     inflation exists to rescue pages that are not, and every band here has a
     phone width. Not a zoom lock — `user-scalable=no` would stop somebody
     pinching to read something, which this does not touch. */
  text-size-adjust: 100%;
  -webkit-text-size-adjust: 100%;
}

img {
  max-width: 100%;
  /* Without this an image keeps its intrinsic height while max-width shrinks
     it, and every photograph on the page is subtly squashed. */
  height: auto;
  display: block;
}

a {
  color: inherit;
}

h1,
h2,
h3,
p,
ul,
ol {
  margin: 0;
}

ul,
ol {
  padding: 0;
  list-style: none;
}

button {
  font: inherit;
  color: inherit;
  cursor: pointer;
}

/* Every interactive control gets a visible focus ring, and it is the same one
   everywhere. Browsers only show :focus-visible for keyboard focus, so this
   costs a mouse user nothing and is the whole of keyboard navigation for
   somebody who needs it. */
:where(a, button, input, select, textarea, summary):focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 3px;
  border-radius: 4px;
}

/* Honour a system preference for less movement. The design's transitions are
   subtle, but "subtle" is not the same as "safe" for somebody with a
   vestibular disorder. */
@media (prefers-reduced-motion: reduce) {
  *,
  *::before,
  *::after {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
    scroll-behavior: auto !important;
  }
}

/* Text for a screen reader and nobody else.
   `clip-path` with a 1px box rather than `display:none`, which removes it from
   the accessibility tree as well, and rather than `width:0`, which some
   screen readers skip. Used by the navigation's burger and the carousel's
   arrows, where the visible content is a glyph that announces as nothing. */
.visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
  border: 0;
}

/* ---- Skip link ----------------------------------------------------------
   The first thing a keyboard user reaches. Off-screen until focused, then
   placed over the navigation rather than shifting the page down. */

.skip-link {
  position: absolute;
  left: -9999px;
  z-index: 100;
  padding: 12px 20px;
  background: var(--gold);
  color: var(--ink);
  font-weight: 700;
  font-size: 11px;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  text-decoration: none;
  border-radius: var(--radius-pill);
}

.skip-link:focus {
  left: var(--gutter);
  top: 12px;
}

/* ---- Bands --------------------------------------------------------------
   The page is a stack of full-width bands, alternating ground. Padding is
   vertical only; horizontal spacing is the gutter, so a band can hold
   full-bleed content by opting out. */

.band {
  padding-left: var(--gutter);
  padding-right: var(--gutter);
}

.band--dark {
  background: var(--dark);
  color: var(--paper);
}

.band--light {
  background: var(--light);
  color: var(--ink);
}

/* ---- Type ---------------------------------------------------------------
   The design specifies exact sizes per element rather than a scale. These are
   the shared ones; anything used once lives with its component. */

.eyebrow {
  display: flex;
  align-items: center;
  gap: 10px;
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.24em;
  text-transform: uppercase;
  color: var(--gold);
}

/* The rule before an eyebrow's text. A pseudo-element rather than an empty
   span: it is decoration, and decoration does not belong in the document for
   a screen reader to announce. */
.eyebrow::before {
  content: "";
  width: 26px;
  height: 1px;
  background: currentColor;
  flex: none;
}

.band--light .eyebrow {
  color: var(--rust);
}

/* ---- Buttons ------------------------------------------------------------
   Three kinds, all pills. `.button` is the shape; the modifier is the weight
   of the invitation. */

.button {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 8px;
  padding: 11px 20px;
  border: 1px solid transparent;
  border-radius: var(--radius-pill);
  background: none;
  font-weight: 700;
  font-size: 10.5px;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  text-decoration: none;
  white-space: nowrap;
  transition: background var(--quick), color var(--quick),
    border-color var(--quick);
}

/* The one that asks for the sale. */
.button--gold {
  background: var(--gold);
  color: var(--ink);
}

.button--gold:hover {
  background: #fff;
}

/* Present but quieter — the two secondary actions in the contact bar. */
.button--outline {
  border-color: rgba(255, 216, 151, 0.7);
  color: var(--gold);
}

.button--outline:hover {
  background: var(--gold-dim);
}

/* ---- Navbar -------------------------------------------------------------
   Sticky on mobile, static on desktop — the design's choice, and the right
   one: a fixed bar costs 60px of a 390px-tall viewport on every scroll. */

.nav {
  display: flex;
  align-items: center;
  justify-content: space-between;
  padding: 20px var(--gutter);
  background: var(--dark);
}

.nav__brand {
  display: flex;
  align-items: center;
  gap: 12px;
  text-decoration: none;
}

.nav__logo {
  width: 34px;
  height: 34px;
  object-fit: contain;
}

.nav__wordmark {
  font-weight: 800;
  font-size: 15px;
  line-height: 1;
  letter-spacing: 0.28em;
  color: var(--paper);
}

/* The links and the Hire button share one pill on desktop. */
.nav__pill {
  display: flex;
  align-items: center;
  gap: 14px;
  padding: 8px 8px 8px 26px;
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius-pill);
  background: rgba(242, 237, 230, 0.07);
}

.nav__links {
  display: flex;
  align-items: center;
  gap: 26px;
}

.nav__link {
  font-weight: 600;
  font-size: 11px;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  text-decoration: none;
  color: rgba(242, 237, 230, 0.66);
  transition: color var(--quick);
}

.nav__link:hover {
  color: var(--paper);
}

/* Which page you are on. `aria-current="page"` rather than a class, so the
   fact is in the document for a screen reader and the styling reads it —
   one source, and the visual and announced states cannot disagree. */
.nav__link[aria-current="page"] {
  color: var(--paper);
}

/* The burger is desktop-hidden rather than mobile-added, so the markup is the
   same at both breakpoints and only its visibility changes. */
.nav__burger {
  display: none;
  flex: none;
  width: 44px;
  height: 44px;
  align-items: center;
  justify-content: center;
  border: 1px solid rgba(242, 237, 230, 0.16);
  border-radius: 50%;
  background: none;
  /* The handoff's own strength, and a step down from `--paper`: the icon
     sits beside a gold Hire button, which is the one thing on that row
     anybody is meant to press. */
  color: rgba(242, 237, 230, 0.75);
}

/* Only where there is a pointer to hover with. A touch screen fires this on
   tap and then holds it, which leaves the button looking pressed after the
   drawer has opened — and `aria-expanded` is what says pressed here. */
@media (hover: hover) and (pointer: fine) {
  .nav__burger:hover {
    background: rgba(242, 237, 230, 0.08);
  }
}

/* ---- Three soundwaves, and an X made of two ------------------------------
   `claude_designs/design_handoff_wave_menu`, 28-09-2026.

   **The shape is in the markup; only the motion is here.** The handoff sets
   `d` as an inline style, which this site's CSP discards along with every
   other style attribute — so the paths are `d` attributes and `data-wave-open`
   in shell.html, and nav.ts swaps them. A `d` attribute participates in the
   cascade as a presentation attribute, so changing it moves the *computed*
   value and this transition runs: measured in Chrome mid-flight at
   `path("M 1.00373 4.9987…")`, genuinely interpolating between the two.

   Safari does not animate `d`, so the icon snaps there — agreed 28-09-2026,
   against tweening the strings by hand in a bundle that loads on every page.
   The shape still changes, which is the half that matters.

   **No reduced-motion block**, deliberately: the rule at the top of this file
   already cuts every transition on `*` with `!important`. One written here
   would be dead on arrival, which this project has done once already. */

.nav__waves {
  display: block;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.6;
  stroke-linecap: round;
}

.nav__waves path {
  transition: d 0.42s cubic-bezier(0.65, 0, 0.35, 1), opacity 0.25s ease;
}

/* The middle wave collapses to a point under the crossing arms, so it is
   faded rather than left as a dot in the middle of the X. Keyed on the
   button's own `aria-expanded` — the state a screen reader is told, so what
   is heard and what is seen cannot drift. */
.nav__burger[aria-expanded="true"] .nav__waves-middle {
  opacity: 0;
}

.nav__drawer {
  display: none;
}

@media (max-width: 900px) {
  /* **Anything scrolled to lands below the nav, not under it.**

     The nav is sticky at this width and static above it, so this fault is a
     phone and tablet one only — which is why it went unseen on a desktop.
     Scrolling an element to the top of the viewport puts it *behind* the
     69px bar: `elementFromPoint` at a carousel label's own top-left corner
     returns the nav. The label is then half-legible through a 94% opaque
     background, which reads as clipped text rather than as a covered one.

     **`scroll-padding-top` on the scroller, not `scroll-margin-top` on the
     element.** Three elements had already been patched one at a time — the
     brief, its bounce panel and the gear list's kits — and each was found
     only when somebody noticed that one. One declaration on the scroll
     container covers every anchor, every `scrollIntoView` and every
     browser-driven focus scroll, including the ones nobody has written yet.

     80px rather than 69: the bar plus a little air, so what you land on does
     not sit flush against it. */
  :root {
    scroll-padding-top: 80px;
  }

  .nav {
    position: sticky;
    top: 0;
    z-index: 60;
    /* Not fully opaque: content scrolling under it stays faintly visible,
       which is what tells somebody the page is moving. */
    background: rgba(14, 13, 11, 0.94);
    border-bottom: 1px solid rgba(242, 237, 230, 0.09);
    padding: 12px var(--gutter);
  }

  .nav__logo {
    width: 28px;
    height: 28px;
  }

  .nav__wordmark {
    font-size: 12px;
    letter-spacing: 0.24em;
  }

  /* The pill loses its border and its links; only Hire and the burger stay. */
  .nav__pill {
    gap: 10px;
    padding: 0;
    border: none;
    background: none;
  }

  .nav__links {
    display: none;
  }

  .nav__burger {
    display: inline-flex;
  }

  /* Shown by the island when open. Without JavaScript the drawer never opens,
     which is why the same links are also in the footer — see the note there. */
  .nav__drawer[data-open="true"] {
    display: block;
    position: sticky;
    top: 68px;
    z-index: 55;
    background: #14120f;
    border-bottom: 1px solid rgba(242, 237, 230, 0.09);
  }

  .nav__drawer a {
    display: block;
    padding: 15px var(--gutter);
    border-bottom: 1px solid rgba(242, 237, 230, 0.07);
    font-weight: 600;
    font-size: 12px;
    letter-spacing: 0.14em;
    text-transform: uppercase;
    text-decoration: none;
    color: rgba(242, 237, 230, 0.66);
  }

  .nav__drawer a[aria-current="page"] {
    color: var(--paper);
  }
}

/* ---- The contact bar ----------------------------------------------------
   Full-bleed: it sits inside a guttered band and pulls back out, so the rust
   reaches both edges while its buttons stay on the page's rhythm.

   **It only sticks on the homepage** — decided 01-09-2026. A bar that follows
   somebody down every page is one they stop seeing, and on a page they came to
   read it covers the thing they came for. Everywhere else it sits where it
   falls, hugging the footer: still the last thing on the page, no longer the
   thing on top of it. */

.contactbar {
  display: flex;
  align-items: center;
  justify-content: center;
  /* The box the pin is placed against — 24-09-2026. It sits in the bar's
     right corner and is out of the flow, so the two ways of writing to the
     studio and the gold button stay centred in the bar rather than being
     shifted left by a control that is a preference rather than an action.

     **Every rule that stops the bar sticking sets `relative` for this
     reason**, not `static`: a static bar is not a containing block, and the
     pin would jump to the corner of the *viewport*. No offsets are set, so
     the bar sits exactly where `static` put it. */
  position: relative;
  gap: 10px;
  /* **No negative side margins**, and that is the fix for a real overflow.
     They were here to bleed the rust colour past an inset parent — but every
     page puts this bar directly in `<main>`, which has no padding of its own,
     so there was nothing to pull against and the bar simply became two
     gutters wider than the page. The symptom was the whole document shifted
     left with content running off the right edge, on all nine pages that
     draw it. Found 08-09-2026 while measuring the hire page on a phone.

     The bar is already full width; `padding` alone is what keeps its buttons
     off the edges. */
  margin: 66px 0 0;
  padding: 16px var(--gutter);
  background: var(--rust);
  border-top: 1px solid var(--gold);
}

/* The homepage's, and only the homepage's. `bottom` is what makes a sticky
   element stop near the viewport edge; without it the property does nothing
   at all, which is a quiet way for this to look applied and not be.

   **12px on anything touched, 0 only under a mouse — 22-09-2026.** Safari
   on iOS 27 reads a bar that touches the bottom of the viewport as the
   site's own toolbar, paints its colour into Safari's toolbar, and keeps
   that colour for the life of the page: past the footer and under the
   full-screen player. Ten experiments on the owner's phone, in CLAUDE.md;
   a gap beneath the bar is the one thing its rule cannot see past. The gap
   is the base, and the flush bar the owner wanted on a desktop is the
   exception below — by pointer rather than by width alone, because an
   iPhone Pro Max on its side is 932px wide and would otherwise cross the
   site's 900px line straight back into the fault. A test holds both. */
.contactbar--sticky {
  position: sticky;
  bottom: 12px;
  z-index: 50;
}

@media (min-width: 901px) and (hover: hover) and (pointer: fine) {
  .contactbar--sticky {
    bottom: 0;
  }
}

/* Out of the way of the faders — 22-09-2026, from a beta tester. On a
   phone held upright the bar rode over the bottom of the video player's
   open layers panel and covered the faders somebody was dragging. The
   player puts `ba-layers-open` on the root while its inline panel is
   open, and for that long the bar stops sticking and sits where it falls,
   above the footer — still on the page, still reachable, just not on top
   of the faders. In that orientation only: on its side the panel is
   beside the picture and the bar covers nothing. Unstuck rather than
   hidden, on the owner's word: the invitation stays where a scroll finds
   it. */
@media (max-width: 900px) and (orientation: portrait) {
  html.ba-layers-open .contactbar--sticky {
    /* `relative` rather than `static`, so the pin in the corner stays placed
       against the bar — see the base rule. Identical in flow, and the
       z-index goes with the sticking it belonged to. */
    position: relative;
    z-index: auto;
  }
}

/* Released by the visitor — 24-09-2026, asked for the same day the studio
   gained the policy that can take this choice away.

   **The class is only ever added by the island**, so with no JavaScript the
   bar sticks exactly as it always has: the enhancement adds, never subtracts.
   And it is added nowhere at all under a forced policy, because the server
   then renders no switch to add it — which is what makes `forced-on`
   unescapable rather than merely undrawn.

   It drops the sticking and not the `bottom`: a second `bottom: 0` on this
   selector would collide with the mouse-only rule above, where a test asserts
   there is exactly one. `relative` rather than `static` because the pin is
   placed against the bar — see the base rule. */
html.contactbar-static .contactbar--sticky {
  position: relative;
  z-index: auto;
}

/* The switch itself, drawn from `aria-checked` rather than from a class this
   island would have to keep in step with it — the rule the admin's chips and
   the snap toggle already follow.

   Pinned is the filled state, because that is the bar doing something;
   released is the hairline every other button in the row wears. The mark is
   the same `.button__icon` the email and WhatsApp buttons use, so it takes
   `currentColor` and moves with hover and focus. */
/* **In the right corner, not in the row — the owner's word, 24-09-2026.**
   It sat beside the gold button, which put a preference in among the two ways
   of writing to the studio and the one action the bar exists for. Out of the
   flow, so those three stay centred in the bar whatever this does; against
   the gutter, so it lines up with everything else on the page's edge. */
/* **The mount point is a flex item too, and an empty one still counts.**
   React mounts the pin inside a `data-island` wrapper, which stays in the
   row: with the pin itself out of the flow the wrapper is zero-wide, but the
   row's `gap` still applies to it — measured as the three centred controls
   sitting 5px left of centre. `display: contents` takes the wrapper out of
   layout altogether; the pin inside is positioned against the bar either
   way, because the wrapper is not what it is placed against. */
.contactbar > [data-island="contact-bar-pin"] {
  display: contents;
}

.contactbar__pin {
  position: absolute;
  right: var(--gutter);
  top: 50%;
  transform: translateY(-50%);
}

/* **Smaller under a mouse — the owner's word, 24-09-2026.** At the size of
   the buttons beside it the pin reads as a fourth way of getting in touch,
   which it is not: it is a preference about the bar, and the quietest thing
   on it.

   Gated on hover and a fine pointer as well as width, not on width alone —
   the contact bar's own rule, and the right axis here: what decides this is
   whether a *hand* or a *cursor* presses it, and a finger needs the 42px the
   base rule gives. An iPhone Pro Max on its side is 932px wide and keeps the
   big target, which a width-only split would have taken away. */
@media (min-width: 901px) and (hover: hover) and (pointer: fine) {
  /* **`.contactbar .contactbar__pin`, not `.contactbar__pin`.** `.button--icon`
     sets `padding: 10px 16px` and is declared *after* this block, so at equal
     specificity it won on source order and the padding here did nothing — the
     trap this stylesheet has now recorded five times, measured as a pin that
     stayed 50px wide while the rule looked perfectly correct. Specificity
     rather than a move, so this cannot come undone by a later tidy-up. */
  .contactbar .contactbar__pin {
    /* **The gap goes with it.** `.button` puts 8px between its contents, and
       the only contents here are the mark and the `.visually-hidden` name, so
       8 of those pixels were a gap beside a span nobody can see. */
    gap: 0;
    padding: 8px;
  }

  .contactbar__pin .button__icon {
    width: 16px;
    height: 16px;
  }
}

.contactbar__pin[aria-checked="true"] {
  background: var(--gold-dim);
  border-color: var(--gold);
}

/* No sticky contactbar when in landscape mode on small screens */
@media (max-width: 932px) and (orientation: landscape) {
  .contactbar--sticky {
    position: relative;
    z-index: auto;
  }
}

/* Glass — asked for 22-09-2026, after the gap, for the stuck bar; and the
   same evening for every bar, so the pages match the homepage. A bar
   riding over the page reads better as a pane the page shows through
   than as a solid band, and it is the look the phone's own toolbar has;
   in the flow above the footer the same rust at just over half over the
   page's dark reads as the same colour, which is what was asked for. The
   gold line and the buttons still sit on something. Inside `@supports`,
   because a browser without the blur would show the page *sharp* through
   a half-transparent bar, which is worse than the solid one it had; the
   prefixed property is what Safari still needs, and the test asks for
   both. */
@supports (backdrop-filter: blur(1px)) or (-webkit-backdrop-filter: blur(1px)) {
  .contactbar {
    background: rgba(140, 60, 31, 0.58);
    -webkit-backdrop-filter: blur(18px) saturate(140%);
    backdrop-filter: blur(18px) saturate(140%);
  }
}

@media (max-width: 900px) {
  .contactbar {
    /* Centred, the same as desktop — the base rule already says so, and this
       block only changes the spacing.

       `space-evenly` was tried here and pushes the outer two buttons against
       the gutters, which reads as three separate things rather than one
       group. A slightly wider gap than desktop's is enough to keep them from
       crowding on a narrow screen. */
    gap: 12px;
    padding: 12px var(--gutter);
    margin-top: 26px;
  }
  /* **A button is as wide as its label, the same as on desktop.** `flex: 1`
     was here so "Hire" would take everything the two marks left — which on a
     phone stretched one word across most of the screen and made the bar read
     as a full-width banner with two buttons stuck to its side, rather than as
     three controls.

     The row is centred with a gap, so the three sit together and the rust
     band still reaches both edges. Only the type shrinks. */
  .contactbar .button {
    padding: 14px 18px;
    font-size: 10px;
    letter-spacing: 0.12em;
  }

  /* **An icon button takes only what it needs.** A square holding a 20px mark
     given a third of the row would sit in the middle of an empty box, and the
     button that carries a word would lose the space to it. Two of the three
     are marks now, so this is most of the row's layout. */
  .contactbar .button--icon {
    flex: 0 0 auto;
    padding: 10px 14px;
  }
}

/* A button whose whole label is a picture.

   Only the padding, because `.button` is already a centred inline-flex box —
   restating that here would be two places to change one layout. A mark needs
   less horizontal room than a word, and the 20px `letter-spacing` padding
   would otherwise leave it floating in an oval. */
.button--icon {
  padding: 10px 16px;
}

/* `currentColor` on the path is what makes this work: the mark takes the
   button's colour, so hover and focus move it too. An <img> could not do
   that, which is why this is an inline SVG. */
.button__icon {
  display: block;
}

/* ---- Footer ------------------------------------------------------------- */

.footer {
  padding: 54px var(--gutter) 20px;
  background: var(--dark);
  color: var(--paper);
  display: flex;
  gap: 48px;
}

.footer__brand {
  width: 300px;
  flex: none;
}

.footer__wordmark {
  display: flex;
  align-items: center;
  gap: 12px;
  font-weight: 800;
  font-size: 13px;
  letter-spacing: 0.26em;
  text-decoration: none;
}

.footer__wordmark img {
  width: 30px;
  height: 30px;
  object-fit: contain;
}

.footer__blurb {
  margin-top: 16px;
  font-size: 12.5px;
  line-height: 1.75;
  color: rgba(242, 237, 230, 0.58);
}

.footer__columns {
  display: flex;
  gap: 36px;
  flex: 1;
}

.footer__column {
  flex: 1;
}

.footer__heading {
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--gold);
}

.footer__column li {
  font-size: 12.5px;
  line-height: 2.1;
}

.footer__column a {
  color: rgba(242, 237, 230, 0.64);
  text-decoration: none;
  transition: color var(--quick);
}

.footer__column a:hover {
  color: var(--paper);
}

.footer__bottom {
  display: flex;
  justify-content: space-between;
  gap: 16px;
  padding: 14px var(--gutter) 22px;
  background: var(--dark);
  font-size: 11px;
  color: rgba(242, 237, 230, 0.4);
}

/* The switch to the other language (Module 13, 13d-3): last on the bottom
   line, pushed to its right end, and as bright as the footer's links rather
   than the faded line it sits on — it is the one thing here a visitor
   presses. The press area is 44px; the negative margins keep that from
   making the line itself taller. Six pixels either side so the focus ring
   does not touch the word, pulled back by the same so the word, not its
   padding, stays on the gutter. */
.footer__language {
  display: inline-flex;
  align-items: center;
  min-height: 44px;
  padding: 0 6px;
  margin: -16px -6px -16px auto;
  font-size: 12.5px;
  color: rgba(242, 237, 230, 0.64);
  text-decoration: none;
  transition: color var(--quick);
}

.footer__language:hover {
  color: var(--paper);
}

.footer__language:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* The social links (Module 24): a row of their own between the columns and
   the copyright line. Its left edge is the gutter the logo and the line
   below start on — the press area is 44px and the logo inside it 20px, so
   the list is pulled back by the difference and the logo, not its padding,
   lines up. */
.footer__social {
  padding: 0 var(--gutter) 6px;
  background: var(--dark);
}

.footer__social ul {
  display: flex;
  flex-wrap: wrap;
  gap: 4px;
  margin: 0 0 0 -12px;
  padding: 0;
  list-style: none;
}

.footer__social a {
  display: flex;
  align-items: center;
  justify-content: center;
  width: 44px;
  height: 44px;
  color: rgba(242, 237, 230, 0.64);
  transition: color var(--quick);
}

.footer__social a:hover {
  color: var(--gold);
}

.footer__social a:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: -4px;
}

.footer__social svg {
  width: 20px;
  height: 20px;
  fill: currentColor;
}

@media (max-width: 900px) {
  .footer {
    flex-direction: column;
    gap: 32px;
    padding-top: 36px;
  }

  .footer__brand {
    width: auto;
  }

  .footer__columns {
    flex-wrap: wrap;
    gap: 24px 32px;
  }

  .footer__column {
    /* Two per row rather than four: four columns at 390px is four words
       stacked one letter wide. */
    flex: 1 1 40%;
  }

  .footer__bottom {
    flex-direction: column;
    gap: 4px;
  }

  /* In a column the line is a stack: the switch starts at the left like the
     rest, and its 44px is a row of its own rather than reaching into the
     line above. */
  .footer__language {
    align-self: flex-start;
    margin: 0 0 0 -6px;
  }
}

/* ---- Hero ---------------------------------------------------------------
   Two columns on desktop, one on mobile. The design gives the right column no
   gap and its own left padding, so the player's panel edge lands where the
   grid says rather than where a gap pushes it. */

.hero {
  padding-top: 44px;
  padding-bottom: 172px;
  overflow: hidden;
}

.hero__row {
  display: flex;
  align-items: stretch;
}

.hero__words {
  flex: 1;
  /* Without this a long unbroken word — a filename in a heading — makes the
     flex item refuse to shrink and pushes the player off the page. */
  min-width: 0;
  padding-top: 14px;
  padding-right: 28px;
}

.hero__heading {
  margin: 22px 0 0;
  font-weight: 800;
  font-size: 60px;
  line-height: 1.02;
  letter-spacing: -0.025em;
  max-width: 600px;
  /* Balances the last line rather than leaving one word alone on it. */
  text-wrap: pretty;
}

.hero__intro {
  margin-top: 20px;
  max-width: 470px;
  color: var(--paper-soft);
}

.hero__intro p {
  margin: 0 0 12px;
}

.hero__intro p:last-child {
  margin-bottom: 0;
}

.hero__player {
  flex: 1;
  min-width: 0;
  padding-left: 28px;
}

/* ---- Service routes -----------------------------------------------------
   Three cards, each a single link. The whole card is the target: a card that
   looks clickable but only responds on a small arrow is the usual way this
   pattern disappoints. */

.routes {
  display: flex;
  flex-direction: column;
  gap: 12px;
  margin-top: 34px;
  max-width: 560px;
}

.route__link {
  display: flex;
  align-items: center;
  gap: 16px;
  padding: 18px 20px;
  border-radius: var(--radius);
  background: var(--dark-raised);
  box-shadow: var(--shadow-card);
  text-decoration: none;
  transition: background var(--quick), transform var(--quick);
}

.route__link:hover {
  background: var(--dark-raised-hover);
  transform: translateY(-2px);
}

.route__index {
  width: 22px;
  flex: none;
  font-weight: 700;
  font-size: 9.5px;
  letter-spacing: 0.18em;
  color: var(--paper-faint);
}

.route__body {
  flex: 1;
  min-width: 0;
}

.route__title {
  display: block;
  font-weight: 700;
  font-size: 21px;
  line-height: 1.15;
  letter-spacing: -0.01em;
}

.route__text {
  display: block;
  margin-top: 4px;
  font-size: 12.5px;
  line-height: 1.5;
  color: rgba(242, 237, 230, 0.56);
}

.route__arrow {
  display: flex;
  align-items: center;
  justify-content: center;
  width: 34px;
  height: 34px;
  flex: none;
  border-radius: 50%;
  background: var(--gold-dim);
  color: var(--gold);
  font-size: 14px;
}

@media (max-width: 900px) {
  .hero {
    padding-top: 26px;
    padding-bottom: 30px;
  }

  /* One column, and the player above the cards — the design puts the proof
     of craft before the routes into it. */
  .hero__row {
    flex-direction: column;
  }

  .hero__words,
  .hero__player {
    padding-right: 0;
    padding-left: 0;
  }

  .hero__player {
    order: -1;
    margin-bottom: 24px;
  }

  .hero__heading {
    font-size: 36px;
    line-height: 1.04;
    max-width: none;
  }

  .hero__intro {
    font-size: 13.5px;
    max-width: none;
  }

  .routes {
    max-width: none;
  }

  .route__link {
    padding: 16px 18px;
  }

  /* No lift on touch: there is no hover to leave it in, so a card can stay
     raised after a tap. */
  .route__link:hover {
    transform: none;
  }

  .route__title {
    font-size: 17px;
  }

  .route__text {
    font-size: 11.5px;
  }
}

/* ---- The before/after band ----------------------------------------------
   The light band under the hero: the comparison player on the left, the
   behind-the-scenes photographs on the right. 3:2 on desktop, stacked on
   mobile — the design's split. */

.proof {
  padding-top: 130px;
  /*
    **The band needs its own bottom padding**, and having none was a fault
    hidden by the taller of the two columns.

    The row is the player beside the carousel. On a tall, narrow screen the
    carousel runs longer than the player, so its own height left a gap under
    the band and the spacing looked deliberate. On a wide screen both columns
    are short, nothing extends past the player, and it sat flush against the
    contact bar below.

    Not a media query: the gap belongs at every width. A query would only
    reinstate it where somebody happened to notice it missing, and the same
    fault would return at the next width nobody checked.
  */
  padding-bottom: 110px;
}

.proof__header {
  display: flex;
  align-items: flex-start;
  justify-content: space-between;
  gap: 32px;
  flex-wrap: wrap;
  margin-bottom: 34px;
}

.proof__heading {
  margin-top: 14px;
  font-weight: 800;
  font-size: 34px;
  line-height: 1.1;
  letter-spacing: -0.015em;
}

.proof__support {
  max-width: 320px;
  font-size: 13px;
  line-height: 1.6;
  color: var(--ink-soft);
}

.proof__row {
  display: flex;
  gap: 26px;
  align-items: flex-start;
}

/* 3:2 — the player earns the larger share, because it is the argument. */
.proof__player {
  flex: 3;
  min-width: 0;
}

.proof__carousels {
  flex: 2;
  min-width: 0;
  display: flex;
  flex-direction: column;
  gap: 26px;
}

@media (max-width: 900px) {
  .proof {
    padding-top: 36px;
    /* Both ends drop together. Inheriting the desktop 110px here would leave
       a third of a phone screen empty under the band. */
    padding-bottom: 44px;
  }

  .proof__header {
    display: block;
    margin-bottom: 24px;
  }

  .proof__heading {
    font-size: 28px;
    line-height: 1.08;
  }

  .proof__support {
    margin-top: 10px;
    max-width: none;
    font-size: 12.5px;
  }

  .proof__row {
    flex-direction: column;
    gap: 24px;
  }

  .proof__player,
  .proof__carousels {
    width: 100%;
  }
}

/* ---- Behind-the-scenes photographs --------------------------------------
   A list of every photograph, not a one-at-a-time carousel. The arrows and
   dots need JavaScript, and a carousel built as JavaScript shows a crawler
   one photo and somebody with scripting off none — see photos.html. */

.photos {
  border-radius: var(--radius-lg);
  overflow: hidden;
  background: #fff;
  box-shadow: 0 30px 70px rgba(27, 24, 21, 0.18);
}

/* 16 across, matching the frame below it — the design puts the tab row at
   `14px 16px 0` and the image frame at the same 16. An 18 here left the label
   two pixels out of line with the picture, which is the kind of thing that
   reads as "badly spaced" without being nameable. */
.photos__label {
  margin: 0;
  padding: 14px 16px 0;
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--ink-faint);
}

.photos__list {
  display: flex;
  flex-direction: column;
  gap: 18px;
  /* No bottom padding: the last slide's body already carries 18. */
  padding: 14px 16px 0;
}

.photos__image {
  width: 100%;
  border-radius: 14px;
  box-shadow: 0 14px 32px rgba(27, 24, 21, 0.2);
}

/* A padded box, not a bare top margin. Without horizontal padding the
   caption and the meta tiles ran to the card's edge while the image above was
   inset — which is what made the card look badly spaced.
   
   16 across rather than the design's 18, so the text lines up with the frame
   and the label above it. The design's own numbers put the tabs and the image
   at 16 and the body at 18, which is a two-pixel step nobody wants; matching
   the picture is the version that reads as deliberate. 18 top and bottom is
   the design's, and that part is right. */
.photos__body {
  padding: 18px 16px;
}

.photos__caption {
  font-weight: 700;
  font-size: 17px;
  line-height: 1.25;
  color: var(--ink);
}

.photos__description {
  margin-top: 6px;
  font-size: 12.5px;
  line-height: 1.65;
  color: var(--ink-soft);
}

/* Two tiles side by side, as the design draws them. `auto-fit` rather than
   two fixed columns, so a slide with only a location gets one full-width
   tile instead of one tile and a gap. */
/* Two equal tiles, wrapping to one column only when there genuinely is not
   room. `auto-fit` with a minimum let a single tile stretch the full width of
   a wide card, which read as a stray box rather than a pair. */
.photos__meta {
  display: grid;
  grid-template-columns: 1fr 1fr;
  gap: 10px;
  margin-top: 14px;
}

@media (max-width: 420px) {
  .photos__meta {
    grid-template-columns: 1fr;
  }
}

.photos__tile {
  padding: 12px 14px;
  border-radius: 12px;
  background: #f6f2ec;
}

.photos__tile dt {
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--ink-faint);
}

.photos__tile dd {
  margin: 2px 0 0;
  font-weight: 600;
  font-size: 12.5px;
  color: var(--ink);
}

@media (max-width: 900px) {
  .photos {
    border-radius: 18px;
  }

  .photos__caption {
    font-size: 16px;
  }

  .photos__description {
    font-size: 12px;
  }
}

/* ---- The carousel, once the island runs --------------------------------
   The server renders every photograph as a list; React replaces it with one
   frame and arrows. These rules style the replacement — the list's own
   styles above are what a visitor without JavaScript keeps. */

.photos__frame {
  position: relative;
  margin: 14px 16px 0;
  /* The body below supplies its own 18; this is only the gap the design draws
     between the picture and the counter. */
  border-radius: 14px;
  overflow: hidden;
  box-shadow: 0 14px 32px rgba(27, 24, 21, 0.2);
}

/* Focusable, so the arrow keys have somewhere to land — and it has to show
   that it is focused. */
.photos__frame:focus-visible {
  outline: 2px solid var(--rust);
  outline-offset: 2px;
}

.photos__frame .photos__image {
  border-radius: 0;
  box-shadow: none;

  /* **A ratio, not a height.** The frame still has to be fixed — the card
     must not jump as a portrait photograph follows a landscape one — but a
     fixed *pixel* height only suited the width this carousel first had, in
     the homepage's narrower column. On Field Recording it spans the whole
     page, and 300px there is a letterbox that crops a portrait shot to a
     strip. A ratio holds the card still at any width.

     3:2 rather than the design's 380px in a 1.4fr column, which works out at
     roughly the same shape: it is the proportion most cameras take, so the
     average photograph loses the least to the crop.

     `cover` still crops, and that is deliberate — `contain` would letterbox a
     portrait against a white card, which looks like a mistake rather than a
     choice. What changes is how much. */
  width: 100%;
  height: auto;
  aspect-ratio: 3 / 2;
  object-fit: cover;
}

.photos__arrow {
  position: absolute;
  top: 50%;
  transform: translateY(-50%);
  display: flex;
  align-items: center;
  justify-content: center;
  /* 44px: the smallest a touch target should be, and the size the design's
     mobile spec asks for throughout. */
  width: 44px;
  height: 44px;
  border: none;
  border-radius: 50%;
  background: rgba(255, 255, 255, 0.9);
  color: var(--ink);
  font-size: 16px;
  box-shadow: 0 4px 14px rgba(27, 24, 21, 0.25);
  transition: background var(--quick);
}

.photos__arrow:hover {
  background: #fff;
}

/* **Shown when asked for, not always** (04-11-2026, the owner's word): over
   the photo they covered it. A mouse asks by hovering — only on a screen
   that has one, or a phone's tap would leave a sticky hover behind — and a
   touch by tapping the photo (`--controls`, the island's). Keyboard focus on
   the frame or an arrow shows them too, or arrow keys and Tab would move
   through a carousel whose controls nobody can see — `:focus-visible`, not
   `:focus-within`, which a mouse click on the frame also sets and which
   would keep them up after the mouse has gone. Hidden, they cannot be
   pressed by accident; PREV / NEXT and the dots below are always there. */
.photos__frame .photos__arrow {
  opacity: 0;
  pointer-events: none;
  transition: opacity var(--quick), background var(--quick);
}

.photos__frame--controls .photos__arrow,
.photos__frame:focus-visible .photos__arrow,
.photos__frame:has(.photos__arrow:focus-visible) .photos__arrow {
  opacity: 1;
  pointer-events: auto;
}

@media (hover: hover) {
  .photos__frame:hover .photos__arrow {
    opacity: 1;
    pointer-events: auto;
  }
}

.photos__arrow--back {
  left: 12px;
}

.photos__arrow--next {
  right: 12px;
}

.photos__counter {
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--ink-faint);
  margin-bottom: 6px;
}

/* A reserve, so the card does not resize as captions of different lengths
   follow each other — the design asks for this explicitly. */
.photos__frame ~ .photos__body .photos__description {
  min-height: 42px;
}

/* PREV · dots · NEXT, above a hairline — the design's row inside the card.
   Named `__nav` rather than `__footer`, because `.footer` above is the page's
   own footer and one word for two things is a trap. */
.photos__nav {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 12px;
  margin-top: 16px;
  padding-top: 14px;
  border-top: 1px solid var(--line-on-light);
}

.photos__step {
  padding: 0;
  border: none;
  background: none;
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--ink-faint);
  transition: color var(--quick);
}

.photos__step:hover {
  color: var(--ink);
}

.photos__dots {
  position: relative;
  display: flex;
  align-items: center;
  gap: 8px;
}

.photos__dot {
  width: 6px;
  height: 6px;
  padding: 0;
  border: none;
  border-radius: 50%;
  background: rgba(27, 24, 21, 0.18);
  transition: background var(--quick);
}

.photos__dot[aria-current="true"] {
  background: var(--rust);
}

/* **Light dots on a dark card** (04-11-2026, the owner's word): the other
   photos' dots were dark ink at 18%, which vanished against the dark card and
   left the current red dot alone — nothing said there were more. The page's
   own light ink, the mirror of the white card's. `:not` keeps the current dot
   red whatever the order of the two rules. */
.photos--dark .photos__dot:not([aria-current="true"]) {
  background: rgba(242, 237, 230, 0.35);
}

/* The dot itself is 6px, which is far too small to hit. The button keeps its
   size and grows an invisible target around it. */
.photos__dot::before {
  content: "";
  position: absolute;
  width: 24px;
  height: 24px;
  margin: -9px;
}

.photos__dot {
  position: relative;
}

@media (max-width: 900px) {
  /* The design tightens the card's inset to 14 at 390px. All four have to
     move together, or the picture sits two pixels off the text beside it —
     the same misalignment the desktop card had. */
  .photos__label,
  .photos__list {
    padding-left: 14px;
    padding-right: 14px;
  }

  .photos__frame {
    margin: 14px 14px 0;
  }

  .photos__body {
    padding: 16px 14px;
  }

  .photos__frame .photos__image {
    /* Taller in proportion on a phone, where the card is narrow and 3:2
       leaves a picture too short to read. */
    aspect-ratio: 4 / 3;
  }

  /* Two lines of caption at 390px, so the card holds still. */
  .photos__frame ~ .photos__body .photos__description {
    min-height: 58px;
  }
}

/* ---- The booking card ---------------------------------------------------
   Module 6e. Tape Some's frame; Calendly's calendar.

   The design draws a month grid, a week number and five day cells. None of
   that is here, and that is the decision rather than an omission: Calendly
   owns the calendar, so a grid drawn on this page would be a promise it
   cannot keep — and one claiming Wednesday while Calendly offers Tuesday is
   worse than a card that claims nothing.

   What is kept is the frame: the waveform header, the "now booking" line and
   the CTA. */

.booking {
  margin-top: 26px;
  border-radius: 18px;
  overflow: hidden;
  background: #1a1714;
  box-shadow: 0 18px 44px rgba(0, 0, 0, 0.5);
}

.booking__wave {
  position: relative;
  height: 64px;
  background: #221d19;
}

.booking__wave svg {
  display: block;
  width: 100%;
  height: 64px;
}

/* "Now booking" — a statement about the studio, not about a particular week.
   It stays true without anything having to keep it true. */
.booking__status {
  position: absolute;
  left: 16px;
  top: 14px;
  display: flex;
  align-items: center;
  gap: 7px;
  margin: 0;
  font-weight: 700;
  font-size: 8.5px;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.7);
}

/* **The colour comes from the state**, the same three the hire page's
   indicator uses — so the two pages cannot disagree about how busy the studio
   is. Green available, amber busy, muted red full; the red is deliberately
   not a stop-sign, because that reads as something being broken rather than
   as a studio that is booked up.

   The base rule carries the shape and the glow, and each state supplies its
   own colour. `currentColor` on the shadow would be neater and is wrong here:
   the dot has no text, so there is no colour to inherit. */
.booking__dot {
  width: 6px;
  height: 6px;
  flex: none;
  border-radius: 50%;
}

.booking__dot--available {
  background: #7fd18b;
  box-shadow: 0 0 10px #7fd18b;
}

.booking__dot--busy {
  background: #e0a35c;
  box-shadow: 0 0 10px #e0a35c;
}

.booking__dot--full {
  background: #c96f5c;
  box-shadow: 0 0 10px #c96f5c;
}

/* **Dormant: the whole card rests, the button included.**

   When the studio says nothing about availability the card keeps its shape
   and its link and loses its colour, so it reads as resting rather than as a
   card whose status line failed to load.

   **Dimmed as a whole, which overrules my own objection — asked for
   13-09-2026.** I argued the call to action should keep full strength,
   because a greyed button looks disabled while still working. The studio's
   answer is that a dormant card should plainly look dormant, and that a
   visitor who presses anyway still reaches Calendly. Recorded rather than
   quietly reversed, so the trade-off is visible to whoever reads this next:
   the button is legible and reachable, it simply does not shout.

   **Opacity on the card, not on its parts.** The first version dimmed the
   waveform and the words separately and changed the card by 2.8 points of
   255 — about one percent, measured on the running site, and invisible.
   `#1a1714` against a near-black page has almost nowhere to fade to. One
   opacity on the whole card composites it against the page in a single step,
   which is what actually reads, and `grayscale` takes out the gold — the one
   saturated thing on the card, and therefore the one whose absence is
   noticed. */
/* Not saying how busy we are: the gold goes, the strength stays. */
.booking--unsaid {
  filter: grayscale(0.85);
}

/* Not saying *and* not taking bookings: the card rests.
   Both classes are on the element, so the filters would otherwise replace
   rather than combine — `filter` is not additive, and the later rule wins.
   Restated here so the grey survives the dimming. */
.booking--quiet {
  opacity: 0.5;
  filter: grayscale(0.85);
}

/* **The switched-off button: drawn, and plainly off.**

   Half strength, and not a link — see the template. The greying is the
   message rather than a side effect of the card resting, so it is stated on
   the button itself and survives whatever the card around it is doing.

   `cursor: default` because there is nothing to click; a pointer over a dead
   control is the last thing that suggests it might work. */
.booking__cta--off {
  opacity: 0.5;
  cursor: default;
}

/* Keeping the focus ring at full strength. A dimmed card is a design
   decision; a dimmed focus ring is an accessibility fault, and somebody
   reaching the button with a keyboard needs to see where they are. */
.booking--quiet .booking__cta:focus-visible {
  opacity: 1;
  filter: none;
}


.booking__body {
  padding: 16px 18px 18px;
}

.booking__heading {
  margin: 0;
  font-weight: 800;
  font-size: 20px;
  line-height: 1.05;
  letter-spacing: -0.01em;
  color: var(--paper, #f2ede6);
}

.booking__text {
  margin-top: 10px;
  font-size: 11px;
  line-height: 1.5;
  color: rgba(242, 237, 230, 0.6);
}

.booking__text p {
  margin: 0 0 0.6em;
}

.booking__text p:last-child {
  margin-bottom: 0;
}

/* The design's tan pill. A block, so the whole width is the target rather
   than the words in the middle of it. */
.booking__cta {
  display: block;
  margin-top: 14px;
  padding: 16px 20px;
  border-radius: var(--radius-pill, 999px);
  background: var(--gold, #ffd897);
  color: #1b1815;
  font-weight: 700;
  font-size: 11px;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  text-align: center;
  text-decoration: none;
  transition: background 0.18s ease;
}

.booking__cta:hover {
  background: #fff;
}

.booking__cta:focus-visible {
  outline: 2px solid var(--gold, #ffd897);
  outline-offset: 3px;
}

/* Where Tape Some is, on the contact page only — see contact.html. Lines
   rather than a run-on sentence, because an address is read as a block. */
.contact__address {
  display: flex;
  flex-direction: column;
  gap: 2px;
  margin-top: 20px;
  font-style: normal;
  font-size: 14px;
  line-height: 1.5;
  color: var(--ink-soft, #5c554d);
}

/* ---- The services hub ---------------------------------------------------
   Design 14a. Four cards, one per service, each a gradient swatch with an
   inset frame — one warm palette getting deeper down the page.

   The cards alternate sides on desktop and stack on mobile, which is why the
   template renders one list and this file does the alternating. Two templates
   for one set of content would be two places to change a card. */

.hub {
  padding-top: 40px;
  padding-bottom: 80px;
}

/* The heading and its paragraph sit on one row, the paragraph pushed right
   and narrow — the design sets it against the heading rather than under it. */
.hub__header {
  display: flex;
  align-items: flex-start;
  justify-content: space-between;
  gap: 40px;
  margin-bottom: 34px;
}

.hub__heading {
  margin: 0;
  font-weight: 800;
  font-size: 54px;
  line-height: 1.04;
  letter-spacing: -0.025em;
  max-width: 520px;
  text-wrap: pretty;
}

.hub__intro {
  max-width: 330px;
  padding-top: 10px;
  font-size: 13.5px;
  line-height: 1.6;
  color: var(--paper-soft);
}

.hub__intro p {
  margin: 0 0 10px;
}

.hub__intro p:last-child {
  margin-bottom: 0;
}

/* ---- The guide card -----------------------------------------------------
   "Tell us what's wrong with the sound." Darker than the cards below it and
   deliberately not part of the numbered set: it is a way in, not a service. */

.guide {
  position: relative;
  margin-bottom: 26px;
  padding: 26px 30px 34px;
  border-radius: var(--radius-lg);
  border: 1px solid var(--line-on-dark);
  background: linear-gradient(180deg, #16130f 0%, #100e0c 100%);
}

.guide__eyebrow {
  display: flex;
  align-items: center;
  gap: 10px;
  margin: 0;
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.24em;
  text-transform: uppercase;
  color: var(--gold);
}

/* The boxed "?" before the label. A span rather than a pseudo-element because
   the character is content the design draws, not a rule — but it is still
   decoration, so the template hides it from screen readers. */
.guide__mark {
  display: flex;
  align-items: center;
  justify-content: center;
  width: 18px;
  height: 18px;
  flex: none;
  border-radius: 5px;
  border: 1px solid var(--gold-edge);
  background: var(--gold-dim);
  font-size: 10px;
  letter-spacing: 0;
}

.guide__heading {
  margin: 14px 0 22px;
  font-weight: 800;
  font-size: 27px;
  line-height: 1.24;
  letter-spacing: -0.015em;
  max-width: 560px;
  text-wrap: pretty;
}

/* Three across on desktop, stacking below. `1fr` columns rather than flex so
   the three boxes are the same width whatever their text length — a row of
   options that are different sizes reads as a ranking. */
.guide__options {
  display: grid;
  grid-template-columns: repeat(3, 1fr);
  gap: 12px;
  margin: 0;
  padding: 0;
  list-style: none;
}

.guide__link {
  display: block;
  height: 100%;
  padding: 16px 18px;
  border-radius: var(--radius);
  border: 1px solid var(--line-on-dark);
  background: var(--dark-raised);
  color: inherit;
  text-decoration: none;
  transition: background var(--quick), transform var(--quick);
}

.guide__link:hover {
  background: var(--dark-raised-hover);
  transform: translateY(-2px);
}

/* An option that resolves to no page — see `guide_options`. It keeps the box
   so the row stays even, and loses the hover, which would otherwise promise
   something to press. */
.guide__link--plain,
.guide__link--plain:hover {
  background: var(--dark-raised);
  transform: none;
  cursor: default;
}

.guide__title {
  display: block;
  font-weight: 700;
  font-size: 14.5px;
  line-height: 1.3;
}

.guide__text {
  display: block;
  margin-top: 6px;
  font-size: 12.5px;
  line-height: 1.5;
  color: rgba(242, 237, 230, 0.56);
}

/* ---- The service cards -------------------------------------------------- */

.services {
  display: flex;
  flex-direction: column;
  gap: 22px;
  margin: 0;
  padding: 0;
  list-style: none;
}

/* The swatch. Each card names its own gradient below; this is the shape they
   share. */
.service {
  border-radius: var(--radius-lg);
  background: var(--dark-raised);
  overflow: hidden;
}

/* **A run of bands is one panel, not three that nearly join — 25-09-2026,
   reported with a crop of the artifact.**

   The rule above is the *card's* shape, shared by the hub's four cards and —
   on a service page — by three full-width bands. Cards sit apart in a grid,
   so the corner is a corner. Bands are stacked with no margin at all between
   them, and where two rounded corners meet, the page's darker ground shows
   through the gap between the two curves: a shape that comes to a point at
   both ends and reads as a small arrowhead at each edge of the seam. Three
   bands, two seams, four of them per page.

   **Only the corners that touch are flattened.** The first band keeps its
   top and the last keeps its bottom, so the run is still the rounded panel
   the design draws — the change is that it now reads as one panel rather
   than as three with a fault at every join. Nothing moves and nothing
   resizes; the same rectangle is drawn with two of its corners square.

   **`.service.band` rather than `.band`**, because a band is only a problem
   when it is *also* drawing the card's shape: every other band on the site
   has no radius to leave a gap with. And the compound is (0,2,0) against the
   rule above at (0,1,0), so this wins on specificity rather than on source
   order — the trap this stylesheet has recorded five times. */
.service.band + .service.band {
  border-top-left-radius: 0;
  border-top-right-radius: 0;
}

.service.band:has(+ .service.band) {
  border-bottom-left-radius: 0;
  border-bottom-right-radius: 0;
}

/* The design's inset frame: a hairline rectangle 16px inside the card edge.
   Padding on the frame rather than a border on the card, so the gradient runs
   to the corner behind it. */
.service__frame {
  margin: 16px;
  padding: 22px 26px 26px;
  border-radius: var(--radius);
  border: 1px solid rgba(242, 237, 230, 0.16);
  display: flex;
  flex-direction: column;
}

.service__label {
  display: flex;
  align-items: baseline;
  gap: 8px;
  margin: 0;
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.72);
}

.service__number {
  color: rgba(242, 237, 230, 0.5);
  letter-spacing: 0.2em;
}

.service__body {
  min-width: 0;
  /* The words keep a reading measure even though the card is far wider and
     the player below runs its full width. A line of prose across 1352px is
     hard to track back from the end of one line to the start of the next —
     the reason every column on this site has a ceiling. */
  max-width: 640px;
}

/* Words and player, side by side from 1280px and stacked below it.
 *
 * The reference draws these side by side, and that works — but only where
 * both halves get the width they need, which is the thing three earlier
 * attempts got wrong by squeezing the player into a third of the card.
 *
 * What the player actually needs, from its own stylesheet: `minmax(140px,
 * 1fr)` faders, so a set of up to seven stems wants five columns to sit in
 * two rows. That is 775px, and it is the cap below. What the words need is a
 * readable column — 380px before the heading starts breaking badly.
 *
 * 775 + 40 + 380 is 1195px of card, which a 1280px page provides and a
 * 1200px one does not. Hence the breakpoint. Below it the card stacks, which
 * is the design's own mobile arrangement and gives the player the full width
 * rather than a squeezed third.
 *
 * Stacked is the *default* and the row is the enhancement, so the narrow case
 * needs no override — one rule turning it on rather than two disagreeing.
 */
.service__row {
  display: flex;
  flex-direction: column;
  gap: 30px;
  padding-top: 34px;
}

@media (min-width: 1280px) {
  .service__row {
    flex-direction: row;
    align-items: center;
    gap: 40px;
  }

  /* The design alternates which side the player sits on down the page. Only
     where there are two columns to swap — stacked, reversing would put the
     player above the heading that introduces it. */
  .service:nth-child(even) .service__row {
    flex-direction: row-reverse;
  }

  /* Takes what the player leaves, rather than a share of the row: the player
     is capped, so a proportional split would leave a gap on a wide screen.
     The 640px ceiling above still applies and is still right — at 1920 this
     column would otherwise be 933px of prose. */
  .service__body {
    flex: 1;
    min-width: 380px;
  }
}

/* The player is held by its *width*, and the aspect ratio does the rest.
 *
 * **Not `max-height` on the stage.** That was the previous attempt and it
 * cropped the picture: the stage is `aspect-ratio: 16 / 9` and the video is
 * `object-fit: cover`, so limiting the height keeps the full width and fills
 * it with the middle band of the frame — heads and feet cut off. The height
 * is an *output* here, not something to set.
 *
 * So the ceiling goes back on the width, which is what the aspect ratio reads
 * from — but at a figure derived from the height wanted rather than guessed
 * at. 775px gives a 420px-tall picture, and leaves the fader grid five
 * columns of its `minmax(140px, 1fr)`, so a seven-stem set is two rows rather
 * than the four it wrapped to at 420px.
 *
 * The earlier caps failed because they were chosen to make the *picture*
 * smaller and ignored what the grids underneath it needed. This one is the
 * other way round.
 */
.service__player {
  width: 100%;
  max-width: 775px;
}

/* The label row's trailing phrase — what the service covers. Dimmed against
   the title beside it: the title is the name, this is the detail. */
.service__covers {
  color: rgba(242, 237, 230, 0.45);
}

/* The line above the cards saying the names open. Not shown wide, where there
   is nothing to tap and the roles are printed inline — a hint describing a
   control that is not there is worse than no hint. Off by default and turned
   on in the phone block, the same way round as everything else in the fold. */
.services__hint {
  display: none;
}

@media (max-width: 900px) {
  .services__hint {
    display: block;
    margin: -14px 0 18px;
    font-size: 12.5px;
    line-height: 1.5;
    color: rgba(242, 237, 230, 0.5);
  }
}

/* ---- The role fold — MOBILE-ROLE-FOLD-18 --------------------------------
   Narrow, the covers list folds behind the service name. Wide, it is printed
   inline as the design draws it and there is nothing to open.

   **Everything here is off by default and switched on in the phone block.**
   The wide rendering is the one the design specifies, so it is what the
   cascade gives without a media query — the same reasoning `.service__row`
   already states about stacked being the default and the row the
   enhancement. One rule turning the fold on, rather than two disagreeing. */

/* The control is drawn nowhere; the label is what is seen. Clipped rather
   than `display: none`, so it stays in the tab order — a checkbox taken out
   of it cannot be reached, and the row would be unopenable with a keyboard.
   `.visually-hidden` in the markup does that; this rule only stops the
   hidden input taking a line box in the flex label row. */
.service__toggle {
  position: absolute;
}

/* Wide, the name is plain text in the label row and the fold is not a
   control: no underline, no chevron, no pointer. */
.service__fold {
  display: contents;
}

.service__chevron,
.service__rolewrap {
  display: none;
}

@media (max-width: 900px) {
  /* The head row: number, name, chevron. `space-between` puts the chevron at
     the far edge whatever the name's length, which is the reference's
     anatomy. */
  .service__label {
    flex-wrap: wrap;
    align-items: center;
  }

  /* The whole row is the tap target, not the words — the reference is
     explicit about this, and 44px is the floor it names. */
  .service__fold {
    display: flex;
    flex: 1;
    align-items: center;
    justify-content: space-between;
    gap: 10px;
    min-height: 44px;
    cursor: pointer;
  }

  /* Signal one: a dashed underline under the name. **Dashed, not solid** —
     solid reads as a link, and this opens a block rather than going
     anywhere. */
  .service__name {
    padding-bottom: 2px;
    border-bottom: 1px dashed rgba(242, 237, 230, 0.5);
  }

  .service__toggle:checked + .service__label .service__name {
    border-bottom-color: rgba(242, 237, 230, 0.85);
  }

  /* Signal two: a circled chevron at the far end. Two signals rather than
     one, because on a dark gradient card the underline alone reads as
     decoration and the chevron alone is easy to miss beside a heavy
     heading. */
  .service__chevron {
    display: block;
    flex: none;
    width: 22px;
    height: 22px;
    border: 1px solid rgba(242, 237, 230, 0.35);
    border-radius: 50%;
    background: none;
    transition: transform var(--quick), background var(--quick),
      border-color var(--quick);
  }

  /* The glyph, drawn rather than written: a chevron in the markup is a
     character a screen reader would read out beside a name that already says
     which service this is. */
  .service__chevron::before {
    content: "";
    display: block;
    width: 6px;
    height: 6px;
    margin: 5px auto 0;
    border-right: 1px solid currentcolor;
    border-bottom: 1px solid currentcolor;
    transform: rotate(45deg);
  }

  .service__toggle:checked + .service__label .service__chevron {
    border-color: rgba(242, 237, 230, 0.7);
    background: rgba(242, 237, 230, 0.16);
    transform: rotate(180deg);
  }

  /* The focus ring goes on the *label*, because the input it belongs to is
     drawn nowhere — without this a keyboard reaches the toggle and nothing
     on screen says so. The gear list's toggle needs this for the same
     reason. */
  .service__toggle:focus-visible + .service__label .service__fold {
    outline: 2px solid var(--gold);
    outline-offset: 4px;
  }

  /* The inline enumeration is what the fold replaces. Hidden rather than
     absent, so the roles are in the document at every width — the fold is a
     disclosure change, not a copy rewrite. */
  .service__covers {
    display: none;
  }

  /* The reveal, height-animated without measuring: a grid row going 0fr to
     1fr. `min-height: 0` on the inner element is **mandatory** — a grid item
     has an automatic minimum size of its content, so without it the row
     never collapses and every card ships open. */
  .service__rolewrap {
    display: grid;
    grid-template-rows: 0fr;
    transition: grid-template-rows 0.24s cubic-bezier(0.4, 0, 0.2, 1);
  }

  .service__toggle:checked ~ .service__rolewrap {
    grid-template-rows: 1fr;
  }

  .service__roles {
    overflow: hidden;
    min-height: 0;
    opacity: 0;
    padding-top: 0;
    transition: opacity 0.18s ease, padding-top 0.18s ease;
  }

  .service__toggle:checked ~ .service__rolewrap .service__roles {
    opacity: 1;
    padding-top: 14px;
  }

  /* The one piece of uppercase mono in the revealed block. The roles
     themselves are sentence case — tracked uppercase is what made the inline
     version wrap in the first place. */
  .service__roleslabel {
    margin: 0 0 2px;
    font-weight: 600;
    font-size: 8.5px;
    line-height: 1;
    letter-spacing: 0.16em;
    text-transform: uppercase;
    color: rgba(242, 237, 230, 0.5);
  }

  .service__rolelist {
    margin: 0;
    padding: 0;
    list-style: none;
  }

  /* Plain rows with a hairline between, not chips: "Production sound mixing"
     is too long for a pill and would break mid-word. The separator is a top
     border skipped on the first, so the block opens with a role rather than
     with a line. */
  .service__role {
    padding: 8px 0;
    border-top: 1px solid rgba(242, 237, 230, 0.14);
    font-weight: 500;
    font-size: 12.5px;
    line-height: 1.45;
    color: rgba(242, 237, 230, 0.9);
  }

  .service__role:first-child {
    border-top: 0;
  }
}

/* Reduced motion: the state change stays, the animation goes. The reference
   asks for exactly this. */
@media (prefers-reduced-motion: reduce) {
  .service__rolewrap,
  .service__roles {
    transition: none;
  }
}

/* ---- The card's corner mark ----------------------------------------------
   **Nothing is rendered, and this note is the record of why.**

   The design prints a year bottom-left and the card's own hex bottom-right.
   The hex was never drawn — a colour code is a note the design tool wrote to
   itself. The year went with it on 12-09-2026: a hard-coded "2026" is a date
   that is wrong from January, and there is nothing on a services card it
   tells a visitor about the work. Rendering `now()` instead would be a
   timestamp on a page that is not dated.

   Kept as a comment rather than deleted silently, so the next reader of the
   handoff does not add it back as a missing piece. */

.service__heading {
  margin: 0;
  font-weight: 800;
  font-size: 32px;
  line-height: 1.12;
  letter-spacing: -0.02em;
  text-wrap: pretty;
}

/* One sentence per line — see `heading_lines`. A block, so the next sentence
   starts on its own line without a `<br>` coming from the content. */
.service__headline {
  display: block;
}

/* The heading is the link, and it is underlined only on hover: a card this
   size reads as a target already, and four underlined headings down a page
   is noise. */
.service__link {
  color: inherit;
  text-decoration: none;
}

.service__link:hover {
  text-decoration: underline;
  text-underline-offset: 4px;
}

.service__summary {
  margin: 12px 0 0;
  font-size: 14px;
  line-height: 1.6;
  color: rgba(242, 237, 230, 0.74);
}

.service__cta {
  display: inline-flex;
  align-items: center;
  margin-top: 22px;
  padding: 11px 22px;
  border-radius: var(--radius-pill);
  border: 1px solid rgba(242, 237, 230, 0.55);
  font-weight: 700;
  font-size: 11px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--paper);
  text-decoration: none;
  transition: background var(--quick), color var(--quick);
}

.service__cta:hover {
  background: var(--paper);
  color: var(--ink);
}

/* The label on a service that cannot be booked — "Introducing", "Coming
   soon". Filled rather than outlined, so it does not read as a button
   somebody is failing to press. */
.service__soon {
  display: inline-flex;
  align-items: center;
  margin: 22px 0 0;
  padding: 10px 22px;
  border-radius: var(--radius-pill);
  background: var(--gold);
  color: var(--dark);
  font-weight: 700;
  font-size: 11px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
}

/* One palette, warming down the page. Keyed on the page rather than on
   position, so reordering the services in content_specs.py cannot leave two
   cards the same colour. */
.service--sound-design {
  background: linear-gradient(150deg, #2a1109 0%, var(--rust) 62%, #a04a27 100%);
}

.service--sound-recording {
  background: linear-gradient(150deg, #241410 0%, var(--clay-deep) 58%, #8a5540 100%);
}

.service--sound-restoration {
  background: linear-gradient(150deg, #2b1610 0%, var(--clay) 60%, #a86a4f 100%);
}

.service--field-recording {
  background: linear-gradient(150deg, #1d1512 0%, #4a3328 62%, #6d5040 100%);
}

/* ---- The hub, narrow ---------------------------------------------------- */

@media (max-width: 900px) {
  .hub__header {
    flex-direction: column;
    gap: 14px;
    margin-bottom: 24px;
  }

  .hub__heading {
    font-size: 38px;
  }

  .hub__intro {
    max-width: none;
    padding-top: 0;
  }

  .guide {
    padding: 22px 20px 26px;
  }

  .guide__heading {
    font-size: 22px;
  }

  /* One column. Three boxes side by side below this width are too narrow to
     hold a sentence without breaking every second word. */
  .guide__options {
    grid-template-columns: 1fr;
  }

  .service__frame {
    margin: 10px;
    padding: 18px 18px 22px;
    min-height: 0;
  }

  .service__row {
    gap: 22px;
    padding-top: 26px;
  }

  .service__body {
    max-width: none;
  }

  /* A phone is narrower than the ceiling anyway, so the card's width is the
     only limit that applies. */
  .service__player {
    max-width: none;
  }

  .service__heading {
    font-size: 26px;
  }

  /* Full width, because a pill floating in a card is easy to miss on a phone
     and this is the one thing on the card worth pressing. */
  .service__cta,
  .service__soon {
    justify-content: center;
    width: 100%;
  }
}

/* ---- Hiring — design 12a -------------------------------------------------
   A dark hero with the first-week card beside it, then a light band of
   packages. The one page besides the before/after proof band where the ground
   flips, and for the same reason: a price list reads as a document rather than
   as an argument. */

.hire {
  padding-top: 40px;
  padding-bottom: 76px;
}

.hire__row {
  display: flex;
  align-items: flex-start;
  gap: 44px;
}

.hire__words {
  flex: 1;
  /* Without this a long unbroken word makes the flex item refuse to shrink
     and pushes the card off the page — the same guard .hero__words needs. */
  min-width: 0;
}

.hire__heading {
  margin: 20px 0 0;
  font-weight: 800;
  font-size: 58px;
  line-height: 1.03;
  letter-spacing: -0.025em;
  max-width: 620px;
  /* Balances the last line rather than leaving one word alone on it. */
  text-wrap: pretty;
}

.hire__intro {
  margin-top: 20px;
  max-width: 470px;
  color: var(--paper-soft);
}

.hire__intro p {
  margin: 0 0 12px;
}

.hire__intro p:last-child {
  margin-bottom: 0;
}

.hire__actions {
  display: flex;
  align-items: center;
  flex-wrap: wrap;
  gap: 18px 26px;
  margin-top: 32px;
}

.hire__cta {
  padding: 14px 26px;
  font-weight: 700;
  font-size: 11px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  text-decoration: none;
}

/* The three promises. A list, because they are three separate claims — the
   design's separating mark is drawn rather than typed, so a screen reader
   hears three items instead of one sentence punctuated by dots. */
.hire__promises {
  display: flex;
  flex-wrap: wrap;
  gap: 6px 22px;
  margin: 0;
  padding: 0;
  list-style: none;
  font-size: 12.5px;
  line-height: 1.45;
  color: var(--paper-soft);
}

.hire__promises li {
  position: relative;
}

/* The separator, on every item but the first. A pseudo-element because it is
   punctuation between items rather than content of one. */
.hire__promises li + li::before {
  content: "·";
  position: absolute;
  left: -13px;
  color: var(--paper-faint);
}

/* ---- What the first week looks like -------------------------------------- */

.week {
  flex: none;
  width: 330px;
  padding: 24px 26px 28px;
  border-radius: var(--radius-lg);
  background: var(--dark-raised);
  box-shadow: 0 24px 60px rgba(0, 0, 0, 0.5);
}

.week__status {
  display: flex;
  align-items: center;
  gap: 8px;
  margin: 0;
  font-weight: 700;
  font-size: 9.5px;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--paper-soft);
}

/* The availability dot.
 *
 * **Only ever decoration.** The words beside it say the same thing, so
 * somebody who cannot distinguish green from orange loses nothing — the rule
 * that a state is never carried by colour alone. It is `aria-hidden` in the
 * template for the same reason.
 *
 * The colour comes from the state rather than from its own setting, so a
 * studio cannot be "full" behind a green light. */
.week__dot {
  width: 7px;
  height: 7px;
  flex: none;
  border-radius: 50%;
  /* Grey, so a state this stylesheet does not know about is visibly neutral
     rather than accidentally reassuring. */
  background: var(--paper-faint);
}

.week__dot--available {
  background: #7fd18b;
}

.week__dot--busy {
  background: #e0a35c;
}

/* Muted rather than a warning red: this says "not right now", not "error".
   A stop-sign colour on a studio's own site reads as something being broken. */
.week__dot--full {
  background: #c96f5c;
}

.week__heading {
  margin: 12px 0 20px;
  font-weight: 800;
  font-size: 20px;
  line-height: 1.2;
  letter-spacing: -0.01em;
}

/* The numbers come from a counter rather than the document, so they cannot
   disagree with the list they label — and a screen reader announces an
   ordered list on its own without reading "01" as content. */
.week__steps {
  display: flex;
  flex-direction: column;
  gap: 14px;
  margin: 0;
  padding: 0;
  list-style: none;
  counter-reset: week;
}

.week__step {
  counter-increment: week;
  display: grid;
  grid-template-columns: 26px 1fr;
  gap: 2px 6px;
}

.week__step::before {
  content: counter(week, decimal-leading-zero);
  grid-row: span 2;
  font-weight: 700;
  font-size: 9.5px;
  letter-spacing: 0.16em;
  color: var(--gold);
  padding-top: 3px;
}

.week__title {
  font-weight: 700;
  font-size: 12.5px;
  line-height: 1.3;
}

.week__text {
  grid-column: 2;
  font-size: 11px;
  line-height: 1.5;
  color: rgba(242, 237, 230, 0.56);
}

/* ---- The packages -------------------------------------------------------- */

.prices {
  padding-top: 54px;
  padding-bottom: 66px;
}

.prices__header {
  display: flex;
  align-items: flex-start;
  justify-content: space-between;
  gap: 32px;
  flex-wrap: wrap;
  margin-bottom: 30px;
}

.prices__heading {
  margin-top: 14px;
  font-weight: 800;
  font-size: 34px;
  line-height: 1.1;
  letter-spacing: -0.02em;
  text-transform: uppercase;
}

.prices__intro {
  max-width: 380px;
  font-size: 13.5px;
  line-height: 1.6;
  color: #3a342e;
}

.prices__intro p {
  margin: 0 0 10px;
}

.prices__intro p:last-child {
  margin-bottom: 0;
}

/* Equal columns rather than flex, so three cards are the same width whatever
   their copy length — packages of different sizes read as a ranking. */
.packages {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(280px, 1fr));
  gap: 20px;
  margin: 0;
  padding: 0;
  list-style: none;
}

.package {
  display: flex;
  flex-direction: column;
  padding: 24px 26px 26px;
  border-radius: var(--radius-lg);
  background: #f6f2ec;
  box-shadow: var(--shadow-panel);
  color: var(--ink);
}

.package__badge {
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--ink-faint);
}

.package__name {
  margin: 10px 0 0;
  font-weight: 800;
  font-size: 22px;
  line-height: 1.15;
  letter-spacing: -0.015em;
}

.package__price {
  display: flex;
  align-items: baseline;
  gap: 8px;
  margin: 12px 0 0;
}

.package__from {
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--ink-faint);
}

.package__amount {
  font-weight: 800;
  font-size: 30px;
  letter-spacing: -0.02em;
}

.package__unit {
  font-size: 11.5px;
  color: var(--ink-soft);
}

.package__blurb {
  margin: 12px 0 0;
  font-size: 13.5px;
  line-height: 1.6;
  color: #3a342e;
}

/* `auto` above pushes the CTA to the bottom, so three cards of different
   lengths still line their buttons up. */
.package__points {
  margin: 18px 0 auto;
  padding: 18px 0 0;
  border-top: 1px solid var(--line-on-light);
  list-style: none;
  display: flex;
  flex-direction: column;
  gap: 8px;
  font-size: 12.5px;
  line-height: 1.5;
  color: #3a342e;
}

.package__points li {
  padding-left: 14px;
  position: relative;
}

/* The marker is drawn, not typed: a `·` in the document would be read out
   before every point. */
.package__points li::before {
  content: "·";
  position: absolute;
  left: 2px;
  color: var(--rust);
  font-weight: 700;
}

.package__cta {
  margin-top: 22px;
  padding-top: 18px;
  border-top: 1px solid var(--line-on-light);
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--ink);
  text-decoration: none;
}

.package__cta:hover {
  text-decoration: underline;
  text-underline-offset: 4px;
}

/* ---- "Not sure which package fits?" -------------------------------------- */

.unsure {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 28px;
  flex-wrap: wrap;
  margin-top: 22px;
  padding: 24px 28px;
  border-radius: var(--radius-lg);
  background: var(--dark-raised-hover);
  color: var(--paper);
}

.unsure__heading {
  margin: 0;
  font-weight: 800;
  font-size: 17px;
  line-height: 1.25;
}

.unsure__text {
  margin: 6px 0 0;
  max-width: 560px;
  font-size: 13px;
  line-height: 1.55;
  color: var(--paper-soft);
}

.unsure .button {
  flex: none;
  padding: 12px 22px;
  font-weight: 700;
  font-size: 11px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  text-decoration: none;
}

/* ---- Hiring, narrow ------------------------------------------------------ */

@media (max-width: 900px) {
  .hire {
    padding-top: 26px;
    padding-bottom: 44px;
  }

  /* The card moves below the words rather than beside them — the design's
     own mobile arrangement. */
  .hire__row {
    flex-direction: column;
    gap: 28px;
  }

  .hire__heading {
    font-size: 34px;
    line-height: 1.06;
  }

  .hire__intro {
    max-width: none;
  }

  /* Stacked, so the button is full width and the promises read as a list
     under it rather than as a row that wraps mid-phrase. */
  .hire__actions {
    flex-direction: column;
    align-items: stretch;
    gap: 16px;
  }

  .hire__cta {
    justify-content: center;
  }

  .hire__promises {
    flex-direction: column;
    gap: 5px;
  }

  /* The separator was punctuation between items on one line; stacked, each
     line stands on its own. */
  .hire__promises li + li::before {
    content: none;
  }

  .week {
    width: 100%;
  }

  .prices {
    padding-top: 36px;
    padding-bottom: 44px;
  }

  .prices__heading {
    font-size: 27px;
  }

  .prices__intro {
    max-width: none;
  }

  /* One column: two 280px cards side by side is where the price stops being
     legible at a glance, which is the whole job of the card. */
  .packages {
    grid-template-columns: 1fr;
    gap: 14px;
  }

  .unsure {
    align-items: stretch;
    padding: 20px 20px 22px;
  }

  .unsure .button {
    justify-content: center;
  }
}

/* ---- The brief -----------------------------------------------------------
   The form the hire page carries, and the stepped panel the island puts over
   it. Both are styled here rather than half here and half in the island's own
   stylesheet: they are the same fields, and two definitions of one form is one
   that drifts. */

/* Jumped to from three CTAs on the hire page. The offset keeps the heading
   clear of the navigation, which would otherwise sit over what somebody just
   pressed a button to reach. */
#brief {
  scroll-margin-top: 90px;
}

/* Where a sent or bounced contact form lands (`FORM_ANCHORS`). On a desk
   the root has no scroll padding, so without this the receipt sits flush
   against the top edge; 24px is the legal pages' figure. */
#message {
  scroll-margin-top: 24px;
}

/* **The column, and it is set on both roots deliberately.**
 *
 * `.brief` is the server's wrapper; `.briefsteps` is the island's, which is a
 * <form> mounted in that wrapper's place — `createRoot` replaces the mount
 * point's children, so the island never inherits `.brief` at all. Setting the
 * width only there gave a 720px form with no scripting and a form spanning the
 * whole viewport with it: one brief, two layouts, and the wide one is what
 * almost everybody saw.
 *
 * **940px is the site's content column** — the measure the design handoff
 * uses, and what `.reach__inner` on the contact page already follows. A form
 * narrower than the rest of the site reads as a different page rather than a
 * calmer one: on an ultrawide monitor a 640px ribbon leaves most of the screen
 * empty, which is what it looked like before this.
 *
 * The *options* inside it are what keep it from feeling stretched, and they
 * are capped separately rather than by squeezing the whole column — see
 * `.brief__options`. Width and density are two decisions, and tying them
 * together is what made a readable form into a narrow one. */
.brief,
.briefsteps {
  max-width: 940px;
  margin: 0 auto;
  padding: 46px 0 60px;
}

/* The island's root is the form itself, so it carries the form's own spacing
   as well as the column above. */
.briefsteps {
  padding: 34px 0 44px;
}

.brief__form {
  display: flex;
  flex-direction: column;
  gap: 18px;
  margin-top: 20px;
}

/* A bounced brief. Announced as well as shown — see the role="alert" in the
   template.

   There is no `.brief__sent` beside it any more: a brief that arrived is
   answered by `.receipt`, the panel the contact page already had. */
.brief__problem {
  margin-top: 14px;
  padding: 12px 16px;
  border-radius: var(--radius);
  font-size: 13.5px;
  line-height: 1.5;
  background: rgba(201, 111, 92, 0.14);
  border: 1px solid rgba(201, 111, 92, 0.45);
}

/* The bounce message, where the fault is.
 *
 * **A panel rather than a line, and beside the fields rather than at the top
 * of the page.** It sat above the three question cards, which on a filled-in
 * brief is a screen and a half from the box that is wrong — somebody who
 * pressed Send went looking for what had happened. This is what it looks like
 * when it is meant to stop you.
 */
.brief__problem--panel {
  margin: 0;
  padding: 18px 20px;
  border-left-width: 3px;
  scroll-margin-top: 90px;
}

/* No focus ring on the panel itself: it is focused programmatically to take
   somebody to it, not because it is a control. The border already says where
   you are. */
.brief__problem--panel:focus {
  outline: none;
}

.brief__problem-heading {
  margin: 0;
  font-weight: 800;
  font-size: 15px;
  line-height: 1.3;
}

.brief__problem-text {
  margin: 6px 0 0;
}

.brief__problem-note {
  margin: 8px 0 0;
  font-size: 12.5px;
  color: var(--paper-soft);
}

/* ---- One card ------------------------------------------------------------
   A question and whatever follows it, read together — how big *and* when it
   ships. The grouping comes from Python so the plain form and the island
   cannot disagree about what belongs in a card. */

.brief__card {
  position: relative;
  display: flex;
  flex-direction: column;
  gap: 20px;
  padding: 22px 26px 24px 52px;
  border-radius: var(--radius-lg);
  border: 1px solid var(--line-on-dark);
  background: var(--dark-raised);
}

/* The number, in the gutter the padding leaves for it. Decoration — the
   questions are in order in the document, so a screen reader is not told
   "01" before each one. */
.brief__index {
  position: absolute;
  left: 20px;
  top: 24px;
  margin: 0;
  width: 24px;
  height: 24px;
  display: flex;
  align-items: center;
  justify-content: center;
  border-radius: 50%;
  background: var(--gold-dim);
  color: var(--gold);
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.06em;
}

/* A follow-up inside a card. Quieter than the question it belongs to, so the
   two read as one thing with a detail rather than as two questions. */
.brief__question--sub .brief__legend {
  font-size: 10px;
  font-weight: 700;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

/* The link, revealed by the audio answer. */
.brief__link {
  margin-top: 4px;
}

/* What a field check said, beside the field. Announced as well as shown —
   see `role="alert"` in the island. */
.field__problem,
.field__warning {
  font-size: 12.5px;
  line-height: 1.45;
}

/* A required field that is wrong. */
.field__problem {
  color: #c96f5c;
}

/* An *optional* field that is wrong — the phone number.
   Orange rather than red, because "leave it empty" resolves it perfectly
   well, and a red border on something nobody has to fill in reads as a
   blocked form. */
.field__warning {
  color: #e0a35c;
}

/* Same distinction on the box itself, so the border agrees with the text
   beside it. */
.brief :is(input, select)[aria-invalid="true"] {
  border-color: #c96f5c;
}

.briefsteps .field:has(.field__warning) :is(input, select) {
  border-color: #e0a35c;
}

/* ---- One question -------------------------------------------------------- */

.brief__question {
  margin: 0;
  padding: 0;
  border: 0;
}

.brief__legend {
  padding: 0;
  font-weight: 700;
  font-size: 15px;
  line-height: 1.3;
}

.brief__help {
  margin: 6px 0 0;
  font-size: 12.5px;
  line-height: 1.5;
  color: var(--paper-soft);
}

/* **Pills, since 23e** — the brief's handoff draws every answer as one, on a
   desk and on a phone. A row that wraps rather than a grid: seven short
   answers sit side by side, and a long one takes the room it needs. */
.brief__options {
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  margin-top: 14px;
}

/* The whole pill is the target, not a dot beside it. The radio stays in the
   document and in the tab order — clipped, never `display: none`, or a
   keyboard could not reach the answer — and the pill shows its state. */
.brief__option {
  position: relative;
  display: inline-flex;
  align-items: center;
  padding: 11px 17px;
  border-radius: var(--radius-pill);
  border: 1px solid var(--line-on-dark);
  background: rgba(242, 237, 230, 0.04);
  color: rgba(242, 237, 230, 0.78);
  font-weight: 700;
  font-size: 12px;
  line-height: 1;
  white-space: nowrap;
  cursor: pointer;
  transition: background var(--quick), border-color var(--quick), color var(--quick);
}

.brief__option:hover {
  background: rgba(242, 237, 230, 0.08);
}

/* Styled from the input's own state rather than a class, so what a screen
   reader announces and what is visible cannot disagree. */
.brief__option:has(input:checked) {
  border-color: rgba(255, 216, 151, 0.55);
  background: rgba(255, 216, 151, 0.16);
  color: var(--gold);
}

.brief__option:has(input:focus-visible) {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

.brief__option input {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: 0;
  opacity: 0;
  pointer-events: none;
}

/* A field the server marked as wrong. The sentence above the form says what
   to fix; this says where — never colour alone. */
.brief__question[aria-invalid="true"] .brief__legend,
.field :is(input, select, textarea)[aria-invalid="true"] {
  border-color: #c96f5c;
}

.field :is(input, select, textarea)[aria-invalid="true"] {
  border-width: 2px;
}

/* ---- The details step ---------------------------------------------------- */

.brief__fields {
  display: grid;
  /* Four fields across at 940px, which is what the column is for. `1fr`
     rather than a ceiling here: a text box gains from the extra width in a
     way a radio label does not, and four boxes of equal width read as one
     row of fields. */
  grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
  gap: 14px;
}

.brief .field,
.briefsteps .field {
  display: flex;
  flex-direction: column;
  gap: 6px;
}

.brief .field__label,
.briefsteps .field__label {
  font-weight: 700;
  font-size: 11px;
  letter-spacing: 0.12em;
  text-transform: uppercase;
  color: var(--paper-soft);
}

.field__note {
  margin-left: 6px;
  font-weight: 600;
  letter-spacing: 0.04em;
  text-transform: none;
  color: var(--paper-faint);
}

.brief :is(input, select, textarea),
.briefsteps :is(input, select, textarea) {
  padding: 10px 12px;
  border-radius: var(--radius);
  border: 1px solid var(--line-on-dark);
  background: var(--dark-raised);
  color: var(--paper);
  font: inherit;
  font-size: 14px;
}

.brief textarea,
.briefsteps textarea {
  resize: vertical;
  min-height: 84px;
}

/* A box being typed in lights its own border, as the contact form's does
   (the owner's word, 15-11-2026). The site-wide ring sits 3px outside the
   box, so the box's grey border showed inside the gold one and the box
   looked indented. Ticks and radios keep the ring their label draws. */
.brief :is(input:not([type="radio"], [type="checkbox"]), select, textarea):focus-visible,
.briefsteps :is(input:not([type="radio"], [type="checkbox"]), select, textarea):focus-visible {
  outline: none;
  border-color: var(--gold-edge);
  background: rgba(242, 237, 230, 0.07);
}

/* The spam trap. Off-screen rather than `display: none`, which some bots
   check for — and `aria-hidden` with `tabindex="-1"` in the markup, so a
   keyboard user can never land in it. */
.brief__trap {
  position: absolute;
  left: -9999px;
  width: 1px;
  height: 1px;
  overflow: hidden;
}

.brief__send {
  align-self: flex-start;
  padding: 14px 26px;
  font-weight: 700;
  font-size: 11px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  text-decoration: none;
}

/* ---- A named link (Module 37) ----------------------------------------------
   A link pasted into the brief shows by its name in a box drawn as the
   brief's other boxes, its address behind the name, with Edit beside it.
   Edit opens "Edit link" over the brief — the owner's design, 19-11-2026 —
   on the consent box's scrim, in the brief's own colours. */
.linkbox {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 12px;
  /* The empty box's height (46px with Edit's 30 and 8px around it — the
     owner's word: a clear gap, not touching), so the field does not move
     when a link is pasted. */
  min-height: 46px;
  padding: 0 8px 0 14px;
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius);
  background: var(--dark-raised);
  animation: linkbox-in var(--quick);
}

/* The name a long address takes: one line, cut with an ellipsis when even
   the name is long, never pushing Edit out of the box. It opens the link,
   so it is only as wide as its words: a press beside them does nothing
   (the owner's word, 20-11-2026: ✕ alone clears) rather than opening the
   link from empty room. 44px to press, and no taller, so the box keeps
   the empty box's 46. */
.linkbox__name {
  flex: 0 1 auto;
  box-sizing: border-box;
  min-width: 0;
  min-height: 44px;
  padding: 9px 0;
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
  color: var(--gold);
  font-weight: 600;
  text-decoration: none;
}

.linkbox__name:hover,
.linkbox__name:focus-visible {
  text-decoration: underline;
}

/* Edit and ✕ are drawn 30px so they sit well inside the box; what can be
   pressed is 44px all the same — `::after` reaches 7px past each. */
.linkbox__edit,
.linkbox__remove {
  position: relative;
}

.linkbox__edit::after,
.linkbox__remove::after {
  content: "";
  position: absolute;
  inset: -7px;
}

.linkbox__edit {
  flex: none;
  min-height: 30px;
  padding: 0 14px;
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius-pill);
  background: none;
  color: var(--paper);
  font: inherit;
  font-size: 13px;
  cursor: pointer;
  transition: border-color var(--quick);
}

.linkbox__edit:hover,
.linkbox__edit:focus-visible {
  border-color: var(--gold-edge);
}

/* ✕ beside Edit: the box emptied for another link. Round, 44px to press. */
.linkbox__remove {
  flex: none;
  /* ✕ and Edit at the right, however short the name. */
  margin-left: auto;
  width: 30px;
  height: 30px;
  border: 0;
  border-radius: var(--radius-pill);
  background: none;
  color: var(--paper-soft);
  font: inherit;
  cursor: pointer;
}

.linkbox__remove:hover,
.linkbox__remove:focus-visible {
  color: var(--paper);
}

@keyframes linkbox-in {
  from {
    opacity: 0;
  }
}

@media (prefers-reduced-motion: reduce) {
  .linkbox {
    animation: none;
  }
}

.linkedit {
  position: fixed;
  inset: 0;
  z-index: 70;
  display: grid;
  place-items: center;
  padding: clamp(12px, 4vw, 32px);
  background: rgba(14, 13, 11, 0.72);
}

.linkedit__box {
  width: min(480px, 100%);
  display: flex;
  flex-direction: column;
  gap: 18px;
  padding: clamp(20px, 4vw, 28px);
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius-lg);
  background: var(--dark-raised);
  color: var(--paper);
}

.linkedit__head {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 12px;
}

.linkedit__title {
  margin: 0;
  font-weight: 800;
  font-size: 17px;
}

.linkedit__close {
  flex: none;
  width: 44px;
  height: 44px;
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius-pill);
  background: none;
  color: var(--paper);
  cursor: pointer;
}

/* Its boxes are the brief's: the editor sits outside the brief's markup,
   so the brief's box rule is given to it here. */
.linkedit .field {
  display: flex;
  flex-direction: column;
  gap: 8px;
}

.linkedit .field__label {
  font-size: 12px;
  color: var(--paper-soft);
}

.linkedit input {
  width: 100%;
  min-height: 48px;
  padding: 12px 16px;
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius);
  background: var(--dark);
  color: var(--paper);
  font: inherit;
}

.linkedit input:focus-visible {
  outline: none;
  border-color: var(--gold-edge);
}

/* A Link Save refused stays red with the cursor in it: Save puts the
   cursor there, and the gold above would hide the refusal. */
.linkedit input[aria-invalid="true"],
.linkedit input[aria-invalid="true"]:focus-visible {
  border-color: #c96f5c;
}

.linkedit__actions {
  display: flex;
  justify-content: flex-end;
  flex-wrap: wrap;
  gap: 12px;
}

/* ---- The stepped panel ---------------------------------------------------
   What the island draws over the form above. Only the stepping is new: the
   questions and fields inside it are the same ones styled above. */

/* The counter and Clear all, on one line. */
.briefsteps__header {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 16px;
}

/* Send, and the quieter way to empty the fields beside it. */
.briefsteps__send {
  display: flex;
  align-items: center;
  gap: 12px;
  flex-wrap: wrap;
}

.briefsteps__progress {
  margin: 0;
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--paper-soft);
}

.briefsteps__bar {
  display: flex;
  gap: 6px;
}

.briefsteps__segment {
  flex: 1;
  height: 3px;
  border-radius: var(--radius-pill);
  background: var(--line-on-dark);
  transition: background var(--quick);
}

.briefsteps__segment--done {
  background: var(--gold);
}

/* The contact panel and its body keep the form's own spacing. They were
   added inside the form in 23e-2, and a wrapper is not a flex item's parent:
   without this the fields lost the form's 18px gap, so the notes label sat
   flush under the project box and its focus ring drew over it — reported
   from the running page, 09-10-2026. At every width, because the wrapper is. */
.briefcontact,
.briefcontact__body {
  display: flex;
  flex-direction: column;
  gap: 18px;
}

/* ---- The brief on a desk — design_handoff_admin_inquiries, 17a ----------
   Package cards above; one panel holding three numbered steps; the contact
   form in a second panel beneath, locked by the island until the steps are
   answered. Above a phone's width only: the phone keeps its carousel. */

/* ---- The package cards — design_handoff_admin_inquiries ----------------
   Above the brief at every width since 23e-3: three across on a desk (17a),
   stacked rows on a phone (17b). The card's own look is shared; only the
   arrangement differs, set in the two blocks below. */

.briefpacks {
  display: flex;
  flex-direction: column;
  gap: 10px;
  margin-bottom: 22px;
}

.briefpack {
  display: flex;
  flex-direction: column;
  align-items: flex-start;
  gap: 6px;
  padding: 20px 22px;
  border-radius: 16px;
  border: 1px solid transparent;
  background: var(--dark-raised);
  color: var(--paper);
  font: inherit;
  text-align: left;
  cursor: pointer;
  box-shadow: 0 14px 34px rgba(0, 0, 0, 0.45);
  transition: background var(--quick), border-color var(--quick);
}

.briefpack:hover {
  background: #221d19;
}

.briefpack[aria-pressed="true"] {
  border-color: rgba(255, 216, 151, 0.55);
  background: rgba(255, 216, 151, 0.1);
}

.briefpack__eyebrow {
  font-size: 8.5px;
  font-weight: 700;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.45);
}

.briefpack__name {
  font-size: 15px;
  font-weight: 700;
}

.briefpack__price {
  font-size: 11.5px;
  color: var(--paper-soft);
}

.briefpack__cta {
  align-self: flex-end;
  margin-top: 12px;
  font-size: 10px;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.55);
}

.briefpack[aria-pressed="true"] .briefpack__cta {
  color: var(--gold);
}

@media (min-width: 721px) {
  .briefpacks {
    display: grid;
    grid-template-columns: repeat(3, minmax(0, 1fr));
    gap: 14px;
    margin-bottom: 34px;
  }

  .briefpanel,
  .briefcontact {
    padding: 30px 34px;
    border-radius: var(--radius-lg);
    border: 1px solid rgba(242, 237, 230, 0.14);
    background: linear-gradient(#22201c, #171512);
    box-shadow: 0 24px 60px rgba(0, 0, 0, 0.45);
    transition: background var(--quick), box-shadow var(--quick);
  }

  /* Every step answered: the panel steps back and the fields come forward. */
  .briefpanel--done {
    border-color: rgba(242, 237, 230, 0.09);
    background: rgba(255, 255, 255, 0.02);
    box-shadow: none;
  }

  .briefpanel--done .brief__card {
    opacity: 0.5;
  }

  .briefpanel__head,
  .briefcontact__head {
    display: flex;
    align-items: baseline;
    justify-content: space-between;
    gap: 20px;
  }

  .briefpanel__eyebrow {
    margin: 0;
    font-size: 9px;
    font-weight: 700;
    letter-spacing: 0.2em;
    text-transform: uppercase;
    color: rgba(242, 237, 230, 0.45);
  }

  .briefpanel__status {
    display: flex;
    align-items: center;
    gap: 14px;
  }

  /* Clear all (18-10-2026): a finger's height, which `.button` alone is not. */
  .briefpanel__status .button {
    min-height: 44px;
  }

  .briefpanel__count {
    margin: 0;
    padding: 7px 13px;
    border-radius: var(--radius-pill);
    border: 1px solid var(--line-on-dark);
    background: rgba(242, 237, 230, 0.06);
    font-size: 9.5px;
    font-weight: 700;
    letter-spacing: 0.14em;
    text-transform: uppercase;
    color: rgba(242, 237, 230, 0.55);
  }

  .briefpanel__count--done {
    border-color: rgba(52, 199, 123, 0.35);
    background: rgba(52, 199, 123, 0.14);
    color: #7bd9a6;
  }

  .briefpanel__edit {
    padding: 0;
    border: 0;
    background: none;
    font: inherit;
    font-size: 9.5px;
    font-weight: 700;
    letter-spacing: 0.16em;
    text-transform: uppercase;
    color: var(--gold);
    text-decoration: underline;
    text-underline-offset: 3px;
    cursor: pointer;
  }

  /* Inside the panel a card is a step: no box of its own, a hairline above
     every step after the first, and its number in the gutter. */
  /* No flex gap inside a step: the design's spacing is set per part — 5px
     from the heading to its hint, 20px above each follow-up — and the card's
     own 20px gap put the hint a whole line under the heading it belongs to. */
  .briefpanel .brief__card {
    gap: 0;
    padding: 24px 0 24px 50px;
    border: 0;
    border-radius: 0;
    background: none;
    transition: opacity var(--quick);
  }

  .briefpanel .brief__card + .brief__card {
    border-top: 1px solid rgba(242, 237, 230, 0.09);
  }

  .briefpanel .brief__index {
    left: 0;
    top: 22px;
    width: 34px;
    height: 34px;
    border: 1px solid rgba(242, 237, 230, 0.2);
    background: transparent;
    color: rgba(242, 237, 230, 0.5);
    font-size: 10.5px;
    transition: background var(--quick), color var(--quick), border-color var(--quick);
  }

  .briefpanel .brief__card--done .brief__index {
    border-color: var(--gold);
    background: var(--gold);
    color: #1b1815;
  }

  .brief__step {
    margin: 6px 0 0;
    font-size: 16px;
    font-weight: 700;
    line-height: 1.25;
  }

  .briefpanel .brief__step + .brief__question .brief__help {
    margin-top: 5px;
  }

  .briefpanel .brief__question--sub {
    margin-top: 20px;
  }

  .briefpanel .brief__question--sub .brief__legend {
    margin-top: 0;
    font-size: 8.5px;
    letter-spacing: 0.18em;
    color: rgba(242, 237, 230, 0.4);
  }

  .briefcontact {
    position: relative;
    margin-top: 14px;
  }

  .briefcontact__aside {
    margin: 0;
    font-size: 11px;
    color: rgba(242, 237, 230, 0.35);
  }

  .briefcontact__body {
    margin-top: 4px;
  }

  .briefcontact__notice {
    margin: 0;
    font-size: 11.5px;
    color: rgba(242, 237, 230, 0.45);
  }

  /* Over the fields until the steps are answered. The fields under it are
     `inert`, set by the island, so neither a pointer nor a keyboard reaches
     them; this says why. */
  .briefcontact__lock {
    position: absolute;
    inset: 0;
    display: flex;
    align-items: center;
    justify-content: center;
    margin: 0;
    border-radius: var(--radius-lg);
    background: rgba(14, 13, 11, 0.55);
    font-size: 12px;
    font-weight: 600;
    color: rgba(242, 237, 230, 0.8);
    cursor: not-allowed;
  }

  .briefcontact__pill {
    display: flex;
    align-items: center;
    gap: 12px;
    padding: 14px 22px;
    border-radius: var(--radius-pill);
    border: 1px solid rgba(242, 237, 230, 0.16);
    background: var(--dark-raised);
    box-shadow: 0 20px 50px rgba(0, 0, 0, 0.6);
  }

  .briefcontact__dot {
    width: 8px;
    height: 8px;
    flex: none;
    border-radius: 50%;
    background: var(--gold);
  }
}

/* ---- The brief as a carousel, on a phone --------------------------------
   HIRE-MOBILE-17B: five single-question cards swiped one at a time, rather
   than three cards holding two questions each. A card with two questions is
   one nobody can see the bottom of at 390px.

   **The row is drawn here, not by the island.** Scroll-snap means a swipe
   works with no JavaScript and every card stays in the document for a
   crawler; the island adds the dots, the counter, Back/Next and the move
   after an answer — the shape KitCarousel and the photo carousel follow. */

/* At every width the track is just a wrapper: the cards stack as they always
   have, and the gap between them is the form's own. */
.briefsteps__track {
  display: flex;
  flex-direction: column;
  gap: 22px;
}

/* The controls exist only where they move something. The island renders
   nothing above a phone's width; this is the second guard. */
.briefnav {
  display: none;
}

@media (max-width: 720px) {
  .briefsteps__track {
    flex-direction: row;
    gap: 16px;
    overflow-x: auto;
    scroll-snap-type: x mandatory;
    /* **No `scroll-behavior: smooth` here, and that is deliberate.**
       Measured on the real page: with smooth scrolling, both `scrollLeft =
       461` and a smooth `scrollTo` land at 0 and stay there — the animation
       starts, mandatory snapping re-targets it, and the row never moves.
       That is the bug that made this carousel look frozen while its counter
       advanced. A swipe still glides, because a finger's own momentum is
       what moves it; only the programmatic jump is instant. */
    /* The bar under a row that has dots and arrows is a second control for
       the same thing. Hidden, not disabled: the row still swipes. */
    scrollbar-width: none;
    /* **As tall as the step on screen** (05-11-2026): the island measures
       that card and sets the height; until it does, or without it, the row
       is as tall as its tallest card, as before. Each card keeps its own
       height rather than stretching to the row's, or the measure would read
       the row back. A taller neighbour is cut off below, never scrolled to:
       it is off to the side and comes into view only as the step shown,
       measured again. */
    align-items: flex-start;
    height: var(--brief-step-height, auto);
    overflow-y: hidden;
  }

  .briefsteps__track::-webkit-scrollbar {
    display: none;
  }

  /* One card fills the viewport. `flex: 0 0 100%` rather than a width, so a
     card's own content cannot widen it and push the next one off the snap. */
  .briefsteps__track > .brief__card {
    flex: 0 0 100%;
    scroll-snap-align: start;
    /* **The card's left inset is desktop framing.** 52px holds the numbered
       circle beside the question at wider widths; on a 390px screen that is
       an eighth of the width spent on a two-digit number, and the options are
       what need it. The number moves above the question instead — see
       `.brief__index` below. */
    padding: 18px;
  }

  /* **Beneath the cards, where a thumb already is.** The same decision the
     kit carousel records: on a phone the bottom of the screen is within
     reach, and the cards swipe, so the buttons are the second way to move
     rather than the only one. */
  .briefnav {
    display: flex;
    flex-direction: column;
    margin: 18px -18px 0;
    padding: 14px 18px;
    border-top: 1px solid rgba(242, 237, 230, 0.09);
  }

  /* Back at one end and Next at the other, the handoff's row: the two
     presses are apart, so a thumb reaching for Next does not land on Back. */
  .briefnav__buttons {
    display: flex;
    justify-content: space-between;
    gap: 12px;
  }

  .briefnav__buttons .button {
    min-height: 44px;
    padding-inline: 20px;
  }

  /* ---- The phone's panel — 17b ----------------------------------------
     One raised panel holding the header, the segment bar, the card being
     answered and the two presses. Scoped to `--phone`, which only the island
     draws: with no script the server's cards keep their own boxes, and a
     panel around them would be a box in a box. */

  .briefpanel--phone {
    padding: 16px 18px 0;
    border-radius: 18px;
    border: 1px solid rgba(242, 237, 230, 0.14);
    background: linear-gradient(#22201c, #171512);
    box-shadow: 0 18px 44px rgba(0, 0, 0, 0.45);
  }

  .briefpanel--phone .briefpanel__head {
    display: flex;
    align-items: center;
    justify-content: space-between;
    gap: 12px;
  }

  .briefpanel--phone .briefpanel__eyebrow {
    margin: 0;
    font-size: 9px;
    font-weight: 700;
    letter-spacing: 0.2em;
    text-transform: uppercase;
    color: rgba(242, 237, 230, 0.45);
  }

  .briefpanel--phone .briefpanel__status {
    display: flex;
    align-items: center;
    gap: 12px;
  }

  .briefpanel--phone .briefpanel__status .button {
    min-height: 44px;
  }

  .briefpanel--phone .briefpanel__count {
    margin: 0;
    font-size: 9.5px;
    font-weight: 700;
    letter-spacing: 0.14em;
    text-transform: uppercase;
    color: rgba(242, 237, 230, 0.55);
  }

  /* One segment per question, replacing Module 19's dots: the one being read
     is gold, an answered one is gold at half strength, the rest a hairline.
     Drawn from `aria-current`, the attribute a screen reader hears, so what is
     announced and what is drawn cannot drift. */
  .briefnav__segments {
    display: flex;
    gap: 5px;
    margin-top: 14px;
  }

  /* **3px of line is not a tap target.** The button is 32px tall and draws
     its line through the middle with a gradient clipped to the content box,
     the scrub's trick — so a finger gets the height and the design keeps its
     hairline. */
  .briefnav__segment {
    flex: 1;
    min-width: 0;
    height: 32px;
    padding: 14.5px 0;
    border: 0;
    border-radius: 0;
    background: rgba(242, 237, 230, 0.12) content-box;
    cursor: pointer;
    transition: background-color var(--quick);
  }

  .briefnav__segment--done {
    background: rgba(255, 216, 151, 0.4) content-box;
  }

  .briefnav__segment[aria-current="true"] {
    background: var(--gold) content-box;
  }

  .briefnav__segment:focus-visible {
    outline: 2px solid var(--gold);
    outline-offset: -8px;
  }

  /* Inside the panel a card is the panel's content, not a box of its own. */
  .briefpanel--phone .briefsteps__track > .brief__card {
    gap: 0;
    padding: 4px 0;
    border: 0;
    border-radius: 0;
    background: none;
  }

  /* "01 / 07" in gold above the question, where the desk draws a circle. */
  .briefpanel--phone .brief__index {
    width: auto;
    height: auto;
    justify-content: flex-start;
    border-radius: 0;
    background: none;
    font-size: 9px;
    letter-spacing: 0.18em;
  }

  .briefpanel--phone .brief__legend {
    margin-top: 11px;
    font-size: 19px;
    line-height: 1.25;
  }

  .briefpanel--phone .brief__help {
    margin-top: 6px;
  }

  /* Answers are full-width rows on a phone, each with a tick when chosen —
     a pill sized to its words is a target sized to its words. */
  .briefpanel--phone .brief__options {
    flex-direction: column;
    flex-wrap: nowrap;
    margin-top: 16px;
  }

  .briefpanel--phone .brief__option {
    min-height: 48px;
    justify-content: space-between;
    gap: 10px;
    padding: 14px 15px;
    border-radius: 12px;
    color: var(--paper);
    font-size: 13px;
    line-height: 1.2;
    white-space: normal;
  }

  .briefpanel--phone .brief__option::after {
    content: "✓";
    flex: none;
    font-size: 11px;
    color: var(--gold);
    opacity: 0;
  }

  .briefpanel--phone .brief__option:has(input:checked)::after {
    opacity: 1;
  }

  /* ---- The package cards on a phone: one row each ---------------------
     The name and price on the left, the press on the right. A grid rather
     than flex, because the card is one button and its four spans are
     siblings: the call to action spans the rows beside them. The card's own
     6px gap spaces the rows; a third row with no price has no height. */

  .briefpack {
    display: grid;
    grid-template-columns: minmax(0, 1fr) auto;
    align-items: center;
    column-gap: 12px;
    min-height: 48px;
    padding: 16px 18px;
  }

  .briefpack > :not(.briefpack__cta) {
    grid-column: 1;
  }

  .briefpack__cta {
    grid-column: 2;
    grid-row: 1 / span 3;
    align-self: center;
    margin-top: 0;
    white-space: nowrap;
  }

  /* ---- The contact panel, once the brief is saved ----------------------
     The same raised panel as the brief's, holding the attached answers and
     the fields. `.briefsteps` only: the server's plain form has no panel. */

  .briefsteps .briefcontact {
    padding: 20px 18px 22px;
    border-radius: 18px;
    border: 1px solid rgba(242, 237, 230, 0.14);
    background: linear-gradient(#22201c, #171512);
    box-shadow: 0 18px 44px rgba(0, 0, 0, 0.45);
  }

  .briefsteps .briefcontact .briefpanel__eyebrow {
    margin: 0;
    font-size: 9px;
    font-weight: 700;
    letter-spacing: 0.2em;
    text-transform: uppercase;
    color: rgba(242, 237, 230, 0.45);
  }

  /* ---- The brief once it is saved --------------------------------------
     Answering the last question puts the questions away and shows the
     fields: one thing at a time, which is the mobile handoff's own rule.
     Only drawn on a phone — at wider widths both are on screen together and
     nothing collapses. */

  .briefsaved {
    display: flex;
    align-items: center;
    justify-content: space-between;
    gap: 12px;
    margin-bottom: 20px;
    padding: 14px 16px;
    border: 1px solid rgba(52, 199, 123, 0.35);
    border-radius: 14px;
    /* The handoff's success ground. Dark enough that the gold Send button
       below it is still the brightest thing on the screen. */
    background: rgba(16, 46, 30, 0.55);
  }

  .briefsaved__line {
    display: flex;
    align-items: center;
    gap: 8px;
    margin: 0;
    font-weight: 700;
    font-size: 11px;
    letter-spacing: 0.06em;
    color: var(--paper);
  }

  /* Drawn rather than written, and `aria-hidden` in the markup: a screen
     reader reading "tick Brief saved" is worse than one reading "Brief
     saved". */
  .briefsaved__mark {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    flex: none;
    width: 22px;
    height: 22px;
    border-radius: 50%;
    background: #34c77b;
    font-size: 11px;
    line-height: 1;
    color: #102e1e;
  }

  .briefsaved__words {
    display: flex;
    flex-direction: column;
    gap: 3px;
    font-size: 12.5px;
    letter-spacing: 0;
  }

  .briefsaved__count {
    font-weight: 400;
    font-size: 11px;
    color: rgba(242, 237, 230, 0.55);
  }

  /* The answers, still reachable while the fields are filled in. Closed:
     five lines nobody needs while typing a name. */
  .briefattached {
    border: 1px solid rgba(255, 216, 151, 0.2);
    border-radius: 12px;
    background: rgba(255, 216, 151, 0.05);
  }

  .briefattached__summary {
    display: flex;
    align-items: center;
    justify-content: space-between;
    gap: 10px;
    min-height: 44px;
    padding: 0 15px;
    font-weight: 700;
    font-size: 9px;
    letter-spacing: 0.18em;
    text-transform: uppercase;
    color: var(--gold);
    cursor: pointer;
    list-style: none;
  }

  .briefattached__summary::-webkit-details-marker {
    display: none;
  }

  /* The handoff's Show / Hide, from the disclosure's own state — so it
     cannot say Hide over a closed list. Decoration only: `<summary>` already
     tells a screen reader whether it is expanded. The plain `content` first
     is for a browser that does not read the alt-text form and drops it. */
  .briefattached__summary::after {
    content: "Show";
    content: "Show" / "";
    font-size: 9.5px;
    letter-spacing: 0.14em;
    color: rgba(242, 237, 230, 0.6);
  }

  .briefattached[open] .briefattached__summary::after {
    content: "Hide";
    content: "Hide" / "";
  }

  /* The same two words on a Dutch page (13g-4d-2). A stylesheet's words are
     out of reach of the word lists, so they are said here, by the page's
     own `lang`. The open rule keeps the higher specificity, as above. */
  html[lang="nl"] .briefattached__summary::after {
    content: "Tonen";
    content: "Tonen" / "";
  }

  html[lang="nl"] .briefattached[open] .briefattached__summary::after {
    content: "Verbergen";
    content: "Verbergen" / "";
  }

  .briefattached__list {
    margin: 0;
    padding: 0 16px 14px;
    font-size: 12px;
  }

  .briefattached__list dt {
    margin-top: 10px;
    color: var(--paper-faint);
  }

  .briefattached__list dd {
    margin: 2px 0 0;
    color: var(--paper);
  }

  /* ---- Thumb-sized, and the width spent on content ----------------------
     The handoff asks for 44–48px on everything tappable and 18px of padding
     inside a card. */

  .briefsteps__track > .brief__card > .brief__index {
    position: static;
  }

  /* An option is what a finger presses, and a row of text with 10px above
     and below it is about 40. */
  .brief__option {
    min-height: 48px;
    align-items: center;
    padding: 12px 14px;
  }

  /* The same for anything typed into, which the handoff puts at 46. */
  .briefsteps :is(input, select, textarea) {
    min-height: 46px;
  }

  /* A textarea is sized by its rows; a minimum would only fight them. */
  .briefsteps textarea {
    min-height: 0;
  }

  /* The line beside Send, in the no-JavaScript brief too: a phone never
     shows it, for the room — the owner's word, 30-10-2026 (30d). The island
     leaves it out at this width itself. */
  .briefcontact__notice {
    display: none;
  }
}

.briefsteps__details {
  margin: 0;
  font-size: 14px;
  line-height: 1.6;
  color: var(--paper-soft);
}

.briefsteps__actions {
  display: flex;
  align-items: center;
  gap: 12px;
}

.briefsteps__actions .button {
  padding: 13px 24px;
  font-weight: 700;
  font-size: 11px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
}

/* The answers so far. A definition list, because that is what it is: each
   question and what was said to it. */
.briefsteps__scope {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
  gap: 12px;
  margin: 0;
  padding-top: 18px;
  border-top: 1px solid var(--line-on-dark);
}

.briefsteps__scope dt {
  font-weight: 700;
  font-size: 9.5px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

.briefsteps__scope dd {
  margin: 3px 0 0;
  font-size: 13px;
  line-height: 1.4;
}

@media (max-width: 900px) {
  .brief,
  .briefsteps {
    padding: 30px 0 40px;
  }

  /* One column below 900px. Three across at 160px would fit here on
     arithmetic alone, and it is the wrong answer: the gutters are narrower on
     a phone, so each option lands near its minimum and a label like
     "Medium — a full pass over one piece of work" breaks into a column of
     single words. The budget bands used to be the widest string here and are
     not any more — they are written €1k rather than €1.000 — but the scope
     answers are longer than either, and they are what this protects. */
  .brief__options,
  .brief__fields {
    grid-template-columns: 1fr;
    /* `start` is what keeps a ragged last row left-aligned on a wide screen.
       At one column it would leave every option at its content width instead
       of filling the card, so it is undone here rather than only set there. */
    justify-content: stretch;
  }

  .brief__send,
  .briefsteps__actions .button {
    flex: 1;
    justify-content: center;
  }
}

/* ---- The contact page ----------------------------------------------------
   Design handoff `design_handoff_contact_1a`, option 1a. Two breakpoints,
   1440 and 390, both final-intent.

   **Almost every token the design names already existed.** `--dark` is its
   `#0E0D0B`, `--gold` its `#FFD897`, `--gold-dim` the selected card's
   background. The homepage established them, so what follows is layout and
   states rather than a second palette.

   **Where this parts from the design, and why.** The design gates the form:
   with no reason picked it is greyed, `pointer-events: none`, and covered by
   a "Pick a reason to unlock" overlay. That state cannot be reached back out
   of without JavaScript, so with scripting off nobody could write to Tape
   Some at all — on the one page where that costs work rather than polish. A
   reason is preselected instead: the choice is still first and still visible,
   and the form is never inert. Everything else about the panel is the design.
   -------------------------------------------------------------------------- */

.reach {
  padding-top: 44px;
  padding-bottom: 80px;
}

/*
  The design's centred 940px column.

  **Without it the panels stretch to the viewport**, which on a wide monitor
  makes every card enormous and the whole page read as a different design —
  the cards keep their specified padding and type sizes while growing to a
  third of the screen each. `.band` sets the gutter and nothing else, because
  a band is a full-width background; what sits *inside* one needs its own
  measure.
*/
.reach__inner {
  width: min(940px, 100%);
  margin-inline: auto;
}

.reach__header {
  max-width: 640px;
}

.reach__heading {
  margin: 20px 0 0;
  font-size: clamp(32px, 5vw, 46px);
  line-height: 1.05;
  letter-spacing: -0.025em;
  font-weight: 800;
  text-wrap: pretty;
}

.reach__intro {
  margin-top: 16px;
  font-size: 15px;
  line-height: 1.65;
  color: var(--paper-soft);
}

/* ---- The three ways in --------------------------------------------------- */

.contact__actions ul {
  display: flex;
  flex-wrap: wrap;
  gap: 10px;
  margin: 26px 0 0;
  padding: 0;
  list-style: none;
}

.contact__action {
  display: inline-block;
  padding: 13px 22px;
  border-radius: var(--radius-pill);
  border: 1px solid var(--line-on-dark);
  background: rgba(242, 237, 230, 0.04);
  color: var(--paper);
  font-size: 12px;
  font-weight: 600;
  letter-spacing: 0.08em;
  text-decoration: none;
  transition: background var(--quick), border-color var(--quick);
}

.contact__action:hover,
.contact__action:focus-visible {
  background: var(--gold-dim);
  border-color: var(--gold-edge);
}

/* ---- The reason cards ---------------------------------------------------- */

.reasons {
  margin: 34px 0 0;
  padding: 30px 34px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: var(--radius-lg);
  background: linear-gradient(#22201c, #171512);
  box-shadow: 0 24px 60px rgba(0, 0, 0, 0.45);
}

/*
  The panel's label, *inside* the panel.

  **`float` is what puts it there**, and it is not a stylistic choice. A
  `<legend>` is laid out on the fieldset's border by default — straddling the
  top edge, outside the padding — which is the one thing this element does
  that no other does. Floating it removes it from that special flow and makes
  it an ordinary block inside the box; `width: 100%` then makes the cards
  below start on a new line rather than wrapping beside it.

  It stays a `<legend>` rather than becoming a styled `<p>`, because that is
  what names the radio group: without one a screen reader reads three
  unrelated options and never says what is being chosen.
*/
.reasons__legend {
  float: left;
  width: 100%;
  padding: 0;
  font-size: 9px;
  font-weight: 700;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.45);
}

.reasons__cards {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(210px, 1fr));
  gap: 9px;
  margin-top: 20px;
}

/* The whole card is the label, so pressing anywhere in it selects — the same
   reasoning the homepage's service cards follow. A card that looks pressable
   and only responds on its radio is how this pattern usually disappoints. */
.reason {
  /* The hidden radio below is placed against the card, never the page. */
  position: relative;
  display: flex;
  align-items: flex-start;
  justify-content: space-between;
  gap: 12px;
  padding: 15px 17px;
  border: 1px solid var(--line-on-dark);
  border-radius: 13px;
  background: rgba(242, 237, 230, 0.04);
  cursor: pointer;
  transition: background var(--quick), border-color var(--quick),
    opacity var(--quick);
}

/* The radio itself is not drawn — the card is. Kept in the layout rather than
   `display: none`, so it stays focusable and the focus ring below has
   something to sit on.

   **Two classes, on purpose**: `.contact :is(input, select, textarea)` is a
   class and an element, and gave this radio the form's full width and
   padding — without JavaScript the page was 2075px wide (bug 4). Its own
   padding and border are cleared for the same reason. */
.reason .reason__input {
  position: absolute;
  top: 0;
  left: 0;
  width: 1px;
  height: 1px;
  padding: 0;
  border: 0;
  opacity: 0;
  margin: 0;
}

.reason__words {
  display: flex;
  flex-direction: column;
  gap: 5px;
}

.reason__title {
  font-size: 13px;
  font-weight: 700;
  line-height: 1.2;
}

.reason__sub {
  font-size: 11px;
  line-height: 1.5;
  opacity: 0.62;
}

/* The design's tick. 22px circle, empty until chosen. */
.reason__tick {
  flex: none;
  display: grid;
  place-items: center;
  width: 22px;
  height: 22px;
  border: 1px solid rgba(242, 237, 230, 0.2);
  border-radius: 50%;
  font-size: 10px;
  font-weight: 700;
  color: transparent;
  opacity: 0.4;
  transition: all var(--quick);
}

/* Chosen — from `:has()`, so the visible state and the state a screen reader
   announces cannot drift apart. Styling a class the template also sets would
   be two sources for one fact. */
.reason:has(.reason__input:checked) {
  background: var(--gold-dim);
  border-color: rgba(255, 216, 151, 0.5);
  color: var(--gold);
}

.reason:has(.reason__input:checked) .reason__tick {
  background: var(--gold);
  border-color: var(--gold);
  color: var(--ink);
  opacity: 1;
}

/* The unchosen siblings dim once something is picked — the design's
   `opacity: .45`. Only while the group holds a selection, so all three are
   full strength before anybody has chosen. */
/*
  **The unchosen cards are not dimmed, and the design dims them.**

  Its `opacity: .45` marks a choice somebody made: nothing is picked when the
  page loads, so the dimming appears as feedback. Here a reason is always
  preselected — that is what keeps the form usable without JavaScript — so
  the same rule would dim two cards permanently, from the moment the page
  renders, as feedback for a choice nobody made.

  It is also a contrast problem once it is permanent rather than momentary:
  11px body text at 0.62 opacity, dimmed again to 0.45, is roughly 2:1
  against the panel. The selected card is already distinguished by a gold
  border, a gold background and a filled tick — three signals, none of which
  needs the others weakened to be legible.
*/

.reason:hover {
  border-color: var(--gold-edge);
}

/* The focus ring goes on the card, because the input it belongs to is
   invisible. Without this, tabbing through the group shows nothing at all. */
.reason:has(.reason__input:focus-visible) {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

@media (prefers-reduced-motion: reduce) {
  .reason,
  .reason__tick,
  .contact__action {
    transition: none;
  }
}

/* ---- The form panel ------------------------------------------------------ */

.contact {
  margin-top: 14px;
  padding: 30px 34px 32px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: var(--radius-lg);
  background: linear-gradient(#22201c, #171512);
  box-shadow: 0 24px 60px rgba(0, 0, 0, 0.45);
}

.contact > h2 {
  margin: 0;
  font-size: 9px;
  font-weight: 700;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.45);
}

/* Two columns on desktop, one on a phone. The message spans both — it is the
   field somebody spends the longest in — and so does "What is this about":
   its cards are a row of their own, as the island draws them, never squeezed
   into one field's column (seen without JavaScript, 19-11-2026). */
.contact__form {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(240px, 1fr));
  gap: 18px 20px;
  margin-top: 22px;
}

.contact__form .field:has(textarea),
.contact__form .reasons,
.contact__form .contact__submit {
  grid-column: 1 / -1;
}

/* The contact form's fields, matching the brief's rather than a third set of
   rules — the same fields doing the same job, and three copies would be two
   chances to drift. */
.contact .field {
  display: flex;
  flex-direction: column;
  gap: 7px;
}

.contact .field label {
  font-size: 8.5px;
  font-weight: 700;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.5);
}

.contact .field__hint {
  letter-spacing: 0.04em;
  text-transform: none;
  color: var(--paper-faint);
}

.contact :is(input, select, textarea) {
  width: 100%;
  padding: 13px 15px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: 11px;
  background: rgba(242, 237, 230, 0.05);
  color: var(--paper);
  font: inherit;
  font-size: 13px;
  line-height: 1.45;
  transition: border-color var(--quick), background var(--quick);
}

.contact textarea {
  min-height: 108px;
  resize: vertical;
}

.contact :is(input, select, textarea):focus-visible {
  outline: none;
  border-color: var(--gold-edge);
  background: rgba(242, 237, 230, 0.07);
}

/* A field the server marked as wrong.
   **This class had no styling at all until now** — carried in CLAUDE.md as a
   known gap since Module 9, because there was no public stylesheet to put it
   in. The sentence above the form says what to fix; this says where. Never
   colour alone: `aria-invalid` is on the control too, so a screen reader
   announces it. */
.contact .field--wrong :is(input, select, textarea) {
  border-color: #e8735b;
  border-width: 2px;
  background: rgba(232, 115, 91, 0.07);
}

.contact .field--wrong label {
  color: #e8735b;
}

/* A refusal the server drew goes by itself — bug 1d, the owner's word,
   18-11-2026: after the islands' 8 seconds (`messageThatGoes.ts`), a short
   fade. Without JavaScript nothing can see an edit, so time alone decides.
   Its room stays (the owner's choice), so nothing moves under the visitor.
   Only on the server's markup — an island draws its own and times it.
   Reduced motion: the site-wide rule above cuts the fade, never the wait. */
.goes-by-itself {
  animation: goes-by-itself 0.6s ease-in 8s forwards;
}

@keyframes goes-by-itself {
  to {
    opacity: 0;
    visibility: hidden;
  }
}

/* What the server said, above the form. `role="alert"` in the markup, so it
   is announced rather than only shown. */
.contact__problem,
.contact__sent {
  margin: 18px 0 0;
  padding: 14px 18px;
  border-radius: var(--radius);
  font-size: 13px;
  line-height: 1.55;
}

.contact__problem {
  border: 1px solid rgba(232, 115, 91, 0.5);
  background: rgba(232, 115, 91, 0.08);
  color: #f0a293;
}

.contact__sent {
  border: 1px solid rgba(52, 199, 123, 0.4);
  background: rgba(52, 199, 123, 0.1);
  color: #7bd9a6;
}

.contact__submit {
  justify-self: start;
  margin-top: 8px;
  padding: 15px 28px;
  border: none;
  border-radius: var(--radius-pill);
  background: var(--gold);
  color: var(--ink);
  font: inherit;
  font-size: 11px;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  cursor: pointer;
  transition: background var(--quick);
}

.contact__submit:hover,
.contact__submit:focus-visible {
  background: #fff;
}

@media (max-width: 720px) {
  .reasons,
  .contact {
    padding: 20px 18px 22px;
    border-radius: 18px;
  }

  .reasons__cards {
    grid-template-columns: 1fr;
    gap: 8px;
  }

  /* A touch target, per the design's 390 breakpoint. */
  .reason {
    min-height: 64px;
  }

  .contact__form {
    grid-template-columns: 1fr;
    gap: 14px;
  }

  .contact__submit {
    justify-self: stretch;
    text-align: center;
    padding: 18px 20px;
  }
}

/* ---- The studio grid ------------------------------------------------------
   The design's four info cells, rendered as however many have a setting
   behind them — see the `studio` macro. `gap: 2px` with a bordered container
   makes the hairlines out of the background showing through, which is why
   the cells carry no borders of their own. */

.studio {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(220px, 1fr));
  gap: 1px;
  margin-top: 34px;
  border: 1px solid rgba(242, 237, 230, 0.11);
  border-radius: var(--radius);
  background: rgba(242, 237, 230, 0.11);
  overflow: hidden;
  font-style: normal;
}

.studio__cell {
  padding: 20px 22px;
  background: #131110;
  transition: background var(--quick);
}

.studio__cell:hover {
  background: rgba(255, 216, 151, 0.06);
}

.studio__key {
  margin: 0;
  font-size: 8.5px;
  font-weight: 700;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.42);
}

.studio__value {
  margin: 9px 0 0;
  font-size: 14px;
  font-weight: 600;
  line-height: 1.45;
  color: var(--paper);
}

.studio__value a {
  color: inherit;
  text-decoration: none;
  border-bottom: 1px solid var(--gold-edge);
}

.studio__value a:hover,
.studio__value a:focus-visible {
  color: var(--gold);
}

@media (max-width: 720px) {
  .studio {
    grid-template-columns: 1fr;
  }

  .studio__cell {
    padding: 18px;
  }
}

/* ---- The receipt ----------------------------------------------------------
   What replaces the form once a message has been sent.

   **No ticket number**, and the design draws one — "ORDER TICKET
   TSINQ-2508-4173" with "Keep the ticket number." underneath. The inquiry has
   a reference and the sender is told it, but in the *confirmation email*: a
   page is something somebody may be standing behind, and an email is what
   they still have next week. See app/services/references.py.

   The plain form gets `.contact__sent` instead — a green bar above the form,
   because without JavaScript the form is still there and replacing it is not
   something a stylesheet can do. */

.receipt {
  margin-top: 34px;
  padding: 48px 46px 42px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: var(--radius-lg);
  background: linear-gradient(#22201c, #161411);
  box-shadow: 0 30px 70px rgba(0, 0, 0, 0.5);
  text-align: center;
}

.receipt__mark {
  display: grid;
  place-items: center;
  width: 86px;
  height: 86px;
  margin: 0 auto;
  border-radius: 50%;
  background: rgba(52, 199, 123, 0.14);
  color: #34c77b;
  font-size: 30px;
  font-weight: 700;
}

.receipt__title {
  margin: 22px 0 0;
  font-size: 30px;
  line-height: 1.15;
  letter-spacing: -0.02em;
  font-weight: 800;
}

.receipt__copy {
  max-width: 430px;
  margin: 12px auto 0;
  font-size: 13.5px;
  line-height: 1.6;
  color: var(--paper-soft);
}

.receipt__again {
  display: inline-block;
  margin-top: 30px;
  padding: 15px 28px;
  border: 1px solid var(--gold-edge);
  border-radius: var(--radius-pill);
  color: var(--gold);
  font-size: 11px;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  text-decoration: none;
  transition: background var(--quick);
}

.receipt__again:hover,
.receipt__again:focus-visible {
  background: var(--gold-dim);
}

/* The submit row: the button, and the way to start over beside it. */
.contact__actions-row {
  grid-column: 1 / -1;
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 16px;
  margin-top: 8px;
  padding-top: 22px;
  border-top: 1px solid rgba(242, 237, 230, 0.1);
}

/* The error slot under a field. Always in the document, so a message
   appearing does not push the rest of the form down — the design's
   `min-height: 14px`. */
.contact .field__problem {
  min-height: 14px;
  margin: 0;
  font-size: 10.5px;
  font-weight: 600;
  line-height: 1.4;
  color: #e8735b;
}

@media (max-width: 720px) {
  .receipt {
    padding: 30px 20px 26px;
  }

  .receipt__mark {
    width: 74px;
    height: 74px;
    font-size: 26px;
  }

  .receipt__title {
    font-size: 24px;
  }

  .receipt__again {
    display: block;
    text-align: center;
  }

  .contact__actions-row {
    flex-direction: column;
    align-items: stretch;
  }
}

/* ---- Sound Restoration ----------------------------------------------------
   Design handoff `design_handoff_subpages`, screens 13b (1440) and 16b (390).

   **The page is a tool, so its layout is a tool's**: the words, then the
   thing you use, with "what happens next" on a rail beside it. On a phone the
   rail moves under the tool, which is the design's own instruction.

   Built in steps — this is the page shell, the drop zone and the file chip.
   The presets, the player and the send flow follow.
   -------------------------------------------------------------------------- */

.restore {
  padding-top: 44px;
  padding-bottom: 80px;
}

/* The measure. `.band` is a full-width background and sets the gutter only,
   so what sits inside one needs its own — the lesson from the contact page,
   where its absence made every panel stretch to the viewport. */
.restore__inner {
  width: min(1100px, 100%);
  margin-inline: auto;
}

.restore__header {
  max-width: 900px;
}

.restore__heading {
  margin: 20px 0 0;
  font-size: clamp(28px, 4vw, 36px);
  line-height: 1.1;
  letter-spacing: -0.02em;
  font-weight: 800;
  text-wrap: pretty;
}

.restore__intro {
  margin-top: 16px;
  font-size: 14px;
  line-height: 1.7;
  color: var(--paper-soft);
}

/* What the preview is, and is not. Near the heading deliberately: it is what
   stops somebody judging the studio by a rough automatic pass. */
.restore__caveat {
  margin-top: 14px;
  font-size: 12px;
  line-height: 1.6;
  color: var(--paper-faint);
}

/* Content and rail. One column under 900px, which is where the design's two
   breakpoints stop being ambiguous. */
.restore__body {
  display: grid;
  grid-template-columns: minmax(0, 1fr) 300px;
  gap: 24px;
  margin-top: 34px;
  align-items: start;
}

.restore__panel {
  padding: 26px 28px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: 18px;
  background: linear-gradient(#22201c, #171512);
  box-shadow: 0 24px 60px rgba(0, 0, 0, 0.45);
}

.restore__label {
  margin: 0 0 18px;
  font-size: 9px;
  font-weight: 700;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.45);
}

/* ---- The drop zone ------------------------------------------------------- */

.dropzone {
  position: relative;
  border: 1.5px dashed rgba(242, 237, 230, 0.25);
  border-radius: 14px;
  transition: border-color var(--quick), background var(--quick);
}

/* The input is the control; the label is what you see. Kept in the layout
   rather than `display: none`, so it stays focusable and the focus ring below
   has something to sit on. */
.dropzone__input {
  position: absolute;
  width: 1px;
  height: 1px;
  opacity: 0;
}

.dropzone__label {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 8px;
  padding: 38px 24px;
  text-align: center;
  cursor: pointer;
}

.dropzone__lead {
  font-size: 14px;
  font-weight: 600;
}

.dropzone__sub {
  font-size: 11.5px;
  color: var(--paper-faint);
}

.dropzone:hover,
.dropzone--over {
  border-color: rgba(255, 216, 151, 0.55);
  background: rgba(255, 216, 151, 0.04);
}

/* The ring goes on the zone, because the input it belongs to is invisible.
   Without this, tabbing to the control shows nothing at all. */
.dropzone:has(.dropzone__input:focus-visible) {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* ---- The chosen file ----------------------------------------------------- */

.filechip {
  display: flex;
  align-items: center;
  gap: 14px;
  padding: 14px 16px;
  border: 1px solid var(--line-on-dark);
  border-radius: 14px;
  background: rgba(242, 237, 230, 0.04);
}

.filechip__mark {
  flex: none;
  display: grid;
  place-items: center;
  width: 36px;
  height: 36px;
  border-radius: 10px;
  background: rgba(255, 216, 151, 0.15);
  color: var(--gold);
  font-size: 16px;
}

/* `min-width: 0` so the name below can actually ellipsise — a flex child
   refuses to shrink past its content without it. */
.filechip__words {
  display: flex;
  flex-direction: column;
  gap: 3px;
  min-width: 0;
  flex: 1;
}

.filechip__name {
  font-size: 12.5px;
  font-weight: 700;
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
}

.filechip__meta {
  font-size: 11px;
  color: var(--paper-faint);
}

.restore__problem {
  margin: 16px 0 0;
  padding: 12px 16px;
  border: 1px solid rgba(232, 115, 91, 0.5);
  border-radius: var(--radius);
  background: rgba(232, 115, 91, 0.08);
  font-size: 12.5px;
  line-height: 1.55;
  color: #f0a293;
}

/* ---- What happens next --------------------------------------------------- */

.restore__next {
  padding: 24px 26px;
  border-radius: 18px;
  background: var(--dark-raised);
  box-shadow: 0 24px 60px rgba(0, 0, 0, 0.5);
}

.restore__next-heading {
  margin: 0;
  font-size: 9px;
  font-weight: 700;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.45);
}

.restore__next-text {
  margin-top: 12px;
  font-size: 13px;
  line-height: 1.65;
  color: var(--paper);
}

/* What somebody with no JavaScript gets: not a degraded player — the preview
   *is* Web Audio — but a real way to send the files. */
.restore__noscript {
  padding: 26px 28px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: 18px;
  background: linear-gradient(#22201c, #171512);
}

.restore__noscript h2 {
  margin: 0 0 10px;
  font-size: 18px;
  font-weight: 800;
}

.restore__noscript p {
  margin: 0 0 18px;
  font-size: 13px;
  line-height: 1.65;
  color: var(--paper-soft);
}

@media (max-width: 900px) {
  .restore__body {
    grid-template-columns: 1fr;
  }

  .restore__panel,
  .restore__noscript {
    padding: 20px 18px;
    border-radius: 16px;
  }

  .dropzone__label {
    padding: 32px 20px;
  }
}

@media (prefers-reduced-motion: reduce) {
  .dropzone {
    transition: none;
  }
}

/* ---- Restoration presets --------------------------------------------------
   Five passes and a loudness switch. Offered only once a file is loaded —
   chips above an empty drop zone are controls that do nothing. */

.presets {
  margin-top: 26px;
  padding-top: 22px;
  border-top: 1px solid rgba(242, 237, 230, 0.1);
}

.restore__label--tight {
  margin-bottom: 14px;
}

/* A fieldset, because the chips are one choice — see the island. Its default
   border and padding are removed; the grouping is semantic, not visual. */
.presets__set {
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  margin: 0;
  padding: 0;
  border: none;
}

.chip {
  padding: 10px 16px;
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius-pill);
  background: rgba(242, 237, 230, 0.04);
  font-size: 12px;
  font-weight: 600;
  cursor: pointer;
  transition: background var(--quick), border-color var(--quick),
    color var(--quick);
}

/* The radio is the control; the chip is what you see. Kept in the layout so
   it stays focusable and the ring below has something to sit on. */
.chip__input {
  position: absolute;
  width: 1px;
  height: 1px;
  opacity: 0;
}

.chip:has(.chip__input:checked) {
  background: var(--gold-dim);
  border-color: var(--gold-edge);
  color: var(--gold);
}

.chip:hover {
  border-color: var(--gold-edge);
}

.chip:has(.chip__input:focus-visible) {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* Reserved whether or not a preset is chosen, so choosing one does not push
   the switch below it down the page. */
.presets__blurb {
  min-height: 1.6em;
  margin: 12px 0 0;
  font-size: 12px;
  line-height: 1.6;
  color: var(--paper-faint);
}

/* ---- The normalize switch ------------------------------------------------- */

.switchrow {
  display: flex;
  align-items: center;
  gap: 12px;
  margin-top: 18px;
  padding-top: 18px;
  border-top: 1px solid rgba(242, 237, 230, 0.08);
  cursor: pointer;
}

.switchrow__input {
  position: absolute;
  width: 1px;
  height: 1px;
  opacity: 0;
}

.switchrow__track {
  flex: none;
  position: relative;
  width: 42px;
  height: 24px;
  border: 1px solid rgba(242, 237, 230, 0.24);
  border-radius: var(--radius-pill);
  background: rgba(242, 237, 230, 0.06);
  transition: background var(--quick), border-color var(--quick);
}

.switchrow__knob {
  position: absolute;
  top: 3px;
  left: 3px;
  width: 16px;
  height: 16px;
  border-radius: 50%;
  background: var(--paper-faint);
  transition: transform var(--quick), background var(--quick);
}

.switchrow:has(.switchrow__input:checked) .switchrow__track {
  background: var(--gold-dim);
  border-color: var(--gold-edge);
}

.switchrow:has(.switchrow__input:checked) .switchrow__knob {
  transform: translateX(18px);
  background: var(--gold);
}

.switchrow:has(.switchrow__input:focus-visible) .switchrow__track {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

.switchrow__words {
  display: flex;
  flex-direction: column;
  gap: 2px;
}

.switchrow__label {
  font-size: 13px;
  font-weight: 600;
}

.switchrow__sub {
  font-size: 11px;
  color: var(--paper-faint);
}

@media (prefers-reduced-motion: reduce) {
  .chip,
  .switchrow__track,
  .switchrow__knob {
    transition: none;
  }
}

/* ---- The proof-listen player ----------------------------------------------
   Play, a progress bar, and where the playhead is. The design's transport row.

   **No dry/wet fader yet.** It only means something once there is a processed
   pass to fade towards — which is the engine, and its own module. A fader
   that moves and changes nothing teaches somebody the processing is
   inaudible. */

.player {
  display: flex;
  align-items: center;
  gap: 14px;
  margin-top: 20px;
}

.player__play {
  flex: none;
  display: grid;
  place-items: center;
  width: 44px;
  height: 44px;
  border: none;
  border-radius: 50%;
  background: var(--gold);
  color: var(--ink);
  font-size: 13px;
  cursor: pointer;
  transition: background var(--quick);
}

.player__play:hover,
.player__play:focus-visible {
  background: #fff;
}

.player__track {
  flex: 1;
  height: 4px;
  border-radius: var(--radius-pill);
  background: rgba(242, 237, 230, 0.12);
  overflow: hidden;
}

.player__fill {
  height: 100%;
  background: var(--gold);
}

/* Tabular figures, so the seconds ticking over does not shift the layout —
   proportional digits are different widths and the row jitters. */
.player__time {
  flex: none;
  margin: 0;
  font-size: 11.5px;
  font-variant-numeric: tabular-nums;
  color: var(--paper-soft);
}

.player__total {
  color: var(--paper-faint);
}

@media (prefers-reduced-motion: reduce) {
  .player__play {
    transition: none;
  }
}

/* ---- Sending the files ----------------------------------------------------
   A centred modal on a wide screen, a bottom sheet on a phone. The design
   draws both; they are one component and the difference is here. */

.restore__send {
  margin-top: 24px;
  padding-top: 22px;
  border-top: 1px solid rgba(242, 237, 230, 0.1);
}

.restore__send-note {
  margin: 10px 0 0;
  font-size: 11.5px;
  line-height: 1.6;
  color: var(--paper-faint);
}

.sheet {
  position: fixed;
  inset: 0;
  z-index: 60;
  display: grid;
  place-items: center;
  padding: 24px;
}

.sheet__scrim {
  position: absolute;
  inset: 0;
  background: rgba(11, 10, 9, 0.76);
}

.sheet__panel {
  position: relative;
  width: min(520px, 100%);
  max-height: min(94vh, 760px);
  display: flex;
  flex-direction: column;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: 20px;
  background: linear-gradient(#22201c, #161411);
  box-shadow: 0 34px 80px rgba(0, 0, 0, 0.65);
  color: var(--paper);
}

/* The panel takes focus when it opens, so it needs no ring of its own — the
   controls inside it have theirs. */
.sheet__panel:focus {
  outline: none;
}

.sheet__header {
  position: relative;
  padding: 26px 28px 0;
}

.sheet__eyebrow {
  margin: 0;
  font-size: 8.5px;
  font-weight: 700;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--gold);
}

.sheet__title {
  margin: 10px 0 0;
  font-size: 22px;
  line-height: 1.2;
  font-weight: 800;
  padding-right: 40px;
}

.sheet__close {
  position: absolute;
  top: 20px;
  right: 20px;
  display: grid;
  place-items: center;
  width: 30px;
  height: 30px;
  border: 1px solid var(--line-on-dark);
  border-radius: 50%;
  background: transparent;
  color: var(--paper);
  font-size: 16px;
  cursor: pointer;
}

.sheet__progress {
  display: flex;
  gap: 6px;
  margin: 20px 28px 0;
}

.sheet__segment {
  flex: 1;
  height: 3px;
  border-radius: var(--radius-pill);
  background: rgba(242, 237, 230, 0.12);
}

.sheet__segment--done {
  background: var(--gold);
}

/* Scrolls inside the panel, so the header and footer stay put on a long
   step — the design's sticky header and footer. */
.sheet__body {
  flex: 1;
  overflow-y: auto;
  padding: 24px 28px;
}

.sheet__question {
  margin: 0 0 24px;
  padding: 0;
  border: none;
}

.sheet__question:last-child {
  margin-bottom: 0;
}

.sheet__legend {
  padding: 0 0 12px;
  font-size: 8.5px;
  font-weight: 700;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.45);
}

.sheet__options {
  display: flex;
  flex-direction: column;
  gap: 8px;
}

.option {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 12px;
  padding: 14px 16px;
  border: 1px solid var(--line-on-dark);
  border-radius: 12px;
  background: rgba(242, 237, 230, 0.04);
  cursor: pointer;
  transition: background var(--quick), border-color var(--quick);
}

.option__input {
  position: absolute;
  width: 1px;
  height: 1px;
  opacity: 0;
}

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

.option__label {
  font-size: 13px;
  font-weight: 600;
}

.option__blurb {
  font-size: 11px;
  line-height: 1.5;
  color: var(--paper-faint);
}

.option__tick {
  flex: none;
  display: grid;
  place-items: center;
  width: 22px;
  height: 22px;
  border: 1px solid rgba(242, 237, 230, 0.2);
  border-radius: 50%;
  font-size: 10px;
  color: transparent;
  transition: all var(--quick);
}

.option:has(.option__input:checked) {
  background: var(--gold-dim);
  border-color: var(--gold-edge);
}

.option:has(.option__input:checked) .option__tick {
  background: var(--gold);
  border-color: var(--gold);
  color: var(--ink);
}

.option:has(.option__input:focus-visible) {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

.sheet__fields {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
  gap: 16px;
}

.sheet__fields .field {
  display: flex;
  flex-direction: column;
  gap: 7px;
}

.sheet__fields .field--wide {
  grid-column: 1 / -1;
}

.sheet__fields .field__label {
  font-size: 8.5px;
  font-weight: 700;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.5);
}

.sheet__fields .field__note {
  letter-spacing: 0.04em;
  text-transform: none;
  color: var(--paper-faint);
}

.sheet__fields :is(input, select, textarea) {
  width: 100%;
  padding: 12px 14px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: 11px;
  background: rgba(242, 237, 230, 0.05);
  color: var(--paper);
  font: inherit;
  font-size: 13px;
}

.sheet__fields textarea {
  resize: vertical;
}

/* ---- The receipt --------------------------------------------------------- */

.sheet__done {
  text-align: center;
  padding: 12px 0;
}

.sheet__mark {
  display: grid;
  place-items: center;
  width: 64px;
  height: 64px;
  margin: 0 auto;
  border-radius: 50%;
  background: rgba(52, 199, 123, 0.14);
  color: #34c77b;
  font-size: 24px;
  font-weight: 700;
}

.sheet__copy {
  max-width: 380px;
  margin: 18px auto 0;
  font-size: 13.5px;
  line-height: 1.6;
  color: var(--paper-soft);
}

/* The reference. Shown on screen here — unlike a contact inquiry, where it
   goes only in the email — because this one *is* how a client reaches their
   ticket again. */
.sheet__reference {
  display: flex;
  flex-direction: column;
  gap: 6px;
  margin: 24px 0 0;
  padding: 16px;
  border: 1px solid var(--gold-edge);
  border-radius: 12px;
  background: var(--gold-dim);
  font-size: 18px;
  letter-spacing: 0.04em;
  color: var(--gold);
}

.sheet__reference-label {
  font-size: 8.5px;
  font-weight: 700;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.45);
}

.sheet__keep {
  margin: 10px 0 0;
  font-size: 11px;
  color: var(--paper-faint);
}

.sheet__problem {
  margin: 18px 0 0;
  padding: 12px 16px;
  border: 1px solid rgba(232, 115, 91, 0.5);
  border-radius: var(--radius);
  background: rgba(232, 115, 91, 0.08);
  font-size: 12.5px;
  line-height: 1.55;
  color: #f0a293;
}

.sheet__sending {
  margin: 18px 0 0;
  font-size: 12.5px;
  color: var(--paper-soft);
  font-variant-numeric: tabular-nums;
}

.sheet__footer {
  display: flex;
  align-items: center;
  justify-content: flex-end;
  gap: 14px;
  padding: 18px 28px;
  border-top: 1px solid rgba(242, 237, 230, 0.1);
  background: rgba(0, 0, 0, 0.25);
  border-radius: 0 0 20px 20px;
}

.sheet__footer .button--quiet {
  margin-right: auto;
}

.sheet__footer .button:disabled {
  opacity: 0.4;
  cursor: not-allowed;
}

/* A bottom sheet on a phone, as the design draws it. */
@media (max-width: 720px) {
  .sheet {
    padding: 0;
    place-items: end stretch;
  }

  .sheet__panel {
    width: 100%;
    max-height: 94vh;
    border-radius: 22px 22px 0 0;
    box-shadow: 0 -20px 60px rgba(0, 0, 0, 0.6);
  }

  /* A touch target, per the design's 390 breakpoint. */
  .sheet__close {
    width: 44px;
    height: 44px;
    top: 14px;
    right: 14px;
  }

  .sheet__fields {
    grid-template-columns: 1fr;
  }

  .sheet__footer {
    border-radius: 0;
  }

  .sheet__footer .button {
    flex: 1;
    justify-content: center;
    text-align: center;
  }
}

@media (prefers-reduced-motion: reduce) {
  .option,
  .option__tick {
    transition: none;
  }
}

/* ---- The service pages --------------------------------------------------
   Sound Design first, from the 31-08-2026 handoff. The shared visual system
   is already here — `.band--dark`, `.eyebrow` with its gold rule, and
   `.button--gold` — so what follows is this page's own geometry only.

   The design draws a fixed 1440 frame with 56px sides. That does not
   transfer: the site is responsive and its content has a measure. `--gutter`
   on the band gives the sides, and the column below gives the measure. */

.service__inner {
  width: min(1100px, 100%);
  margin-inline: auto;
}

/* **The band carries its own gap, top and bottom.** It was `60px 0 0` until
   12-09-2026 and ended flush against whatever came next — measured on the
   running page, the hero's last element touched the engine at exactly 0px.

   That read as two different bugs and is one: at 1440 the hero's last element
   is "Based in Apeldoorn", at 390 the columns stack so it is the
   Request/Hire pill. Padding the *band* fixes both, where nudging each child
   would be two rules that have to be remembered separately — the fault this
   stylesheet already records against `.service__photos`, which had bottom
   padding only and was correct on one page by accident. */
.service__hero {
  padding: 60px 0 72px;
}

/* The design's 76px display against a 360px column of intro. Below the
   breakpoint they stack, because 76px beside a paragraph on a phone is two
   columns of four words each. */
.service__hero-row {
  display: grid;
  grid-template-columns: 1fr 360px;
  gap: 60px;
  align-items: end;
  margin-top: 22px;
}

.service__heading {
  margin: 0;
  max-width: 900px;
  font-size: clamp(38px, 6vw, 76px);
  font-weight: 800;
  line-height: 0.98;
  letter-spacing: -0.035em;
  /* Balances the last line rather than leaving one orphaned word. Ignored by
     browsers that do not know it, which is the correct failure. */
  text-wrap: pretty;
}

.service__intro {
  color: var(--paper-soft);
  font-size: 15px;
  line-height: 1.9;
}

/* **An intro that follows the heading directly needs its own air.**
   Every other service hero puts the two in `.service__hero-row`, a grid whose
   `gap` separates them; the Gear List has no such row — its intro is a plain
   paragraph under the `<h1>` — so the two sat flush, measured at a 0px gap
   against 244px on Sound Recording. The heading's `line-height: 0.98` makes
   that worse than it sounds: a display face at 76px with tight leading has
   its descenders almost touching the line below.

   `:not()` on the row rather than a rule on the Gear List, because this is
   about *which arrangement* a hero uses rather than about which page it is —
   a second page built without the row would otherwise hit the same thing and
   nobody would know why. Below 820px the row stacks too and its own 24px gap
   covers it, which is why the value here is close to that. */
.service__hero > .service__heading + .service__intro,
:not(.service__hero-row) > .service__heading + .service__intro {
  margin-top: 20px;
}

.service__intro p {
  margin: 0;
}

/* The strip: one to four cells (04-11-2026, the owner's word). As many
   columns as cells up to three; four is three across and the fourth under
   the middle one — a T. The page names the count as a class, since the CSP
   allows no inline style.

   **The hairlines are the cells' own borders**, between neighbours only.
   They were the strip's background showing through 1px gaps, which in a T
   would have painted the two empty corners beside the fourth cell. */
.strip {
  --strip-line: rgba(242, 237, 230, 0.12);
  display: grid;
  grid-template-columns: repeat(3, 1fr);
  margin: 56px 0 0;
  padding: 0;
  list-style: none;
}

.strip--n1 {
  grid-template-columns: 1fr;
}

.strip--n2 {
  grid-template-columns: repeat(2, 1fr);
}

/* Each cell its own near-black, a shade under the band — the design's, and
   the owner's word to keep it (04-11-2026). On the cell, never the strip, so
   the T's empty corners stay the band's colour. */
.strip__cell {
  background: var(--dark);
  padding: 26px 28px;
}

.strip__cell + .strip__cell {
  border-left: 1px solid var(--strip-line);
}

/* The T: a line under the whole first row, so its three cells read as one
   bar (the owner's word, 04-11-2026), and the stem under the middle one,
   lined on both sides. The bar is the top row's own bottom border — the
   stem's top border would sit a pixel below the other two. */
.strip--n4 .strip__cell:nth-child(-n + 3) {
  border-bottom: 1px solid var(--strip-line);
}

.strip--n4 .strip__cell:nth-child(4) {
  grid-column: 2;
  border-right: 1px solid var(--strip-line);
}

.strip__key {
  margin: 0;
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

.strip__line {
  margin: 10px 0 0;
  font-size: 12.5px;
  line-height: 1.55;
  color: var(--paper-soft);
}

/* The statement and its Hire pill. */
.service__statement {
  display: flex;
  align-items: flex-start;
  gap: 64px;
  margin-top: 56px;
  /* The band below supplies its own top gap — see `.service__photos`. This
     one closes the hero band itself, which ends here on Sound Design. */
  padding-bottom: 56px;
}

.service__statement-text {
  margin: 0;
  max-width: 760px;
  font-size: clamp(20px, 2.4vw, 30px);
  line-height: 1.4;
  letter-spacing: -0.015em;
  text-wrap: pretty;
}

.service__statement .button {
  flex: none;
}

/* The design puts 56px above the photographs and 56px below them.
   **Both halves belong here**, not on whatever happens to precede it: Sound
   Design's hero ends with a statement carrying its own bottom padding, and
   Sound Recording's does not — so a band relying on its neighbour for the gap
   is a band that sits flush on one page and correct on the other. */

.service__photos {
  padding-top: 56px;
  padding-bottom: 56px;
  /* Between the pair and any carousels below it. Without this they touch, and
     two picture blocks with no air between them read as one. */
  display: flex;
  flex-direction: column;
  gap: 56px;
}

/* ---- The photo pair -----------------------------------------------------
   The design's two frames: 1.55fr and 1fr, 16px apart, 420px tall, radius 20.

   A list rather than two divs, because it is two of the same thing — and a
   list of one is still correct markup when a page fills only one frame. */

/* ---- Sound Recording's hero ---------------------------------------------
   The same two-column frame as Sound Design, with the heading stacked above a
   list rather than sitting beside an intro. */

.service__hero-row--recording {
  align-items: start;
  gap: 80px;
}

.service__hero-words {
  display: flex;
  flex-direction: column;
  gap: 34px;
  min-width: 0;
}

.service__location {
  margin: 0;
  max-width: 620px;
  font-size: 12.5px;
  line-height: 1.6;
  color: var(--paper-faint);
}

/* What the studio does on set: three rows, each a title against a
   right-aligned descriptor, divided by hairlines. */

.doeslist {
  max-width: 620px;
}

.doeslist__label {
  margin: 0 0 14px;
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

.doeslist__rows {
  margin: 0;
  padding: 0;
  list-style: none;
}

.doeslist__row {
  display: flex;
  justify-content: space-between;
  align-items: baseline;
  gap: 40px;
  padding: 13px 0;
  border-top: 1px solid rgba(242, 237, 230, 0.12);
}

/* The last row closes the list, so it reads as a block rather than as three
   things that ran out. */
.doeslist__row:last-child {
  border-bottom: 1px solid rgba(242, 237, 230, 0.12);
}

.doeslist__title {
  font-weight: 600;
  font-size: 13px;
}

.doeslist__text {
  font-size: 12.5px;
  color: var(--paper-soft);
  text-align: right;
}

/* The split pill: two halves in one rounded frame, the second gold. */

.splitpill {
  display: flex;
  align-items: center;
  gap: 8px;
  padding: 8px;
  border-radius: 999px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  background: rgba(242, 237, 230, 0.05);
}

.splitpill__half {
  flex: 1;
  padding: 12px 18px;
  border-radius: 999px;
  background: #3b3b3b;
  color: var(--paper-soft);
  font-weight: 700;
  font-size: 10.5px;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  text-align: center;
  text-decoration: none;
}

.splitpill__half:hover,
.splitpill__half:focus-visible {
  background: rgba(242, 237, 230, 0.12);
  color: var(--paper);
}

.splitpill__half--gold {
  background: var(--gold);
  color: var(--dark);
}

.splitpill__half--gold:hover,
.splitpill__half--gold:focus-visible {
  background: #ffffff;
  color: var(--dark);
}

/* Field Recording's hero has two intro lines and the design dims the second
   further — an afterthought under a statement. A rule rather than a second
   field: they are one piece of writing, and splitting them in the admin would
   ask somebody to know which box is the quieter one. */

.service__intro p + p {
  color: var(--paper-faint);
}

/* ---- Field Recording's action card --------------------------------------
   Four rows in one bordered frame, hairlines between. Two of them are links
   and two are text, and they are built to look identical — the difference is
   whether pressing does anything, which a cursor and a hover already say. */

.actions {
  margin: 0;
  padding: 0;
  list-style: none;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: 18px;
  overflow: hidden;
}

.actions__row + .actions__row {
  border-top: 1px solid rgba(242, 237, 230, 0.14);
}

.actions__row,
.actions__link {
  display: flex;
  align-items: center;
  gap: 16px;
  padding: 20px 24px;
  background: rgba(255, 255, 255, 0.03);
  text-decoration: none;
  color: inherit;
}

/* The row is already padded; a link inside one must not pad again, and it
   fills the row so the whole thing is pressable rather than the words only. */
.actions__link {
  flex: 1;
  margin: -20px -24px;
}

/* ---- The four marks -----------------------------------------------------
   Drawn rather than written: the row's title already names it, so markup
   would be announced twice — "circle Record" is worse than "Record".

   `::before` on the row, and on the *link* where there is one, because the
   link fills the row and the mark has to sit inside the same flex line. */

/* **One mark, on one element.** A row either holds a link or it does not, so
   the mark goes on whichever of the two is the flex container — never on both.

   The first version put it on the row *and* on the link, with a `:has()` rule
   meant to switch the row's off. That failed: `content: none` came before the
   per-mark rules that set `content`, so the row's own glyph came back and
   Request drew two question marks. Rows 1 and 2 hid it, because they draw with
   `background` rather than `content` and an empty box over an empty box looks
   like one box.

   Rules are scoped to `:not(:has(.actions__link))` on the row, so the two
   selectors are mutually exclusive rather than one undoing the other. */

.actions__row:not(:has(.actions__link))::before,
.actions__link::before {
  content: "";
  width: 26px;
  flex: none;
  text-align: center;
  color: var(--paper-soft);
  font-size: 16px;
  line-height: 1;
}

/* 1 — Record: the design's solid accent dot. */
.actions__row[data-mark="1"]:not(:has(.actions__link))::before,
.actions__row[data-mark="1"] .actions__link::before {
  height: 26px;
  border-radius: 50%;
  background: var(--record);
}

/* 2 — Search: three stacked bars, drawn with a gradient rather than three
   elements, because they are one mark and not three. */
.actions__row[data-mark="2"]:not(:has(.actions__link))::before,
.actions__row[data-mark="2"] .actions__link::before {
  height: 14px;
  background: repeating-linear-gradient(
    to bottom,
    rgba(242, 237, 230, 0.7) 0 2px,
    transparent 2px 6px
  );
}

/* 3 — Download, and 4 — Request. Glyphs, so they take the row's colour. */
.actions__row[data-mark="3"]:not(:has(.actions__link))::before,
.actions__row[data-mark="3"] .actions__link::before {
  content: "↓";
}

.actions__row[data-mark="4"]:not(:has(.actions__link))::before,
.actions__row[data-mark="4"] .actions__link::before {
  content: "?";
  font-weight: 700;
  font-size: 15px;
}

/* "gear" — the gear list's own mark, from the Sound Recording design: a
   26×20 bordered rectangle with two lines inside it, like a page of entries.

   **Named rather than numbered**, unlike the four above. Those belong to
   Field Recording's editable set, where the mark is a property of the *slot*
   so a renamed row keeps its icon. This row is fixed and has one icon — and
   numbering it `1` borrowed that page's record dot, which drew a filled
   circle where the design draws a list.

   The two inner lines are a gradient rather than child elements, because a
   `::before` has no children — the same technique the search mark uses, and
   for the same reason. `background-clip: content-box` keeps them off the
   border, and the padding is what sets their length. */

.actions__row[data-mark="gear"]:not(:has(.actions__link))::before,
.actions__row[data-mark="gear"] .actions__link::before {
  height: 20px;
  box-sizing: border-box;
  padding: 5px;
  border: 1px solid rgba(242, 237, 230, 0.45);
  border-radius: 4px;
  background-clip: content-box;
  background-image: repeating-linear-gradient(
    to bottom,
    rgba(242, 237, 230, 0.55) 0 1.5px,
    transparent 1.5px 4.5px
  );
}

/* The offer, against three descriptions. Gold, and dark text on it. */
.actions__row--offer,
.actions__row--offer .actions__link {
  background: var(--gold);
  color: var(--dark);
}

.actions__row--offer .actions__link:hover,
.actions__row--offer .actions__link:focus-visible {
  background: #ffffff;
}

.actions__row--offer .actions__text,
.actions__row--offer:not(:has(.actions__link))::before,
.actions__row--offer .actions__link::before {
  color: var(--dark);
}

.actions__link:hover,
.actions__link:focus-visible {
  background: rgba(255, 216, 151, 0.08);
}

.actions__title {
  display: block;
  font-weight: 700;
  font-size: 12.5px;
}

.actions__text {
  display: block;
  margin-top: 4px;
  font-size: 12.5px;
  line-height: 1.5;
  color: var(--paper-soft);
}

/* ---- The carousel on a dark page, side by side --------------------------
   The design puts the picture and its facts in one row — `1.4fr / 1fr` — and
   the stacked card was right for the homepage's narrower column and wrong on
   a service page, where it spans the page and the frame becomes a letterbox.

   The card's three children are the label, the frame and the body; the label
   spans both columns because it names the whole thing. */

/* **A dark card, not the homepage's white one.** The carousel was built for
   the light band it first sat in, and reusing it on a dark page put a white
   panel with a drop shadow on near-black. The reference draws one bordered
   frame on the ground itself: no fill, no shadow, a hairline between the
   picture and its facts.

   **A modifier on the card, not a page scope.** These rules were written for
   Field Recording's record panel and scoped to `.records`, which is why Sound
   Recording's carousel — the same card, in the same handoff, on the same dark
   ground — kept the light one. The shape belongs to the card, so the class
   does too, and Home keeps the light card it was designed with. */

.photos--dark {
  background: transparent;
  box-shadow: none;
  border: 1px solid rgba(242, 237, 230, 0.12);
  border-radius: 20px;
}

/* **The dark card draws no label of its own** — 12-09-2026.

   It used to render the carousel's name as a gold eyebrow inside the card,
   which gave this page two different section shapes: a carousel announced
   itself from inside its card, while a project block put "01 — ON SET" and a
   bold title *above* one. The design draws a single shape for both, so the
   name moved out to `photos.heading` and the card holds only the picture and
   its facts.

   `display: none`, not removed from the markup — the label is what
   `aria-labelledby` points at, and a referenced element that does not exist
   leaves the region unnamed. The same reasoning `.photos--bare` gives.

   Before this it was `padding: 0 0 16px`, which put the text one pixel from
   a 20px rounded corner and sliced the M of "MEDIA". Visible only below
   900px, because a `min-width: 900px` block restored the inset — worth
   keeping as a note: **a base rule that is only correct because a query
   overrides it is wrong wherever the query does not reach.** */
.photos--dark .photos__label {
  display: none;
}

/* The frame is flush inside the card — the border is the card's, and an
   inset picture inside a bordered panel is two frames. */
.photos--dark .photos__frame {
  margin: 0;
  border-radius: 0;
  box-shadow: none;
}

.photos--dark .photos__body {
  padding: 34px 32px;
  background: rgba(255, 255, 255, 0.02);
}

.photos--dark .photos__caption {
  font-size: 22px;
  letter-spacing: -0.02em;
  color: var(--paper);
}

.photos--dark .photos__description {
  color: var(--paper-soft);
}

/* **Rows with hairlines, not tiles.** The design lists the facts as
   key-against-value with a line under each; the tiled pair was the homepage's
   shape and puts two boxes where four rows belong. */
.photos--dark .photos__meta {
  display: block;
  margin-top: 18px;
}

.photos--dark .photos__meta > div {
  display: flex;
  justify-content: space-between;
  gap: 20px;
  padding: 11px 0;
  border-bottom: 1px solid rgba(242, 237, 230, 0.1);
  background: none;
}

.photos--dark .photos__meta dt {
  font-size: 12.5px;
  font-weight: 400;
  letter-spacing: 0;
  text-transform: none;
  color: var(--paper-soft);
}

.photos--dark .photos__meta dd {
  margin: 0;
  font-size: 12.5px;
  font-weight: 600;
  text-align: right;
  color: var(--paper);
}

/* The production a photograph belongs to, and where it leads — Module 21b,
   made a title card 24-09-2026 on the owner's word.

   **It was a key label over the links.** The name sat at 9px uppercase in the
   faint ink, which is the vocabulary this panel uses for "LOCATION" and
   "GEAR" — a heading naming a row rather than a title naming the work. With
   the function above it and the year beneath, the three facts read as the
   Projects page's own block does, and the card stands whether or not the
   production has a link yet.

   A hairline above it, because the card is a different kind of thing from
   the facts it follows: those describe the photograph, this names the work.

   On the element rather than under `.photos--dark`, like Listen: a light
   carousel's photographs belong to productions too, and the homepage's
   carousel is the light one. Only the colours change with the card. */
.photos__production {
  margin-top: 16px;
  padding-top: 14px;
  border-top: 1px solid rgba(27, 24, 21, 0.12);
}

/* What the studio did on it — the Projects page's eyebrow, in its gold. */
.photos__production-function {
  margin: 0;
  font-family: var(--font-mono);
  font-weight: 600;
  font-size: 9px;
  line-height: 1;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--rust);
}

/* The title of the work. A block, because it is a link as often as not and
   an inline one would take its underline across the line it sits on. */
.photos__production-name {
  display: block;
  margin: 8px 0 0;
  font-weight: 800;
  font-size: 19px;
  line-height: 1.15;
  letter-spacing: -0.015em;
  text-decoration: none;
  color: var(--ink);
}

/* Underlined only on hover and focus: the card already reads as a card, and
   a permanent rule under a 19px title fights the hairline above it. */
a.photos__production-name:hover,
a.photos__production-name:focus-visible {
  text-decoration: underline;
  text-underline-offset: 3px;
}

.photos__production-year {
  margin: 6px 0 0;
  font-family: var(--font-mono);
  font-weight: 600;
  font-size: 10.5px;
  line-height: 1;
  letter-spacing: 0.14em;
  color: var(--ink-faint);
}


.photos__production-links {
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  /* The gap below the year. Written into the shorthand rather than as a
     `margin-top` rule of its own: this one sets `margin: 0`, and a second
     rule of equal specificity is decided by source order — the trap this
     stylesheet has recorded three times. A card with no links has no list,
     so the space goes with them. */
  margin: 12px 0 0;
  padding: 0;
  list-style: none;
}

.photos__production-link {
  display: inline-flex;
  align-items: center;
  padding: 8px 16px;
  border: 1px solid var(--ink-faint);
  border-radius: var(--radius-pill);
  font-weight: 700;
  font-size: 10.5px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--ink);
  text-decoration: none;
  transition: border-color var(--quick), color var(--quick);
}

.photos__production-link:hover {
  border-color: var(--gold);
  color: var(--gold);
}

.photos--dark .photos__production-function {
  color: var(--gold);
}

.photos--dark .photos__production {
  border-top-color: rgba(242, 237, 230, 0.14);
}

.photos--dark .photos__production-year {
  color: var(--paper-faint);
}

.photos--dark .photos__production-name {
  /* Full paper, not the dimmed `--paper-soft` it wore as a key label: it is
     the title of the work now, and the brightest thing in the card. */
  color: var(--paper);
}

.photos--dark .photos__production-link {
  border-color: rgba(242, 237, 230, 0.3);
  color: var(--paper);
}

/* Listen to the recording this photograph was taken during.
   `claude_designs` draws it as a filled gold pill under the facts.

   **A link, not a player.** The library is where a sound is heard; this
   sends somebody to the recording, and it renders only when there is one
   that can actually be played — see `sound_link`.

   Styled beside the dark card because the record panel is where it appears.
   The rule is on the element rather than under `.photos--dark` so a light
   carousel gaining a recording is a legible button rather than a browser
   default, which is what it was on the first run. */
.photos__actions {
  margin: 18px 0 0;
}

.photos__listen {
  display: inline-flex;
  align-items: center;
  padding: 11px 26px;
  border-radius: var(--radius-pill);
  background: var(--gold);
  font-weight: 700;
  font-size: 10.5px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--ink);
  text-decoration: none;
  transition: filter var(--quick);
}

.photos__listen:hover {
  filter: brightness(1.08);
}

@media (min-width: 900px) {
  .photos--dark {
    display: grid;
    grid-template-columns: 1.4fr 1fr;
    align-items: start;
    overflow: hidden;
  }

  .photos--dark .photos__body {
    /* Filling the row rather than hugging its content, so the hairline
       between the columns runs the full height of the picture. */
    align-self: stretch;
  }

  /* The design's 380px frame in a 1.4fr column is about this shape. */
  .photos--dark .photos__frame .photos__image {
    aspect-ratio: 4 / 3;
  }
}

/* **A carousel inside an engine block brings no card of its own.**

   Blocks 02 and 03 of the Sound Recording design are the same bordered card
   as block 01 with pictures where the reel is — so `.block__card` already
   supplies the frame, the hairline and the facts column beside it. A `.photos`
   card dropped in there is a card inside a card, and its body would be a
   second panel under the block's own.

   So the carousel keeps only its picture: the label and the facts belong to
   the block, which draws them from the project. */

.photos--bare {
  background: transparent;
  box-shadow: none;
  border: 0;
  border-radius: 0;
}

.photos--bare .photos__label,
.photos--bare .photos__body {
  /* `display: none`, not absent from the markup. The label names the carousel
     for a screen reader through `aria-labelledby`, and a referenced element
     that does not exist leaves the region unnamed — hidden still names it. */
  display: none;
}

.photos--bare .photos__frame {
  margin: 0;
  border-radius: 0;
  box-shadow: none;
}

/* ---- The library teaser -------------------------------------------------
   Rows that lead into the real library rather than reproducing it. No play
   button and no download: the pack page has both, and this page has neither
   the audio nor the right to give it away. */

.packlist__all {
  margin-left: auto;
  font-weight: 700;
  font-size: 10.5px;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--gold);
}

.packlist__rows {
  margin: 0;
  padding: 0;
  list-style: none;
  border-top: 1px solid rgba(242, 237, 230, 0.12);
}

.packlist__row {
  border-bottom: 1px solid rgba(242, 237, 230, 0.12);
}

.packlist__link {
  display: flex;
  align-items: baseline;
  gap: 20px;
  padding: 14px 0;
  text-decoration: none;
  color: inherit;
}

.packlist__link:hover,
.packlist__link:focus-visible {
  background: rgba(255, 216, 151, 0.05);
}

.packlist__name {
  flex: 1;
  min-width: 0;
  font-weight: 600;
  font-size: 13px;
}

.packlist__count,
.packlist__hear {
  flex: none;
  font-size: 12.5px;
  color: var(--paper-soft);
}

.packlist__hear {
  color: var(--gold);
}

.pictures {
  display: grid;
  grid-template-columns: 1.55fr 1fr;
  gap: 16px;
  margin: 0;
  padding: 0;
  list-style: none;
}

.pictures__frame {
  /* Its own stacking context so the radius clips the image, and `min-width`
     so a wide photograph cannot push the grid past its column. */
  min-width: 0;
  border-radius: 20px;
  overflow: hidden;
  background: rgba(242, 237, 230, 0.04);
}

.pictures__image {
  display: block;
  width: 100%;
  /* **One shape at every width** (05-11-2026, the owner's word): the
     frame's shape at the full column, where the design draws it 420 high —
     the wide frame 1.569 and the second 1.012, `page_photos.PAIR_RATIOS`,
     which the admin's picker draws too. A fixed height made the shape drift
     with the window, so what somebody aimed in the picker held at no width
     but one. A narrower window now gives a lower frame, not a thinner one,
     and the two stay level because the shapes follow the columns' shares.
     The frame fills with the photograph rather than letting each set its
     own; `cover` crops, nothing is distorted. */
  aspect-ratio: 1.569;
  object-fit: cover;
}

.pictures__frame:nth-child(2) .pictures__image {
  aspect-ratio: 1.012;
}

.pictures__caption {
  margin: 0;
  padding: 14px 18px;
  font-size: 12.5px;
  line-height: 1.55;
  color: var(--paper-soft);
}

@media (max-width: 820px) {
  /* One column, each frame keeping its shape: stacked at a phone's width
     the wide frame is 350 by 223 and the second 350 by 346. They were both
     3:2 here, which cut the second frame's near-square aim to a strip.

     **No wider than 560, centred** (05-11-2026, the owner's choice after
     looking at a real iPad): a tablet in portrait stacks too, and at its
     column's 728 the near-square frame was 70% of the screen. Phones are
     narrower than the cap and keep the whole column. `page_photos`
     tells the browser the same width (`STACKED_CAP_PX`). */
  .pictures {
    grid-template-columns: 1fr;
    max-width: 560px;
    margin-inline: auto;
  }
}

/* ---- The engine blocks --------------------------------------------------
   One per project. The 120px gap is deliberate in the design — the blocks
   must not hug, or three cards read as one striped panel. */

.blocks {
  display: flex;
  flex-direction: column;
  gap: 120px;
  padding-bottom: 108px;
}

.block__title {
  display: flex;
  align-items: baseline;
  gap: 14px;
  margin-bottom: 16px;
  flex-wrap: wrap;
}

.block__index {
  margin: 0;
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--gold);
  white-space: nowrap;
}

.block__heading {
  margin: 0;
  font-size: clamp(20px, 2.2vw, 26px);
  font-weight: 800;
  line-height: 1.15;
  letter-spacing: -0.02em;
}

.block__card {
  display: grid;
  grid-template-columns: 1.4fr 1fr;
  gap: 2px;
  border: 1px solid rgba(242, 237, 230, 0.12);
  border-radius: 20px;
  overflow: hidden;
}

.block__reel {
  display: flex;
  flex-direction: column;
  background: rgba(242, 237, 230, 0.04);
  min-width: 0;
}

/* The caption — "Media reel · 0:37".

   **In the flow under the player, not floated over the column.** It was
   `position: absolute; bottom: 22px`, which is right for the design's empty
   frame and wrong the moment a real player sits in it: `bottom` anchors to
   the whole column, so the caption landed past the end of the video and on
   top of whatever the player draws there — the project name, and the
   "Loading the audio…" line, which read as two pieces of text hugging each
   other.

   The player already carries its own padding, so the caption sits close
   enough to the reel to belong to it without being pushed against it.

   The order comes from the markup rather than from `order:`, so what a
   screen reader meets is what somebody sees — a caption read before the
   thing it captions is a caption for nothing. */
.block__reel-caption {
  margin: 0;
  padding: 0 24px 22px;
  pointer-events: none;
  font-weight: 700;
  font-size: 11px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

.block__details {
  margin: 0;
  padding: 34px 32px;
  background: rgba(255, 255, 255, 0.02);
  display: flex;
  flex-direction: column;
  justify-content: center;
  gap: 14px;
}

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

.block__key {
  font-weight: 700;
  font-size: 8.5px;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

.block__line {
  margin: 0;
  font-size: 12.5px;
  line-height: 1.55;
  color: var(--paper-soft);
}

@media (max-width: 820px) {
  /* Every two-column arrangement on this page becomes one. The design is a
     desktop frame; none of these hold at a phone's width — 360px of intro
     beside a display heading is two narrow columns rather than a layout. */
  .service__hero-row,
  .block__card {
    grid-template-columns: 1fr;
    gap: 24px;
  }

  /* The recording hero's wider desktop gap goes with the columns. */
  .service__hero-row--recording {
    gap: 34px;
  }

  /* Less air under the hero than at a desk. The gap exists for the same
     reason at both widths — the band must not end flush against the engine —
     but 72px of empty dark is a third of a phone screen to scroll past, and
     here the element it separates is the Request/Hire pill rather than a line
     of text. */
  .service__hero {
    padding-bottom: 48px;
  }

  /* A title and its descriptor stack rather than sitting at opposite edges:
     40px between two short phrases is a gap on a phone, not a layout. */
  .doeslist__row {
    flex-direction: column;
    align-items: flex-start;
    gap: 4px;
  }

  .doeslist__text {
    text-align: left;
  }

  /* One column on a phone, whatever the count: the fourth simply comes last,
     and the lines run between the stacked cells instead of beside them. */
  .strip,
  .strip--n1,
  .strip--n2 {
    grid-template-columns: 1fr;
  }

  .strip__cell + .strip__cell {
    border-left: 0;
    border-top: 1px solid var(--strip-line);
  }

  .strip--n4 .strip__cell:nth-child(-n + 3) {
    border-bottom: 0;
  }

  .strip--n4 .strip__cell:nth-child(4) {
    grid-column: auto;
    border-right: 0;
  }

  .service__statement {
    flex-direction: column;
    gap: 24px;
  }

  .blocks {
    gap: 72px;
  }

  .block__card {
    gap: 0;
  }
}

/* ---- The gear list's three views ----------------------------------------
   Compare, guide and browse. The design draws them as pill buttons; they are
   *links*, because all three are addresses — a crawler follows each one, a
   visitor can send one, and the page works with no JavaScript.

   The current one is styled from `aria-current` rather than a class, so what
   a screen reader announces and what somebody can see cannot drift apart —
   the same rule the admin's chips follow. */

.gearviews {
  display: flex;
  flex-wrap: wrap;
  gap: 10px;
  margin-top: 34px;
}

.gearviews__tab {
  padding: 13px 22px;
  border: 1px solid rgba(242, 237, 230, 0.18);
  border-radius: 10px;
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--paper-soft);
  text-decoration: none;
  transition: all 0.18s ease;
}

.gearviews__tab:hover {
  color: var(--paper);
  border-color: rgba(242, 237, 230, 0.4);
}

.gearviews__tab[aria-current="page"] {
  border-color: var(--gold);
  background: rgba(255, 216, 151, 0.1);
  color: var(--gold);
}

/* Each tab carries two wordings from GEAR_VIEWS — "Compare kits" and
   "Compare" — and one is shown per width. `display: none` rather than
   `visibility` or a clip, because a hidden-but-present span is still read
   aloud, and a tab announced as "Compare kits Compare" is worse than either
   word alone. */
.gearviews__short {
  display: none;
}

@media (max-width: 900px) {
  /* The tablet handoff: the same three tabs at 12px 20px, a shade closer. */
  .gearviews {
    gap: 9px;
    margin-top: 28px;
  }

  .gearviews__tab {
    padding: 12px 20px;
  }
}

@media (max-width: 720px) {
  /* The phone handoff: three equal-width tabs across the row, one word each.
     `flex: 1` rather than a grid, so a fourth view — if one ever exists —
     still shares the row rather than wrapping under it. */
  .gearviews {
    flex-wrap: nowrap;
    gap: 6px;
    margin-top: 24px;
  }

  .gearviews__tab {
    flex: 1;
    padding: 13px 8px;
    text-align: center;
    letter-spacing: 0.12em;
  }

  .gearviews__long {
    display: none;
  }

  .gearviews__short {
    display: inline;
  }
}

@media (prefers-reduced-motion: reduce) {
  .gearviews__tab {
    transition: none;
  }
}

/* ---- The gear list's bands ----------------------------------------------
   Each carries its own vertical space, and none relies on its neighbour for
   it. `.service__photos` already records why: a band spaced by whatever
   happens to precede it is correct on one page by accident and flush on the
   next. Here all three sections sat flush — the tabs against the cards, and
   "Full spec comparison" against the card bottoms.

   The numbers are the design's own (`padding: 44px 56px 0` on the kits and
   `64px 56px 90px` on the comparison). Only the vertical halves are taken:
   the 56px sides are the design's gutter, which `--gutter` on the band
   already supplies. */

.service__kits {
  padding-top: 44px;
}

.service__spectable {
  padding-top: 64px;
  padding-bottom: 90px;
}

/* A view that is the last thing on the page needs the bottom half too — the
   contact bar follows it directly. The compare view does not: its comparison
   table already carries the 90px. */
.service__kits--only {
  padding-bottom: 90px;
}

/* ---- The kit cards ------------------------------------------------------
   Three side by side, from the gear list design. The middle one is drawn in
   gold — the kit most productions want — and that is a flag on the row rather
   than a position, because "recommended" is an editorial decision. */

.kits {
  display: grid;
  grid-template-columns: repeat(3, 1fr);
  gap: 16px;
  margin: 0;
  padding: 0;
  list-style: none;
}

.kit {
  display: flex;
  flex-direction: column;
  padding: 26px 26px 28px;
  border: 1px solid rgba(242, 237, 230, 0.12);
  border-radius: 18px;
  background: rgba(255, 255, 255, 0.02);
}

.kit--accent {
  border-color: rgba(255, 216, 151, 0.45);
  background: rgba(255, 216, 151, 0.05);
}

.kit__tag {
  margin: 0;
  font-weight: 700;
  font-size: 8.5px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--gold);
}

.kit__name {
  margin: 12px 0 0;
  font-size: 26px;
  font-weight: 800;
  line-height: 1.1;
  letter-spacing: -0.02em;
}

.kit__claim {
  margin: 6px 0 0;
  font-size: 13px;
  color: var(--paper-soft);
}

.kit__suits {
  margin: 12px 0 0;
  font-size: 11.5px;
  line-height: 1.6;
  color: var(--paper-faint);
}

/* The design's picture frame with the kit's letter in it. There is no
   photograph of a kit, and the letter is what stops this being dead space. */
.kit__letter {
  display: flex;
  align-items: flex-end;
  height: 190px;
  margin: 20px 0 0;
  padding: 18px;
  border: 1px dashed rgba(242, 237, 230, 0.18);
  border-radius: 14px;
  background: rgba(242, 237, 230, 0.04);
  font-size: 44px;
  font-weight: 800;
  line-height: 1;
  color: rgba(242, 237, 230, 0.14);
}

.kit__rows {
  margin: 22px 0 0;
}

.kit__row {
  display: flex;
  justify-content: space-between;
  gap: 16px;
  padding: 10px 0;
  border-bottom: 1px solid rgba(242, 237, 230, 0.08);
}

.kit__key {
  font-weight: 700;
  font-size: 8.5px;
  line-height: 1.3;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

.kit__value {
  margin: 0;
  font-weight: 700;
  font-size: 12px;
  line-height: 1.3;
  text-align: right;
  color: var(--paper);
}

/* Not carried. Dimmed rather than hidden: the design keeps the row so the
   three cards stay aligned, and an absent line is itself information. */
.kit__value--absent {
  color: rgba(242, 237, 230, 0.3);
}

.kit__total {
  display: flex;
  justify-content: space-between;
  align-items: center;
  gap: 16px;
  margin: 18px 0 0;
  padding: 13px 16px;
  border-radius: 10px;
  background: rgba(242, 237, 230, 0.06);
  color: var(--paper-soft);
}

.kit--accent .kit__total {
  background: rgba(255, 216, 151, 0.16);
  color: var(--gold);
}

.kit__total-key {
  font-weight: 700;
  font-size: 8.5px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
}

.kit__total-value {
  font-weight: 700;
  font-size: 12px;
}

.kit__chips {
  display: flex;
  flex-wrap: wrap;
  gap: 6px;
  margin: 16px 0 0;
  padding: 0;
  list-style: none;
}

.kit__chip {
  padding: 6px 11px;
  border: 1px solid rgba(242, 237, 230, 0.16);
  border-radius: var(--radius-pill, 999px);
  font-weight: 600;
  font-size: 9.5px;
  letter-spacing: 0.06em;
  color: var(--paper-soft);
}

/* `margin-top: auto` pushes it to the bottom, so the three links line up
   however much the cards differ in height. */
.kit__more {
  margin-top: auto;
  padding-top: 20px;
  border-top: 1px solid rgba(242, 237, 230, 0.12);
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--gold);
  text-decoration: none;
}

.kit__more::after {
  content: " →";
}

.kit__more:hover {
  color: var(--paper);
}

/* ---- The gear guide -----------------------------------------------------
   Four questions and a recommendation. The only gear list view that is an
   island: compare and browse are documents, this is a flow.

   The fallback under the mount point is the comparison table, so these rules
   style the React output and the `.spectable` rules already style what
   somebody with no JavaScript sees. */

.guide {
  max-width: 720px;
}

.guide__lead,
.guide__fallback-note {
  margin: 0;
  max-width: 620px;
  font-size: 13.5px;
  line-height: 1.7;
  color: var(--paper-soft);
}

/* The fallback's own note, above the table it introduces. */
.guide__fallback-note {
  margin-top: 12px;
  color: var(--paper-faint);
}

/* Progress. Four bars filling left to right — `aria-hidden`, because the
   counter beneath says the same in words. */
.guide__steps {
  display: flex;
  gap: 8px;
  margin: 26px 0 0;
  padding: 0;
  list-style: none;
}

.guide__step {
  flex: 1;
  height: 2px;
  background: rgba(242, 237, 230, 0.16);
}

.guide__step--done {
  background: var(--gold);
}

.guide__counter {
  margin: 32px 0 0;
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--gold);
}

/* A fieldset, because the answers are one question's options — that is what
   groups a set of radios for a screen reader. Its default border and padding
   are removed rather than styled. */
.guide__question {
  margin: 0;
  padding: 0;
  border: 0;
}

.guide__title {
  padding: 0;
  margin-top: 14px;
  max-width: 640px;
  font-size: 34px;
  font-weight: 800;
  line-height: 1.15;
  letter-spacing: -0.025em;
}

.guide__hint {
  margin: 12px 0 0;
  max-width: 700px;
  font-size: 13px;
  line-height: 1.6;
  color: rgba(242, 237, 230, 0.55);
}

.guide__answers {
  display: flex;
  flex-direction: column;
  gap: 10px;
  margin-top: 26px;
}

/* The whole row is the label, so pressing anywhere in it picks the answer —
   a real `<label>` gives that for free, where a div would need a handler. */
.guide__answer {
  display: flex;
  align-items: flex-start;
  gap: 14px;
  padding: 16px 18px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: 12px;
  background: rgba(255, 255, 255, 0.02);
  cursor: pointer;
  transition: border-color 0.18s ease, background 0.18s ease;
}

.guide__answer:hover {
  border-color: rgba(242, 237, 230, 0.32);
}

.guide__answer--picked {
  border-color: rgba(255, 216, 151, 0.5);
  background: rgba(255, 216, 151, 0.07);
}

/* The radio itself is drawn rather than hidden: `appearance: none` with a
   real input keeps the keyboard behaviour and the announced state, where
   `display: none` would take the control out of the tab order entirely. */
.guide__radio {
  appearance: none;
  flex: none;
  width: 18px;
  height: 18px;
  margin: 1px 0 0;
  border: 1px solid rgba(242, 237, 230, 0.35);
  border-radius: 50%;
  background: transparent;
  cursor: pointer;
}

.guide__radio:checked {
  border-color: var(--gold);
  /* The dot, drawn with an inset shadow so no pseudo-element is needed. */
  box-shadow: inset 0 0 0 4px var(--gold);
}

.guide__radio:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 3px;
}

.guide__answer-body {
  display: flex;
  flex-direction: column;
  gap: 5px;
}

.guide__answer-label {
  font-weight: 700;
  font-size: 13px;
  line-height: 1.2;
}

.guide__answer-detail {
  font-size: 11.5px;
  line-height: 1.5;
  color: rgba(242, 237, 230, 0.5);
}

.guide__nav {
  display: flex;
  gap: 10px;
  margin-top: 26px;
}

.guide__back,
.guide__next,
.guide__restart,
.guide__go {
  padding: 14px 26px;
  border-radius: var(--radius-pill, 999px);
  font-weight: 700;
  font-size: 10.5px;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  text-decoration: none;
  cursor: pointer;
  transition: background 0.18s ease, border-color 0.18s ease;
}

.guide__back,
.guide__restart {
  border: 1px solid rgba(242, 237, 230, 0.2);
  background: transparent;
  color: var(--paper-soft);
}

.guide__back:hover,
.guide__restart:hover {
  background: rgba(242, 237, 230, 0.06);
}

.guide__next,
.guide__go {
  border: 1px solid rgba(255, 216, 151, 0.6);
  background: transparent;
  color: var(--gold);
}

.guide__next:hover,
.guide__go:hover {
  background: rgba(255, 216, 151, 0.14);
}

.guide__go::after {
  content: " →";
}

/* **`aria-disabled`, never `:disabled`.** A disabled button cannot be
   focused, so a keyboard reader meets a control they can neither use nor
   learn the reason for. `:disabled` will never match this, which is why it
   needs its own rule. */
.guide__next[aria-disabled="true"] {
  border-color: rgba(242, 237, 230, 0.16);
  color: rgba(242, 237, 230, 0.3);
  cursor: not-allowed;
}

.guide__next[aria-disabled="true"]:hover {
  background: transparent;
}

/* The brief's Next and its segments follow the guide since 22-09-2026: refused
   until the question is answered, and drawn as refused. */
.briefnav__buttons .button[aria-disabled="true"] {
  border-color: rgba(242, 237, 230, 0.16);
  background: transparent;
  color: rgba(242, 237, 230, 0.3);
  cursor: not-allowed;
}

.briefnav__segment[aria-disabled="true"] {
  opacity: 0.3;
  cursor: not-allowed;
}

/* ---- The result --------------------------------------------------------- */

.guide__eyebrow {
  margin: 0;
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  color: var(--gold);
}

.guide__result {
  margin: 14px 0 0;
  font-size: 38px;
  font-weight: 800;
  line-height: 1.1;
  letter-spacing: -0.03em;
}

.guide__claim {
  margin: 6px 0 0;
  font-size: 26px;
  line-height: 1.2;
  color: rgba(242, 237, 230, 0.7);
}

/* The design's quoted paragraph: a gold rule down the left rather than a box,
   so it reads as an aside rather than as another panel. */
.guide__blurb {
  margin: 24px 0 0;
  padding: 24px 28px;
  border-left: 3px solid var(--gold);
  background: rgba(255, 255, 255, 0.03);
  font-size: 13.5px;
  line-height: 1.75;
  color: rgba(242, 237, 230, 0.72);
}

.guide__features {
  margin: 22px 0 0;
  border: 1px solid rgba(242, 237, 230, 0.12);
  border-radius: 16px;
  overflow: hidden;
}

.guide__feature {
  display: flex;
  justify-content: space-between;
  gap: 16px;
  padding: 16px 22px;
  border-top: 1px solid rgba(242, 237, 230, 0.08);
}

.guide__feature:first-child {
  border-top: 0;
}

.guide__feature-name {
  font-weight: 700;
  font-size: 8.5px;
  line-height: 1.3;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

.guide__feature-value {
  margin: 0;
  font-weight: 700;
  font-size: 13px;
  line-height: 1.3;
  text-align: right;
}

.guide__feature-value--absent {
  color: rgba(242, 237, 230, 0.3);
}

.guide__actions {
  display: flex;
  flex-wrap: wrap;
  gap: 10px;
  margin-top: 24px;
}

/* ---- The glossary ------------------------------------------------------- */

.guide__terms {
  margin-top: 26px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: 14px;
  overflow: hidden;
}

.guide__terms-toggle {
  display: flex;
  align-items: center;
  gap: 12px;
  width: 100%;
  padding: 18px 22px;
  border: 0;
  background: rgba(255, 255, 255, 0.03);
  font-weight: 700;
  font-size: 10.5px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  text-align: left;
  color: var(--paper);
  cursor: pointer;
}

.guide__terms-toggle:hover {
  background: rgba(255, 255, 255, 0.06);
}

.guide__terms-mark {
  display: flex;
  align-items: center;
  justify-content: center;
  flex: none;
  width: 24px;
  height: 24px;
  border: 1px solid rgba(255, 216, 151, 0.5);
  border-radius: 50%;
  font-size: 10px;
  color: var(--gold);
}

/* The caret, drawn from the button's own state so what is announced and what
   is seen cannot drift — the same rule the admin's disclosure rows follow. */
.guide__terms-toggle::after {
  content: "▾";
  margin-left: auto;
  font-size: 12px;
  color: rgba(242, 237, 230, 0.5);
}

.guide__terms-toggle[aria-expanded="true"]::after {
  content: "▴";
}

.guide__terms-list {
  margin: 0;
}

.guide__term {
  padding: 20px 22px;
  border-top: 1px solid rgba(242, 237, 230, 0.08);
}

.guide__term-name {
  font-weight: 700;
  font-size: 12.5px;
  line-height: 1;
}

.guide__term-body {
  margin: 9px 0 0;
  max-width: 640px;
  font-size: 12px;
  line-height: 1.75;
  color: var(--paper-soft);
}

/* ---- The glossary as its own view ----------------------------------------
   `?view=faq`, added 04-10-2026 — the owner pointed out the question mark was
   reachable only by answering four questions first.

   **Its own rules rather than reusing `.guide__term`.** Those sit inside a
   disclosure the guide opens over its result: 12.5px against a panel, with a
   hairline between entries, sized to be skimmed after the answer somebody
   came for. This is the whole page, read on purpose, so it carries the band's
   own measure and reads at the size the rest of the page does.

   The shape is deliberately the same — a term, then what it means, with a
   rule between — because they are one list seen two ways, and two layouts for
   the same five definitions would read as two different things. */

.gearfaq {
  margin: 0;
  /* The public column, not the band's full width: this is prose, and a
     definition running the width of a desk is one nobody finishes. The
     measure `.block__card` and the About page's markers already use. */
  max-width: 760px;
}

.gearfaq__entry {
  padding: 26px 0;
}

/* The rule goes between, never above the first or below the last — a line
   under the last entry reads as a list that was cut off. */
.gearfaq__entry + .gearfaq__entry {
  border-top: 1px solid rgba(242, 237, 230, 0.08);
}

.gearfaq__question {
  font-weight: 700;
  font-size: 15px;
  line-height: 1.3;
}

.gearfaq__answer {
  margin: 10px 0 0;
  font-size: 13.5px;
  line-height: 1.8;
  color: var(--paper-soft);
}

@media (max-width: 720px) {
  .gearfaq__entry {
    padding: 22px 0;
  }

  .gearfaq__question {
    font-size: 14px;
  }
}

/* ---- The guide at a tablet's width ----------------------------------------
   The responsive handoff (07-09-2026): question 30px, the answers in a two-up
   grid capped at 700px, Back and Next still side by side, the result column
   capped at 660px. These were the *phone's* sizes until then — one block for
   everything under 900px, so an 834px screen got 26px questions in a single
   column with most of its width empty. */
@media (max-width: 900px) {
  .guide__title {
    max-width: 560px;
    font-size: 30px;
  }

  .guide__hint {
    max-width: 600px;
  }

  .guide__answers {
    display: grid;
    grid-template-columns: 1fr 1fr;
    max-width: 700px;
    margin-top: 22px;
  }

  .guide__answer-label {
    font-size: 12.5px;
  }

  .guide__answer-detail {
    font-size: 11px;
  }

  .guide__nav {
    margin-top: 22px;
  }

  .guide__result {
    font-size: 34px;
  }

  .guide__claim {
    font-size: 23px;
  }

  .guide__blurb {
    padding: 20px 24px;
    font-size: 13px;
  }

  .guide__back,
  .guide__next,
  .guide__restart,
  .guide__go {
    padding: 13px 24px;
  }
}

/* ---- The guide on a phone ---------------------------------------------------
   One column again, 26px question, the answers stacked at 9px. Back becomes
   a 40px arrow pill and Next takes the rest of the row; the result's two
   buttons stack full width. */
@media (max-width: 720px) {
  .guide__lead {
    font-size: 13px;
    line-height: 1.65;
  }

  .guide__steps {
    gap: 6px;
    margin-top: 20px;
  }

  .guide__title {
    font-size: 26px;
  }

  .guide__hint {
    font-size: 12.5px;
  }

  .guide__answers {
    display: flex;
    flex-direction: column;
    gap: 9px;
    max-width: none;
  }

  .guide__answer-label {
    font-size: 13px;
    line-height: 1.25;
  }

  .guide__answer-detail {
    font-size: 11.5px;
  }

  .guide__nav {
    gap: 8px;
  }

  /* **The word stays; only its size goes.** `font-size: 0` on the button
     leaves "Back" as its accessible name, where `display: none` on the text
     or a bare "←" would give a screen reader a button called nothing or
     called "leftwards arrow". The arrow is drawn on a pseudo-element at its
     own size. */
  .guide__back {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    flex: none;
    width: 40px;
    height: 40px;
    padding: 0;
    font-size: 0;
  }

  .guide__back::before {
    content: "←";
    font-size: 15px;
    letter-spacing: 0;
  }

  .guide__next {
    flex: 1;
    padding: 14px 20px;
    text-align: center;
  }

  .guide__result {
    font-size: 30px;
  }

  .guide__claim {
    font-size: 20px;
  }

  .guide__blurb {
    padding: 18px 20px;
    line-height: 1.7;
  }

  .guide__actions {
    flex-direction: column;
    gap: 8px;
  }

  .guide__go,
  .guide__restart {
    padding: 15px 20px;
    text-align: center;
  }

  .guide__terms-toggle {
    padding: 16px 18px;
    font-size: 10px;
  }

  .guide__term {
    padding: 18px;
  }
}

@media (prefers-reduced-motion: reduce) {
  .guide__answer,
  .guide__back,
  .guide__next,
  .guide__restart,
  .guide__go {
    transition: none;
  }
}

/* ---- Browse: each kit read in full --------------------------------------
   The design's two columns — a 420px picture frame and the kit's words —
   at `1fr 1.5fr` with a 40px gap, stacked 64px apart.

   The frame is the compare card's frame at a different size, which is the
   same decision that put framing on the *place* rather than on the asset: a
   photograph in a 420px frame shows a different part of itself than one in a
   190px card. Both hold either the photograph or the lettered empty state. */

.browse {
  display: flex;
  flex-direction: column;
  gap: 64px;
}

.browse__kit {
  display: grid;
  grid-template-columns: 1fr 1.5fr;
  gap: 40px;
  align-items: start;
  /* The compare card's "See kit →" links to `#kit-{id}`, so an anchor landing
     under the sticky header would put the kit's name off-screen. */
  scroll-margin-top: 24px;
}

/* The picture frame. `position: relative` for the tag pinned inside it, and
   the letter sits at the bottom the way the design draws it. */
.browse__frame {
  position: relative;
  display: flex;
  align-items: flex-end;
  height: 420px;
  padding: 24px;
  border: 1px dashed rgba(242, 237, 230, 0.18);
  border-radius: 18px;
  background: rgba(242, 237, 230, 0.04);
}

/* A photograph fills the frame, so the dashed border would draw *over* the
   picture — it belongs to the empty state. */
.browse__frame:has(.browse__photo) {
  padding: 0;
  border-style: none;
  background: none;
}

.browse__tag {
  position: absolute;
  left: 24px;
  top: 22px;
  z-index: 1;
  margin: 0;
  padding: 8px 14px;
  border: 1px solid rgba(255, 216, 151, 0.5);
  border-radius: 8px;
  background: rgba(18, 17, 16, 0.55);
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--gold);
}

/* The same fixed frame as the compare card, one size up: the picture adapts
   and the layout does not. See app/services/framing.py. */
.browse__photo {
  display: block;
  width: 100%;
  height: 420px;
  border-radius: 18px;
  object-fit: cover;
}

.browse__letter {
  margin: 0;
  font-size: 64px;
  font-weight: 800;
  line-height: 1;
  color: rgba(242, 237, 230, 0.14);
}

.browse__name {
  margin: 0;
  font-size: 34px;
  font-weight: 800;
  line-height: 1.1;
  letter-spacing: -0.025em;
}

.browse__claim {
  margin: 6px 0 0;
  font-size: 14px;
  color: var(--paper-soft);
}

.browse__blurb {
  margin: 16px 0 0;
  max-width: 620px;
  font-size: 12.5px;
  line-height: 1.7;
  color: var(--paper-soft);
}

/* The design's three highlighted boxes. `gap: 2px` with the border on the
   wrapper draws the hairlines between them, so a kit with two lines or four
   needs no separate rule. */
.browse__highlights {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(140px, 1fr));
  gap: 2px;
  margin: 22px 0 0;
  border: 1px solid rgba(242, 237, 230, 0.12);
  border-radius: 14px;
  overflow: hidden;
}

.browse__highlight {
  padding: 16px 18px;
  background: rgba(255, 255, 255, 0.03);
}

.browse__panel {
  margin-top: 20px;
  border: 1px solid rgba(242, 237, 230, 0.12);
  border-radius: 14px;
  overflow: hidden;
}

.browse__group {
  margin: 0;
  padding: 12px 18px;
  background: rgba(255, 216, 151, 0.08);
  font-weight: 700;
  font-size: 8.5px;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--gold);
}

.browse__lines {
  margin: 0;
}

.browse__line {
  display: flex;
  justify-content: space-between;
  gap: 16px;
  padding: 11px 18px;
  border-top: 1px solid rgba(242, 237, 230, 0.08);
}

.browse__key {
  font-weight: 700;
  font-size: 8.5px;
  line-height: 1.3;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

.browse__value {
  margin: 0;
  font-weight: 700;
  font-size: 13px;
  line-height: 1.3;
  color: var(--paper);
}

.browse__highlight .browse__value {
  margin-top: 9px;
}

.browse__line .browse__value {
  text-align: right;
}

/* Not carried. Dimmed rather than hidden, the same rule the compare card
   follows: an absent line is itself information. */
.browse__value--absent {
  color: rgba(242, 237, 230, 0.3);
}

/* The equipment list's link, at the foot of a browse block.

   The design's gold pill, and the same shape `.kit__more` uses on the compare
   card — the two are the only things a visitor presses in either view, so
   they should not be two different treatments of the same idea. */
.browse__kitlist {
  display: inline-block;
  margin-top: 22px;
  padding: 13px 22px;
  border: 1px solid rgba(255, 216, 151, 0.6);
  border-radius: var(--radius-pill, 999px);
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--gold);
  text-decoration: none;
  transition: background var(--quick, 0.18s ease);
}

.browse__kitlist:hover {
  background: rgba(255, 216, 151, 0.14);
}

.browse__kitlist::after {
  content: " →";
}

@media (prefers-reduced-motion: reduce) {
  .browse__kitlist {
    transition: none;
  }
}

.browse__chips {
  display: flex;
  flex-wrap: wrap;
  gap: 6px;
  margin: 18px 0 0;
  padding: 0;
  list-style: none;
}

/* ---- Browse at a tablet's width ---------------------------------------------
   The handoff keeps the two columns, closer: `1fr 1.35fr` with a 26px gap, a
   340px frame, the highlights as three columns. One column here — which is
   what the phone rule did for everything under 900px — put a 420px frame
   over the words on a screen wide enough for both. */
@media (max-width: 900px) {
  .browse {
    gap: 48px;
  }

  .browse__kit {
    grid-template-columns: 1fr 1.35fr;
    gap: 26px;
  }

  /* The frame and the photograph inside it share one height at every
     width, or a kit with a picture stands taller than one without — the
     rule `.kit__photo` records for the compare card. */
  .browse__frame,
  .browse__photo {
    height: 340px;
    border-radius: 16px;
  }

  .browse__frame {
    padding: 20px;
  }

  .browse__tag {
    left: 20px;
    top: 18px;
    padding: 7px 12px;
  }

  .browse__letter {
    font-size: 50px;
  }

  .browse__name {
    margin-top: 10px;
    font-size: 28px;
  }

  .browse__claim {
    font-size: 13.5px;
  }

  .browse__blurb {
    margin-top: 14px;
  }

  .browse__highlights {
    margin-top: 18px;
    border-radius: 12px;
  }

  .browse__highlight {
    padding: 13px 14px;
  }

  .browse__highlight .browse__value {
    margin-top: 8px;
    font-size: 12px;
  }

  .browse__panel {
    margin-top: 16px;
    border-radius: 12px;
  }

  .browse__group {
    padding: 11px 16px;
  }

  .browse__line {
    gap: 12px;
    padding: 10px 16px;
  }

  .browse__line .browse__value {
    font-size: 11.5px;
  }
}

/* ---- Browse on a phone ------------------------------------------------------
   One block per kit, stacked 44px apart: a 220px frame, then the words. The
   highlights go two across, and a third box — CREW, on the seeded kits —
   spans the row rather than sitting alone at half width. */
@media (max-width: 720px) {
  /* **The same carousel the compare cards get.** The handoff's phone frame
     draws browse as a 350px track with arrows and dots beneath, and a browse
     block is the longest thing on the page — three of them stacked is a very
     long scroll to reach the third.

     A scroll-snap row again rather than a transform, for the reason the
     compare row gives: it swipes with no JavaScript and every kit stays in
     the document. The gap is the track's spacing between blocks, which is
     why `.browse`'s 44px stacking gap becomes the row's gap here. */
  .browse {
    flex-direction: row;
    gap: 40px;
    overflow-x: auto;
    scroll-snap-type: x mandatory;
    scrollbar-width: none;
  }

  .browse::-webkit-scrollbar {
    display: none;
  }

  .browse__kit {
    display: flex;
    flex-direction: column;
    flex: 0 0 100%;
    scroll-snap-align: start;
    gap: 18px;
    /* **The frame spans the column.**

       A flex item shrinks to its content unless told otherwise, so the
       picture frame collapsed to the photograph's own width — about 40% of
       the column — and `width: 100%` on the image measured that collapsed
       box rather than the column. It read as a picture that was too tall,
       which is the same fault seen from the other end. The block is a grid
       at every wider width, where `stretch` is already the default. */
    align-items: stretch;
  }

  /* **The same 150px frame the compare card uses.**

     The handoff draws browse's frame at 220px against compare's 150px, and
     both views are now the same carousel of the same kits — so the picture
     changing size between them reads as two different photographs rather
     than one seen twice. Matched to compare deliberately, against the
     handoff, on 07-09-2026. */
  .browse__frame,
  .browse__photo {
    height: 150px;
  }

  .browse__frame {
    padding: 16px;
  }

  .browse__tag {
    left: 18px;
    top: 16px;
  }

  .browse__letter {
    font-size: 44px;
  }

  .browse__name {
    margin-top: 0;
  }

  .browse__highlights {
    grid-template-columns: 1fr 1fr;
  }

  /* An odd last box spans both columns. `:last-child:nth-child(odd)` rather
     than naming the third, so a kit whose first group has five lines gets
     the same treatment as one with three. */
  .browse__highlight:last-child:nth-child(odd) {
    grid-column: 1 / -1;
  }

  .browse__highlight {
    padding: 14px 16px;
  }

  .browse__highlight .browse__value {
    margin-top: 9px;
    font-size: 13px;
  }

  .browse__line {
    padding: 11px 16px;
  }

  .browse__line .browse__value {
    font-size: 12px;
  }

  /* Full width on a phone, like the guide's result buttons: a pill floating
     at the left of a card somebody is swiping is a small target beside a
     large empty space. */
  .browse__kitlist {
    display: block;
    margin-top: 18px;
    padding: 14px 20px;
    text-align: center;
  }
}

/* ---- The full spec comparison -------------------------------------------
   A real table: tabular data with row and column headers. A grid of divs
   would give a screen reader a list of unrelated values. */

.spectable__label {
  margin: 0 0 24px;
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.2em;
  text-transform: uppercase;
  text-align: center;
  color: var(--paper-faint);
}

/* The table scrolls inside its own box rather than the page scrolling
   sideways — four columns do not fit a phone, and a horizontally scrolling
   page is a broken one. */
.spectable__scroll {
  overflow-x: auto;
  border: 1px solid rgba(242, 237, 230, 0.12);
  border-radius: 16px;
}

.spectable {
  width: 100%;
  border-collapse: collapse;
  /* So the columns keep the design's 1.4fr / 1fr / 1fr / 1fr rather than
     sizing themselves to the longest value in each. */
  table-layout: fixed;
  min-width: 640px;
}

.spectable th,
.spectable td {
  padding: 13px 24px;
  text-align: left;
  font-weight: 600;
  font-size: 12px;
  line-height: 1.3;
}

.spectable thead th {
  background: rgba(255, 255, 255, 0.03);
  font-weight: 700;
  font-size: 11px;
}

.spectable tbody th {
  width: 32%;
  color: var(--paper-soft);
}

.spectable tbody tr {
  border-top: 1px solid rgba(242, 237, 230, 0.08);
}

.spectable__group th {
  padding: 11px 24px;
  background: rgba(255, 216, 151, 0.07);
  font-weight: 700;
  font-size: 8.5px;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--gold);
}

.spectable__absent {
  color: rgba(242, 237, 230, 0.3);
}

/* ---- Choosing which kits the table compares -----------------------------
   Above three kits the columns are a selection, and the picker is made of
   links — see `comparison_mode` in app/services/gear.py. That is why nothing
   here is a `:hover`-only affordance or an `:active` state doing real work:
   every chip is an anchor, so the browser's own focus, hover and visited
   handling apply and the whole picker works with scripting off.

   Drawn only when the server drew it. At three kits or fewer there is no
   `.kitpick` in the document at all, so none of this costs a page anything. */

.kitpick {
  margin: 0 0 20px;
}

/* The count above the chips. Reads the selection, not the kit list — see the
   template, where it takes `gear_compared` rather than `gear_kits`. */
.kitpick__count {
  margin: 0 0 10px;
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

/* A real list, drawn as a row. The chips are a set of related choices, so
   `<ul>` is what a screen reader should meet — `list-style: none` with
   padding removed is how that is drawn without the bullets. */
.kitpick__chips {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 8px;
  margin: 0;
  padding: 0;
  list-style: none;
}

.kitpick__chip {
  display: inline-flex;
  align-items: center;
  gap: 8px;
  padding: 8px 14px;
  border: 1px solid rgba(242, 237, 230, 0.16);
  border-radius: 999px;
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  text-decoration: none;
  white-space: nowrap;
  color: rgba(242, 237, 230, 0.55);
  transition: border-color 0.15s ease, color 0.15s ease, background 0.15s ease;
}

/* The kit's letter, in the round badge the cards use. `aria-hidden` in the
   markup: the name is right beside it, and "S Small" is a stutter. */
.kitpick__letter {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 18px;
  height: 18px;
  border-radius: 50%;
  background: rgba(242, 237, 230, 0.08);
  font-size: 9px;
  line-height: 1;
}

/* A shown kit, from the server's own attribute rather than a class — so what
   the markup says and what the eye sees cannot drift apart, the same rule the
   view tabs follow with `aria-current` and the pair chips with `:checked`. */
.kitpick__chip[data-shown="true"] {
  border-color: var(--gold);
  background: rgba(255, 216, 151, 0.1);
  color: var(--gold);
}

.kitpick__chip[data-shown="true"] .kitpick__letter {
  background: rgba(255, 216, 151, 0.18);
}

.kitpick__chip:hover {
  border-color: rgba(242, 237, 230, 0.35);
  color: var(--paper-soft);
}

.kitpick__chip[data-shown="true"]:hover {
  border-color: var(--gold);
  color: var(--gold);
}

.kitpick__chip:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* The table is full and this kit is not in it. A `<span>`, not a link — so
   there is nothing to press and nothing to focus, and the hidden text says
   why. Dimmed rather than hidden: knowing the kit exists is the reason
   somebody would go and drop another one. */
.kitpick__chip--full {
  border-style: dashed;
  color: rgba(242, 237, 230, 0.3);
  cursor: default;
}

/* Everything past the three production kits.

   **A hidden checkbox, and the chip is its label.** The reference puts the
   toggle in the row as one more chip and opens the extra kits on a second
   line left-aligned with the first — which `<details>` cannot express,
   because its summary and its content are parent and child, so the opened
   list can only hang beneath the toggle wherever the row left it. The
   checkbox keeps what mattered: it opens with no JavaScript. */

/* Kept in the document and focusable, drawn nowhere.
   `.visually-hidden` in the markup does the hiding — it is the same eight
   declarations and duplicating them here was a second copy that a mutation
   caught immediately, by "landing" on the original instead. `display: none`
   would be wrong either way: it takes the checkbox out of the tab order, so
   somebody using a keyboard could not open the row at all. */
.kitpick__toggle {
  /* The row's own state, not the checkbox's, is what everything below reads
     — this rule exists so the selector has something to name. */
  margin: 0;
}

.kitpick__summary {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  padding: 8px 14px;
  border: 1px dashed rgba(242, 237, 230, 0.24);
  border-radius: 999px;
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  white-space: nowrap;
  color: rgba(242, 237, 230, 0.5);
  cursor: pointer;
}

/* The chevron. Points down when closed and up when open, which is the
   reference's own mark and the only thing saying the row can be opened. */
.kitpick__summary::after {
  content: "\203a";
  font-size: 13px;
  line-height: 1;
  transform: rotate(90deg);
  transition: transform 0.15s ease;
}

.kitpick:has(.kitpick__toggle:checked) .kitpick__summary::after {
  transform: rotate(-90deg);
}

.kitpick__summary:hover {
  border-color: rgba(242, 237, 230, 0.4);
  color: var(--paper-soft);
}

/* The focus ring goes on the *label*, because the input it belongs to is
   drawn nowhere — without this a keyboard reaches the toggle and nothing on
   screen says so. */
.kitpick__toggle:focus-visible + .kitpick__chips .kitpick__summary {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* The second line: left-aligned with the row above, not indented under the
   toggle. That is the whole reason this is a checkbox rather than a
   `<details>`.

   **Always in the document**, so a crawler reads every kit and the count
   above stays honest — hidden by height rather than by `display: none`,
   which is what lets it animate open. */
.kitpick__chips--more {
  margin-top: 0;
  max-height: 0;
  overflow: hidden;
  opacity: 0;
  transition: max-height 0.2s ease, opacity 0.15s ease, margin-top 0.2s ease;
}

.kitpick:has(.kitpick__toggle:checked) .kitpick__chips--more {
  margin-top: 8px;
  /* Generous rather than exact: a max-height that fits three rows of chips
     on the narrowest width, since the real height cannot be known here. */
  max-height: 20rem;
  opacity: 1;
}

/* Only one of the two wordings, chosen by width — the same shape the view
   tabs use, and `display: none` also keeps a screen reader from hearing
   "Other kits Other". */
.kitpick__summary-short {
  display: none;
}

/* ---- The table as a picker ----------------------------------------------
   The ✕ on each column and the Add slot where one was dropped. Rendered only
   in select mode: the macro draws them when it is given a path, so the
   guide's fallback table stays a table to read. */

/* The header holds the kit's name and the control that removes it.

   **The flex row is an inner element, never the `<th>` itself.** `display:
   flex` on a table cell takes it out of table layout — the browser stops
   treating it as a column and stacks all three headers into the first one.
   Caught in a screenshot rather than by a test, because a stylesheet test
   reads rules and cannot see a layout. */
.spectable thead th:has(.spectable__drop) {
  padding: 0;
}

.spectable__head {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 8px;
  /* The cell's own padding, moved in with the content it wraps. */
  padding: 13px 24px;
}

.spectable__drop {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  flex: none;
  width: 22px;
  height: 22px;
  border: 1px solid rgba(242, 237, 230, 0.16);
  border-radius: 50%;
  font-size: 13px;
  line-height: 1;
  text-decoration: none;
  color: rgba(242, 237, 230, 0.45);
  transition: border-color 0.15s ease, color 0.15s ease;
}

.spectable__drop:hover {
  border-color: var(--gold);
  color: var(--gold);
}

.spectable__drop:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* An empty column. Dashed, so it reads as a slot waiting to be filled rather
   than a column whose values failed to load. */
.spectable__add {
  color: rgba(242, 237, 230, 0.3);
}

.spectable thead th.spectable__add {
  background: rgba(255, 255, 255, 0.015);
}

.spectable__addlink {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  padding: 5px 10px;
  border: 1px dashed rgba(242, 237, 230, 0.24);
  border-radius: 999px;
  font-size: 10px;
  text-decoration: none;
  white-space: nowrap;
  color: rgba(242, 237, 230, 0.5);
  transition: border-color 0.15s ease, color 0.15s ease;
}

.spectable__addlink:hover {
  border-color: var(--gold);
  color: var(--gold);
}

.spectable__addlink:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* Nothing left to add — said rather than drawn as a control that would do
   nothing. */
.spectable__addnone {
  font-weight: 600;
  font-size: 10px;
  color: rgba(242, 237, 230, 0.22);
}

/* ---- Two kits at a time, on a phone -------------------------------------
   Four columns do not fit 390px, so the phone handoff compares a pair behind
   a row of chips — S × M, S × L, M × L. The chips are radios and the columns
   are hidden from here, one `:has(:checked)` rule per pair: no JavaScript,
   and a crawler still reads every column.

   Hidden above a phone's width, where the whole table fits. `display: none`
   on the fieldset also takes its radios out of the tab order, so a desktop
   keyboard never meets a control that changes nothing. */

.pairs {
  display: none;
}

/* The kit carousel's controls, likewise: KitCarousel.tsx renders nothing
   above a phone's width, and this is the second guard. */
.kitnav {
  display: none;
}

@media (max-width: 720px) {
  /* Closer to the table than to the label above it: the chips filter what
     follows, so the row should read as belonging to it. The reference draws
     the three as one block rather than three evenly spaced rows. */
  .pairs {
    display: flex;
    align-items: center;
    gap: 6px;
    margin: 12px 0 10px;
    padding: 0;
    border: none;
  }

  /* A <legend> sits outside a flex row unless it is floated; that is the
     one layout browsers agree to give it. */
  .pairs__legend {
    float: left;
    padding: 0;
    margin-right: 8px;
    font-weight: 700;
    font-size: 9px;
    letter-spacing: 0.1em;
    text-transform: uppercase;
    white-space: nowrap;
    color: rgba(242, 237, 230, 0.35);
  }

  /* The reference writes "Compare —" before the chips. A pseudo-element
     rather than the word, because the dash is punctuation joining the label
     to what follows — a screen reader reading "compare em dash" is worse
     than one reading "compare". */
  .pairs__legend::after {
    content: " —";
  }

  .pairs__chip {
    position: relative;
    padding: 9px 12px;
    border: 1px solid rgba(242, 237, 230, 0.18);
    border-radius: 8px;
    font-weight: 700;
    font-size: 9px;
    letter-spacing: 0.1em;
    text-transform: uppercase;
    white-space: nowrap;
    color: var(--paper-soft);
    cursor: pointer;
  }

  /* The radio is the control and the chip is its label. Kept in the
     document and focusable, drawn nowhere: `display: none` would take it
     out of the tab order and `appearance: none` alone still paints a box. */
  .pairs__radio {
    position: absolute;
    inset: 0;
    margin: 0;
    opacity: 0;
    cursor: pointer;
  }

  /* The chosen pair, styled from the radio's own state rather than a class,
     so what is announced and what is seen cannot drift — the same rule the
     view tabs follow with `aria-current`. */
  .pairs__chip:has(.pairs__radio:checked) {
    border-color: var(--gold);
    background: rgba(255, 216, 151, 0.1);
    color: var(--gold);
  }

  .pairs__chip:has(.pairs__radio:focus-visible) {
    outline: 2px solid var(--gold);
    outline-offset: 2px;
  }

  /* One rule per pair, written for three kits: the column outside the pair
     goes. `kit_pairs` in app/services/gear.py offers chips only for three,
     which is what keeps a fourth kit from meeting a chip that hides nothing. */
  .service__spectable:has(.pairs__radio[value="1-2"]:checked) .spectable__col-3,
  .service__spectable:has(.pairs__radio[value="1-3"]:checked) .spectable__col-2,
  .service__spectable:has(.pairs__radio[value="2-3"]:checked) .spectable__col-1 {
    display: none;
  }

  /* The table at a phone's width: no minimum, so a label and two kit
     columns fit without the scroll box.

     **`auto`, not `fixed`, and that is what closes the empty fourth
     column.** `table-layout: fixed` divides the width across *every*
     column, so the one hidden by the pair chips kept its share as a gap at
     the right-hand edge — the table drawn for four columns while showing
     two. With `auto` the width is shared among the columns that are
     actually drawn. The reason `fixed` exists at wider widths is to hold
     the design's 1.4fr / 1fr / 1fr / 1fr against a long value, and with two
     columns there is nothing to hold. */
  .spectable {
    min-width: 0;
    table-layout: auto;
  }

  .spectable tbody th {
    /* `auto` sizes to content, so the label column needs a share rather than
       a fixed width — 46% leaves the two value columns even. */
    width: 46%;
  }

  .spectable th,
  .spectable td {
    padding: 10px 12px;
    font-size: 11px;
  }

  .spectable thead th {
    padding: 12px;
    font-size: 10px;
    text-align: right;
  }

  .spectable td {
    text-align: right;
  }

  /* The group heading is a band across the table, so it keeps the row
     padding rather than the cells' — the reference draws it tight. */
  .spectable__group th {
    padding: 8px 12px;
    text-align: left;
  }

  .spectable__label {
    margin-bottom: 0;
    text-align: left;
  }

  /* The picker on a phone. The chips wrap to as many lines as they need
     rather than scrolling sideways: a row that scrolls hides the chip
     somebody is looking for, and there is nothing above it saying so. */
  .kitpick__chip,
  .kitpick__summary {
    padding: 7px 11px;
    font-size: 9px;
    letter-spacing: 0.08em;
  }

  .kitpick__letter {
    width: 16px;
    height: 16px;
    font-size: 8px;
  }

  /* The handoff abbreviates the button to "Other" at 390px. Two wordings,
     one summary — the same shape the view tabs use, and swapping which is
     `display: none` also changes what a screen reader hears. */
  .kitpick__summary-long {
    display: none;
  }

  .kitpick__summary-short {
    display: inline;
  }

  /* **The inner row wins back its alignment.** The phone block sets
     `text-align: right` on every `thead th`, which is right for a plain
     value column and wrong for one holding a name and a ✕ — `text-align`
     does nothing to flex children, so the ✕ would sit wherever
     `justify-content` left it and the name would look unaligned against the
     cells below. `space-between` is what the column wants at every width, so
     it is restated rather than left to the cascade. */
  .spectable__head {
    justify-content: space-between;
    padding: 12px;
    text-align: left;
  }

  .spectable__drop {
    width: 20px;
    height: 20px;
    font-size: 12px;
  }

  .spectable__addlink {
    padding: 4px 8px;
    font-size: 9px;
  }
}


/* The kit's photograph, in the frame the letter otherwise fills. Same box, so
   a card with a picture and one without stand the same height in the row. */
/* **A fixed frame, and the picture adapts to it.**

   This was `height: auto`, letting each photograph set the card's height —
   which made three cards stand at three heights and let an uploaded portrait
   shot change the design. The rule is the other way round: the frame's shape
   is the decision, and a picture too tall for it is cropped rather than
   allowed to break the row.

   **The same 190px as the lettered empty state, which is the design's own
   number.** A square `aspect-ratio` was tried and is the same fault one step
   along: a square frame *scales with its column*, so at the design's width it
   stands about 340px against the letter's 190px — one card 150px taller than
   the two beside it, which is exactly what a fixed frame exists to prevent.
   The reasoning that produced it — "a square loses least of a tall subject" —
   is true about cropping and says nothing about the row, and the row is what
   broke.

   Which part survives the crop is `object-position`, chosen per place and sent
   as an inline style — see app/services/framing.py. Centre is the default and
   renders no style at all. */
.kit__photo {
  display: block;
  width: 100%;
  height: 190px;
  margin-top: 20px;
  border-radius: 14px;
  object-fit: cover;
}

/* ---- The kit cards at a tablet's width -----------------------------------
   The responsive handoff (07-09-2026) keeps all three side by side at 834px
   with a 12px gap and every size stepped down one notch: name 22px, claim
   12.5px, keys 8px, chips 9px, a 130px frame. This used to stack them at
   anything under 900px, which put three long cards one under another on a
   screen wide enough for the row. */
@media (max-width: 900px) {
  .kits {
    gap: 12px;
  }

  .kit {
    padding: 20px 18px 22px;
    border-radius: 16px;
  }

  .kit__name {
    margin-top: 10px;
    font-size: 22px;
  }

  .kit__claim {
    margin-top: 5px;
    font-size: 12.5px;
  }

  .kit__suits {
    margin-top: 10px;
    font-size: 11px;
    line-height: 1.55;
  }

  .kit__letter,
  .kit__photo {
    height: 130px;
    margin-top: 16px;
    border-radius: 12px;
  }

  .kit__letter {
    padding: 14px;
    font-size: 34px;
  }

  .kit__rows {
    margin-top: 16px;
  }

  .kit__row {
    gap: 10px;
    padding: 9px 0;
  }

  .kit__key {
    font-size: 8px;
    letter-spacing: 0.12em;
  }

  .kit__value {
    font-size: 11px;
  }

  .kit__total-key {
    font-size: 8px;
    letter-spacing: 0.14em;
  }

  .kit__total-value {
    font-size: 11px;
  }

  .kit__chips {
    gap: 5px;
    margin-top: 14px;
  }

  .kit__chip {
    padding: 5px 9px;
    font-size: 9px;
    letter-spacing: 0.05em;
  }

  .kit__more {
    padding-top: 16px;
    font-size: 9.5px;
  }

  /* The table's cells at 16px rather than 24px, which is what lets four
     columns fit 834px without the scroll box having to do anything. */
  .spectable th,
  .spectable td {
    padding: 14px 16px;
    font-size: 11.5px;
  }

  .spectable thead th {
    font-size: 10.5px;
  }

  /* The header's padding lives on the inner row — see `.spectable__head` —
     so tightening the cells has to tighten it too, or the picker's columns
     would keep the desktop's 24px while every other cell moved to 16px.

     **Bounded below at 721px, because this block sits after the 720px one.**
     Both queries match on a phone and equal specificity is decided by order,
     so without the bound the tablet's 16px wins back over the phone's 12px.
     It costs nothing to lay out — `table-layout: auto` at that width sizes
     to content, so the columns simply redistribute — but a rule that applies
     where it was not meant to is how the next one does real damage. The trap
     this file has recorded before. */
  @media (min-width: 721px) {
    .spectable__head {
      padding: 14px 16px;
    }
  }

  .spectable__group th {
    padding: 10px 16px;
  }

  /* The picker at 834px: the same chips, tighter. The handoff's tablet is
     the desktop layout at closer metrics rather than a layout of its own. */
  .kitpick__chip,
  .kitpick__summary {
    padding: 7px 12px;
    font-size: 9.5px;
  }

  .service__kits {
    padding-top: 34px;
  }

  .service__spectable {
    padding-top: 48px;
    padding-bottom: 72px;
  }

  .service__kits--only {
    padding-bottom: 72px;
  }
}

/* ---- One card at a time on a phone --------------------------------------
   The phone handoff draws the three cards as a carousel: one in view, the
   neighbours fully off-screen, arrows and dots beneath.

   **A scroll-snap row, not a transform.** The prototype slides a track with
   `translateX`, which needs JavaScript for the first card to be reachable at
   all. A row that scrolls and snaps works with scripting off — a swipe is
   the native gesture — and every card stays in the document for a crawler.
   KitCarousel.tsx adds only what CSS cannot: the arrows, the dots and the
   counter. The 40px gap is the handoff's, and is what puts a neighbour fully
   off-screen rather than peeking. */
@media (max-width: 720px) {
  .kits {
    display: flex;
    gap: 40px;
    overflow-x: auto;
    scroll-snap-type: x mandatory;
    /* The bar under a row that has arrows and dots is a second control
       for the same thing. Hidden, not disabled: the row still scrolls. */
    scrollbar-width: none;
  }

  .kits::-webkit-scrollbar {
    display: none;
  }

  .kit {
    flex: 0 0 100%;
    scroll-snap-align: start;
  }

  /* **The controls stay beneath the cards, which is where the handoff puts
     them.**

     Moved above them for a day, on the reasoning that a kit card is about
     two screens tall so an arrow underneath is a long scroll away. The
     better argument is the opposite one: on a phone the bottom of the screen
     is where a thumb already is, and the cards swipe, so the arrows are the
     second way to move rather than the only one. Reverted 07-09-2026.

     Kept as a note because the first reasoning is not wrong, it is
     outweighed — and somebody reading only the scroll-distance argument
     would move them back. */

  /* The counter and hint at one end, the dots and arrows at the other —
     the mockup of 07-09-2026. `space-between` rather than two floats, so
     the row holds whatever the counter's text turns out to be. */
  .kitnav {
    display: flex;
    align-items: center;
    justify-content: space-between;
    gap: 16px;
    padding-top: 22px;
  }

  .kitnav__controls {
    display: inline-flex;
    align-items: center;
    gap: 10px;
  }

  .kitnav__arrow {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    width: 40px;
    height: 40px;
    padding: 0;
    border: 1px solid rgba(242, 237, 230, 0.3);
    border-radius: 50%;
    background: none;
    font: inherit;
    font-size: 15px;
    color: var(--paper);
    cursor: pointer;
  }

  .kitnav__arrow:hover {
    border-color: var(--gold);
    color: var(--gold);
  }

  /* The mockup draws the forward arrow in gold: it is the one somebody
     presses to keep going, and the way through three kits. Back is the
     quieter of the two rather than disabled — the arrows wrap. */
  .kitnav__arrow--next {
    border-color: var(--gold);
    color: var(--gold);
  }

  .kitnav__dots {
    display: inline-flex;
    align-items: center;
    gap: 7px;
    /* Between the counter and the arrows in the mockup, so it needs a little
       air before the first arrow rather than sitting against it. */
    margin-right: 4px;
  }

  /* 5px at 25% when idle, 7px gold when current — from the handoff. Sized
     inside a larger pressable box, because a 5px target is not one. */
  .kitnav__dot {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    width: 24px;
    height: 24px;
    padding: 0;
    border: none;
    background: none;
    cursor: pointer;
  }

  .kitnav__dot::before {
    content: "";
    width: 5px;
    height: 5px;
    border-radius: 50%;
    background: rgba(242, 237, 230, 0.25);
  }

  .kitnav__dot[aria-current="true"]::before {
    width: 7px;
    height: 7px;
    background: var(--gold);
  }

  .kitnav__counter {
    margin: 0;
    font-weight: 700;
    font-size: 9px;
    letter-spacing: 0.2em;
    text-transform: uppercase;
    color: var(--paper-faint);
  }

  /* **The swipe hint appears only where swiping is possible.**

     `(hover: none) and (pointer: coarse)` is a touch screen — a desktop
     window narrowed to a phone's width has a mouse, and telling somebody to
     swipe something they cannot is worse than saying nothing. Hidden by
     default and shown by the query, so anything that cannot answer it gets
     no hint rather than a wrong one. */
  .kitnav__hint {
    display: none;
  }

  /* The phone card is the desktop card again — 26px name, 150px frame — at
     the tablet's padding. */
  .kit {
    padding: 22px 20px 24px;
  }

  .kit__name {
    font-size: 26px;
  }

  .kit__claim {
    margin-top: 6px;
    font-size: 13px;
  }

  .kit__suits {
    font-size: 11.5px;
    line-height: 1.6;
  }

  .kit__letter,
  .kit__photo {
    height: 150px;
    margin-top: 18px;
  }

  .kit__letter {
    padding: 16px;
    font-size: 38px;
  }

  .kit__rows {
    margin-top: 18px;
  }

  .kit__row {
    gap: 14px;
    padding: 10px 0;
  }

  .kit__key {
    font-size: 8.5px;
    letter-spacing: 0.14em;
  }

  .kit__value {
    font-size: 12px;
  }

  .service__kits {
    padding-top: 28px;
  }

  /* The reference runs the label, the chips and the table together as one
     block, tighter than the desktop's 36/64.

     **One rule, because there were two.** A second phone block further up
     also set `padding-top` here, and being later in the file it won — so a
     value written for the reference never applied and nothing said so. */
  .service__spectable {
    padding-top: 30px;
    padding-bottom: 64px;
  }

  .service__kits--only {
    padding-bottom: 64px;
  }
}

/* **The swipe hint appears only where swiping is possible.**

   `(hover: none) and (pointer: coarse)` is a touch screen. A desktop window
   narrowed to a phone's width has a mouse, and telling somebody to swipe
   something they cannot is worse than saying nothing — so the hint is hidden
   by default and shown only by this query, which means anything that cannot
   answer it gets no hint rather than a wrong one.

   A separate top-level query rather than one nested inside the phone block:
   nesting is valid CSS and current browsers handle it, but nothing else in
   this file nests, and a flat rule needs no such claim. The controls are
   already phone-only, so this cannot show a hint anywhere they are hidden.

   **After the phone block, never before it.** The hint's `display: none`
   lives in that block, and two rules of equal specificity are decided by
   order — so this one placed above it loses on the one kind of device it
   exists for. Written the wrong way round first, and caught by its own
   test. */
@media (hover: none) and (pointer: coarse) {
  .kitnav__hint {
    display: inline;
  }
}


/* ---- Seeing a photograph whole ------------------------------------------
   The frame crops — see app/services/framing.py — so a card shows about 300
   pixels of a file that is 1600 wide. Pressing one opens it at the size it
   actually is.

   The overlay is drawn by the island, so none of this applies until the
   bundle runs: with no JavaScript there is no viewer and the pictures are
   already whole in the document. */

.viewer {
  position: fixed;
  inset: 0;
  z-index: 100;
  display: flex;
  align-items: center;
  justify-content: center;
  padding: clamp(16px, 5vw, 64px);
  /* Nearly opaque rather than a light scrim: the point is to see the
     photograph, and a page showing through competes with it. */
  background: rgba(11, 10, 9, 0.94);
}

.viewer__image {
  display: block;
  max-width: 100%;
  max-height: 100%;
  /* `contain` here, and it is the opposite of the frame's `cover` on purpose:
     this is the one place nothing should be cropped. */
  object-fit: contain;
  border-radius: 4px;
  /* Pressing it closes the viewer, so say so. The opener says zoom-in. */
  cursor: zoom-out;
}

.viewer__close {
  position: absolute;
  top: clamp(12px, 3vw, 28px);
  right: clamp(12px, 3vw, 28px);
  display: flex;
  align-items: center;
  justify-content: center;
  /* 44px, the smallest thing a finger reliably hits. */
  width: 44px;
  height: 44px;
  padding: 0;
  border: 1px solid rgba(242, 237, 230, 0.22);
  border-radius: 50%;
  background: rgba(11, 10, 9, 0.7);
  color: var(--paper);
  font-size: 22px;
  line-height: 1;
  cursor: pointer;
}

.viewer__close:hover {
  border-color: var(--gold);
  color: var(--gold);
}

.viewer__close:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* ---------------------------------------------------------------------------
   About — the session spine.

   From the about page handoff of 13-09-2026, design id 1c. The page is one
   recorded take: a hero with a waveform, four numbered markers down a rail,
   and a closing band.

   **Every colour the handoff names was already a token.** Its ink, surface,
   bone, gold, rust and gradient stops are this palette — the same finding
   Sound Design's band recorded. What is new is `--font-mono`, for the
   timecodes and spec keys.

   **The measure is the site's, not the design's 1440 frame.** `--gutter`
   gives the sides and `min(1100px, 100%)` the column, the shape every other
   band uses. A page inventing its own width is the fault §9 names.
--------------------------------------------------------------------------- */

.about {
  /* The band carries its own gap. A band relying on its neighbour for
     spacing is correct on one page by accident — the Sound Recording
     lesson. */
  padding-top: 44px;
  padding-bottom: 56px;
}

.about__inner {
  width: min(1100px, 100%);
  margin-inline: auto;
}

/* The hero ------------------------------------------------------------- */

.about__eyebrow {
  margin: 0;
  font-family: var(--font-mono);
  font-size: 10px;
  font-weight: 600;
  line-height: 1.5;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: rgba(255, 216, 151, 0.9);
}

.about__heading {
  /* 76px at the design's width, and it must not overflow a phone. The
     handoff's own recommendation. */
  margin: 20px 0 0;
  max-width: 900px;
  font-size: clamp(38px, 6vw, 76px);
  font-weight: 800;
  line-height: 1;
  letter-spacing: -0.035em;
  color: #fff;
  text-wrap: pretty;
}

/* The waveform. Bars are drawn by the server — see `wave_bars` — and their
   heights arrive as inline styles, because each one is a different value.
   Static: no animation, so nothing here answers `prefers-reduced-motion`. */
.about__wave {
  display: flex;
  align-items: center;
  gap: 2px;
  height: 74px;
  margin-top: 30px;
}

.about__bar {
  flex: 1;
  border-radius: 2px;
  background: rgba(255, 255, 255, 0.22);
}

.about__bar--played {
  background: var(--gold);
}

/* The bar heights, one class each.
 *
 * **Not an inline style, and the CSP is the reason.** `style-src 'self'`
 * carries no `'unsafe-inline'` — deliberately, see app/middleware.py — so a
 * browser refuses every `style` attribute on this site. The first version of
 * this waveform set each bar's height that way and drew 120 bars of nothing:
 * correct markup, correct stylesheet, and a 74px gap on the page. No test
 * could see it, because the attribute really was in the HTML.
 *
 * Generated from `wave_heights()` in app/services/about.py, which reads the
 * same formula the bars do — and `test_every_bar_height_has_a_rule` fails if
 * the two ever part company.
 */
.about__bar--h3 { height: 3px; }
.about__bar--h4 { height: 4px; }
.about__bar--h5 { height: 5px; }
.about__bar--h6 { height: 6px; }
.about__bar--h7 { height: 7px; }
.about__bar--h8 { height: 8px; }
.about__bar--h9 { height: 9px; }
.about__bar--h10 { height: 10px; }
.about__bar--h11 { height: 11px; }
.about__bar--h12 { height: 12px; }
.about__bar--h13 { height: 13px; }
.about__bar--h14 { height: 14px; }
.about__bar--h15 { height: 15px; }
.about__bar--h17 { height: 17px; }
.about__bar--h18 { height: 18px; }
.about__bar--h20 { height: 20px; }
.about__bar--h21 { height: 21px; }
.about__bar--h22 { height: 22px; }
.about__bar--h23 { height: 23px; }
.about__bar--h24 { height: 24px; }
.about__bar--h25 { height: 25px; }
.about__bar--h26 { height: 26px; }
.about__bar--h27 { height: 27px; }
.about__bar--h28 { height: 28px; }
.about__bar--h29 { height: 29px; }
.about__bar--h30 { height: 30px; }
.about__bar--h31 { height: 31px; }
.about__bar--h32 { height: 32px; }
.about__bar--h33 { height: 33px; }
.about__bar--h35 { height: 35px; }
.about__bar--h36 { height: 36px; }
.about__bar--h37 { height: 37px; }
.about__bar--h38 { height: 38px; }
.about__bar--h39 { height: 39px; }
.about__bar--h40 { height: 40px; }
.about__bar--h41 { height: 41px; }
.about__bar--h44 { height: 44px; }
.about__bar--h45 { height: 45px; }
.about__bar--h46 { height: 46px; }
.about__bar--h47 { height: 47px; }
.about__bar--h49 { height: 49px; }
.about__bar--h50 { height: 50px; }
.about__bar--h51 { height: 51px; }
.about__bar--h53 { height: 53px; }
.about__bar--h54 { height: 54px; }
.about__bar--h55 { height: 55px; }
.about__bar--h57 { height: 57px; }
.about__bar--h59 { height: 59px; }
.about__bar--h60 { height: 60px; }
.about__bar--h61 { height: 61px; }
.about__bar--h62 { height: 62px; }
.about__bar--h63 { height: 63px; }
.about__bar--h64 { height: 64px; }
.about__bar--h66 { height: 66px; }
.about__bar--h67 { height: 67px; }
.about__bar--h69 { height: 69px; }
.about__bar--h70 { height: 70px; }
.about__bar--h71 { height: 71px; }
.about__bar--h73 { height: 73px; }

.about__strip {
  display: flex;
  justify-content: space-between;
  gap: 12px;
  margin: 10px 0 0;
  font-family: var(--font-mono);
  font-size: 9.5px;
  font-weight: 600;
  line-height: 1;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: rgba(255, 255, 255, 0.4);
}

/* The markers ---------------------------------------------------------- */

.about__marker {
  display: flex;
  align-items: flex-start;
  gap: 44px;
  padding-top: 52px;
}

.about__rail {
  flex: none;
  width: 132px;
  padding-top: 6px;
}

.about__number {
  margin: 0;
  font-size: 40px;
  font-weight: 800;
  line-height: 1;
  color: var(--gold);
}

.about__railline {
  margin: 10px 0 0;
  font-family: var(--font-mono);
  font-size: 9.5px;
  font-weight: 600;
  line-height: 1.6;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: rgba(255, 255, 255, 0.42);
}

.about__railline + .about__railline {
  margin-top: 0;
}

.about__column {
  flex: 1;
  min-width: 0;
  padding-left: 44px;
  border-left: 1px solid rgba(242, 237, 230, 0.14);
}

.about__title {
  margin: 0;
  max-width: 700px;
  font-size: clamp(24px, 3vw, 32px);
  font-weight: 800;
  line-height: 1.15;
  letter-spacing: -0.02em;
  color: #fff;
  text-wrap: pretty;
}

.about__body {
  max-width: 760px;
  font-size: 16px;
  line-height: 1.8;
  color: rgba(242, 237, 230, 0.86);
  text-wrap: pretty;
}

.about__body p {
  margin: 18px 0 0;
}

.about__closing {
  max-width: 760px;
  font-size: 15px;
  line-height: 1.8;
  color: rgba(242, 237, 230, 0.7);
}

.about__closing p {
  margin: 22px 0 0;
}

/* Cards ---------------------------------------------------------------- */

.about__pair {
  display: flex;
  align-items: stretch;
  gap: 20px;
  margin-top: 26px;
  max-width: 820px;
}

.about__portrait {
  position: relative;
  flex: none;
  width: 300px;
  height: 200px;
  /* The handoff's gradient. It sits *behind* the portrait, and the portrait
     is not yet supplied — so what renders is this, which is the design's own
     empty state rather than a broken image. */
  background: linear-gradient(150deg, #241812, #4a2013 50%, #8c3c1f);
}

/* The portrait itself, once an editor has chosen one.
   `cover`, because the frame is fixed and the picture adapts — the Module 18
   rule. Which part survives the crop is the `focus-x`/`focus-y` classes. */
.about__portraitimage {
  width: 100%;
  height: 100%;
  object-fit: cover;
  display: block;
}

/* The signature and its caption. A column, so the caption sits under the
   picture when there is one and stands alone when there is not. */
/* The picture and its caption, side by side.
 *
 * **A row, not a column, and the picture sets the height.** The handoff draws
 * a 300x90 box for a white-on-transparent signature graphic; what the studio
 * actually put there is a *photograph of the founder*, which that box turns
 * into a stamp. It fills the band's inner frame now and the caption sits
 * beside it — the picture is the point, and a portrait is read at portrait
 * size.
 */
.about__signatureblock {
  flex: none;
  display: flex;
  align-items: center;
  gap: 40px;
}

/* **A frame, like every other framed picture on the site.**
 *
 * This holds either a photograph of the founder or a signature graphic —
 * whichever the studio puts there — so it is a fixed box the picture fills
 * and the admin aims, rather than a shape that changes with the file. It was
 * `contain` with `width: auto` until 13-09-2026, on the reasoning that
 * cropping a signature cuts the name in half; true of a signature, and it
 * made the framing and zoom controls do nothing at all for the photograph
 * that is actually in there.
 *
 * **A fixed height, not `100%` of the row.** Stretching to the row made the
 * picture push the row taller in turn, which grew the band past the hairline
 * frame it sits inside — the picture set the height and then chased it. 220
 * is what fills it: the band's inner hairline is 217px, inset 16px, and the
 * row's own 46px padding is what stands between them.
 */
.about__signatureframe {
  flex: none;
  width: 200px;
  height: 220px;
  /* The zoom's own rule clips a frame holding a scaled picture; this one
     clips whatever it holds, because `cover` overflows at any zoom. */
  overflow: hidden;
}

.about__signatureimage {
  display: block;
  width: 100%;
  height: 100%;
  /* `cover`, so the picture fills its frame and the choice of *which part*
     is the admin's — the Module 18 rule, which this slot was outside of. */
  object-fit: cover;
}

/* The inset hairline, on the portrait and the closing band. An absolutely
   positioned overlay rather than the element's own border, because the
   design insets it from the edge. */
.about__frame {
  position: absolute;
  inset: 12px;
  border: 1px solid rgba(242, 237, 230, 0.3);
  pointer-events: none;
}

.about__card {
  flex: 1;
  padding: 22px 24px;
  background: #14120f;
  border: 1px solid rgba(242, 237, 230, 0.14);
}

.about__card--gold {
  background: rgba(255, 216, 151, 0.1);
  border-color: rgba(255, 216, 151, 0.35);
}

.about__pair--even .about__card {
  background: rgba(255, 255, 255, 0.04);
  border-color: rgba(242, 237, 230, 0.12);
}

.about__pair--even .about__card--gold {
  background: rgba(255, 216, 151, 0.1);
  border-color: rgba(255, 216, 151, 0.35);
}

.about__cardlabel {
  margin: 0;
  font-family: var(--font-mono);
  font-size: 9.5px;
  font-weight: 600;
  line-height: 1;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: rgba(255, 216, 151, 0.9);
}

/* The two cards under the comparison use Raleway for their labels, not the
   mono face — the handoff specifies both, and they sit at different sizes. */
.about__cardlabel--plain {
  font-family: var(--font);
  font-weight: 700;
  letter-spacing: 0.18em;
  color: var(--gold);
}

.about__names {
  margin: 14px 0 0;
  font-size: 22px;
  font-weight: 700;
  line-height: 1.4;
  color: #fff;
}

.about__note {
  margin: 12px 0 0;
  font-size: 13.5px;
  line-height: 1.7;
  color: rgba(242, 237, 230, 0.65);
}

.about__cardbody {
  font-size: 14.5px;
  line-height: 1.75;
  color: rgba(242, 237, 230, 0.84);
}

.about__cardbody p {
  margin: 12px 0 0;
}

.about__card--gold .about__cardbody {
  color: #fff;
}

/* The comparison ------------------------------------------------------- */

.about__toggleblock {
  margin-top: 22px;
}

.about__toggle {
  display: flex;
  gap: 2px;
  width: fit-content;
  padding: 4px;
  border-radius: var(--radius-pill);
  background: rgba(255, 255, 255, 0.05);
  border: 1px solid rgba(255, 255, 255, 0.1);
}

.about__segment {
  padding: 9px 20px;
  border: 0;
  border-radius: var(--radius-pill);
  background: transparent;
  color: rgba(255, 255, 255, 0.7);
  font-family: var(--font);
  font-size: 10.5px;
  font-weight: 700;
  line-height: 1;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  white-space: nowrap;
  cursor: pointer;
  transition: background var(--quick), color var(--quick);
}

.about__segment--on {
  background: var(--gold);
  /* `--ink` is #1b1815, which is what the handoff calls `gold-on`. */
  color: var(--ink);
}

/* The handoff's own suggestion, and the ring a keyboard needs: the segments
   are pills on a pill, so an outline would be drawn square around one. */
.about__segment:focus-visible {
  outline: none;
  box-shadow: 0 0 0 3px rgba(255, 216, 151, 0.35);
}

/* The fallback renders every side as its own card; the island renders one.
   Both use this, which is what keeps them looking the same. */
.about__compare {
  display: flex;
  flex-direction: column;
  gap: 20px;
  margin-top: 20px;
}

.about__comparecard {
  margin-top: 20px;
  padding: 30px 34px;
  max-width: 820px;
  background: #14120f;
  border: 1px solid rgba(242, 237, 230, 0.14);
}

/* Inside the fallback's stack the cards carry their own gap, so the
   per-card margin would double it. */
.about__compare .about__comparecard {
  margin-top: 0;
}

.about__comparehead {
  margin: 14px 0 0;
  font-size: 24px;
  font-weight: 700;
  line-height: 1.45;
  color: #fff;
}

.about__comparetext {
  margin: 14px 0 0;
  font-size: 14.5px;
  line-height: 1.75;
  color: rgba(242, 237, 230, 0.7);
}

/* The pricing grid ----------------------------------------------------- */

/* **The 1px gap is the hairline.** The grid's background shows through
   between cells, which is why there is no border on the cells themselves —
   the handoff's own construction. */
.about__specs {
  display: grid;
  grid-template-columns: repeat(2, 1fr);
  gap: 1px;
  margin: 26px 0 0;
  max-width: 820px;
  background: rgba(242, 237, 230, 0.12);
  border: 1px solid rgba(242, 237, 230, 0.12);
}

.about__cell {
  padding: 18px 22px;
  background: #14120f;
}

.about__speckey {
  font-family: var(--font-mono);
  font-size: 9px;
  font-weight: 600;
  line-height: 1;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: rgba(255, 255, 255, 0.45);
}

.about__specvalue {
  margin: 9px 0 0;
  font-size: 15px;
  font-weight: 700;
  line-height: 1.5;
  color: #fff;
}

/* The closing band ----------------------------------------------------- */

.about__cta {
  position: relative;
  margin-top: 56px;
  background:
    radial-gradient(120% 160% at 82% 0%, rgba(255, 216, 151, 0.2), transparent 46%),
    linear-gradient(150deg, #241812 0%, #4a2013 44%, #8c3c1f 100%);
}

.about__cta .about__frame {
  inset: 16px;
  border-color: rgba(242, 237, 230, 0.28);
}

.about__ctarow {
  position: relative;
  display: flex;
  align-items: center;
  gap: 48px;
  padding: 46px 56px;
}

.about__ctawords {
  flex: 1;
  min-width: 0;
}

.about__ctahead {
  margin: 0;
  max-width: 620px;
  font-size: clamp(26px, 4vw, 40px);
  font-weight: 800;
  line-height: 1.15;
  letter-spacing: -0.02em;
  color: #fff;
  text-wrap: pretty;
}

.about__ctabutton {
  display: inline-block;
  margin-top: 26px;
  padding: 14px 26px;
  border-radius: var(--radius-pill);
  background: var(--gold);
  color: var(--ink);
  font-size: 11px;
  font-weight: 700;
  line-height: 1;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  text-decoration: none;
}

/* The name, then the role beneath it.
 *
 * **Two lines by construction, not by wrapping.** This was one string with a
 * `max-width`, so the browser broke it wherever it happened to fit —
 * "DICKENSON / EEKMAN — / FOUNDER", the dash dangling and the three lines
 * reading as one cramped block. The server splits the caption on its own
 * dash now, and the two parts are spaced deliberately.
 *
 * A column rather than a line height, because the gap between a name and a
 * role is a different decision from the leading *inside* the name — which
 * stays tight, since "Dickenson Eekman" is one thing.
 */
.about__signature {
  margin: 0;
  display: flex;
  flex-direction: column;
  gap: 15px;
  font-family: var(--font-mono);
  font-size: 9.5px;
  font-weight: 600;
  line-height: 1;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: rgba(255, 255, 255, 0.6);
}

/* Each part wraps within itself at its own tight leading — "Dickenson
   Eekman" over two lines is still one thing, and the 15px above separates
   the name from the role rather than every line from the next. */
.about__signaturename,
.about__signaturerole {
  display: block;
  line-height: 1.5;
}

/* Below the site's breakpoint the rail sits above its column, as the
   handoff recommends: 132px of rail beside a narrow column is most of a
   phone's width spent on a number. */
@media (max-width: 900px) {
  .about__marker {
    flex-direction: column;
    gap: 0;
  }

  .about__rail {
    display: flex;
    align-items: baseline;
    gap: 12px;
    width: auto;
    padding-top: 0;
  }

  .about__railline {
    margin-top: 0;
  }

  .about__column {
    padding-left: 0;
    padding-top: 18px;
    border-left: 0;
  }

  .about__pair {
    flex-direction: column;
  }

  .about__portrait {
    width: 100%;
  }

  .about__ctarow {
    flex-direction: column;
    align-items: flex-start;
    gap: 26px;
    padding: 34px 30px;
  }

  /* The picture is shorter where the band is stacked and narrow.
     
     220px beside a headline that has become two or three lines is most of a
     phone's screen spent on one photograph — and the block is no longer
     width-constrained, so the rule that used to live here (`width: auto` on
     a 300px wrapper) had stopped doing anything at all. */
  .about__signatureimage {
    height: 160px;
  }
}

@media (max-width: 720px) {
  .about__specs {
    grid-template-columns: 1fr;
  }

  /* Five items across 390px is four characters each. The strip keeps the
     take's start and its markers move to the rails, where they already
     render. */
  .about__strip {
    display: none;
  }

  /* The comparison's two choices, one above the other — 13f-5d. Side by
     side and unwrapped, the Dutch labels made About 657px wide on a 390px
     phone. Stacked, each takes the column's width, its words may wrap, and
     it is tall enough to press. The corners follow one choice's height
     rather than the pill's, which would round a two-row box into a capsule. */
  .about__toggle {
    flex-direction: column;
    width: 100%;
    border-radius: 22px;
  }

  .about__segment {
    min-height: 44px;
    white-space: normal;
    line-height: 1.3;
  }
}

/* Where a framed photograph sits inside its frame.
 *
 * **Classes, not an inline style, and the CSP is why.** `style-src 'self'`
 * carries no `'unsafe-inline'` — see app/middleware.py — so a browser refuses
 * every `style` attribute on this site. The server-rendered framing had been
 * emitting one per picture since Module 18 and every one was discarded: the
 * attribute was in the HTML and the tests asserted it was, while no photograph
 * was ever cropped where it was told to be. Found 13-09-2026, from the About
 * page's waveform having the same fault.
 *
 * **The carousel was never affected**, and that is worth knowing before
 * anybody 'fixes' it there too: its island sets React's `objectPosition`,
 * which is a DOM property assignment rather than an attribute, and CSP does
 * not govern those.
 *
 * Two custom properties rather than 441 combined classes. Generated from
 * `focus_steps()` in app/services/framing.py, with a test asserting every
 * step has a rule.
 */
[class*="focus-x"] {
  object-position: var(--focus-x, 50%) var(--focus-y, 50%);
}

.focus-x0 { --focus-x: 0%; }
.focus-x5 { --focus-x: 5%; }
.focus-x10 { --focus-x: 10%; }
.focus-x15 { --focus-x: 15%; }
.focus-x20 { --focus-x: 20%; }
.focus-x25 { --focus-x: 25%; }
.focus-x30 { --focus-x: 30%; }
.focus-x35 { --focus-x: 35%; }
.focus-x40 { --focus-x: 40%; }
.focus-x45 { --focus-x: 45%; }
.focus-x50 { --focus-x: 50%; }
.focus-x55 { --focus-x: 55%; }
.focus-x60 { --focus-x: 60%; }
.focus-x65 { --focus-x: 65%; }
.focus-x70 { --focus-x: 70%; }
.focus-x75 { --focus-x: 75%; }
.focus-x80 { --focus-x: 80%; }
.focus-x85 { --focus-x: 85%; }
.focus-x90 { --focus-x: 90%; }
.focus-x95 { --focus-x: 95%; }
.focus-x100 { --focus-x: 100%; }

.focus-y0 { --focus-y: 0%; }
.focus-y5 { --focus-y: 5%; }
.focus-y10 { --focus-y: 10%; }
.focus-y15 { --focus-y: 15%; }
.focus-y20 { --focus-y: 20%; }
.focus-y25 { --focus-y: 25%; }
.focus-y30 { --focus-y: 30%; }
.focus-y35 { --focus-y: 35%; }
.focus-y40 { --focus-y: 40%; }
.focus-y45 { --focus-y: 45%; }
.focus-y50 { --focus-y: 50%; }
.focus-y55 { --focus-y: 55%; }
.focus-y60 { --focus-y: 60%; }
.focus-y65 { --focus-y: 65%; }
.focus-y70 { --focus-y: 70%; }
.focus-y75 { --focus-y: 75%; }
.focus-y80 { --focus-y: 80%; }
.focus-y85 { --focus-y: 85%; }
.focus-y90 { --focus-y: 90%; }
.focus-y95 { --focus-y: 95%; }
.focus-y100 { --focus-y: 100%; }

/* How far into a picture its frame is cropped.
 *
 * **A scale on the image, aimed by `object-position`.** The picture already
 * fills its frame with `cover`; this magnifies it further, and the focal
 * point decides which part stays in view — so zoom and position compose
 * rather than fighting.
 *
 * `transform-origin` follows the focal point through a custom property, or
 * zooming would always pull towards the centre and undo the aim. The
 * fallback is 50% 50%, which is where an unframed picture already sits.
 *
 * Classes rather than an inline style, because `style-src 'self'` carries
 * no `'unsafe-inline'` — see app/middleware.py. Generated from
 * `zoom_steps()`, with a test asserting every step has a rule.
 */
[class*="zoom-"] {
  transform-origin: var(--focus-x, 50%) var(--focus-y, 50%);
}

/* **The frame has to clip, or the picture spills out of it.**
 *
 * A scaled image is larger than its box, and two of the four frames that
 * carry framing did not hide their overflow — the page photographs and the
 * carousel did, the gear card and About's portrait did not. Rather than
 * patch four selectors, the clip travels with the zoom: a frame holding a
 * zoomed picture clips, and one holding an ordinary picture is untouched.
 *
 * `:has()` rather than a class on the frame, because the frame is rendered
 * by four different templates and the zoom is a property of the picture. */
:has(> [class*="zoom-"]) {
  overflow: hidden;
}

.zoom-110 { transform: scale(1.1); }
.zoom-120 { transform: scale(1.2); }
.zoom-130 { transform: scale(1.3); }
.zoom-140 { transform: scale(1.4); }
.zoom-150 { transform: scale(1.5); }
.zoom-160 { transform: scale(1.6); }
.zoom-170 { transform: scale(1.7); }
.zoom-180 { transform: scale(1.8); }
.zoom-190 { transform: scale(1.9); }
.zoom-200 { transform: scale(2.0); }

/* ---- The Projects page ---------------------------------------------------
 *
 * From `design_handoff_projects_page` (23-09-2026): a numbered index, then a
 * block per production, alternating sides down the page. Two breakpoints as
 * everywhere: the desk at 1440 and the phone at 390, split at the site's
 * 900px.
 *
 * **Every number below is the handoff's**, which states its colours, type and
 * spacing are final. The page's ground is the design's pure black rather than
 * the site's near-black, on purpose: the handoff names `#000` and the posters
 * are what the page is, so the ground gets out of their way. */
.projects {
  background: #000;
  color: var(--paper);
}

/* The index: a column of numbered titles, the number sitting like a
   superscript beside a 44px title. */
.projects__index {
  padding: 64px var(--gutter) 0 150px;
}

.projects__list {
  display: flex;
  flex-direction: column;
  gap: 6px;
  margin: 0;
  padding: 0;
  list-style: none;
}

.projects__entry {
  display: flex;
  align-items: flex-start;
  gap: 10px;
  color: #fff;
  text-decoration: none;
  transition: color var(--quick);
}

.projects__entry:hover,
.projects__entry:focus-visible {
  color: var(--gold);
}

.projects__no,
.projects__count {
  font-family: var(--font-mono);
  font-weight: 600;
  font-size: 10px;
  line-height: 1;
  color: rgba(255, 255, 255, 0.6);
}

.projects__no {
  width: 18px;
  flex: none;
  padding-top: 6px;
}

.projects__entry-title {
  font-weight: 800;
  font-size: 44px;
  line-height: 1.1;
  letter-spacing: -0.025em;
}

/* The blocks. */
.projects__blocks {
  display: flex;
  flex-direction: column;
  gap: 110px;
  padding: 90px var(--gutter) 0;
}

.projects__block {
  display: flex;
  align-items: flex-start;
  gap: 64px;
  scroll-margin-top: 24px;
}

/* Even blocks change sides and step in from both edges — the alternation
   that keeps six blocks from reading as one long table.

   **The inset is what the width can spare, not a fixed 120px — 24-09-2026.**
   At the design's 1440 it is the full 120 and nothing has moved; it reaches
   zero exactly where the two columns are at their drawn sizes and the row has
   nothing left to give. A flat 120 took 240px out of a window that was already
   short of them, which made a tiled browser worse than a narrow one for no
   reason a reader could see. */
.projects__block--even {
  flex-direction: row-reverse;
  padding: 0 clamp(0px, (100vw - 1072px) / 2, 120px);
}

/* The poster, the trailer under it, and the number beside them. A grid
   rather than a flex row, because the button belongs under the picture and
   not under the number: the picture and the button share the first column,
   the number is the second and spans neither. */
.projects__poster-column {
  display: grid;
  grid-template-columns: 1fr auto;
  align-items: start;
  column-gap: 12px;
  /* **440 where there is room, and less where there is not — 24-09-2026.**
     It was `width: 440px; flex: none`, and the facts column beside it was
     480 the same way: 440 + 64 + 480 + two 44px gutters is 1072px, which the
     page then was at *every* width. A window tiled to half a laptop — 901 to
     1071 — scrolled sideways and cut the left edge off every block, reported
     by the owner from exactly that. Below 900 the stacked layout takes over
     and was never affected, which is why this band had nobody looking at it.

     `flex-shrink: 1` with `min-width: 0` rather than a percentage: the two
     columns then give up width *in proportion* to what they were drawn at,
     so the poster stays the larger of the two all the way down. A grid child
     will not shrink below its content without the `min-width` — the default
     `auto` is what makes a flex item refuse. */
  flex: 0 1 440px;
  min-width: 0;
}

.projects__poster-area {
  grid-column: 1;
  min-width: 0;
}

/* The box the frame lives in. On a desk it is the column's first cell; on
   a phone it is what flexes, and the frame reads its height. */

/* The poster's frame is fixed at 2:3 and the picture adapts — Module 18's
   rule. A production without a poster keeps the frame, in the page's ground,
   so the trailer button has somewhere to sit and the blocks line up. */
.projects__frame {
  position: relative;
  width: 100%;
  aspect-ratio: 2 / 3;
  background: var(--dark-raised);
  overflow: hidden;
}

/* **Out of the flow, so the picture never sizes its frame.** On a phone the
   frame takes its width from its height through the 2:3 ratio, and an
   in-flow image with an intrinsic width of its own was winning that
   argument — measured as a 234×432 frame on the second probe, the `sizes`
   attribute's 60vw exactly. Absolute, the frame is sized by the ratio alone
   and the picture fills whatever that is. */
.projects__poster {
  position: absolute;
  inset: 0;
  display: block;
  width: 100%;
  height: 100%;
  object-fit: cover;
}

/* **Below the poster, not over it** — the owner's word, 23-09-2026. The
   handoff floats it in the frame's bottom-left corner; a poster is the one
   picture a production chose for itself, and a pill across it covers
   whatever is there. `align-self: start` so the pill is its own width
   rather than the column's. */
.projects__trailer {
  grid-column: 1;
  justify-self: start;
  margin-top: 12px;
  display: inline-flex;
  align-items: center;
  gap: 10px;
  padding: 13px 20px;
  border-radius: var(--radius-pill);
  background: var(--gold);
  color: var(--ink);
  font-weight: 700;
  font-size: 10.5px;
  line-height: 1;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  text-decoration: none;
  transition: filter var(--quick);
}

.projects__trailer:hover {
  filter: brightness(1.08);
}

/* The counter, and on a phone the snap toggle beside it. On a desk this is
   the column's second cell and holds the number alone — the island draws
   nothing above 900px. */
.projects__top {
  grid-column: 2;
  grid-row: 1;
}

.projects__count {
  margin: 0;
  color: rgba(255, 255, 255, 0.7);
}

/* The switch: a pill with the words and a track, the handoff's own sizes.
   Drawn only where it can do something, which is to say on a phone. */
.projects__snap {
  display: none;
}

/* On a desk the number stands alone beside the poster; the "/ 06" belongs
   to the phone's top row. */
.projects__count-of {
  display: none;
}

.projects__facts {
  /* The poster column's pair — see the reasoning there. 480 where there is
     room, shrinking in proportion where there is not, and `min-width: 0` so
     the title and the fact rows may wrap rather than holding the row open. */
  flex: 0 1 480px;
  min-width: 0;
  padding-top: 10px;
}

.projects__function {
  margin: 0;
  font-family: var(--font-mono);
  font-weight: 600;
  font-size: 9.5px;
  line-height: 1;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--gold);
}

.projects__title {
  margin: 12px 0 0;
  font-weight: 800;
  font-size: 40px;
  line-height: 1.1;
  letter-spacing: -0.025em;
  color: #fff;
}

.projects__year {
  margin: 12px 0 0;
  font-family: var(--font-mono);
  font-weight: 600;
  font-size: 11px;
  line-height: 1;
  letter-spacing: 0.14em;
  color: rgba(255, 255, 255, 0.6);
}

/* The facts: a two-column grid of mono labels and plain values. */
.projects__grid {
  display: grid;
  grid-template-columns: 96px 1fr;
  row-gap: 12px;
  margin: 28px 0 0;
  font-size: 15px;
  line-height: 1.4;
  color: var(--paper);
}

.projects__grid dt {
  font-family: var(--font-mono);
  font-weight: 600;
  font-size: 9.5px;
  line-height: 1.6;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: rgba(255, 255, 255, 0.45);
}

.projects__grid dd {
  margin: 0;
}

/* The links: full-width rows between hairlines, the arrow at the right. */
.projects__links {
  margin: 32px 0 0;
  padding: 0;
  list-style: none;
  border-top: 1px solid rgba(255, 255, 255, 0.16);
}

.projects__link {
  display: flex;
  align-items: center;
  justify-content: space-between;
  min-height: 56px;
  border-bottom: 1px solid rgba(255, 255, 255, 0.16);
  color: #fff;
  font-weight: 700;
  font-size: 11px;
  line-height: 1;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  text-decoration: none;
  transition: color var(--quick);
}

.projects__link:hover,
.projects__link:focus-visible {
  color: var(--gold);
}

.projects__arrow {
  font-size: 15px;
}

/* The index jumps smoothly, as the handoff asks; under reduced motion the
   jump is a jump. The property is on the root because the anchors scroll
   the document. */
html:has(.projects) {
  scroll-behavior: smooth;
}

@media (prefers-reduced-motion: reduce) {
  html:has(.projects) {
    scroll-behavior: auto;
  }
}

/* ---- The Projects page on a phone ---------------------------------------
 *
 * One vertical scroller. The index is the top; then every block fills the
 * screen — `100svh`, the handoff's 844 — with the poster taking whatever
 * height the facts leave it. Below the site's 900px split, as everywhere. */
@media (max-width: 900px) {
  .projects__index {
    padding: 32px 20px 40px;
  }

  .projects__list {
    gap: 0;
  }

  .projects__entry {
    min-height: 44px;
    gap: 8px;
  }

  .projects__no {
    width: 16px;
    font-size: 9px;
    padding-top: 5px;
  }

  .projects__entry-title {
    font-size: 28px;
    line-height: 1.2;
    letter-spacing: -0.02em;
  }

  .projects__blocks {
    gap: 0;
    padding: 0;
  }

  /* A block is a screen: column, the poster area flexing to fill, the
     facts beneath at their natural height. */
  /* One selector for both: the even block's reversal and inset are a class
     of the same weight written earlier, so this later rule wins for it too. */
  .projects__block {
    flex-direction: column;
    /* **Stretch, not the desk's `flex-start`.** As a column the block's
       cross axis is the width, and inherited `flex-start` left the poster
       column shrinking to its content — measured at 43px, which is what
       made the frame's 2:3 look broken for three attempts before the cause
       was measured rather than guessed at. */
    align-items: stretch;
    gap: 0;
    /* **A screen, less the sticky header.** The handoff draws a phone whose
       header scrolls away and gives each block the whole 844; this site's
       header stays, and `scroll-padding-top: 80px` is where a snapped block
       lands. A full `100svh` here put the last link 80px below the fold —
       seen in a screenshot, after the frame's width was fixed. */
    min-height: calc(100svh - 80px);
    box-sizing: border-box;
    padding: 12px 20px 24px;
    border-top: 1px solid rgba(255, 255, 255, 0.1);
    scroll-margin-top: 0;
  }

  /* The top row reads "01 / 06"; the poster sits under it, left-aligned,
     as tall as the room allows and never wider than the screen.

     **A ratio only transfers from a height that is already definite**, and
     three measured attempts say so. The picture in the flow sized the frame
     from its own intrinsic width (234x432, the `sizes` attribute exactly). A
     grid row and then a flexed frame both left the width shrinking to
     nothing (43x432): a flex item's cross size is computed before its main
     size is flexed, so there is no height to read yet. What works is the
     handoff's own shape - an *area* that flexes, and a frame inside it
     taking `height: 100%` of a height that has already been resolved. */
  /* **Not `column-reverse`.** It was, to lift the counter above the poster
     while the markup had only those two; the trailer moved under the poster
     on 23-09-2026 and reversing three children put the button *above* the
     picture — seen in a screenshot. The counter is moved on its own
     instead, which says what is meant and survives a fourth child. */
  .projects__poster-column {
    display: flex;
    flex-direction: column;
    align-items: stretch;
    flex: 1;
    min-height: 0;
    width: auto;
    gap: 8px;
  }

  .projects__poster-area {
    display: flex;
    flex: 1 1 0;
    min-height: 0;
  }

  /* The counter and the toggle share the top row. */
  .projects__top {
    order: -1;
    flex: none;
    display: flex;
    align-items: center;
    justify-content: space-between;
    gap: 12px;
    min-height: 44px;
  }

  .projects__count {
    display: flex;
    align-items: center;
    letter-spacing: 0.12em;
  }

  .projects__snap {
    display: inline-flex;
    align-items: center;
    gap: 10px;
    min-height: 44px;
    padding: 0 6px 0 16px;
    border: 1px solid rgba(242, 237, 230, 0.18);
    border-radius: var(--radius-pill);
    background: none;
    color: var(--paper);
    font-family: var(--font);
    font-weight: 700;
    font-size: 10px;
    line-height: 1;
    letter-spacing: 0.14em;
    text-transform: uppercase;
    cursor: pointer;
  }

  .projects__snap-track {
    display: flex;
    justify-content: flex-start;
    align-items: center;
    box-sizing: border-box;
    width: 40px;
    height: 24px;
    padding: 3px;
    border-radius: var(--radius-pill);
    background: rgba(255, 255, 255, 0.18);
    transition: background var(--quick);
  }

  .projects__snap-knob {
    width: 18px;
    height: 18px;
    border-radius: 50%;
    background: var(--paper);
  }

  /* **On is read from the button's own state.** `aria-checked` is what a
     screen reader hears, so drawing from it means what is announced and
     what is seen cannot drift — the rule the admin's chips already follow. */
  .projects__snap[aria-checked="true"] .projects__snap-track {
    justify-content: flex-end;
    background: var(--gold);
  }

  .projects__snap[aria-checked="true"] .projects__snap-knob {
    background: var(--ink);
  }

  .projects__count-of {
    display: inline;
    color: rgba(255, 255, 255, 0.4);
  }

  .projects__frame {
    height: 100%;
    width: auto;
    max-width: 100%;
  }

  .projects__trailer {
    /* Its own width, not the column's: a pill across the screen reads as a
       band rather than a button. */
    align-self: flex-start;
    flex: none;
    margin-top: 2px;
    min-height: 44px;
    padding: 0 18px;
    font-size: 10px;
    white-space: nowrap;
  }

  .projects__facts {
    /* **A basis written for a row is a height in a column — 28-09-2026,
       reported from an iPhone as the posters not showing at all.**

       The base rule is `flex: 0 1 480px`, which is a *width* where the block
       is a flex row. Here the block is a column, so the very same 480px
       claimed the facts 480 of a 764px screen, and the poster took what was
       left: a 94x141 frame. On a real phone it is smaller again, because
       `100svh` is shorter there — small enough that iOS drew its
       broken-image glyph in the gap, which read as a picture that had failed
       to load rather than as one squeezed to nothing.

       **`width: auto` below cancels the rule this replaced, not this one.**
       Until 24-09-2026 the base was `width: 480px; flex: none`, and `none`
       is `0 0 auto` — already the content height, so there was nothing here
       to undo. The tiled-window fix turned the width into a basis and this
       block was never told, which is how a fix for a half-screen laptop
       crushed the phone with every test still green.

       Measured on the running page at 390: the facts fall to their content,
       323px and 277px, and the three frames become 199x298, 235x352 and
       229x344, with the block still exactly one screen. */
    flex: 0 0 auto;
    width: auto;
    padding-top: 0;
  }

  .projects__function {
    margin-top: 18px;
  }

  /* Title and year share a line on a phone. */
  .projects__title {
    margin-top: 9px;
    font-size: 26px;
  }

  .projects__year {
    margin-top: 6px;
    font-size: 10px;
  }

  .projects__grid {
    grid-template-columns: 86px 1fr;
    row-gap: 8px;
    margin-top: 14px;
    font-size: 14px;
  }

  .projects__grid dt {
    font-size: 9px;
    letter-spacing: 0.12em;
  }

  .projects__links {
    margin-top: 14px;
  }

  .projects__link {
    min-height: 46px;
    font-size: 10.5px;
  }
}

/* Snap scroll on a phone — one project per swipe — is the island's to turn
   on: it puts `projects-snap` on the root while the toggle is on, the
   default. With scripting off the page is a plain scroller, because a
   mandatory snap with no way to turn it off would be a trap rather than a
   convenience. */
@media (max-width: 900px) {
  html.projects-snap {
    scroll-snap-type: y mandatory;
  }

  html.projects-snap .projects__index {
    scroll-snap-align: start;
  }

  html.projects-snap .projects__block {
    scroll-snap-align: start;
    scroll-snap-stop: always;
  }

  /* **The end of the page is a place to rest** — the owner's word,
     23-09-2026: past the last project the scroller pulled back and it read
     as broken.

     `y mandatory` means the scroller must always come to rest *on* a snap
     point, so with only the blocks marked there was nowhere legal below the
     last one and a swipe past it snapped back. The footer is a snap point
     now, aligned to the bottom of the screen — which is what the handoff's
     own phone frame does with it — so the contact bar and the footer are
     reachable and the snapping lets go there.

     Not `proximity` instead: that would soften every swipe between projects
     to fix the one at the end, and one swipe landing on one project is the
     whole of what this toggle is for.

     **On the copyright line, not on `.footer`.** That line is a *sibling*
     of the footer element rather than inside it, so a snap point on the
     footer sat 54px above the bottom of the page — measured, after the
     first version still would not let go. The rule belongs on whatever the
     page actually ends with. */
  html.projects-snap .footer__bottom {
    scroll-snap-align: end;
  }
}


/* ---------------------------------------------------------------------------
   The legal pages — Module 22, both designs.

   Two handoffs, one stylesheet. `design_handoff_legal_pages` draws a readable
   document with a numbered rail and licence cards;
   `design_handoff_legal_pages_v2` draws the plain official document. They
   share the column, the title block and the type, and differ in how the
   clauses are drawn — which is why they share a template too.

   Every colour both handoffs name was already a token: the ground, the
   surface, the paper ink and `--gold` are exact matches.
   --------------------------------------------------------------------------- */

.legal {
  padding-block: clamp(40px, 7vw, 88px) 96px;
}

/* **760px, not the site's 940.** A legal page is read front to back, and 940
   is a wide measure for continuous prose — the handoff asks for 760 in v1 and
   720 in v2, and the narrower of the site's own habits is the right one here.
   The gutters stay the band's, so the page lines up with every other. */
.legal__doc {
  width: min(760px, 100%);
  margin-inline: auto;
  display: flex;
  flex-direction: column;
  gap: 40px;
}

.legal__head {
  display: flex;
  flex-direction: column;
  gap: 14px;
  /* The handoff's 1px rule under the title block. Drawn on the header rather
     than as a separate element, so a page with no intro still gets it. */
  border-bottom: 1px solid rgba(242, 237, 230, 0.12);
  padding-bottom: 28px;
}

.legal__title {
  margin: 0;
  font-weight: 800;
  font-size: clamp(28px, 4vw, 44px);
  line-height: 1.12;
  letter-spacing: -0.02em;
}

.legal__updated {
  margin: 0;
  font-weight: 500;
  font-size: 13px;
  color: rgba(242, 237, 230, 0.55);
}

.legal__intro {
  margin: 0;
  font-size: 16px;
  line-height: 1.7;
  color: rgba(242, 237, 230, 0.8);
}

/* --- the readable design: a numbered run of clauses ----------------------- */

.legal__sections,
.legal__tiers {
  display: flex;
  flex-direction: column;
  gap: 34px;
}

.legal__section-title {
  margin: 0 0 14px;
  font-weight: 800;
  font-size: 13px;
  line-height: 1.4;
  letter-spacing: 0.14em;
  text-transform: uppercase;
}

/* The number is the only gold on a clause, which is what makes the rail read
   as a rail rather than as decoration. */
.legal__number {
  color: var(--gold);
  margin-right: 10px;
}

.legal__p {
  margin: 0 0 14px;
  font-size: 15px;
  line-height: 1.75;
  color: rgba(242, 237, 230, 0.75);
  /* The official design's line breaks are the author's own and survive as
     newlines all the way from the admin — so they are drawn here rather than
     by building a `<br>`, which is what keeps the body plain text. */
  white-space: pre-wrap;
}

.legal__p:last-child {
  margin-bottom: 0;
}

.legal__lines {
  margin: 0;
  padding: 0;
  list-style: none;
  display: flex;
  flex-direction: column;
  gap: 8px;
}

.legal__lines li {
  position: relative;
  padding-left: 22px;
  font-size: 15px;
  line-height: 1.7;
  color: rgba(242, 237, 230, 0.75);
}

/* The handoff's dash marker, drawn rather than written: a screen reader
   reading "em dash" before every line of a privacy policy is worse than a
   list it can announce as a list. */
.legal__lines li::before {
  content: "—";
  position: absolute;
  left: 0;
  color: var(--gold);
}

/* The one table in the readable design — the cancellation fees. A description
   list, because each row is a term and what it costs rather than two
   unrelated cells. */
.legal__rows {
  margin: 16px 0 0;
  display: flex;
  flex-direction: column;
  border: 1px solid rgba(242, 237, 230, 0.12);
  border-radius: 12px;
  overflow: hidden;
}

.legal__row {
  display: flex;
  justify-content: space-between;
  gap: 18px;
  padding: 13px 18px;
}

.legal__row + .legal__row {
  border-top: 1px solid rgba(242, 237, 230, 0.12);
}

.legal__row dt {
  font-weight: 700;
  font-size: 14px;
}

.legal__row dd {
  margin: 0;
  font-weight: 600;
  font-size: 14px;
  color: var(--gold);
  text-align: right;
}

/* --- the readable design: a licence card per service --------------------- */

.legal__tier {
  padding: clamp(20px, 3vw, 28px);
  border: 1px solid rgba(242, 237, 230, 0.12);
  border-radius: 14px;
  background: rgba(242, 237, 230, 0.03);
}

.legal__tier-name {
  margin: 0 0 10px;
  font-weight: 800;
  font-size: 22px;
  line-height: 1.2;
}

.legal__tier-summary {
  margin: 0 0 20px;
  font-size: 15px;
  line-height: 1.7;
  color: rgba(242, 237, 230, 0.75);
}

.legal__tier-columns {
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: 24px;
}

.legal__tier-label {
  margin: 0 0 10px;
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.55);
}

.legal__tier-list {
  margin: 0;
  padding: 0;
  list-style: none;
  display: flex;
  flex-direction: column;
  gap: 8px;
}

.legal__tier-list li {
  position: relative;
  padding-left: 20px;
  font-size: 14px;
  line-height: 1.6;
  color: rgba(242, 237, 230, 0.8);
}

.legal__tier-list li::before {
  position: absolute;
  left: 0;
}

/* The permitted column is gold and the refused one is not, which is the
   handoff's own distinction: what a licence *grants* is what somebody came to
   read. */
.legal__tier-list--can li::before {
  content: "+";
  color: var(--gold);
}

.legal__tier-list--cannot li::before {
  content: "–";
  color: rgba(242, 237, 230, 0.4);
}

/* --- the closing box ----------------------------------------------------- */

.legal__contact {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  justify-content: space-between;
  gap: 18px;
  padding: clamp(18px, 3vw, 24px);
  border: 1px solid rgba(242, 237, 230, 0.12);
  border-radius: 14px;
}

.legal__contact-heading {
  margin: 0;
  font-weight: 700;
  font-size: 16px;
}

/* --- the official design: a plain document ------------------------------- */

.legal__contents {
  border-top: 1px solid rgba(242, 237, 230, 0.12);
  border-bottom: 1px solid rgba(242, 237, 230, 0.12);
  padding-block: 18px;
}

.legal__contents-title {
  margin: 0 0 10px;
  font-weight: 700;
  font-size: 14px;
}

.legal__contents-list {
  margin: 0;
  padding: 0;
  list-style: none;
  display: flex;
  flex-direction: column;
  gap: 6px;
}

.legal__contents-list a {
  font-size: 14px;
  color: rgba(242, 237, 230, 0.82);
  text-decoration-color: rgba(242, 237, 230, 0.3);
  text-underline-offset: 3px;
}

.legal__contents-list a:hover {
  color: var(--gold);
}

.legal__body {
  display: flex;
  flex-direction: column;
  gap: 16px;
}

/* The official design's headings are the author's, numbered in the text. Flat
   weight and size rather than a rail: it should read like a document, not like
   a brochure.

   **24px, not 96 — measured on the running page.** This is what keeps the
   sticky header off a heading somebody has just followed a contents link to,
   and the first version assumed it had to clear that header on its own. It
   does not: below the desktop step the root is already padded by 80px for
   exactly this, the two add up, and 96 put the heading 176px down the
   viewport — 107px of clearance under a 69px header. 24 is the handoff's own
   figure and leaves about 35px.

   Above the step the header is static and the root is not padded, so 24px is
   the whole offset there — which is what that width wants, since there is no
   header to clear.

   The property the root uses is deliberately not written out here: the
   stylesheet tests read these comments, and naming it in prose is how a
   comment fails a test about the rule it is describing. */
.legal__h {
  margin: 12px 0 0;
  font-weight: 700;
  font-size: 16px;
  line-height: 1.5;
  scroll-margin-top: 24px;
}

/* A paragraph inside the official body carries its gap from the flex column
   above, so the margin the readable design needs would double it. */
.legal__body > .legal__p {
  margin-bottom: 0;
}

/* --- the Cookie policy: one Markdown body in the legal column ------------- */

/* The fourth legal page is a heading and a body rather than a run of clauses,
   so what it draws is whatever the sanitiser let through — see ALLOWED_TAGS in
   `app/services/rendering.py`. Every element on that list has a rule below,
   with a test asserting so: a page that names seven cookies in backticks and
   then draws them as the browser's default monospace is the fault this whole
   block exists to prevent, and nothing in the markup can show it.

   The type scale is the readable design's, element for element, so following
   Privacy's Cookies link lands somewhere that reads like the page it came
   from.

   **Not `pre-wrap`, unlike `.legal__p`.** That rule keeps the official
   design's authored line breaks, which arrive as newlines from the admin and
   are the author's own. Markdown has already decided where the paragraphs
   are, and its source is wrapped at the editor's width — so pre-wrap here
   would draw every one of those wraps as a hard break. The one declaration
   this block must not inherit. */
.legal__prose {
  display: flex;
  flex-direction: column;
  gap: 16px;
}

.legal__prose p {
  margin: 0;
  font-size: 15px;
  line-height: 1.75;
  color: rgba(242, 237, 230, 0.75);
}

/* Markdown headings are demoted, so `#` is an h2 and `##` an h3. Flat weight
   and size rather than a rail, the official design's reasoning: it should read
   like a document.

   **No scroll offset here, unlike `.legal__h` — removed 07-10-2026 after
   measuring.** That rule exists so a heading followed from a contents link
   lands clear of the sticky header. These headings come out of
   `render_markdown` as bare elements with no `id` at all, so nothing can link
   to one and the offset guarded a case that cannot happen. Giving them
   anchors would mean slugging headings in the Markdown renderer, which every
   Markdown field on the site goes through — a site-wide change, not this
   page's, and nobody has asked for links into a cookie policy. */
.legal__prose h2,
.legal__prose h3,
.legal__prose h4,
.legal__prose h5,
.legal__prose h6 {
  margin: 14px 0 0;
  font-weight: 700;
  font-size: 16px;
  line-height: 1.5;
}

/* The deeper levels step down in size rather than sharing one, so a heading
   nested under another reads as nested. */
.legal__prose h3 {
  font-size: 15px;
}

.legal__prose h4,
.legal__prose h5,
.legal__prose h6 {
  font-size: 14px;
  letter-spacing: 0.04em;
  text-transform: uppercase;
  color: rgba(242, 237, 230, 0.6);
}

/* The dash marker the readable design draws, and the same reason it is drawn
   rather than written: a screen reader reading "em dash" before every line of
   a cookie policy is worse than a list it can announce as a list. A numbered
   list keeps its own markers, because the number is the content there. */
.legal__prose ul {
  margin: 0;
  padding: 0;
  list-style: none;
  display: flex;
  flex-direction: column;
  gap: 8px;
}

.legal__prose ol {
  margin: 0;
  padding-left: 22px;
  display: flex;
  flex-direction: column;
  gap: 8px;
}

.legal__prose li {
  font-size: 15px;
  line-height: 1.7;
  color: rgba(242, 237, 230, 0.75);
}

.legal__prose ul > li {
  position: relative;
  padding-left: 22px;
}

.legal__prose ul > li::before {
  /* The character itself, not `\` plus its code point — `.legal__lines` next
     door already writes it this way, and an escaped one reads as a four-digit
     year to the sweep that forbids a hard-coded year in generated content.
     Which is this stylesheet's own "prose is read by the tests" rule arriving
     as an escape rather than as a comment. */
  content: "—";
  position: absolute;
  left: 0;
  color: var(--gold);
}

/* A nested list sits in from its parent and carries no gap of its own above,
   so the two read as one run rather than two blocks. */
.legal__prose li > ul,
.legal__prose li > ol {
  margin-top: 8px;
}

.legal__prose strong {
  font-weight: 700;
  color: rgba(242, 237, 230, 0.92);
}

.legal__prose em {
  font-style: italic;
}

/* Links in the paper ink with a faint underline, the contents list's
   treatment: the gold is for hover, so a paragraph holding three links does
   not read as three buttons. */
.legal__prose a {
  color: rgba(242, 237, 230, 0.82);
  text-decoration-color: rgba(242, 237, 230, 0.3);
  text-underline-offset: 3px;
}

.legal__prose a:hover {
  color: var(--gold);
}

/* This page names seven cookie keys, each in backticks — `tapesome_consent`
   and the rest. A stored key is a literal somebody may have to match against
   what their browser shows them, so it is set in the monospace face at a size
   that still sits on the line around it.

   **`overflow-wrap`, not `word-break: break-word` — corrected 07-10-2026
   after measuring the running page.** A key is one unbroken word and a 390px
   screen is narrower than some of them, so it has to be allowed to break. The
   first version used the deprecated `word-break: break-word`, whose effect is
   applied at layout and is *not* reflected in any computed value — so neither
   a probe nor a stylesheet test could tell whether it was doing anything, and
   the longest key happened to fit at 390, which proved nothing either way.
   `overflow-wrap: break-word` is the standard property, breaks only when the
   word would otherwise overflow, and its computed value is readable. */
.legal__prose code {
  font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
  font-size: 13px;
  padding: 1px 5px;
  border-radius: 4px;
  background: rgba(242, 237, 230, 0.08);
  color: rgba(242, 237, 230, 0.92);
  overflow-wrap: break-word;
}

/* A fenced block is its own box and must scroll rather than widen the column,
   and the inline treatment inside it would draw a second background on every
   line. */
.legal__prose pre {
  margin: 0;
  padding: 14px 16px;
  border-radius: 10px;
  background: rgba(242, 237, 230, 0.06);
  overflow-x: auto;
}

.legal__prose pre code {
  padding: 0;
  background: none;
  border-radius: 0;
  white-space: pre;
}

/* A quotation is marked by a gold rule rather than quotation marks, which the
   author may have typed themselves. */
.legal__prose blockquote {
  margin: 0;
  padding-left: 16px;
  border-left: 2px solid rgba(255, 216, 151, 0.5);
  color: rgba(242, 237, 230, 0.7);
}

/* A break between two runs of a document, at the weight of the rule under the
   title block so the page has one hairline rather than two. */
.legal__prose hr {
  width: 100%;
  height: 0;
  margin: 8px 0;
  border: 0;
  border-top: 1px solid rgba(242, 237, 230, 0.12);
}

/* A hard break inside a paragraph is the author's, and carries no height of
   its own — stated so the sweep over the allow-list has a rule to find, and
   because `line-height` on a break is what some resets get wrong. */
.legal__prose br {
  line-height: inherit;
}

@media (max-width: 720px) {
  /* Two columns of permissions do not fit a phone, and the labels are what
     tell them apart — so they stack rather than shrink. */
  .legal__tier-columns {
    grid-template-columns: minmax(0, 1fr);
    gap: 18px;
  }

  /* A fee and what it applies to read better one above the other than
     squeezed to the two edges of a 390px screen. */
  .legal__row {
    flex-direction: column;
    gap: 4px;
  }

  .legal__row dd {
    text-align: left;
  }
}

/* The official document's download link, and a licence card's.
   The handoff draws both as plain underlined text in the accent rather than
   as buttons: a document is something to fetch, and a filled pill beside
   "Last updated" would read as the page's main action. */
.legal__download,
.legal__tier-download {
  margin: 0;
}

.legal__tier-download {
  margin-top: 18px;
}

.legal__download a,
.legal__tier-download a {
  font-weight: 600;
  font-size: 14px;
  color: var(--gold);
  text-underline-offset: 3px;
}

.legal__download a:hover,
.legal__tier-download a:hover {
  color: var(--paper);
}

/* The way back to the cookie box, in the footer of every page.
   **Withdrawing has to be as easy as giving**, which is the law's rule and
   the handoff's — so it is the same size and weight as the links beside it
   rather than a quieter afterthought. Drawn as a button because it opens a
   box rather than going anywhere; it looks like its neighbours because it
   belongs in the row. */
.footer__consent {
  padding: 0;
  border: 0;
  background: none;
  color: inherit;
  font: inherit;
  cursor: pointer;
  text-decoration: underline;
  text-underline-offset: 3px;
}

.footer__consent:hover {
  color: var(--gold);
}

/* ---- The loading cover — claude_designs/design_handoff_loading_page ------

   **Hidden unless something switches it on, and only a script can.** The
   markup is in every page (loader.html) so that a first visit can open
   behind it from the very first paint; this rule keeps it out of the way
   everywhere else. Three classes show it: `ts-loading` on the root, added by
   the head gate on the first page of a visit (the long design);
   `ts-reloading`, added by the same gate when a page that asks for it is
   reloaded (the short design); and `is-shown`, added by the navigation
   script when a click is slow to leave. With no JavaScript
   neither appears and nobody ever sees it.

   **Every value below is the handoff's**, which calls its colours, type,
   sizes and motion final — except the hairline frame it draws inset from
   the edge, which the owner took out on seeing it on a phone, 07-10-2026. The phone sizes take over below 768px — the
   handoff's own step for this screen, rather than the site's 720 or 900,
   because it is the width its phone frame was drawn for. */

.loader {
  display: none;
  position: fixed;
  inset: 0;
  z-index: 10000;
  overflow: hidden;
  font-family: Raleway, system-ui, sans-serif;
  background: linear-gradient(140deg, #2e211a 0%, #4a3527 58%, #6e4a35 100%) #35261d;
  /* The exit, and the only transition: no entrance animation, the cover
     appears at full opacity straight away. */
  transition: opacity 0.4s ease;
}

html.ts-loading .loader,
html.ts-reloading .loader,
.loader.is-shown {
  display: block;
}

/* The long cover: the glow, and the flowing lines on the canvas. A first
   visit is long from its first frame — set here rather than waiting for the
   script, or the glow would arrive a moment after the cover did. */
html.ts-loading .loader,
.loader--long {
  background:
    radial-gradient(70% 60% at 50% 50%, rgba(217, 136, 106, 0.2), transparent 60%),
    linear-gradient(140deg, #2e211a 0%, #4a3527 58%, #6e4a35 100%) #35261d;
}

/* **The colours Safari paints into its own status bar and toolbar** —
   settled on the owner's phone, 07-10-2026.

   The bands above and below the cover on an iPhone are Safari's chrome, not
   the page, and Safari chooses their colour itself: it reads the solid
   `background-color` of a fixed element touching the screen's edge, which is
   what the contact bar's toolbar experiments of 22-09-2026 found. The
   cover's ground was a gradient *image* with no colour beneath it, so there
   was nothing to read and both bands came out the site's near-black.

   **The top** is the cover's own background colour, carried inside each
   `background` shorthand below (a shorthand resets the colour, and the long
   cover's rule outranks a separate one): #35261D, the gradient where it
   meets the top of a 390px phone, worked out from the 140deg angle and the
   three stops. On the phone the status bar took it, and let it go again
   when the cover faded.

   **The bottom** needs a lighter colour, about #624330, and the cover can
   only carry one — so Safari read the top colour there too, a visible step
   under the toolbar. A first strip of 2px was ignored, evidently too small to
   count. A 120px strip, solid for Safari to read and faded into the cover by
   a mask so nobody sees a band, was read: the mask changes what is painted,
   not the computed colour.

   **And the same strip at the top, for a different reason.** Measured off
   the phone's own screenshot: Safari paints the status bar a flat #34271F —
   the colour it was given — while the cover just beneath runs #2D231C on the
   left, #352820 in the middle and #3B2D23 on the right. A flat band against
   a gradient steps at both ends whatever colour is chosen. So the cover's
   top edge is made flat instead, in the band's own colour, fading into the
   gradient below. The bottom strip does the same thing to the bottom edge,
   which is why it blended. */
.loader__edge {
  /* Only on a phone, below. A desktop browser has no toolbar under the
     page, and its gradient runs much further across each edge — about
     #2E211A to #4A3527 along the top at 1440 wide — so a flat strip there
     would show as a band of its own. */
  display: none;
  position: fixed;
  left: 0;
  right: 0;
  height: 120px;
  pointer-events: none;
}

.loader__edge--top {
  top: 0;
  background-color: #35261d;
  -webkit-mask-image: linear-gradient(to bottom, #000, transparent);
  mask-image: linear-gradient(to bottom, #000, transparent);
}

.loader__edge--bottom {
  bottom: 0;
  background-color: #624330;
  -webkit-mask-image: linear-gradient(to top, #000, transparent);
  mask-image: linear-gradient(to top, #000, transparent);
}

.loader__canvas {
  display: none;
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
}

html.ts-loading .loader__canvas,
.loader--long .loader__canvas {
  display: block;
}

.loader__col {
  position: absolute;
  inset: 0;
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: 26px;
}

.loader__logo {
  width: 240px;
  height: 198px;
}

.loader__logo svg {
  display: block;
  width: 100%;
  height: 100%;
}

.loader__words {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 14px;
}

/* Tracking adds space after every letter, the last one included, so the
   matching left padding is what keeps a tracked word optically centred. */
.loader__mark {
  font-weight: 800;
  font-size: 15px;
  letter-spacing: 0.28em;
  padding-left: 0.28em;
  color: #fff;
}

.loader__label {
  display: flex;
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.24em;
  padding-left: 0.24em;
  text-transform: uppercase;
  color: #ffd897;
}

/* A fixed box, so the word does not move as the dots type out. */
.loader__dots {
  display: inline-block;
  width: 1.4em;
  text-align: left;
}

/* Leaving: faded out, and no longer catching presses while it does — under
   reduced motion the fade is instant but the element stays for the same
   moment, and it must not swallow a click in that moment. */
.loader.is-leaving {
  opacity: 0;
  pointer-events: none;
}

/* **The failsafe, and why it is CSS.** The head gate switches a first-visit
   cover on before any other script has run; the navigation script is what
   takes it away. If that script never runs — blocked, broken, a build that
   did not deploy — nothing else would, and the visitor would be left looking
   at a loading screen over a page that loaded long ago. So the stylesheet
   takes the cover away by itself after eight seconds, twice the script's own
   longest wait. A failsafe that needed JavaScript would fail with it.

   The reduced-motion sweep near the top of this file shortens every
   animation's *duration*, not its *delay*, so this still waits the eight
   seconds and then simply vanishes rather than fading. */
html.ts-loading .loader {
  animation: loader-failsafe 0.4s ease 8s forwards;
}

/* The same failsafe for a reload's cover, which the same gate switches on
   and the same script takes away. Its own rule rather than a second selector
   on the one above, so each can be read on its own. */
html.ts-reloading .loader {
  animation: loader-failsafe 0.4s ease 8s forwards;
}

@keyframes loader-failsafe {
  to {
    opacity: 0;
    visibility: hidden;
  }
}

@media (max-width: 767px) {
  .loader__edge {
    display: block;
  }

  .loader__col {
    gap: 20px;
  }

  .loader__logo {
    width: 150px;
    height: 124px;
  }

  .loader__words {
    gap: 12px;
  }

  .loader__mark {
    font-size: 12.5px;
  }

  .loader__label {
    font-size: 9.5px;
  }

  html.ts-loading .loader,
  .loader--long {
    background:
      radial-gradient(90% 50% at 50% 50%, rgba(217, 136, 106, 0.2), transparent 60%),
      linear-gradient(140deg, #2e211a 0%, #4a3527 58%, #6e4a35 100%) #35261d;
  }
}

/* The hire brief v2's fields (26e-2a): a gap between one field and the next
   at every width. The 20px above is the wide panel's alone, and on a phone a
   box ran straight into the next field's label. Scoped to `[data-field]`,
   which only the new brief's fields carry. */
.briefsteps .brief__question--sub[data-field] + .brief__question--sub[data-field] {
  margin-top: 20px;
}


/* Production days' steppers (26e-2b): − · number · +, a pill in today's
   chip colours, the presses a finger's size. */
.brief-days {
  display: flex;
  flex-wrap: wrap;
  gap: 10px 16px;
}

.brief-stepper {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  padding: 3px;
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius-pill);
}

.brief-stepper__press {
  width: 44px;
  height: 44px;
  border: 0;
  border-radius: 50%;
  background: rgba(255, 216, 151, 0.16);
  color: var(--gold);
  font: inherit;
  font-size: 20px;
  line-height: 1;
  cursor: pointer;
}

.brief-stepper__press[aria-disabled="true"] {
  opacity: 0.35;
  cursor: default;
}

.briefsteps .brief-stepper input {
  width: 4.5ch;
  padding: 8px 4px;
  border: 0;
  background: transparent;
  text-align: center;
  font-size: 16px;
}

/* The number box has no border of its own — the stepper draws it — so the
   stepper is what lights while the box has focus. */
.briefsteps .brief-stepper:has(input:focus-visible) {
  border-color: var(--gold-edge);
}

/* The steps put away for the details on a phone (26e-5b). The track has a
   `display` of its own at every width, which beats the `hidden` attribute's
   — so `hidden` alone left the steps on screen under "Edit brief". Three
   classes and an attribute, above every rule that sets the track's
   display. */
.briefsteps .briefsteps__track[hidden] {
  display: none;
}

/* The brief's own calendar (26e-2c-1), for a date and for dates: a card in
   the brief's colours, a month with round arrows, seven columns Monday first.
   The day cells are the Availability handoff's — radius 10, today ringed,
   the past faded — and a picked day is solid gold, the brief's own picked
   colour. The width is a calendar's, not the card's: 7 × 44px days and their
   gaps, so a wide card does not stretch it into a strip.
   **The gap between days is inside each day**: a transparent 2px border with
   the background painted within it, so the press reaches the whole cell
   while the days still look apart — on a 390px phone 312 / 7 leaves 44px
   with nothing to spare for a gap. */
/* 16px from the chips above it and to the picked days under it — the
   owner's word, 16-10-2026: the field's own 6px, and 10px, ran them
   together. The margin adds to the field's gap. */
.daypicker {
  display: grid;
  gap: 16px;
  margin-top: 10px;
  justify-items: start;
}

.calendar {
  display: grid;
  gap: 10px;
  box-sizing: border-box;
  width: 100%;
  max-width: 380px;
  padding: 14px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: var(--radius);
  background: rgba(255, 255, 255, 0.03);
}

.calendar__head {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 8px;
}

.calendar__month {
  font-weight: 700;
  font-size: 14px;
  color: var(--paper);
}

.calendar__turn {
  width: 44px;
  height: 44px;
  border: 1px solid var(--line-on-dark);
  border-radius: 50%;
  background: rgba(242, 237, 230, 0.04);
  color: var(--paper);
  font: inherit;
  font-size: 22px;
  line-height: 1;
  cursor: pointer;
}

.calendar__turn[aria-disabled="true"] {
  opacity: 0.3;
  cursor: default;
}

.calendar__grid {
  display: grid;
}

.calendar__week {
  display: grid;
  grid-template-columns: repeat(7, minmax(0, 1fr));
}

.calendar__weekday {
  padding: 2px 0;
  text-align: center;
  font-weight: 700;
  font-size: 9px;
  letter-spacing: 0.12em;
  text-transform: uppercase;
  color: var(--paper-faint);
}

.calendar__day {
  width: 100%;
  min-height: 44px;
  padding: 0;
  border: 2px solid transparent;
  border-radius: 10px;
  background: rgba(242, 237, 230, 0.04);
  background-clip: padding-box;
  color: rgba(242, 237, 230, 0.78);
  font: inherit;
  font-weight: 800;
  font-size: 15px;
  cursor: pointer;
  transition: background var(--quick), color var(--quick);
}

/* An inner ring: the border is the gap, so the ring sits inside it. */
.calendar__day[aria-current="date"] {
  box-shadow: inset 0 0 0 1px rgba(242, 237, 230, 0.42);
}

/* Hover only on a day still to pick: a picked day keeps its gold under the
   pointer, a shut one does not look pressable. */
@media (hover: hover) {
  .calendar__day[aria-pressed="false"]:not([aria-disabled="true"]):hover,
  .calendar__turn:not([aria-disabled="true"]):hover {
    /* The colour only: the shorthand would put the clip back to the border
       and fill the gap. */
    background-color: rgba(242, 237, 230, 0.1);
  }
}

.calendar__day[aria-pressed="true"] {
  background-color: var(--gold);
  color: var(--dark);
}

.calendar__day[aria-disabled="true"] {
  opacity: 0.3;
  cursor: default;
}

.calendar__day:focus-visible,
.calendar__turn:focus-visible,
.daypicker__chip:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* On a phone the card is the calendar's frame: its own would take the
   width seven 44px days need. */
@media (max-width: 720px) {
  .calendar {
    padding: 0;
    border: 0;
    background: none;
  }
}

/* The studio's places above a location's box (26e-3): one line, as many as
   fit and then a dashed More…. Pills of their own — on a phone
   `brief__option` becomes a full-width row. The line is `relative` for the
   copy it measures from, which is clipped to nothing inside it.
   **`contain: inline-size`**: the chips' widths never size the line. On a
   phone the step's card is sized by what is in it, so a line of uncounted
   chips made itself wide enough and then measured that (530px in a 312px
   card, 16-10-2026). */
.placechips {
  position: relative;
  display: flex;
  flex-wrap: nowrap;
  gap: 8px;
  margin-top: 10px;
  contain: inline-size;
}

.placechips__copy {
  position: absolute;
  top: 0;
  left: 0;
  display: flex;
  gap: 8px;
  width: 0;
  height: 0;
  overflow: hidden;
  visibility: hidden;
}

.placechip {
  position: relative;
  flex: none;
  display: inline-flex;
  align-items: center;
  box-sizing: border-box;
  min-height: 44px;
  padding: 0 17px;
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius-pill);
  background: rgba(242, 237, 230, 0.04);
  color: rgba(242, 237, 230, 0.78);
  font: inherit;
  font-weight: 700;
  font-size: 12px;
  line-height: 1;
  white-space: nowrap;
  cursor: pointer;
  transition: background var(--quick), border-color var(--quick), color var(--quick);
}

@media (hover: hover) {
  .placechip:hover {
    background: rgba(242, 237, 230, 0.08);
  }
}

.placechip:has(input:checked) {
  border-color: rgba(255, 216, 151, 0.55);
  background: rgba(255, 216, 151, 0.16);
  color: var(--gold);
}

.placechip--more {
  border-style: dashed;
  border-color: rgba(242, 237, 230, 0.3);
}

.placechip:has(input:focus-visible),
.placechip--more:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* In the document and the tab order, never seen: the pill shows its state. */
.placechip input {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: 0;
  opacity: 0;
  pointer-events: none;
}

/* More…'s box, over the page it blocks (`inert`, in PlaceChips.tsx). The
   handoff's: a blurred dark cover, a card at most 420px wide, radius 20,
   tick rows and a gold Done. The page under it does not scroll. */
/* The scrollbar's room is kept: without it the page behind widens by a
   scrollbar when it stops scrolling, and everything measured on it moves. */
html.ts-boxed {
  overflow: hidden;
  scrollbar-gutter: stable;
}

.placesbox {
  position: fixed;
  inset: 0;
  z-index: 100;
  display: flex;
  align-items: center;
  justify-content: center;
  padding: 16px;
  background: rgba(11, 10, 9, 0.6);
  backdrop-filter: blur(6px);
  overscroll-behavior: contain;
}

.placesbox__card {
  display: flex;
  flex-direction: column;
  gap: 14px;
  box-sizing: border-box;
  width: 100%;
  max-width: 420px;
  max-height: calc(100dvh - 32px);
  padding: 20px;
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius-lg);
  background: #1d1b18;
  box-shadow: var(--shadow-card);
  color: var(--paper);
}

.placesbox__head {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 12px;
}

.placesbox__title {
  margin: 0;
  font-weight: 700;
  font-size: 18px;
  line-height: 1.2;
}

.placesbox__close {
  flex: none;
  width: 44px;
  height: 44px;
  border: 1px solid var(--line-on-dark);
  border-radius: 50%;
  background: rgba(242, 237, 230, 0.04);
  color: var(--paper);
  font: inherit;
  font-size: 22px;
  line-height: 1;
  cursor: pointer;
}

/* Long lists scroll inside the card, never the page behind it. */
.placesbox__list {
  display: grid;
  gap: 6px;
  overflow-y: auto;
  overscroll-behavior: contain;
}

.placesbox__row {
  display: flex;
  align-items: center;
  gap: 12px;
  min-height: 44px;
  padding: 0 14px;
  border: 1px solid var(--line-on-dark);
  border-radius: 12px;
  background: rgba(242, 237, 230, 0.04);
  font-weight: 700;
  font-size: 13px;
  cursor: pointer;
}

.placesbox__row:has(input:checked) {
  border-color: rgba(255, 216, 151, 0.55);
  background: rgba(255, 216, 151, 0.16);
  color: var(--gold);
}

/* The browser's checkbox is a white square on the dark card: it stays in the
   document and the tab order, unseen, and the tick box beside it shows its
   state, as the chips do. */
.placesbox__row {
  position: relative;
}

.placesbox__row input {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: 0;
  opacity: 0;
  pointer-events: none;
}

.placesbox__tick {
  flex: none;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  box-sizing: border-box;
  width: 20px;
  height: 20px;
  border: 1.5px solid rgba(242, 237, 230, 0.35);
  border-radius: 6px;
  color: transparent;
  font-size: 12px;
  line-height: 1;
}

.placesbox__row:has(input:checked) .placesbox__tick {
  border-color: var(--gold);
  background: var(--gold);
  color: var(--dark);
}

.placesbox__done {
  min-height: 44px;
}

.placesbox__close:focus-visible,
.placesbox__row:has(input:focus-visible),
.placesbox__done:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* An estimation's month and week (26e-2c-2), in the same card. A month is a
   day's cell with a month's words, three across; a week is one press, a row
   of the week's number and its seven days, on eight columns that match the
   header's. The gap between rows is each row's own transparent border, as
   between days. */
.calendar__week--months {
  grid-template-columns: repeat(3, minmax(0, 1fr));
}

.calendar__day--month {
  font-size: 13px;
}

.calendar__week--weeks,
.calendar__weekrow {
  grid-template-columns: 2rem repeat(7, minmax(0, 1fr));
}

/* A week's row holds one cell holding the press: both blocks, so the press
   is the row's width. */
.calendar__weekline,
.calendar__weekline > [role="gridcell"] {
  display: block;
}

.calendar__weekrow {
  display: grid;
  align-items: center;
  width: 100%;
  min-height: 44px;
  padding: 0;
  border: 2px solid transparent;
  border-radius: 10px;
  background: rgba(242, 237, 230, 0.04);
  background-clip: padding-box;
  color: rgba(242, 237, 230, 0.78);
  font: inherit;
  font-weight: 800;
  font-size: 14px;
  cursor: pointer;
  transition: background var(--quick), color var(--quick);
}

.calendar__weeknumber {
  font-weight: 700;
  font-size: 10px;
  letter-spacing: 0.04em;
  color: var(--paper-faint);
}

.calendar__weekdate--outside {
  opacity: 0.45;
}

.calendar__weekrow[aria-current="date"] {
  box-shadow: inset 0 0 0 1px rgba(242, 237, 230, 0.42);
}

@media (hover: hover) {
  .calendar__weekrow[aria-pressed="false"]:not([aria-disabled="true"]):hover {
    /* The colour only, as a day's: the shorthand would fill the gap. */
    background-color: rgba(242, 237, 230, 0.1);
  }
}

.calendar__weekrow[aria-pressed="true"] {
  background-color: var(--gold);
  color: var(--dark);
}

.calendar__weekrow[aria-pressed="true"] .calendar__weeknumber {
  color: inherit;
}

.calendar__weekrow[aria-disabled="true"] {
  opacity: 0.3;
  cursor: default;
}

.calendar__weekrow:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* The picked days under it, a chip each in the brief's picked colours; a
   press takes one off. */
.daypicker__picked {
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  margin: 0;
  padding: 0;
  list-style: none;
}

.daypicker__chip {
  display: inline-flex;
  align-items: center;
  gap: 10px;
  min-height: 44px;
  padding: 0 16px 0 17px;
  border: 1px solid rgba(255, 216, 151, 0.55);
  border-radius: var(--radius-pill);
  background: rgba(255, 216, 151, 0.16);
  color: var(--gold);
  font: inherit;
  font-weight: 700;
  font-size: 12px;
  cursor: pointer;
}

.daypicker__chip span {
  font-size: 16px;
  line-height: 1;
}

/* A draft's day that has passed (26e-4b): faded like the calendar's past,
   still pressable — the note beside it asks for it to be taken off. */
.daypicker__chip--past {
  opacity: 0.45;
}

.daypicker__passed {
  margin: 0;
  color: var(--gold);
}

/* ---------------------------------------------------------------------------
   The hire brief v2's gear kit step (26f-3) — the brief's own look, the
   owner's word: a picked kit in the chips' gold, a kit over budget faded as
   a calendar's past day is. Three across where there is room, one a row on
   a phone; each card a finger's height and more.
   --------------------------------------------------------------------------- */

.kitcards {
  display: grid;
  grid-template-columns: repeat(auto-fill, minmax(min(100%, 220px), 1fr));
  gap: 12px;
  margin-top: 10px;
}

.kitcard {
  display: flex;
  flex-direction: column;
  min-width: 0;
  border: 1px solid var(--line-on-dark);
  border-radius: 14px;
  background: rgba(242, 237, 230, 0.04);
  transition: background var(--quick), border-color var(--quick);
}

.kitcard__body {
  position: relative;
  display: flex;
  flex: 1;
  flex-direction: column;
  gap: 6px;
  min-height: 44px;
  padding: 14px 16px;
  color: rgba(242, 237, 230, 0.78);
  cursor: pointer;
}

/* The radio is the card's state for the keyboard and a screen reader, and
   the card is what is seen — styled from the input, as a chip is. */
.kitcard__body input {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: 0;
  opacity: 0;
}

.kitcard:has(input:checked) {
  border-color: rgba(255, 216, 151, 0.55);
  background: rgba(255, 216, 151, 0.16);
}

.kitcard:has(input:focus-visible) {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

.kitcard--over {
  opacity: 0.45;
}

.kitcard--over .kitcard__body {
  cursor: not-allowed;
}

.kitcard__bar {
  display: flex;
  gap: 10px;
  align-items: baseline;
}

.kitcard__tag {
  font-size: 10px;
  font-weight: 700;
  letter-spacing: 0.16em;
  color: var(--paper-soft);
}

.kitcard__name {
  font-weight: 700;
  font-size: 16px;
  color: var(--paper);
}

.kitcard:has(input:checked) .kitcard__name,
.kitcard:has(input:checked) .kitcard__mark {
  color: var(--gold);
}

.kitcard__claim {
  font-weight: 700;
  font-size: 12.5px;
}

.kitcard__suits,
.kitcard__blurb {
  font-size: 12.5px;
  line-height: 1.5;
  color: var(--paper-soft);
}

.kitcard__mark {
  font-size: 10px;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--paper-soft);
}

.kitcard__list {
  display: flex;
  align-items: center;
  min-height: 44px;
  padding: 0 16px;
  border-top: 1px solid var(--line-on-dark);
  font-size: 12.5px;
  color: var(--paper-soft);
}

.kitcard__list:hover {
  color: var(--paper);
}

.kitcards__passion {
  display: flex;
  flex-wrap: wrap;
  gap: 12px;
  align-items: center;
  margin: 14px 0 0;
  font-weight: 700;
  font-size: 13px;
}

.kitcards__contact {
  display: inline-flex;
  align-items: center;
  min-height: 44px;
  padding: 0 17px;
  border: 1px solid var(--line-on-dark);
  border-radius: var(--radius-pill);
  color: var(--paper);
}

.kitcards__contact:hover {
  border-color: var(--gold);
}

/* "Not sure" (26f-4): the fourth tile, dashed — a question, not a kit — and
   the kit guide it opens under the cards. */
.kitcard--unsure {
  align-items: center;
  justify-content: center;
  gap: 6px;
  min-height: 120px;
  padding: 16px;
  border-style: dashed;
  border-color: rgba(242, 237, 230, 0.22);
  background: transparent;
  color: var(--paper);
  font: inherit;
  cursor: pointer;
}

.kitcard--unsure[aria-expanded="true"] {
  border-color: rgba(255, 216, 151, 0.7);
}

.kitcard--unsure:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

.kitcard__question {
  display: grid;
  place-items: center;
  width: 32px;
  height: 32px;
  border: 1px solid var(--line-on-dark);
  border-radius: 50%;
  font-weight: 700;
}

.kitcard__unsure {
  font-weight: 700;
  font-size: 16px;
}

.kitcard__count {
  font-size: 12.5px;
  color: var(--paper-soft);
}

.kitguide {
  display: grid;
  gap: 16px;
  margin-top: 14px;
  padding: 18px;
  border: 1px solid var(--line-on-dark);
  border-radius: 14px;
}

.kitguide__eyebrow {
  margin: 0;
  font-size: 10px;
  font-weight: 700;
  letter-spacing: 0.22em;
  text-transform: uppercase;
  color: var(--gold);
}

.kitguide__title {
  margin: 0;
  font-weight: 700;
  font-size: 13px;
}

.kitguide__result {
  display: flex;
  flex-wrap: wrap;
  gap: 12px;
  align-items: center;
  padding-top: 14px;
  border-top: 1px solid var(--line-on-dark);
}

.kitguide__said {
  flex-basis: 100%;
  margin: 0;
  font-weight: 700;
}

.kitguide__pick,
.kitguide__kit {
  display: inline-flex;
  align-items: center;
  min-height: 44px;
  padding: 0 20px;
  border-radius: var(--radius-pill);
  font: inherit;
  font-weight: 700;
  font-size: 12px;
  cursor: pointer;
}

.kitguide__pick {
  border: 0;
  background: var(--gold);
  color: var(--ink);
}

.kitguide__kit {
  border: 1px solid var(--line-on-dark);
  color: var(--paper);
}

/* The picked kit's add-ons (26f-5): a row each — name and "from" price,
   the brief's stepper beside them; under one another on a phone. */
.kitaddons {
  margin-top: 16px;
}

.kitaddons__title {
  margin: 0;
  font-weight: 700;
  font-size: 13px;
}

.kitaddons__list {
  display: grid;
  gap: 10px;
  margin: 12px 0 0;
  padding: 0;
  list-style: none;
}

.kitaddons__row {
  display: grid;
  grid-template-columns: minmax(0, 1fr) auto;
  grid-template-areas:
    "name stepper"
    "price stepper";
  align-items: center;
  gap: 2px 16px;
  padding: 10px 0;
  border-top: 1px solid var(--line-on-dark);
}

.kitaddons__name {
  grid-area: name;
  font-weight: 700;
  font-size: 13px;
}

.kitaddons__price {
  grid-area: price;
  font-size: 12.5px;
  color: var(--paper-soft);
}

.kitaddons__row > .brief-stepper {
  grid-area: stepper;
}

/* The hire brief v2 without JavaScript (26j): today's brief classes, and
   these few for what only the plain form draws. A fieldset that groups
   boxes inside a question carries no frame of its own — the browser's
   default border read as a second panel. */
.briefplain__dates,
.briefplain__addons {
  border: 0;
  margin: 12px 0 0;
  padding: 0;
  min-width: 0;
}

.briefplain__dates {
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
}

.briefplain__dates legend {
  margin-bottom: 8px;
}

.briefplain__kit {
  margin-bottom: 16px;
}

.briefplain__pair {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(180px, 1fr));
  gap: 12px;
}

/* A box under a row of chips — "If Something else: describe it", Date,
   City or region — had nothing between them (the owner's word,
   15-11-2026). Close to the 14px above the chips, so the two read alike. */
.briefplain .brief__options + .field,
.briefplain .brief__options + .briefplain__pair {
  margin-top: 16px;
}

.briefplain .briefsteps__send {
  margin-top: 20px;
}

.briefplain__change {
  margin-left: auto;
}

.briefplain__addon {
  margin-top: 12px;
}

.briefplain__addon input {
  max-width: 8rem;
}

/* ---- The Availability calendar — Module 27d, design_handoff_availability ----

   A plugin's card under the Hire pill on Sound Recording (the page's
   `service_hero_aside` slot). Drawn by the server as a working form; the
   island (27d-2) mounts over it.

   **The handoff's values, with one change for the hand.** Its card has 18px
   of padding and 5px between days, which leaves a 360px column 42px a day.
   The site's minimum to press is 44, so the padding is 14 and the gap 3:
   44.9px a day on desktop. On a 390px phone the column is 350 (20px
   gutters), which left 43.1 — measured — so there the padding is 10:
   44.3px a day. */

.availcal {
  --avail-open: #34c77b;
  --avail-maybe: #e8a54b;
  --avail-closed: #e8735b;
  position: relative;
  display: flex;
  flex-direction: column;
  gap: 16px;
  margin-top: 16px;
  padding: 14px;
  border: 1px solid rgba(242, 237, 230, 0.14);
  border-radius: 16px;
  background: rgba(255, 255, 255, 0.03);
}

.availcal__head {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 12px;
}

.availcal__title {
  margin: 0;
  color: rgba(242, 237, 230, 0.42);
  font-size: 9px;
  font-weight: 700;
  letter-spacing: 0.2em;
  text-transform: uppercase;
}

.availcal__status {
  display: flex;
  align-items: center;
  gap: 7px;
  margin: 0;
  color: var(--paper);
  font-size: 12.5px;
  font-weight: 600;
}

.availcal__dot {
  width: 8px;
  height: 8px;
  border-radius: 999px;
  background: var(--avail-open);
}

.availcal__dot--busy {
  background: var(--avail-maybe);
}

.availcal__dot--off {
  background: rgba(242, 237, 230, 0.4);
}

.availcal__problem {
  margin: 0;
  color: var(--avail-closed);
  font-size: 12.5px;
  font-weight: 600;
}

.availcal__week {
  margin: 0;
  padding: 0;
  border: 0;
  min-width: 0;
}

.availcal__range {
  margin-bottom: 8px;
  padding: 0;
  color: var(--paper-soft);
  font-size: 12px;
  font-weight: 600;
}

.availcal__days {
  display: grid;
  grid-template-columns: repeat(7, minmax(0, 1fr));
  gap: 3px;
}

.availcal__day {
  position: relative;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 6px;
  min-height: 44px;
  padding: 10px 0 11px;
  border: 1px solid transparent;
  border-radius: 10px;
}

.availcal__weekday {
  font-size: 8.5px;
  font-weight: 700;
  letter-spacing: 0.08em;
  text-transform: uppercase;
}

.availcal__number {
  font-size: 15px;
  font-weight: 800;
}

.availcal__day--available {
  background: rgba(52, 199, 123, 0.12);
  color: var(--avail-open);
}

.availcal__day--uncertain {
  background: rgba(232, 165, 75, 0.12);
  color: var(--avail-maybe);
}

.availcal__day--unavailable {
  background: rgba(232, 115, 91, 0.1);
  color: var(--avail-closed);
}

.availcal__day--today {
  border-color: rgba(242, 237, 230, 0.5);
}

.availcal__day--past {
  opacity: 0.3;
}

/* A pickable day is a label around its checkbox: the box itself is out of
   sight but not out of reach, so a keyboard still lands on it and the
   label shows where. */
label.availcal__day {
  cursor: pointer;
}

.availcal__pick {
  position: absolute;
  inset: 0;
  margin: 0;
  opacity: 0;
  cursor: pointer;
}

.availcal__day:has(.availcal__pick:checked) {
  background: var(--avail-open);
  border-color: var(--avail-open);
  color: var(--dark);
}

.availcal__day:has(.availcal__pick:focus-visible) {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

.availcal__legend {
  display: flex;
  flex-wrap: wrap;
  gap: 14px;
  margin: 0;
  padding: 0;
  list-style: none;
  color: var(--paper-soft);
  font-size: 11px;
}

.availcal__key {
  display: flex;
  align-items: center;
  gap: 6px;
}

.availcal__key::before {
  content: "";
  width: 8px;
  height: 8px;
  border-radius: 3px;
}

.availcal__key--available::before {
  background: var(--avail-open);
}

.availcal__key--uncertain::before {
  background: var(--avail-maybe);
}

.availcal__key--unavailable::before {
  background: var(--avail-closed);
}

.availcal__hire {
  min-height: 44px;
  padding: 13px 18px;
  border: 0;
  border-radius: 999px;
  background: var(--gold);
  color: var(--dark);
  font: inherit;
  font-size: 10.5px;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  cursor: pointer;
}

.availcal__hire:hover,
.availcal__hire:focus-visible {
  background: #ffffff;
}

/* The trap, as the brief's: off-screen rather than `display: none`. */
.availcal__trap {
  position: absolute;
  left: -9999px;
  width: 1px;
  height: 1px;
  overflow: hidden;
}

/* Inactive: the whole card greyed and still, its pill saying why. The
   plain form's weeks and the island's single week (its nav and days) alike
   — the island has no week wrapper, which the UI check found. */
.availcal--inactive .availcal__week,
.availcal--inactive .availcal__nav,
.availcal--inactive .availcal__days,
.availcal--inactive .availcal__legend {
  filter: grayscale(1);
  opacity: 0.4;
}

.availcal__pill {
  align-self: center;
  margin: 0;
  padding: 9px 16px;
  border: 1px solid rgba(242, 237, 230, 0.2);
  border-radius: 999px;
  background: rgba(14, 13, 11, 0.7);
  color: var(--paper);
  font-size: 12.5px;
  font-weight: 700;
}

@media (max-width: 720px) {
  .availcal {
    padding: 10px;
  }
}

/* ---- The calendar's island (27d-2) ----

   The same card, one week at a time. These rules are here rather than in an
   island stylesheet because the card is one design drawn two ways; the
   classes below appear only when the island has mounted. */

.availcal__nav {
  display: flex;
  align-items: center;
  justify-content: space-between;
}

.availcal--island .availcal__range {
  margin: 0;
}

/* The handoff's 30px round arrow, inside a 44px press. */
.availcal__arrow {
  display: grid;
  place-items: center;
  width: 44px;
  height: 44px;
  padding: 0;
  border: 0;
  background: none;
  color: var(--paper);
  font: inherit;
  cursor: pointer;
}

.availcal__arrow span {
  display: grid;
  place-items: center;
  width: 30px;
  height: 30px;
  border: 1px solid rgba(242, 237, 230, 0.2);
  border-radius: 999px;
  font-size: 16px;
  font-weight: 700;
  line-height: 1;
}

.availcal__arrow[aria-disabled="true"] {
  color: rgba(242, 237, 230, 0.2);
  cursor: default;
}

.availcal__arrow[aria-disabled="true"] span {
  border-color: rgba(242, 237, 230, 0.08);
}

.availcal__arrow:focus-visible span {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

/* A day the island draws as a button wears the card's day, not a button's. */
button.availcal__day {
  width: 100%;
  font: inherit;
  cursor: pointer;
}

button.availcal__day:focus-visible {
  outline: 2px solid var(--gold);
  outline-offset: 2px;
}

.availcal__day--picked {
  background: var(--avail-open);
  border-color: var(--avail-open);
  color: var(--dark);
}

/* Hire before a day is picked: the handoff's dim pill. */
.availcal__hire[aria-disabled="true"] {
  background: rgba(242, 237, 230, 0.06);
  color: rgba(242, 237, 230, 0.35);
  cursor: not-allowed;
}

/* ---- Days held for the brief (27e-2), design_handoff_availability §4 ----

   The countdown at the top of the brief while the calendar holds its days:
   the contact bar's glass, a green edge that turns yellow at 20 seconds and
   red at 10. Sticky at the top of the brief rather than fixed to the
   bottom, where a phone's own bars sit. On a phone the site's header stays
   (69px), so the bar sits the handoff's 8px beneath it — to be tuned on a
   real phone, as the contact bar was. */

.heldbar {
  position: sticky;
  top: 12px;
  z-index: 40;
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 14px;
  margin-bottom: 16px;
  padding: 12px 16px;
  border: 1px solid #34c77b;
  border-radius: 18px;
  background: rgba(14, 13, 11, 0.5);
  backdrop-filter: blur(14px);
  -webkit-backdrop-filter: blur(14px);
  box-shadow: 0 18px 44px rgba(0, 0, 0, 0.45);
  color: var(--paper);
}

@media (max-width: 900px) {
  .heldbar {
    top: 77px;
  }
}

.heldbar__words {
  margin: 0;
  font-size: 13px;
  font-weight: 600;
}

.heldbar__keep {
  display: block;
  margin-top: 3px;
  color: var(--paper-soft);
  font-size: 12px;
  font-weight: 500;
}

.heldbar__clock {
  margin: 0;
  color: #34c77b;
  font-size: 18px;
  font-weight: 800;
  font-variant-numeric: tabular-nums;
}

.heldbar--warn {
  border-color: #e8c14b;
}

.heldbar--warn .heldbar__clock {
  color: #e8c14b;
}

.heldbar--last {
  border-color: #e8735b;
}

.heldbar--last .heldbar__clock {
  color: #e8735b;
}

.heldbar--over {
  border-color: rgba(242, 237, 230, 0.2);
}

/* Over, the bar counts its own thirty seconds beside Pick again, then goes
   (03-11-2026). Plain: the hold's yellow and red are for the hold. */
.heldbar__end {
  display: flex;
  align-items: center;
  gap: 14px;
  flex: none;
}

.heldbar--over .heldbar__clock {
  color: var(--paper-soft);
}

.heldbar__again {
  display: inline-flex;
  align-items: center;
  min-height: 44px;
  padding: 0 18px;
  border-radius: 999px;
  background: var(--gold);
  color: var(--dark);
  font-size: 10.5px;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  text-decoration: none;
  white-space: nowrap;
}

/* Under When: a held day the brief no longer names, "free again". */
.heldhint {
  margin: 10px 0 0;
  padding: 0;
  list-style: none;
  color: #e8a54b;
  font-size: 12.5px;
  font-weight: 600;
}

.heldhint li + li {
  margin-top: 4px;
}
