/*
 * Playset — commercial landing page.
 *
 * Hand-written CSS on purpose. This page is not a tenant surface and not part
 * of the white-label product: it must not import the generated token layer,
 * because those tokens follow `tenants/.active` and would silently paint a
 * CUSTOMER's branding onto Pixeesoft's own sales page — with nothing in the
 * build failing. The one value shared with the product is the page ground of
 * the DARK theme, which is pinned to `theme.tokens.background` by
 * `packages/cli/src/__tests__/landing.test.mjs`; the rest is derived from the
 * artwork, for the reason given at the palette block below.
 *
 * No @theme / @custom-variant / @utility here: `scripts/lib/ui-guard.sh` fails
 * the build on any stylesheet outside packages/config that declares a private
 * token layer, and it is right to.
 */

/* ---------------------------------------------------------------- fonts -- */
/*
 * Plus Jakarta Sans (text) and Bricolage Grotesque (display), SIL Open Font
 * License. Both are VARIABLE faces shipped as one file each, with a weight
 * RANGE in the descriptor — which is the whole payload for every weight the
 * page sets. The first cut declared five static faces and shipped Google's
 * variable file five times: `inter-400`, `-600` and `-700` were byte-identical,
 * 48KB each, and two of them were preloaded. Weights still rendered correctly —
 * a variable face pinned by its descriptor does — so nothing looked wrong.
 *
 * Latin subset only: every glyph this page sets — accented French, guillemets,
 * em dash — falls inside the range below. The one exception is the ✓ that
 * `renderPricing` writes into the feature matrix (U+2713), which falls back to
 * the system UI font by design; a tick is a tick in any face, and carrying the
 * symbol subset for one character is not worth the request.
 */

@font-face {
  font-family: 'Plus Jakarta Sans';
  font-style: normal;
  font-weight: 200 800;
  font-display: swap;
  src: url(./fonts/plus-jakarta-sans-latin.cd8db90c.woff2) format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}

@font-face {
  font-family: 'Bricolage Grotesque';
  font-style: normal;
  font-weight: 600 800;
  font-stretch: 100%;
  font-display: swap;
  src: url(./fonts/bricolage-grotesque-latin.9fee080f.woff2) format('woff2');
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}

/* -------------------------------------------------------------- palette -- */

/*
 * Palette derived from the Playset Platform mark itself (tenants/playset/assets/
 * logo.png): four fanned cards — navy backs, gold linework, one blue card, one
 * red — inside a navy relationship ring.
 *
 * Deliberately NOT the app's `primary` violet. The product's UI token layer is
 * violet; the brand artwork contains no violet at all, and scripts/
 * make-tenant-logo.mjs records that violet was tried in the mark's halo and
 * rejected for exactly this reason. On a sales page the reader sees the mark
 * first, so the mark wins. Anything that must match the app's chrome belongs in
 * a screenshot, not in this stylesheet.
 *
 * These are the RAW colours, and they do not move between themes. What moves is
 * the semantic layer below, which maps them onto roles. Two raw values are used
 * directly and on purpose: `--ink` and `--gold` paint the gold surfaces — the
 * primary button, the founding slab, the skip link, the chosen audience pill —
 * which are identical in both themes, because a gold plate with navy on it
 * needs no light variant and reads as the brand either way.
 */
:root {
  /* the mark */
  --ink: #020817;
  --ink-deep: #060d1c;
  --slate: #0d1626;
  --navy-line: #1c2c44;
  --mist: #93a4bd;
  --paper: #f4f7fb;
  --gold: #f3c14a;
  --gold-lit: #ffd98a;
  --gold-mid: #c9931c;
  --gold-deep: #8b5e04;
  --steel: #5fa8d8;
  --steel-deep: #24699f;
  --ember: #d4604f;
  --ember-deep: #ab3a28;

  /* the light ground, one family with the navy rather than a neutral grey */
  --snow: #ffffff;
  --chalk: #f6f8fc;
  --chalk-deep: #eaeff7;
  --chalk-line: #dbe3ef;
  --chalk-ink: #0d1729;
  --chalk-mute: #55657e;

  --sans: 'Plus Jakarta Sans', ui-sans-serif, system-ui, -apple-system, 'Segoe UI', sans-serif;
  --display: 'Bricolage Grotesque', var(--sans);

  --radius: 0.5rem;
  --radius-lg: 0.75rem;

  --shell: 1120px;
  --gutter: clamp(1.25rem, 4vw, 2rem);
  --band-y: clamp(4rem, 8.5vw, 7rem);
}

/* ---------------------------------------------------------------- theme -- */
/*
 * Light and dark, in the three blocks the pattern needs and no fewer.
 *
 * `:root` carries the LIGHT set, because that is what a visitor with no stated
 * preference gets and most of the people this page is written for — a club
 * treasurer, a shop owner — have never changed that setting. The dark set is
 * then applied twice: once for a system preference that no explicit choice has
 * overridden, and once for the explicit choice itself, so the nav's switch wins
 * in BOTH directions. A single `@media` block cannot do that: a reader on a
 * dark OS who asks for light has to be able to get it.
 *
 * The two dark blocks are duplicated verbatim, which is a real hazard — a token
 * added to one and not the other produces a page that is correct until someone
 * changes their OS setting. `landing.test.mjs` parses all three blocks and
 * fails when the light set and either dark set stop naming exactly the same
 * tokens. `light-dark()` would remove the duplication outright, but a browser
 * that does not know the function drops every declaration using it, and the
 * failure mode there is an unstyled page rather than a stale colour.
 *
 * `color-scheme` is part of the swap, not decoration: it is what makes the
 * scrollbars, the `<details>` markers and the focus rings the browser draws
 * itself agree with the page.
 */

:root {
  color-scheme: light;

  --bg: var(--chalk);
  --bg-deep: var(--chalk-deep);
  --surface: var(--snow);
  --card: var(--snow);
  --card-hover: var(--chalk-deep);
  --panel: rgba(255, 255, 255, 0.82);
  --panel-shadow: 0 18px 44px rgba(13, 23, 41, 0.08);
  --line: var(--chalk-line);
  --text: var(--chalk-ink);
  --muted: var(--chalk-mute);
  --link: var(--steel-deep);
  --link-soft: rgba(36, 105, 159, 0.4);

  --accent-ink: var(--gold-deep);
  --accent-line: var(--gold-mid);
  --accent-ring: var(--gold-deep);

  --alert: var(--ember-deep);
  --alert-line: rgba(171, 58, 40, 0.45);
  --alert-wash: rgba(171, 58, 40, 0.05);

  --chip: rgba(13, 23, 41, 0.055);
  --track: rgba(13, 23, 41, 0.1);
  --hatch: rgba(13, 23, 41, 0.05);
  --halo-steel: rgba(95, 168, 216, 0.22);
  --halo-gold: rgba(243, 193, 74, 0.26);

  --btn-shadow: 0 1px 2px rgba(13, 23, 41, 0.16);
  --btn-shadow-lit: 0 8px 20px rgba(201, 147, 28, 0.32);
  --feature-ring: rgba(201, 147, 28, 0.45);
  --feature-glow: 0 0 0 1px rgba(201, 147, 28, 0.16), 0 14px 34px rgba(13, 23, 41, 0.07);

  /* the messaging app in the hero panel — see the `.wa` block */
  --wa-bar: #f0f2f5;
  --wa-thread: #ece5dd;
  --wa-in: #ffffff;
  --wa-out: #d9fdd3;
  --wa-ink: #111b21;
  --wa-sub: rgba(17, 27, 33, 0.45);
  --wa-tick: #34a3d8;
  --wa-name: #1f7a8c;
  --wa-name-alt: #a8437b;

  /* which half of the theme switch is showing — the icon of the theme you get */
  --icon-sun: none;
  --icon-moon: block;

  /*
   * Which cut of the nav mark is showing. The mark is one artwork in two
   * colourways — gold for a dark ground, navy for a light one — rather than one
   * file with a glow behind it to survive both. Same mechanism as the switch
   * icons above: both images ship, and the theme decides which one displays.
   */
  --mark-gold: none;
  --mark-navy: block;
}

@media (prefers-color-scheme: dark) {
  :root:not([data-theme='light']) {
    color-scheme: dark;

    --bg: var(--ink);
    --bg-deep: var(--ink-deep);
    --surface: var(--slate);
    --card: var(--ink);
    --card-hover: var(--slate);
    --panel: rgba(14, 19, 27, 0.72);
    --panel-shadow: none;
    --line: var(--navy-line);
    --text: var(--paper);
    --muted: var(--mist);
    --link: var(--steel);
    --link-soft: rgba(95, 168, 216, 0.45);

    --accent-ink: var(--gold);
    --accent-line: var(--gold);
    --accent-ring: var(--gold);

    --alert: var(--ember);
    --alert-line: rgba(212, 96, 79, 0.55);
    --alert-wash: rgba(212, 96, 79, 0.06);

    --chip: rgba(148, 163, 184, 0.11);
    --track: rgba(148, 163, 184, 0.18);
    --hatch: rgba(148, 163, 184, 0.07);
    --halo-steel: rgba(95, 168, 216, 0.2);
    --halo-gold: rgba(243, 193, 74, 0.16);

    --btn-shadow: 0 0 22px rgba(243, 193, 74, 0.24);
    --btn-shadow-lit: 0 0 34px rgba(243, 193, 74, 0.42);
    --feature-ring: rgba(243, 193, 74, 0.5);
    --feature-glow: 0 0 0 1px rgba(243, 193, 74, 0.16), 0 0 44px rgba(243, 193, 74, 0.08);

    --wa-bar: #202c33;
    --wa-thread: #0b141a;
    --wa-in: #202c33;
    --wa-out: #005c4b;
    --wa-ink: #e9edef;
    --wa-sub: rgba(233, 237, 239, 0.5);
    --wa-tick: #53bdeb;
    --wa-name: #7fd8c6;
    --wa-name-alt: #f0a6c8;

    --icon-sun: block;
    --icon-moon: none;

    --mark-gold: block;
    --mark-navy: none;
  }
}

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

  --bg: var(--ink);
  --bg-deep: var(--ink-deep);
  --surface: var(--slate);
  --card: var(--ink);
  --card-hover: var(--slate);
  --panel: rgba(14, 19, 27, 0.72);
  --panel-shadow: none;
  --line: var(--navy-line);
  --text: var(--paper);
  --muted: var(--mist);
  --link: var(--steel);
  --link-soft: rgba(95, 168, 216, 0.45);

  --accent-ink: var(--gold);
  --accent-line: var(--gold);
  --accent-ring: var(--gold);

  --alert: var(--ember);
  --alert-line: rgba(212, 96, 79, 0.55);
  --alert-wash: rgba(212, 96, 79, 0.06);

  --chip: rgba(148, 163, 184, 0.11);
  --track: rgba(148, 163, 184, 0.18);
  --hatch: rgba(148, 163, 184, 0.07);
  --halo-steel: rgba(95, 168, 216, 0.2);
  --halo-gold: rgba(243, 193, 74, 0.16);

  --btn-shadow: 0 0 22px rgba(243, 193, 74, 0.24);
  --btn-shadow-lit: 0 0 34px rgba(243, 193, 74, 0.42);
  --feature-ring: rgba(243, 193, 74, 0.5);
  --feature-glow: 0 0 0 1px rgba(243, 193, 74, 0.16), 0 0 44px rgba(243, 193, 74, 0.08);

  --wa-bar: #202c33;
  --wa-thread: #0b141a;
  --wa-in: #202c33;
  --wa-out: #005c4b;
  --wa-ink: #e9edef;
  --wa-sub: rgba(233, 237, 239, 0.5);
  --wa-tick: #53bdeb;
  --wa-name: #7fd8c6;
  --wa-name-alt: #f0a6c8;

  --icon-sun: block;
  --icon-moon: none;

  --mark-gold: block;
  --mark-navy: none;
}

/* ---------------------------------------------------------------- reset -- */

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

html {
  -webkit-text-size-adjust: 100%;
  scroll-behavior: smooth;
}

body {
  margin: 0;
  background-color: var(--bg);
  background-image: linear-gradient(180deg, var(--bg) 0%, var(--bg-deep) 100%);
  background-attachment: fixed;
  color: var(--text);
  font-family: var(--sans);
  font-size: 1rem;
  font-weight: 400;
  line-height: 1.65;
  -webkit-font-smoothing: antialiased;
  text-rendering: optimizeLegibility;
}

img,
svg {
  display: block;
  max-width: 100%;
  height: auto;
}

a {
  color: var(--link);
  text-decoration-color: var(--link-soft);
  text-underline-offset: 0.2em;
}

a:hover {
  text-decoration-color: var(--link);
}

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

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

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

/* ----------------------------------------------------------- typography -- */
/*
 * Two families, one job each. Bricolage Grotesque sets the headlines, the big
 * numbers and the pull quote — the places a reader looks at rather than reads —
 * and Plus Jakarta Sans sets everything else.
 *
 * There is no monospace on this page any more, and its absence is the point. A
 * mono face was carrying every eyebrow, price, statistic and table header, which
 * gave a page sold to club committees and game shops the texture of a terminal.
 * Those labels are the same information in the text face, tracked out and
 * uppercased — 0.14em at 600, wherever one appears.
 *
 * What the mono was silently also doing is figure alignment, so every place
 * that lost it and sets a number in a column — the panel rows, the price, the
 * statistics, the matrix — asks for `tabular-nums` explicitly instead.
 */

/* ------------------------------------------------------------ structure -- */

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

.band {
  padding-block: var(--band-y);
  border-top: 1px solid var(--line);
}

.band--plain {
  border-top: 0;
  /* Attached to the block above it: two full band paddings back to back read as
     a dropped section rather than a consequence of the one before. */
  padding-top: 0;
}

.band--slim {
  padding-block: clamp(1.5rem, 3.5vw, 2.5rem);
}

.skip {
  position: absolute;
  left: -9999px;
  top: 0;
  z-index: 100;
  padding: 0.75rem 1.25rem;
  background: var(--gold);
  color: var(--ink);
  font-weight: 600;
  border-radius: 0 0 var(--radius) 0;
}

.skip:focus {
  left: 0;
}

/*
 * The one recurring structural device: a short gold rule, then a tracked label.
 * It marks each part of the argument the way a committee paper marks its
 * sections — the label is information, not decoration.
 */
.eyebrow {
  display: flex;
  align-items: center;
  gap: 0.75rem;
  margin: 0 0 1.5rem;
  font-family: var(--sans);
  font-size: 0.72rem;
  font-weight: 600;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--muted);
}

.eyebrow::before {
  content: '';
  flex: 0 0 1.75rem;
  height: 2px;
  background: var(--accent-line);
}

.h2 {
  font-family: var(--display);
  font-size: clamp(1.85rem, 3.5vw, 2.7rem);
  font-weight: 700;
  letter-spacing: -0.025em;
  line-height: 1.08;
  max-width: 22ch;
}

.h2--wide {
  max-width: 30ch;
}

.lede {
  margin-top: 1.25rem;
  max-width: 62ch;
  font-size: clamp(1.02rem, 1.4vw, 1.18rem);
  color: var(--muted);
}

.hl {
  color: var(--accent-ink);
  font-style: normal;
}

/* ----------------------------------------------------------------- nav --- */

.nav {
  position: relative;
  z-index: 10;
  display: flex;
  align-items: center;
  gap: 0.6rem;
  padding-block: 1.25rem;
}

.nav > * {
  flex-shrink: 0;
}

.nav__brand {
  display: flex;
  align-items: center;
  gap: 0.6rem;
  margin-right: auto;
  color: var(--text);
  text-decoration: none;
  font-family: var(--display);
  font-weight: 700;
  font-size: 1.1rem;
  letter-spacing: -0.015em;
}

.nav__mark {
  width: 28px;
  height: 28px;
  border-radius: 6px;
}

/*
 * Both cuts of the mark ship and the theme picks one, the same way the switch
 * icons work. It is two files rather than one because the mark is flat and
 * two-colour: gold on ink, navy on paper, no glow. The previous single file
 * needed an outer glow precisely so that one artwork could sit on either
 * ground, and the glow is what this replaces.
 */
.nav__mark--gold {
  display: var(--mark-gold);
}

.nav__mark--navy {
  display: var(--mark-navy);
}

/*
 * The language menu.
 *
 * A `<details>`, so it opens, closes, takes focus and announces itself with the
 * page's JavaScript blocked — the standard everything interactive here is held
 * to. Two languages were a link that could BE the other page; three are a
 * choice, and a choice in a nav is a menu.
 *
 * The summary is styled to match `.nav__theme` beside it: same height, same
 * border, same muted-until-hover ink, so the two read as one pair of controls
 * rather than a button next to a badge.
 */

.locales {
  position: relative;
}

.locales__button {
  display: inline-flex;
  align-items: center;
  gap: 0.3rem;
  height: 2.25rem;
  padding-inline: 0.8rem;
  font-family: var(--sans);
  font-size: 0.72rem;
  font-weight: 600;
  letter-spacing: 0.1em;
  color: var(--muted);
  border: 1px solid var(--line);
  border-radius: 999px;
  background: var(--chip);
  cursor: pointer;
  /* Both halves of removing the disclosure triangle: the standard property and
     the WebKit pseudo-element that ignores it. */
  list-style: none;
  transition: color 0.18s ease, border-color 0.18s ease;
}

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

.locales__button:hover,
.locales[open] .locales__button {
  color: var(--text);
  border-color: var(--muted);
}

.locales__chevron {
  width: 0.85rem;
  height: 0.85rem;
  stroke: currentColor;
  fill: none;
  stroke-width: 2;
  stroke-linecap: round;
  stroke-linejoin: round;
  transition: transform 0.18s ease;
}

.locales[open] .locales__chevron {
  transform: rotate(180deg);
}

.locales__menu {
  position: absolute;
  right: 0;
  z-index: 30;
  min-width: 11rem;
  padding: 0.3rem;
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  background: var(--surface);
  box-shadow: var(--panel-shadow);
}

/* Which way it opens is the only difference between the two copies of this
   control — a menu at the foot of the page that opens downwards opens off the
   end of it. */
.locales--nav .locales__menu {
  top: calc(100% + 0.4rem);
}

.locales--foot .locales__menu {
  bottom: calc(100% + 0.4rem);
}

.locales__item {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 1rem;
  padding: 0.5rem 0.6rem;
  border-radius: var(--radius);
  color: var(--text);
  font-size: 0.9rem;
  text-decoration: none;
}

.locales__item:hover {
  background: var(--card-hover);
}

.locales__code {
  font-size: 0.68rem;
  font-weight: 600;
  letter-spacing: 0.1em;
  color: var(--muted);
}

/*
 * The page you are already on, marked rather than removed. A menu that lists
 * only the other languages is a menu whose contents move every time you use it.
 */
.locales__item[aria-current] {
  color: var(--accent-ink);
  font-weight: 600;
}

.locales__item[aria-current] .locales__code {
  color: var(--accent-ink);
}

/*
 * The theme switch.
 *
 * Ships with `hidden` on it and is revealed by the same inline script that
 * applies a stored choice — so a reader with no JavaScript is never shown a
 * control that cannot do anything, and simply gets the theme their system asked
 * for. The icon shown is the theme the button will GIVE you, not the one you
 * are in, which is the reading almost everyone applies to a half-moon in a nav.
 */
.nav__theme {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 2.25rem;
  height: 2.25rem;
  padding: 0;
  font-family: var(--sans);
  color: var(--muted);
  border: 1px solid var(--line);
  border-radius: 999px;
  background: var(--chip);
  cursor: pointer;
  transition: color 0.18s ease, border-color 0.18s ease;
}

.nav__theme:hover {
  color: var(--text);
  border-color: var(--muted);
}

.nav__theme[hidden] {
  display: none;
}

.nav__theme svg {
  width: 1rem;
  height: 1rem;
  stroke: currentColor;
  fill: none;
  stroke-width: 1.7;
  stroke-linecap: round;
  stroke-linejoin: round;
}

.nav__theme .icon-sun {
  display: var(--icon-sun);
}

.nav__theme .icon-moon {
  display: var(--icon-moon);
}

/* --------------------------------------------------------------- button -- */

.btn {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 0.5rem;
  padding: 0.8rem 1.4rem;
  border-radius: var(--radius);
  border: 1px solid transparent;
  font-family: var(--sans);
  font-size: 0.95rem;
  font-weight: 600;
  line-height: 1.2;
  text-decoration: none;
  cursor: pointer;
  transition: transform 0.18s ease, box-shadow 0.18s ease, background-color 0.18s ease, border-color 0.18s ease;
}

.btn--primary {
  background-image: linear-gradient(135deg, var(--gold), var(--gold-lit));
  color: var(--ink);
  box-shadow: var(--btn-shadow);
}

.btn--primary:hover {
  box-shadow: var(--btn-shadow-lit);
  transform: translateY(-1px);
}

.btn--ghost {
  border-color: var(--line);
  background: transparent;
  color: var(--text);
}

.btn--ghost:hover {
  border-color: var(--muted);
  transform: translateY(-1px);
}

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

.btn--ink:hover {
  transform: translateY(-1px);
  box-shadow: 0 8px 24px rgba(2, 8, 23, 0.35);
}

.btn--sm {
  padding: 0.55rem 1rem;
  font-size: 0.85rem;
}

.btn-row {
  display: flex;
  flex-wrap: wrap;
  gap: 0.75rem;
  margin-top: 2rem;
}

/*
 * The header's two shapes, and the ONE width where they trade places (owner
 * ruling, 2026-08-30, after the vaultaire.app header).
 *
 * Every destination is rendered twice — a row of text links for a wide screen
 * and, behind a hamburger, a panel of glyph + title + blurb rows for a narrow
 * one — because a `<details>` cannot be opened from CSS, so no one markup can
 * be both. The base rules are the PHONE's: the row, the inline demo button and
 * the theme switch's word are hidden here and restored by the single
 * `min-width` query at the end of this block, which is also where the
 * hamburger goes. `landing.test.mjs` reads that query back and refuses a
 * stylesheet whose two shapes do not meet at exactly one number, so no width
 * is ever left with neither — the failure the previous header had at 720px.
 *
 * The demo button has two homes rather than one: inline from the breakpoint
 * up, and the full-width foot of the panel below it.
 */
.nav__links {
  display: none;
}

.nav__links ul {
  display: flex;
  align-items: center;
  gap: clamp(0.8rem, 1.4vw, 1.4rem);
  margin: 0;
  padding: 0;
  list-style: none;
}

.nav__link {
  display: inline-block;
  padding-block: 0.3rem;
  font-family: var(--sans);
  font-size: 0.72rem;
  font-weight: 600;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  white-space: nowrap;
  color: var(--muted);
  text-decoration: none;
  transition: color 0.18s ease;
}

.nav__link:hover,
.nav__link:focus-visible,
.nav__link[aria-current] {
  color: var(--text);
}

.nav__cta {
  display: none;
  white-space: nowrap;
}

.nav__theme-label {
  display: none;
  font-size: 0.78rem;
  font-weight: 600;
  line-height: 1;
}

/*
 * The hamburger and its panel. The `<details>` is `static` so the panel is
 * positioned by the HEADER (`.nav` is `relative`), edge to edge beneath it,
 * rather than by a button in the top-right corner.
 */
.navmenu {
  position: static;
}

.navmenu__button {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 2.25rem;
  height: 2.25rem;
  color: var(--muted);
  border: 1px solid var(--line);
  border-radius: 999px;
  background: var(--chip);
  cursor: pointer;
  /* Both halves of removing the disclosure triangle, as `.locales__button`. */
  list-style: none;
  transition: color 0.18s ease, border-color 0.18s ease, box-shadow 0.18s ease;
}

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

.navmenu__button:hover {
  color: var(--text);
  border-color: var(--muted);
}

/* Open, the control is the one thing on the header that is lit — a ring in
   the accent, and a cross where the bars were. */
.navmenu[open] .navmenu__button {
  color: var(--text);
  border-color: var(--accent-ring);
  box-shadow: 0 0 0 3px var(--halo-gold);
}

.navmenu__icon {
  width: 1.1rem;
  height: 1.1rem;
  stroke: currentColor;
  fill: none;
  stroke-width: 2;
  stroke-linecap: round;
}

.navmenu__icon--close,
.navmenu[open] .navmenu__icon--bars {
  display: none;
}

.navmenu[open] .navmenu__icon--close {
  display: block;
}

/*
 * The scrim: the page behind the open panel, dimmed and blurred. A
 * pseudo-element of the `<details>` itself, which hit-tests as the element —
 * what lets `DISCLOSURE_MENU_SCRIPT` treat a tap on it as "outside". It sits
 * at z -1 INSIDE the header's stacking context (`.nav` is `relative` with a
 * z-index), so it paints over every section of the page and under every
 * control of the header: the brand and the pills stay crisp above it.
 */
.navmenu[open]::before {
  content: '';
  position: fixed;
  inset: 0;
  z-index: -1;
  background: color-mix(in srgb, var(--bg) 55%, transparent);
  -webkit-backdrop-filter: blur(10px);
  backdrop-filter: blur(10px);
}

.navmenu__panel {
  position: absolute;
  top: 100%;
  right: 0;
  left: 0;
  z-index: 30;
  padding: 0.5rem var(--gutter) 1.25rem;
  background: var(--panel);
  -webkit-backdrop-filter: blur(18px);
  backdrop-filter: blur(18px);
  border-bottom: 1px solid var(--line);
  box-shadow: var(--panel-shadow);
}

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

/* A row: the glyph spans both lines of text. */
.navmenu__item {
  display: grid;
  grid-template-columns: 2.5rem 1fr;
  grid-template-rows: auto auto;
  column-gap: 0.9rem;
  align-items: center;
  padding: 0.6rem 0;
  color: var(--text);
  text-decoration: none;
}

.navmenu__glyph {
  grid-row: 1 / span 2;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 2.5rem;
  height: 2.5rem;
  border: 1px solid var(--line);
  border-radius: 0.7rem;
  background: var(--chip);
  color: var(--accent-ink);
  transition: border-color 0.18s ease;
}

.navmenu__glyph svg {
  width: 1.15rem;
  height: 1.15rem;
  stroke: currentColor;
  fill: none;
  stroke-width: 1.7;
  stroke-linecap: round;
  stroke-linejoin: round;
}

.navmenu__title {
  align-self: end;
  font-family: var(--sans);
  font-size: 0.8rem;
  font-weight: 700;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  line-height: 1.3;
}

.navmenu__blurb {
  align-self: start;
  font-size: 0.85rem;
  line-height: 1.35;
  color: var(--muted);
}

.navmenu__item:hover .navmenu__glyph,
.navmenu__item:focus-visible .navmenu__glyph,
.navmenu__item[aria-current] .navmenu__glyph {
  border-color: var(--accent-line);
}

.navmenu__item[aria-current] .navmenu__title {
  color: var(--accent-ink);
}

.navmenu__cta {
  display: flex;
  width: 100%;
  margin-top: 0.75rem;
}

/*
 * The wide screen. This is the ONLY query that touches the header's members,
 * and everything it does is symmetric: what the base rules hid, it shows, and
 * the one thing it hides is the hamburger whose contents it has just laid out
 * inline. 1140 rather than a tablet-ish 960 because French is the yardstick:
 * "Fonctionnalités … À vos couleurs" beside "Demander une démo" is a 1050px
 * row, and at 1100 it "fit" only by letting the flex algorithm crush the
 * pills' icons to nothing, at 1120 by leaking into the gutter. Measured, not
 * chosen: the number is the first one at which the French row sits inside
 * the shell with its icons intact.
 */
@media (min-width: 1140px) {
  .nav__links {
    display: block;
    margin-right: auto;
    margin-left: clamp(0.75rem, 1.5vw, 1.5rem);
  }

  .nav__cta {
    display: inline-flex;
  }

  .nav__theme {
    width: auto;
    padding-inline: 0.8rem;
    gap: 0.45rem;
  }

  .nav__theme-label--dark {
    display: var(--icon-moon);
  }

  .nav__theme-label--light {
    display: var(--icon-sun);
  }

  .navmenu {
    display: none;
  }
}

/* ---------------------------------------------------------------- hero --- */

.hero {
  position: relative;
  padding-block: clamp(2.5rem, 6vw, 4.5rem) clamp(3.5rem, 8vw, 6rem);
  overflow: hidden;
}

/*
 * Both halos fall to nothing BEFORE the edges of the box that clips them.
 *
 * They used to be centred above the hero's top edge and bled past it on both
 * sides, so `overflow: hidden` cut them mid-strength and drew a pale rectangle
 * the width of the shell. Invisible at the dark theme's alphas, obvious the
 * moment the same gradients were laid on a light ground — which is how it was
 * found. Every radius here is chosen so that `transparent 70%` lands inside the
 * box: move a centre and check the corners.
 */
.hero::before {
  content: '';
  position: absolute;
  inset: 0 0 auto 0;
  height: 80%;
  background: radial-gradient(42% 46% at 26% 34%, var(--halo-steel), transparent 70%),
    radial-gradient(38% 42% at 74% 28%, var(--halo-gold), transparent 70%);
  pointer-events: none;
}

.hero__inner {
  position: relative;
  display: grid;
  gap: clamp(2.5rem, 5vw, 4rem);
}

.hero__title {
  font-family: var(--display);
  font-size: clamp(2.5rem, 6.4vw, 4.2rem);
  font-weight: 700;
  letter-spacing: -0.03em;
  line-height: 1.0;
  max-width: 15ch;
  text-wrap: balance;
}

.hero__lede {
  margin-top: 1.5rem;
  max-width: 52ch;
  font-size: clamp(1.05rem, 1.6vw, 1.25rem);
  color: var(--muted);
}

.hero__sub {
  margin-top: 1rem;
  max-width: 52ch;
  font-size: 0.95rem;
  color: var(--muted);
  opacity: 0.85;
}

.hero__promise {
  margin-top: 1.1rem;
  max-width: 46ch;
  font-size: 0.84rem;
  line-height: 1.7;
  color: var(--muted);
}

/* ------------------------------------------------------ signature panel -- */
/*
 * The page's one signature: the same Wednesday evening, twice — once in the
 * group chat it is organised in today, once on the club's own site.
 *
 * Both halves are DRAWN, and both are drawn as the thing they depict rather
 * than as a diagram of it. The argument the page makes starts before the
 * headline is read: a reader has to recognise their own Tuesday night in the
 * top half and want the bottom one. Grey bubbles and a list of counters — what
 * this was — are a chat and a product in the abstract, and nobody recognises
 * either. Used here and nowhere else; everything below this is disciplined.
 */

.panel {
  padding: clamp(0.85rem, 2vw, 1.15rem);
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  background: var(--panel);
  box-shadow: var(--panel-shadow);
  backdrop-filter: blur(12px);
}

/*
 * One beat: a label, a device, a line of commentary. Both halves get the same
 * three, in the same order, and that repetition is the whole of the structure —
 * the first cut ran the chat flush to the panel's edges with a caption loose
 * underneath and a hairline captioned "with Playset" between the halves, which
 * left the reader to work out where one exhibit stopped and the next began.
 *
 * The label and the note are the PAGE's voice; everything between them is a
 * screen. So they sit on the panel's own ground, outside the device's frame, at
 * the panel's text size — never inside the mock, where they would read as one
 * more piece of somebody's UI.
 */
.beat {
  margin: 0;
}

.beat--after {
  margin-top: 1.15rem;
  padding-top: 1.15rem;
  border-top: 1px solid var(--line);
}

.beat__label {
  display: flex;
  align-items: center;
  gap: 0.4rem;
  margin: 0 0 0.55rem;
  font-size: 0.7rem;
  font-weight: 600;
  letter-spacing: 0.12em;
  text-transform: uppercase;
  color: var(--muted);
}

/* The turn, marked where the turn happens: gold, and an arrow pointing into
   the half that answers the one above. */
.beat__label--lit {
  color: var(--accent-ink);
}

.beat__label svg {
  width: 0.9rem;
  height: 0.9rem;
  fill: none;
  stroke: currentColor;
  stroke-width: 2;
  stroke-linecap: round;
  stroke-linejoin: round;
}

.beat__note {
  margin: 0.6rem 0 0;
  font-size: 0.78rem;
  line-height: 1.55;
  color: var(--muted);
}

/* ---------------------------------------------------------- the group -- */
/*
 * A messaging app, in its own vernacular and none of its artwork: no doodle
 * wallpaper, no logo, no screenshot. What is here is what a group thread has
 * and what a column of grey pills did not — a header carrying the group's name
 * and member count, a date pill, the sender's name over every incoming message,
 * a clock on each bubble and delivery ticks on the reader's own.
 *
 * Its palette is a token set of its own (`--wa-*`, in all three theme blocks)
 * because it is somebody else's surface: it follows the page from light to dark
 * so the panel does not glow in a light reader's face, but its greens and its
 * greys are not the page's and must not drift into being.
 */

.wa {
  overflow: hidden;
  border-radius: 0.6rem;
  background: var(--wa-thread);
  box-shadow: 0 1px 2px rgba(11, 20, 26, 0.18);
  color: var(--wa-ink);
  font-family: var(--sans);
}

.wa__bar {
  display: flex;
  gap: 0.6rem;
  align-items: center;
  padding: 0.5rem 0.7rem;
  background: var(--wa-bar);
}

.wa__avatar {
  display: grid;
  flex: none;
  place-items: center;
  width: 2rem;
  height: 2rem;
  border-radius: 999px;
  background: linear-gradient(160deg, #8696a0, #667781);
  color: #fff;
}

.wa__avatar svg {
  width: 1.1rem;
  height: 1.1rem;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.8;
  stroke-linecap: round;
}

.wa__who {
  overflow: hidden;
  min-width: 0;
}

.wa__who b {
  display: block;
  overflow: hidden;
  font-size: 0.82rem;
  font-weight: 600;
  white-space: nowrap;
  text-overflow: ellipsis;
}

.wa__who i {
  display: block;
  overflow: hidden;
  font-size: 0.68rem;
  font-style: normal;
  color: var(--wa-sub);
  white-space: nowrap;
  text-overflow: ellipsis;
}

.wa__tools {
  display: flex;
  flex: none;
  gap: 0.85rem;
  margin-left: auto;
  color: var(--wa-sub);
}

.wa__tools svg {
  width: 1.05rem;
  height: 1.05rem;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.7;
  stroke-linejoin: round;
}

/*
 * The faint grain is a texture, not a copy of anybody's wallpaper: two dot
 * grids at 3% of the thread's own ink, which is what stops a flat beige (or a
 * flat near-black) reading as a placeholder rectangle.
 */
.wa__thread {
  display: grid;
  gap: 0.4rem;
  justify-items: start;
  padding: 0.75rem 0.7rem;
  background-image: radial-gradient(color-mix(in srgb, var(--wa-ink) 6%, transparent) 1px, transparent 1px),
    radial-gradient(color-mix(in srgb, var(--wa-ink) 4%, transparent) 1px, transparent 1px);
  background-position: 0 0, 11px 11px;
  background-size: 22px 22px;
}

.wa__day {
  justify-self: center;
  padding: 0.15rem 0.65rem;
  border-radius: 999px;
  background: var(--wa-in);
  box-shadow: 0 1px 1px rgba(11, 20, 26, 0.13);
  font-size: 0.66rem;
  font-weight: 500;
  color: var(--wa-sub);
  text-transform: uppercase;
  letter-spacing: 0.04em;
}

.wa__msg {
  position: relative;
  max-width: 84%;
  /*
   * The stamp is absolutely placed, so the last line has to be told to end
   * before it — the alternative is a time sitting on top of a word, which is
   * exactly what the French page did: `20 h 03` is half again as wide as
   * `20:03`, and the reserve has to clear the widest clock any locale writes,
   * plus the ticks on the reader's own messages.
   */
  padding: 0.35rem 3.6rem 0.32rem 0.55rem;
  border-radius: 0.45rem;
  background: var(--wa-in);
  box-shadow: 0 1px 1px rgba(11, 20, 26, 0.13);
  font-size: 0.84rem;
  line-height: 1.35;
}

.wa__msg--me {
  justify-self: end;
  padding-right: 4.7rem;
  background: var(--wa-out);
}

/*
 * The tail: a 0×0 box whose top border is the only coloured one, so the
 * trapezoid degenerates to a triangle with a flat top and a vertical edge
 * against the bubble. Squared corner on that side, round everywhere else — the
 * shape every messaging app draws and the one this read as missing.
 */
.wa__msg--in {
  border-top-left-radius: 0;
}

.wa__msg--in::before {
  content: '';
  position: absolute;
  top: 0;
  left: -8px;
  width: 0;
  height: 0;
  border-top: 8px solid var(--wa-in);
  border-left: 8px solid transparent;
}

.wa__msg--me {
  border-top-right-radius: 0;
}

.wa__msg--me::before {
  content: '';
  position: absolute;
  top: 0;
  right: -8px;
  width: 0;
  height: 0;
  border-top: 8px solid var(--wa-out);
  border-right: 8px solid transparent;
}

/* Two colours alternating, because one colour for every sender is the detail
   that says "mock" — a real group gives each person their own. */
.wa__from {
  display: block;
  font-size: 0.72rem;
  font-weight: 700;
  color: var(--wa-name);
}

.wa__msg:nth-of-type(even) .wa__from {
  color: var(--wa-name-alt);
}

.wa__text {
  display: block;
}

.wa__stamp {
  position: absolute;
  right: 0.5rem;
  bottom: 0.28rem;
  display: flex;
  gap: 0.18rem;
  align-items: center;
  font-size: 0.62rem;
  font-variant-numeric: tabular-nums;
  color: var(--wa-sub);
}

.wa__stamp svg {
  width: 0.95rem;
  height: 0.6rem;
  fill: none;
  stroke: var(--wa-tick);
  stroke-width: 2;
  stroke-linecap: round;
  stroke-linejoin: round;
}

/*
 * The reaction pill, hanging off the bottom edge of the bubble it belongs to.
 *
 * Nine thumbs on one message is how a group answers "who's coming", and it is
 * the page's own argument in one object: a count nobody can act on. It overlaps
 * the bubble the way the app draws it, so `--reacted` pays for the overlap with
 * bottom margin — otherwise the pill lands on the next message.
 */
.wa__react {
  position: absolute;
  left: 0.45rem;
  bottom: -0.62rem;
  display: flex;
  gap: 0.2rem;
  align-items: center;
  padding: 0.08rem 0.4rem;
  border: 1px solid color-mix(in srgb, var(--wa-thread) 55%, transparent);
  border-radius: 999px;
  background: var(--wa-in);
  box-shadow: 0 1px 2px rgba(11, 20, 26, 0.2);
  font-size: 0.68rem;
  line-height: 1.3;
}

.wa__react b {
  font-size: 0.66rem;
  font-weight: 600;
  font-variant-numeric: tabular-nums;
  color: var(--wa-sub);
}

.wa__msg--reacted {
  margin-bottom: 0.5rem;
}

.wa__composer {
  display: flex;
  gap: 0.5rem;
  align-items: center;
  padding: 0.45rem 0.6rem;
  background: var(--wa-bar);
}

.wa__composer > svg {
  flex: none;
  width: 1.1rem;
  height: 1.1rem;
  fill: none;
  stroke: var(--wa-sub);
  stroke-width: 2;
  stroke-linecap: round;
}

.wa__field {
  flex: 1;
  min-width: 0;
  padding: 0.35rem 0.7rem;
  border-radius: 999px;
  background: var(--wa-in);
  font-size: 0.78rem;
  color: var(--wa-sub);
}

.wa__send {
  display: grid;
  flex: none;
  place-items: center;
  width: 1.85rem;
  height: 1.85rem;
  border-radius: 999px;
  background: #00a884;
  color: #fff;
}

.wa__send svg {
  width: 0.95rem;
  height: 0.95rem;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.8;
  stroke-linecap: round;
}

/* ------------------------------------------------------ the same evening -- */
/*
 * The club's own site, traced from `apps/web` the way the preview mock's
 * `site` view is: `Header` — wordmark, nav with the active link underlined, a
 * sign-up button — over one `PlayDayCard`, with its tinted date strip and
 * calendar tile, a `FormatBadge`, the clock/venue/capacity meta row, the member
 * price and the card's own "all events" link.
 *
 * It takes the page's OWN tokens, unlike the chat above it: this half is the
 * product, and the product on this page is ours. The one colour it uses as an
 * accent is `--link` — steel, not gold — because gold is the sales page's
 * chrome and a mock painted in it stops reading as somebody else's site.
 */

/*
 * The browser around it — the same device the preview page's three views sit
 * in, and here it does a second job: the half above this one is a phone
 * conversation, this one is a website, and two different frames say that
 * without a word of copy. It is deliberately neutral, as it is there: a browser
 * belongs to nobody's brand.
 */
.browser {
  overflow: hidden;
  border: 1px solid var(--line);
  border-radius: 0.6rem;
  background: var(--surface);
  box-shadow: 0 1px 2px rgba(13, 23, 41, 0.06);
}

.browser__bar {
  display: flex;
  gap: 0.55rem;
  align-items: center;
  padding: 0.4rem 0.55rem;
  border-bottom: 1px solid var(--line);
  background: var(--bg-deep);
}

.browser__dots {
  display: flex;
  flex: none;
  gap: 0.25rem;
}

.browser__dots i {
  width: 0.42rem;
  height: 0.42rem;
  border-radius: 999px;
  background: var(--line);
}

.browser__url {
  display: flex;
  gap: 0.3rem;
  align-items: center;
  overflow: hidden;
  padding: 0.1rem 0.6rem;
  border: 1px solid var(--line);
  border-radius: 999px;
  background: var(--surface);
  font-size: 0.66rem;
  color: var(--muted);
  white-space: nowrap;
}

.browser__url svg {
  flex: none;
  width: 0.6rem;
  height: 0.6rem;
  fill: none;
  stroke: currentColor;
  stroke-width: 2;
}

.shot {
  background: var(--surface);
}

.shot__bar {
  display: flex;
  gap: 0.5rem;
  align-items: center;
  padding: 0.45rem 0.6rem;
  border-bottom: 1px solid var(--line);
  background: var(--bg-deep);
}

.shot__mark {
  display: grid;
  flex: none;
  place-items: center;
  width: 1.5rem;
  height: 1.5rem;
  border-radius: 0.4rem;
  background: var(--steel-deep);
  color: #fff;
  font-size: 0.6rem;
  font-weight: 700;
}

.shot__brand {
  overflow: hidden;
  font-size: 0.8rem;
  white-space: nowrap;
  text-overflow: ellipsis;
}

.shot__nav {
  display: flex;
  gap: 0.7rem;
  margin-left: auto;
}

.shot__nav i {
  font-size: 0.68rem;
  font-style: normal;
  color: var(--muted);
  white-space: nowrap;
}

/* Underlined, not filled — `NavActiveUnderline` is how the app marks it. */
.shot__nav i.is-on {
  padding-bottom: 0.1rem;
  border-bottom: 2px solid var(--link);
  color: var(--text);
  font-weight: 600;
}

/* `--steel-deep` rather than `--link`, which lightens in the dark theme: this
   is a filled button, and white on the light blue is the one pairing here that
   fails contrast. The mark above it is set the same way, for the same reason. */
.shot__cta {
  flex: none;
  padding: 0.22rem 0.55rem;
  border-radius: 0.3rem;
  background: var(--steel-deep);
  color: var(--snow);
  font-size: 0.66rem;
  font-weight: 600;
  white-space: nowrap;
}

.shot__day {
  display: flex;
  gap: 0.5rem;
  align-items: center;
  padding: 0.5rem 0.6rem;
  border-bottom: 1px solid var(--line);
  background: var(--chip);
  background: color-mix(in srgb, var(--link) 10%, transparent);
}

.shot__tile {
  display: grid;
  flex: none;
  place-items: center;
  width: 1.7rem;
  height: 1.7rem;
  border-radius: 0.35rem;
  background: var(--track);
  background: color-mix(in srgb, var(--link) 18%, transparent);
  color: var(--link);
}

.shot__tile svg {
  width: 0.95rem;
  height: 0.95rem;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.8;
  stroke-linecap: round;
}

.shot__when b {
  display: block;
  font-size: 0.82rem;
}

.shot__when i {
  font-size: 0.68rem;
  font-style: normal;
  color: var(--muted);
}

/* The accent as a left rule is the app's own mark for an event you are in. */
.shot__ev {
  display: flex;
  gap: 0.6rem;
  align-items: flex-start;
  justify-content: space-between;
  padding: 0.55rem 0.6rem 0.4rem;
  border-left: 3px solid var(--link);
}

.shot__evmain {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  gap: 0.2rem;
  justify-items: start;
  min-width: 0;
}

.shot__evmain b {
  font-size: 0.84rem;
}

.shot__badge {
  display: inline-flex;
  gap: 0.3rem;
  align-items: center;
  padding: 0.08rem 0.4rem;
  border: 1px solid var(--line);
  border-radius: 0.25rem;
  font-size: 0.62rem;
  font-weight: 600;
  color: var(--muted);
}

.shot__dot {
  flex: none;
  width: 0.35rem;
  height: 0.35rem;
  border-radius: 999px;
  background: var(--link);
}

.shot__meta {
  font-size: 0.7rem;
  font-variant-numeric: tabular-nums;
  color: var(--muted);
}

/* The reset makes every `svg` a block; these three sit INSIDE a sentence. */
.shot__meta svg {
  display: inline-block;
  width: 0.78rem;
  height: 0.78rem;
  margin-right: 0.12rem;
  vertical-align: -0.13rem;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.8;
  stroke-linecap: round;
  stroke-linejoin: round;
}

.shot__price {
  flex: none;
  font-size: 0.82rem;
  font-variant-numeric: tabular-nums;
  color: var(--link);
  white-space: nowrap;
}

.shot__fill {
  padding: 0 0.6rem 0.55rem 0.75rem;
}

.shot__split {
  margin-top: 0.4rem;
  font-size: 0.7rem;
  color: var(--muted);
}

.shot__foot {
  padding: 0.45rem 0.6rem;
  border-top: 1px solid var(--line);
  background: var(--bg-deep);
  font-size: 0.7rem;
  font-weight: 600;
  color: var(--link);
}

.meter {
  height: 4px;
  margin-top: 0.9rem;
  border-radius: 2px;
  background: var(--track);
  overflow: hidden;
}

.meter span {
  display: block;
  width: 75%;
  height: 100%;
  background: linear-gradient(90deg, var(--steel), var(--gold));
}

.shot .meter {
  margin-top: 0;
}

.shot .meter span {
  background: var(--link);
}

/* ------------------------------------------------------ audience chooser -- */
/*
 * Two audiences, one page, zero JavaScript.
 *
 * The two radios are emitted at the top of <main>, as siblings of every section
 * that follows, which is what lets `:checked ~ [data-track]` hide the track the
 * reader did not pick. Both tracks stay in the HTML, so a crawler, reader mode
 * and print all get the whole offer.
 *
 * The inputs are CLIPPED, never `display: none` — hiding them that way takes
 * them out of the tab order and turns the segmented control into a mouse-only
 * device. The focus ring is drawn on the label instead, since the input the
 * keyboard is actually on has no pixels of its own.
 */

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

/*
 * One row on a wide screen, three stacked rows on a phone — where the eyebrow,
 * squeezed into a flex row beside a full-width group, broke "JE SUIS…" over two
 * lines. It gets its own row here instead.
 */
.who {
  display: grid;
  justify-items: start;
  gap: 0.85rem;
}

.who .eyebrow {
  margin-bottom: 0;
}

/*
 * Stacked on a phone, side by side from 720px: the French labels — "Un club ou
 * une association", "Une boutique de jeux" — measure 446px in a row, which
 * overflowed a 390px viewport horizontally.
 *
 * The pill radius belongs to the ROW form only. Kept on the stacked form it
 * draws an oval around two options and reads as a rendering accident, so the
 * phone gets a rounded rectangle — with the option's radius derived from the
 * group's, minus the padding between them, which is what makes the two corners
 * concentric instead of merely both round.
 */
.who__group {
  --who-pad: 0.35rem;

  display: grid;
  width: 100%;
  gap: var(--who-pad);
  padding: var(--who-pad);
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  background: var(--surface);
}

.who__option {
  padding: 0.6rem 1.25rem;
  border-radius: calc(var(--radius-lg) - var(--who-pad));
  font-size: 0.94rem;
  font-weight: 600;
  text-align: center;
  color: var(--muted);
  cursor: pointer;
  transition:
    color 0.15s ease,
    background-color 0.15s ease;
}

.who__option:hover {
  color: var(--text);
}

.who__note {
  font-size: 0.86rem;
  color: var(--muted);
}

#who-community:checked ~ .who-band .who__option[for='who-community'],
#who-business:checked ~ .who-band .who__option[for='who-business'] {
  background: var(--gold);
  color: var(--ink);
}

#who-community:focus-visible ~ .who-band .who__option[for='who-community'],
#who-business:focus-visible ~ .who-band .who__option[for='who-business'] {
  outline: 2px solid var(--accent-ring);
  outline-offset: 3px;
}

#who-business:checked ~ [data-track='community'],
#who-community:checked ~ [data-track='business'] {
  display: none;
}

/* --------------------------------------------------------------- cards --- */

.grid {
  display: grid;
  gap: 1px;
  margin-top: clamp(2.25rem, 4vw, 3rem);
  background: var(--line);
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  overflow: hidden;
}

.cell {
  padding: clamp(1.4rem, 2.4vw, 1.9rem);
  background: var(--card);
  transition: background-color 0.2s ease;
}

.cell:hover {
  background: var(--card-hover);
}

.cell__tag {
  display: inline-block;
  margin-bottom: 0.9rem;
  padding: 0.2rem 0.5rem;
  border: 1px solid var(--line);
  border-radius: 4px;
  font-size: 0.65rem;
  font-weight: 600;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  color: var(--muted);
}

.cell h3 {
  font-size: 1.08rem;
  font-weight: 700;
  letter-spacing: -0.012em;
  line-height: 1.35;
}

.cell p {
  margin-top: 0.6rem;
  font-size: 0.93rem;
  color: var(--muted);
}

.cell__n {
  display: block;
  margin-bottom: 0.85rem;
  font-size: 0.72rem;
  font-weight: 600;
  letter-spacing: 0.14em;
  color: var(--accent-ink);
}

/* ----------------------------------------------------------- case study -- */

.case {
  display: grid;
  gap: clamp(2rem, 4vw, 3rem);
  margin-top: clamp(2rem, 4vw, 2.75rem);
}

/*
 * "Go and look at it" — the case study's evidence, offered rather than
 * asserted. The trailing arrow is drawn in CSS so the label stays translatable
 * text with no glyph baked into three content files.
 */
.case__visit {
  margin-top: 1.25rem;
}

.link-out {
  font-weight: 600;
  text-decoration: none;
  border-bottom: 1px solid var(--link-soft);
  padding-bottom: 0.1em;
}

.link-out::after {
  content: " ↗";
  font-weight: 400;
}

.link-out:hover {
  border-bottom-color: var(--link);
}

/*
 * The stats label opens the case study's second column — there is no testimonial
 * above it any more, and the `.case` grid gap already separates the two columns
 * when they stack on a phone, so it carries no top margin of its own.
 */
.stats__label {
  margin-top: 0;
  font-size: 0.76rem;
  font-weight: 500;
  letter-spacing: 0.02em;
  color: var(--muted);
}

.stats {
  display: grid;
  grid-template-columns: repeat(3, 1fr);
  gap: 1px;
  background: var(--line);
  border: 1px solid var(--line);
  border-radius: var(--radius);
  overflow: hidden;
}

.stats div {
  padding: 1.1rem 1rem;
  background: var(--card);
}

.stats b {
  display: block;
  font-family: var(--display);
  font-size: 1.7rem;
  font-weight: 700;
  letter-spacing: -0.02em;
  font-variant-numeric: tabular-nums;
  color: var(--text);
}

.stats span {
  display: block;
  margin-top: 0.35rem;
  font-size: 0.74rem;
  line-height: 1.45;
  color: var(--muted);
}

/*
 * The release strip reuses `.stats`, but its values are DATES where the case
 * study's are short numerals ("229", "79", "714"). "7. Dezember 2025" set at
 * 1.7rem does not fit a third of a 375px viewport — and because `.stats` is
 * `overflow: hidden`, the third cell was CLIPPED rather than pushing the page
 * sideways. Nothing looked broken; the date was just gone. Caught by the
 * 375px leg of the layout matrix in English and German (French's shorter
 * label fitted, which is exactly why one language is not a check).
 */
.stats--dates b {
  font-size: 1.15rem;
  letter-spacing: -0.01em;
}

@media (max-width: 640px) {
  .stats--dates {
    grid-template-columns: 1fr;
  }
}

/* -------------------------------------------------------------- screens -- */

.frames {
  display: grid;
  gap: 1.25rem;
  margin-top: clamp(2rem, 4vw, 2.75rem);
}

.frame {
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  overflow: hidden;
  background: var(--surface);
}

.frame__shot {
  position: relative;
  aspect-ratio: 16 / 10;
  border-bottom: 1px dashed var(--alert-line);
  background-image: repeating-linear-gradient(
    135deg,
    var(--hatch) 0 10px,
    transparent 10px 20px
  );
}

.frame__shot::after {
  content: attr(data-label);
  position: absolute;
  inset: auto 0 0 0;
  padding: 0.5rem 0.9rem;
  font-size: 0.65rem;
  font-weight: 600;
  letter-spacing: 0.12em;
  text-transform: uppercase;
  /* The alert colour means "not real yet" on this page. The case-study quote
     used to carry the same signal; these three frames are the last thing on the
     page still wearing it. Gold is the brand; it must never mark a
     placeholder. */
  color: var(--alert);
}

/*
 * A real capture, in the slot `.frame__shot` holds when there is none. It takes
 * none of the placeholder's signals — no dashed ember rule, no hatch, no
 * uppercase label over the corner — because those all mean "not real yet".
 * Anchored to the top so the product's header and first rows survive the crop
 * on a narrow card.
 */
.frame__img {
  display: block;
  width: 100%;
  height: auto;
  aspect-ratio: 16 / 10;
  object-fit: cover;
  object-position: top center;
  border-bottom: 1px solid var(--line);
  background: var(--surface);
}

/*
 * The whole thumbnail is the way in, with the word only appearing on hover or
 * keyboard focus — the shot itself is the affordance, and a permanent badge
 * over three cards is three pieces of furniture the reader has to look past.
 */
.frame__zoom {
  position: relative;
  display: block;
  cursor: zoom-in;
}

.frame__zoom-hint {
  position: absolute;
  right: 0.6rem;
  bottom: 0.7rem;
  padding: 0.3rem 0.6rem;
  border-radius: 999px;
  /* Fixed values, not tokens: this pill sits on a screenshot of a dark app in
     BOTH themes, so it takes its contrast from the image rather than the page. */
  border: 1px solid rgba(255, 255, 255, 0.25);
  background: rgba(3, 6, 16, 0.78);
  color: #fff;
  font-size: 0.68rem;
  font-weight: 600;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  opacity: 0;
  transition: opacity 0.15s ease;
}

.frame__zoom:hover .frame__zoom-hint,
.frame__zoom:focus-visible .frame__zoom-hint {
  opacity: 1;
}

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

.frame__meta {
  padding: 1rem 1.1rem;
}

/* ------------------------------------------------------------ lightbox -- */

/*
 * Open state is `:target`, so the reader's back button closes it and a blocked
 * bundle changes nothing. It is `display: none` until targeted rather than
 * merely transparent, so a closed lightbox is out of the tab order and out of
 * the accessibility tree without needing `inert`.
 */
.lightbox {
  display: none;
}

.lightbox:target {
  position: fixed;
  inset: 0;
  z-index: 90;
  display: grid;
  place-items: center;
  padding: clamp(1rem, 4vw, 3rem);
}

/* The scrim IS the close control — clicking anywhere outside the shot exits. */
.lightbox__scrim {
  position: absolute;
  inset: 0;
  background: rgba(3, 6, 16, 0.82);
  backdrop-filter: blur(3px);
}

.lightbox__inner {
  position: relative;
  max-width: min(1280px, 100%);
  /* Grid items floor at min-content, so an intrinsically wide shot would push
     the track past the viewport and take the scroll container with it. */
  min-width: 0;
  margin: 0;
}

.lightbox__inner img {
  display: block;
  width: 100%;
  height: auto;
  max-height: calc(100vh - 8rem);
  object-fit: contain;
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  background: var(--surface);
}

.lightbox__inner figcaption {
  margin-top: 0.85rem;
  text-align: center;
  font-size: 0.85rem;
  color: rgba(255, 255, 255, 0.72);
}

/*
 * Anchored to the SHOT, not to the viewport. Pinned to the window corner it
 * floated away from a centred image — furthest from it on exactly the narrow
 * screens where the gap is widest — and read as belonging to the page behind
 * rather than to the thing it closes.
 *
 * It hangs just OUTSIDE the corner, in the scrim, because these are screenshots
 * of applications: sat inside the corner it lands on whatever the captured app
 * keeps top-right, which in the back office is the user avatar. The narrow
 * breakpoint pulls it back inside, where there is no margin left to hang in.
 */
.lightbox__close {
  position: absolute;
  top: -1.15rem;
  right: -1.15rem;
  z-index: 2;
  display: grid;
  place-items: center;
  width: 2.5rem;
  height: 2.5rem;
  border-radius: 999px;
  border: 1px solid rgba(255, 255, 255, 0.22);
  background: rgba(3, 6, 16, 0.6);
  color: #fff;
  font-size: 1.4rem;
  line-height: 1;
  text-decoration: none;
}

.lightbox__close:hover {
  background: rgba(3, 6, 16, 0.9);
  border-color: rgba(255, 255, 255, 0.45);
}

/*
 * On a phone, a 16:10 screenshot fitted to the width is ~350px across — the
 * same postage stamp the reader tapped to escape, which makes the enlarge a
 * lie. So below this width the shot is sized by HEIGHT instead and pans
 * sideways: ~1100px of back office, legible, one thumb-drag from end to end.
 *
 * This is the case that matters most. A committee reads a link someone dropped
 * in the group chat, and it reads it on a phone.
 */
@media (max-width: 720px) {
  .lightbox:target {
    padding: 0.75rem;
  }

  .lightbox__scroll {
    /* Pinned to the viewport rather than to the parent, which the image would
       otherwise stretch out from under it. */
    max-width: calc(100vw - 1.5rem);
    overflow-x: auto;
    overscroll-behavior-x: contain;
    border-radius: var(--radius-lg);
  }

  .lightbox__inner img {
    width: auto;
    max-width: none;
    height: calc(100vh - 8rem);
    max-height: none;
    border-radius: 0;
  }

  /* No scrim margin left to hang in at this width — back inside the corner. */
  .lightbox__close {
    top: 0.6rem;
    right: 0.6rem;
  }
}

.frame__meta h3 {
  font-size: 0.98rem;
  font-weight: 700;
}

.frame__meta p {
  margin-top: 0.3rem;
  font-size: 0.86rem;
  color: var(--muted);
}

/* -------------------------------------------------------------- pricing -- */

.tiers {
  display: grid;
  gap: 1.25rem;
  margin-top: clamp(2rem, 4vw, 2.75rem);
}

.tier {
  display: flex;
  flex-direction: column;
  padding: clamp(1.5rem, 2.8vw, 2rem);
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  background: var(--surface);
}

.tier--featured {
  border-color: var(--feature-ring);
  box-shadow: var(--feature-glow);
}

.tier__name {
  font-size: 0.76rem;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--muted);
}

.tier__price {
  display: flex;
  align-items: baseline;
  gap: 0.45rem;
  margin-top: 0.9rem;
  font-family: var(--display);
  font-weight: 700;
  letter-spacing: -0.03em;
  font-variant-numeric: tabular-nums;
}

.tier__price b {
  font-size: clamp(2.5rem, 5vw, 3.2rem);
  line-height: 1;
  font-weight: 700;
}

.tier__cur {
  font-family: var(--sans);
  font-size: 0.9rem;
  letter-spacing: 0.04em;
  color: var(--muted);
  font-weight: 600;
}

.tier__per {
  font-family: var(--sans);
  font-size: 0.8rem;
  letter-spacing: 0;
  color: var(--muted);
  font-weight: 500;
}

.tier__summary {
  margin-top: 0.9rem;
  font-size: 0.93rem;
  color: var(--muted);
}

.tier .btn {
  margin-top: auto;
  align-self: flex-start;
}

.tier__spacer {
  height: 1.5rem;
}

.matrix {
  width: 100%;
  margin-top: clamp(2rem, 4vw, 2.5rem);
  border-collapse: collapse;
  font-size: 0.9rem;
}

.matrix caption {
  text-align: left;
  padding-bottom: 0.9rem;
  font-size: 0.72rem;
  font-weight: 600;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--muted);
}

.matrix th,
.matrix td {
  padding: 0.85rem 0.6rem;
  border-bottom: 1px solid var(--line);
  text-align: left;
  vertical-align: top;
  font-weight: 400;
}

.matrix thead th {
  font-size: 0.72rem;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--muted);
}

/* Value columns were 8.5rem when every cell was a tick or one word. The rows
   are derived from the module catalog now and a partial tier lists the
   modules it carries by name, so the columns take a share of the width and
   keep the old value only as a floor. */
.matrix td + td,
.matrix thead th + th {
  width: 22%;
  min-width: 8.5rem;
  text-align: right;
  font-variant-numeric: tabular-nums;
}

/* On a phone two 8.5rem floors leave the label column a word wide; share the
   width instead and let the names wrap. */
@media (max-width: 640px) {
  .matrix td + td,
  .matrix thead th + th {
    width: 30%;
    min-width: 0;
  }
}

.matrix td:first-child {
  color: var(--muted);
}

.yes {
  color: var(--accent-ink);
}

.no {
  color: var(--muted);
  opacity: 0.5;
}

.addons {
  display: grid;
  gap: 1rem;
  margin-top: clamp(2rem, 4vw, 2.5rem);
}

.addon {
  padding: 1.25rem 1.4rem;
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  background: var(--surface);
}

.addon__head {
  display: flex;
  flex-wrap: wrap;
  align-items: baseline;
  justify-content: space-between;
  gap: 0.75rem;
}

.addon h3 {
  font-size: 1rem;
  font-weight: 700;
}

.addon__price {
  font-size: 0.88rem;
  font-weight: 700;
  letter-spacing: 0.01em;
  font-variant-numeric: tabular-nums;
  color: var(--accent-ink);
}

.addon p {
  margin-top: 0.5rem;
  font-size: 0.9rem;
  color: var(--muted);
}

.closer {
  margin-top: clamp(2rem, 4vw, 2.5rem);
  padding-top: 1.5rem;
  border-top: 1px solid var(--line);
  font-size: 1.02rem;
  max-width: 70ch;
  color: var(--muted);
}

/* ------------------------------------------------------------- founding -- */
/*
 * The one inverted slab on the page. It sits exactly where the conversion
 * pressure is, and nothing else is allowed to compete with it. Identical in
 * both themes on purpose: gold with navy on it is the brand, not a mode.
 */

.founding {
  display: grid;
  gap: 1.75rem;
  padding: clamp(1.75rem, 4vw, 3rem);
  border-radius: var(--radius-lg);
  background: linear-gradient(135deg, var(--gold), var(--gold-lit));
  color: var(--ink);
}

.founding .eyebrow {
  color: rgba(2, 8, 23, 0.62);
  margin-bottom: 1.1rem;
}

.founding .eyebrow::before {
  background: var(--ink);
}

.founding h2 {
  font-family: var(--display);
  font-size: clamp(1.75rem, 3.3vw, 2.5rem);
  font-weight: 700;
  letter-spacing: -0.025em;
  line-height: 1.08;
  max-width: 20ch;
}

.founding p {
  margin-top: 1rem;
  max-width: 56ch;
  font-size: 1rem;
  color: rgba(2, 8, 23, 0.78);
}

.founding__slots {
  display: flex;
  align-items: baseline;
  /* Wider than it was: the display face carries almost no side bearing, so the
     numeral and its label touched at the old 0.6rem. */
  gap: 0.9rem;
  font-family: var(--display);
  font-weight: 800;
  font-variant-numeric: tabular-nums;
}

.founding__slots b {
  font-size: clamp(3rem, 8vw, 4.5rem);
  letter-spacing: -0.04em;
  line-height: 0.9;
}

.founding__slots span {
  font-family: var(--sans);
  font-size: 0.74rem;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: rgba(2, 8, 23, 0.7);
}

.founding__expiry {
  margin-top: 1.5rem;
  padding-top: 1.1rem;
  border-top: 1px solid rgba(2, 8, 23, 0.22);
  font-size: 0.8rem;
  font-weight: 500;
  letter-spacing: 0.01em;
  color: rgba(2, 8, 23, 0.75);
}

.founding__expiry b {
  font-weight: 700;
  color: var(--ink);
}

/**
 * The line that says what one annual price actually covers. It sits under the
 * tiers because that is where a reader does the arithmetic — and it is the only
 * qualification on "unlimited", so it gets the accent rule rather than the
 * small print treatment.
 */
.pricing-scope {
  margin-top: clamp(1.75rem, 3vw, 2.25rem);
  padding-left: 1.1rem;
  border-left: 2px solid var(--accent-line);
  font-size: 1.02rem;
  max-width: 62ch;
}

/* ------------------------------------------------------------- promises -- */

.promises__list {
  display: grid;
  gap: 0;
  margin-top: clamp(2rem, 4vw, 2.75rem);
  border-top: 1px solid var(--line);
}

.promise {
  display: grid;
  gap: 0.5rem;
  padding-block: 1.5rem;
  border-bottom: 1px solid var(--line);
}

.promise h3 {
  font-family: var(--display);
  font-size: 1.1rem;
  font-weight: 700;
  letter-spacing: -0.015em;
}

.promise p {
  font-size: 0.95rem;
  color: var(--muted);
  max-width: 70ch;
}

/* ----------------------------------------------------------- releases -- */

/*
 * The list is a TIMELINE: one continuous rail down the left, a gold node per
 * release, a larger hollow node per month. The rail is what makes the shape of
 * the history readable at a glance — that releases run in one line, that August
 * is dense and January is not, and that nothing sits between May and August.
 *
 * The rail is drawn once on the container rather than as a border on each row,
 * so it does not break at a month heading: months are stops ALONG the line, not
 * separate lists. Its geometry is two custom properties — change `--rail` or
 * `--node` and the line, both node sizes and every indent follow.
 *
 * `.releases` is its OWN element inside `.shell`, never both classes on one
 * div: `.shell` owns `padding-inline: var(--gutter)`, so a `padding-left` here
 * would override the page gutter and drag the whole list to the viewport edge.
 *
 * No new colour token — `--accent-line`, `--chip` and `--bg` are already defined
 * in all three theme blocks, so the rail is right in both themes by
 * construction rather than by remembering to update a third place.
 */
.releases {
  --rail: 0.5rem;
  --node: 0.6875rem;
  position: relative;
  padding-left: calc(var(--rail) * 2 + var(--node));
}

/*
 * The rail. It fades out at both ends rather than stopping flat — a 1px line
 * meeting the band padding at full strength reads as a clipped border, while a
 * fade reads as a span that continues beyond what is on screen.
 */
.releases::before {
  content: '';
  position: absolute;
  left: calc(var(--rail) + var(--node) / 2 - 0.5px);
  top: 0.5rem;
  bottom: 1.5rem;
  width: 1px;
  /*
   * Tinted with the accent, not `--line`. A hairline of `--line` measured
   * #dbe3ef against a #f6f8fc ground — technically painted, visually absent, so
   * the nodes read as loose dots rather than as stops on one thread. The mix
   * keeps it quiet enough to sit behind the copy while still being a line
   * somebody can follow.
   */
  background: linear-gradient(
    to bottom,
    transparent,
    color-mix(in srgb, var(--accent-line) 50%, transparent) 2rem,
    color-mix(in srgb, var(--accent-line) 50%, transparent) calc(100% - 2rem),
    transparent
  );
}

.rel-month {
  position: relative;
  margin-top: 2.75rem;
  padding-bottom: 0.35rem;
  font-family: var(--display);
  font-size: 0.95rem;
  font-weight: 700;
  letter-spacing: -0.01em;
  /* Stronger than the rows' metadata: the month is what a reader scans for when
     they want "what happened in the spring", so it must not be the same grey as
     the dates beneath it. NEVER add `text-transform` — French lowercases its
     months and German does not, and a test pins that. */
  color: var(--text);
}

.rel-month:first-child {
  margin-top: 0;
}

/*
 * The month node: larger, hollow, filled with the page ground so the rail does
 * not show through. Hollow-versus-filled carries the hierarchy — a bigger dot
 * of the same kind would just read as "a more important release".
 */
.rel-month::before {
  content: '';
  position: absolute;
  left: calc((var(--rail) + var(--node)) * -1 - 0.125rem);
  top: 0.15rem;
  width: calc(var(--node) + 0.25rem);
  height: calc(var(--node) + 0.25rem);
  box-sizing: border-box;
  border: 2px solid var(--accent-line);
  border-radius: 50%;
  background: var(--bg);
}

.rel {
  position: relative;
  display: grid;
  gap: 0.4rem;
  padding-block: 1.15rem;
}

/*
 * The release node, aligned with the META row — the date and the audience tag —
 * because that is the line the eye lands on when scanning down the rail. Its
 * offset is derived from the row's own `padding-block`, so changing that above
 * moves the node with it instead of leaving it stranded.
 */
.rel::before {
  content: '';
  position: absolute;
  left: calc((var(--rail) + var(--node)) * -1);
  top: calc(1.15rem + 0.3rem);
  width: var(--node);
  height: var(--node);
  border-radius: 50%;
  background: var(--accent-line);
  /* Hides the rail behind the node without having to break the line. */
  box-shadow: 0 0 0 0.1875rem var(--bg);
}

.rel__meta {
  display: flex;
  align-items: center;
  flex-wrap: wrap;
  gap: 0.6rem;
  font-size: 0.8rem;
  color: var(--muted);
}

/*
 * The date is the row's name and its permalink, so it carries the row's colour
 * rather than the metadata grey. The tag beside it stays quiet: two emphasised
 * things side by side is neither of them emphasised.
 */
.rel__anchor {
  font-weight: 600;
  font-variant-numeric: tabular-nums;
  color: var(--text);
  text-decoration: none;
}

.rel__anchor:hover,
.rel__anchor:focus-visible {
  color: var(--accent-ink);
  text-decoration: underline;
  text-underline-offset: 0.2em;
}

.rel__tag {
  padding: 0.12rem 0.42rem;
  border-radius: 4px;
  background: var(--chip);
  font-size: 0.6rem;
  font-weight: 600;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--muted);
}

.rel__headline {
  font-family: var(--display);
  font-size: 1.05rem;
  font-weight: 700;
  letter-spacing: -0.015em;
  color: var(--text);
}

.rel__bullets {
  display: grid;
  gap: 0.3rem;
  margin: 0;
  padding-left: 1rem;
  max-width: 68ch;
  font-size: 0.92rem;
  line-height: 1.6;
  color: var(--muted);
}

/* The markers pick up the rail's colour, so the eye reads one accent down the
   page rather than gold nodes beside grey list bullets. */
.rel__bullets li::marker {
  color: var(--accent-line);
}

.rel__bullets li {
  /*
   * German compounds do not break at a hyphen the way the other two languages
   * do, and these are list items inside a 375px viewport. Without this a single
   * long noun pushes the row past the edge and takes the whole page's
   * horizontal scroll with it.
   */
  overflow-wrap: anywhere;
}

.foot__pages {
  display: grid;
  gap: 0.4rem;
  align-content: start;
}


/* ------------------------------------------------------------ bring/get -- */

.columns {
  display: grid;
  gap: clamp(2rem, 4vw, 3rem);
  margin-top: clamp(2rem, 4vw, 2.75rem);
}

.column h3 {
  font-size: 0.74rem;
  font-weight: 700;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--accent-ink);
  padding-bottom: 0.9rem;
  border-bottom: 1px solid var(--line);
}

.column ul {
  display: grid;
  gap: 0.85rem;
  margin-top: 1.1rem;
}

.column li {
  position: relative;
  padding-left: 1.4rem;
  font-size: 0.95rem;
  color: var(--muted);
}

.column li::before {
  content: '';
  position: absolute;
  left: 0;
  top: 0.62em;
  width: 6px;
  height: 6px;
  border-radius: 1px;
  background: var(--accent-line);
}

/* ------------------------------------------------------------------ faq -- */

.faq {
  margin-top: clamp(2rem, 4vw, 2.75rem);
  border-top: 1px solid var(--line);
}

.faq details {
  border-bottom: 1px solid var(--line);
}

.faq summary {
  display: flex;
  align-items: baseline;
  justify-content: space-between;
  gap: 1.5rem;
  padding-block: 1.25rem;
  cursor: pointer;
  font-size: 1.02rem;
  font-weight: 600;
  letter-spacing: -0.01em;
  list-style: none;
}

.faq summary::-webkit-details-marker {
  display: none;
}

.faq summary::after {
  content: '+';
  flex: 0 0 auto;
  font-size: 1.25rem;
  font-weight: 400;
  line-height: 1;
  color: var(--accent-ink);
}

.faq details[open] summary::after {
  content: '–';
}

.faq p {
  padding-bottom: 1.4rem;
  max-width: 72ch;
  font-size: 0.95rem;
  color: var(--muted);
}

/* ---------------------------------------------------------- final + foot -- */

.final {
  text-align: left;
}

.final__note {
  margin-top: 1.1rem;
  font-size: 0.8rem;
  color: var(--muted);
}

.foot {
  padding-block: clamp(2.5rem, 5vw, 3.5rem);
  border-top: 1px solid var(--line);
  font-size: 0.86rem;
  color: var(--muted);
}

.foot__top {
  display: grid;
  gap: 1.5rem;
}

.foot__brand {
  font-family: var(--display);
  font-weight: 700;
  font-size: 1rem;
  letter-spacing: -0.015em;
  color: var(--text);
}

.foot__lang {
  display: flex;
  align-items: center;
  gap: 0.75rem;
}

.foot__lang-label {
  font-size: 0.78rem;
  letter-spacing: 0.08em;
  text-transform: uppercase;
  color: var(--muted);
}

.foot__legal {
  display: grid;
  gap: 0.7rem;
  margin-top: 2rem;
  padding-top: 1.5rem;
  border-top: 1px solid var(--line);
  font-size: 0.78rem;
  line-height: 1.7;
}

/* ------------------------------------------------------------ responsive -- */

/*
 * On a phone the buttons stop being a row and become a stack of ONE width.
 *
 * `flex-wrap` gave each of them its own — "See it in your colours" a full line,
 * "See a live demo" two thirds of one under it — which reads as two ranks of
 * button rather than as a choice between two. A grid with a single column makes
 * both stretch to the same edge, and it is the same rule for the hero, the
 * closing call to action and the preview page's send block, so none of them can
 * drift from the others.
 */
@media (max-width: 559px) {
  .btn-row {
    display: grid;
  }
}

@media (min-width: 720px) {
  .foot__top {
    grid-template-columns: 2fr 1fr 1fr;
  }

  .grid--3 {
    grid-template-columns: repeat(3, 1fr);
  }

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

  .who {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 0.85rem 1.5rem;
  }

  .who__group {
    --who-pad: 0.3rem;

    width: auto;
    grid-auto-flow: column;
    border-radius: 999px;
  }

  .who__option {
    padding-block: 0.5rem;
    border-radius: 999px;
    white-space: nowrap;
  }

  .frames {
    grid-template-columns: repeat(3, 1fr);
  }

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

  /* One tier is one card, not a half-empty two-column row. */
  .tiers--one {
    grid-template-columns: minmax(0, 26rem);
  }

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

  .founding {
    grid-template-columns: auto 1fr;
    align-items: center;
    gap: clamp(2rem, 5vw, 4rem);
  }

  .foot__top {
    grid-template-columns: 1fr auto;
    align-items: start;
  }

  .promise {
    grid-template-columns: 15rem 1fr;
    gap: 1.5rem;
    align-items: baseline;
  }
}

@media (min-width: 1000px) {
  .hero__inner {
    grid-template-columns: 1.05fr 0.95fr;
    align-items: center;
  }

  .case {
    grid-template-columns: 1.1fr 0.9fr;
    align-items: start;
  }
}

/* --------------------------------------------------------------- studio -- */
/*
 * The preview page: a form on the left, a schematic of the product on the
 * right, and no JavaScript in the load-bearing parts.
 *
 * The tabs and the mock's light/dark are RADIOS declared at the top of the
 * section, as siblings of the grid — the same device as the audience chooser
 * above, and for the same reason. `:checked ~ .studio__grid …` is what makes a
 * page with a blocked bundle still switch surface and still switch theme, and
 * it is why every rule in this block reaches across from an input to something
 * two levels down rather than styling a class the script would have to write.
 *
 * The mock's palette is a SEPARATE token set (`--pv-*`) scoped to `.pv`, and
 * never the page's own. Two reasons, both load-bearing: the reader chooses the
 * mock's theme independently of the theme they are reading the page in — a
 * light-mode reader has to be able to see the dark product — and the accent is
 * a colour that arrives at runtime from a picker, which is exactly the kind of
 * value that must not be able to reach the page's chrome.
 */

/*
 * The five radios, clipped but still focusable — and `fixed`, which is the one
 * part of this that is not the usual visually-hidden recipe.
 *
 * They have to be siblings of the grid to reach it with `~`, so they sit at the
 * top of the section while their labels sit in the two columns below. Clicking
 * a label moves focus to the input, and the browser then scrolls that input
 * into view: `position: absolute` leaves it at the top of the section, so on a
 * phone — where the form is a screen and a half above the mock — every tap on a
 * tab threw the reader back to the headline. Pinned to the viewport it is
 * always already in view, so there is nothing to scroll to, and a 1px box in
 * the corner takes no clicks.
 */
.vis-hidden {
  position: fixed;
  top: 0;
  left: 0;
  width: 1px;
  height: 1px;
  margin: 0;
  padding: 0;
  border: 0;
  overflow: hidden;
  clip-path: inset(50%);
  pointer-events: none;
  white-space: nowrap;
}

.studio {
  padding-block: clamp(2.5rem, 6vw, 4rem) var(--band-y);
}

.studio__head {
  max-width: 46ch;
  margin-bottom: clamp(2rem, 4vw, 2.75rem);
}

.studio__title {
  margin: 0.35rem 0 0.9rem;
  font-family: var(--display);
  font-size: clamp(2rem, 5vw, 2.9rem);
  font-weight: 700;
  line-height: 1.05;
  letter-spacing: -0.02em;
}

.studio__grid {
  display: grid;
  gap: clamp(1.5rem, 3vw, 2.5rem);
  align-items: start;
}

/* No `action`, no submit: the element is here for the labels and the grouping.
   Nothing on this page is posted anywhere. */
.studio__form {
  display: grid;
  /*
   * `minmax(0, 1fr)`, never the implicit `auto`: a file input's max-content
   * width is whatever Chrome feels the button plus "No file chosen" needs —
   * ~330px — and an auto track sized to that pushed every field 40px past the
   * card's own padding, on the one screen where the reader is typing.
   */
  grid-template-columns: minmax(0, 1fr);
  gap: 1.15rem;
  padding: clamp(1.1rem, 3vw, 1.5rem);
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  background: var(--surface);
}

.studio__legend {
  margin: 0;
  font-family: var(--display);
  font-size: 1.05rem;
  font-weight: 700;
}

.field {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  gap: 0.4rem;
  justify-items: start;
}

.field > * {
  max-width: 100%;
}

.field__label {
  font-size: 0.85rem;
  font-weight: 600;
}

.field__hint,
.field__warn {
  margin: 0;
  font-size: 0.78rem;
  line-height: 1.5;
  color: var(--muted);
}

.field__warn {
  padding-left: 0.6rem;
  border-left: 2px solid var(--alert-line);
  color: var(--alert);
}

.field__warn[hidden] {
  display: none;
}

.input {
  width: 100%;
  padding: 0.55rem 0.7rem;
  border: 1px solid var(--line);
  border-radius: var(--radius);
  background: var(--bg);
  color: var(--text);
  font-family: var(--sans);
  font-size: 0.92rem;
}

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

.color {
  display: flex;
  gap: 0.5rem;
  width: 100%;
}

/*
 * The one control on the page drawn by the operating system. Sized and framed
 * here; what opens when it is pressed is the platform's own colour picker, and
 * that is the whole reason the presets below exist beside it.
 */
.color__well {
  flex: none;
  width: 3rem;
  height: 2.6rem;
  padding: 0.2rem;
  border: 1px solid var(--line);
  border-radius: var(--radius);
  background: var(--bg);
  cursor: pointer;
}

.color__hex {
  flex: 1;
  min-width: 0;
  font-variant-numeric: tabular-nums;
  letter-spacing: 0.04em;
  text-transform: lowercase;
}

.swatches {
  display: flex;
  flex-wrap: wrap;
  gap: 0.4rem;
}

.swatch {
  width: 1.7rem;
  height: 1.7rem;
  padding: 0;
  border: 1px solid var(--line);
  border-radius: 999px;
  background: var(--swatch);
  cursor: pointer;
  transition: transform 0.15s ease;
}

.swatch:hover {
  transform: scale(1.12);
}

.seg {
  --seg-pad: 0.3rem;

  display: inline-grid;
  grid-auto-flow: column;
  gap: var(--seg-pad);
  padding: var(--seg-pad);
  border: 1px solid var(--line);
  border-radius: 999px;
  background: var(--bg);
}

.seg__option {
  padding: 0.35rem 1.1rem;
  border-radius: 999px;
  font-size: 0.85rem;
  font-weight: 600;
  color: var(--muted);
  cursor: pointer;
  transition:
    color 0.15s ease,
    background-color 0.15s ease;
}

.seg__option:hover {
  color: var(--text);
}

.file {
  max-width: 100%;
  font-family: var(--sans);
  font-size: 0.82rem;
  color: var(--muted);
}

.file::file-selector-button {
  margin-right: 0.6rem;
  padding: 0.4rem 0.8rem;
  border: 1px solid var(--line);
  border-radius: var(--radius);
  background: var(--bg);
  color: var(--text);
  font-family: var(--sans);
  font-size: 0.82rem;
  font-weight: 600;
  cursor: pointer;
}

.linkish {
  padding: 0;
  border: 0;
  background: none;
  color: var(--link);
  font-family: var(--sans);
  font-size: 0.8rem;
  text-decoration: underline;
  text-decoration-color: var(--link-soft);
  text-underline-offset: 0.2em;
  cursor: pointer;
}

.linkish[hidden] {
  display: none;
}

.linkish--reset {
  justify-self: start;
  color: var(--muted);
}

/*
 * FOUR tabs since the partner portal joined, and the sizing had to change with
 * the count. `grid-auto-flow: column` with the default `auto` columns sizes
 * each tab to its own label, so the strip grew past its container on the
 * longest pair the corpus holds — German's "Öffentliche Website" beside
 * "Partnerportal". `minmax(0, 1fr)` makes the four share the width and lets a
 * long label wrap inside its own tab instead of pushing the strip wider.
 */
.tabs {
  --tabs-pad: 0.3rem;

  display: grid;
  grid-auto-flow: column;
  grid-auto-columns: minmax(0, 1fr);
  gap: var(--tabs-pad);
  margin-bottom: 0.85rem;
  padding: var(--tabs-pad);
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  background: var(--surface);
}

.tab {
  min-width: 0;
  padding: 0.45rem 0.6rem;
  border-radius: calc(var(--radius-lg) - var(--tabs-pad));
  font-size: 0.82rem;
  font-weight: 600;
  text-align: center;
  color: var(--muted);
  cursor: pointer;
  transition:
    color 0.15s ease,
    background-color 0.15s ease;
}

.tab:hover {
  color: var(--text);
}

#pv-view-site:checked ~ .studio__grid .tab[for='pv-view-site'],
#pv-view-admin:checked ~ .studio__grid .tab[for='pv-view-admin'],
#pv-view-vendor:checked ~ .studio__grid .tab[for='pv-view-vendor'],
#pv-view-partner:checked ~ .studio__grid .tab[for='pv-view-partner'],
#pv-theme-light:checked ~ .studio__grid .seg__option[for='pv-theme-light'],
#pv-theme-dark:checked ~ .studio__grid .seg__option[for='pv-theme-dark'] {
  background: var(--gold);
  color: var(--ink);
}

/* The input the keyboard is actually on has no pixels of its own. */
#pv-view-site:focus-visible ~ .studio__grid .tab[for='pv-view-site'],
#pv-view-admin:focus-visible ~ .studio__grid .tab[for='pv-view-admin'],
#pv-view-vendor:focus-visible ~ .studio__grid .tab[for='pv-view-vendor'],
#pv-view-partner:focus-visible ~ .studio__grid .tab[for='pv-view-partner'],
#pv-theme-light:focus-visible ~ .studio__grid .seg__option[for='pv-theme-light'],
#pv-theme-dark:focus-visible ~ .studio__grid .seg__option[for='pv-theme-dark'] {
  outline: 2px solid var(--accent-ring);
  outline-offset: 3px;
}

.studio__caption {
  margin: 0.8rem 0 0;
  font-size: 0.78rem;
  line-height: 1.5;
  color: var(--muted);
}

/* ------------------------------------------------------------ the mock --- */

.pv {
  --pv-accent: #2f6fed;
  --pv-accent-ink: #ffffff;
  --pv-bg: #ffffff;
  --pv-surface: #f5f8fc;
  --pv-line: #e2e8f2;
  --pv-text: #0d1729;
  --pv-muted: #64748b;

  display: grid;
  grid-template-columns: minmax(0, 1fr);
  /*
   * One floor for all three, sized to the tallest: switching surface must not
   * resize the page under the reader's cursor, and a sticky stage beside a
   * scrolling form makes any jump doubly visible. Each view stretches to it and
   * the leftover reads as what it is — the app's own empty canvas.
   */
  min-height: 30rem;
  overflow: hidden;
  border: 1px solid var(--line);
  border-radius: var(--radius-lg);
  background: var(--pv-bg);
  color: var(--pv-text);
  box-shadow: var(--panel-shadow);
  font-size: 0.78rem;
  line-height: 1.45;
}

#pv-theme-dark:checked ~ .studio__grid .pv {
  --pv-bg: #0b1220;
  --pv-surface: #131e31;
  --pv-line: #24334b;
  --pv-text: #e9eef8;
  --pv-muted: #93a4bd;
}

.pv__view {
  display: none;
  /*
   * Declared on the hidden base rule, where it applies to whichever view is
   * revealed: a grid whose implicit column is `auto` sizes to its widest child
   * and overflows its own box, and `.pv` clips — so on a 390px phone the event
   * rows were not narrow, they were cut off mid-button.
   */
  grid-template-columns: minmax(0, 1fr);
  grid-template-rows: auto minmax(0, 1fr);
}

/*
 * `grid`, not `block`: the mock has a floor (`min-height` above, so switching
 * surface does not resize the page under the reader's cursor) and each view has
 * to REACH that floor. As a block it stopped at its own content and left a pale
 * shelf under the admin sidebar that read as a half-loaded screenshot.
 */
#pv-view-site:checked ~ .studio__grid .pv__view[data-view='site'],
#pv-view-admin:checked ~ .studio__grid .pv__view[data-view='admin'],
#pv-view-vendor:checked ~ .studio__grid .pv__view[data-view='vendor'],
#pv-view-partner:checked ~ .studio__grid .pv__view[data-view='partner'] {
  display: grid;
}

/* ------------------------------------------------- the browser around it -- */
/*
 * The chrome is what turns three panels into three PRODUCTS: the reader sees
 * their own domain in an address bar, on three hosts, which is the thing a
 * screenshot of our demo can never say. It is deliberately NEUTRAL — the one
 * strip here that does not take the reader's colour, because a browser is not
 * part of anybody's brand and painting it would read as a toy.
 */
.pv-chrome {
  display: flex;
  gap: 0.6rem;
  align-items: center;
  padding: 0.45rem 0.65rem;
  border-bottom: 1px solid var(--pv-line);
  background: var(--pv-surface);
}

.pv-dots {
  display: flex;
  flex: none;
  gap: 0.25rem;
}

.pv-dots i {
  width: 0.42rem;
  height: 0.42rem;
  border-radius: 999px;
  background: var(--pv-line);
}

.pv-url {
  display: flex;
  gap: 0.3rem;
  align-items: center;
  overflow: hidden;
  min-width: 0;
  padding: 0.15rem 0.6rem;
  border: 1px solid var(--pv-line);
  border-radius: 999px;
  background: var(--pv-bg);
  font-size: 0.68rem;
  white-space: nowrap;
}

.pv-lock {
  flex: none;
  width: 0.62rem;
  height: 0.62rem;
  fill: none;
  stroke: var(--pv-muted);
  stroke-width: 2;
}

.pv-url__host {
  overflow: hidden;
  text-overflow: ellipsis;
}

.pv-url__path {
  color: var(--pv-muted);
}

/* ------------------------------------------------------- shared atoms --- */

.pv-mark {
  display: grid;
  flex: none;
  place-items: center;
  width: 1.6rem;
  height: 1.6rem;
  overflow: hidden;
  border-radius: 0.4rem;
  background: var(--pv-accent);
  color: var(--pv-accent-ink);
  font-size: 0.62rem;
  font-weight: 700;
}

/* An uploaded mark brings its own ground with it — a logo on a coloured tile
   is a logo nobody approved. */
.pv-mark.is-logo {
  background: transparent;
}

.pv-mark img {
  width: 100%;
  height: 100%;
  object-fit: contain;
}

.pv-mark--sm {
  width: 1.35rem;
  height: 1.35rem;
  font-size: 0.55rem;
}

.pv-name {
  overflow: hidden;
  max-width: 9rem;
  font-weight: 700;
  white-space: nowrap;
  text-overflow: ellipsis;
}

.pv-name--wordmark {
  font-size: 0.85rem;
}

.pv-name--sm {
  max-width: 7rem;
  font-size: 0.72rem;
}

.pv-btn {
  flex: none;
  padding: 0.28rem 0.6rem;
  border: 1px solid transparent;
  border-radius: 0.3rem;
  background: var(--pv-accent);
  color: var(--pv-accent-ink);
  font-size: 0.66rem;
  font-weight: 600;
  white-space: nowrap;
}

/* The outline button beside it — `apps/web` pairs exactly this way, and it is
   also the honest place to show that not everything goes solid in your colour. */
.pv-btn--quiet {
  border-color: var(--pv-line);
  background: transparent;
  color: var(--pv-text);
}

.pv-btn--wide {
  display: block;
  width: 100%;
  padding-block: 0.35rem;
  text-align: center;
}

.pv-lang {
  flex: none;
  font-size: 0.62rem;
  font-weight: 600;
  color: var(--pv-muted);
}

.pv-meta {
  display: block;
  overflow: hidden;
  font-size: 0.64rem;
  font-variant-numeric: tabular-nums;
  color: var(--pv-muted);
  white-space: nowrap;
  text-overflow: ellipsis;
}

.pv-price {
  flex: none;
  font-size: 0.72rem;
  font-variant-numeric: tabular-nums;
  white-space: nowrap;
}

/* The format badge is a dot plus a word in both apps — and a DOT rather than a
   filled chip on purpose: the accent as 10px text is the one place a colour the
   reader chose could fail contrast against the card behind it. */
.pv-badge {
  display: inline-flex;
  gap: 0.3rem;
  align-items: center;
  padding: 0.1rem 0.4rem;
  border: 1px solid var(--pv-line);
  border-radius: 0.25rem;
  font-size: 0.6rem;
  font-weight: 600;
  color: var(--pv-muted);
}

.pv-dot {
  flex: none;
  width: 0.35rem;
  height: 0.35rem;
  border-radius: 999px;
  background: var(--pv-accent);
}

/*
 * The hamburger both apps show below their breakpoint. Hidden on a wide mock,
 * because both then lay their navigation out in full.
 */
.pv-burger {
  display: none;
  flex: none;
  flex-direction: column;
  gap: 0.15rem;
  justify-content: center;
  width: 0.9rem;
}

.pv-burger i {
  height: 1.5px;
  border-radius: 999px;
  background: var(--pv-muted);
}

/* --------------------------------------------------- the public site --- */
/* apps/web: header, hero, the stats strip, one PlayDayCard. */

.pv-web,
.pv-admin {
  display: grid;
  align-content: start;
}

.pv-web__nav {
  display: flex;
  gap: 0.45rem;
  align-items: center;
  padding: 0.5rem 0.7rem;
  border-bottom: 1px solid var(--pv-line);
}

.pv-web__links {
  display: flex;
  flex: 1;
  gap: 0.7rem;
  justify-content: center;
  overflow: hidden;
  min-width: 0;
}

.pv-web__links i {
  font-size: 0.66rem;
  font-style: normal;
  color: var(--pv-muted);
  white-space: nowrap;
}

/* The active link is underlined in the app (NavActiveUnderline), not filled. */
.pv-web__links i.is-on {
  padding-bottom: 0.1rem;
  border-bottom: 2px solid var(--pv-accent);
  color: var(--pv-text);
  font-weight: 600;
}

/*
 * The hero's own heading is the club's NAME in `apps/web` — which is why the
 * reader's typing lands at 1.4rem in the middle of the mock, and why the
 * gradient behind it is built from their colour.
 */
.pv-hero {
  display: grid;
  gap: 0.4rem;
  justify-items: center;
  padding: 1.1rem 1rem;
  background-image: linear-gradient(180deg, color-mix(in srgb, var(--pv-accent) 16%, transparent), transparent);
  text-align: center;
}

.pv-hero__title {
  overflow: hidden;
  max-width: 100%;
  font-family: var(--display);
  font-size: 1.4rem;
  line-height: 1.1;
  white-space: nowrap;
  text-overflow: ellipsis;
}

.pv-hero__lede {
  max-width: 34ch;
  font-size: 0.66rem;
  color: var(--pv-muted);
}

.pv-hero__row {
  display: flex;
  gap: 0.4rem;
  margin-top: 0.2rem;
}

.pv-strip {
  display: flex;
  gap: 1.2rem;
  justify-content: center;
  padding: 0.4rem 0.7rem;
  border-block: 1px solid var(--pv-line);
  background: var(--pv-surface);
  font-size: 0.64rem;
  color: var(--pv-muted);
}

.pv-strip span {
  display: inline-flex;
  gap: 0.35rem;
  align-items: center;
  white-space: nowrap;
}

.pv-strip b {
  color: var(--pv-text);
}

.pv-day {
  margin: 0.7rem;
  overflow: hidden;
  border: 1px solid var(--pv-line);
  border-radius: 0.45rem;
}

/* The tinted date header of a PlayDayCard, calendar tile and all. */
.pv-day__head {
  display: flex;
  gap: 0.5rem;
  align-items: center;
  padding: 0.45rem 0.6rem;
  border-bottom: 1px solid var(--pv-line);
  background: var(--pv-surface);
  background: color-mix(in srgb, var(--pv-accent) 12%, transparent);
}

.pv-day__tile {
  width: 1.35rem;
  height: 1.35rem;
  border-radius: 0.3rem;
  background: var(--pv-line);
  background: color-mix(in srgb, var(--pv-accent) 30%, transparent);
}

.pv-day__when b {
  display: block;
  font-size: 0.74rem;
}

.pv-day__when i {
  font-size: 0.62rem;
  font-style: normal;
  color: var(--pv-muted);
}

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

/* Each row carries the accent as its left rule — the app's own way of marking
   an event you are registered for. */
.pv-ev {
  display: flex;
  gap: 0.6rem;
  align-items: flex-start;
  justify-content: space-between;
  padding: 0.45rem 0.6rem;
  border-bottom: 1px solid var(--pv-line);
  border-left: 3px solid var(--pv-accent);
}

.pv-ev:last-child {
  border-bottom: 0;
}

.pv-ev__main {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  gap: 0.15rem;
  justify-items: start;
  min-width: 0;
}

.pv-ev__main b {
  overflow: hidden;
  max-width: 100%;
  font-size: 0.72rem;
  white-space: nowrap;
  text-overflow: ellipsis;
}

.pv-day__foot {
  padding: 0.4rem 0.6rem;
  border-top: 1px solid var(--pv-line);
  background: var(--pv-surface);
  font-size: 0.64rem;
  font-weight: 600;
}

/* ---------------------------------------------------- the back office --- */
/*
 * apps/admin has a TOP nav, not a sidebar — `useNavTabs` lists these tabs and
 * `AppHeader` lays them out beside the wordmark. The first sketch of this page
 * gave it a sidebar, which is the kind of detail a prospect who has seen a demo
 * would notice and nobody else would.
 */

.pv-admin__nav {
  display: flex;
  gap: 0.5rem;
  align-items: center;
  padding: 0.5rem 0.7rem;
  border-bottom: 1px solid var(--pv-line);
  background: var(--pv-surface);
}

.pv-tabs {
  display: flex;
  flex: 1;
  gap: 0.55rem;
  overflow: hidden;
  min-width: 0;
  margin-left: 0.5rem;
}

.pv-tabs i {
  font-size: 0.66rem;
  font-style: normal;
  color: var(--pv-muted);
  white-space: nowrap;
}

.pv-tabs i.is-on {
  padding-bottom: 0.1rem;
  border-bottom: 2px solid var(--pv-accent);
  color: var(--pv-text);
  font-weight: 600;
}

.pv-avatar {
  flex: none;
  width: 1.25rem;
  height: 1.25rem;
  border-radius: 999px;
  background: var(--pv-line);
}

.pv-admin__body {
  display: grid;
  gap: 0.55rem;
  align-content: start;
  padding: 0.7rem;
}

.pv-admin__head {
  display: flex;
  gap: 0.6rem;
  align-items: center;
  justify-content: space-between;
}

.pv-admin__head b {
  display: block;
  font-size: 0.9rem;
}

.pv-admin__head i {
  font-size: 0.64rem;
  font-style: normal;
  color: var(--pv-muted);
}

/* The pill tabs of EventManagementTab — upcoming / past. */
.pv-pills {
  display: inline-flex;
  gap: 0.2rem;
  align-self: start;
  padding: 0.15rem;
  border-radius: 999px;
  background: var(--pv-surface);
}

.pv-pills i {
  padding: 0.2rem 0.6rem;
  border-radius: 999px;
  font-size: 0.64rem;
  font-style: normal;
  color: var(--pv-muted);
}

.pv-pills i.is-on {
  background: var(--pv-accent);
  color: var(--pv-accent-ink);
  font-weight: 600;
}

/* One event card, expandable — the chevron is the affordance the real row has
   for opening the attendee list underneath it. */
.pv-card {
  display: flex;
  gap: 0.6rem;
  align-items: center;
  justify-content: space-between;
  padding: 0.5rem 0.6rem;
  border: 1px solid var(--pv-line);
  border-radius: 0.4rem;
  background: var(--pv-surface);
}

.pv-card--flat {
  background: transparent;
}

/* The selected redemption in the vendor portal is ringed, not filled. */
.pv-card.is-on {
  border-color: var(--pv-accent);
  box-shadow: 0 0 0 1px var(--pv-accent);
}

.pv-card__main {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  gap: 0.2rem;
  justify-items: start;
  min-width: 0;
}

.pv-card__main b {
  overflow: hidden;
  max-width: 100%;
  font-size: 0.74rem;
  white-space: nowrap;
  text-overflow: ellipsis;
}

.pv-chevron {
  flex: none;
  width: 0.5rem;
  height: 0.5rem;
  border-right: 2px solid var(--pv-muted);
  border-bottom: 2px solid var(--pv-muted);
  transform: rotate(45deg);
}

/* ------------------------------------------------ the portal chrome --- */
/*
 * TWO portals wear this, and the class is named for the shape rather than for
 * either of them. `apps/vendor` is one narrow column at any width — it is used
 * standing at a counter, on a phone — and `apps/partner` is the same, because
 * since wave 0d they are literally the same component: both instantiate
 * `PortalShell` from `@playset/ui`, header, nav row and single column. Rendering
 * either full-bleed would make it look like a second admin panel, which is the
 * opposite of what a shop owner or an outside organiser is being told.
 *
 * It was `.pv-vendor*` until the partner tab arrived and made the name a lie.
 */

.pv-portal {
  display: grid;
  align-content: start;
  background: var(--pv-surface);
}

.pv-portal__head,
.pv-portal__nav,
.pv-portal__body {
  width: 100%;
  max-width: 22rem;
  margin-inline: auto;
}

.pv-portal__head {
  display: flex;
  gap: 0.5rem;
  align-items: center;
  justify-content: space-between;
  padding: 0.5rem 0.7rem 0.3rem;
}

.pv-portal__title {
  display: inline-flex;
  gap: 0.3rem;
  align-items: baseline;
  overflow: hidden;
  min-width: 0;
  font-size: 0.72rem;
  font-weight: 600;
  white-space: nowrap;
}

.pv-portal__nav {
  display: flex;
  gap: 0.8rem;
  padding: 0 0.7rem 0.4rem;
  border-bottom: 1px solid var(--pv-line);
}

.pv-portal__nav i {
  font-size: 0.66rem;
  font-style: normal;
  color: var(--pv-muted);
}

.pv-portal__nav i.is-on {
  padding-bottom: 0.25rem;
  border-bottom: 2px solid var(--pv-accent);
  color: var(--pv-text);
  font-weight: 600;
}

.pv-portal__body {
  display: grid;
  gap: 0.4rem;
  align-content: start;
  padding: 0.7rem;
}

.pv-stats {
  display: grid;
  grid-template-columns: repeat(3, minmax(0, 1fr));
  gap: 0.35rem;
}

.pv-stat {
  display: grid;
  gap: 0.1rem;
  padding: 0.4rem 0.5rem;
  border: 1px solid var(--pv-line);
  border-radius: 0.35rem;
  background: var(--pv-bg);
}

.pv-stat i {
  overflow: hidden;
  font-size: 0.58rem;
  font-style: normal;
  color: var(--pv-muted);
  white-space: nowrap;
  text-overflow: ellipsis;
}

.pv-stat b {
  font-size: 0.82rem;
  font-variant-numeric: tabular-nums;
}

.pv-portal__h {
  margin: 0.25rem 0 0;
  font-size: 0.64rem;
  font-weight: 600;
  color: var(--pv-muted);
}

.pv-portal__body .pv-card {
  background: var(--pv-bg);
}

/* -------------------------------------------------- the partner body --- */
/*
 * The same `pv-portal` chrome as the vendor view above, and a body that has
 * nothing to do with it: an outside organiser looks at their own evenings and
 * the four things they can do about each, not at a counter's takings. Traced
 * from `packages/modules/partner-events/src/partner/EventsPage.tsx`.
 */

.pv-partner__head {
  display: flex;
  gap: 0.5rem;
  align-items: center;
  justify-content: space-between;
  margin-bottom: 0.1rem;
}

.pv-partner__head b {
  font-size: 0.8rem;
}

.pv-portal__body .pv-partner__row {
  display: grid;
  gap: 0.25rem;
  padding: 0.45rem 0.55rem;
}

.pv-partner__line {
  display: flex;
  flex-wrap: wrap;
  gap: 0.3rem;
  align-items: center;
}

.pv-partner__line b {
  font-size: 0.72rem;
}

/*
 * The two chips every row carries: its status, and whether sign-ups happen
 * here or on the organiser's own site. The second is the whole feature in two
 * words, which is why the mock never draws a row without it.
 */
.pv-chip {
  padding: 0.05rem 0.3rem;
  border: 1px solid var(--pv-line);
  border-radius: 0.5rem;
  font-size: 0.55rem;
  font-style: normal;
  color: var(--pv-muted);
  white-space: nowrap;
}

/* Drawn on the first row only — a finished event loses its write controls. */
.pv-partner__acts {
  display: flex;
  flex-wrap: wrap;
  gap: 0.25rem;
  margin-top: 0.1rem;
}

.pv-partner__acts i {
  padding: 0.15rem 0.4rem;
  border: 1px solid var(--pv-line);
  border-radius: 0.3rem;
  background: var(--pv-surface);
  font-size: 0.58rem;
  font-style: normal;
}

.pv-partner__past {
  padding-top: 0.2rem;
  font-size: 0.62rem;
  color: var(--pv-muted);
  text-align: center;
}

/* The code the player reads out, which is what makes a redemption real. */
.pv-code {
  display: grid;
  gap: 0.35rem;
  padding: 0.5rem 0.6rem;
  border: 1px solid var(--pv-line);
  border-radius: 0.4rem;
  background: var(--pv-bg);
}

.pv-code__label {
  font-size: 0.6rem;
  color: var(--pv-muted);
}

.pv-code__boxes {
  display: flex;
  gap: 0.3rem;
}

.pv-code__boxes i {
  width: 1.5rem;
  height: 1.6rem;
  border: 1px solid var(--pv-line);
  border-radius: 0.25rem;
  background: var(--pv-surface);
}

/*
 * A 375px phone is where a two-column application shows. Everything steps down
 * rather than anything being dropped: a reader looking at "the committee's back
 * office" should see every tab it has.
 */
/*
 * Below 600px the mock shows each app's OWN small-screen layout, which is also
 * the only honest way to fit them: `apps/web` hides its nav and its two auth
 * buttons behind a sheet under `md`, `apps/admin` hides its tabs under `lg`,
 * and both put a hamburger where they were. The first cut kept the wide layout
 * and let `.pv` clip it, which reads as a broken screenshot rather than as a
 * phone.
 */
@media (max-width: 599px) {
  /*
   * Two rows of two. Four tabs across a phone is four one-word columns and a
   * label nobody can read; the strip is navigation, so it may take a second
   * row rather than shrink the words.
   */
  .tabs {
    grid-auto-flow: row;
    grid-template-columns: repeat(2, minmax(0, 1fr));
  }

  .pv {
    font-size: 0.72rem;
  }

  .pv-burger {
    display: flex;
  }

  .pv-web__links,
  .pv-tabs,
  .pv-lang,
  .pv-web__nav .pv-btn {
    display: none;
  }

  .pv-web__nav,
  .pv-admin__nav {
    justify-content: flex-start;
  }

  .pv-admin__nav .pv-avatar {
    margin-left: auto;
  }

  /* StatsBar is `flex-col sm:flex-row` in the app — it stacks, it does not
     shrink. */
  .pv-strip {
    flex-direction: column;
    gap: 0.15rem;
    align-items: center;
  }

  .pv-hero__title {
    font-size: 1.15rem;
  }

  .pv-name {
    max-width: 8rem;
  }

  .pv-stat b {
    font-size: 0.72rem;
  }
}

/* ------------------------------------------------------------- send it --- */

.send {
  display: grid;
  gap: 1.5rem;
  margin-top: clamp(2.5rem, 5vw, 3.5rem);
  padding-top: clamp(2rem, 4vw, 2.75rem);
  border-top: 1px solid var(--line);
}

.send .btn-row {
  margin-top: 0;
}

.send__logo {
  margin-top: 1rem;
  padding-left: 0.7rem;
  border-left: 2px solid var(--accent-line);
  font-size: 0.85rem;
}

.send__logo[hidden] {
  display: none;
}

@media (min-width: 720px) {
  .send {
    grid-template-columns: 1.2fr 0.8fr;
    align-items: start;
  }
}

@media (min-width: 1000px) {
  .studio__grid {
    grid-template-columns: 21rem minmax(0, 1fr);
  }

  /* The mock stays put while the form scrolls past it: every control on the
     left is a control whose whole point is what it does on the right. */
  .studio__stage {
    position: sticky;
    top: 1.5rem;
  }
}

/* ---------------------------------------------------------------- motion -- */
/*
 * One orchestrated moment: the hero arrives in sequence on load. Nothing else
 * on the page animates on scroll — a page that reveals every section as you
 * pass it reads as a template, not as a document.
 */

@keyframes rise {
  from {
    opacity: 0;
    transform: translateY(12px);
  }
  to {
    opacity: 1;
    transform: none;
  }
}

.rise {
  animation: rise 0.55s cubic-bezier(0.22, 1, 0.36, 1) both;
}

.rise--1 { animation-delay: 0.04s; }
.rise--2 { animation-delay: 0.12s; }
.rise--3 { animation-delay: 0.2s; }
.rise--4 { animation-delay: 0.28s; }
.rise--5 { animation-delay: 0.38s; }

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

  *,
  *::before,
  *::after {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
  }

  .btn:hover,
  .cell:hover {
    transform: none;
  }
}