/* Vault1 typography: self-hosted fonts + the eyebrow/ID/date treatment.
 * Hand-authored (not generated - see static/tokens.css for the one file
 * that is). v1/design-system commit 3.
 *
 * DESIGN_SPEC.md S2: Barlow for everything except identifiers and dates,
 * which use IBM Plex Mono. Self-hosted rather than a Google Fonts <link> -
 * see static/fonts/NOTICE.md for why (CLAUDE.md S7, deliberately boring
 * infrastructure: no third-party dependency in the render path).
 *
 * Scope of this commit: the base typeface swap (every page now renders in
 * Barlow instead of Inter, everywhere, for free - font-family inherits)
 * plus the one eyebrow/mono utility class, applied to the one instance
 * DESIGN_SPEC.md S2 names explicitly ("Revision 1 · Published Sep 9,
 * 2026"). The rest of the type scale (page-title, section-heading,
 * card-title, body, secondary, button-label as actual utility classes with
 * real numeric sizes) is NOT built here - defining them with nothing
 * using them would mean reviewing CSS with no heading to see it against,
 * same reasoning as components.css's deferred row/badge/field/etc. Each
 * gets added when the template pass reaches the page whose heading needs
 * it. Other current "Revision N · <date>" instances
 * (evaluation_review_detail.html, player_evaluations.html,
 * coach_player_actions.html, coach_team_actions.html, my_surveys.html,
 * player_actions.html) are known and deliberately left alone - each
 * converts alongside its own template in the pass that follows this
 * commit, not ahead of it.
 */

@font-face {
  font-family: "Barlow";
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url("/static/fonts/barlow-400.woff2") format("woff2");
}

@font-face {
  font-family: "Barlow";
  font-style: normal;
  font-weight: 500;
  font-display: swap;
  src: url("/static/fonts/barlow-500.woff2") format("woff2");
}

@font-face {
  font-family: "Barlow";
  font-style: normal;
  font-weight: 600;
  font-display: swap;
  src: url("/static/fonts/barlow-600.woff2") format("woff2");
}

@font-face {
  font-family: "Barlow";
  font-style: normal;
  font-weight: 700;
  font-display: swap;
  src: url("/static/fonts/barlow-700.woff2") format("woff2");
}

@font-face {
  font-family: "IBM Plex Mono";
  font-style: normal;
  font-weight: 500;
  font-display: swap;
  src: url("/static/fonts/ibm-plex-mono-500.woff2") format("woff2");
}

/* 2.289 (3), Colin: the body line-height belongs here, not on each page.
 * Every board sets body text at 1.55 in its own helmet <style> and the app
 * set none, so a page that wanted to match its board carried its own copy -
 * twelve page stylesheets had one, each with the same comment explaining
 * why. §9's threshold for consolidating a repeated declaration is three.
 *
 * On :root beside the family, because that is how body's one other
 * consumed property already reaches every page for free (components.css's
 * own type block: "bound to the element, not shipped as a utility class
 * nobody would remember to add to the next new page"). Headings are
 * unaffected - h1/h2/h3 each set their own line-height, which wins.
 *
 * **Both widths, from the desktop token, and now the pair agrees.** No board
 * has a mobile media query for this: all 94 that declare a body line-height
 * declare 1.55, so 1.55 is what matches a board at 390 as well as at 1320.
 * This comment used to go on to say the token pair said mobile 1.5, which no
 * board agreed with, left alone and raised in docs/FINDINGS.md rather than
 * edited here because design/tokens.json also feeds the phone. **2.290
 * (Colin, 2026-11-02) answered that**: the mobile value is 1.55 too, so
 * either half of the pair would do here. Reading the desktop token is left
 * as it is - it is not wrong, and a token rename is not what 2.290 asked
 * for.
 *
 * **And deliberately no 768px override**, which is the one way this role
 * differs from its siblings in components.css: they pair a mobile base with
 * a desktop size because their sizes genuinely differ, and this has nothing
 * to override while the pair agrees. If the two ever diverge again, that is
 * when the media query arrives.
 */
:root {
  font-family: var(--vault-type-body-family);
  line-height: var(--vault-type-body-line-height-desktop);
}

/* DESIGN_SPEC.md S2's "Eyebrow, ID, date" row: mono, uppercase,
 * letterspaced - and S1's colour table pairs this treatment with
 * ink-faint ("Eyebrow labels, captions, disabled help text"), not the
 * ink-soft .muted uses for general secondary text. A complete, self-
 * contained treatment - callers apply this class alone, not alongside
 * .muted. */
.eyebrow {
  font-family: var(--vault-type-eyebrow-family);
  font-weight: var(--vault-type-eyebrow-weight);
  font-size: var(--vault-type-eyebrow-size-mobile);
  letter-spacing: var(--vault-type-eyebrow-letter-spacing-mobile);
  text-transform: var(--vault-type-eyebrow-transform);
  color: var(--vault-color-ink-faint);
}

@media (min-width: 768px) {
  .eyebrow {
    font-size: var(--vault-type-eyebrow-size-desktop);
    letter-spacing: var(--vault-type-eyebrow-letter-spacing-desktop);
  }
}

/* Colin, 2026-10-04: round one's items 1, 2, 6, 9, 10, 15 and 38 were
 * never about the individual pages - there is no shared layout
 * vocabulary, so each page invented its own. Item 10 named the sharpest
 * case directly: Action Library's category headings (e.g. "Fitness")
 * rendered at the same visual weight as the items under them, because
 * neither had a real heading class - just whatever inline font-size a
 * template happened to type that day. This file's own top comment
 * predicted exactly this gap in v1/design-system's third commit ("the
 * rest of the type scale... is NOT built here - defining them with
 * nothing using them would mean reviewing CSS with no heading to see it
 * against... each gets added when the template pass reaches the page
 * whose heading needs it"). That pass never came back to finish it, so
 * every page's h1/h2/h3 is still a bare, unstyled browser default with
 * an inline font-size bolted on top, one per caller, one vocabulary.
 *
 * The five classes below give the tokens DESIGN_SPEC.md §2 already
 * names (page-title, section-heading, card-title, secondary, button-
 * label - unchanged from that table, already generated into
 * tokens.css) something to attach to. New-files groundwork only, per
 * Colin's own instruction: no existing template is converted to use
 * them in this pass - that conversion is the UI overhaul that follows
 * V1, and §9's own "do not restyle and restructure in the same pass"
 * rule applies to it, not to adding the classes themselves. */
.page-title {
  font-family: var(--vault-type-page-title-family);
  font-weight: var(--vault-type-page-title-weight);
  font-size: var(--vault-type-page-title-size-mobile);
  line-height: var(--vault-type-page-title-line-height);
}

.section-heading {
  font-family: var(--vault-type-section-heading-family);
  font-weight: var(--vault-type-section-heading-weight);
  font-size: var(--vault-type-section-heading-size-mobile);
  line-height: var(--vault-type-section-heading-line-height);
}

.card-title {
  font-family: var(--vault-type-card-title-family);
  font-weight: var(--vault-type-card-title-weight);
  font-size: var(--vault-type-card-title-size-mobile);
  line-height: var(--vault-type-card-title-line-height);
}

.secondary {
  font-family: var(--vault-type-secondary-family);
  font-weight: var(--vault-type-secondary-weight);
  font-size: var(--vault-type-secondary-size-mobile);
  line-height: var(--vault-type-secondary-line-height);
}

.button-label {
  font-family: var(--vault-type-button-label-family);
  font-weight: var(--vault-type-button-label-weight);
  font-size: var(--vault-type-button-label-size-mobile);
  line-height: var(--vault-type-button-label-line-height);
}

@media (min-width: 768px) {
  .page-title { font-size: var(--vault-type-page-title-size-desktop); }
  .section-heading { font-size: var(--vault-type-section-heading-size-desktop); }
  .card-title { font-size: var(--vault-type-card-title-size-desktop); }
  .secondary { font-size: var(--vault-type-secondary-size-desktop); }
  .button-label { font-size: var(--vault-type-button-label-size-desktop); }
}
