/*
  kingstrikers.com — the whole site's styles, in one file.

  The site has no build step, so this is the shared layer: every page links it and
  adds nothing of its own. One file means one place to change a colour and one
  request to make, and at this size (a few kB gzipped) splitting it would cost
  more in round trips than it saves in bytes.

  The vocabulary is small on purpose:

    .topbar   the menu, on every page
    .band     a full-bleed picture with a navy wash and words on top
    .slab     a solid navy section: cards, lists, tables. No picture.
    .card     the game's box: a dark field inside a yellow contour
    .btn      the sticker button from the style guide

  A page is a stack of .band and .slab, alternating. That alternation is the
  whole design: a picture to look at, then something to read, then another
  picture. Nothing else is needed and nothing else is here.
*/

/* ─────────────────────────────────────────────────────────────────────────────
   TOKENS

   Copied from client/src/ks/tokens.css rather than imported: this page ships no
   build step and no client code, and two files that agree today are cheaper here
   than a bundler. If the palette moves, move it here too — there is no mechanism
   that will notice.

   The contrast ratios in the comments are against the surface each colour is
   used on, and site.test.mjs recomputes every one of them out of this file.

   THE BODY FACE NOW MATCHES THE GAME. On 2026-09-20 the client's body face
   became Rubik, because the owner's read was that the UI "feels very Word
   document" — and `system-ui` on Windows is Segoe UI, which is precisely the
   face that judgement was about, so this page was the worse offender of the
   two. Done the way the note above predicted: the variable woff2 is committed
   to public/font/ and declared beside Barlow Condensed's, because this folder
   has no npm and no build step. One file covers every weight the page uses —
   the axis is 300-900 and the page only ever asks for 400 and 700.
   ───────────────────────────────────────────────────────────────────────────── */
:root {
  --ks-navy: #0e2050; /* paper 15.66:1 · yellow 10.80:1 */
  --ks-navy-raised: #16306b;
  --ks-navy-deep: #0a1737; /* the footer, and the bottom of a slab */
  --ks-yellow: #ffd21e; /* ink 12.61:1 */
  --ks-yellow-press: #f5b800;
  --ks-ink: #101425; /* paper 18.28:1 */
  --ks-ink-muted: #5a6480; /* paper 5.88:1 */
  --ks-paper: #ffffff;
  /*
    Muted text on navy is a COLOUR, not an opacity. `opacity: 0.7` on white gives
    a ratio nothing can check, because the number depends on what is behind it;
    over a picture that is unknowable. This blue is 10.03:1 on navy and 5.2:1 on
    the worst scrim the art can produce, and both are testable.
  */
  --ks-sky: #a9c6ff;

  /*
    THE SCRIM, AND WHY IT IS THIS STRONG.

    The backdrops are illustration, and illustration is not a controlled surface:
    the art behind any given word may be a navy sky or a floodlit white shirt. So
    the contrast of the text is not a property of the art, it is a property of
    this wash — and it has to hold for the worst pixel the art could ever
    contain, which is pure white.

    Over white, 0.78 navy composites to #434F76: white text 7.8:1, yellow 5.4:1,
    sky blue 4.7:1. All three clear AA at normal size, and they clear it for ANY
    art, so a picture can be swapped without re-testing the type.

    --scrim-top/mid/bottom are the hero's gradient, which only ever adds darkness
    downwards, so the top stop is the worst case and the top stop is the number
    the test judges. --scrim-band is the flat wash on every other picture: a band
    is short, its text sits in the middle, and a ramp across 40vh would be doing
    its darkening where nothing is written.
  */
  --scrim-top: 0.78;
  --scrim-mid: 0.86;
  --scrim-bottom: 0.93;
  --scrim-band: 0.82;

  /*
    THE WASH UNDER A BOX'S NAME (round twelve, 2026-09-27). Home's boxes letter the
    name over the game's picture, bottom-left, as the game does. The name only ever
    starts in the lower part of the picture, where a navy-deep ramp has reached at
    least this strength, and at this strength white still clears AA over a pure
    white pixel. site.test.mjs checks the sum.
  */
  --box-shade: 0.66;
  /*
    SQUARE, like the game (review five, 2026-09-26). The client zeroed its radius
    tokens ("Square everywhere, and one display face"; "Pills are square too"), and
    a rounded site beside a square game read as a different product. Kept as a
    token so every card, stat, warning and accordion follows one value.
  */
  --radius: 0;
  /* the topbar's height, so an anchor can clear it — see scroll-margin-top */
  --bar: 78px;
}

@font-face {
  font-family: 'Barlow Condensed';
  font-style: normal;
  font-weight: 700;
  font-display: swap;
  src: url('/font/barlow-condensed-latin-700-normal.woff2') format('woff2');
}

/* One variable file for the whole body axis. The weight range is what the file
   really carries; declaring a wider one lets the browser synthesise past the
   ends. `format('woff2')`, NOT the `woff2-variations` string fontsource emits:
   that one is from a withdrawn draft, and a parser that rejects it drops the
   whole src and falls back to system-ui silently — the exact failure this
   change exists to undo. Plain `woff2` loads a variable file everywhere. */
@font-face {
  font-family: 'Rubik Variable';
  font-style: normal;
  font-weight: 300 900;
  font-display: swap;
  src: url('/font/rubik-latin-wght-normal.woff2') format('woff2');
}

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

html {
  scroll-behavior: smooth;
}

body {
  margin: 0;
  background: var(--ks-navy);
  color: var(--ks-paper);
  font-family: 'Rubik Variable', system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif;
  font-size: 1rem;
  line-height: 1.6;
  -webkit-font-smoothing: antialiased;
  overflow-x: hidden;
}

h1,
h2,
h3,
.kicker,
.btn,
.stat__n {
  font-family: 'Barlow Condensed', system-ui, sans-serif;
  font-weight: 700;
  text-transform: uppercase;
  line-height: 1.05;
  letter-spacing: 0.01em;
}

/*
 * The head band's title is the page's one <h1>; every other title on the page is an
 * <h2>. They are the same size on purpose -- the heading level is there for Google and
 * for screen readers, and it is not allowed to change what the page looks like.
 */
h1,
h2 {
  margin: 0;
  font-size: clamp(2rem, 6.2vw, 3.2rem);
  /* the same as h3 below: "TEN PLACES, RUN BY THE PEOPLE / IN THEM" left one word
     alone on the second line (review six) */
  text-wrap: balance;
}

h3 {
  margin: 0 0 8px;
  font-size: clamp(1.15rem, 3.4vw, 1.4rem);
  letter-spacing: 0.03em;
  /*
    Splits a two-line heading down the middle instead of filling line one and
    leaving one orphaned word on line two. "Get a job, buy your / boots" was the
    complaint, and there were three of them in one row.
  */
  text-wrap: balance;
}

p {
  margin: 0;
}

a {
  color: inherit;
}

img {
  max-width: 100%;
}

:focus-visible {
  /*
    Two bands, ink then yellow, always. Yellow alone disappears on a yellow
    button; ink alone disappears against the navy scrim. The pair always has one
    band that holds, whichever surface it lands on.
  */
  outline: 3px solid var(--ks-ink);
  outline-offset: 2px;
  box-shadow: 0 0 0 6px var(--ks-yellow);
  border-radius: var(--radius);
}

.skip {
  position: absolute;
  left: -9999px;
  top: 0;
  z-index: 100;
  padding: 12px 18px;
  background: var(--ks-yellow);
  color: var(--ks-ink);
  font-weight: 700;
  text-decoration: none;
}

.skip:focus {
  left: 8px;
  top: 8px;
}

/* ─────────────────────────────────────────────────────────────────────────────
   THE TOPBAR

   Fixed, because the whole point of the menu is that it is reachable from the
   middle of a long page. It is SOLID navy. It was translucent with a blur, and
   when a white card scrolled under it the bar turned a washed grey-blue behind
   the logo and the Menu button (review five, 2026-09-26). A bar that changes
   colour with whatever is under it is not the same bar on every screen.
   ───────────────────────────────────────────────────────────────────────────── */
.topbar {
  position: fixed;
  inset: 0 0 auto;
  z-index: 50;
  display: flex;
  align-items: center;
  gap: 14px;
  min-height: var(--bar);
  padding: 8px max(14px, env(safe-area-inset-left)) 8px max(14px, env(safe-area-inset-right));
  background: var(--ks-navy);
  border-bottom: 1px solid rgb(255 255 255 / 0.12);
}

/*
  THE MARK IN THE BAR IS THE OWNER'S LOGO, WHOLE.

  It was the crown on its own for a while, with the words "King Strikers" set in
  type beside it, because the full logo is a stacked lockup and a stacked lockup
  does not fit a slim bar. That was the wrong trade and it was not mine to make:
  the logo is the owner's, it is used as given, and a substitute mark is a
  branding decision rather than a layout one.

  So the bar grew instead. The logo carries its own wordmark, so there is no
  text beside it to repeat.
*/
.topbar__brand {
  display: flex;
  align-items: center;
  flex: 0 0 auto;
  min-height: 44px;
  padding: 0 6px;
  text-decoration: none;
}

.topbar__brand img {
  width: auto;
  height: 58px;
  display: block;
}

.topbar__toggle {
  display: none;
  margin-left: auto;
  padding: 9px 14px;
  border: 2px solid var(--ks-paper);
  border-radius: var(--radius);
  background: transparent;
  color: var(--ks-paper);
  font: inherit;
  font-weight: 700;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  cursor: pointer;
}

/*
  THE MENU SITS IN THE MIDDLE OF THE BAR.

  A three-column grid with equal outer columns, rather than absolute positioning:
  `1fr auto 1fr` puts the middle column dead centre of the viewport by
  construction, because the two flanking columns are always the same width
  whatever the logo and the button measure. It also cannot overlap them, which
  an absolutely centred list eventually would.

  The Play button had to come OUT of <nav> for this: it is a link to a different
  site rather than a navigation item, so it was always slightly wrong in there,
  and out here it can hold the third column on its own.
*/
@media (min-width: 881px) {
  .topbar {
    display: grid;
    grid-template-columns: 1fr auto 1fr;
  }

  .topbar__brand {
    grid-column: 1;
    justify-self: start;
  }

  .nav {
    grid-column: 2;
    justify-self: center;
  }

  .topbar__play {
    grid-column: 3;
    justify-self: end;
  }
}

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

.nav__list {
  display: flex;
  align-items: center;
  gap: 2px;
  margin: 0;
  padding: 0;
  list-style: none;
}

/*
  THE MENU IS THE GAME'S TABS (round twelve, 2026-09-27): uppercase Barlow Condensed
  at the size of the game's `.ks-menutab`, with a 4px underline that only the current
  page fills. The game also dims the tabs it is not on; this bar does not, because a
  dimmed white would be a contrast nothing can check.

  12px over the text and 8px plus the 4px line under it, on a 27px line, is 51px
  tall: the 44px target minimum, cleared on a laptop as well as a phone, because a
  trackpad is not a precise instrument either.
*/
.nav__list a {
  display: block;
  padding: 12px 12px 8px;
  border-bottom: 4px solid transparent;
  border-radius: var(--radius);
  color: var(--ks-paper);
  font-family: 'Barlow Condensed', system-ui, sans-serif;
  font-size: 1.06rem;
  font-weight: 700;
  letter-spacing: 0.03em;
  text-transform: uppercase;
  text-decoration: none;
  white-space: nowrap;
}

.nav__list a:hover {
  color: var(--ks-yellow);
}

/*
  THE CURRENT PAGE IS YELLOW, UNDERLINED, AND NEVER A PILL.

  It was a filled yellow pill, borrowed from the game's own chrome. The owner's
  objection is a good one and it is about affordance rather than taste: on this
  site the only other yellow pill is the Play button, so the marker for "you are
  already here" looked exactly like the one thing on the page worth pressing.
  Two identical shapes, opposite meanings.

  It was then bold yellow text, until round twelve made every tab the same weight.
  Now it is the game's own marker: yellow text on a 4px yellow underline. A line
  under a word is not a filled shape, so it cannot be taken for the Play button.
  Yellow on the bar's solid navy is 10.8:1.
*/
.nav__list a[aria-current='page'] {
  color: var(--ks-yellow);
  border-bottom-color: var(--ks-yellow);
}

/* ─────────────────────────────────────────────────────────────────────────────
   THE MENU ON A PHONE

   The list is visible by default and JavaScript COLLAPSES it. The other way
   round — hidden by default, revealed by script — leaves a visitor whose script
   failed with a menu that is in the markup and cannot be opened. `js` is set by
   site.js while the head is parsed, before the body paints, so there is no flash.
   ───────────────────────────────────────────────────────────────────────────── */
@media (max-width: 880px) {
  .topbar {
    flex-wrap: wrap;
  }

  .js .topbar__toggle {
    display: block;
  }

  /* logo, then Play, then Menu, with the list dropping below all three. The
     source order is logo, Menu, list, Play, which is the order a keyboard
     should meet them in; `order` is only rearranging the picture. */
  .topbar__brand {
    order: 1;
  }

  .topbar__play {
    order: 2;
    margin-left: auto;
  }

  .topbar__toggle {
    order: 3;
    margin-left: 0;
  }

  .nav {
    order: 4;
    width: 100%;
    flex-direction: column;
    align-items: stretch;
    gap: 6px;
    margin: 6px 0 4px;
  }

  .js .nav[hidden] {
    display: none;
  }

  /* the tabs stack, and each one is only as wide as its word, so the current
     page's underline sits under the word rather than across the screen */
  .nav__list {
    flex-direction: column;
    align-items: flex-start;
    gap: 2px;
  }

  .nav__list a {
    padding: 12px 14px 8px;
    font-size: 1.12rem;
  }

}

/* ─────────────────────────────────────────────────────────────────────────────
   BUTTONS — the sticker from the style guide: yellow face, ink text, a 2px ink
   line and a darker bottom edge that collapses when it is pressed. Yellow never
   carries white — that pair is 1.45:1.
   ───────────────────────────────────────────────────────────────────────────── */
.btn {
  display: inline-block;
  padding: 13px 30px;
  border: 2px solid var(--ks-ink);
  border-radius: var(--radius);
  background: var(--ks-yellow);
  box-shadow: 0 4px 0 0 var(--ks-ink);
  color: var(--ks-ink);
  font-size: 1.12rem;
  letter-spacing: 0.06em;
  text-decoration: none;
  cursor: pointer;
  transition: transform 120ms ease, box-shadow 120ms ease, background-color 120ms ease;
}

.btn:hover {
  background: var(--ks-yellow-press);
}

.btn:active {
  transform: translateY(4px);
  box-shadow: 0 0 0 0 var(--ks-ink);
}

.btn--big {
  padding: 16px 44px;
  font-size: clamp(1.3rem, 5vw, 1.55rem);
}

.btn--small {
  padding: 12px 20px;
  font-size: 0.98rem;
  box-shadow: 0 3px 0 0 var(--ks-ink);
}

/* the second button in a pair: no fill, so the yellow one stays the loud one */
.btn--ghost {
  background: transparent;
  border-color: var(--ks-paper);
  box-shadow: 0 4px 0 0 rgb(6 14 36 / 0.55);
  color: var(--ks-paper);
}

.btn--ghost:hover {
  background: rgb(255 255 255 / 0.12);
}

/* ─────────────────────────────────────────────────────────────────────────────
   BANDS — a picture, a wash, and words
   ───────────────────────────────────────────────────────────────────────────── */
/*
  THE HEIGHT OF A BAND IS A FUNCTION OF THE WIDTH, NOT THE VIEWPORT.

  A band crops its picture with `cover`, so the taller the band the more of the
  picture survives. The first version was `min(78vh, 620px)`, which on a 2560px
  ultrawide left a 620px strip across a picture that had been scaled to 1707px
  tall — about a third of it, and the wrong third.

  `clamp(560px, 42vw, 860px)` ties the height to the width instead: the wider the
  screen, the taller the band, so the crop stays roughly proportional and the art
  keeps its shape. It stops at 860px so a band never eats a whole laptop screen.
*/
.band {
  position: relative;
  /*
    THE PARALLAX NEEDS THIS, AND IT IS NOT OPTIONAL.

    `.drift .band__art` is 118% tall so the picture has somewhere to move. The
    navy wash is `.band::after` at `inset: 0`, which covers the BAND and not the
    overspill, so without a clip the picture hangs 50 to 70px past the top and
    bottom edges with no wash over it: a clear strip of artwork, then a hard line,
    then the washed part. That shipped, and it looked exactly as bad as it sounds.

    Clipping here is the whole fix. It keeps every visible pixel of art inside the
    rectangle the scrim covers, which is the invariant the contrast tests assume.
  */
  overflow: hidden;
  display: flex;
  align-items: center;
  justify-content: center;
  isolation: isolate;
  min-height: clamp(560px, 42vw, 860px);
  padding: clamp(64px, 12vh, 130px) 16px;
  text-align: center;
  scroll-margin-top: var(--bar);
}

/*
  `display: contents` makes the <picture> box itself disappear and hands its <img>
  straight to the band's layout, so the absolutely positioned art below behaves
  exactly as it did before the two orientations existed.

  The <picture> is what makes the art adaptive: its <source> carries the upright
  frame behind `(orientation: portrait)`, and the <img> carries the wide one. The
  browser picks one and downloads one.
*/
.band > picture {
  display: contents;
}

/*
  The art is an <img> rather than a background-image for two reasons: `loading`
  works on it, so a band five screens down costs nothing until it is nearly in
  view, and `alt=""` states plainly to a screen reader that it is decoration.
*/
.band__art {
  position: absolute;
  inset: 0;
  z-index: -2;
  width: 100%;
  height: 100%;
  object-fit: cover;
  /*
    DEAD CENTRE, and it has to be. `center 60%` was right for the first set of
    art, which put its figures low in the frame; the redrawn set puts them in the
    vertical middle so that a wide monitor — which only ever keeps a strip through
    the middle — keeps their faces. Biasing the crop downwards against art drawn
    that way cuts every head off, which is exactly what it did.
  */
  object-position: center center;
}

.band::after {
  content: '';
  position: absolute;
  inset: 0;
  z-index: -1;
  background: rgb(14 32 80 / var(--scrim-band));
}

.band__inner {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: clamp(14px, 2.4vh, 22px);
  max-width: 62ch;
}

/* the hero is taller, and its wash is a gradient rather than a flat wash */
.band--hero {
  min-height: 100svh;
  padding-top: calc(var(--bar) + 28px);
}

.band--hero::after {
  background: linear-gradient(
    180deg,
    rgb(14 32 80 / var(--scrim-top)) 0%,
    rgb(14 32 80 / var(--scrim-mid)) 55%,
    rgb(14 32 80 / var(--scrim-bottom)) 100%
  );
}

/* A second heading further down the same slab needs the air a new section would
   have given it. Privacy and the roadmap run two topics under one slab. */
.slab__next {
  margin-top: clamp(48px, 8vh, 84px);
}

/*
  THE PORTRAIT CROP USED TO BE A BODGE, AND IS NOT ANY MORE.

  On a phone held upright, `cover` on a 3:2 frame fits it by HEIGHT and throws
  away more than half the width — and the interest in this art is deliberately at
  the left and right edges, which is exactly the part that goes. The old fix was
  to zoom past 100% and anchor to the bottom, which salvaged the hero and nothing
  else.

  Every band now carries a second, upright drawing of the same scene behind
  `(orientation: portrait)`, so there is nothing left to salvage: the phone gets a
  picture composed for a phone. The rule below only still covers the case where
  the upright file is missing and the wide one is standing in for it.
*/
@media (max-aspect-ratio: 4 / 5) {
  .band--hero .band__art {
    object-position: center bottom;
  }
}

/*
  A page header. It has been raised twice now, and the second time is the lesson:
  a header band is a PICTURE, and a picture in a strip is a picture you have
  ruined. At 460px the sub-page banners still cropped their art down to a letterbox
  and looked cheap for it.

  It is now within a hair of a full band, which is the honest answer — the only
  reason to make it shorter at all is that a sub-page should start reading sooner
  than the home page does.
*/
.band--head {
  min-height: clamp(540px, 40vw, 820px);
  padding-top: calc(var(--bar) + 40px);
}

/*
  THE HEADS SIT HIGH IN A HEADER PICTURE (21 October audit). The header art is
  centred, and on a wide screen a centred crop keeps the middle strip and throws
  away the top, which is where the faces are: the shredder's head, the referee's
  face. Anchoring at 30% keeps the faces and gives up a little floor instead. The
  parallax overscan is off here (site.js skips a head band and the rule below sizes
  its picture to the band), because a picture that is also being pushed 46px
  around loses its top edge a second time.
*/
.band--head .band__art,
.drift .band--head .band__art {
  object-position: center 30%;
}

.drift .band--head .band__art {
  height: 100%;
  top: 0;
  bottom: 0;
}

/* 404.html is one band and the footer; on a tall screen the band fills it, so the
   page does not end in a strip of empty navy under the footer */
.band--lost {
  min-height: 100vh;
  min-height: 100svh;
}

.hero__logo {
  width: min(340px, 72vw);
  height: auto;
  /* the art behind it is busy; the logo's own blue outline needs help holding */
  filter: drop-shadow(0 6px 18px rgb(6 14 36 / 0.65));
}

/*
  It grows a little under the pointer, which is the only hint that it does
  anything at all. Five clicks on it is a hidden thing; a hidden thing nobody
  suspects is there is just dead code.
*/
@media (hover: hover) and (prefers-reduced-motion: no-preference) {
  .hero__logo {
    transition: transform 220ms cubic-bezier(0.2, 0.75, 0.3, 1);
  }

  h1:hover .hero__logo {
    transform: scale(1.045);
  }
}

.kicker {
  font-size: clamp(0.9rem, 3.2vw, 1.05rem);
  letter-spacing: 0.18em;
  color: var(--ks-yellow);
}

/*
  `margin-inline: auto` on both of these, and it is not decoration.

  Each has a max-width, which makes it a BOX narrower than its parent. Inside a
  band the parent is a centred flex column, so the box lands in the middle by
  itself; inside a slab it is an ordinary block, so the box sits hard against the
  left while its text is centred within it — which reads as text that is somehow
  centred and off to one side at the same time. That is what the owner was
  looking at under the Play button.
*/
.lede {
  max-width: 46ch;
  margin-inline: auto;
  font-size: clamp(1.03rem, 2.6vw, 1.2rem);
  line-height: 1.55;
  text-wrap: balance;
}

.note {
  max-width: 52ch;
  margin-inline: auto;
  font-size: 0.88rem;
  line-height: 1.55;
  color: var(--ks-sky);
  text-align: center;
  /* two even lines rather than a full one and an orphan, which is what splitting
     "Google Play" across the break looked like */
  text-wrap: balance;
}

.band .note a,
.slab .note a {
  color: var(--ks-sky);
}

/* the arrow under the hero: something to say the page goes on */
.scroll-cue {
  position: absolute;
  bottom: 18px;
  left: 50%;
  translate: -50% 0;
  padding: 8px 12px;
  color: var(--ks-sky);
  font-size: 0.78rem;
  letter-spacing: 0.22em;
  text-transform: uppercase;
  text-decoration: none;
}

.scroll-cue span {
  display: block;
  font-size: 1.2rem;
  animation: nudge 2.4s ease-in-out infinite;
}

@keyframes nudge {
  0%,
  100% {
    transform: translateY(0);
  }
  50% {
    transform: translateY(5px);
  }
}

/* ─────────────────────────────────────────────────────────────────────────────
   SLABS — solid navy, where the reading happens
   ───────────────────────────────────────────────────────────────────────────── */
.slab {
  position: relative;
  padding: clamp(52px, 9vh, 96px) 16px;
  scroll-margin-top: var(--bar);
  /*
    THE GAME'S SEATED CROWD (round twelve, 2026-09-27): one dot per 16px seat, the
    dot and the seat the game's own (`fifa.css`, the crowd ground), in the house
    yellow over the navy. It replaced a faint diagonal streak, which in the game
    survives only as an optional club pattern; the crowd is the ground a player
    sits on every minute.

    It is decoration on a solid colour. A dot is 1.4px, smaller than any stroke of
    any letter, and even text sitting right on one clears AA (site.test.mjs).
  */
  background:
    radial-gradient(circle at 8px 8px, rgb(255 210 30 / 0.16) 1.4px, transparent 1.9px) 0 0 / 16px 16px,
    var(--ks-navy);
}

.slab--deep {
  background-color: var(--ks-navy-deep);
}

.wrap {
  max-width: 1080px;
  margin: 0 auto;
}

.wrap--narrow {
  max-width: 720px;
}

/*
  ULTRAWIDE FILLS OUT LIKE THE BANDS DO (review five, 2026-09-26).

  A band is full-bleed at every width; a slab kept a 1080px column, so on a 3440px
  monitor two thirds of every card section was empty navy and the page swapped
  between full and narrow on every scroll. From 2000px the column grows and the
  type steps up with it, so the cards keep their proportions instead of sitting
  small in the middle. Everything sized in rem follows the root size.
*/
@media (min-width: 2000px) {
  html {
    font-size: 112.5%;
  }

  .wrap {
    max-width: 1440px;
  }

  .wrap--narrow {
    max-width: 880px;
  }
}

@media (min-width: 2800px) {
  /* review 13 Oct: from 2800px the type and the column keep growing with the screen
     (21px at 2800, 26px at 3440, 32px at the cap) instead of stopping at one step, so
     a 3440px monitor is not a small island of 14px cards. The bar is in rem, so it follows. */
  html {
    font-size: clamp(21px, 0.76vw, 32px);
  }

  :root {
    --bar: 4.9rem;
  }

  /* review round 2 (site-05): the logo was a fixed 58px, so at 3440 the bar looked lost
     beside the growing text. Sized in rem it grows with the root, like the menu. */
  .topbar__brand {
    min-height: 2.75rem;
  }

  .topbar__brand img {
    height: 3.6rem;
  }

  .wrap {
    max-width: min(62vw, 2600px);
  }

  .wrap--narrow {
    max-width: min(32vw, 1400px);
  }
}

.slab h2 {
  text-align: center;
}

.slab__intro {
  max-width: 56ch;
  margin: 14px auto 0;
  text-align: center;
  color: var(--ks-sky);
}

/*
  GRIDS ARE COUNTED, NOT FITTED.

  `repeat(auto-fit, minmax(255px, 1fr))` packs as many columns as will go, which
  means the last row holds whatever is left over: four cards became three and a
  lonely one, six became four and two. The owner's note: "let's try to make sure
  that whatever aspect ratio we fix to continues being symmetrical".

  So each grid declares HOW MANY cards it holds, and the breakpoints only ever
  step between counts that divide it exactly:

    --two    1 → 2
    --three  1 → 3        (never 2, which would leave one on its own; from 760px, so a
                          fold screen gets three narrow cards, not one very wide one)
    --four   1 → 2 → 4
    --six    1 → 2 → 3

  A card with fewer words than its neighbours still fills its cell, so the row
  stays level; balancing the WORDS is the copy's job, not the grid's.
*/
.grid {
  display: grid;
  gap: 18px;
  margin-top: clamp(26px, 5vh, 44px);
  grid-template-columns: 1fr;
}

@media (min-width: 680px) {
  .grid--two,
  .grid--four,
  .grid--six {
    grid-template-columns: repeat(2, 1fr);
  }

  /*
    EVERY TITLE IN A ROW RESERVES TWO LINES.

    Balancing the wrap fixes the orphans but not the raggedness: with one
    two-line title and one one-line title beside it, the body copy of the two
    cards starts at different heights and the row reads as unfinished. Holding
    two lines for all of them lines the paragraphs up, at the cost of a little
    air under the short ones.

    Only where there is more than one card per row. On a phone each card is its
    own row and there is nothing to line up with, so the reserved space would be
    a gap for no reason.
  */
  .card h3 {
    min-height: 2.1em;
  }
}

@media (min-width: 760px) {
  .grid--three {
    grid-template-columns: repeat(3, 1fr);
  }
}

@media (min-width: 1000px) {
  .grid--six {
    grid-template-columns: repeat(3, 1fr);
  }
}

@media (min-width: 1200px) {
  .grid--four {
    grid-template-columns: repeat(4, 1fr);
  }
}

/* ─────────────────────────────────────────────────────────────────────────────
   CARDS — the game's box, on the site
   ───────────────────────────────────────────────────────────────────────────── */
/*
  THE GAME'S BOX (round twelve, 2026-09-27). The cards were white paper on the navy,
  and nothing in the game is white paper any more. A box in the game is a dark field
  inside a 3px contour in the club's colour, with no soft shadow; the site has no
  club, so its yellow is the contour, which is what the game draws for a yellow and
  navy club. On a deep slab the field steps up to the page navy so the box still
  reads as a box.

  TEXT IS LEFT-ALIGNED INSIDE, THE BOXES STAY CENTRED ON THE PAGE. The owner asked
  on 2026-09-20 for the cards to be centred ("these cards, they seem to be on the
  left. I rather if you center them"), and the grid still centres every row in the
  column. Inside a box the name and the words start at the left edge, as the game's
  boxes letter them (owner, 2026-09-26, round twelve's fourth proposal).
*/
.card {
  padding: 20px 22px 24px;
  border: 3px solid var(--ks-yellow);
  border-radius: var(--radius);
  background: var(--ks-navy-deep);
  color: var(--ks-paper);
  text-align: left;
}

.slab--deep .card {
  background: var(--ks-navy);
}

.card p + p {
  margin-top: 10px;
}

.card__muted {
  color: var(--ks-sky);
  font-size: 0.93rem;
}

/* The small label over a name (Clubs' roles, Contact's kinds of mail): yellow type
   on a yellow hairline, so it is a label and not a second button. */
.card__tag {
  display: inline-block;
  margin-bottom: 10px;
  padding: 2px 9px;
  border: 1px solid rgb(255 210 30 / 0.5);
  border-radius: var(--radius);
  color: var(--ks-yellow);
  font-size: 0.75rem;
  font-weight: 700;
  letter-spacing: 0.1em;
  text-transform: uppercase;
}

/*
  A BOX WITH A PICTURE: Home's four, wearing the game's own Home box art in the
  house kit (tools/art-gen/site-box-art.mjs). The picture runs to the contour, the
  name is lettered over it bottom-left, and the words sit underneath. Only the words
  keep the box's padding.

  16:9 until the four share one row, and 4:3 once they do. On a phone the four
  stack, and on a fold they sit two by two; a squarer picture there would make the
  section half as long again.
*/
.card--art {
  padding: 0;
}

.card__art {
  position: relative;
  aspect-ratio: 16 / 9;
  overflow: hidden;
  border-bottom: 3px solid var(--ks-yellow);
}

@media (min-width: 1200px) {
  .card__art {
    aspect-ratio: 4 / 3;
  }
}

.card__art img {
  display: block;
  width: 100%;
  height: 100%;
  object-fit: cover;
}

/* The ramp under the name: clear over the top of the picture, then navy-deep at
   --box-shade by the middle and deeper still at the foot, where the name sits. */
.card__art::after {
  content: '';
  position: absolute;
  inset: 0;
  background: linear-gradient(transparent 30%, rgb(10 23 55 / var(--box-shade)) 58%, rgb(10 23 55 / 0.9));
}

.card .card__name {
  position: absolute;
  left: 16px;
  right: 16px;
  bottom: 10px;
  z-index: 1;
  min-height: 0;
  margin: 0;
  color: var(--ks-paper);
  font-size: clamp(1.4rem, 3.6vw, 1.6rem);
  line-height: 1.02;
  text-shadow: 0 2px 0 rgb(0 0 0 / 0.5);
}

.card--art > p {
  padding: 0 22px;
}

.card--art > p:first-of-type {
  margin-top: 16px;
}

.card--art > p:last-child {
  padding-bottom: 22px;
}

/* ─────────────────────────────────────────────────────────────────────────────
   LISTS — the ticked and crossed kind, used by the roadmap and the FAQ
   ───────────────────────────────────────────────────────────────────────────── */
.ticks {
  margin: 0;
  padding: 0;
  list-style: none;
}

.ticks li {
  position: relative;
  padding-left: 30px;
}

.ticks li + li {
  margin-top: 10px;
}

.ticks li::before {
  position: absolute;
  left: 0;
  top: 0;
  font-weight: 700;
}

.ticks--done li::before {
  content: '✓';
  color: #2fbf71;
}

.ticks--next li::before {
  content: '▸';
  color: var(--ks-yellow);
}

.ticks--no li::before {
  content: '—';
  color: var(--ks-ink-muted);
}

/*
  The roadmap's "Not in the game yet" (review five, 2026-09-26). Read down the
  dashes, so it is a left-aligned column centred as a block.
  The name of each item is white, the sentence after it sky.
*/
.missing {
  max-width: 60ch;
  margin: clamp(22px, 4vh, 32px) auto 0;
  text-align: left;
}

.missing li {
  color: var(--ks-sky);
}

.missing li + li {
  margin-top: 14px;
}

.missing li::before {
  color: var(--ks-yellow);
}

.missing strong {
  color: var(--ks-paper);
}

/* ─────────────────────────────────────────────────────────────────────────────
   STATS — three or four numbers in a row
   ───────────────────────────────────────────────────────────────────────────── */
/* Flex rather than grid, so two tiles sit as a centred pair instead of stretching
   to fill a row built for five. */
.stats {
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  gap: 14px;
  margin-top: clamp(26px, 5vh, 40px);
}

.stats .stat {
  flex: 0 1 190px;
}

.stat {
  padding: 18px 14px;
  border: 2px solid rgb(255 255 255 / 0.18);
  border-radius: var(--radius);
  background: rgb(255 255 255 / 0.05);
  text-align: center;
}

.stat__n {
  display: block;
  font-size: clamp(2rem, 6vw, 2.6rem);
  color: var(--ks-yellow);
}

.stat__l {
  display: block;
  margin-top: 4px;
  font-size: 0.88rem;
  color: var(--ks-sky);
}

/* ─────────────────────────────────────────────────────────────────────────────
   Q&A and the changelog
   ───────────────────────────────────────────────────────────────────────────── */
.qa {
  margin-top: clamp(26px, 5vh, 40px);
  text-align: center;
}

/*
  A QUESTION IS A ROW, NOT A BOX (21 October audit). The site has two kinds of
  surface: the yellow-outlined card, for things to scan, and boxless text, for
  reading. A see-through grey box was a third. Rows with a hairline between them
  are boxless text, which is what a list of questions is.
*/
.qa details {
  border-top: 1px solid rgb(255 255 255 / 0.18);
}

.qa details:last-child {
  border-bottom: 1px solid rgb(255 255 255 / 0.18);
}

.qa summary {
  padding: 16px 4px;
  font-family: 'Barlow Condensed', system-ui, sans-serif;
  font-weight: 700;
  font-size: 1.16rem;
  letter-spacing: 0.02em;
  text-transform: uppercase;
  cursor: pointer;
}

.qa summary::marker {
  color: var(--ks-yellow);
}

/* The answer starts under the question's own text: the left padding is the
   disclosure arrow's width, so the two read as one column. */
.qa details > p,
.qa details > ul {
  margin: 0;
  padding: 0 4px 18px 28px;
  color: var(--ks-sky);
  /*
    An answer is LEFT-aligned, the question stays centred (review five,
    2026-09-26). Answers run to several lines on a phone, and a centred paragraph
    that long gives the eye no edge to come back to; Privacy and Terms left-align
    their prose for the same reason.
  */
  text-align: left;
}

.qa details > p + p {
  padding-top: 12px;
}

.qa details > ul {
  padding-left: 40px;
}

/* Centred like everything else, so the rule that used to run down the left is a
   divider between entries instead. */
.log {
  margin-top: clamp(26px, 5vh, 40px);
  text-align: center;
}

.log__item + .log__item {
  margin-top: 26px;
  padding-top: 26px;
  border-top: 2px solid rgb(255 255 255 / 0.14);
}

.log__item p {
  max-width: 62ch;
  margin-left: auto;
  margin-right: auto;
}

.log__date {
  font-family: 'Barlow Condensed', system-ui, sans-serif;
  font-weight: 700;
  font-size: 1rem;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--ks-yellow);
}

.log__item h3 {
  margin: 4px 0 6px;
}

.log__item p {
  color: var(--ks-sky);
}

/* ─────────────────────────────────────────────────────────────────────────────
   THE WARNING

   One thing on this site has to be read before somebody spends a month on a
   career, and it is that the alpha gets wiped. So it does not look like the rest
   of the page: yellow rule, yellow heading, its own box, and it sits inside the
   band rather than after it.

   Yellow as a border and a heading, never as a fill behind body text — the body
   text here is white, and white on yellow is 1.45:1.
   ───────────────────────────────────────────────────────────────────────────── */
.warn {
  max-width: 62ch;
  margin: clamp(6px, 1.4vh, 14px) auto;
  padding: 20px 22px;
  border: 2px solid var(--ks-yellow);
  border-radius: var(--radius);
  background: rgb(10 23 55 / 0.72);
  text-align: center;
}

.warn p + p {
  margin-top: 12px;
}

.warn__title {
  margin-bottom: 10px;
  /* two even lines, never "... WILL BE" and then RESET on its own */
  text-wrap: balance;
  line-height: 1.25;
  font-family: 'Barlow Condensed', system-ui, sans-serif;
  font-weight: 700;
  font-size: 1.5rem;
  letter-spacing: 0.08em;
  text-transform: uppercase;
  color: var(--ks-yellow);
}

.warn strong {
  color: var(--ks-yellow);
}

/* ─────────────────────────────────────────────────────────────────────────────
   PROSE — a column of plain text, used by the long pages
   ───────────────────────────────────────────────────────────────────────────── */
.prose {
  margin-top: clamp(22px, 4vh, 34px);
  text-align: center;
}

/*
  The exception, and the reason it is one: a page somebody reads to find a
  specific sentence — what is stored, how to delete it — is scanned rather than
  read, and a centred column gives the eye no fixed edge to come back to. The
  same goes for any prose of more than one short paragraph: Clubs' "Joining,
  founding, leaving" and The Game's "And if you disappear" (review six). Only a
  line or two under a heading stays centred.
*/
.prose--left {
  text-align: left;
}

.prose h3 {
  margin-top: 30px;
  color: var(--ks-yellow);
}

.prose p,
.prose li {
  color: var(--ks-sky);
}

.prose p + p {
  margin-top: 12px;
}

.prose strong {
  color: var(--ks-paper);
}

.prose a {
  color: var(--ks-paper);
}

/* A list in centred prose is centred as a block and its rows are not, because a
   bullet that moves on every line is not a bullet. */
.prose ul {
  display: inline-block;
  margin: 12px 0 0;
  padding-left: 22px;
  text-align: left;
}

.prose li + li {
  margin-top: 8px;
}

/* A paragraph after a list gets a paragraph's gap, or it reads as one more bullet
   that lost its dot (Privacy, "Who else handles it"). */
.prose ul + p {
  margin-top: 14px;
}

/*
  THE POINTER AFTER THE PROSE. "What a club actually does on a matchday is on the
  game page" sat tight under the last paragraph in smaller type and read as the end
  of that paragraph. It is a pointer for the whole page, so it gets its own air and
  a short rule above it.
*/
.prose + .note,
.missing + .note {
  margin-top: clamp(30px, 5vh, 44px);
  padding-top: 20px;
  border-top: 2px solid rgb(255 255 255 / 0.14);
}

/* ─────────────────────────────────────────────────────────────────────────────
   THE FOOTER
   ───────────────────────────────────────────────────────────────────────────── */
.foot {
  padding: 46px 16px max(34px, env(safe-area-inset-bottom));
  background: var(--ks-navy-deep);
  border-top: 1px solid rgb(255 255 255 / 0.12);
  text-align: center;
}

.foot__links {
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  gap: 6px 4px;
  margin: 0 0 18px;
  padding: 0;
  list-style: none;
}

.foot__links a {
  display: block;
  min-height: 44px;
  padding: 11px 12px;
  border-radius: var(--radius);
  color: var(--ks-sky);
  font-size: 0.94rem;
  text-decoration: none;
}

.foot__links a:hover {
  background: rgb(255 255 255 / 0.08);
  color: var(--ks-paper);
}

.foot__note {
  max-width: 52ch;
  margin: 0 auto;
  color: var(--ks-sky);
  font-size: 0.85rem;
}

.foot__note a {
  display: inline-block;
  padding-block: 12px;
  color: var(--ks-paper);
}

/* Privacy and terms (2026-09-26): two small links under the note, on every page. Not
   the menu again (the menu is the top bar, `.foot__links` is gone on purpose), just
   the two pages that live nowhere else. The padding makes each a finger-sized target. */
.foot__legal {
  margin: 10px 0 0;
  color: var(--ks-sky);
  font-size: 0.85rem;
}

.foot__legal a {
  display: inline-block;
  min-height: 44px;
  padding: 11px 6px;
  color: var(--ks-paper);
}

/* ─────────────────────────────────────────────────────────────────────────────
   TWO UTILITIES, AND NO MORE

   Everything else in this file is a named thing. These two exist so that no page
   has to carry a `style=` attribute, which is the one thing that would put a
   spacing or a colour outside this file where nothing can check it.
   ───────────────────────────────────────────────────────────────────────────── */
.prose--narrow {
  max-width: 68ch;
  margin-left: auto;
  margin-right: auto;
}

.cta-row {
  margin-top: clamp(26px, 5vh, 40px);
  text-align: center;
}

/* ─────────────────────────────────────────────────────────────────────────────
   MOTION

   Everything in this block is optional by construction. The markup is complete
   and visible without any of it; `site.js` adds the classes that start the
   animations, and it refuses to add any of them when the visitor has asked for
   reduced motion. So the "off" state is not a degraded version of the page, it
   is the page.
   ───────────────────────────────────────────────────────────────────────────── */

/* ── sections rise as you reach them ──────────────────────────────────────── */

/*
  `.rise` is added by script, never written in the markup. That is the whole
  safety argument: a stylesheet that hid sections on its own would hide them for
  anybody whose script failed, and this page would be a navy rectangle.
*/
.rise {
  opacity: 0;
  transform: translateY(44px);
}

.rise--in {
  opacity: 1;
  transform: none;
  transition: opacity 700ms ease, transform 760ms cubic-bezier(0.2, 0.75, 0.3, 1);
}

/*
  AND THE CONTENT ARRIVES AFTER THE SECTION.

  A whole section fading as one block is a surprisingly quiet effect: the eye
  reads it as the page loading rather than as anything deliberate. Staggering the
  few children inside it is what makes it look designed, and it costs four rules.

  The delays are deliberately short. This is a landing page, not a slideshow, and
  anybody scrolling at speed should never be waiting on a heading.
*/
.rise .band__inner > *,
.rise .wrap > * {
  opacity: 0;
  transform: translateY(18px);
}

.rise--in .band__inner > *,
.rise--in .wrap > * {
  opacity: 1;
  transform: none;
  transition: opacity 520ms ease, transform 560ms cubic-bezier(0.2, 0.75, 0.3, 1);
}

.rise--in .band__inner > :nth-child(2),
.rise--in .wrap > :nth-child(2) {
  transition-delay: 90ms;
}

.rise--in .band__inner > :nth-child(3),
.rise--in .wrap > :nth-child(3) {
  transition-delay: 170ms;
}

.rise--in .band__inner > :nth-child(n + 4),
.rise--in .wrap > :nth-child(n + 4) {
  transition-delay: 240ms;
}

/* ── the art drifts slower than the words over it ─────────────────────────── */

/*
  The overscan is what makes the drift possible. `inset: 0` sizes the picture to
  exactly its band, so moving it 46px up would show 46px of nothing underneath.
  118% tall, pulled up by half the excess, gives it somewhere to go in both
  directions.
*/
.drift .band__art {
  height: 118%;
  top: -9%;
  bottom: auto;
  will-change: transform;
}

/* ── the ball that follows the pointer ────────────────────────────────────── */

.ball {
  position: fixed;
  left: 0;
  top: 0;
  z-index: 90;
  width: 36px;
  height: 36px;
  /* it must never eat a click, a hover or a text selection */
  pointer-events: none;
  opacity: 0;
  filter: drop-shadow(0 3px 5px rgb(4 10 28 / 0.45));
  transition: opacity 220ms ease;
}

.ball--on {
  opacity: 1;
}

/*
  The system pointer goes away only once the ball is on screen, and comes back
  the moment the mouse leaves the window. `cursor: none` has to be repeated on
  the interactive elements because their own `cursor` declarations would
  otherwise win over an inherited one.
*/
.ball-on,
.ball-on a,
.ball-on button,
.ball-on summary,
.ball-on .btn {
  cursor: none;
}

/* the job the pointer's changing shape used to do */
.ball--over svg {
  transform: scale(1.28);
}

.ball svg {
  transition: transform 140ms ease;
}

.ball svg {
  display: block;
}

/* The outer element is moved, this one is spun. Anything pinned to the outer box
   therefore stays upright while the ball rolls. */
.ball__spin {
  width: 100%;
  height: 100%;
}

/* The squash and the pop. The spinner is being rotated by script, so the kick
   animates the SVG inside it: two transforms on one element would fight. */
.ball--kick svg {
  animation: ball-kick 320ms cubic-bezier(0.3, 1.4, 0.4, 1);
}

/* ── leave it alone and it falls asleep ───────────────────────────────────── */

.ball--doze::after {
  content: 'z';
  position: absolute;
  top: -6px;
  right: -8px;
  font-family: 'Barlow Condensed', system-ui, sans-serif;
  font-weight: 700;
  font-size: 1.1rem;
  line-height: 1;
  color: var(--ks-yellow);
  animation: doze 1.8s ease-in-out infinite;
}

.ball--doze .ball__spin {
  transition: transform 600ms ease;
}

@keyframes doze {
  0% {
    opacity: 0;
    transform: translate(0, 0) scale(0.7);
  }
  35% {
    opacity: 1;
  }
  100% {
    opacity: 0;
    transform: translate(9px, -16px) scale(1.25);
  }
}

@keyframes ball-kick {
  0% {
    transform: scale(1);
  }
  28% {
    transform: scale(1.3, 0.72);
  }
  60% {
    transform: scale(0.88, 1.16);
  }
  100% {
    transform: scale(1);
  }
}

/* ── click the crown five times ───────────────────────────────────────────── */

/*
  Two elements because the ball is doing two unrelated things at once: crossing
  the screen at a steady rate, and bouncing. One element cannot hold two
  animations on the same property.

  FIXED, not absolute inside the footer. It is triggered from the logo at the top
  of the page, so it has to play where the visitor is rather than a full screen
  below them.
*/
.kick {
  position: fixed;
  left: 0;
  bottom: 40px;
  z-index: 85;
  width: 92px;
  height: 92px;
  pointer-events: none;
  animation: kick-across 2.4s linear forwards;
}

.kick__b {
  width: 100%;
  height: 100%;
  animation: kick-bounce 0.46s cubic-bezier(0.3, 0, 0.7, 1) infinite alternate;
}

.kick svg {
  display: block;
  width: 100%;
  height: 100%;
  filter: drop-shadow(0 6px 10px rgb(4 10 28 / 0.5));
}

@keyframes kick-across {
  from {
    transform: translateX(-120px) rotate(0deg);
  }
  to {
    transform: translateX(calc(100vw + 120px)) rotate(1200deg);
  }
}

@keyframes kick-bounce {
  from {
    transform: translateY(0);
  }
  to {
    transform: translateY(-170px);
  }
}

/* ── the konami code ──────────────────────────────────────────────────────── */

.rain {
  position: fixed;
  inset: 0;
  z-index: 80;
  pointer-events: none;
  overflow: hidden;
}

.rain__b {
  position: absolute;
  top: -60px;
  width: 40px;
  height: 40px;
  animation: rain-fall linear forwards;
}

@keyframes rain-fall {
  from {
    transform: translateY(0) rotate(0deg);
  }
  to {
    transform: translateY(calc(100vh + 120px)) rotate(900deg);
  }
}

/* ── cards answer the pointer ─────────────────────────────────────────────── */

/* The game's hover: the box lifts 3px onto a hard 6px shadow in its contour colour. */
@media (hover: hover) and (prefers-reduced-motion: no-preference) {
  .card {
    transition: transform 120ms ease, box-shadow 120ms ease;
  }

  .card:hover {
    transform: translateY(-3px);
    box-shadow: 0 6px 0 0 var(--ks-yellow);
  }

  /* the tag lights up, which is the cheapest way to make a card feel answered */
  .card__tag {
    transition: background-color 120ms ease, color 120ms ease;
  }

  .card:hover .card__tag {
    background: var(--ks-yellow);
    color: var(--ks-ink);
  }
}

/* ── between pages ────────────────────────────────────────────────────────── */

/*
  One declaration and a navigation cross-fades instead of flashing white. A
  browser that has never heard of it ignores the block and behaves exactly as
  before, which is the only reason this is worth having on a site with no build
  step and no framework.
*/
@view-transition {
  navigation: auto;
}

/* ── off, when asked ──────────────────────────────────────────────────────── */

@media (prefers-reduced-motion: reduce) {
  html {
    scroll-behavior: auto;
  }

  .btn,
  .scroll-cue span {
    transition: none;
    animation: none;
  }

  /* the view transition is the one piece of motion the script cannot switch off,
     because the browser runs it; this is how it is switched off */
  ::view-transition-group(*),
  ::view-transition-old(*),
  ::view-transition-new(*) {
    animation: none !important;
  }
}

/* ─────────────────────────────────────────────────────────────────────────────
   THE SHARED HEAD BAND (owner, 2026-10-08)

   One page header for every landing page: the same height, the same three-line
   structure (kicker, title, lede) and the same width of words. All eight interior
   pages already use `.band--head`, whose `min-height` is the one height; what
   made two of them differ was their words. The padding under the words is now the
   same fixed amount on every page, and the words have the same measure, so a
   longer lede or the Contact page's address button does not grow the band.
   ───────────────────────────────────────────────────────────────────────────── */
.band--head {
  padding-bottom: 64px;
}

.band--head .band__inner {
  width: 100%;
  max-width: 62ch;
}

.band--head .lede {
  max-width: 54ch;
}

/* ── Clubs and Contact ─────────────────────────────────────────────────────── */
.card > h3:first-child {
  margin-top: 0;
}

/* an address is read, not shouted: normal case, and it may break on a phone */
.btn--mail {
  max-width: 100%;
  text-transform: none;
  letter-spacing: 0.02em;
  overflow-wrap: anywhere;
}

/* the box a reader most needs is first. It is the same solid card as its
   neighbours: a see-through one read as disabled. Only its tag is filled. */
.card--lead .card__tag {
  background: var(--ks-yellow);
  border-color: var(--ks-yellow);
  color: var(--ks-ink);
}

/* ── FAQ: questions start at the left edge, the arrow beside them ───────────── */
.qa {
  text-align: left;
}

/* ── Privacy: a list of headings at the top, and a column that stops growing ──
   Plain rows with a hairline, like the FAQ's questions: boxless text. */
.toc {
  max-width: 40em;
  margin: 0 auto clamp(30px, 5vh, 48px);
  padding: 14px 4px 6px;
  border-top: 1px solid rgb(255 255 255 / 0.18);
  border-bottom: 1px solid rgb(255 255 255 / 0.18);
  text-align: left;
}

.toc__title {
  font-family: 'Barlow Condensed', system-ui, sans-serif;
  font-weight: 700;
  letter-spacing: 0.12em;
  text-transform: uppercase;
  color: var(--ks-yellow);
}

.toc ul {
  margin: 10px 0 0;
  padding: 0;
  list-style: none;
  columns: 2 220px;
  column-gap: 28px;
}

.toc li {
  break-inside: avoid;
  padding: 0;
  border-bottom: 1px solid rgb(255 255 255 / 0.12);
}

.toc a {
  display: block;
  padding-block: 10px;
  color: var(--ks-paper);
}

.prose {
  max-width: 40em;
  margin-left: auto;
  margin-right: auto;
}

/* ── Dev log: a chip names the kind of line, big changes stand out ─────────── */
.log__date {
  font-size: 1.3rem;
}

.log .ticks li {
  font-size: 1rem;
  line-height: 1.5;
  color: var(--ks-sky);
}

.chip {
  display: inline-block;
  margin-right: 6px;
  padding: 0 7px;
  border: 1px solid currentColor;
  border-radius: var(--radius);
  font-family: 'Barlow Condensed', system-ui, sans-serif;
  font-size: 0.78rem;
  font-weight: 700;
  letter-spacing: 0.1em;
  line-height: 1.5;
  text-transform: uppercase;
  vertical-align: 1px;
}

.chip--added {
  color: #7fe0a8;
}

.chip--changed {
  color: var(--ks-yellow);
}

.chip--fixed {
  color: #ffa89a;
}

.log__big {
  padding: 8px 12px 8px 30px;
  border-left: 3px solid var(--ks-yellow);
  background: rgb(255 255 255 / 0.05);
  color: var(--ks-paper);
}

.log__big::before {
  left: 10px;
  top: 8px;
}

.log__big strong {
  color: var(--ks-paper);
  font-size: 1.1rem;
}

.month {
  margin-top: clamp(22px, 4vh, 34px);
  padding: 20px 22px 22px;
  border: 3px solid var(--ks-yellow);
  border-radius: var(--radius);
  background: var(--ks-navy-deep);
  text-align: left;
}

.month h2 {
  margin: 0;
  text-align: left;
  font-size: 1.5rem;
}

.month__list {
  margin: 12px 0 0;
  padding-left: 1.2em;
  color: var(--ks-paper);
}

.month__list li + li {
  margin-top: 6px;
}

.month__more {
  margin-top: 12px;
  color: var(--ks-sky);
  font-size: 0.93rem;
}

/*
  INLINE LINKS IN PROSE ARE EASY TO TAP (review round 2, site-04).

  A link inside a sentence is as tall as its line (17-19px). On a touch screen only,
  vertical padding on an inline box widens its hit area without moving a single line
  of text, because inline padding does not enter the line box. The look is unchanged.
*/
@media (pointer: coarse) {
  main p a:not([class]),
  main li a:not([class]),
  main dd a:not([class]),
  main summary a:not([class]),
  .prose a,
  .qa a:not(.btn),
  .slab .note a {
    padding-block: 14px;
  }
}

/* ─────────────────────────────────────────────────────────────────────────────
   THE 21 OCTOBER AUDIT
   ───────────────────────────────────────────────────────────────────────────── */

/* Home's four boxes on a phone: two by two, a short strip of picture with the name
   over it, and one sentence underneath. Stacked one to a row they made the section
   nearly two screens tall (the audit measured 1,878px at 390 wide). */
@media (max-width: 679px) {
  .grid--tiles {
    grid-template-columns: repeat(2, 1fr);
    gap: 12px;
  }

  .grid--tiles .card__art {
    aspect-ratio: auto;
    height: 96px;
  }

  .grid--tiles .card .card__name {
    left: 10px;
    right: 10px;
    bottom: 8px;
    font-size: 1.12rem;
  }

  .grid--tiles .card--art > p {
    padding: 0 12px;
    font-size: 0.95rem;
  }

  .grid--tiles .card--art > p:first-of-type {
    margin-top: 12px;
  }

  .grid--tiles .card--art > p:last-child {
    padding-bottom: 14px;
  }
}

/* A real capture of the game, framed like one of its boxes. The picture is the game's
   own replay screen, cropped and compressed, not drawn. */
.band__inner--shot {
  max-width: min(100%, 880px);
}

.shot {
  width: 100%;
  margin: 8px 0 4px;
  border: 3px solid var(--ks-yellow);
  background: var(--ks-navy-deep);
}

.shot img {
  display: block;
  width: 100%;
  height: auto;
}

.foot__crest {
  display: block;
  width: auto;
  height: 44px;
  margin: 0 auto 14px;
}

/* the dev log folds every month before the current one away */
.log__older {
  margin-top: clamp(22px, 4vh, 34px);
  border-top: 1px solid rgb(255 255 255 / 0.18);
  border-bottom: 1px solid rgb(255 255 255 / 0.18);
}

.log__older > summary {
  padding: 16px 4px;
  font-family: 'Barlow Condensed', system-ui, sans-serif;
  font-weight: 700;
  font-size: 1.16rem;
  letter-spacing: 0.02em;
  text-transform: uppercase;
  cursor: pointer;
}

.log__older > summary::marker {
  color: var(--ks-yellow);
}

/* THE PHONE MENU IS A SHEET (audit site.21). It used to drop a short list over the hero,
   which kept going, undimmed, right underneath; now it covers the page below the bar and
   keeps Play in thumb reach at the foot. Only when scripted: without script the list is
   simply open in the bar, as before. */
.topbar__sheetplay {
  display: none;
}

@media (max-width: 880px) {
  .js .nav:not([hidden]) {
    position: fixed;
    inset: var(--bar) 0 0 0;
    z-index: 1;
    width: auto;
    margin: 0;
    padding: 18px 16px 110px;
    overflow-y: auto;
    background: var(--ks-navy);
  }

  .js .nav:not([hidden]) .nav__list a {
    padding: 14px 8px 10px;
    font-size: 1.5rem;
  }

  /* the sheet ends in its own Play now, so the bar's Play sits out while it is open (visibility keeps the bar from jumping) */
  .menu-open .topbar__play {
    visibility: hidden;
  }

  .menu-open .topbar__sheetplay {
    display: block;
    position: fixed;
    left: 16px;
    right: 16px;
    bottom: max(16px, env(safe-area-inset-bottom));
    z-index: 2;
    text-align: center;
  }
}

/* ULTRAWIDE: the bar keeps to the same column as the words under it, so the logo, the
   menu and Play read as one group and not as three things 3,300px apart. */
@media (min-width: 2000px) {
  .topbar {
    padding-inline: max(14px, calc((100% - 1440px) / 2));
  }
}

@media (min-width: 2400px) and (max-width: 2799px) {
  html {
    font-size: 125%;
  }
}

@media (min-width: 2800px) {
  .topbar {
    padding-inline: max(14px, calc((100% - min(62vw, 2600px)) / 2));
  }
}
