/* MelloTone Studios. Direction A, "the player's own artwork, at its real size" (the owner's pick,
   2026-10-26 18:24): the web app's own colours, type, glass header and marketing frame, so the company
   pages and /app read as one product. One focal point per screen, one big real picture, filled panels
   with no outlines, one accent colour spent on the main button, solid text colours, a closing band. */

@font-face {
  font-family: 'Outfit';
  src: url('/assets/font/outfit-regular.woff2') format('woff2');
  font-weight: 400;
  font-display: swap;
}
@font-face {
  font-family: 'Outfit';
  src: url('/assets/font/outfit-medium.woff2') format('woff2');
  font-weight: 500;
  font-display: swap;
}
@font-face {
  font-family: 'Outfit';
  src: url('/assets/font/outfit-semibold.woff2') format('woff2');
  font-weight: 600;
  font-display: swap;
}
:root {
  /* The web app's colours (tokens.css). Text is solid, never white made grey by transparency. */
  --bg: #01090C;
  --surface: #0A171D;
  --surface-2: #13222A;
  --text: #E8F9FF;
  --muted: #A9BCC4;
  --line: rgba(232, 249, 255, 0.12);
  --line-strong: rgba(232, 249, 255, 0.22);
  /* The outline pill's border. */
  --outline: #728891;
  /* Spent on the main button ("Play in your browser") and keyboard focus only. */
  --accent: #13BCF5;
  --glass: rgba(5, 16, 21, 0.8);
  --glass-solid: #0B181E;
  /* The bars' glass (SYN 7.5, the app's after lane T2): blur and colour, with a half-pixel ring in place of
     the 1px hairline. */
  --glass-blur: blur(24px) saturate(2.2);
  --glass-ring: inset 0 0 0 0.5px rgba(232, 249, 255, 0.2);
  /* The art edge (SYN 7.3): a faint ring on every picture, following its radius; one pixel on a 1x screen and
     half a pixel on a 2x or sharper one (below), one device pixel either way. */
  --art-edge: inset 0 0 0 1px rgba(232, 249, 255, 0.08);
  --glass-card: rgba(5, 16, 21, 0.62);
  --glass-card-border: rgba(232, 249, 255, 0.1);
  --shadow-cover: 0 24px 64px rgba(0, 0, 0, 0.55);

  /* The marketing frame: a 1120px column, 40px gutters (16px on phones), 80px between sections. */
  --content: 1120px;
  --gutter: 40px;
  --section: 80px;
  /* The fixed header's height plus its 16px from the top, and room under it. */
  --page-top: 144px;
  --radius: 16px;
  --radius-sm: 8px;
  /* Picture tiles and art up to 200 px wide (SYN 7.4); larger art and cards take --radius. */
  --radius-tile: 12px;
  /* The one curve everything that lands rides (SYN 4.2), and the entrance's clock (D13). */
  --ease-surface: cubic-bezier(0.32, 0.72, 0, 1);
  --ease-productive: cubic-bezier(0.3, 0, 0, 1);
  --duration-entrance: 400ms;
  --stagger-block: 60ms;
  /* The 17-stop eased fade (SYN 7.6), from clear to the ground, as one gradient's stops. */
  --fade-to-bg: rgba(1, 9, 12, 0) 0%, rgba(1, 9, 12, 0.008) 6.25%, rgba(1, 9, 12, 0.03) 12.5%, rgba(1, 9, 12, 0.07) 18.75%,
    rgba(1, 9, 12, 0.13) 25%, rgba(1, 9, 12, 0.204) 31.25%, rgba(1, 9, 12, 0.294) 37.5%, rgba(1, 9, 12, 0.392) 43.75%,
    rgba(1, 9, 12, 0.5) 50%, rgba(1, 9, 12, 0.608) 56.25%, rgba(1, 9, 12, 0.706) 62.5%, rgba(1, 9, 12, 0.796) 68.75%,
    rgba(1, 9, 12, 0.87) 75%, rgba(1, 9, 12, 0.93) 81.25%, rgba(1, 9, 12, 0.97) 87.5%, rgba(1, 9, 12, 0.992) 93.75%, #01090C 100%;
  --font: 'Outfit', -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif;
}
@media (max-width: 767px) {
  :root { --gutter: 16px; --section: 56px; --page-top: 100px; }
}
@media (-webkit-min-device-pixel-ratio: 2), (min-resolution: 2dppx) {
  :root { --art-edge: inset 0 0 0 0.5px rgba(232, 249, 255, 0.08); }
}

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

/* Keyboard focus and in-page links never land under the fixed header (WCAG 2.2 2.4.11, technique C43):
   the header is 64px tall, 16px from the top, so 96px clears it with room. On phones (767px and
   narrower) and in a short window the header scrolls away with the page and needs none. Where a
   reader's larger text shows the Menu on a wider window it scrolls away too and the 96px stays, so
   the opened menu turns off scroll anchoring (below). */
html { -webkit-text-size-adjust: 100%; scroll-padding-top: 96px; background: var(--bg); }

body {
  margin: 0;
  background: var(--bg);
  color: var(--text);
  font-family: var(--font);
  font-size: 18px;
  line-height: 30px;
  -webkit-font-smoothing: antialiased;
  overflow-wrap: break-word;
}
/* No 700 face is fetched (SYN 7.1: a screen downloads 400, 500 and 600): strong words are semibold. */
strong, b { font-weight: 600; }
p, li, figcaption, dd { text-wrap: pretty; }
::selection { background: rgba(19, 188, 245, 0.35); color: #FFFFFF; }

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

a { color: var(--text); text-decoration: underline; text-decoration-thickness: 1px; text-underline-offset: 3px; }
a:hover { color: var(--text); text-decoration-thickness: 2px; }

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

.skip-link {
  position: absolute;
  left: -9999px;
  top: 0;
  background: var(--accent);
  color: #021014;
  padding: 12px 20px;
  font-weight: 600;
  z-index: 100;
}
.skip-link:focus { left: 0; }

.container {
  width: 100%;
  max-width: calc(var(--content) + 2 * var(--gutter));
  margin: 0 auto;
  padding-left: var(--gutter);
  padding-right: var(--gutter);
}
.container-narrow { max-width: calc(760px + 2 * var(--gutter)); }
/* A legal page's header pill spans exactly the text and its Contents rail from 1100px, its left edge on the
   text's and its right edge on the rail's (L508): it holds only the name, so it is no wider than the page. */
@media (min-width: 1100px) and (min-height: 481px) {
  .site-header-legal .header-pill { left: max(var(--gutter), calc((100% - var(--content)) / 2)); right: auto; width: calc(100% - 2 * var(--gutter)); max-width: 984px; margin: 0; }
}
/* From 768 to 1099px, where Contents opens above the text, the pill spans the 680px text column alone, its
   left edge on the text's, whether it is fixed (a window wider than the header's 52em) or in the header (the
   header's 16px padding plus 24 is the page's 40px gutter). */
@media (min-width: 768px) and (max-width: 1099px) {
  .site-header-legal .header-pill { max-width: 680px; margin: 0 0 0 calc(var(--gutter) - 16px); }
}

/* ---------- header: the web app's floating glass pill ---------- */

/* The header is the container its switch below measures. It lies over the top of the page, as wide as
   the window, and scrolls away with it; its padding puts the pill 16px from the top and the sides
   (1120px wide at most, centred), and its content box, the pill's width, is what the switch measures.
   Where the nav shows, the pill is fixed to the window in the same place (below). The header's box is
   the window's width so that the pill lands in that place whichever box it is fixed to: Chrome before
   129 and Safari before 18.4 also gave a container layout containment, which makes the header, not the
   window, the box a fixed pill is placed in (with the header at 16px from each side the pill was drawn
   16px lower and 16px further in, npm run layout's contained-header rule). There the pill scrolls away
   with the page, as on a phone. Its font size is the switch's unit and draws nothing: each part of the
   header sets its own. The box itself takes no taps; its pill does. */
.site-header {
  position: absolute;
  top: 0;
  left: 0;
  right: 0;
  z-index: 50;
  padding: 16px max(16px, calc((100% - var(--content)) / 2)) 0;
  font-size: 16px;
  container: site-header / inline-size;
  pointer-events: none;
}
/* The top fade (L502, docs/design/SITE-FURNITURE.md 3): wherever the pill is fixed, a strip of the ground
   across the top of the window, under the pill, solid for 18px and clear by 36px, so words scrolling up
   are never left sliced in the 16px above the pill (the web app's .mk-topfade). These pages have no
   script to watch the scroll, so it is always there where the pill is fixed: at the top of a page it is
   the ground over the ground. It takes no taps. */
.top-fade { display: none; }
@media (min-width: 768px) and (min-height: 481px) {
  .top-fade {
    display: block;
    position: fixed;
    top: 0;
    left: 0;
    right: 0;
    height: 36px;
    background: linear-gradient(var(--bg) 18px, rgba(1, 9, 12, 0));
    pointer-events: none;
  }
}
/* One row: the icon and the name, then the nav (its links and the one Listen action), or, where the
   links do not fit, the Listen action and the Menu button (below). A radius of half the closed height
   draws the same pill closed and a rounded panel open. */
.header-pill {
  position: relative;
  display: grid;
  grid-template-columns: minmax(0, 1fr) auto;
  align-items: center;
  column-gap: 8px;
  min-height: 64px;
  --pill-top: 7px;
  --pill-end: 8px;
  padding: var(--pill-top) var(--pill-end);
  border: 0;
  border-radius: 32px;
  background: var(--glass);
  -webkit-backdrop-filter: var(--glass-blur);
  backdrop-filter: var(--glass-blur);
  box-shadow: var(--glass-ring), 0 8px 24px rgba(0, 0, 0, 0.35);
  pointer-events: auto;
}
/* Where the nav shows, in a window wider than 767px and taller than 480px, the pill stays at the top
   of the window, where the header puts it. Where the Menu button shows instead (a phone, or a reader's
   larger text: below), the pill stays in the header and scrolls away with the page, as on a phone, so
   the opened menu, which takes its room at the top of the page, is always where it was opened. */
@media (min-width: 768px) and (min-height: 481px) {
  .header-pill { position: fixed; top: 16px; left: 16px; right: 16px; max-width: var(--content); margin: 0 auto; }
}
@supports not ((backdrop-filter: blur(1px)) or (-webkit-backdrop-filter: blur(1px))) {
  .header-pill { background: var(--glass-solid); }
}
@media (prefers-reduced-transparency: reduce) {
  .header-pill { background: var(--glass-solid); -webkit-backdrop-filter: none; backdrop-filter: none; }
}

.wordmark {
  grid-area: 1 / 1;
  justify-self: start;
  display: inline-flex;
  align-items: center;
  gap: 12px;
  min-height: 48px;
  padding: 0 8px;
  border-radius: 999px;
  color: var(--text);
  font-size: 18px;
  line-height: 24px;
  font-weight: 600;
  text-decoration: none;
  /* It wraps only where its column is short (a reader's text spacing at 768px, a phone), its words
     broken only when one is wider than the column, so it never runs under the nav or the button. */
  min-width: 0;
  overflow-wrap: anywhere;
}
.wordmark:hover { text-decoration: none; }
/* The app's icon at 32px (its gold ear cups are the only gold on the page). */
.wordmark-icon { width: 32px; height: 32px; border-radius: 8px; flex: none; }

.site-nav { grid-area: 1 / 2; display: flex; align-items: center; gap: 4px; }
.nav-link {
  display: inline-flex;
  align-items: center;
  min-height: 44px;
  padding: 0 16px;
  border-radius: 999px;
  color: var(--muted);
  font-size: 16px;
  line-height: 20px;
  font-weight: 500;
  text-decoration: none;
  white-space: nowrap;
  transition: background-color 150ms, color 150ms;
}
.nav-link:hover { color: var(--text); background: rgba(232, 249, 255, 0.07); transition-duration: 50ms; }
.nav-link[aria-current='page'] { color: var(--text); background: rgba(232, 249, 255, 0.07); }
/* The header's one filled action, Listen (SITE-FURNITURE.md 5), at every width: on a phone it stays in
   the row beside the Menu button while the links go into the menu. No icon here, as the web app's header
   draws its action. */
.nav-cta {
  display: inline-flex;
  align-items: center;
  min-height: 48px;
  margin-left: 8px;
  padding: 0 22px;
  border-radius: 999px;
  background: var(--accent);
  color: #021014;
  font-size: 16px;
  line-height: 20px;
  font-weight: 500;
  text-decoration: none;
  white-space: nowrap;
  transition: transform 150ms var(--ease-productive);
}
.nav-cta:hover { color: #021014; text-decoration: none; }

/* Where the nav does not fit: the icon, the name and a Menu button (details and summary, no script).
   The button's column is held by its hidden twin (.menu-twin: the same element with the same word, so
   a browser that translates the page translates both), never by the word's width written into the
   stylesheet: opened, the menu's links take a row of their own under the name and the twin, across the
   pill, and the button stays where it was, drawn over its twin. So opening the menu never moves the
   name or the button, with or without :has(), and the links start under the name however many lines
   it takes. */
.menu-button {
  display: inline-flex;
  align-items: center;
  gap: 10px;
  min-height: 44px;
  padding: 0 16px;
  border: 1px solid var(--line-strong);
  border-radius: 999px;
  color: var(--text);
  font-size: 16px;
  line-height: 20px;
  font-weight: 500;
  vertical-align: top;
  list-style: none;
  cursor: pointer;
}
.menu-button::-webkit-details-marker { display: none; }
/* After .menu-button, which the twin is too: without the Menu, the twin has no box at all. */
.menu, .menu-twin { display: none; grid-area: 1 / 2; }
.menu-twin { visibility: hidden; }
/* Closed, the Menu is as tall as its button: the line the button sits on would otherwise take the
   body's line height, which with 200% text is 60px, and the pill grew 14px into the page under it. */
.menu:not([open]) { line-height: 0; }
/* Three bars, drawn as lines. */
.menu-button::before {
  content: '';
  flex: none;
  width: 16px;
  height: 12px;
  background: linear-gradient(var(--text), var(--text)) 0 0 / 100% 2px no-repeat,
    linear-gradient(var(--text), var(--text)) 0 5px / 100% 2px no-repeat,
    linear-gradient(var(--text), var(--text)) 0 10px / 100% 2px no-repeat;
}
/* The opened menu takes room in the page instead of covering it: its links sit inside the pill, under
   the icon, the name and the Menu button, and the header joins the page's flow while the menu is open,
   so the page moves down. A details element with no script stays open when keyboard focus leaves it,
   and a panel drawn over the page would hide the control focus moves to after its last link (WCAG 2.2
   2.4.11; npm run layout tabs past it). */
.menu-panel {
  display: flex;
  flex-direction: column;
  margin: 8px -2px 0 0;
  padding: 8px;
  border-radius: 24px;
  background: var(--glass-solid);
  text-align: left;
}
.menu-link {
  display: flex;
  align-items: center;
  min-height: 52px;
  padding: 0 16px;
  border-radius: 12px;
  color: var(--text);
  font-size: 18px;
  font-weight: 500;
  text-decoration: none;
}
.menu-link:hover, .menu-link[aria-current='page'] { background: rgba(232, 249, 255, 0.07); }
/* Where the sheet is wide (a tablet, or a reader's larger text on a wider window) its links take two columns,
   read across in their order, so six links take three rows instead of a narrow list beside an empty sheet; the
   menu's own Listen, when it shows, takes a row of its own above them. */
@media (min-width: 600px) {
  .menu-panel { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); column-gap: 8px; }
  .menu-listen { grid-column: 1 / -1; }
}
/* Open, the three bars become a cross, the close mark a phone menu draws (the web app's sheet has one). */
.menu[open] > .menu-button::before {
  width: 18px;
  height: 18px;
  background: linear-gradient(var(--text), var(--text)) center / 100% 2px no-repeat;
  transform: rotate(45deg);
}
.menu[open] > .menu-button::after {
  content: '';
  position: absolute;
  top: 50%;
  left: 50%;
  width: 18px;
  height: 2px;
  margin: -1px 0 0 -9px;
  background: var(--text);
  transform: rotate(-45deg);
}
/* The menu's own Listen, shown only where the row is too narrow to hold the action (below). */
.menu-listen { display: none; }
/* While the menu is open the header takes its room in the page, its pill where it was when it floated
   (browsers without :has() keep it floating). And while the menu is open the page has no scroll
   anchoring: a browser with it (Playwright's WebKit 27.2, Safari's engine) holds still what it reads
   below the 96px of scroll padding a computer keeps for the fixed pill (above), which is main's words
   and not the header, so when the opened header pushed main down it scrolled the page as far again
   (284px with 150% text at 1024px) and drew the header and every link above the window. */
.site-header:has(.menu[open]) { position: relative; inset: auto; }
:root:has(.menu[open]) { overflow-anchor: none; }
/* From 768px a closed header lies over the page, which leaves it 80px of room at its top (the pill's 64 and the
   16 above it). Opened, the header takes its room in the page instead, so it gives those 80px back: the page
   moves down by the sheet alone, and its words keep their distance under the pill (they had stood 160px under it
   on Support at 768). A fixed pill (the nav's) is out of the page's flow, so the margin does nothing there. */
@media (min-width: 768px) {
  .header-pill:has(.menu[open]) { margin-bottom: -80px; }
  /* The page's wash then starts under the opened sheet, not at the window's top: it rises out of the ground
     there, as on a phone, instead of drawing a hard edge beside the pill. */
  :root:has(.menu[open]) main > :first-child > .wash::after { background: linear-gradient(to bottom, #01090C 0, rgba(1, 9, 12, 0) 96px), linear-gradient(to bottom, var(--fade-to-bg)); }
}

/* The Menu button instead of the nav's links: on a phone (767px and narrower), and on a wider window where
   the reader's larger text leaves the links no room. The Listen action stays in the row, between the name
   and the Menu button (SITE-FURNITURE.md 3), and the button shows its three bars, its word kept as its
   name. 52em of the header's 16px is 832px, the pill at 864px, where the row (the name, the five links,
   Listen and the pill's padding) takes about 760px at 100% text; the em grows with the reader's text as
   the row's words do (a media query's em does not), so it switches before the links run out of the pill:
   at 130% text below about 1112px, from 140% at 1120px. The two blocks hold the same rules (browsers
   without container queries get the phone's), and the second also keeps the pill in the header, which
   scrolls away with the page (above). */
@media (max-width: 767px) {
  .header-pill { grid-template-columns: minmax(0, 1fr) auto auto; }
  .wordmark { align-self: start; }
  .site-nav { align-self: start; margin-top: 2px; }
  .nav-link { display: none; }
  .nav-cta { margin-left: 0; min-height: 44px; padding: 0 18px; }
  .menu { display: block; }
  .menu-twin { display: inline-flex; }
  .menu, .menu-twin { grid-area: 1 / 3; align-self: start; margin-top: 2px; }
  .menu-button { gap: 0; width: 44px; padding: 0; justify-content: center; }
  .menu-word { position: absolute; width: 1px; height: 1px; overflow: hidden; clip-path: inset(50%); white-space: nowrap; }
  .menu[open] { grid-area: 2 / 1 / 3 / 4; margin-top: 0; }
  .menu[open] > .menu-button { position: absolute; top: calc(var(--pill-top) + 2px); right: var(--pill-end); }
}
@container site-header (width < 52em) {
  .header-pill { position: relative; inset: auto; max-width: none; margin: 0; grid-template-columns: minmax(0, 1fr) auto auto; }
  .top-fade { display: none; }
  .wordmark { align-self: start; }
  .site-nav { align-self: start; margin-top: 2px; }
  .nav-link { display: none; }
  .nav-cta { margin-left: 0; min-height: 44px; padding: 0 18px; }
  .menu { display: block; }
  .menu-twin { display: inline-flex; }
  .menu, .menu-twin { grid-area: 1 / 3; align-self: start; margin-top: 2px; }
  .menu-button { gap: 0; width: 44px; padding: 0; justify-content: center; }
  .menu-word { position: absolute; width: 1px; height: 1px; overflow: hidden; clip-path: inset(50%); white-space: nowrap; }
  .menu[open] { grid-area: 2 / 1 / 3 / 4; margin-top: 0; }
  .menu[open] > .menu-button { position: absolute; top: calc(var(--pill-top) + 2px); right: var(--pill-end); }
}
/* Where even the action does not fit beside the name and the button (under 20em: 320px at 100% text, a
   window below 344px, a phone below 440px at 130% text and below 664px at 200%), it moves into the menu,
   first, as the web app's header does at its compact level, so the name's longest word keeps a line of
   its own, with a reader's text spacing too. */
@container site-header (width < 20em) {
  .header-pill { grid-template-columns: minmax(0, 1fr) auto; }
  .site-nav { display: none; }
  .menu, .menu-twin { grid-area: 1 / 2; }
  .menu[open] { grid-area: 2 / 1 / 3 / 3; }
  .menu-listen { display: flex; }
}
/* A phone: the header scrolls away with the page, 12px from the window's edges, the pill 56px tall. On
   a page whose first section is words, not the home page's photo, the header takes its room in the page
   (where the browser has :has()), so the page starts 30px under it (100px down, as before, at 100% text)
   however tall a reader's larger text makes it: with 200% text the name takes two lines below about
   380px and the pill 106px. The home page's photo runs under it. */
@media (max-width: 767px) {
  .site-header { padding: 12px 12px 0; }
  .site-header:has(.menu[open]), :root:not(:has(.hero-home)) .site-header { position: relative; inset: auto; }
  :root:not(:has(.hero-home)) { --page-top: 30px; }
  .header-pill { min-height: 56px; --pill-top: 4px; --pill-end: 6px; padding: var(--pill-top) var(--pill-end) var(--pill-top) 4px; border-radius: 28px; }
  .wordmark { font-size: 17px; gap: 10px; }
  html { scroll-padding-top: 0; }
}
/* A short window: the header scrolls away with the page instead of covering it (its pill is not fixed,
   above). */
@media (max-height: 480px) {
  html { scroll-padding-top: 0; }
}

/* ---------- type: Outfit 400, 500 and 600, the app's weights (SYN 7.1, SITE-FURNITURE.md 2) ---------- */

/* A heading breaks a word only where the word alone is wider than its line (the body's break-word: the
   reader's larger text on a phone), never to keep a run of words on one line. Words that read best
   together, as an app's name ("Sleep & Focus"), are a .keep: one box that moves to the next line whole
   while it fits a line, and wraps at its spaces where it does not (npm run layout fails a heading word
   broken where it would fit its line). The box draws its link's underline itself. */
h1, h2, h3, h4 { margin: 0 0 16px; text-wrap: balance; }
h1 { font-weight: 400; }
h2, h3 { font-weight: 500; letter-spacing: -0.005em; }
h4 { font-weight: 600; }
.keep { display: inline-block; text-decoration: inherit; }
h1 { font-size: 60px; line-height: 68px; letter-spacing: -0.02em; }
.page-title { font-size: 48px; line-height: 56px; margin-bottom: 16px; }
.section-title { font-size: 32px; line-height: 40px; margin: 0 0 12px; }
h3 { font-size: 20px; line-height: 28px; letter-spacing: 0; }

.lede { font-size: 20px; line-height: 30px; color: var(--muted); margin: 0 0 32px; max-width: 56ch; }
.section-intro { color: var(--muted); max-width: 62ch; margin: 0 0 32px; }
/* A paragraph that another of the same section follows. */
.section-intro-run { margin-bottom: 16px; }
/* Every heading one step (the sections' own 80px, 56 on a phone) below the words before it (L952): the
   paragraph before it keeps its 32px. */
.prose-block h2 { margin-top: calc(var(--section) - 32px); }
.prose-block h2:first-child { margin-top: 0; }
/* From 1100px a section's heading sits on the left and its words on the right, across the whole column
   (L516), every heading still one step below the words before it. */
@media (min-width: 1100px) {
  .prose-block { display: grid; grid-template-columns: minmax(0, 360px) minmax(0, 1fr); column-gap: 64px; align-items: baseline; }
  .prose-block > h2 { grid-column: 1; margin-bottom: 0; }
  .prose-block > p { grid-column: 2; max-width: 68ch; margin: 0; }
  .prose-block > p + p { margin-top: 16px; }
  .prose-block > h2:not(:first-child), .prose-block > h2:not(:first-child) + p { margin-top: var(--section); }
}

.eyebrow {
  display: inline-block;
  font-size: 13px;
  line-height: 20px;
  font-weight: 600;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--muted);
  margin: 0 0 16px;
}

.center { text-align: center; }
/* A name a line must never break inside, such as 4-7-8 at its hyphens. */
.nowrap { white-space: nowrap; }
/* A web address in a heading with its brackets (build.js breakableAddresses): one inline box, so a line
   breaks before it first and it starts a new line whole wherever it fits a line; it breaks at its <wbr>s
   only when it is wider than its line. No wider than its line, so with 200% text on a phone the page
   never scrolls sideways (without max-width it ran to 412 px at 390). */
.web-address { display: inline-block; max-width: 100%; }

@media (max-width: 767px) {
  body { font-size: 16px; line-height: 26px; }
  h1 { font-size: 40px; line-height: 48px; }
  .page-title { font-size: 36px; line-height: 44px; }
}
@media (max-width: 359px) {
  h1 { font-size: 34px; line-height: 42px; }
}
@media (max-width: 767px) {
  .section-title { font-size: 26px; line-height: 32px; }
  h3 { font-size: 19px; line-height: 26px; }
  .lede { font-size: 17px; line-height: 26px; margin-bottom: 24px; }
}

/* ---------- buttons and store badges ---------- */

/* Store badges as Google and Apple ship them, sized by height only, so each keeps its own shape:
   max-width none undoes the img rule above and flex none keeps a row from shrinking one. Both stores
   ask for clear space of a quarter of the badge's height around it, and Apple for at least 40px of
   height on a screen. The App Store badge comes first in a row of badges and Google's is never
   smaller than a badge beside it: one height for both (--badge), and Google's is the wider. Google's
   file (646 by 250) carries clear space as transparent pixels around its badge (564 by 168, 41 file
   pixels in from every edge), so the file is drawn whole, 250/168 of the badge's height, and a
   negative margin of those 41 pixels lets the badge itself take its place: its edges line up with
   the App Store's. npm run layout measures the drawn badges at every width. */
.store-badge { --badge: 48px; display: inline-block; flex: none; line-height: 0; border-radius: 8px; }
.store-badge img { height: var(--badge); width: auto; max-width: none; }
.store-badge img.badge-google-play { height: calc(var(--badge) * 250 / 168); margin: calc(var(--badge) * -41 / 168); }

.platform-soon { margin: 0; color: var(--muted); font-size: 15px; line-height: 22px; font-weight: 500; }

.button {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 10px;
  min-height: 48px;
  max-width: 100%;
  padding: 12px 24px;
  border-radius: 999px;
  background: var(--accent);
  color: #021014;
  font-size: 16px;
  line-height: 20px;
  font-weight: 500;
  text-align: center;
  text-decoration: none;
  transition: transform 150ms var(--ease-productive), background-color 150ms;
}
.button:hover { color: #021014; text-decoration: none; }
/* The one play icon (L966, SITE-FURNITURE.md 5): the app's own (lucide play), filled and stroked, 20px. */
.icon-play { width: 20px; height: 20px; flex: none; fill: currentColor; stroke: currentColor; stroke-width: 1.75; stroke-linejoin: round; stroke-linecap: round; }
.button-lg { min-height: 56px; padding: 16px 28px; font-size: 18px; line-height: 24px; }
/* The second action: an outline pill, never a second accent. */
.button-outline { background: transparent; color: var(--text); border: 1px solid var(--outline); }
.button-outline:hover { color: var(--text); background: rgba(232, 249, 255, 0.07); }

/* A filled pill grows to 1.02 under a mouse, in 50ms and back in 150 (lane T1's pill), and settles to .98
   while pressed. */
@media (hover: hover) and (prefers-reduced-motion: no-preference) {
  .button:not(.button-outline):hover, .nav-cta:hover { transform: scale(1.02); transition-duration: 50ms; }
  .button:not(.button-outline):active, .nav-cta:active { transform: scale(0.98); }
}

.button-row { display: flex; gap: 16px; flex-wrap: wrap; align-items: center; }
.button-row-center { justify-content: center; }

/* A phone app's store block (/iphone, /android): the badge, a line under it, then, wider than 767px,
   the store's QR code and its line, as wide as the badge. A phone shows no QR code: it cannot scan
   its own screen (npm run layout fails one drawn there). */
.store-pick { display: inline-flex; flex-direction: column; align-items: flex-start; gap: 16px; }
.store-pick .store-badge { --badge: 56px; }
.store-note { margin: 0; color: var(--muted); font-size: 15px; line-height: 22px; }
.store-qr { width: 112px; height: 112px; border-radius: 8px; background: #FFFFFF; }
.store-qr-line { width: 0; min-width: 100%; margin: 0; color: var(--muted); font-size: 14px; line-height: 20px; text-wrap: pretty; }
/* Nor a touch tablet held in the hand (L969): a QR code is for a computer's screen. */
@media (max-width: 767px), (hover: none) and (pointer: coarse) {
  .store-qr, .store-qr-line { display: none; }
}

/* ---------- sections ---------- */

/* Sections are set apart by space, never by lines; the page's last section keeps the same room under it. */
.section { padding: var(--section) 0 0; }
main { display: block; padding-bottom: var(--section); }
/* The first section of a page that has no picture hero starts below the fixed header. */
.page-top { padding-top: var(--page-top); }
/* A section's last words keep no room of their own under them: the next block starts one step below
   their ink, whatever ends the section (L952). */
.section-intro:last-child, .lede:last-child, .prose-block > :last-child { margin-bottom: 0; }

/* The artwork wash (L500, SITE-FURNITURE.md 1): a 64 px copy of the page's hero picture, blurred when the
   file was made, behind the top of the section that holds it, fading into the ground through the 17 eased
   stops. It is a background: no room in the layout, no filter, never moving, nothing to load before the
   words. Its section is the layer it sits in, and it stays inside that section's box: the section is
   positioned, so anything of it past its foot would paint over the next section's words. */
.hero, .missing, .close-band { position: relative; isolation: isolate; }
.wash {
  position: absolute;
  z-index: -1;
  inset: 0;
  background-position: center 30%;
  background-size: cover;
  background-repeat: no-repeat;
  opacity: 0.5;
  pointer-events: none;
}
.wash::after { content: ''; position: absolute; inset: 0; background: linear-gradient(to bottom, var(--fade-to-bg)); }
.wash-home { background-image: url('/assets/img/wash-home.webp'); }
.wash-iphone { background-image: url('/assets/img/wash-iphone.webp'); }
.wash-android { background-image: url('/assets/img/wash-android.webp'); }
/* On a phone the home page's photo is itself the band of art at the top, fading into the page: a wash
   under the words would meet its faded foot as a lighter band. On the other pages the header sits in the
   page above the section, so the wash also rises out of the ground at its top edge. */
@media (max-width: 767px) {
  .hero-home .wash { display: none; }
  .wash::after { background: linear-gradient(to bottom, #01090C 0, rgba(1, 9, 12, 0) 96px), linear-gradient(to bottom, var(--fade-to-bg)); }
}

/* The first-load entrance (D13, SITE-FURNITURE.md 6): the first section's blocks fade in and rise 8 px over
   400 ms on the landing curve, 60 ms apart, once. No fill after they end, so one second after the page
   loads nothing runs; nothing on scroll; nothing under reduced motion. */
@keyframes enter {
  from { opacity: 0; transform: translateY(8px); }
}
@media (prefers-reduced-motion: no-preference) {
  .enter { animation: enter var(--duration-entrance) var(--ease-surface) backwards; }
  .enter-2 { animation-delay: var(--stagger-block); }
}

/* A filled panel (no outline): the app's raised surface. */
.panel { background: var(--surface); border-radius: var(--radius); padding: 32px; }
.panel > :last-child { margin-bottom: 0; }

.card-grid { display: grid; grid-template-columns: minmax(0, 1fr); gap: 16px; }
.card { background: var(--surface); border-radius: var(--radius); padding: 28px; }
.card h3 { margin-bottom: 12px; }
/* From 968px each card is a row across the column, its title on the left and its four lines in two
   columns on the right (L970), so no card ends early beside a taller one, as the sections' headings sit
   beside their words (L516). */
@media (min-width: 968px) {
  .card { display: grid; grid-template-columns: minmax(0, 280px) minmax(0, 1fr); column-gap: 40px; align-items: baseline; padding: 32px; }
  .card h3 { margin: 0; }
  .card .tick-list { grid-template-columns: repeat(2, minmax(0, 1fr)); column-gap: 32px; row-gap: 12px; }
}
.card p { color: var(--muted); margin: 0; }

.tick-list { list-style: none; padding: 0; margin: 0; display: grid; gap: 12px; }
.tick-list li { position: relative; padding-left: 26px; color: var(--muted); text-wrap: pretty; }
.tick-list li::before {
  content: '';
  position: absolute;
  left: 4px;
  top: 11px;
  width: 8px;
  height: 8px;
  border-radius: 50%;
  background: var(--muted);
}
@media (max-width: 767px) {
  .panel { padding: 24px 20px; }
  .card { padding: 24px 20px; }
  .tick-list li::before { top: 9px; }
}

/* ---------- the closing band: a filled panel over the page's art, centred, the page's action again ---------- */

.close-band {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 24px;
  padding: 64px;
  overflow: hidden;
  border-radius: var(--radius);
  background: var(--surface);
  text-align: center;
}
/* The band's wash (L526): the page's art, blurred, rising from the band's foot under its surface. */
.close-band > .wash { inset: auto 0 0; height: 100%; opacity: 0.55; background-position: center; }
.close-band > .wash::after { background: linear-gradient(to top, rgba(10, 23, 29, 0) 0%, rgba(10, 23, 29, 0.55) 55%, #0A171D 100%); }
.close-band .page-title { margin: 0; }
.close-band h2 { margin: 0; font-size: 48px; line-height: 56px; letter-spacing: -0.02em; text-wrap: balance; }
.close-band p { margin: 0; color: var(--muted); max-width: 56ch; }
/* Each phone app's own page, drawn alike, the iPhone's first (Apple: "List Apple products first"). */
.close-links { display: flex; flex-wrap: wrap; justify-content: center; gap: 8px 32px; margin: -8px 0; font-size: 16px; line-height: 24px; }
.close-links a { display: inline-flex; align-items: center; min-height: 44px; }
@media (max-width: 767px) {
  .close-band { padding: 40px 20px; gap: 20px; }
  .close-band h2 { font-size: 32px; line-height: 40px; }
}
/* "Download on the App Store" and "Play in your browser" keep one line from 320px (npm run layout
   fails a button whose words wrap). */
@media (max-width: 380px) {
  .close-band { padding: 32px 12px; }
  .button-lg { padding: 14px 22px; font-size: 16px; }
}

/* A note on what this is: quiet text, no box. */
.health-title { font-size: 18px; line-height: 24px; font-weight: 600; margin: 0 0 8px; }
.health p { max-width: 78ch; margin: 0; color: var(--muted); font-size: 15px; line-height: 24px; }

/* ---------- home: the hero ---------- */

/* Two columns inside 1120: the words (596px at most) and the art (the beat's own photo, 480px, square:
   920 file pixels, sharp on a 2x screen), centred on each other. The picture of the player's beat card
   that stood under the photo is gone (L525: it looked like a control and did nothing). The art shrinks
   with a short window so the stores stay in the first screen. A flex row that wraps: the words never get narrower than their longest
   word (a flex item's min-content), so where the reader's larger text makes a word wider than the
   words' column, the art goes under the words instead of a word breaking or running over the art
   (npm run layout fails either). At 100% text the row never wraps wider than 767px. */
.hero-home { padding: 104px 0 0; }
.hero-split {
  --art: clamp(320px, calc(100svh - 240px), 480px);
  --words: 596px;
  display: flex;
  flex-wrap: wrap;
  justify-content: space-between;
  column-gap: 64px;
  row-gap: 40px;
  align-items: center;
}
.hero-words { flex: 1 1 0; max-width: var(--words); display: flex; flex-direction: column; align-items: flex-start; }
.hero-art, .hero-panel { flex: none; width: var(--art); }
/* As wide as the column, so a word wider than the column (a phone with the reader's larger text) breaks
   inside it instead of running past the window. */
.hero-words > h1 { align-self: stretch; }
.hero-home h1 { margin: 0 0 20px; max-width: 596px; }
.hero-home .lede { margin: 0 0 32px; }
.hero-stores { display: flex; flex-wrap: wrap; align-items: center; gap: 16px; margin-top: 16px; }
.hero-caption { margin: 16px 0 0; color: var(--muted); font-size: 15px; line-height: 22px; }
.hero-play-phone, .hero-also { display: none; }
.hero-also { margin: 16px 0 0; color: var(--muted); font-size: 15px; line-height: 22px; }

.hero-art { display: flex; flex-direction: column; gap: 16px; }
/* The beat's own photo, square, with the art edge (SYN 7.3) and the cover's shadow. */
.hero-art { position: relative; border-radius: var(--radius); }
.hero-photo { width: var(--art); height: var(--art); border-radius: var(--radius); object-fit: cover; box-shadow: var(--shadow-cover); }
.hero-art::after { content: ''; position: absolute; inset: 0; border-radius: inherit; box-shadow: var(--art-edge); pointer-events: none; }

@media (min-width: 768px) and (max-width: 1099px) {
  .hero-split { --art: clamp(300px, min(calc(100svh - 240px), 40vw), 480px); --words: none; column-gap: 40px; }
  .hero-home h1 { font-size: 48px; line-height: 56px; }
}

/* Phones: the photo as a band across the top (the header floats over it), then the words, the
   visitor's own store badge, the browser as an outline pill, and the other store as a line. Any
   phone that is not an iPhone gets Google Play. */
@media (max-width: 767px) {
  .hero-home { padding: 0; }
  .hero-split { flex-direction: column; flex-wrap: nowrap; align-items: stretch; row-gap: 0; }
  .hero-words, .hero-art, .hero-panel { flex: none; width: auto; max-width: none; }
  .hero-art { order: -1; margin: 0 calc(-1 * var(--gutter)); border-radius: 0; }
  .hero-photo { width: 100%; height: clamp(160px, 36svh, 300px); border-radius: 0; box-shadow: none; }
  /* The photo's bottom third fades into the page (L537), as the web app's washes do. */
  .hero-art::after { inset: 33% 0 0; border-radius: 0; box-shadow: none; background: linear-gradient(to bottom, var(--fade-to-bg)); }
  .hero-play, .hero-caption { display: none; }
  .hero-words { padding-top: 24px; }
  .hero-home h1 { margin-bottom: 16px; }
  .hero-home .lede { margin-bottom: 24px; }
  .hero-stores { margin-top: 0; }
  .hero-stores .store-badge { --badge: 56px; }
  .hero-store-apple, .hero-also-play { display: none; }
  /* The visitor's own store's badge, then Listen in the brand blue at the badge's own width and height
     (L538), the store order kept: Google's badge is 564/168 of its height wide, Apple's 119.66/40. */
  .hero-play-phone { display: inline-flex; margin-top: 16px; width: calc(56px * 564 / 168); min-height: 56px; padding: 0 16px; }
  .hero-also-apple { display: block; }
}
/* An iPhone (Safari's engine, every iPhone browser): the App Store's badge, Google Play as the line. */
@supports (-webkit-touch-callout: none) {
  @media (max-width: 767px) {
    .hero-store-apple, .hero-also-play { display: block; }
    .hero-store-play, .hero-also-apple { display: none; }
    .hero-play-phone { width: calc(56px * 119.66 / 40); }
  }
}

/* ---------- home: the sections ---------- */

/* The player: the web app's full player in a rounded frame with no browser chrome (L967), over a soft wash
   of its own art, which fades out at its edges. */
.home-player .container { position: relative; isolation: isolate; }
.home-player .container::before {
  content: '';
  position: absolute;
  z-index: -1;
  inset: 64px 0 0;
  background: radial-gradient(closest-side, rgba(1, 9, 12, 0) 30%, #01090C 100%), url('/assets/img/wash-home.webp') center / cover no-repeat;
  opacity: 0.6;
  pointer-events: none;
}
.player-window {
  position: relative;
  margin: 0;
  border-radius: var(--radius);
  overflow: hidden;
  background: var(--surface-2);
  box-shadow: var(--shadow-cover);
}
.player-window::after { content: ''; position: absolute; inset: 0; border-radius: inherit; box-shadow: var(--art-edge); pointer-events: none; }
/* The capture loads at once, never lazily: on a tablet held upright it is in the first screen and is
   the page's largest picture. On a phone this figure is hidden, and its picture's phone source is a
   6 KB preview of the same capture in the same shape, so a phone never fetches the computer's capture.
   The capture comes at 2x and 3x (srcset by density): a 3x screen gets the 3360px file, never drawn past
   it, and a 1x or 2x screen only ever takes the 2240px one.
   On a phone turned on its side the window shows nothing or that preview until the capture loads,
   never a picture stretched out of its shape. */
.player-window picture { display: block; }
.player-window img { width: 100%; height: auto; aspect-ratio: 2240 / 1414; }
.player-phone { display: none; margin: 0; }

@media (max-width: 767px) {
  .player-window { display: none; }
  .player-phone { display: flex; justify-content: center; }
  .player-phone img { width: min(300px, 100%); height: auto; aspect-ratio: 780 / 1612; border-radius: 24px; }
}

/* Beat categories: each a link to the category's page in the web app (/app/beats/<slug>/, L529), drawn
   with the picture the app's Beats pages show for it (D22), at 5:3, four a row (two on a phone), each
   name bottom left on a dark layer. The whole tile is the link; a mouse over it grows the picture to
   1.04, as the web app's tiles do. The layer is darkest under the name, measured in pixels from the bottom edge (where
   the name sits at every size), then fades out by three quarters of the way up: the name keeps 4.5:1
   against the lightest tenth of the photo behind it at every width (WCAG 1.4.3; npm run layout measures
   it). */
.tiles { list-style: none; margin: 0; padding: 0; display: grid; grid-template-columns: repeat(4, minmax(0, 1fr)); gap: 24px; container-type: inline-size; }
.tile { position: relative; aspect-ratio: 5 / 3; overflow: hidden; border-radius: var(--radius-tile); }
.tile-link { position: absolute; inset: 0; color: var(--text); text-decoration: none; border-radius: inherit; }
.tile-link:hover { color: var(--text); }
.tile img { width: 100%; height: 100%; object-fit: cover; transition: transform 200ms var(--ease-productive); }
.tile-link::after { content: ''; position: absolute; inset: 0; border-radius: inherit; box-shadow: var(--art-edge); background: linear-gradient(to top, rgba(2, 14, 19, 0.75) 0, rgba(2, 14, 19, 0.55) 44px, rgba(2, 14, 19, 0) 75%); }
/* The tile clips its picture. A browser without :has() (Firefox before 121, Chrome before 105) draws the
   ring inside the clip; one with it draws the ring on the tile, outside the clip, and only such a browser
   takes the link's own ring away (with it inside @supports, no browser is left with none, WCAG 2.4.7).
   Inside the clip the link's outline lies under its own dark layer (::after, positioned, so painted over
   the link's outline), which dimmed the ring's foot almost to nothing; so the layer itself draws the ring
   too, as an inset shadow, which paints over the layer's own gradient (SITE-4). The outline stays for
   forced colours, where shadows are not drawn. */
.tile-link:focus-visible { outline-offset: -3px; }
.tile-link:focus-visible::after { box-shadow: inset 0 0 0 3px var(--accent), var(--art-edge); }
@supports selector(:has(*)) {
  .tile-link:focus-visible { outline: none; }
  .tile-link:focus-visible::after { box-shadow: var(--art-edge); }
  .tile:has(.tile-link:focus-visible) { overflow: visible; }
  .tile:has(.tile-link:focus-visible) .tile-link { outline: 3px solid var(--accent); outline-offset: 3px; }
  .tile:has(.tile-link:focus-visible) img { border-radius: var(--radius-tile); }
}
@media (hover: hover) and (prefers-reduced-motion: no-preference) {
  .tile-link:hover img { transform: scale(1.04); transition-duration: 100ms; }
}
.tile-label { position: absolute; left: 16px; bottom: 12px; z-index: 1; font-size: 18px; line-height: 24px; font-weight: 600; }
@media (max-width: 767px) {
  .tiles { gap: 12px; }
  .tile { grid-column: span 2; }
  .tile-label { left: 12px; bottom: 8px; font-size: 16px; line-height: 22px; }
}
/* With the reader's larger text the longest name (Meditate) can outgrow its tile: two tiles a row on a
   row narrower than 28em of its own type, one on a row narrower than 13.5em. The em grows with the
   reader's text as the names do, so at 100% text neither changes a row (at the least 688px wide with
   four tiles, 288px with two). */
@container (width < 28em) {
  .tile { grid-column: span 2; }
}
@container (width < 13.5em) {
  .tile { grid-column: span 4; }
}

/* Inside the app: the app's own screens, each cropped below the status bar (no device's own
   details), straight, with its caption. Four across from 1180px, where each is at least 240px wide;
   narrower, a sideways row with the next screen peeking in, each 260 to 300px wide, so the words in
   a screen stay readable (npm run layout fails a screen drawn under 240px wide). The row is a named
   region that takes keyboard focus (tabindex 0), so the arrow keys scroll it in every engine, Safari
   included (WCAG 2.1.1; npm run layout fails a sideways row a keyboard cannot reach). Its ring is
   drawn inside its box: the row reaches the window's edges, where the usual ring would be off screen. */
.screens { display: grid; grid-template-columns: repeat(4, minmax(0, 1fr)); gap: 32px; }
.screens:focus-visible { outline-offset: -3px; }
.screen-shot { margin: 0; }
.screen-shot img { width: 100%; height: auto; border-radius: var(--radius); background: var(--bg); box-shadow: var(--art-edge); }
.screen-shot figcaption { margin-top: 12px; color: var(--muted); font-size: 15px; line-height: 22px; text-wrap: pretty; }
@media (max-width: 1179px) {
  .screens {
    display: flex;
    gap: 24px;
    margin: 0 calc(-1 * var(--gutter));
    padding: 0 var(--gutter) 12px;
    overflow-x: auto;
    scroll-snap-type: x mandatory;
    scroll-padding: 0 var(--gutter);
  }
  .screen-shot { flex: 0 0 clamp(260px, 68vw, 300px); scroll-snap-align: start; }
}

/* The explainer: the wave photo under a flat veil, one glass card on it (as the web app's /about). */
.explainer { position: relative; isolation: isolate; overflow: hidden; border-radius: var(--radius); padding: 64px 48px; }
.explainer-art { position: absolute; inset: -24px; z-index: -1; background: url('/assets/img/explainer-waves.webp') center / cover no-repeat; filter: blur(6px) saturate(1.2); }
.explainer-art::after { content: ''; position: absolute; inset: 0; background: rgba(10, 23, 29, 0.4); }
.explainer-card {
  max-width: 760px;
  padding: 32px;
  border: 1px solid var(--glass-card-border);
  border-radius: var(--radius);
  background: var(--glass-card);
}
@media (prefers-reduced-transparency: reduce) {
  .explainer-card { background: var(--glass-solid); }
}
.explainer-card h2 { font-size: 24px; line-height: 32px; margin: 0 0 16px; }
.explainer-card p { margin: 0 0 16px; color: var(--text); }
.explainer-card p:last-child { margin-bottom: 0; }
.explainer-card .explainer-aside { padding-top: 16px; border-top: 1px solid var(--line); }
@media (max-width: 767px) {
  .explainer { display: flex; flex-direction: column; padding: 0; background: var(--surface); }
  .explainer-art { position: relative; inset: auto; z-index: auto; height: 160px; filter: none; }
  .explainer-art::after { display: none; }
  .explainer-card { max-width: none; padding: 20px; border: 0; border-radius: 0; background: var(--surface); }
  .explainer-card h2 { font-size: 22px; line-height: 28px; }
}

/* ---------- the phone apps' pages (/iphone, /android): one structure for both ---------- */

/* The words beside the app itself, on a filled panel. */
.hero-app { padding: var(--page-top) 0 0; }
/* Both app pages draw their app in one frame of one shape at every width (L533), so going from /iphone to
   /android the frame neither moves nor changes size: a filled panel 20 wide to 19 tall, 600px wide at the
   1120 column (the words take the 464px it leaves), 320 to 440 on a tablet, and on a phone a band across
   the whole window, at most 440px tall. The iPhone app rises from 24px under the frame's top: two phones
   whole from 1180px, one cut by the frame's foot narrower. /android's older art (two tilted phones, cut
   above their tab bars) spans the frame's width standing on its foot, until captures of the live Android
   app replace it (lane Z, with L493). The art edge is drawn over whatever reaches the frame's edge. */
.hero-app .hero-split { --art: 600px; --words: none; column-gap: 56px; }
/* Beside the words, level with the heading's top on both pages, so the words' own height (the iPhone page's
   lede runs a line longer) never moves the frame. */
@media (min-width: 768px) {
  .hero-app .hero-panel { align-self: flex-start; }
}
.hero-panel { position: relative; display: flex; align-items: flex-start; justify-content: center; aspect-ratio: 20 / 19; padding: 24px; border-radius: var(--radius); background: var(--surface); overflow: hidden; }
.hero-panel::after { content: ''; position: absolute; inset: 0; border-radius: inherit; box-shadow: var(--art-edge); pointer-events: none; }
.hero-panel-edge { align-items: flex-end; padding: 0; }
.hero-panel img { width: 100%; height: auto; }
@media (min-width: 768px) and (max-width: 1179px) {
  .hero-app .hero-split { --art: clamp(320px, 40vw, 440px); column-gap: 40px; }
}
@media (min-width: 768px) and (max-width: 1099px) {
  .hero-app h1 { font-size: 48px; line-height: 56px; }
}
@media (max-width: 767px) {
  .hero-app .hero-split { gap: 24px; }
  .hero-app .hero-words { padding: 0; }
  .hero-panel { max-height: 440px; margin: 0 calc(-1 * var(--gutter)); padding: 24px 16px 0; border-radius: 0; }
  .hero-panel::after { display: none; }
  .hero-panel-edge { padding: 0; }
  .hero-panel-edge img { width: min(100%, 520px); }
}

/* A phone drawn around one of the app's screens: a generic rounded frame, with no button, no sensor
   housing and no status bar (the screen is cropped below it). */
.device {
  flex: none;
  padding: 8px;
  border-radius: 36px;
  background: #0B161B;
  box-shadow: inset 0 0 0 2px rgba(232, 249, 255, 0.16), 0 24px 48px rgba(0, 0, 0, 0.5);
}
.device img { width: 100%; height: auto; border-radius: 28px; background: var(--bg); }
/* /iphone's second screen is a picture element whose source below 1180px, where it is hidden, is the
   first screen's own file, so it loads at once without costing a phone a file (site-code-3). */
.device picture { display: block; }

/* /iphone: the app as straight screens, never as thumbnails. From 1180px, Home and the player side by
   side, each screen 248px wide; from 768 to 1179px, Home alone beside the words, 256 to 300px wide; on
   a phone, Home alone, 272 to 300px wide, the panel across the whole window (npm run layout fails an
   app screen in a hero drawn under 240px wide, or under 260 on a phone). */
.hero-screens { gap: 24px; align-items: flex-start; }
.hero-screens .device { width: 264px; }
@media (max-width: 1179px) {
  .hero-screens .device { width: min(100%, 316px); }
  .hero-screens .device-second { display: none; }
}


/* ---------- About and Support ---------- */

/* Our apps: one filled panel per app, the iPhone's first, each with the app itself. Three across from
   968px (each at least 280px wide), one per row below it, so a panel never sits alone beside an empty
   space (npm run layout fails a grid whose rows hold different numbers of panels). */
.app-panels { display: grid; grid-template-columns: minmax(0, 1fr); gap: 24px; list-style: none; margin: 0; padding: 0; }
@media (min-width: 968px) {
  .app-panels { grid-template-columns: repeat(3, minmax(0, 1fr)); }
}
/* One art treatment (L545): each app rises into its panel's art box from 24px under its top and is cut
   by the box's foot: the iPhone app's Home as one screen 216px wide in a generic frame, the Android app's
   older art across the box, and the web app as a desktop window, its Sounds library beside Now playing.
   The whole panel is the link (its name's link stretched over it), lit a step on hover.
   Each picture keeps the size the three panels across draw it at when the panels stack below 968px (as
   Stripe's and Linear's product shots do when a grid drops to one column), instead of growing with the
   panel: the Android art at most 300px wide (its file is 900, so sharp on a 3x phone), so no picture is
   drawn past its file and each shows the product, not a blown-up strip of its top (site-eyes-1).
   The web app's window (SITE-6) is always 315px wide, the computer capture's library and Now playing
   columns (828 of the app's 1120 CSS px) at 0.38 of the app's size, so the window's foot always falls in
   the gutter under both panels, under the second sound's slider and over the player bar, and the mix is
   whole at every width (945px file for a 3x screen, srcset). It is centred where it fits. In a narrower
   box (three across from 968 to about 1145px, and phones narrower than 371px) it never runs out past a
   side edge, which would cut the library's "Sounds" heading and its row icons at the window's left: it
   shrinks to the panel less 12px each side and moves down by what it lost in height (margin-top, a
   percentage of the art box's width), so the card's foot still cuts it at the same line of the app,
   the gutter under both panels (216/315 = 0.6857 of its width), as Stripe lets a card's foot cut a
   window rising from it. */
.app-panel { position: relative; display: flex; flex-direction: column; overflow: hidden; border-radius: var(--radius); background: var(--surface); transition: background-color 150ms; }
.app-panel:hover { background: #0E1C23; transition-duration: 50ms; }
.app-panel-link { color: var(--text); text-decoration: none; }
.app-panel-link::after { content: ''; position: absolute; inset: 0; z-index: 1; border-radius: inherit; }
.app-panel:hover .app-panel-link { color: var(--text); text-decoration: underline; text-decoration-thickness: 1px; }
/* Without :has() the link keeps the site's own ring, inside the panel's clip (see the tiles). */
@supports selector(:has(*)) {
  .app-panel-link:focus-visible { outline: none; }
  .app-panel:has(.app-panel-link:focus-visible) { outline: 3px solid var(--accent); outline-offset: 3px; }
}
.app-panel-art { display: flex; align-items: flex-start; justify-content: center; height: 240px; padding: 24px 24px 0; background: var(--surface-2); overflow: hidden; }
.app-panel-art img { width: 100%; max-width: 300px; height: auto; }
.app-panel-art .device { width: 232px; }
.app-panel-art .device img { width: 100%; max-width: none; max-height: none; }
.browser { flex: none; width: min(315px, calc(100% + 24px)); margin: max(0px, calc(216px - (100% + 24px) * 0.6857)) max(calc((100% - 315px) / 2), -12px) 0; border-radius: 12px; overflow: hidden; background: var(--bg); box-shadow: 0 16px 40px rgba(0, 0, 0, 0.45); }
.browser img { display: block; width: 100%; max-width: none; }
.app-panel-body { padding: 24px 28px 28px; }
/* From 768 to 967px a stacked panel is 720 to 919px wide, and the art centred over a line of words read
   sparse and lopsided (SITE-4). There each panel lays its art beside its words, the art in the left half
   and the name and line centred in the right, as leading app sites lay out a product card at tablet
   width. The pictures keep their sizes (the iPhone's 232px frame, the Android art at most 300px, the
   web app's 315px window). */
@media (min-width: 768px) and (max-width: 967px) {
  .app-panel { flex-direction: row; }
  .app-panel-art { flex: 0 0 50%; }
  .app-panel-body { flex: 1 1 0; min-width: 0; align-self: center; padding: 28px 32px; }
}
.app-panel h3 { margin: 0 0 6px; }
.app-panel p { margin: 0; color: var(--muted); }

.details-grid { display: grid; grid-template-columns: minmax(0, 1fr); gap: 24px 32px; margin: 0; }
/* Three across from a tablet up, never two over one (L951). */
@media (min-width: 768px) {
  .details-grid { grid-template-columns: repeat(3, minmax(0, 1fr)); }
}
.details-grid dt { margin: 0 0 4px; font-weight: 600; }
.details-grid dd { margin: 0; color: var(--muted); font-size: 16px; line-height: 26px; }

/* /support: the words, then the answers; from 900px the contact panel is a column of its own beside them,
   staying in sight while the answers scroll (L520), so the answers and the panel fill the 1120 column. */
.support-grid { display: grid; grid-template-columns: minmax(0, 1fr); gap: 32px; }
.support-intro .lede { margin-bottom: 0; }
.support-answers { padding-top: calc(var(--section) - 32px); }
@media (min-width: 900px) {
  .support-grid { grid-template-columns: minmax(0, 1fr) minmax(0, 360px); grid-template-rows: auto 1fr; column-gap: 64px; row-gap: 0; }
  .support-intro { grid-column: 1; grid-row: 1; }
  .contact-panel { grid-column: 2; grid-row: 1 / 3; align-self: start; }
  .support-answers { grid-column: 1; grid-row: 2; }
}
@media (min-width: 900px) and (min-height: 640px) {
  .contact-panel { position: sticky; top: 112px; }
}
.contact-email { margin: 0 0 12px; font-size: 24px; line-height: 32px; font-weight: 500; overflow-wrap: anywhere; }
.contact-panel p { color: var(--muted); }
.contact-panel .contact-email { color: var(--text); font-size: 20px; line-height: 28px; }
/* The answers as real accordions (L496), the first one open: a filled panel each, its question the
   control, a chevron that turns when it opens. Closed answers stay findable (a browser's find in page
   opens them). */
.faq { display: grid; grid-template-columns: minmax(0, 1fr); gap: 12px; }
.faq-item { background: var(--surface); border-radius: var(--radius); padding: 0 32px; }
.faq-item[open] { padding-bottom: 28px; }
.faq-item > summary {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 16px;
  margin: 0 -32px;
  padding: 24px 32px;
  border-radius: var(--radius);
  list-style: none;
  cursor: pointer;
}
.faq-item > summary::-webkit-details-marker { display: none; }
.faq-item > summary h3 { margin: 0; font-size: 20px; line-height: 28px; }
.faq-item > summary::after {
  content: '';
  flex: none;
  width: 10px;
  height: 10px;
  margin-right: 4px;
  border-right: 2px solid var(--muted);
  border-bottom: 2px solid var(--muted);
  transform: translateY(-3px) rotate(45deg);
  transition: transform 150ms var(--ease-productive);
}
.faq-item[open] > summary::after { transform: translateY(2px) rotate(-135deg); }
.faq-item > summary:hover h3 { text-decoration: underline; text-decoration-thickness: 1px; text-underline-offset: 3px; }
.faq-item p { color: var(--muted); margin: 0; }
.faq-item p + p, .faq-item .steps + p { margin-top: 12px; }
/* The cancel steps (L524): one filled group per place, each its steps in order. */
.steps { display: grid; gap: 12px; margin: 16px 0 0; }
.steps-group { padding: 16px 20px; border-radius: 12px; background: var(--surface-2); }
.steps-group h4 { margin: 0 0 6px; font-size: 16px; line-height: 24px; }
.steps ol { display: grid; gap: 6px; margin: 0; padding-left: 22px; color: var(--muted); font-size: 16px; line-height: 24px; }
@media (max-width: 767px) {
  .faq-item { padding: 0 20px; }
  .faq-item[open] { padding-bottom: 24px; }
  .faq-item > summary { margin: 0 -20px; padding: 20px; }
  .faq-item > summary h3 { font-size: 18px; line-height: 26px; }
  .steps-group { padding: 14px 16px; }
  .contact-email { font-size: 20px; line-height: 28px; }
}

/* The 404 page (L519): the brand's photo over its own wash, the message, and three ways on. */
.missing-card { display: flex; flex-direction: column; align-items: center; gap: 16px; max-width: 680px; margin: 0 auto; text-align: center; }
.missing-card .eyebrow, .missing-card .page-title { margin: 0; }
.missing-card p { margin: 0; color: var(--muted); }
.missing-card .button-row { margin-top: 16px; }
.missing-art { width: 200px; height: 200px; margin-bottom: 8px; border-radius: var(--radius); object-fit: cover; box-shadow: var(--shadow-cover); outline: 1px solid rgba(232, 249, 255, 0.08); outline-offset: -1px; }
@media (max-width: 767px) {
  .missing-art { width: 160px; height: 160px; }
}

/* ---------- legal pages: the same type, the policy's own text ---------- */

.section-legal { padding: var(--page-top) 0 0; }
.prose { color: var(--muted); }
.prose h2 { color: var(--text); font-size: 26px; line-height: 34px; margin: 48px 0 12px; }
.prose h3 { color: var(--text); font-size: 20px; line-height: 28px; margin: 32px 0 10px; }
.prose h4 { color: var(--text); font-size: 17px; line-height: 26px; margin: 24px 0 8px; font-weight: 600; }
.prose p { margin: 0 0 16px; }
.prose ul, .prose ol { padding-left: 22px; margin: 0 0 18px; }
.prose li { margin-bottom: 10px; }
.prose li > ul, .prose li > ol { margin-top: 10px; }
.prose strong, .prose b { color: var(--text); font-weight: 600; }
.prose > h2:first-child { margin-top: 0; }
/* Markdown turns a line indented with a tab into <pre><code>. In the policy that is running text,
   so it wraps and reads like the paragraphs around it. */
.prose pre { margin: 0 0 16px; white-space: pre-wrap; overflow-wrap: anywhere; }
.prose pre, .prose pre code { font: inherit; }
.legal-updated { color: var(--muted); font-size: 15px; line-height: 22px; margin: 0 0 40px; }
/* The legal pages' column (L508, L953, L539): the text at about 680px, starting where the header's pill
   starts; from 1100px the Contents rail beside it on the right, staying in sight as the text scrolls;
   narrower, Contents opens and closes above the text. The rail is the page's own section headings
   (build.js legalContents), and the text is the policy's own, unchanged. */
.legal-layout { display: grid; grid-template-columns: minmax(0, 680px); column-gap: 64px; }
.legal-layout > .page-title, .legal-layout > .legal-updated { grid-column: 1 / -1; }
.contents-rail { display: none; }
.contents-fold { margin: 0 0 40px; border-radius: var(--radius); background: var(--surface); }
.contents-fold > summary {
  display: flex;
  align-items: center;
  justify-content: space-between;
  min-height: 52px;
  padding: 0 20px;
  border-radius: var(--radius);
  color: var(--text);
  font-size: 16px;
  font-weight: 500;
  list-style: none;
  cursor: pointer;
}
.contents-fold > summary::-webkit-details-marker { display: none; }
.contents-fold > summary::after { content: ''; width: 9px; height: 9px; margin-right: 4px; border-right: 2px solid var(--muted); border-bottom: 2px solid var(--muted); transform: translateY(-3px) rotate(45deg); }
.contents-fold[open] > summary::after { transform: translateY(2px) rotate(-135deg); }
.legal-contents ol { margin: 0; padding: 0; list-style: none; }
.legal-contents li a {
  display: block;
  padding: 7px 0;
  color: var(--muted);
  font-size: 15px;
  line-height: 22px;
  text-decoration: none;
}
.legal-contents li a:hover { color: var(--text); text-decoration: underline; }
.contents-fold ol { padding: 0 20px 12px; }
.contents-fold li a { padding: 10px 0; min-height: 44px; }
.contents-title { margin: 0 0 8px; color: var(--text); font-size: 13px; line-height: 20px; font-weight: 600; letter-spacing: 0.09em; text-transform: uppercase; }
@media (min-width: 1100px) {
  .legal-layout { grid-template-columns: minmax(0, 680px) minmax(0, 240px); }
  .legal-layout > .prose { grid-column: 1; grid-row: 3; }
  .legal-contents { grid-column: 2; grid-row: 3; align-self: start; }
  .contents-fold { display: none; }
  .contents-rail { display: block; }
  .legal-contents li a { padding: 5px 0; font-size: 14px; line-height: 20px; }
}
/* The rail stays in sight as the text scrolls only where the window holds it whole (it never scrolls
   inside itself, so each of its links is reached by scrolling the page alone): 14 sections or so from a
   600px window, the Terms' 25 in tighter rows from 870px. The Terms' rail, stuck 112px down, ends 850px
   down (three of its entries take two lines in its 240px), so its last entry, Contact Us, was under the
   window's foot from 820 to 849px (site-code-1); npm run layout fails a stuck rail that runs past it. */
.legal-contents-long .contents-rail li a { padding-top: 3px; padding-bottom: 3px; }
@media (min-width: 1100px) and (min-height: 600px) {
  .legal-contents:not(.legal-contents-long) { position: sticky; top: 112px; }
}
@media (min-width: 1100px) and (min-height: 870px) {
  .legal-contents-long { position: sticky; top: 112px; }
}
/* A Japanese heading breaks between phrases, not inside a word (L521), where the browser can tell them
   apart; elsewhere it breaks as today. */
:lang(ja) h1, :lang(ja) h2 { word-break: auto-phrase; }
@media (max-width: 767px) {
  .prose h2 { font-size: 22px; line-height: 30px; }
  /* Only Chromium reads auto-phrase (Safari and Firefox do not, MDN's data on 2026-11-12), so on a phone
     the Japan notice's title (12 characters, each 1em wide in the phone's Japanese font, 0.98em with the
     title's -0.02em spacing) is set small enough to stay on one line of the text column: a line that never
     breaks cannot break inside a word in any browser (r3-site-eyes-all-1). The 12.5 leaves room for a
     desktop window's scrollbar; from 482px wide it is 36px again. min() and calc() in font-size: Safari
     11.1, Firefox 75, Chrome 79. */
  :lang(ja) .page-title { font-size: min(36px, calc((100vw - 2 * var(--gutter)) / 12.5)); line-height: 1.3; }
}

/* ---------- footer ---------- */

.site-footer { background: var(--bg); border-top: 1px solid var(--line); padding-top: 48px; }
/* No footer link wraps (npm run layout fails one that does). The longest in a column is the email
   address (257px at 15px, 240px at 14px), measured 2026-10-26: four columns of 262px from 1100px, two
   of 332px or more down to 768px, and on a phone Legal and Contact across the whole width, Listen and
   Company side by side only where each gets 180px. "Your Privacy Choices" with its icon (215px at 15px,
   203px at 14px) has the footer's last line to itself (.footer-choices). */
.footer-nav { display: grid; grid-template-columns: repeat(4, minmax(0, 1fr)); gap: 32px 24px; padding-bottom: 40px; }
@media (max-width: 1099px) {
  .footer-nav { grid-template-columns: repeat(2, minmax(0, 1fr)); }
}
/* With the reader's larger text the email address's longest piece ("@mellotonestudios.com", 157px at
   15px) outgrows a quarter of the row: two columns instead of four where the row is narrower than 39em
   of its own type. The em grows with the reader's text as the address does, so at 100% text it never
   applies (the row is 1020px wide at the least from 1100px). */
.site-footer > .container { container-type: inline-size; }
@media (min-width: 1100px) {
  @container (width < 39em) {
    .footer-nav { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  }
}
.footer-col { display: flex; flex-direction: column; gap: 0; align-items: flex-start; }
.footer-heading { font-size: 15px; line-height: 20px; font-weight: 600; letter-spacing: 0; color: var(--text); margin: 0 0 4px; }
/* Each link a target of its own: 32px tall with a mouse, 44 on a phone or any touch screen (L499), its
   words on one line (npm run layout fails one that wraps). */
.footer-col a { display: inline-flex; align-items: center; min-height: 32px; color: var(--muted); text-decoration: none; font-size: 15px; line-height: 22px; }
.footer-col .footer-name, .footer-col .footer-address { margin-top: 5px; }
.footer-col a:hover { color: var(--text); text-decoration: underline; }
.footer-name { margin: 0; color: var(--text); font-size: 15px; line-height: 22px; }
.footer-address { margin: 0; color: var(--muted); font-size: 15px; line-height: 22px; }
/* "Your Privacy Choices" with the CCPA opt-out icon 6px after the last word; the word and the icon
   never part. */
.privacy-choices-tail { white-space: nowrap; }
.privacy-choices-tail img { display: inline-block; vertical-align: middle; margin-left: 6px; }
.footer-base { border-top: 1px solid var(--line); padding-top: 20px; padding-bottom: 32px; }
.footer-base p { color: var(--muted); font-size: 13px; line-height: 20px; margin: 0; }
.footer-base p + p { margin-top: 6px; }
/* "Your Privacy Choices", for readers in the US and its territories only, is the footer's last line,
   after the credit lines, as Headspace's footer puts it in its bottom row of legal links. Nothing
   comes after it, so its showing moves nothing on the page, at any width. */
.footer-choices { display: block; width: fit-content; min-height: 32px; margin-top: 8px; padding: 5px 0; color: var(--muted); text-decoration: none; font-size: 15px; line-height: 22px; }
.footer-choices:hover { color: var(--text); text-decoration: underline; }
/* On any touch screen every footer link is a 44px target (L499), "Your Privacy Choices" too: a block of
   words (a flex box drops the space before its no-wrap tail), 44 tall from its padding. This comes after
   the rules above, whose 32px it overrides at the same specificity: before them, the later 32px won on
   a tablet or a touch laptop (site-code-2; npm run layout measures the footer on a touch tablet). */
@media (pointer: coarse) {
  .footer-col a { min-height: 44px; }
  .footer-choices { min-height: 44px; padding: 11px 0; }
}
/* Until the one script has read the reader's region file (build/assets/js/site.js), the link is not
   drawn and holds no room: nobody sees it, Tab skips it, a screen reader does not read it, and where it
   leaves the page (outside the US) nothing moves either. In the US it then shows as the last line.
   !important, so no later rule can draw it while it waits; npm run check refuses any other rule that
   sets display with !important or visibility to anything but hidden, or uses all. */
[data-privacy-choices-link="waiting"] { display: none !important; }

/* A phone: two columns (L963), Binaural Beats beside Company and Legal one over the other, then Contact
   across the row (the email is wider than half a phone); under 360px Legal goes across too. A legal page
   has no first column: Company and Legal side by side. */
@media (max-width: 767px) {
  .footer-nav { grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 28px 16px; }
  .footer-products { grid-row: span 2; }
  .footer-contact { grid-column: 1 / -1; }
  .footer-col a, .footer-name, .footer-address, .footer-choices { font-size: 14px; }
  .footer-col a { min-height: 44px; }
  .footer-choices { min-height: 44px; padding: 11px 0; }
}
@media (max-width: 359px) {
  .footer-legal { grid-column: 1 / -1; }
}

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