/* ==========================================================================
   ACME CO — styles.css

   Design language: the document.
   Borrowed from the split sheet CatalogTracker itself generates —
   a mono numeral, a tracked-caps label, and a hairline running to the margin.

   - One ground. No cards, no fills, no shadows, no alternating bands.
   - The hairline is the only structural device. The section rubric IS the
     divider, so one line does the work of a rule, a number, and a heading.
   - Mono carries the document's apparatus — section numerals and their labels,
     figure numerals and captions, dates. Sans carries everything read as
     language: headings, copy, product names, actions.
   - The page is monochrome. The screenshots are the only colour in the
     content; accent blue means "you can act on this" and nothing else.

   Ordering convention: Tokens → Reset → Base → Layout → Components → Sections
   Every spacing value is a token; every token is a multiple of 8.
   ========================================================================== */

/* --------------------------------------------------------------------------
   Tokens
   -------------------------------------------------------------------------- */

:root {
  /* Spacing — 8-point grid, authored in rem so it is a grid of POINTS and
     not of pixels (2026-08-19).

     A point is 0.125rem. At the browser's default that is the same 8px this
     scale has always been, so nothing moves for a reader who has changed
     nothing — verified: check-layout measures identical geometry either way.
     What changes is the reader who has set their browser text larger, which
     is the web's Dynamic Type. In px they got bigger type crammed into gaps
     that stayed put; in rem the whole system scales with them and the design
     holds its proportions at every text size, at every width.

     Nothing here sets a root font-size, and that is the other half of it:
     the `62.5%` trick makes `1rem` a round `10px` and takes the reader's
     setting away to do it. `check_layout_test.py` fails if one ever appears.

     Touch targets are the deliberate exception and stay in px — 44pt is a
     finger, not a font, and HIG sizes it against the hand. `--header-h`
     below, and design.md's own note beside it. */
  --space-1: 0.5rem;    /* 8pt  */
  --space-2: 1rem;      /* 16pt */
  --space-3: 1.5rem;    /* 24pt */
  --space-4: 2rem;      /* 32pt */
  --space-6: 3rem;      /* 48pt */
  --space-8: 4rem;      /* 64pt */
  --space-12: 6rem;     /* 96pt */
  --space-16: 8rem;     /* 128pt */

  /* Type. -apple-system resolves to SF Pro with optical sizing on Apple
     platforms; Inter is the cross-platform stand-in where it is installed.
     The mono is its sibling — SF Mono on Apple — and is used for numerals
     only, which is what earns a second face on a one-typeface site. */
  --font-sans: -apple-system, BlinkMacSystemFont, "SF Pro Display", "SF Pro Text",
    "Inter", "Segoe UI", Roboto, "Helvetica Neue", Helvetica, Arial, sans-serif;
  --font-mono: ui-monospace, SFMono-Regular, "SF Mono", Menlo, Consolas,
    "Liberation Mono", monospace;

  --text-display: clamp(2.25rem, 1.05rem + 5.1vw, 4.5rem);
  --text-title: clamp(1.75rem, 1.16rem + 2.5vw, 3rem);
  --text-subtitle: clamp(1.5rem, 1.14rem + 1.55vw, 2.25rem);
  --text-lead: clamp(1.1875rem, 1.06rem + 0.55vw, 1.5rem);
  --text-body: 1.0625rem;
  --text-small: 0.9375rem;
  --text-micro: 0.8125rem;

  /* Motion */
  --ease: cubic-bezier(0.4, 0, 0.2, 1);
  --ease-out: cubic-bezier(0.16, 1, 0.3, 1);
  --duration-fast: 150ms;
  --duration: 250ms;

  /* Layout */
  --container: 61.25rem; /* 980px */
  --measure: 36rem;      /* ~55 characters at lead size */
  --gutter: clamp(1.5rem, 5vw, 2.5rem);   /* 24pt … 40pt */
  --radius-pill: 980px;
  /* One app frame. A token rather than a component value because the row needs
     it to compute its own padding, and a width declared on the frame cannot
     reach the scroller that has to centre it. Each frame ships as a 600px/1200px
     srcset pair, so at the 300px ceiling a 2x display draws the 600 exactly and
     a 3x display draws the 1200 — a lone 600 upscaled 1.5x on every 3x phone,
     which read as blur. The `sizes` attribute on all sixteen frame imgs (both
     editions) recites this token's two formulas verbatim; change one here and
     the recitals must move with it. */
  --shot-w: clamp(200px, 25vw, 300px);
  /* HIG touch minimum; design.md exempts targets from the grid. **In px on
     purpose**, and it is the one place the rem scale stops: 44pt is the size
     of a fingertip, which does not change when a reader changes their text
     size. Scaling it would grow every control on a page whose reader asked
     for larger words, not larger buttons. */
  --header-h: 44px;

  /* Where the container's content edge falls, for full-bleed rows that still
     need to line up with it. Resolves against the element that uses it. */
  --edge: max(var(--gutter), calc((100% - var(--container)) / 2 + var(--gutter)));
}

/* Light is the default and the no-JS baseline. */
:root,
:root[data-scheme="light"] {
  color-scheme: light;

  --bg: #ffffff;
  --fg: #1d1d1f;
  --fg-secondary: #6e6e73;
  --accent: #0071e3;      /* selection tint */
  --accent-ink: #0066cc;  /* interaction: link text and focus */
  --separator: rgba(0, 0, 0, 0.12);
  --header-bg: rgba(255, 255, 255, 0.72);
}

:root[data-scheme="dark"] {
  color-scheme: dark;

  --bg: #000000;
  --fg: #f5f5f7;
  --fg-secondary: #a1a1a6;
  --accent: #0071e3;
  --accent-ink: #2997ff;
  --separator: rgba(255, 255, 255, 0.16);
  --header-bg: rgba(0, 0, 0, 0.72);
}

/* Without JavaScript there is no data-scheme, so fall back to the OS. */
@media (prefers-color-scheme: dark) {
  :root:not([data-scheme]) {
    color-scheme: dark;

    --bg: #000000;
    --fg: #f5f5f7;
    --fg-secondary: #a1a1a6;
    --accent: #0071e3;
    --accent-ink: #2997ff;
    --separator: rgba(255, 255, 255, 0.16);
    --header-bg: rgba(0, 0, 0, 0.72);
  }
}

/* --------------------------------------------------------------------------
   Reset
   -------------------------------------------------------------------------- */

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

* { margin: 0; }

/* --------------------------------------------------------------------------
   Base
   -------------------------------------------------------------------------- */

html {
  /* Anchored jumps have to clear the sticky bar, not slide under it. */
  scroll-padding-top: calc(var(--header-h) + var(--space-4));
  -webkit-text-size-adjust: 100%;
}

@media (prefers-reduced-motion: no-preference) {
  html { scroll-behavior: smooth; }

  /* One document to the next is a cross-fade, not a cut. Every page opts in,
     so the waitlist form's submit — a 303 to the sent page — arrives the way
     a tap on a link does, and so does every other same-origin navigation.
     No script: the browser draws it from the two documents (the CSS View
     Transitions spec names a form submission as a qualifying navigation).
     Engines without it show the cut they always did. Inside the no-preference
     query on purpose: for reduce, the at-rule is never declared, which is
     "reduce, never remove" applied at the source rather than patched below. */
  @view-transition { navigation: auto; }

  /* Slightly longer than a hover, with the site's settle curve, so the change
     of page is seen as one — a plain 250ms cross-fade of a dark page was read
     as a cut (2026-09-18).

     The header carries no view-transition-name, and must not. It held one for
     two days: named so it would "hold still" while the document under it
     faded. It already does. The two root snapshots cross-fade inside an
     isolated image pair with plus-lighter blending — the spec's own
     stylesheet, there so that identical pixels come out identical at every
     step — and the chips are the same pixels on both pages. A name buys
     nothing there and costs the glass: a named element is captured as an
     isolated group, which makes it a backdrop root, so the chips'
     backdrop-filter could see only the header's own empty padding and blurred
     nothing, on every page, whenever the visitor had scrolled (measured
     2026-09-20 in Chrome 152: crisp text under the capsule, blurred the
     moment the name was removed and the box rebuilt). Where the chips do
     differ between pages — the back chip arriving, a scrolled capsule leaving
     for a page at the top — the fade is the honest rendering, and only the
     un-named path shows the old document softening into the new one inside
     the glass; a captured group is flat for the whole 400ms. */
  ::view-transition-old(root),
  ::view-transition-new(root) {
    animation-duration: 400ms;
    animation-timing-function: var(--ease-out);
  }
}

body {
  background: var(--bg);
  color: var(--fg);
  font-family: var(--font-sans);
  font-size: var(--text-body);
  line-height: 1.6;
  font-optical-sizing: auto;
  -webkit-font-smoothing: antialiased;
  -moz-osx-font-smoothing: grayscale;
  transition: background-color var(--duration) var(--ease),
              color var(--duration) var(--ease);
}

h1, h3 {
  font-weight: 600;
  letter-spacing: -0.02em;
  line-height: 1.08;
  text-wrap: balance;
}

p { text-wrap: pretty; }

a {
  color: var(--accent-ink);
  text-underline-offset: 3px;
  transition: color var(--duration-fast) var(--ease);
}

:focus-visible {
  outline: 2px solid var(--accent-ink);
  outline-offset: 3px;
}

::selection {
  background: color-mix(in srgb, var(--accent) 22%, transparent);
}

svg { display: block; }

/* --------------------------------------------------------------------------
   Layout
   -------------------------------------------------------------------------- */

.container {
  width: 100%;
  max-width: var(--container);
  margin-inline: auto;
  padding-inline: var(--gutter);
}

/* Every horizontal scroller on the site, stated once (2026-08-15, owner's
   ruling: nothing that scrolls sideways may have the page's background cut
   in beside it).

   Two things are true of a row that scrolls, and one declaration block is
   what keeps them true together:

   - **It runs to the page's edges.** A scroller inset by the gutter shows a
     band of ground down each side, and the clipped edge — the only
     affordance a scroller without a scrollbar has — lands in the middle of
     the page instead of at the edge of the screen. It reads as a window cut
     into the page rather than as content continuing past it.
   - **At rest it lines up with the prose.** `--edge` is the token for
     exactly this: it resolves to wherever the container's content edge
     falls for the element that asks, so the first cell of a table sits on
     the same left edge as the paragraph above it, and `scroll-padding`
     keeps that edge honoured when a snap or a focus scrolls the row.

   The walkthrough row already worked this way and is the precedent; it sits
   OUTSIDE `.container` and so is page-width already. The other two sit
   inside it and cancel its gutter to get there. The cancel is a negative
   margin against the container's own inset — never `100vw`, which is wider
   than the viewport by the width of a classic scrollbar and would push the
   page sideways, the one thing design.md forbids outright. */
.shots-row,
ul.related-row,
.article .container > .table-scroll {
  padding-inline: var(--edge);
  scroll-padding-inline: var(--edge);
}

/* The scope row on /writing bleeds the same way, on its sticky wrapper
   rather than on the list (`.scopes`, below), and is inset in its own block:
   its chips are capsules, and it is the LABEL inside the first capsule that
   lands on the prose edge, not the capsule's ring. */
ul.related-row,
.article .container > .table-scroll {
  margin-inline: calc(-1 * var(--gutter));
}

/* Tighter than the banded version was. A ruled rubric is a strong divider, and
   a strong divider needs less air around it than a change of background did. */
.section { padding-block: var(--space-8); }

/* A run of short numbered clauses. The rubric already puts 48px between its
   rule and its text, so 48px a side keeps the gap between clauses exactly
   double the gap inside one — proximity doing the grouping. */
.section--clause { padding-block: var(--space-6); }

.lead {
  max-width: var(--measure);
  font-size: var(--text-lead);
  line-height: 1.45;
  color: var(--fg-secondary);
  letter-spacing: -0.01em;
}

.kicker {
  color: var(--fg-secondary);
  font-size: var(--text-small);
}

/* Body prose. Held to the measure so a clause stays inside 60–75 characters
   however wide the window gets. */
.prose {
  max-width: var(--measure);
  color: var(--fg);
}

.prose + .prose { margin-top: var(--space-2); }

/* The product page's FAQ. Every rule that shapes the site's other FAQ is
   scoped under `.article`, which only a writing piece carries — so the same
   `h3`/`p` markup on /catalogtracker drew nothing at all: no measure, no
   colour, no rhythm, headings at the browser's default size. A 320px render
   is what showed it; no law here would have, because an unstyled paragraph
   does not overflow, overlap or under-size a tap target. It is only wrong to
   look at.

   The values are `.article`'s, named rather than matched by eye, so the two
   FAQs stay one thing and a change to the measure moves both. */
.faq h3 {
  max-width: var(--measure);
  margin-top: var(--space-4);
  font-size: var(--text-lead);
}

.faq p {
  max-width: var(--measure);
  margin-top: var(--space-2);
  color: var(--fg);
}

.visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
}

/* --------------------------------------------------------------------------
   The rubric — number, label, rule. Taken from the generated split sheet.
   It is the section heading and the section divider at the same time.
   -------------------------------------------------------------------------- */

.rubric {
  display: flex;
  align-items: center;
  gap: var(--space-3);
  margin-bottom: var(--space-6);
  color: var(--fg);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  font-weight: 500;
  /* Lighter than the 0.1em the sans wanted — mono is already wide, and caps
     at full tracking came apart into loose letters. */
  letter-spacing: 0.06em;
  line-height: 1;
  text-transform: uppercase;
}

.rubric::after {
  content: "";
  flex: 1;
  height: 1px;
  background: var(--separator);
  transition: background-color var(--duration) var(--ease);
}

/* No scroll-triggered reveal here on purpose. Hiding structural text until a
   script reveals it means a failed observer costs you the content, and
   design.md is explicit that nothing should move without the visitor causing
   it. Motion on this page is input-driven or it reports state; never both
   absent. */

/* Figures read better untracked than the letters beside them. */
.rubric-index {
  color: var(--fg-secondary);
  letter-spacing: 0;
}

/* --------------------------------------------------------------------------
   Components
   -------------------------------------------------------------------------- */

/* No shadow at rest: its blur would bleed back onto the page from off-screen. */
.skip-link {
  position: absolute;
  top: var(--space-1);
  left: var(--space-1);
  z-index: 10;
  padding: var(--space-1) var(--space-2);
  background: var(--bg);
  border: 1px solid var(--separator);
  border-radius: 8px;
  transform: translateY(calc(-100% - var(--space-4)));
}

.skip-link:focus-visible { transform: none; }

/* The interactive device for navigation. Large text, hairline underline, no
   fill — a pill was the last piece of borrowed web-UI chrome until the owner
   drew one line through that (2026-09-18): a control that COLLECTS is a
   filled .button, and this stays the shape of everything that merely goes
   somewhere. */
.action {
  display: inline-block;
  padding-block: var(--space-1);
  color: var(--fg);
  font-size: var(--text-subtitle);
  font-weight: 600;
  /* Display line-height: at 1.6 the line box left ~25px of dead space under
     the text, so the gap to the next rubric measured larger than it was. */
  line-height: 1.2;
  letter-spacing: -0.02em;
  text-decoration-line: underline;
  text-decoration-thickness: 1px;
  text-decoration-color: var(--separator);
  text-underline-offset: 8px;
  transition: text-decoration-color var(--duration) var(--ease);
}

.action:hover {
  color: var(--fg);
  text-decoration-color: currentColor;
}

.action .arrow {
  display: inline-block;
  transition: transform var(--duration) var(--ease-out);
}

.action:hover .arrow { transform: translateX(4px); }

/* Quiet link — the one sanctioned exception to "accent means interactive".
   It reads as the sentence it sits in until someone reaches for it, then
   commits. The hairline underline is present at rest, so the affordance is
   never carried by colour alone. :active covers touch, where hover cannot. */
.link-quiet {
  color: inherit;
  text-decoration-line: underline;
  text-decoration-thickness: 1px;
  /* Mixed from the inherited colour so the resting underline stays legible
     whatever text it sits in — grey colophon or full-strength prose. */
  text-decoration-color: color-mix(in srgb, currentColor 35%, transparent);
  text-underline-offset: 4px;
  transition: color var(--duration-fast) var(--ease),
              text-decoration-color var(--duration-fast) var(--ease),
              text-decoration-thickness var(--duration-fast) var(--ease);
}

/* Reached for: the accent arrives and the rule thickens. Two cues, so the
   change never depends on colour alone. :active covers touch, where there is
   no hover to rely on. */
.link-quiet:hover,
.link-quiet:focus-visible,
.link-quiet:active {
  color: var(--accent-ink);
  text-decoration-color: currentColor;
  text-decoration-thickness: 2px;
}

/* --------------------------------------------------------------------------
   Nav — sticky, translucent, blurred. The bar and its hairline run the full
   viewport width rather than the container: it is chrome sitting above the
   document, not part of the document's own ruled structure.
   -------------------------------------------------------------------------- */

/* The bar does not span the viewport. It is two floating chips — a wordmark
   capsule and a detached round control — which is the shape CatalogTracker's own
   tab bar uses. Borrowed from the product for the same reason the rubric was.
   The strip itself is inert so it cannot swallow clicks on the content it
   floats over; only the chips take pointer events. */
.site-header {
  position: sticky;
  top: 0;
  z-index: 5;
  padding-block: var(--space-2);
  pointer-events: none;
}

/* Three tracks, and the outer two are equal by construction — that is what
   puts the middle one on the true centre of the viewport. Flex cannot do
   this: space-between or justify-content: center would centre the wordmark
   in whatever the toggle leaves over, which is the centre of nothing. Equal
   tracks hold regardless of what flanks them, including the no-JS case where
   the toggle is display:none and not a grid item at all.

   minmax(0, 1fr), never a bare 1fr — this is the whole of it. A bare 1fr
   floors at min-content, so at 320px the trailing track was propped open by
   the toggle while the leading track collapsed, the tracks stopped being
   equal, and the mark sat 17.5px left of centre. Measured, not theorised,
   and invisible at every width above it. An explicit 0 minimum makes the
   tracks equal at every viewport and lets the toggle overflow its track,
   which its negative margin already had it doing.

   No gap. The mark is centred by construction and the toggle is pinned to
   the content edge, so a gap moves neither — it only shrinks the spacer
   tracks it sits between. Verified byte-identical geometry with and
   without, so it is not here. */
.header-inner {
  display: grid;
  grid-template-columns: minmax(0, 1fr) auto minmax(0, 1fr);
  align-items: center;
  min-height: var(--header-h);
}

/* Nothing until content is underneath, the way a UINavigationBar carries no
   chrome at rest. Same threshold that used to drive the separator, so this
   needed no new script — and with JavaScript off the chips simply stay plain. */
.back,
.lang,
.wordmark,
.appearance {
  pointer-events: auto;
  border: 1px solid transparent;
  transition: background-color var(--duration) var(--ease),
              border-color var(--duration) var(--ease),
              color var(--duration-fast) var(--ease);
}

:root:not(.is-top) .back,
:root:not(.is-top) .lang,
:root:not(.is-top) .wordmark,
:root:not(.is-top) .appearance {
  background: var(--header-bg);
  border-color: var(--separator);
  -webkit-backdrop-filter: saturate(180%) blur(20px);
  backdrop-filter: saturate(180%) blur(20px);
}

/* Without backdrop-filter the translucency reads as washed-out text. */
@supports not ((backdrop-filter: blur(1px)) or (-webkit-backdrop-filter: blur(1px))) {
  :root:not(.is-top) .back,
  :root:not(.is-top) .lang,
  :root:not(.is-top) .wordmark,
  :root:not(.is-top) .appearance { background: var(--bg); }
}

@media (prefers-reduced-transparency: reduce) {
  :root:not(.is-top) .back,
  :root:not(.is-top) .lang,
  :root:not(.is-top) .wordmark,
  :root:not(.is-top) .appearance {
    background: var(--bg);
    -webkit-backdrop-filter: none;
    backdrop-filter: none;
  }
}

/* Leading track, article pages only. The back chip is the appearance control
   mirrored: same circle, same overhang, so the chevron lands on the content
   edge and the strip reads as a UINavigationBar in full — back leading,
   title centred, one control trailing. An <a> to /writing, not a history
   button: a reader who arrived from a search result has no history to go
   back through, and those readers are exactly who the chip exists for.
   The index does not carry it — it is the place the chip goes. */
.back {
  grid-column: 1;
  justify-self: start;
  display: grid;
  place-items: center;
  width: var(--header-h);
  height: var(--header-h);
  /* Mirror of the appearance control's overhang, for the same two reasons:
     the icon on the content edge, and real space beside the capsule at 320px. */
  margin-left: calc(var(--space-2) * -1);
  border-radius: 50%;
  color: var(--fg-secondary);
}

.back:hover { color: var(--fg); }

/* Leading track, pages with a translation only — the same slot the back chip
   holds on article pages, so the nav stays a UINavigationBar: at most one
   leading chip, the title centred, one control trailing. A capsule rather
   than a circle because the label is text; mono tracked caps because a
   language code is apparatus, like a rubric label. Set in the language it
   offers — the reader it exists for is the one who cannot read the rest of
   the page.

   Padding and overhang are a half-step, not the wordmark's full step, and
   they cancel by construction: -8px margin plus 8px padding lands the label
   on the content edge at every width, whatever the label says. The full-step
   pair aligned identically but made the capsule 16px wider, and at 320px
   that left 5.7px to the wordmark — the ~5px gap the appearance control's
   own overhang exists to avoid. At the half-step, ESP is a 44px capsule (the
   footprint every other chip has), EN rests on the min-width, and the gap at
   320px is back to ~14px. Measured, not theorised.

   Centred, because flex-start let EN hug the left of its min-width capsule
   with 9px of dead space trailing — invisible until the ring materialised,
   then plainly off-centre. Every other chip centres its content; this one is
   no exception. The cost is that EN's label sits ~5px right of the content
   edge, measured, varying with each platform's mono — ESP fills its capsule
   and still lands exactly. The trade is right because the nav is already
   exempt from the document's edge (design.md), while a lopsided capsule is
   visibly wrong every time the ring materialises. */
.lang {
  grid-column: 1;
  justify-self: start;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: var(--space-1); /* the grid's own icon-to-label interval */
  min-width: var(--header-h);
  min-height: var(--header-h);
  padding-inline: var(--space-1);
  margin-left: calc(var(--space-1) * -1);
  border-radius: var(--radius-pill);
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  font-weight: 500;
  letter-spacing: 0.06em;
  text-decoration: none;
}

.lang:hover { color: var(--fg); }

/* The globe rides with the label — Apple's own glyph for a language switch,
   drawn in the site's icon grammar rather than imported. It is affordance
   reinforcement; the label is the control. So when the wordmark needs the
   room, the globe yields first — the same priority a UINavigationBar applies
   when it drops items — and the chip returns to the 44px footprint whose
   geometry is already verified down to 320px. The threshold is measured,
   not theorised: with the globe the ESP chip's right edge sits at 83.8px,
   the centred wordmark is 173.1px wide, and the ~14px clearance the
   trailing side keeps is met from 369px up — so the globe yields at 368px
   and below, and iPhone-width viewports (375px) keep it. */
@media (max-width: 23rem) {
  .lang .icon { display: none; }
}

/* Centre track. The capsule's padding is symmetric, so centring the capsule
   centres the letters — no optical correction owed. The negative left margin
   this used to carry is gone with the left-edge alignment it existed to
   produce; reintroducing it would pull the mark off centre by exactly its
   own padding. */
.wordmark {
  grid-column: 2;
  display: inline-flex;
  align-items: center;
  min-height: var(--header-h);
  padding-inline: var(--space-2);
  border-radius: var(--radius-pill);
  color: var(--fg);
  font-size: var(--text-body);
  font-weight: 600;
  letter-spacing: -0.01em;
  text-decoration: none;
}

/* The wordmark is one unstyled text node on purpose. If part of it is ever
   given its own element — a mirrored letter, a coloured glyph, anything —
   note that .wordmark is inline-flex, so each surrounding text run becomes
   its own flex item and innerText comes back broken ("A\nC\nME CO") while
   textContent stays clean. A DOM parser never notices; rendered-text
   extraction, which is how much answer-engine scraping works, reads the
   brand name as separate words. Wrap the whole label in a single span if it
   comes to that, and check innerText, not just textContent. */

/* One toggle, two states. A three-state control could not avoid a dead tap:
   'auto' always resolves to the same scheme as light or dark depending on the
   hour, so one step of any cycle changed nothing on screen. Choosing a scheme
   now sets a temporary override that lapses at the next sunrise or sunset, so
   automatic resumes on its own and every tap flips what you see.

   Revealed only once the script has set data-scheme, since it does nothing
   without it. The icon shows the state you would move to, matching the label. */
.appearance { display: none; }

[data-scheme] .appearance {
  grid-column: 3;
  justify-self: end;
  display: grid;
  place-items: center;
  width: var(--header-h);
  height: var(--header-h);
  /* Kept from when the wordmark overhung the left: the circle overhangs the
     right gutter so the icon itself lands on the content edge. That is still
     right with a centred mark — it is the trailing control holding the grid,
     and it is what keeps a real gap between the two touch targets at 320px
     instead of the 5px true centring would otherwise leave. */
  margin-right: calc(var(--space-2) * -1);
  padding: 0;
  border-radius: 50%;
  background: none;
  color: var(--fg-secondary);
  cursor: pointer;
}

.appearance:hover { color: var(--fg); }

.appearance .icon {
  grid-area: 1 / 1;
  opacity: 0;
  transform: rotate(-45deg) scale(0.7);
  transition: opacity var(--duration-fast) var(--ease),
              transform var(--duration) var(--ease-out);
}

[data-scheme="light"] .icon-dark,
[data-scheme="dark"] .icon-light {
  opacity: 1;
  transform: none;
}

/* --------------------------------------------------------------------------
   Hero
   -------------------------------------------------------------------------- */

/* The bottom value is --space-4, not --space-8, and the reason is arithmetic
   rather than taste. The hero's bottom padding and the following section's top
   padding compound: at 64px each they produced a 128px seam, which is the
   --space-16 page-level gap appearing where a --space-12 major-section break
   belongs — a token nobody chose, emergent from two adjacent paddings. 32px
   plus the section's 64px is exactly --space-12, and it lifts everything below
   the hero by 32px on every page. */
.hero { padding-block: var(--space-12) var(--space-4); }

@media (min-width: 48rem) {
  .hero { padding-block: var(--space-16) var(--space-4); }
}

.hero h1 {
  font-size: var(--text-display);
  letter-spacing: -0.03em;
  line-height: 1.04;
}

/* Held at --text-title, but no longer for the original reason. This h1 used to
   be the bare product name, and the argument was that 72px is a lot of weight
   carrying very little information. It now carries a claim as well, so that
   argument has expired — and the size still stands, because a two-part h1 at
   display size is a wall of type rather than a headline. Roughly three lines at
   320px, two on a phone in portrait, one on a laptop.

   Relies on source order rather than added specificity, per the file's stated
   ordering convention. */
.hero--product h1 { font-size: var(--text-title); }

.hero--product .kicker { margin-bottom: var(--space-1); }

.hero .lead { margin-top: var(--space-3); }

/* The hero's action, and the note under it. 48px sets the action apart from the
   lead it follows; 16px keeps the note attached to the action it qualifies.
   Proximity does the grouping, so neither needs a box drawn round it. */
.hero .action { margin-top: var(--space-6); }

.note {
  max-width: var(--measure);
  margin-top: var(--space-2);
  color: var(--fg-secondary);
  font-size: var(--text-small);
}

/* The waitlist form: a rule you write on, then the page's one action. The
   field is the split sheet's .sheet-field — a label above a hairline — so the
   site has one input, not two. 24rem is an address-sized line; the form is
   not a column and does not pretend to be one. */
.hero .waitlist {
  max-width: 24rem;
  margin-top: var(--space-6);
}

/* The honeypot: a field no person sees, so a filled one is a script.
   display: none keeps it out of the accessibility tree and the tab order as
   well as off the screen — a visually-hidden field would still be announced. */
.waitlist-extra { display: none; }

/* The one filled control on the site. design.md's rule stands for navigation
   — a text action, never a pill — and the owner drew the line at collection
   (2026-09-18): a control that takes an address and sends it is a button, in
   the accent, so it reads as the thing to press and not as a link. It is the
   same control the app's own emails draw (a filled accent rectangle), which is
   the consistency that matters more than the site's aversion to chrome.
   Height by min-height (HIG 44pt, exempt from the grid); inset by the scale,
   wider than tall. */
.button {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: var(--space-1);
  min-height: 44px;
  padding-block: 0;
  padding-inline: var(--space-3);
  border: 0;
  border-radius: var(--radius-pill);
  background: var(--accent);
  color: #ffffff;
  font-family: inherit;
  font-size: var(--text-body);
  font-weight: 600;
  line-height: 1;
  letter-spacing: -0.01em;
  cursor: pointer;
  transition: background-color var(--duration-fast) var(--ease),
              opacity var(--duration-fast) var(--ease);
}

.button:hover { background: var(--accent-ink); }

.button:focus-visible {
  outline: 2px solid var(--accent-ink);
  outline-offset: 4px;
}

.button .arrow {
  display: inline-block;
  transition: transform var(--duration) var(--ease-out);
}

.button:hover .arrow { transform: translateX(4px); }

/* Sending: the button reports state — its label changes and it dims — for
   the half-second the function spends talking to the mail provider. Set by
   waitlist.js on submit; without the script the native submission is simply
   unadorned. Motion that reports state is the kind design.md allows. */
.button:disabled {
  cursor: default;
  opacity: 0.6;
}

.button:disabled .arrow { transform: none; }

.hero .waitlist .button { margin-top: var(--space-3); }

/* --------------------------------------------------------------------------
   CatalogTracker
   -------------------------------------------------------------------------- */

.product-name {
  margin-top: var(--space-1);
  font-size: var(--text-title);
}

.product .lead { margin-top: var(--space-3); }

/* Screenshots. The row runs full-bleed so a shot is always cut off at the
   right edge — that clipped edge is the only affordance the scroller needs.
   300px caps it: each frame is a 600px/1200px srcset pair, so the ceiling is
   2x the base file and the @2x covers a 3x display with headroom. */
.shots-row {
  display: flex;
  /* Frames hang from a common bottom edge — and because every image is the same
     600x1304 source at the same width, a common bottom edge is a common top edge
     for the pictures too. This is load-bearing now that the label sits above the
     picture rather than below it: `07 GENERATED SPLIT SHEET` is 215px of tracked
     mono and wraps to two lines between 481px and about 860px, and under the
     default `stretch` that one caption would push its image 21px below the other
     six — a row of screenshots failing to line up, which is the first thing the
     eye catches and the last thing this page can afford. Aligning to the end
     reserves no space, measures nothing, and holds for any caption anyone
     writes later. The raggedness moves to the top of the row, above the labels,
     where it is whitespace nobody can see. */
  align-items: flex-end;
  gap: var(--space-2);
  margin: var(--space-8) 0 0;
  /* The inset and the scroll-padding are the shared scroller construction in
     the Layout section — this row is its precedent, not a second copy of it. */
  /* A scroll container clips both axes, and the frames' hairline is a box-shadow
     ring drawn 1px outside the image on every side. A hairline of padding on
     each block edge is what keeps the ring whole whichever edge is exposed. */
  padding-block: 1px;
  list-style: none;
  overflow-x: auto;
  overscroll-behavior-x: contain;
  scroll-snap-type: x mandatory;
}

/* The native bar is hidden only because the readout below replaces it — two
   indicators for one axis is one too many. Gated on `js` because the readout is
   built by a script: design.md says never hide a scrollbar without putting
   something in its place, and with JavaScript off nothing was in its place. The
   row was then a seven-frame scroller whose only affordance was a clipped edge,
   and the meter still rendered "01/07" with a full-width thumb — an instrument
   reporting that everything was visible while six frames sat off-screen.
   Now: script present, meter shown and bar hidden; script absent, the reverse.
   Exactly one indicator either way, and the class is set pre-paint so hiding
   the bar never costs a layout shift. */
:root.js .shots-row {
  scrollbar-width: none;
  -ms-overflow-style: none;
}

:root.js .shots-row::-webkit-scrollbar { display: none; }

/* Drawn inside: at the viewport edges an outset ring would be clipped. */
.shots-row:focus-visible { outline-offset: -3px; }

.shots-row > li {
  flex: none;
  scroll-snap-align: start;
}

/* Held to the frame width so a caption can never redefine it. `07 GENERATED
   SPLIT SHEET` is 215px of tracked mono, which is wider than a 200px frame — so
   until now that one item was 15px wider than the other six and the row's pitch
   was set by a string. Invisible while everything was start-aligned, and a
   silent 7px decentring the moment anything is centred. The caption wraps
   instead, which is what a caption longer than its picture should do. */
.shot {
  width: var(--shot-w);
  margin: 0;
}

.shot img {
  display: block;
  width: 100%;
  height: auto;
  /* The iPhone's own screen radius, 55 of 402 points, held at every size. */
  border-radius: calc(var(--shot-w) * 0.1368);
  background: var(--bg);
  box-shadow: 0 0 0 1px var(--separator);
}

/* The label leads its frame, the way a rubric leads its section. It is already
   the rubric's vocabulary — mono numeral, gap, tracked caps — and putting it
   above the picture puts it in the rubric's position too, so the walkthrough
   numbers itself the same way the page does. It also changes what the reader
   does: you know which screen you are about to look at instead of reading the
   picture and then hunting underneath for what it was.

   Ordered in the markup rather than with `order` or `column-reverse`. A
   figcaption is valid as a figure's first child, so the sequence a screen
   reader announces, the sequence the page renders with no CSS at all, and the
   sequence on screen are one sequence. Reversing this visually would have made
   three. */
.shot figcaption {
  display: flex;
  gap: var(--space-2);
  margin-bottom: var(--space-2);
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  font-weight: 500;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  transition: color var(--duration-fast) var(--ease);
}

/* The caption brightens under the pointer — the readout acknowledging which
   frame you are looking at. Deliberately not a lift: these are not links, and
   moving them would promise a click that does not exist. */
.shot:hover figcaption { color: var(--fg); }

.shot-index { letter-spacing: 0; }

/* Below 480px the row stops being a filmstrip and becomes a pager: one frame is
   the subject, centred in the viewport, and one flick moves exactly one frame.
   `scroll-snap-stop: always` is what makes that literal — it is the CSS of
   UIScrollView's `isPagingEnabled`, and without it a hard flick sails past
   three frames and lands wherever momentum ran out, which is the opposite of
   what a numbered walkthrough is claiming about itself.

   The frame grows to the 300px ceiling here because a page occupying half its
   viewport is not a page. The 600px/1200px pair keeps every density sharp at
   that width — this ceiling on a 3x phone is exactly where a lone 600px file
   upscaled 1.5x and went soft; `100vw - 96px` holds a 48px gutter either side,
   and floors at 200px so a 320px viewport still gets a frame it can read.

   The size steps at the breakpoint — a 300px pager becomes a 200px filmstrip —
   and that is deliberate. The two modes want different frames and no single
   curve serves both honestly. On a phone the step is only ever crossed by
   rotating, which changes the layout anyway.

   Centring the first and last frames is what the padding is for: with mandatory
   snapping and no room to scroll past either end, frames 01 and 07 would clamp
   to the edges and only the middle five would ever rest centred — five pages
   obeying the rule and two exempt from it. `max()` keeps the content edge as the
   floor so the row can never indent less than the document it sits in.

   `scroll-padding-inline` is left alone on purpose: equal insets shrink the
   snapport symmetrically and do not move its centre, so it stays correct for
   `start` above the breakpoint and costs nothing below it. */
@media (max-width: 30rem) {
  /* The home page's lone frame takes the same width, because it is sized like a
     frame in the row precisely so the two pages agree about how big the product
     is. Leaving it behind at 200px would have the company page and the product
     page disagreeing about that on every phone, which is the one thing that
     rule exists to prevent. It is not a pager and takes none of the rest. */
  .shots-row,
  .shot--single {
    --shot-w: clamp(200px, 100vw - 96px, 300px);
  }

  .shots-row {
    padding-inline: max(var(--edge), calc((100% - var(--shot-w)) / 2));
  }

  .shots-row > li {
    scroll-snap-align: center;
    scroll-snap-stop: always;
  }
}

/* One frame on the company index, where there is no walkthrough for it to be
   part of and so no numeral — design.md numbers these to declare a sequence,
   and a lone numbered figure would be declaring one that is not there. Sized
   exactly like a frame in the row so the two pages agree about how big the
   product is. 48px above groups it with the copy; the action's own 64px below
   separates it. */
.shot--single { margin-top: var(--space-6); }

/* Telemetry for the row: position in the sequence, then a proportional
   indicator. Same shape as a rubric — figure, then a rule to the margin —
   so the instrument is built from the vocabulary already on the page. */
.shots-meter {
  display: none;
  align-items: center;
  gap: var(--space-3);
  margin-top: var(--space-3);
  padding-inline: var(--edge);
}

:root.js .shots-meter { display: flex; }

/* After the rule above, and load-bearing for that reason: equal specificity, so
   source order is what lets the script's `hidden` win when every frame fits.
   The file's ordering convention is the mechanism here, not a coincidence. */
.shots-meter[hidden] { display: none; }

.shots-count {
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  letter-spacing: 0.06em;
}

.shots-track {
  position: relative;
  flex: 1;
  height: 1px;
  background: var(--separator);
  transition: background-color var(--duration) var(--ease);
}

/* Sized and placed by transform rather than width/left: it updates on every
   scroll frame, and no transition — an instrument tracks 1:1 or it lies. */
.shots-thumb {
  position: absolute;
  inset: 0;
  background: var(--fg);
  transform-origin: left;
  transform: translateX(calc(var(--thumb-start, 0) * 100%))
             scaleX(var(--thumb-size, 1));
}

.product .action { margin-top: var(--space-8); }

/* --------------------------------------------------------------------------
   Writing

   Long-form is the one place descendant selectors beat explicit classes: a
   piece has twenty-odd paragraphs and nobody should be writing class="prose"
   on each of them. Everything is scoped under .article so nothing leaks.

   Headings here are set in the sans, not the rubric's mono. The rubric carries
   the document's apparatus — numerals, labels, dates — and an h2 phrased as a
   question someone actually asked is language, which design.md gives to the
   sans. The dateline is apparatus, so it keeps the mono.
   -------------------------------------------------------------------------- */

.article { padding-block: var(--space-12) var(--space-8); }

.article h1 { font-size: var(--text-title); }

/* One rule owns vertical flow: every block in the article gets space above it,
   and the exceptions below say how much. This started as `p + p`, which looked
   right and was not — a paragraph following a blockquote, a table or a list is
   not a `p + p`, so it got no space at all and collided with what it followed.
   Specificity is deliberate rather than incidental: the owl is two classes, and
   every override carries a third simple selector so it wins on merit and not on
   source order. */
.article .container > * + * { margin-top: var(--space-2); }

.article .container > h2 { margin-top: var(--space-8); }

.article .container > .lead { margin-top: var(--space-4); }

.article .container > blockquote,
.article .container > table,
.article .container > .table-scroll,
.article .container > ul,
.article .container > ol { margin-top: var(--space-3); }

/* The disclaimer is an aside, not the next paragraph, so it gets real air. */
.article .container > .note { margin-top: var(--space-6); }

.article .dateline {
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  letter-spacing: 0.06em;
}

.article h2 {
  max-width: var(--measure);
  margin-bottom: var(--space-3);
  font-size: var(--text-subtitle);
  font-weight: 600;
  letter-spacing: -0.02em;
  line-height: 1.2;
  text-wrap: balance;
}

/* FAQ questions. Language, so the sans; lead size so they sit clearly under
   the section h2s; 32px above so each question reads as a heading and not as
   the previous answer's afterthought. Scoped to direct children — the related
   shelf's h3s live deeper and keep their own rules. */
.article .container > h3 {
  max-width: var(--measure);
  margin-top: var(--space-4);
  font-size: var(--text-lead);
}

/* The prose lists, and the related shelf is not one of them. It is a `ul`
   because it is a list of pieces, and it takes none of a prose list's
   geometry: not the measure, because it is a full-bleed scroller, and not
   the bullet indent, because its inset is the page's own edge. Excluded
   here rather than overridden there — these two rules and the scroller
   construction match with the same specificity, so an override in the
   shelf's own block is a coin toss settled by source order, and it was
   settling wrong: the shelf drew a 24px inset that only looked correct at
   320px, where the gutter happens to be 24px too. */
.article p,
.article ul:not(.related-row),
.article ol {
  max-width: var(--measure);
}

.article ul:not(.related-row),
.article ol { padding-left: var(--space-3); }

.article li + li { margin-top: var(--space-1); }

/* Verbatim from the standard, so it is set apart as quotation rather than
   paraphrased into our own voice. The hairline is the only device it gets. */
.article blockquote {
  max-width: var(--measure);
  margin-top: var(--space-3);
  padding-left: var(--space-3);
  border-left: 1px solid var(--separator);
  color: var(--fg-secondary);
}

/* Identifiers are apparatus, so they are set in the mono. 0.92em because the
   mono's figures render optically larger than the sans at a matched size. */
.article code {
  font-family: var(--font-mono);
  font-size: 0.92em;
}

/* Hairlines and nothing else — no header fill, no zebra striping. The type
   split inside a table is the document's own: column labels are apparatus
   (mono, tracked caps, one line — a label that wraps stops reading as a
   label), row leaders are language (sans, medium, wrapping like any other
   sentence). A leader that genuinely is apparatus — the ISRC worked
   example's code parts — declares it in the markup with <code>, which
   carries it back to the mono on its own.
   Column widths are deliberately left to the table algorithm: with nothing
   forbidden to wrap, widths settle in proportion to content, which is the
   balanced result. The first cut pinned tbody leaders to one line, which
   handed a table of sentence-length leaders ~90% of the row and squeezed
   the rest into a ribbon — a width rule tuned to one table is wrong for
   the next one. */
.article table {
  width: 100%;
  max-width: var(--measure);
  margin-top: var(--space-3);
  border-collapse: collapse;
  font-size: var(--text-small);
}

/* A table is the one block whose width its content decides. The thead labels
   above are apparatus and deliberately do not wrap, so a three-column table's
   min-content width is the sum of three unwrapped labels — and no table can be
   laid out narrower than that, whatever `width: 100%` asks for. Measured
   2026-08-08 at 320px: six of the eight article pages pushed the PAGE sideways,
   up to 57px on the Spanish master piece. `design.md` forbids that outright.

   The table therefore scrolls inside its own container, which is the answer
   this site already gives twice — the walkthrough row and the related shelf.
   Three things follow from those precedents rather than from taste: the native
   scrollbar stays, because nothing replaces it here; the measure is carried
   rather than lost, so the table is free to be wider than the column of prose
   while the prose is not; and it is focusable, because a region that scrolls
   has to be reachable with the keyboard alone. Nothing here needs JavaScript,
   and at 390px and up there is nothing to scroll.

   **The measure moved from the container to the table** (2026-08-15). The
   container is a full-bleed scroller now — see the construction in Layout —
   so it is as wide as the page, and a max-width on it would be a second
   answer to a question `.article table` already answers with the same token.
   A table that fits is still exactly `--measure` wide and looks identical;
   one that does not is free to exceed it, which was always the point. */
.article .container > .table-scroll {
  overflow-x: auto;
}

/* Drawn inside, like the walkthrough row and the related shelf: at the
   container edge an outset ring would be clipped by the scroller's own box. */
.table-scroll:focus-visible { outline-offset: -3px; }

/* The wrapper owns the gap now — the table would otherwise add its own inside
   it and the block would sit a step low. */
.article .table-scroll > table { margin-top: 0; }

.article th,
.article td {
  padding: var(--space-1) var(--space-2) var(--space-1) 0;
  border-bottom: 1px solid var(--separator);
  text-align: left;
  vertical-align: baseline;
}

.article thead th {
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  font-weight: 500;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  white-space: nowrap;
}

/* 500, not the UA's bold: the leader is a row's subject, not its shout. */
.article tbody th {
  font-weight: 500;
}

/* The routes block on /writing (2026-08-16). Four symptoms, each pointing at
   where the corpus starts on it — the question a first-time reader actually
   arrives with, which the chronological list below cannot answer because its
   order is fixed by the numbering canon.

   No hairlines here, unlike .posts. The rules between index entries exist
   because those entries are peers of equal weight and need separating; these
   four are a single short block and proximity does the grouping. Giving them
   rules too would make the page read as two lists of the same thing, which
   is the one outcome this block exists to avoid. 24px inside a row against
   the section's own 64px around it. */
.routes {
  max-width: var(--measure);
  margin: 0;
  padding: 0;
  list-style: none;
}

.lead + .routes { margin-top: var(--space-6); }

.routes > li + li { margin-top: var(--space-3); }

/* The symptom leads its row the way a rubric leads its section: the reader
   scans four bold lines and stops at theirs, rather than reading four
   sentences to find out which is which. */
.routes strong { display: block; }

.routes + .note { margin-top: var(--space-6); }

/* The index. One entry today; the rule between entries is what the second one
   will land against. The titles reuse .action rather than cloning it — a post
   title is navigation set in the page's own type, which is what .action is. */
.posts {
  max-width: var(--measure);
  padding: 0;
  list-style: none;
}

/* On /writing the list follows a rubric, which already carries 48px beneath
   it. On the home page it follows a lead, which carries nothing — so the first
   date collided with the last line of the lead. Same 48px the product entry
   puts between its lead and its frame. The Spanish home interposes a note
   ("solo en inglés") between the lead and the list, which silently defeated
   the adjacency and reproduced the original collision one element later —
   the same 48px applies from whichever of the two the list actually follows. */
.lead + .posts,
.note + .posts { margin-top: var(--space-6); }

.posts > li + li {
  margin-top: var(--space-6);
  padding-top: var(--space-6);
  border-top: 1px solid var(--separator);
}

.post-date {
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  letter-spacing: 0.06em;
}

/* The title's underline is a strong horizontal, and a summary sitting 8px under
   it reads as attached to the rule rather than to the title. 16px lets the
   summary belong to the entry instead.

   Two selectors because the index's titles are h4 under a band heading while
   the home page's subset has no bands and keeps its h3 — the rule is about a
   title and its summary, not about a level. */
.posts h3 + p,
.posts h4 + p { margin-top: var(--space-2); }

/* The subject bands on /writing (2026-08-17). Nineteen pieces in one strictly
   descending run answered "what is new" and nothing else; a reader who wants
   one subject had to know the corpus to find it. The list is still one list
   and still descending — the bands group it, they do not reorder within it.

   Borrowed, not invented: this is exactly .sheet-block > h3 — .rubric's shape
   one level down, mono tracked caps with a hairline to the margin — because a
   band is a subsection of the Pieces section in the same way a party is a
   subsection of the sheet. A third heading shape on one page would be a third
   answer to a question the page has already answered twice.

   64px above a band against the 48px between entries inside one, so the gap
   between subjects is larger than the gap within one and proximity does the
   grouping. The first band needs nothing: .rubric already carries 48px
   beneath it, which is why this keys on .posts + .band rather than on .band. */
.band {
  display: flex;
  align-items: baseline;
  gap: var(--space-3);
  margin-bottom: var(--space-3);
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  font-weight: 500;
  letter-spacing: 0.06em;
  text-transform: uppercase;
}

.band::after {
  content: "";
  flex: 1;
  height: 1px;
  background: var(--separator);
  transition: background-color var(--duration) var(--ease);
}

.posts + .band { margin-top: var(--space-8); }

/* The scope row (2026-09-07, at thirty-nine pieces). Four bands are a
   structure the reader could only discover by scrolling through all of them;
   the row states the structure up front, with a count per band, and lets the
   reader hold one band on its own. Generated with the list it governs — the
   counts are apparatus, and apparatus is computed, never typed.

   The chips are the nav's own vocabulary: a 44px capsule, mono tracked caps
   because a band name is a section label, bare at rest and ringed when
   chosen. The ring and the full-strength ink are two cues for one state, so
   the choice never rests on colour alone. No fill — the hairline is the only
   structural device on the page, and the ring is a hairline bent round.

   A row, not a wrap. Each chip carries one word and its count — the full
   names ran to about 1,040px in mono caps and scrolled at every width
   including the desk — so the five chips take about 590px and sit on one
   line from a tablet up (measured: 587px in a 744px row). On a phone the
   row scrolls, by the shared scroller construction above: page-edge to
   page-edge, the first label on the prose edge, the last chip clipped at
   the screen's edge as the affordance. The capsule overhangs the content
   edge by its own inset so the LABEL sits on the edge, which is the same
   trick the language chip plays in the nav.

   The count is design.md's readout: mono figures, secondary ink, no easing.
   It stays secondary inside a chosen chip so the name is what reads.

   The row sticks under the nav once the reader has scrolled past it
   (2026-09-08, owner's ask from a phone). It is the list's own control, and
   a control that leaves the screen while its list is still being read has
   to be scrolled back to — on a phone, through forty entries. Its stuck
   position is the nav's own rhythm: the strip is 16px + 44px + 16px, so the
   row's box starts at 76px and its chips sit 24px under the nav chips.
   Sticky, not fixed, so it releases with the section it governs: the RSS
   note and the footer scroll it away.

   Stuck, the chips materialise exactly as the nav chips do once anything is
   underneath them (owner's ruling, 2026-09-08, from a phone, after two
   other treatments): translucent fill, hairline ring, blur inside each
   capsule — the site's one chip vocabulary, now in both places. Nothing is
   drawn behind the row itself; the list passes between the chips the way it
   passes between the nav chips. The chosen chip keeps its full ink and
   takes a stronger ring, so the choice reads by more than colour while
   every chip is ringed. Shown only while the row is held (`.is-stuck`, set
   by writing.js from the row's own rectangle); in the flow the chips stay
   bare, and only the chosen one is ringed.

   Sticky only once the script has run (`:root.js`): without it nothing can
   say the row is held, so the chips could never materialise, and a bare row
   stuck over sharp text is worse than a row that scrolls with the page. A
   reader who prefers reduced transparency, or an engine without
   backdrop-filter, gets the page's ground inside each chip instead — the
   same two fallbacks the nav chips already take. `z-index` sits under the
   nav's 5. */
.scopes {
  /* A scroller clips on both axes, and a chip's focus ring is drawn 3px
     outside its capsule. 8px of block padding on the list, cancelled by the
     same margin here so the rhythm around the row is unchanged, is the room
     the ring needs — the alternative, a ring drawn inside a 44px capsule,
     reads as a second border rather than as focus. */
  margin-block: calc(-1 * var(--space-1)) calc(var(--space-6) - var(--space-1));
  margin-inline: calc(-1 * var(--gutter));
}

:root.js .scopes {
  position: sticky;
  top: calc(var(--header-h) + 2 * var(--space-2));
  z-index: 4;
}

.scopes.is-stuck .scope {
  background: var(--header-bg);
  border-color: var(--separator);
  -webkit-backdrop-filter: saturate(180%) blur(20px);
  backdrop-filter: saturate(180%) blur(20px);
}

.scopes.is-stuck .scope[aria-current] { border-color: var(--fg-secondary); }

@supports not ((backdrop-filter: blur(1px)) or (-webkit-backdrop-filter: blur(1px))) {
  .scopes.is-stuck .scope { background: var(--bg); }
}

@media (prefers-reduced-transparency: reduce) {
  .scopes.is-stuck .scope {
    background: var(--bg);
    -webkit-backdrop-filter: none;
    backdrop-filter: none;
  }
}

ul.scope-row {
  display: flex;
  gap: var(--space-1);
  padding-block: var(--space-1);
  list-style: none;
  overflow-x: auto;
  overscroll-behavior-x: contain;
  scroll-snap-type: x proximity;
  /* No native bar (owner's ruling, 2026-09-08, on seeing the overlay bar
     drawn under the chips on a phone). design.md says a scrollbar is never
     hidden without something in its place; here that something is the row's
     own shape — the last chip clipped at the screen's edge, the same
     affordance the shelf and the walkthrough row carry — and, with the
     script, the chosen chip brought inside the clip whenever it changes. A
     bar under a chip row is a second control drawn under the first. */
  scrollbar-width: none;
  -ms-overflow-style: none;
}

ul.scope-row::-webkit-scrollbar { display: none; }

/* The first label on the prose edge: the row's inset is the page's edge
   minus one chip inset, so the capsule overhangs into the gutter and the
   text lands on the edge — the language chip's own construction, applied to
   a row. Both editions, every width. The scroller construction's block
   above states the bleed; this states the inset, once. */
ul.scope-row {
  padding-inline: calc(var(--edge) - var(--space-2));
  scroll-padding-inline: calc(var(--edge) - var(--space-2));
}

.scope-row > li {
  flex: none;
  scroll-snap-align: start;
}

.scope {
  display: inline-flex;
  align-items: center;
  gap: var(--space-1);
  min-height: var(--header-h);
  padding-inline: var(--space-2);
  border: 1px solid transparent;
  border-radius: var(--radius-pill);
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  font-weight: 500;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  text-decoration: none;
  white-space: nowrap;
  transition: color var(--duration-fast) var(--ease),
              background-color var(--duration) var(--ease),
              border-color var(--duration) var(--ease);
}

.scope:hover,
.scope[aria-current] { color: var(--fg); }

.scope[aria-current] { border-color: var(--separator); }

.scope-count {
  color: var(--fg-secondary);
  font-weight: 400;
  letter-spacing: 0;
}

/* An anchored jump to a band lands under the stuck row otherwise: the
   page's own scroll-padding clears the nav strip, and this clears the row's
   60px box and leaves 16px between the line and the heading — 76 again,
   the same figure the row itself starts at. Tokens, not a number typed
   twice: the nav's height plus one component step. */
.band { scroll-margin-top: calc(var(--header-h) + var(--space-4)); }

/* A band filtered away takes its list with it, and the survivor loses the
   64px it would otherwise keep above it for a neighbour that is not there.
   `.band` sets its own display, so the UA's [hidden] rule alone would not
   hide it — the same reason .shots-meter[hidden] is stated. */
.band[hidden],
.posts[hidden] { display: none; }

.posts[hidden] + .band { margin-top: 0; }

/* "All writing", where the home page lists a subset. 64px and not the 48px
   between entries: the action closes the list rather than joining it, and
   matching the interval would read as a fourth headline with no date. Same
   value, for the same reason, as the action closing the product section. */
.posts + .action { margin-top: var(--space-8); }

/* Related pieces — the registry's link graph made visible at the foot of a
   piece. Two or three entries, chosen at the proposal stage against
   editorial/docs/content-inventory.md, never generated. A row rather than a
   list: the piece is over, and this is a shelf to leave by, not more of the
   article. Entries reuse the index's own vocabulary — date, action title,
   one-liner — so the site never describes a piece two ways. */
.article .container > .related { margin-top: var(--space-8); }

/* Columns floor at 15rem, so on a phone the second entry is cut at the SCREEN
   edge — the same clipped-edge affordance the walkthrough row uses, and since
   2026-08-15 by the same construction rather than a near-miss of it. The
   native scrollbar is hidden (owner's ruling, 2026-09-08, on seeing the
   overlay bar drawn under the shelf on a phone, the same day the scope row's
   went): the clipped edge is what stands in its place. Same specificity as
   the article's list rules, later in the file — the ordering convention is
   the mechanism, as with .shots-meter[hidden].

   No `padding: 0` here any more. A list's default indent is an inline
   padding, so a shorthand reset in this block silently overrode the inset
   the scroller construction sets — the reset and the inset were two rules
   answering for the same edge. The construction sets `padding-inline`
   outright, which is the reset. */
ul.related-row {
  display: grid;
  grid-auto-flow: column;
  grid-auto-columns: minmax(min(100%, 15rem), 1fr);
  gap: var(--space-3);
  padding-block: 0;
  list-style: none;
  overflow-x: auto;
  overscroll-behavior-x: contain;
  scroll-snap-type: x proximity;
  scrollbar-width: none;
  -ms-overflow-style: none;
}

ul.related-row::-webkit-scrollbar { display: none; }

/* Drawn inside, like the walkthrough row: at the container edge an outset
   ring would be clipped by the scroller's own box. */
.related-row:focus-visible { outline-offset: -3px; }

.related-row > li {
  min-width: 0;
  scroll-snap-align: start;
}

.related-row > li + li {
  margin-top: 0; /* the article's li rhythm is vertical; this row is not */
  padding-left: var(--space-3);
  border-left: 1px solid var(--separator);
}

/* Index titles run at subtitle size across the full measure; in a 15rem
   column that wraps to four lines and stops reading as a title. Lead size
   holds two lines, and the underline offset comes down with it — 6px is a
   typography metric like the base anchor's 3px, not grid spacing. */
.related-row .action {
  position: relative;
  font-size: var(--text-lead);
  text-underline-offset: 6px;
}

/* At the smallest viewports a lead-size title plus its 8px padding lands a
   ~39px target — under the HIG 44 that design.md makes non-negotiable, and
   which the index's subtitle-size titles just clear. The pseudo extends the
   hit area 4px each way without moving a pixel of layout: the sanctioned
   optical-correction allowance, spent on the finger instead of the eye. */
.related-row .action::before {
  content: "";
  position: absolute;
  inset: -4px 0;
}

.related-row h3 + p { margin-top: var(--space-2); }

/* --------------------------------------------------------------------------
   Split sheet

   The design language came from the split sheet CatalogTracker generates, so a
   split sheet on the site is the vocabulary returning to its source. Nothing
   new is invented here: a party block is a rubric with a numeral and a rule,
   and a field is a hairline you write on. design.md already said the hairline
   is the only structural device — on a form it is also the correct affordance,
   which is why this needed no boxes, no fills and no new tokens.

   There is no <form>, no action and no submit. CLAUDE.md rejected a form that
   silently discards an address; this collects nothing and sends nothing, which
   is a different thing and is stated on the page rather than merely true.
   -------------------------------------------------------------------------- */

.sheet { max-width: 44rem; }

/* Same shape as .rubric — mono numeral, tracked-caps label, hairline to the
   margin — one level down, because a party is a subsection of the document
   rather than a section of the page. */
.sheet-block { margin-top: var(--space-6); }

.sheet-block > h3 {
  display: flex;
  align-items: baseline;
  gap: var(--space-3);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  font-weight: 500;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  color: var(--fg-secondary);
}

.sheet-block > h3::after {
  content: "";
  flex: 1;
  height: 1px;
  background: var(--separator);
}

/* Two columns where there is room, one where there is not. minmax(0, 1fr) and
   not 1fr: a grid track floors at min-content, and an input's default size
   attribute is wide enough to push a bare 1fr past its share and overflow the
   row on a narrow screen. Same failure the header's centre track had. */
.sheet-grid {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 16rem), 1fr));
  gap: var(--space-3) var(--space-4);
  margin-top: var(--space-3);
}

.sheet-field {
  display: flex;
  flex-direction: column;
  gap: var(--space-1);
}

/* The label is apparatus, so it is mono and tracked like every other label on
   the site. It sits above the rule rather than inside it — a placeholder that
   vanishes on focus is exactly the pattern that makes printed forms unfillable
   and screen-reader labels disappear. */
.sheet-field label {
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  font-weight: 500;
  letter-spacing: 0.06em;
  text-transform: uppercase;
}

/* A rule you write on. No box, no fill, no radius: the hairline already is the
   field, and drawing a container around it would be the first card on the site.
   44px is the HIG touch minimum, which design.md exempts from the 8-grid. */
.sheet-field input {
  min-height: 44px;
  padding: 0 0 var(--space-1);
  border: 0;
  border-bottom: 1px solid var(--separator);
  border-radius: 0;
  background: none;
  color: var(--fg);
  font-family: inherit;
  font-size: var(--text-body);
  transition: border-color var(--duration-fast) var(--ease);
}

/* Accent means "you can act on this", and a field being edited is the clearest
   case of it. The rule thickens as well as changes colour — two cues, the same
   rule .link-quiet follows, so it never rests on colour alone. */
.sheet-field input:focus {
  outline: none;
  border-bottom: 2px solid var(--accent-ink);
  padding-bottom: calc(var(--space-1) - 1px);
}

/* No ring on a field. A box drawn round a rule-you-write-on is the one thing
   that makes it read as a web form, and the owner cut it (2026-09-18). Focus
   is still plainly visible, for keyboard and pointer alike: the rule thickens
   and turns accent above, and the label turns accent with it — colour and
   weight, two cues, and the caret is a third. engineer.md's rule is "never
   remove a focus outline without replacing it with something better", and
   this is the replacement, not an absence. */
.sheet-field input:focus-visible { outline: none; }

.sheet-field:focus-within label { color: var(--accent-ink); }

.sheet-field--share { max-width: 12rem; }

/* The totals readout. Same instrument grammar as the screenshot meter: mono
   figures, a hairline above, no easing. It states the shortfall in words as
   well as figures because design.md forbids carrying meaning in colour — and
   having done so, it needs no colour at all, which suits a monochrome page.

   Not a live region: it updates on every keystroke and would chatter. It is
   plain text a screen reader can reach, which is the honest middle. */
.sheet-total {
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-1) var(--space-3);
  margin-top: var(--space-6);
  padding-top: var(--space-3);
  border-top: 1px solid var(--separator);
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  letter-spacing: 0.06em;
  text-transform: uppercase;
}

.sheet-total output { color: var(--fg); }

/* Signature lines. Deliberately not inputs — a signature is wet ink or it is
   nothing, and offering a text field for one would suggest this page can do
   something it cannot. */
.sheet-sign {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(min(100%, 16rem), 1fr));
  gap: var(--space-6) var(--space-4);
  margin-top: var(--space-6);
}

.sheet-sign > div {
  padding-top: var(--space-8);
  border-bottom: 1px solid var(--fg);
}

.sheet-sign p {
  margin-top: var(--space-1);
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  letter-spacing: 0.06em;
  text-transform: uppercase;
}

/* Operative clauses — the session-musician assignment. Every other block a
   sheet contains is fields; this one is the text that does the work, and it
   has to stay legible to somebody who finds the printed page in two years.

   An <ol> rather than hand-numbered paragraphs, so the numbering belongs to
   the list and a clause cannot be renumbered wrong by an edit above it — the
   commentary and the FAQ both refer to clause 4 by number. The marker is mono
   because a clause number is apparatus, like every other numeral on this site,
   and ::marker takes font and colour on every engine this site supports. */
.sheet-terms {
  max-width: var(--measure);
  margin-top: var(--space-3);
  padding-left: var(--space-4);
}

.sheet-terms li + li { margin-top: var(--space-3); }

.sheet-terms li::marker {
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  color: var(--fg-secondary);
}

/* Checklist items — the audit checklist tool, same document grammar as the
   sheet: h3 blocks group, items run one line each. The control is the
   platform's own checkbox (color-scheme keeps it right in the dark), tinted
   with the accent because a box you can tick is "you can act on this". The
   label extends the touch target across the whole line. */
.check-list { list-style: none; margin: 0; padding: 0; }

.check-list li {
  display: grid;
  grid-template-columns: 1rem 1fr;
  column-gap: var(--space-2);
  align-items: start;
  padding-block: var(--space-1);
}

.check-list input {
  width: 1rem;
  height: 1rem;
  margin: 0.25rem 0 0; /* optical: centres the box on the label's first line */
  accent-color: var(--accent);
}

/* A box you tick with a thumb is a control, and this file asks 44pt of a
   control regardless of what the grid suggests. These were 16x16 at every
   width — the smallest targets on the site, on the one page built to be
   worked through on a phone — and `check-layout.py` measured 24 of them,
   twice over, in both editions.

   The platform checkbox cannot be grown: `appearance: auto` ignores padding,
   and width or height stretches the DRAWN control rather than its target. So
   on coarse pointers the control is ours — the same 1rem mark, centred in a
   48px target, pulled back by an equal negative margin so nothing on screen
   moves. 48 rather than 44 because 48 and its -16px pull-back are both on the
   8-point grid, where 44 forces -14 and -10 and an exemption for nothing; the
   spare 4px costs the reader nothing. design.md's own note governs the split:
   the grid governs what is authored, the target governs what is drawn.

   The tick is the whole cost of the rule. `appearance: none` throws the
   platform checkmark away, so it comes back as an inline mark over the accent
   fill — one white tick serves both schemes, because `--accent` is the same
   blue in each. The pointer control is untouched: a mouse already hits 16px,
   and redrawing it there would trade a native control for a copy of one. */
@media (pointer: coarse) {
  .check-list input {
    appearance: none;
    -webkit-appearance: none;
    width: 48px;
    height: 48px;
    margin: -1rem 0 0 -1rem;
    display: grid;
    place-content: center;
    background: none;
    border: 0;
  }

  .check-list input::before {
    content: "";
    width: 1rem;
    height: 1rem;
    border: 1px solid var(--fg-secondary);
    border-radius: 4px;
  }

  .check-list input:checked::before {
    background: var(--accent)
      url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 16 16' fill='none' stroke='%23fff' stroke-width='2.4' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M3.6 8.4 6.6 11.4 12.4 4.8'/%3E%3C/svg%3E")
      center / 1rem 1rem no-repeat;
    border-color: var(--accent);
  }
}

/* --------------------------------------------------------------------------
   A button set in the action's type. It stays a button because it submits;
   the native fill and border are the borrowed web chrome this design declines.
   The waitlist's submit uses it. 44pt by min-height, the way every control
   here earns it: min-height draws it, the grid still governs padding.
   -------------------------------------------------------------------------- */
button.action {
  border: 0;
  /* The platform button's side padding would inset the label a few pixels
     from the field above it; a text action has no horizontal inset. */
  padding-inline: 0;
  background: none;
  cursor: pointer;
  font-family: inherit;
  min-height: 44px;
  text-align: left;
}

/* --------------------------------------------------------------------------
   Agreement — /catalogtracker/confirm, where a party without the app reads a
   split sheet and accepts or declines it (2026-10-27, the app's D-020).

   This page is a document, not a page of the site, and it is designed as one
   (decisions.md, "The confirm page is a document, and a document is paper").
   It is always light: the html carries data-scheme="light" and loads no
   theme script, so the site's light tokens hold in dark mode, as Pages and
   Preview keep a page white. It drops the site's editorial grammar — mono
   uppercase labels, text actions, the rubric rule — for the app's: sentence-
   case labels, grouped rows on a quiet fill, and one filled primary button
   beside one bordered secondary at every step. Someone who has never heard
   of us should see in one glance what this is, what their share is, and what
   pressing each button does.

   Tokens: spacing, type, ink, accent and hairline are the site's. The few
   this page adds are declared once, here, and used by name below.
   -------------------------------------------------------------------------- */
html.agreement {
  --ag-fill: #f5f5f7;          /* the grouped-row fill, as iOS Settings */
  --ag-on-accent: #ffffff;     /* label on the filled button: 4.70:1 on --accent, 5.57:1 hovered */
  --ag-field-border: #86868b;  /* a field's edge: 3.62:1 on white (WCAG 1.4.11) */
  --ag-success: #1f7a35;       /* text-grade: 5.39:1 on white, 4.95:1 on --ag-fill */
  --ag-danger: #c9190b;        /* text-grade: 5.79:1 on white */
  --ag-radius: 12px;
  --ag-radius-small: 10px;
  --ag-control-h: 48px;        /* above the 44pt minimum, and on the grid */
  --ag-column: 40rem;          /* one readable column, on a phone and a desk */
  color-scheme: light;
  background: var(--bg);
}

.agreement body {
  background: var(--bg);
  color: var(--fg);
}

/* ---- Header: who this is from, and that the page is secure. -------------- */
.ag-header { border-bottom: 1px solid var(--separator); }

.ag-header-inner {
  max-width: var(--ag-column);
  min-height: 56px;
  margin: 0 auto;
  padding: var(--space-1) var(--gutter);
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--space-2);
}

.ag-brand {
  display: inline-flex;
  align-items: center;
  gap: var(--space-1);
  font-size: var(--text-body);
  font-weight: 600;
}

.ag-brand img { border-radius: 7px; }

.ag-secure {
  display: inline-flex;
  align-items: center;
  gap: var(--space-1);
  color: var(--fg-secondary);
  font-size: var(--text-micro);
}

/* ---- The column. ---------------------------------------------------------- */
.ag-main {
  max-width: var(--ag-column);
  margin: 0 auto;
  padding: var(--space-4) var(--gutter) var(--space-8);
}

.ag-kicker {
  color: var(--fg-secondary);
  font-size: var(--text-small);
  font-weight: 600;
}

.ag-title {
  margin-top: var(--space-1);
  font-size: var(--text-subtitle);
  font-weight: 700;
  line-height: 1.15;
}

.ag-kicker + .ag-title { margin-top: var(--space-1); }
.ag-title:first-child { margin-top: 0; }

.ag-step-title {
  font-size: var(--text-lead);
  font-weight: 700;
  line-height: 1.2;
}

.ag-step-title:focus { outline: none; }

.ag-text {
  margin-top: var(--space-2);
  font-size: var(--text-body);
  line-height: 1.5;
}

.ag-quiet {
  margin-top: var(--space-2);
  color: var(--fg-secondary);
  font-size: var(--text-small);
  line-height: 1.5;
}

/* ---- What this kind of sheet is, for a first-timer: one ⓘ button under the
   title, and the explanation opens in place on the page's quiet fill. ------ */
.ag-info {
  margin-top: var(--space-1);
  min-height: 44px;
  padding: 0;
  display: inline-flex;
  align-items: center;
  gap: var(--space-1);
  border: 0;
  background: none;
  color: var(--accent-ink);
  font-family: inherit;
  font-size: var(--text-small);
  font-weight: 600;
  text-align: left;
  cursor: pointer;
}

.ag-info svg {
  flex: none;
  width: 20px;
  height: 20px;
}

.ag-explain {
  margin-top: var(--space-1);
  padding: var(--space-3);
  border-radius: var(--ag-radius);
  background: var(--ag-fill);
  font-size: var(--text-small);
  line-height: 1.55;
}

.ag-explain[hidden] { display: none; }
.ag-explain p + p,
.ag-explain ul + p { margin-top: var(--space-2); }
.ag-explain-lead { font-weight: 600; }

.ag-explain ul {
  margin: var(--space-1) 0 0;
  padding-left: var(--space-3);
}

.ag-explain li + li { margin-top: 0.25rem; } /* optical: a short checklist reads as one block */

.ag-info:focus-visible {
  outline: 3px solid var(--accent);
  outline-offset: 2px;
}

@media (prefers-reduced-motion: no-preference) {
  .ag-explain.is-opening { animation: ag-rise 250ms var(--ease-out) both; }
}

/* ---- Your share: the one moment on the page that celebrates. ---------------
   Someone's work is about to earn them something, and this card says so: the
   largest type on the page, white on a deep accent-to-indigo field, and the
   song's own waveform, lit up to their share. It celebrates the credit, never the
   yes — Decline stays a plain, equal choice below. Contrast is measured on the
   lightest stop: white 5.80:1, the 86% supporting white 4.72:1. Motion lives
   in the "Motion" block below. */
html.agreement {
  --ag-hero-from: #0a5fd6;
  --ag-hero-to: #4b2bb8;
  --ag-on-hero: #ffffff;
  --ag-on-hero-soft: rgba(255, 255, 255, 0.86);
  --ag-on-hero-line: rgba(255, 255, 255, 0.24);
  --ag-hero-glow: rgba(255, 255, 255, 0.18);
  /* The share is the largest type on the page at every width: 56pt on a
     phone, growing to 80pt on a desk, where the site's display size would
     stop at 36pt on the narrowest screens. */
  --ag-share-size: clamp(3.5rem, 2.6rem + 4vw, 5rem);
}

.ag-share {
  position: relative;
  margin-top: var(--space-3);
  padding: var(--space-3);
  border-radius: 20px;
  overflow: hidden;
  color: var(--ag-on-hero);
  background:
    radial-gradient(120% 90% at 100% 0%, var(--ag-hero-glow), transparent 60%),
    linear-gradient(135deg, var(--ag-hero-from), var(--ag-hero-to));
  box-shadow: 0 16px 40px -16px var(--ag-hero-to);
}

.ag-share-label {
  color: var(--ag-on-hero-soft);
  font-size: var(--text-small);
  font-weight: 600;
}

.ag-share-value {
  margin-top: var(--space-1);
  font-size: var(--ag-share-size);
  font-weight: 800;
  font-variant-numeric: tabular-nums;
  line-height: 1;
}

.ag-share-of {
  margin-top: var(--space-1);
  color: var(--ag-on-hero-soft);
  font-size: var(--text-body);
  line-height: 1.4;
}

/* The song's waveform: thirty-two bars from the agreement's fingerprint, so
   every agreement has its own, lit up to the reader's share. Decorative; the
   share is said in words above it. The 4pt between bars is the half-step,
   spent here as optical spacing inside one drawn shape. */
.ag-wave {
  margin-top: var(--space-3);
  height: 48px;
  display: flex;
  align-items: center;
  gap: 0.25rem;
}

.ag-wave span {
  flex: 1;
  height: calc(var(--h) * 100%);
  border-radius: 2px;
  background: var(--ag-on-hero-line);
}

.ag-wave span.is-lit { background: var(--ag-on-hero); }

.ag-share-credit {
  margin-top: var(--space-3);
  padding-top: var(--space-2);
  border-top: 1px solid var(--ag-on-hero-line);
  display: flex;
  flex-wrap: wrap;
  align-items: baseline;
  justify-content: space-between;
  gap: var(--space-1) var(--space-2);
  font-size: var(--text-small);
}

.ag-share-credit strong { font-weight: 600; }
.ag-share-credit span { color: var(--ag-on-hero-soft); }

.ag-share-badge {
  margin-top: var(--space-2);
  display: inline-flex;
  align-items: center;
  gap: var(--space-1);
  min-height: 32px;
  padding: 0 var(--space-2);
  border-radius: 999px;
  background: var(--ag-on-hero-line);
  font-size: var(--text-small);
  font-weight: 600;
}

/* ---- Progress: three named steps. The current one is bold and filled, the
   done ones filled; the words carry it as well as the bar, and "Step n of 3"
   is said to assistive technology. --------------------------------------- */
.ag-steps {
  margin: var(--space-4) 0 0;
  padding: 0;
  list-style: none;
  display: flex;
  gap: var(--space-1);
}

.ag-steps li {
  flex: 1;
  display: flex;
  flex-direction: column;
  gap: var(--space-1);
  color: var(--fg-secondary);
  font-size: var(--text-micro);
}

.ag-steps li::before {
  content: "";
  height: 4px;
  border-radius: 2px;
  background: var(--separator);
}

.ag-steps li.is-done::before,
.ag-steps li[aria-current="step"]::before { background: var(--accent); }

.ag-steps li[aria-current="step"] {
  color: var(--fg);
  font-weight: 600;
}

/* ---- Sections and grouped rows, as the app lists them. --------------------- */
.ag-section { margin-top: var(--space-4); }

.ag-section-title {
  font-size: var(--text-body);
  font-weight: 600;
}

.ag-group {
  margin: var(--space-2) 0 0;
  padding: 0;
  list-style: none;
  border: 1px solid var(--separator);
  border-radius: var(--ag-radius);
  overflow: hidden;
}

.ag-row {
  min-height: var(--ag-control-h);
  padding: var(--space-2);
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--space-2);
}

.ag-row + .ag-row { border-top: 1px solid var(--separator); }

.ag-row--you { background: var(--ag-fill); }

.ag-row-main {
  min-width: 0;
  display: flex;
  flex-direction: column;
  gap: 0.25rem; /* optical: a name and its detail read as one line pair */
}

.ag-row-name {
  font-size: var(--text-body);
  font-weight: 500;
  overflow-wrap: anywhere;
}

.ag-row-detail {
  color: var(--fg-secondary);
  font-size: var(--text-small);
}

.ag-row-value {
  flex: none;
  font-size: var(--text-body);
  font-weight: 600;
  font-variant-numeric: tabular-nums;
  text-align: right;
}

/* A row that is a sentence (Your rights): read as prose, at the size of the
   app's subheadline. */
.ag-row-text {
  font-size: var(--text-small);
  line-height: 1.5;
}

/* A link inside a row: its words in accent, a full touch target of its own,
   and the line beneath it left free to select and copy. */
.ag-row-link {
  min-height: 44px;
  display: inline-flex;
  align-items: center;
  align-self: flex-start;
  color: var(--accent-ink);
  text-decoration: none;
}

.ag-row-link:hover { text-decoration: underline; }

.ag-row-link:focus-visible {
  outline: 3px solid var(--accent);
  outline-offset: 2px;
}

/* The line under a tick that says why it is asked, kept close to it. */
.ag-consent-hint { margin-top: var(--space-1); }

.ag-tag {
  margin-left: var(--space-1);
  color: var(--accent-ink);
  font-size: var(--text-micro);
  font-weight: 600;
}

.ag-status--agreed { color: var(--ag-success); }

.ag-fingerprint {
  margin-top: var(--space-1);
  color: var(--fg-secondary);
  font-size: var(--text-micro);
  line-height: 1.5;
}

.ag-fingerprint code {
  font-family: var(--font-mono);
  overflow-wrap: anywhere;
}

/* ---- The legal text, set where the decision is made, in sentences. -------- */
.ag-legal {
  margin-top: var(--space-3);
  padding: var(--space-3);
  border-radius: var(--ag-radius);
  background: var(--ag-fill);
  font-size: var(--text-small);
  line-height: 1.55;
}

.ag-legal-title {
  font-size: var(--text-small);
  font-weight: 600;
}

.ag-legal p { margin-top: var(--space-1); }
.ag-legal p + p { margin-top: var(--space-2); }

/* The consent: the whole row is the target, the box is the platform's, and a
   ticked row is outlined in accent as well as ticked — two cues. */
.ag-consent {
  margin-top: var(--space-3);
  min-height: var(--ag-control-h);
  padding: var(--space-2);
  display: flex;
  align-items: flex-start;
  gap: var(--space-2);
  border: 1px solid var(--ag-field-border);
  border-radius: var(--ag-radius);
  cursor: pointer;
}

.ag-consent:has(input:checked) { border-color: var(--accent); }

.ag-consent input {
  flex: none;
  width: 24px;
  height: 24px;
  margin: 0;
  accent-color: var(--accent);
}

.ag-consent span {
  font-size: var(--text-body);
  font-weight: 600;
  line-height: 1.4;
}

/* ---- Fields. A box with an edge you can see, 17px type so no phone zooms. --- */
.ag-field {
  margin-top: var(--space-3);
  display: flex;
  flex-direction: column;
  gap: var(--space-1);
}

.ag-field label {
  font-size: var(--text-small);
  font-weight: 600;
}

.ag-hint {
  color: var(--fg-secondary);
  font-size: var(--text-micro);
}

.ag-input {
  min-height: var(--ag-control-h);
  padding: 0 var(--space-2);
  border: 1px solid var(--ag-field-border);
  border-radius: var(--ag-radius-small);
  background: var(--bg);
  color: var(--fg);
  font-family: inherit;
  font-size: var(--text-body);
}

textarea.ag-input {
  min-height: 96px;
  padding-block: var(--space-1);
  line-height: 1.4;
  resize: vertical;
}

.ag-input[aria-invalid="true"] { border-color: var(--ag-danger); }

.ag-code {
  max-width: 14rem;
  font-family: var(--font-mono);
  font-size: var(--text-lead);
  font-variant-numeric: tabular-nums;
  letter-spacing: 0.12em; /* six digits read as six, not one number */
}

/* ---- Messages. Said in words; the colour only repeats it. ------------------ */
.ag-error {
  margin-top: var(--space-2);
  color: var(--ag-danger);
  font-size: var(--text-small);
  font-weight: 600;
}

.ag-error[hidden] { display: none; }

/* ---- Buttons, as the app sets them: one filled, one bordered. -------------- */
.ag-actions {
  margin-top: var(--space-4);
  display: flex;
  flex-direction: column;
  gap: var(--space-2);
}

/* Side by side where there is room, the primary trailing as on Apple's
   platforms; stacked on a phone with the primary first, which is also the
   reading order. */
@media (min-width: 36rem) {
  .ag-actions { flex-direction: row-reverse; }
  .ag-actions .ag-button { flex: 1; }
}

.ag-button {
  min-height: var(--ag-control-h);
  padding: 0 var(--space-3);
  display: inline-flex;
  align-items: center;
  justify-content: center;
  border: 1px solid transparent;
  border-radius: var(--ag-radius);
  font-family: inherit;
  font-size: var(--text-body);
  font-weight: 600;
  text-align: center;
  text-decoration: none;
  cursor: pointer;
}

.ag-button--primary {
  background: var(--accent);
  color: var(--ag-on-accent);
}

.ag-button--primary:hover { background: var(--accent-ink); }

.ag-button--secondary {
  border-color: var(--ag-field-border);
  background: var(--bg);
  color: var(--fg);
}

.ag-button--secondary:hover { background: var(--ag-fill); }

.ag-button--plain {
  min-height: 44px;
  padding: 0;
  background: none;
  color: var(--accent-ink);
}

.ag-button--small {
  min-height: 44px;
  padding: 0 var(--space-2);
}

.ag-button:disabled {
  cursor: default;
  opacity: 0.5;
}

/* One focus ring for everything you can act on: visible on white, outside
   the control, never removed. */
.ag-button:focus-visible,
.ag-input:focus-visible,
.ag-consent:focus-within,
.ag-footer a:focus-visible {
  outline: 3px solid var(--accent);
  outline-offset: 2px;
}

.ag-input:focus { border-color: var(--accent); }

@media (prefers-reduced-motion: no-preference) {
  .ag-button,
  .ag-input,
  .ag-consent { transition: background-color var(--duration-fast) var(--ease), border-color var(--duration-fast) var(--ease); }
}

/* ---- The settled state. ------------------------------------------------------ */
.ag-mark {
  width: 56px;
  height: 56px;
  margin-bottom: var(--space-2);
  display: block;
}

.ag-mark--agreed { color: var(--ag-success); }
.ag-mark--declined { color: var(--fg-secondary); }

/* ---- Motion. Every movement says what changed, and none decorates.
   - Arrival: the card rises, its bars rise left to right as a track starts,
     the lit ones sweep in to the share, and the number counts up to it. Once.
   - A step: the share card and the progress stay still; the bar fills to the
     next step and the step slides in from the side you are moving toward.
   - A wrong code shakes the field, as the passcode screen does.
   - Waiting: the button carries a small spinner while the code is sent.
   - Accepted: the mark draws itself, a brief burst leaves it, the card comes
     back and "Accepted" settles in.
   With reduced motion asked for, all of it is a short cross-fade, and nothing
   counts, shakes, spins or bursts. Durations come from the site's tokens or
   the three declared here. --------------------------------------------------- */
html.agreement {
  --ag-duration-step: 320ms;
  --ag-duration-arrive: 600ms;
  --ag-ease-settle: cubic-bezier(0.34, 1.4, 0.64, 1);
}

/* The progress bar fills rather than switches: an accent layer over the
   track, grown to full width for a done or current step. */
.ag-steps li::before {
  background:
    linear-gradient(var(--accent), var(--accent)) left / 0% 100% no-repeat,
    var(--separator);
}

.ag-steps li.is-done::before,
.ag-steps li[aria-current="step"]::before {
  background:
    linear-gradient(var(--accent), var(--accent)) left / 100% 100% no-repeat,
    var(--separator);
}

.ag-button.is-busy::before {
  content: "";
  width: 16px;
  height: 16px;
  margin-right: var(--space-1);
  border: 2px solid var(--ag-on-hero-line);
  border-top-color: currentColor;
  border-radius: 50%;
}

.ag-sparks {
  position: relative;
  width: 56px;
  height: 56px;
  margin-bottom: var(--space-2);
}

.ag-sparks .ag-mark { margin: 0; }

.ag-spark {
  position: absolute;
  top: 50%;
  left: 50%;
  width: 8px;
  height: 8px;
  margin: -4px 0 0 -4px;
  border-radius: 50%;
  background: var(--accent);
  opacity: 0;
}

.ag-spark:nth-child(3n) { background: var(--ag-hero-to); }
.ag-spark:nth-child(3n + 1) { background: var(--ag-success); }

@media (prefers-reduced-motion: no-preference) {
  .ag-share.is-arriving { animation: ag-rise 500ms var(--ease-out) both; }
  .ag-share.is-arriving .ag-wave span {
    animation: ag-bar var(--ag-duration-arrive) var(--ease-out) both;
    animation-delay: calc(200ms + var(--i) * 18ms);
  }
  .ag-share.is-arriving .ag-wave span.is-lit {
    animation:
      ag-bar var(--ag-duration-arrive) var(--ease-out) both,
      ag-light 500ms var(--ease-out) both;
    animation-delay: calc(200ms + var(--i) * 18ms), calc(500ms + var(--i) * 18ms);
  }

  .ag-steps li::before { transition: background-size 500ms var(--ease-out); }

  .ag-stage.is-forward { animation: ag-in-forward var(--ag-duration-step) var(--ease-out) both; }
  .ag-stage.is-back { animation: ag-in-back var(--ag-duration-step) var(--ease-out) both; }

  .ag-input.is-shaking { animation: ag-shake 420ms var(--ease) both; }

  .ag-button.is-busy::before { animation: ag-spin 700ms linear infinite; }

  .ag-mark.is-drawing circle,
  .ag-mark.is-drawing path {
    stroke-dasharray: 1;
    animation: ag-draw 500ms var(--ease-out) both;
  }
  .ag-mark.is-drawing path { animation-delay: 300ms; }

  .ag-spark { animation: ag-burst 900ms var(--ease-out) 500ms both; }

  .ag-share.is-accepted { animation: ag-rise 500ms var(--ease-out) 200ms both; }
  .ag-share.is-accepted .ag-share-badge { animation: ag-settle 500ms var(--ag-ease-settle) 700ms both; }
}

@media (prefers-reduced-motion: reduce) {
  .ag-stage.is-forward,
  .ag-stage.is-back,
  .ag-share.is-arriving,
  .ag-share.is-accepted { animation: ag-fade 200ms var(--ease) both; }
}

@keyframes ag-rise { from { opacity: 0; transform: translateY(16px); } }
@keyframes ag-fade { from { opacity: 0; } }
@keyframes ag-bar { from { transform: scaleY(0.08); } }
@keyframes ag-light { from { background-color: var(--ag-on-hero-line); } }
@keyframes ag-in-forward { from { opacity: 0; transform: translateX(24px); } }
@keyframes ag-in-back { from { opacity: 0; transform: translateX(-24px); } }
@keyframes ag-shake {
  20% { transform: translateX(-8px); }
  40% { transform: translateX(8px); }
  60% { transform: translateX(-4px); }
  80% { transform: translateX(4px); }
}
@keyframes ag-spin { to { transform: rotate(360deg); } }
@keyframes ag-draw { from { stroke-dashoffset: 1; } to { stroke-dashoffset: 0; } }
@keyframes ag-burst {
  0% { opacity: 1; transform: rotate(var(--a)) translateY(0) scale(1); }
  100% { opacity: 0; transform: rotate(var(--a)) translateY(calc(var(--d) * -1)) scale(0.4); }
}
@keyframes ag-settle { from { opacity: 0; transform: scale(0.8); } }

/* ---- Footer: the imprint and the two legal pages, nothing to wander off to. - */
.ag-footer {
  max-width: var(--ag-column);
  margin: 0 auto;
  padding: var(--space-4) var(--gutter) var(--space-6);
  border-top: 1px solid var(--separator);
  color: var(--fg-secondary);
  font-size: var(--text-micro);
}

.ag-footer nav {
  margin-top: var(--space-1);
  display: flex;
  flex-wrap: wrap;
  gap: 0 var(--space-2);
}

.ag-footer a {
  min-width: 44px;  /* a short word ("Terms") is still a 44pt target */
  min-height: 44px;
  display: inline-flex;
  align-items: center;
  color: var(--fg-secondary);
  text-decoration: underline;
}

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

.site-footer { padding-block: var(--space-8); }

/* The small print is a stack, not a sentence: where to go next, then the
   imprint, then the stamp. 8px inside the stack so the three rows read as one
   block; the links row carries the 64px separating the block from the action. */
.footer-links,
.colophon {
  color: var(--fg-secondary);
  font-size: var(--text-micro);
}

.footer-links { margin-top: var(--space-8); }

/* Smaller type does not get to mean a smaller target — the rule the related
   shelf already states, applied to the one navigation that never got it. At
   micro size these two were 36×15 and 43×15, the smallest targets on the site.

   Padding and an equal negative block margin grow the target while nothing on
   screen moves. The horizontal padding is the sanctioned 4px, spent on the
   finger rather than the eye, and it also widens the gap between two adjacent
   targets, which HIG asks for separately.

   **This rule used to claim it produced 31×44 and it produced 37px of height**
   — 8px of padding either side of a 21px line box is 37, not 44, and the
   arithmetic was never done. `check-layout.py` measured it on 2026-08-09
   across all fourteen pages of both editions, which is how a false claim
   sitting in a comment for weeks became a finding. The old note went on to
   justify stopping short on the grounds that the colophon sat 8px below and a
   taller hit area would send a stray tap to /about. That reasoning was sound
   and the premise was cheap to change: the colophon takes 16px now — one step
   on the same grid — so the target reaches a true 45px with 4px still between
   it and the copyright line. WCAG 2.2 would have exempted these as inline
   text; HIG asks for 44 on a navigation control, `engineer.md` asks for both,
   and the honest reading is that a <nav> is a control.

   The height comes from `min-height` and nothing is pulled back with a
   negative margin. A -12px margin recovered the old rhythm and was itself an
   off-grid authored value — the exact thing design.md forbids, written into
   the fix for a different rule. 44 is not a multiple of 8 and never will be,
   so the only way to honour both laws is to let the target set the height and
   let the row be as tall as the target: the footer gains 23px, once, at the
   very bottom of the page. */
.footer-links .link-quiet {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-height: 44px;
  /* **Both dimensions, and the width is the one a font can take away.** The
     first version of this rule set only the height and passed every local
     run, because macOS renders "About" at exactly 44px wide. The daily live
     check found it 42px on the CI runner's Linux font stack on its first
     run — the same label, a narrower face, a target under the minimum. A
     44pt target that depends on which font resolved is not a 44pt target,
     and the site deliberately uses the system stack, so the metrics are the
     visitor's, not ours. A floor makes it the visitor's regardless. */
  min-width: 44px;
  padding-inline: 0.25rem;
}

.colophon { margin-top: var(--space-2); }

/* The stamp sits last, the way a generated-on line does on a printed document.
   Mono, because it is numerals. Monospaced figures also mean the digits change
   without the line reflowing — a proportional face would jitter every second.
   Hidden until the script fills it, so no empty element without JavaScript. */
.stamp {
  display: block;
  margin-top: var(--space-1);
  color: var(--fg-secondary);
  font-family: var(--font-mono);
  font-size: var(--text-micro);
  letter-spacing: 0.04em;
}

/* --------------------------------------------------------------------------
   Reduced motion — reduce, never remove
   -------------------------------------------------------------------------- */

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

  .action:hover .arrow { transform: none; }

  .appearance .icon { transform: none; }
}

/* --------------------------------------------------------------------------
   Print

   Only the split sheet page has anything worth printing, and on that page only
   the sheet itself is. Everything explaining how to use it is scaffolding for
   the screen — printed, it would be four pages of preamble in front of the one
   page somebody actually needs to sign.

   Scoped to .sheet-page so no other page acquires print behaviour by accident.
   -------------------------------------------------------------------------- */

@media print {
  /* The sheet is a legal-ish document that gets photographed, emailed and
     filed. It is black on white wherever it is printed from, regardless of the
     scheme the reader had on screen — a dark-mode print is unreadable on paper
     and wastes the toner making itself so. */
  .sheet-page {
    background: #fff;
    color: #000;
    --fg: #000;
    --fg-secondary: #000;
    --separator: rgb(0 0 0 / 45%);
  }

  .sheet-page .site-header,
  .sheet-page .skip-link,
  .sheet-page .hero,
  .sheet-page .section--guide,
  .sheet-page .site-footer { display: none; }

  .sheet-page .section--sheet { padding-block: 0; }

  /* The rubric survives as the document's title — it is the only heading left
     once the page furniture is gone. Its numeral does not: "01" numbers a
     section of a web page, and printed there is only one. */
  .sheet-page .rubric-index { display: none; }

  .sheet-page .container {
    max-width: none;
    padding-inline: 0;
  }

  .sheet-page .sheet { max-width: none; }

  /* A party block that breaks across a page boundary is the one failure that
     makes a printed form unusable — half the fields on one sheet, the signature
     on another, and no way to tell they belong together. A checklist line
     split from its box fails the same way, and so does a clause split from
     its number — the terms block is the one block that can outgrow a page, in
     which case an engine breaks it regardless and the per-clause rule is what
     is left holding. */
  .sheet-block,
  .check-list li,
  .sheet-terms li,
  .sheet-sign > div { break-inside: avoid; }

  /* The totals readout reports live state, and on paper there is no live state
     — it prints whatever happened to be on screen and then claims it forever.
     The blank total on the form is the one that gets filled in by hand. */
  .sheet-total { display: none; }

  .sheet-field input {
    /* Borders are dropped by some engines under print colour adjustment, and a
       field with no rule is an invisible one. */
    -webkit-print-color-adjust: exact;
    print-color-adjust: exact;
    border-bottom: 1px solid rgb(0 0 0 / 45%);

    /* 44px is the HIG touch minimum and paper has no touch. Screen spacing
       printed straight ran the sheet to 2.6 pages, and break-inside on the
       party blocks would have rounded that up to four — a four-page split
       sheet is one nobody prints twice. At 32px it lands on two, which is
       what a four-writer sheet should be, and there is still more room to
       write in than a ruled notebook gives. */
    min-height: 32px;
  }

  /* The same trade, applied to the gaps. Every value here is still a token —
     the grid is tightened, not abandoned, so the printed rhythm is the screen
     rhythm one step down rather than a second layout with its own arithmetic. */
  .sheet-grid { gap: var(--space-2) var(--space-4); }

  .sheet-block { margin-top: var(--space-3); }

  .sheet-page .rubric { margin-bottom: var(--space-3); }

  .sheet-sign { margin-top: var(--space-4); }

  .sheet-sign > div { padding-top: var(--space-6); }

  @page { margin: 16mm; }
}
