/* App-owned structural kit — the replacement for the vendored legacy CSS.
   Every value here was extracted from the deployed pre-migration build
   (parity/foundation-styles.json.txt) which is itself the extracted
   production impression (parity/design-tokens.md, controls-reference.md).
   Shared patterns live here; one-off styling belongs in components as
   Tailwind token utilities. */

/* --- brand font (files in public/static/fonts, weights 300/400/500/700)

   woff2 first — a lossless repackaging of the SAME ttf (verified: 772
   glyphs and identical vertical metrics per weight), ~73% smaller
   (116KB -> ~31KB). The ttf stays as the fallback src for anything too
   old to know woff2. All four files are also preloaded from index.html,
   so they are in flight before this stylesheet is even parsed.

   font-display: OPTIONAL, decided by the stability doctrine, not by
   default. `swap` guarantees Gotham but allows a LATE swap — text
   reflowing after paint, which is exactly the "niemals springen" class,
   and exactly what Chrome's slow-network intervention was doing to us
   uninvited. `optional` inverts the promise: with preload + 31KB files
   the font wins the block period on any ordinary connection, and on a
   genuinely slow first visit the fallback simply STAYS for that
   pageload — no swap, no jump, no intervention (there is nothing left
   to intervene in) — while the font finishes downloading at low
   priority and every later document paints Gotham from cache. Wrong
   font beats moving text; that ranking is the doctrine's, made once. */
@font-face {
  font-family: 'Gotham';
  src:
    url('/static/fonts/Gotham-Light.woff2') format('woff2'),
    url('/static/fonts/Gotham-Light.ttf') format('truetype');
  font-weight: 300;
  font-style: normal;
  font-display: optional;
}
@font-face {
  font-family: 'Gotham';
  src:
    url('/static/fonts/Gotham-Book.woff2') format('woff2'),
    url('/static/fonts/Gotham-Book.ttf') format('truetype');
  font-weight: 400;
  font-style: normal;
  font-display: optional;
}
@font-face {
  font-family: 'Gotham';
  src:
    url('/static/fonts/Gotham-Medium.woff2') format('woff2'),
    url('/static/fonts/Gotham-Medium.ttf') format('truetype');
  font-weight: 500;
  font-style: normal;
  font-display: optional;
}
@font-face {
  font-family: 'Gotham';
  src:
    url('/static/fonts/Gotham-Bold.woff2') format('woff2'),
    url('/static/fonts/Gotham-Bold.ttf') format('truetype');
  font-weight: 700;
  font-style: normal;
  font-display: optional;
}

/* --- document base (ex bootstrap reboot subset we actually rely on) */
html,
body,
#app {
  height: 100%;
}
#app {
  /* the app covers the full document: min-width matches the hard 320
     floor; 100vh includes the strip a horizontal scrollbar occupies —
     without it the dark body canvas showed as a band below the page
     (round 18) */
  min-width: 320px;
  min-height: 100vh;
}
body {
  margin: 0;
  background-color: var(--color-ink);
  /* the exact production stack (per-element audit compares the string) */
  font-family: Gotham, -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto,
    Oxygen, Ubuntu, Cantarell, 'Fira Sans', 'Droid Sans', 'Helvetica Neue',
    Arial, sans-serif;
  font-size: 16px;
  font-weight: 300;
  line-height: 1.5;
  color: var(--color-text);
}
/* form controls inherit the document font like the legacy reboot did —
   without this they fall back to Arial/monospace (audit finding 2026-07-13) */
button,
input,
optgroup,
select,
textarea {
  margin: 0;
  font-family: inherit;
  font-size: inherit;
  font-weight: inherit;
  line-height: inherit;
}
b,
strong {
  /* production computes 500, not the browser's bolder→700 */
  font-weight: 500;
}
small {
  font-size: 80%;
  font-weight: 400;
}
* ,
*::before,
*::after {
  box-sizing: border-box;
}
a {
  color: var(--color-accent);
  text-decoration: none;
}
img {
  max-width: 100%;
  vertical-align: middle;
}
h1, h2, h3, h4, h5, p, ul, figure {
  margin: 0 0 8px;
}
/* weight only on headings — on ul it broke the inherited 500 of the
   mobile value-box cells (reference bolds those values). line-height 1.1
   is the bootstrap-reboot heading value the reference computes. */
h1, h2, h3, h4, h5 {
  font-weight: 300;
  line-height: 1.1;
}
/* THE STRONG TONE IS THE HEADINGS' AND THE CODE BLOCKS' (D-254): an h1–h3
   on a light ground and a block of code are --color-text-strong; the body
   around them is --color-text. A heading on a dark ground takes its
   ground's light text instead (kit-film.css, kit-login.css). */
h1, h2, h3,
pre {
  color: var(--color-text-strong);
}
h1 { font-size: 40px; line-height: 44px; }
h2 { font-size: 32px; }
h3 { font-size: 28px; }
h4 { font-size: 24px; }
h5 { font-size: 20px; }
button {
  font-family: inherit;
}
fieldset {
  min-width: 0;
  padding: 0;
  margin: 0;
  border: 0;
}
table {
  border-collapse: collapse;
}
label {
  margin-bottom: 8px;
  display: inline-block;
}

/* --- centered container (production bootstrap-alpha ladder) */
.fs-container {
  width: 100%;
  margin-right: auto;
  margin-left: auto;
  padding-right: var(--fs-page-inset-mobile);
  padding-left: var(--fs-page-inset-mobile);
}
/* round 20: the ladder rides the unified breakpoint — mobile keeps
   production's 576 cap, the desktop tiers (940/1140) start at X1;
   the old 720 tier sat between the retired 768 and 992 steps and is
   unreachable under the unified model */
@media (min-width: 544px) { .fs-container { max-width: 576px; } }
@media (min-width: 927px) { .fs-container { max-width: 940px; } }
@media (min-width: 1200px) { .fs-container { max-width: 1140px; } }
/* full-width variant with the page gutter (ex container-fluid).
   ROUND 16 (supersedes round 15's single edge), re-homed to the
   unified X1 in rounds 19/20: above it the desktop 32px edge, below
   it the legacyref-extracted 15px mobile edge; no further margin
   steps at any width on either side. */
.fs-container-fluid {
  width: 100%;
  padding-right: var(--fs-page-inset);
  padding-left: var(--fs-page-inset);
}
@media (max-width: 926px) {
  .fs-container-fluid {
    padding-right: var(--fs-page-inset-mobile);
    padding-left: var(--fs-page-inset-mobile);
  }
}

/* --- the scrolling pane (ex .content): keep-alive scroller under the
       fixed header; the transparent variant lets the dark body back the
       film-detail hero AND macOS elastic overscroll */
.app-pane {
  position: relative;
  z-index: 2;
  flex: 1;
  height: 100%;
  width: 100%;
  overflow-y: scroll;
  overflow-x: hidden;
  padding: var(--fs-pane-pad-top) 0 0;
  margin-bottom: -24px;
  background-color: var(--color-surface);
}
.app-pane--transparent {
  background: none;
}

/* --- buttons (production .btn: 10px 16px, uppercase, w500, radius 0) */
.fs-btn {
  display: inline-block;
  padding: 10px 16px;
  border: none;
  border-radius: 0;
  font-size: 14px;
  font-weight: 500;
  line-height: 1.25;
  text-transform: uppercase;
  text-align: center;
  vertical-align: middle;
  white-space: nowrap;
  cursor: pointer;
  background: transparent;
  color: var(--color-text);
  /* legacy .btn carried an 8px bottom margin everywhere */
  margin-bottom: 8px;
}
.fs-btn--primary {
  background-color: var(--color-accent);
  color: var(--color-surface-soft);
}
.fs-btn--primary:hover {
  background-color: #0e6cab;
  color: var(--color-surface-soft);
}
.fs-btn--success {
  background-color: var(--color-action-success);
  color: var(--color-surface-soft);
}
.fs-btn--success:hover {
  background-color: #4cae4c;
  color: var(--color-surface-soft);
}
.fs-btn--danger {
  background-color: var(--color-danger);
  color: var(--color-surface-soft);
}
.fs-btn--danger:hover {
  background-color: #b00217;
  color: var(--color-surface-soft);
}
.fs-btn--sm {
  padding: 8px 10px;
  font-size: 12px;
  line-height: 15px;
}
.fs-btn--link {
  /* legacy .btn-link keeps the .btn 14/500/uppercase; only surface and
     paddings reset (reference: deliver BACK / SHOW ITEMS, 17.5px tall) */
  background: transparent;
  color: var(--color-accent);
  padding: 0;
  margin-bottom: 0;
}
.fs-btn:disabled,
.fs-submit--blocked {
  /* THE disabled look — ONE definition (2026-07-28: the class variant
     joined the existing :disabled register for GuardedSubmit, whose
     button stays CLICKABLE while blocked so the bubble can explain;
     CREATE ORDER's old inline utilities carried these same values). */
  opacity: 0.65;
}
/* ...but the CURSOR splits (D-111 part 4 correction, item 2): a truly
   disabled button is INERT — default cursor, no hand, no promise. The
   blocked submit keeps not-allowed because its click still fires and
   explains. */
.fs-btn:disabled {
  cursor: default;
}
.fs-submit--blocked {
  cursor: not-allowed;
}
/* blocked ≠ disabled: the click still fires, but hover must not react
   either — pin the resting surface (both consumers are accent submits) */
.fs-submit--blocked:hover {
  background-color: var(--color-accent);
  color: var(--color-surface-soft);
}

/* --- data table (production .table impression: uppercase bold headers,
       14px/300 cells, hairline row separators drawn by row borders) */
.fs-table {
  width: 100%;
  max-width: 100%;
  margin-bottom: 16px;
  border-collapse: collapse;
  /* production: the table inherits the 16px document font; only th/td set
     14px — content outside cells (group headings) renders at 16px */
  font-size: 16px;
  line-height: 24px;
}
.fs-table th {
  padding: 12px 8px;
  /* font-size lives once in kit-tables.css (.fs-table th = 0.875rem =
     14px); the redundant 14px copy here was deleted 2026-07-27 (D-041). */
  font-weight: 700;
  line-height: 21px;
  text-transform: uppercase;
  text-align: left;
  vertical-align: bottom;
  color: var(--color-text);
}
.fs-table td {
  /* bootstrap base 0.75rem narrowed by the stack rule; the transfers
     table overrides to 0.35rem 0.5rem in kit-tables */
  padding: 12px 8px;
  vertical-align: top;
  /* font-size: single source in kit-tables.css (.fs-table td = 0.875rem
     = 14px); redundant 14px copy deleted 2026-07-27 (D-041). */
  line-height: 21px;
  font-weight: 300;
}

/* --- panel: ONE definition lives in kit-forms.css (the form/system
   surface — forms own it). This kit.css copy was deleted 2026-07-27
   (D-041): it duplicated .fs-panel background-color across files, the
   silent cross-file override pattern. */

/* --- text input (production .form-control impression on white) */
.fs-input {
  display: block;
  width: 100%;
  /* KIT variant: pre-consolidation geometry restored (verdict);
     horizontal inset = THE token */
  padding: var(--fs-input-pad-y) var(--fs-control-inset);
  font-size: var(--fs-input-font-size);
  font-weight: var(--fs-control-font-weight);
  line-height: 20px;
  color: var(--color-text);
  background-color: var(--color-surface);
  border: 1px solid var(--color-line);
  border-radius: 0;
  outline: none;
}
/* dark variant (header search: gray field, light text) */
/* KIT variant: production nav geometry restored (verdict). */
.fs-input--dark {
  min-height: var(--fs-search-height);
  padding: var(--fs-search-pad-y) var(--fs-control-inset);
  border: none;
  background-color: var(--fs-search-ground);
  color: var(--color-surface-soft);
  font-weight: 400;
  line-height: 16px;
}
/* A PLACEHOLDER IS ITS GROUND'S TEXT COLOUR (D-254; solid on a light ground
   since D-256, Tom 2026-10-17). Chrome's own default is an opaque #757575, a
   grey of its own, so no field is left to it: a light field's placeholder is
   --color-text, SOLID — the tone of the selects beside it in a filter bar,
   so a bar reads uniform (opacity 1 also overrides Firefox's own 0.54) —
   and the dark search field's is its own light text at the muted opacity,
   bootstrap-alpha's .form-control::placeholder, which the reference
   computes as the input's colour at 0.54. */
::placeholder {
  color: var(--color-text);
  opacity: 1;
}
.fs-input--dark::placeholder {
  color: inherit;
  opacity: var(--fs-muted-text-opacity);
}

/* --- icon metrics: every icon is a faGlyphs.ts outline (FA 4.7's, and the
   transfers list's type glyphs drawn as strokes);
   fs-icon--fa is the operative sizing (height-true 1em like the font
   glyph, baseline at -0.143em = the font's 256/1792 descent) --- */
.fs-icon {
  display: inline-block;
  width: 1.2em;
  height: 1.2em;
  vertical-align: -0.245em;
  flex-shrink: 0;
}
/* exact-FA-outline icons (faGlyphs.ts): height-true to 1em like the font
   glyph they replicate; the font's descent puts the baseline at -0.143em */
.fs-icon--fa {
  width: 1em;
  height: 1em;
  vertical-align: -0.143em;
}
.fs-icon--fw {
  width: var(--fs-icon-fw-width);
}
/* THE FILM PAGE'S FONT AWESOME 7 ICONS (D-295, Tom; Icon `cap`): the
   element is the glyph's ink, the width its own aspect. An action's glyph
   carries the height and the baseline offset of the FA 4.7 glyph it
   replaces on master (faGlyphs `metrics`, set inline); without them — the
   padlock — it stands as high as the capitals of its type, centred on
   them. Its spacing is its row's (no margin of its own). */
.fs-icon.fs-icon--cap {
  --icon-ratio: 1;
  --icon-h: var(--fs-cap-height);
  --icon-rise: calc((var(--fs-cap-height) - var(--icon-h)) / 2);
  width: calc(var(--icon-h) * var(--icon-ratio));
  height: var(--icon-h);
  vertical-align: var(--icon-rise);
  margin: 0;
}
.fs-icon--lg {
  /* legacy body .icon-lg: font-size 20px in a 25px line (rows sized to
     36.19px in the admin tables) */
  width: 20px;
  height: 20px;
  vertical-align: -0.25em;
  margin-top: -2px;
  margin-bottom: -2px;
}
/* THE WORKING MARK TURNS (D-258, components/StatusIcon): a short arc on a
   faint track around fa-dot-circle-o's standing dot, clockwise, 1.2 s per
   revolution, linear — a transform animation on the element itself,
   composited, no timer and no layout; the dot and the track sit on the
   axis, so turning the element turns the arc alone to the eye. It stands
   still for a reader who asked for less motion. */
@keyframes fs-spin {
  to {
    transform: rotate(360deg);
  }
}
.fs-icon--spin {
  animation: fs-spin 1.2s linear infinite;
  transform-origin: 50% 50%;
  will-change: transform;
}
@media (prefers-reduced-motion: reduce) {
  .fs-icon--spin {
    animation: none;
  }
}

/* --- app header (extracted: two dark bars, fixed, z 20) --- */
.app-header {
  position: fixed;
  top: 0;
  left: 0;
  right: 0;
  z-index: 20;
  /* fixed positioning tracks the VIEWPORT, so body's min-width cannot
     hold it — the round-17 gap (round 18): clamp the header itself */
  min-width: 320px;
}
/* ROUND 14 (Tom's spec, replaces production-matching for the header):
   ONE header styling at every width — same type, same icons, same
   paddings, one meta height and one nav height, no breakpoint jumps.
   The only responsive rule the header owns is the email cutoff. */
.app-navbar-meta {
  position: relative;
  z-index: 30;
  display: flex;
  align-items: center;
  height: 57.5px;
  padding: 0 32px;
  background-color: var(--color-ink);
}
.app-navbar-main {
  /* no right padding: the search field runs flush to the window edge */
  padding-left: 32px;
  padding-right: 0;
}

.app-navbar-main {
  position: relative;
  display: flex;
  align-items: stretch;
  height: 48px;
  background-color: rgba(77, 77, 77, 0.9);
}
.app-customer {
  display: inline-block;
  flex-shrink: 0;
  /* G.8: a long company name TRUNCATES; it never disappears, never
     wraps, never pushes the layout. Hand-set caps per REGISTERED
     breakpoint (md 927 / lg 1547 below), no runtime measurement — the
     collapse hook uses the same three numbers. */
  max-width: 120px;
  overflow: hidden;
  text-overflow: ellipsis;
  padding: 20px 16px 20px 0;
  color: var(--color-surface-soft);
  font-size: 14px;
  font-weight: 500;
  line-height: 17.5px;
  text-transform: uppercase;
  white-space: nowrap;
  /* the divider next to the customer name: production puts a subtle
     1px #4d4d4d border-right here (audit 2026-07-13), not a var(--color-text)
     border-left on the brand */
  border-right: 1px solid rgb(77, 77, 77);
}
@media (min-width: 927px) {
  .app-customer {
    max-width: 240px;
  }
}
@media (min-width: 1547px) {
  .app-customer {
    max-width: 320px;
  }
}
.app-brand {
  display: inline-block;
  /* round 16: renders whole or not at all (the runtime collapse hides
     it) — round 12's ellipsizing removed */
  white-space: nowrap;
  flex-shrink: 0;
  padding: 20px 16px;
  color: var(--color-surface-soft);
  font-size: 14px;
  font-weight: 300;
  line-height: 17.5px;
  text-transform: uppercase;
}
.app-nav-link {
  display: flex;
  align-items: center;
  min-height: 48px;
  padding: 16px;
  color: var(--color-surface-soft);
  font-size: 14px;
  font-weight: 500;
  line-height: 14px;
  text-transform: uppercase;
}
/* G.2: the film-detail tabs (THEATRICAL / HOMEVIDEO) take the
   MAIN MENU's hover — the same rule, not a copy of its values. */
.app-nav-link:hover,
.fd-tab:hover {
  /* production: the blue lands already on hover (extracted: bg
     rgb(17,131,207), text stays var(--color-surface-muted), no transition) — round 11 */
  background-color: var(--color-accent);
  color: var(--color-surface-soft);
}
.app-nav-link--active {
  background-color: var(--color-accent);
  color: var(--color-surface-soft);
}
/* THE CLICK IS ACKNOWLEDGED, THE SCREEN IS NOT CLAIMED (D-068).
   The highlight says "this is what you are looking at" and may only move
   when the surface does. A click still has to answer at once, so it gets
   its own state on the entry that was CLICKED, while --active stays where
   the reader still is. Deliberately not the accent fill: the two must not
   be mistaken for each other, which is the whole reason the highlight was
   not allowed to move early. */
.app-nav-link--pending {
  background-color: color-mix(in srgb, var(--color-accent) 30%, transparent);
  color: var(--color-surface-soft);
}
.app-toggler {
  flex: 0 0 auto;
  display: flex;
  align-items: center;
  /* flush at the shared 32px edge (round 15) — the nav bar's own
     padding provides the offset; the box is 52.6px wide */
  padding: 0;
  border: none;
  background: transparent;
  color: var(--color-surface-soft);
  cursor: pointer;
}
.app-toggler-box {
  display: inline-flex;
  align-items: center;
  padding: 16px;
}
.app-toggler--open .app-toggler-box {
  background-color: var(--color-accent);
}
/* mobile burger dropdown (opaque per D-005) */
.app-nav {
  display: flex;
  flex: 1;
  align-items: stretch;
}
/* Mobile burger STRUCTURE only (justified survivor: which nav variant
   renders — tabs vs burger — is structure, not styling; closed heights
   are identical). Open-menu structure extracted from production at a
   burger width: solid opaque OVERLAY (content does not move), items
   48px tall with ZERO gaps and equal widths (the active highlight
   spans exactly the item width), first item 16px below the bar. The
   burger-view search constant lives here too (round 15: the search
   width may change only at this breakpoint). */
@media (max-width: 926px) {
  /* the master breakpoint switches margins with the layout (round 16) */
  .app-navbar-meta {
    padding: 0 var(--fs-page-inset-mobile);
  }
  .app-navbar-main {
    position: relative;
    height: 48px;
    padding-left: var(--fs-page-inset-mobile);
  }
  .app-toggler { order: 1; }
  /* G3.3: the field keeps THE width in the mobile layout too and gives way
     only for the hamburger. THE GAP IS THE HARD CONSTRAINT AT EVERY WIDTH
     (reviewer 2026-07-30): a width FLOOR would win over max-width in the
     cascade (min-width beats max-width by spec), and at 320px that is
     exactly what collapsed the gap to 0.5px — the field jumped into the
     hamburger at the very end of the curve. There is no floor any more:
     the field is THE width, capped by what is left beside the hamburger,
     so the curve is continuous and the gap holds everywhere.
     min-width 0 is what lets a flex item shrink past its content. */
  .app-navbar-main .app-search {
    order: 2;
    flex: 0 1 var(--fs-search-width);
    min-width: 0;
    max-width: calc(
      100% - var(--fs-search-toggler) - var(--fs-search-gap-min)
    );
  }
  .app-nav { display: none; }
  .app-nav--open {
    display: block;
    position: absolute;
    top: 100%;
    left: 0;
    right: 0;
    z-index: 40;
    background-color: rgb(77, 77, 77);
    padding: 16px var(--fs-page-inset-mobile);
  }
  .app-nav--open .app-nav-link {
    width: 100%;
    height: 48px;
    padding: 16px;
  }
}

/* --- header dropdown menus (extracted .dropdown-menu impression) --- */
.app-menu-toggle {
  display: inline-flex;
  align-items: center;
  /* height comes from padding + line-height like production (57.5px
     desktop, 55px mobile via the smaller type) — a fixed 57.5px here
     was the round-13 overflow cause at the mobile bar */
  padding: 20px 16px;
  border: none;
  background-color: transparent;
  color: var(--color-surface-soft);
  font-size: 14px;
  font-weight: 300;
  line-height: 17.5px;
  cursor: pointer;
}
/* :last-of-type doubles beat the ported global
   `.fs-icon:last-of-type { margin-right: 0 }` (kit-film.css). Production's
   fa-fw box (18px incl. its 8px padding) already contains the gap — no
   extra margin, or the toggles run 8px wider than production. */
.app-menu-toggle .fs-icon,
.app-menu-toggle .fs-icon:last-of-type {
  margin-right: 0;
}
/* THE FIXED REGION LABEL (D-277 Round B, rule 2): an account holding one
   region gets the globe and its code where the pulldown toggle sits — the
   toggle's own box and type, nothing to open, no caret. */
.app-region-fixed {
  display: inline-flex;
  align-items: center;
  padding: 20px 16px;
  color: var(--color-surface-soft);
  font-size: 14px;
  font-weight: 300;
  line-height: 17.5px;
}
.app-region-fixed .fs-icon,
.app-region-fixed .fs-icon:last-of-type {
  margin-right: 0;
}
/* bootstrap-style solid dropdown caret (production: ~4.2px triangle, not a
   14px chevron glyph) */
.app-caret {
  display: inline-block;
  width: 0;
  height: 0;
  margin-left: var(--fs-caret-gap);
  vertical-align: middle;
  border-top: var(--fs-caret-size) solid;
  border-right: var(--fs-caret-size) solid transparent;
  border-left: var(--fs-caret-size) solid transparent;
}
.app-menu-toggle[aria-expanded='true'] {
  background-color: rgb(77, 77, 77);
}
/* Dropdown anchor (round 19, seam fix): the wrapper stretches to the
   FULL meta-bar height (the toggle stays centered inside), so the
   panel's top: 100% is exactly the bar's bottom edge. Anchoring the
   panel to the toggle's own box let the nav bar bleed through in a
   1.8px strip whenever the collapsed (icon-only) toggle was shorter
   than the bar and got flex-centered. */
.app-menu-wrap {
  position: relative;
  align-self: stretch;
  display: inline-flex;
  align-items: center;
}
.app-menu {
  position: absolute;
  top: 100%;
  right: 0;
  z-index: 2000;
  min-width: 160px;
  padding: 5px 0;
  background-color: rgb(77, 77, 77);
  text-align: left;
}
/* THE REGION MENU — PRODUCTION'S LOOK (Tom's addition after the
   authorisation round, 2026-10-28, replacing the second review's item 5,
   the third review's item 3 and the dev review's finding 7 as built): the
   panel hangs below the trigger on its right edge like every panel here,
   its entries left-aligned with the panel's own padding (16px, as
   production's), neither right-aligned nor fitted to the widest entry —
   somewhat narrower than production's 160px minimum, by eye. What stays
   from the round: the regions first and All last, and no gap above the
   first entry (the 5px paddings are the user menu's). */
.app-menu--fit {
  min-width: 144px;
  padding: 0;
}
.app-menu-item {
  display: block;
  width: 100%;
  padding: 8px 32px 8px 16px;
  color: var(--color-surface-soft);
  font-size: 14px;
  font-weight: 400;
  line-height: 21px;
  white-space: nowrap;
  text-align: left;
  border: none;
  background: transparent;
  cursor: pointer;
}
.app-menu-item:hover {
  color: var(--color-surface-soft);
  background-color: var(--color-ink);
}
/* Stacked icon-column label lead (SHARED — user menu, /contact card):
   every label starts at ONE x = the column edge (MarkIcon axis) +
   GAP_ICON. GAP_ICON arrives as --mk-gap (fed from the registry on the
   column container) — the SAME "following element carries the gap" token
   the deliver-tree name cell and the film-detail column use; no
   page-local value, no per-item gap. */
.mk-col-label {
  padding-left: var(--mk-gap);
}
/* A label that runs to a SECOND line (the /contact address). Inline
   padding applies to the first line box only, so a wrapped line would
   start back under the glyph; as its own box every line starts at the
   text column — the same x, from the same --mk-gap, with no second
   value to keep in step. */
.mk-col-label--lines {
  display: inline-block;
  vertical-align: top;
}
.app-menu-divider {
  height: 1px;
  margin: 8px 0;
  background-color: rgb(229, 229, 229);
  opacity: 0.25;
}

/* --- header search (dark field + magnifier addon + results) --- */
/* G3.1: THE FOOTER IS A PAGE'S CLOSING BAND, NEVER A PAGE — one rule, for
   EVERY page, in one home.
   While a route is still loading (or renders something out of flow, like
   the map's absolutely-positioned canvas), the pane's content is empty and
   the footer moved up under the nav bar: the dark claim band standing in
   for the page. The first attempt gave the outlet's FIRST CHILD a
   min-height, which missed exactly those two cases — an out-of-flow first
   child creates no flow height, and a page that renders several siblings
   only stretched the first one. The pane owns it now: the closing band
   sits at the BOTTOM of the pane's box whatever the page does, and no
   router state or timing is involved. */
.app-pane {
  display: flex;
  flex-direction: column;
}
.app-pane > footer {
  margin-top: auto;
}
/* THE PAGE AREA — one rule, three guarantees (J0, after the D-048 rule
   broke two of them).

   1  THE BOX IS NEVER SHORTER THAN THE PAGE. This is what went wrong: the
      pane is a flex column with a definite height, so this box is a flex
      item, and a flex item SHRINKS by default. It was being squeezed down
      to its own min-height — measured at exactly 100vh on a film detail
      whose content was 1304px and on /films whose grid was 246121px — and
      the closing band, sitting right after that clamped box, landed on top
      of the page. `flex: none` is the fix: the box is its content, always.
   2  AND NEVER SHORTER THAN THE PAGE AREA. A screenful MINUS what the pane
      has already spent on its top padding AND minus the band itself — so
      on a SHORT page the band is ON SCREEN at the bottom of the first
      viewport, without scrolling, which is where production puts it (K0;
      H3 stopped one band short of that and left it just under the fold).
      On a long page it simply follows the content.
   3  WHICH IS WHY THE BAND CAN NEVER BE WRONG. It has exactly two
      legitimate places: directly after the content, or at the bottom of
      the viewport. It can never be ABOVE both — which is what "over the
      page" and "mid-page" meant. A pane whose page is still loading, or
      whose page renders out of flow (the map's canvas), still has a full
      page area, so the band is at the fold from the first frame and never
      higher. No router state and no timing is involved.

   The inner flex column is what lets a full-bleed page (the map) take the
   whole height. */
.app-pane-content {
  display: flex;
  flex-direction: column;
  flex: none;
  min-height: calc(100vh - var(--fs-pane-pad-top) - var(--fs-footer-band));
}

.app-search {
  position: relative;
  display: flex;
  /* ONE width, never fluid (rounds 15/16; G3.3 dropped the separate
     mobile value): the field is --fs-search-width in both layouts, and in
     the mobile layout it shrinks only as far as the hamburger's minimum
     gap requires. */
  flex: 0 0 var(--fs-search-width);
  margin-left: auto;
}
.app-search-addon {
  display: flex;
  align-items: center;
  /* production input-group-addon: 16px left, 8px right (42px with the
     18px fa-fw glyph box); z-index lifts it above the results backdrop —
     without it the dim overlay darkened just the addon cell */
  padding: 0 8px 0 16px;
  position: relative;
  z-index: 10;
  background-color: var(--fs-search-ground);
  color: var(--color-surface-soft);
  font-size: 14px;
}
.app-search-addon .fs-icon,
.app-search-addon .fs-icon:last-of-type {
  margin-right: 0;
}
/* THE HEADER'S PANEL IS THE APP'S ONE SUGGESTION PANEL (D-191, owner's
   second review): .fs-combobox-dropdown, the filter bar's element
   (app.css) — flush, borderless, shadowless, no padding, its scrolling
   contained. What stood here until then was production's
   ul.typeahead__list carried over: 2px below the bar, a 1px #ccc
   border, 5px above the first row and below the last — the legacy
   dropdown look, on the one panel that had not been brought under the
   filter-bar rules. The rows below keep their own skin. */
/* THE HEADER VARIANT of the one list (SuggestionList variant="header",
   Tom's ruling of 2026-11-08): the list as master shows it — master's
   ground, text colour and highlighted row, from these tokens — and exactly
   the search field's width. Where it sits and the page's stillness are the
   one list's.
   THE RECIPIENTS VARIANT (variant="recipients", Tom's ruling, D-294: the
   second named exception): the screener grant's recipient list keeps the
   look it had before the one list (2ae2bc09, whose parent drew
   .screener-recipients-dropdown on these two tokens) — this ground and
   text colour instead of its white field's, its rows' highlight theirs
   (kit-port .screener-recipients-*). Its place, width and type are the one
   list's. */
.fs-combobox-dropdown--header,
.fs-combobox-dropdown--recipients {
  background: var(--color-surface-muted);
  color: var(--color-text);
}
/* rows: 16px on a normal line, hover var(--color-line-strong). The title
   reads in --color-ink, resting and hovered, as it did before D-254 (D-256
   repair); the year and the other titles stay the body tone. */
.app-search-result {
  display: block;
  padding: 6px 12px;
  color: var(--color-ink);
  font-size: 16px;
  font-weight: 400;
  line-height: normal;
  cursor: pointer;
  /* D-191: a long title or subline WRAPS onto a further line — the
     panel keeps its one width and nothing is cut with an ellipsis */
  overflow-wrap: anywhere;
}
.app-search-result:hover,
.app-search-result--active {
  background-color: var(--color-line-strong);
  color: var(--color-ink);
}
/* D-191: the row is a miniature of the film header — the title as
   stored (never uppercased), the year one fixed gap after it in the
   subline's small muted type (two films are called "Renoir"), the other
   titles small beneath. */
.app-search-result-title {
  text-transform: none;
}
.app-search-result-year {
  margin-left: 8px;
  font-size: 12px;
  font-weight: 400;
  color: var(--color-text);
}
.app-search-result-sub {
  font-size: 12px;
  font-weight: 400;
  line-height: normal;
  color: var(--color-text);
}

/* --- film grid (ex .movielist-*, ported from _movielist.scss) --- */
.film-grid {
  display: flex;
  flex-wrap: wrap;
  /* G.12: the grid is WINDOWED — the spacers above and below the rendered
     rows change height as the window moves. Chrome's scroll anchoring
     "helpfully" compensates for that by moving the scroll offset, which
     silently dragged a restored position away (measured: a restore landed
     exactly on 6000px and was then pulled to 4982px). The app owns the
     offset here; the browser must not adjust it. */
  overflow-anchor: none;
  /* M4M/O2a+b: THE GRID'S OUTER EDGE IS THE PAGE'S CONTENT EDGE. The
     tiles carry an 8px gutter each side (16 between neighbours), so the
     grid has to start exactly one gutter OUTSIDE the content box for the
     first card to land on it — and end one gutter outside on the right,
     for the last one. The old -15/+8 pair came from a Bootstrap row and
     matched neither edge: the grid box hung 15px past the content edge
     on the left and 7px on the right, while the cards themselves sat 1px
     inside at both ends. Cards now span the content box exactly, which
     is also the size increase — the row has 16px more to divide. */
  padding: 0;
  margin: 0 calc(var(--fs-grid-gutter) * -1);
  /* containment: memory/resize (PART C). The tiles' content-visibility
     went in D-228's inventory round — see .film-tile */
  contain: layout style;
}
/* round 22 (D-027): the films content sits the SAME extracted 51.5px
   off the bar as the transfers table. The full 51.5 is set here: it
   COLLAPSES with the grid's own 18px internal margin (max wins). */
#content-films .fs-filterbar-section + .fs-container-fluid {
  margin-top: 51.5px;
}
.film-grid-title {
  flex: 0 0 100%;
  margin: 24px 0 16px;
  /* M4T/O8: THE HEADING STARTS WHERE THE COVERS START. It spans the grid
     full-width, and the grid hangs one tile gutter outside the content
     box on each side so that the CARDS land on it (M4M/O2) — so the
     heading and the rule above it inherited that overhang and ran 8px
     into the page margin at every band, while the covers under them were
     correct. Putting the gutter back here is the whole fix: the rule now
     begins on the cover's outer edge and ends on the content edge. */
  padding: 0 var(--fs-grid-gutter);
}
.film-grid-title-heading {
  /* a group's title on /films: the headings' strong tone (D-254) */
  color: var(--color-text-strong);
  font-size: 20px;
  padding: 16px 0 8px;
  border-top: 2px solid var(--color-line-strong);
  margin: 0;
}
/* Windowed grid (list round): the spacers that stand in for the rows
   outside the window. Full-width flex items, so the wrap pattern of the
   visible rows is exactly the wrap pattern of the full list. */
.film-grid-pad {
  flex: 0 0 100%;
}
.film-grid-offscreen {
  width: 100%;
}
.film-tile {
  width: 50%;
  padding: 0 var(--fs-grid-gutter);
  /* NO content-visibility (D-228, the lists inventory; Tom's ruling,
     2026-09-30). The tiles carried `content-visibility: auto` with a
     420px intrinsic placeholder — a second guess beside the planner's
     computed row (365.5 at 1440, 369.3 at 1920), and the one that was
     wrong: a tile never drawn stood 420 tall until it was, so scrolling
     UP through such rows (after a restored position) moved the content
     by ~54px a row while the offset stood still — measured, 55 jumps and
     2 996 px in ten seconds at 1440. The grid's own windowing bounds the
     DOM, so there is no second guess left. */
}
@media (min-width: 600px) { .film-tile { width: 33.3333%; } }
@media (min-width: 800px) { .film-tile { width: 25%; } }
@media (min-width: 960px) { .film-tile { width: 20%; } }
@media (min-width: 1200px) { .film-tile { width: 16.6667%; } }
@media (min-width: 1500px) { .film-tile { width: 14.2857%; } }
@media (min-width: 1900px) { .film-tile { width: 12.5%; } }
@media (min-width: 2200px) { .film-tile { width: 11.1111%; } }
@media (min-width: 2500px) { .film-tile { width: 10%; } }
@media (min-width: 2800px) { .film-tile { width: 9.0909%; } }
@media (min-width: 3100px) { .film-tile { width: 8.3333%; } }
.film-card {
  position: relative;
  display: block;
  margin-bottom: 16px;
}
/* M4O: THE COVER'S FRAME IS THE COVER'S OUTER EDGE.
   There were two rings: this box carried 2px of --color-surface
   (#ffffff, invisible on a white page) and the image inside it carried
   2px of --color-line-strong (#d9d9d9), which is the grey frame a
   reader sees. So the box measured 32 — the page inset — while the
   first painted pixel was at 34, and the cover read as indented by 2px
   against the FILMS tab and the distributor pulldown. Sampled from the
   screenshot, not from the box: tab's first blue pixel at 32, cover's
   first grey pixel at 34.
   ONE ring now, the same grey, the same 2px, on the OUTER box — so the
   frame's outer edge is the cover's box edge and lands on the inset,
   and the image gains the 4px the second ring was taking. Nothing about
   the grid moves; the covers grow into the space they already owned.
   The frame is a BORDER on a border-box element, i.e. drawn inside the
   footprint: turning it blue on selection cannot move anything. */
.film-card-poster {
  position: relative;
  background-color: var(--color-text);
  border: var(--fs-cover-frame) solid var(--color-line-strong);
  /* D-197: THE BOX CARRIES ITS OWN RATIO. It used to take its height
     from a spacer <img> — /static/images/cover.png, 200x285, a fixed URL
     with no cache-control — so a browser holding the pre-40:57 copy
     drew the old, taller tile and a grey strip under the poster. Now
     the ratio is declared here and no cached file can size a tile
     again. On the CONTENT box, deliberately: the spacer was an image
     inside the frame, so the tile's height has always been (inner
     width x 57/40) + the frame, and filmGridGeometry's row formula
     says exactly that; the ratio on the border box would grow every
     row by 1.7px. Whole-number literal, the same 40:57 as
     FILM_COVER_ASPECT (285/200), .fd-poster and the grid skeleton —
     one source gate holds the four to one value. */
  box-sizing: content-box;
  aspect-ratio: 40 / 57;
}
.film-card-poster img {
  width: 100%;
}
/* D-197: the cover fills the box the ratio makes; an off-ratio source is
   centre-cropped, as resize_to_fill crops the variant server-side. */
.film-card-poster .film-card-image {
  height: 100%;
  object-fit: cover;
}
/* M4P: THE SELECTION BAND IS AS THICK AS IT EVER WAS, AND IT GROWS
   INWARD. Before M4O the cover had two rings and both turned blue, so
   the band measured 4px — but it started 2px OUTSIDE the cover's own
   visible edge, on the page-coloured ring, which is the overhang M4M
   objected to. Merging the rings put the edge right and left the band
   at 2px.
   An overlay carries the band now. It is absolutely positioned, so it
   is out of flow and can have no effect on the footprint whatever its
   width; `inset` pulls it out by the ring's width to reach the cover's
   OUTER edge, and its border grows from there inward — over the grey
   ring and the first pixels of the image, which is where Tom asked for
   it. Transparent when unselected, so the grey ring shows through
   unchanged. Not an outline (outlines are drawn outside), not a wider
   border on the poster (that would shrink the image on selection). */
.film-card-poster::after {
  content: '';
  position: absolute;
  inset: calc(var(--fs-cover-frame) * -1);
  border: var(--fs-cover-select) solid transparent;
  pointer-events: none;
  z-index: 1;
}
.film-card:hover .film-card-poster {
  border-color: var(--color-accent);
}
.film-card:hover .film-card-poster::after {
  border-color: var(--color-accent);
}
.film-card-poster .film-card-image {
  position: absolute;
  top: 0;
  left: 0;
}
.film-card-overlay {
  position: absolute;
  top: 0;
  height: 100%;
  width: 100%;
  text-align: center;
}
.film-card-overlay-title {
  position: absolute;
  width: 100%;
  padding: 32px 8px;
  color: var(--color-surface-soft);
}
.film-card-overlay-logo {
  position: absolute;
  left: 20%;
  bottom: 32px;
  width: 60%;
  max-height: 64px;
  margin: 0 auto;
  opacity: 0.8;
}
.film-card-overlay-logo img {
  max-height: 64px;
  border: none;
  width: auto;
  max-width: 100%;
}
/* two-column text row under the poster (title left, count right) */
.film-card-text {
  float: left;
  margin-top: 8px;
  width: calc(100% - 30px);
  color: var(--color-text);
  font-size: 14px;
  line-height: 21px;
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}
/* THE NUMBER IS ALWAYS RIGHT-ALIGNED (the dev review of 2026-10-28,
   finding 6): a right float, so it sits on the card's right edge with or
   without the distributor line on the left. One plain number (Tom's
   second review, item 3): the trailer deliveries under the entry. */
.film-card-count {
  float: right;
  width: 30px;
  margin-top: 8px;
  text-align: right;
  color: var(--color-text);
  font-size: 14px;
  line-height: 21px;
  white-space: nowrap;
  overflow: hidden;
}
.film-card-updated {
  float: left;
  width: 100%;
  color: var(--color-accent);
  text-transform: uppercase;
  font-size: 12px;
  font-weight: 700;
  line-height: 18px;
  /* D-201: the line's space is reserved whether or not there is a date
     — one line, its own line-height, so an empty line is as tall as a
     filled one and every tile is the planner's 63 text block. */
  min-height: 1lh;
}

/* bootstrap-style row/column shims for the ported page grids */
.fs-row {
  display: flex;
  flex-wrap: wrap;
  margin-left: -15px;
  margin-right: -15px;
}
.fs-col {
  padding-left: 15px;
  padding-right: 15px;
  width: 100%;
}

.fs-btn--light {
  background-color: var(--color-surface-muted);
  color: var(--color-text);
}
.fs-btn--light:hover {
  background-color: #e5e5e5;
}
/* bare button (legacy <a class="btn btn-light"> resolved to the base .btn:
   transparent, link-blue text — the film-row PLAY/SCREENER look) */
.fs-btn--bare {
  background-color: transparent;
  color: var(--color-accent);
}

/* type helpers used on dark surfaces (ex display-5 / lead) */
.fs-display {
  font-size: 40px;
  font-weight: 300;
  line-height: 44px;
}
.fs-lead {
  font-size: 20px;
  font-weight: 300;
}
/*! tailwindcss v4.3.3 | MIT License | https://tailwindcss.com */
@layer properties {
  @supports (((-webkit-hyphens: none)) and (not (margin-trim: inline))) or ((-moz-orient: inline) and (not (color: rgb(from red r g b)))) {
    *, :before, :after, ::backdrop {
      --tw-rotate-x: initial;
      --tw-rotate-y: initial;
      --tw-rotate-z: initial;
      --tw-skew-x: initial;
      --tw-skew-y: initial;
      --tw-space-y-reverse: 0;
      --tw-border-style: solid;
      --tw-font-weight: initial;
      --tw-ordinal: initial;
      --tw-slashed-zero: initial;
      --tw-numeric-figure: initial;
      --tw-numeric-spacing: initial;
      --tw-numeric-fraction: initial;
      --tw-shadow: 0 0 #0000;
      --tw-shadow-color: initial;
      --tw-shadow-alpha: 100%;
      --tw-inset-shadow: 0 0 #0000;
      --tw-inset-shadow-color: initial;
      --tw-inset-shadow-alpha: 100%;
      --tw-ring-color: initial;
      --tw-ring-shadow: 0 0 #0000;
      --tw-inset-ring-color: initial;
      --tw-inset-ring-shadow: 0 0 #0000;
      --tw-ring-inset: initial;
      --tw-ring-offset-width: 0px;
      --tw-ring-offset-color: #fff;
      --tw-ring-offset-shadow: 0 0 #0000;
      --tw-outline-style: solid;
      --tw-blur: initial;
      --tw-brightness: initial;
      --tw-contrast: initial;
      --tw-grayscale: initial;
      --tw-hue-rotate: initial;
      --tw-invert: initial;
      --tw-opacity: initial;
      --tw-saturate: initial;
      --tw-sepia: initial;
      --tw-drop-shadow: initial;
      --tw-drop-shadow-color: initial;
      --tw-drop-shadow-alpha: 100%;
      --tw-drop-shadow-size: initial;
      --tw-ease: initial;
      --tw-content: "";
    }
  }
}

@layer theme {
  :root, :host {
    --spacing: .25rem;
    --container-3xl: 48rem;
    --font-weight-light: 300;
    --font-weight-medium: 500;
    --font-weight-bold: 700;
    --ease-out: cubic-bezier(0, 0, .2, 1);
    --ease-in-out: cubic-bezier(.4, 0, .2, 1);
    --default-transition-duration: .15s;
    --default-transition-timing-function: cubic-bezier(.4, 0, .2, 1);
    --breakpoint-md: 927px;
    --breakpoint-lg: 1547px;
    --color-text: #737373;
    --color-text-strong: #474747;
    --color-ink: #333;
    --color-surface: #fff;
    --color-surface-muted: #f2f2f2;
    --color-surface-soft: #f5f5f5;
    --color-line: #f2f2f2;
    --color-line-strong: #d9d9d9;
    --color-accent: #1183cf;
    --color-success: #7ed321;
    --color-danger: #d0021b;
    --color-action-success: #5cb85c;
    --color-overlay: #000000bf;
    --color-scrim: #33333380;
    --color-stage: #1a1a1a;
    --color-clip: #6e6e6e;
    --color-kdm-valid: #76c100;
    --color-kdm-future: #f7cb00;
    --color-kdm-expired: #e00054;
    --color-status-muted: #b2b3b9;
    --color-status-waiting: #d9d9d9;
    --color-surface-pending: #fcf8e3;
    --color-code: #a33333;
    --color-code-surface: #f4f4f4;
    --color-code-border: #e4e4e4;
    --font-sans: Gotham, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto,
    "Helvetica Neue", Arial, sans-serif;
    --font-mono: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;
    --text-xs: 12px;
    --text-sm: 14px;
    --text-sm--line-height: 21px;
    --text-base: 16px;
    --text-base--line-height: 24px;
    --text-display: 40px;
    --text-display--line-height: 44px;
    --spacing-control: 34px;
    --radius-sm: 4px;
  }
}

.pointer-events-none {
  pointer-events: none;
}

.collapse {
  visibility: collapse;
}

.invisible {
  visibility: hidden;
}

.visible {
  visibility: visible;
}

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

.absolute {
  position: absolute;
}

.fixed {
  position: fixed;
}

.relative {
  position: relative;
}

.static {
  position: static;
}

.sticky {
  position: sticky;
}

.inset-0 {
  inset: 0;
}

.top-0 {
  top: 0;
}

.top-2026 {
  top: calc(var(--spacing) * 2026);
}

.bottom-control {
  bottom: var(--spacing-control);
}

.left-0 {
  left: 0;
}

.isolate {
  isolation: isolate;
}

.z-0 {
  z-index: 0;
}

.z-10 {
  z-index: 10;
}

.z-50 {
  z-index: 50;
}

.row-1 {
  grid-row: 1;
}

.float-left {
  float: left;
}

.float-right {
  float: right;
}

.\!container {
  width: 100% !important;
}

@media (min-width: 927px) {
  .\!container {
    max-width: 927px !important;
  }
}

@media (min-width: 1547px) {
  .\!container {
    max-width: 1547px !important;
  }
}

.container {
  width: 100%;
}

@media (min-width: 927px) {
  .container {
    max-width: 927px;
  }
}

@media (min-width: 1547px) {
  .container {
    max-width: 1547px;
  }
}

.m-0 {
  margin: 0;
}

.mt-2 {
  margin-top: calc(var(--spacing) * 2);
}

.mt-4 {
  margin-top: calc(var(--spacing) * 4);
}

.mt-5 {
  margin-top: calc(var(--spacing) * 5);
}

.mt-6 {
  margin-top: calc(var(--spacing) * 6);
}

.mb-2 {
  margin-bottom: calc(var(--spacing) * 2);
}

.mb-3 {
  margin-bottom: calc(var(--spacing) * 3);
}

.mb-4 {
  margin-bottom: calc(var(--spacing) * 4);
}

.mb-6 {
  margin-bottom: calc(var(--spacing) * 6);
}

.mb-8 {
  margin-bottom: calc(var(--spacing) * 8);
}

.mb-10 {
  margin-bottom: calc(var(--spacing) * 10);
}

.mb-11 {
  margin-bottom: calc(var(--spacing) * 11);
}

.mb-12 {
  margin-bottom: calc(var(--spacing) * 12);
}

.ml-2 {
  margin-left: calc(var(--spacing) * 2);
}

.ml-auto {
  margin-left: auto;
}

.block {
  display: block;
}

.contents {
  display: contents;
}

.flex {
  display: flex;
}

.grid {
  display: grid;
}

.hidden {
  display: none;
}

.inline {
  display: inline;
}

.inline-block {
  display: inline-block;
}

.inline-flex {
  display: inline-flex;
}

.table {
  display: table;
}

.table-row {
  display: table-row;
}

.size-20 {
  width: calc(var(--spacing) * 20);
  height: calc(var(--spacing) * 20);
}

.h-control {
  height: var(--spacing-control);
}

.w-1\/3 {
  width: 33.3333%;
}

.w-60 {
  width: calc(var(--spacing) * 60);
}

.w-\[673px\] {
  width: 673px;
}

.w-full {
  width: 100%;
}

.max-w-3xl {
  max-width: var(--container-3xl);
}

.max-w-full {
  max-width: 100%;
}

.min-w-0 {
  min-width: 0;
}

.flex-1 {
  flex: 1;
}

.flex-shrink, .shrink {
  flex-shrink: 1;
}

.grow {
  flex-grow: 1;
}

.table-fixed {
  table-layout: fixed;
}

.border-collapse {
  border-collapse: collapse;
}

.transform {
  transform: var(--tw-rotate-x, ) var(--tw-rotate-y, ) var(--tw-rotate-z, ) var(--tw-skew-x, ) var(--tw-skew-y, );
}

.zoom-8 {
  zoom: 8%;
}

.cursor-pointer {
  cursor: pointer;
}

.resize {
  resize: both;
}

.list-none {
  list-style-type: none;
}

.flex-wrap {
  flex-wrap: wrap;
}

.items-center {
  align-items: center;
}

.items-start {
  align-items: flex-start;
}

.gap-4 {
  gap: calc(var(--spacing) * 4);
}

.gap-6 {
  gap: calc(var(--spacing) * 6);
}

:where(.space-y-1 > :not(:last-child)) {
  --tw-space-y-reverse: 0;
  margin-block-start: calc(var(--spacing) * var(--tw-space-y-reverse));
  margin-block-end: calc(var(--spacing) * calc(1 - var(--tw-space-y-reverse)));
}

.gap-x-3\.5 {
  column-gap: calc(var(--spacing) * 3.5);
}

.truncate {
  text-overflow: ellipsis;
  white-space: nowrap;
  overflow: hidden;
}

.overflow-x-auto {
  overflow-x: auto;
}

.border {
  border-style: var(--tw-border-style);
  border-width: 1px;
}

.border-none {
  --tw-border-style: none;
  border-style: none;
}

.bg-accent {
  background-color: var(--color-accent);
}

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

.bg-surface-muted {
  background-color: var(--color-surface-muted);
}

.bg-transparent {
  background-color: #0000;
}

.p-0 {
  padding: 0;
}

.p-4 {
  padding: calc(var(--spacing) * 4);
}

.p-6 {
  padding: calc(var(--spacing) * 6);
}

.px-4 {
  padding-inline: calc(var(--spacing) * 4);
}

.px-8 {
  padding-inline: calc(var(--spacing) * 8);
}

.py-2\.5 {
  padding-block: calc(var(--spacing) * 2.5);
}

.py-3 {
  padding-block: calc(var(--spacing) * 3);
}

.py-16 {
  padding-block: calc(var(--spacing) * 16);
}

.pt-1 {
  padding-top: var(--spacing);
}

.pb-0 {
  padding-bottom: 0;
}

.pl-0 {
  padding-left: 0;
}

.pl-3 {
  padding-left: calc(var(--spacing) * 3);
}

.text-left {
  text-align: left;
}

.text-right {
  text-align: right;
}

.font-sans {
  font-family: var(--font-sans);
}

.text-base {
  font-size: var(--text-base);
  line-height: var(--tw-leading, var(--text-base--line-height));
}

.text-display {
  font-size: var(--text-display);
  line-height: var(--tw-leading, var(--text-display--line-height));
}

.text-sm {
  font-size: var(--text-sm);
  line-height: var(--tw-leading, var(--text-sm--line-height));
}

.font-bold {
  --tw-font-weight: var(--font-weight-bold);
  font-weight: var(--font-weight-bold);
}

.font-light {
  --tw-font-weight: var(--font-weight-light);
  font-weight: var(--font-weight-light);
}

.font-medium {
  --tw-font-weight: var(--font-weight-medium);
  font-weight: var(--font-weight-medium);
}

.wrap-anywhere {
  overflow-wrap: anywhere;
}

.text-accent {
  color: var(--color-accent);
}

.text-danger {
  color: var(--color-danger);
}

.text-kdm-expired {
  color: var(--color-kdm-expired);
}

.text-kdm-future {
  color: var(--color-kdm-future);
}

.text-kdm-valid {
  color: var(--color-kdm-valid);
}

.text-line {
  color: var(--color-line);
}

.text-line-strong {
  color: var(--color-line-strong);
}

.text-status-muted {
  color: var(--color-status-muted);
}

.text-status-waiting {
  color: var(--color-status-waiting);
}

.text-success {
  color: var(--color-success);
}

.text-surface-muted {
  color: var(--color-surface-muted);
}

.text-surface-soft {
  color: var(--color-surface-soft);
}

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

.text-text-strong {
  color: var(--color-text-strong);
}

.text-transparent {
  color: #0000;
}

.lowercase {
  text-transform: lowercase;
}

.uppercase {
  text-transform: uppercase;
}

.italic {
  font-style: italic;
}

.ordinal {
  --tw-ordinal: ordinal;
  font-variant-numeric: var(--tw-ordinal, ) var(--tw-slashed-zero, ) var(--tw-numeric-figure, ) var(--tw-numeric-spacing, ) var(--tw-numeric-fraction, );
}

.tabular-nums {
  --tw-numeric-spacing: tabular-nums;
  font-variant-numeric: var(--tw-ordinal, ) var(--tw-slashed-zero, ) var(--tw-numeric-figure, ) var(--tw-numeric-spacing, ) var(--tw-numeric-fraction, );
}

.opacity-60 {
  opacity: .6;
}

.opacity-65 {
  opacity: .65;
}

.ring {
  --tw-ring-shadow: var(--tw-ring-inset, ) 0 0 0 calc(1px + var(--tw-ring-offset-width)) var(--tw-ring-color, currentcolor);
  box-shadow: var(--tw-inset-shadow), var(--tw-inset-ring-shadow), var(--tw-ring-offset-shadow), var(--tw-ring-shadow), var(--tw-shadow);
}

.outline {
  outline-style: var(--tw-outline-style);
  outline-width: 1px;
}

.blur {
  --tw-blur: blur(8px);
  filter: var(--tw-blur, ) var(--tw-brightness, ) var(--tw-contrast, ) var(--tw-grayscale, ) var(--tw-hue-rotate, ) var(--tw-invert, ) var(--tw-saturate, ) var(--tw-sepia, ) var(--tw-drop-shadow, );
}

.filter {
  filter: var(--tw-blur, ) var(--tw-brightness, ) var(--tw-contrast, ) var(--tw-grayscale, ) var(--tw-hue-rotate, ) var(--tw-invert, ) var(--tw-saturate, ) var(--tw-sepia, ) var(--tw-drop-shadow, );
}

.transition {
  transition-property: color, background-color, border-color, outline-color, text-decoration-color, fill, stroke, --tw-gradient-from, --tw-gradient-via, --tw-gradient-to, opacity, box-shadow, transform, translate, scale, rotate, filter, -webkit-backdrop-filter, backdrop-filter, display, content-visibility, overlay, pointer-events;
  transition-timing-function: var(--tw-ease, var(--default-transition-timing-function));
  transition-duration: var(--tw-duration, var(--default-transition-duration));
}

.ease-in-out {
  --tw-ease: var(--ease-in-out);
  transition-timing-function: var(--ease-in-out);
}

.ease-out {
  --tw-ease: var(--ease-out);
  transition-timing-function: var(--ease-out);
}

.select-all {
  -webkit-user-select: all;
  user-select: all;
}

.after\:clear-both:after {
  content: var(--tw-content);
  clear: both;
}

.after\:block:after {
  content: var(--tw-content);
  display: block;
}

.after\:content-\[\'\'\]:after {
  --tw-content: "";
  content: var(--tw-content);
}

@media (hover: hover) {
  .hover\:bg-\[\#0e6cab\]:hover {
    background-color: #0e6cab;
  }
}

@media (min-width: 927px) {
  .md\:ml-\[33\.3333\%\] {
    margin-left: 33.3333%;
  }

  .md\:hidden {
    display: none;
  }

  .md\:w-1\/2 {
    width: 50%;
  }

  .md\:w-1\/3 {
    width: 33.3333%;
  }

  .md\:w-1\/4 {
    width: 25%;
  }

  .md\:w-1\/6 {
    width: 16.6667%;
  }

  .md\:w-2\/3 {
    width: 66.6667%;
  }

  .md\:w-3\/4 {
    width: 75%;
  }

  .md\:w-7\/12 {
    width: 58.3333%;
  }
}

@media (min-width: 1547px) {
  .lg\:w-1\/4 {
    width: 25%;
  }
}

:root {
  --fs-login-ground: #000;
  --fs-focus-color: #66afe9;
  --fs-search-ground: #737373;
}

@property --tw-rotate-x {
  syntax: "*";
  inherits: false
}

@property --tw-rotate-y {
  syntax: "*";
  inherits: false
}

@property --tw-rotate-z {
  syntax: "*";
  inherits: false
}

@property --tw-skew-x {
  syntax: "*";
  inherits: false
}

@property --tw-skew-y {
  syntax: "*";
  inherits: false
}

@property --tw-space-y-reverse {
  syntax: "*";
  inherits: false;
  initial-value: 0;
}

@property --tw-border-style {
  syntax: "*";
  inherits: false;
  initial-value: solid;
}

@property --tw-font-weight {
  syntax: "*";
  inherits: false
}

@property --tw-ordinal {
  syntax: "*";
  inherits: false
}

@property --tw-slashed-zero {
  syntax: "*";
  inherits: false
}

@property --tw-numeric-figure {
  syntax: "*";
  inherits: false
}

@property --tw-numeric-spacing {
  syntax: "*";
  inherits: false
}

@property --tw-numeric-fraction {
  syntax: "*";
  inherits: false
}

@property --tw-shadow {
  syntax: "*";
  inherits: false;
  initial-value: 0 0 #0000;
}

@property --tw-shadow-color {
  syntax: "*";
  inherits: false
}

@property --tw-shadow-alpha {
  syntax: "<percentage>";
  inherits: false;
  initial-value: 100%;
}

@property --tw-inset-shadow {
  syntax: "*";
  inherits: false;
  initial-value: 0 0 #0000;
}

@property --tw-inset-shadow-color {
  syntax: "*";
  inherits: false
}

@property --tw-inset-shadow-alpha {
  syntax: "<percentage>";
  inherits: false;
  initial-value: 100%;
}

@property --tw-ring-color {
  syntax: "*";
  inherits: false
}

@property --tw-ring-shadow {
  syntax: "*";
  inherits: false;
  initial-value: 0 0 #0000;
}

@property --tw-inset-ring-color {
  syntax: "*";
  inherits: false
}

@property --tw-inset-ring-shadow {
  syntax: "*";
  inherits: false;
  initial-value: 0 0 #0000;
}

@property --tw-ring-inset {
  syntax: "*";
  inherits: false
}

@property --tw-ring-offset-width {
  syntax: "<length>";
  inherits: false;
  initial-value: 0;
}

@property --tw-ring-offset-color {
  syntax: "*";
  inherits: false;
  initial-value: #fff;
}

@property --tw-ring-offset-shadow {
  syntax: "*";
  inherits: false;
  initial-value: 0 0 #0000;
}

@property --tw-outline-style {
  syntax: "*";
  inherits: false;
  initial-value: solid;
}

@property --tw-blur {
  syntax: "*";
  inherits: false
}

@property --tw-brightness {
  syntax: "*";
  inherits: false
}

@property --tw-contrast {
  syntax: "*";
  inherits: false
}

@property --tw-grayscale {
  syntax: "*";
  inherits: false
}

@property --tw-hue-rotate {
  syntax: "*";
  inherits: false
}

@property --tw-invert {
  syntax: "*";
  inherits: false
}

@property --tw-opacity {
  syntax: "*";
  inherits: false
}

@property --tw-saturate {
  syntax: "*";
  inherits: false
}

@property --tw-sepia {
  syntax: "*";
  inherits: false
}

@property --tw-drop-shadow {
  syntax: "*";
  inherits: false
}

@property --tw-drop-shadow-color {
  syntax: "*";
  inherits: false
}

@property --tw-drop-shadow-alpha {
  syntax: "<percentage>";
  inherits: false;
  initial-value: 100%;
}

@property --tw-drop-shadow-size {
  syntax: "*";
  inherits: false
}

@property --tw-ease {
  syntax: "*";
  inherits: false
}

@property --tw-content {
  syntax: "*";
  inherits: false;
  initial-value: "";
}
/* ==================== THE CONTROL KIT ====================
   Design-system contract (consolidation + reviewer verdict
   2026-07-26): every form-control property is defined ONCE — here as
   tokens/component variants; icon/tree geometry in
   src/features/deliver/treeIconRegistry.ts (sealed D-037). PAGES
   CONSUME, NEVER DEFINE: no padding/height/focus literal on a form
   control outside this contract.
   Verdict state: the kit ARCHITECTURE stands, the consolidation's
   visual deltas are reverted to the pre-consolidation look via the
   named component variants below — with ONE exception: the control
   inset is 16 globally. Out of scope: buttons' inner padding, the
   34px toggle controls. */
:root {
  /* THE inset: inner text inset of every field (reviewer: 16
     everywhere — supersedes the 12px token and the date-field 12) */
  --fs-control-inset: 16px;
  /* TWO AXES, TWO CONSTANTS, TWO HOMES (G2b v2). Both measured off
     Tom's mock (parity/references/homevideo/referenz-richtig.png, a 2x
     capture: rows 80 image px apart, label ink 28 image px past the
     box's paint edge).

     HORIZONTAL — the icon/box -> text distance is GLOBAL: every surface
     that pairs a mark or a box with a label rides it (conversion lists,
     the theatrical tab, the deliver tree's name cell, /transfers, the
     menus, every toggle label seat). Its home is the registry
     (GAP_ICON_TEXT), bridged onto :root at boot; the value below is the
     stylesheet's readable fallback.

     VERTICAL — the pitch is NOT global: it follows the row's CONTENT.
     Only a row with an interactive checkbox takes it (see the consumer
     block below); icon rows keep their own tight rhythm.

     ONE CHECKBOX, APP-WIDE (M4b/O6, corrected by M4c/P1+P2). There were
     two painted sizes in the same family — the base 34 and a compact 29
     — plus a third and fourth in the admin family and a fifth drawn by
     the deliver tree. They are one token.

     M4c REVERSES M4b's choice of value: 34 is the standard, not 29.
     /transfers is the surface that settles it — its rows are built
     around the larger box and shrinking it caused more trouble there
     than the drift it removed.

       --fs-checkbox-size   29 (M4b)  ->  34   (M4c/P1)
       --fs-checkrow-pitch  42 (M4b)  ->  46   (M4c/P2, derived below)
                            46        ->  52   (Tom, 2026-10-28: the form rhythm)
                            52        ->  46   (Tom, 2026-11-01: tight again, forms too)

     THE PITCH IS DERIVED, not hand-set: the visual gap between two
     adjacent checkbox BOXES is one token everywhere, so a row of boxes is
     one box plus one gap tall. Change the box or the gap and the rhythm
     follows. THE GAP IS 12 again since Tom's ruling of 2026-11-01 (D-280:
     the deliver tree's checkbox rows too far apart, forms may be tighter
     too): 46 — box 34 + 12 — for every checkbox list and every form row.
     It was 18 from Tom's addition after the authorisation round
     (2026-10-28: a form row at 46 against production's 54.6 on the user
     form; 52 then), the same one token, global.

     Rows where expanded content or a wrapped second line sits between
     two boxes are the explicit exception (Tom): box-to-box cannot mean
     anything there, and nothing asserts it. */
  --fs-checkbox-size: 34px;
  --fs-checkbox-gap: 12px;
  /* THE ROOM A CHECKBOX LIST KEEPS FOR THE FOCUS RING (the dev review of
     2026-10-28, finding 10): the ring reaches 0.2rem past the box, and the
     compact row pulls its first box 8px up into the list's edge; the list
     pads by this much and pulls itself out by the same, so its boxes stay
     on the column's edge (kit-forms .fs-checkboxes). Measured on the user
     form: 4px left the first box's top 0.2px inside the edge, its ring cut. */
  --fs-check-ring-room: 10px;
  --fs-check-ring-pull: -10px;
  --fs-checkrow-pitch: calc(var(--fs-checkbox-size) + var(--fs-checkbox-gap));
  /* A FORM ROW'S CHECKBOX LIST SHOWS FIVE ROWS (D-286 round 7, the one
     rhythm): five pitches, the ring room above the first box and half a
     gap under the fifth — it ends on a box, so the row below stands one
     gap off it (kit-forms .fs-checkboxes in a form row; 256px before) */
  --fs-checkboxes-height: calc(5 * var(--fs-checkrow-pitch) + var(--fs-check-ring-room) + var(--fs-checkbox-gap) / 2);
  /* M4d/P1 — THE CHAIN GAP. One value on both sides of the box:
     chevron -> box and box -> content. It was 14 (the homevideo mock's
     icon->text distance); the chain ruling supersedes it with 10.
     Bridged from the registry (GAP_ICON_TEXT) at boot — the literal
     below is the stylesheet's readable fallback. Two adjacent status
     MARKS keep GAP_ICON (7.75, sealed): Tom's exception. */
  --fs-checkrow-gap: 10px;
  /* the chevron column = the painted width of the EXPANDED chevron
     (registry CHEVRON_COL, measured 12.59 on screen). Bridged at boot. */
  --fs-chain-chevron: 12.56px;
  /* M4d/P6: THE SPEC COLUMNS. The playlist's specification line is the
     same two columns whether it is rendered one-line (desktop/tablet) or
     stacked (mobile), so both read the width from here. THEATRICAL is
     the reference: these are the widths its one-line cells have always
     had, and its stacked box already rendered at 48.75/97.52 — the
     stacked box now lands on them exactly instead of near them. */
  /* THE SPEC SLOTS (M4g/O3): each column is as wide as its own widest
     value, measured across the catalogue — 20 for a language code, 61
     for a subtitle list, 80 for an aspect, 89 for a runtime — rounded
     up. The GAP between columns is not part of a slot; it is its own
     token below, so widening the air never silently widens a column.
     Column 1 carries language and dimension, column 2 subtitles and
     sound, column 3 aspect and duration. */
  --fs-spec-col-1: 22px;
  --fs-spec-col-2: 52px;
  --fs-spec-col-3: 86px;
  /* AUDIO gets its own slot: today's catalogue holds "5.1" and "7.1",
     but the format names that belong in this column — Atmos, D-Box —
     are three times as wide, and a slot sized on the short case would
     let one of them push its neighbours or wrap. */

  --fs-spec-col-audio: 56px;
  /* THE GAP BETWEEN SPEC COLUMNS. Two named values because the two
     bands are not equally free: on the one-line band there is room to
     spend, on the stacked band the whole row — lead, chevron, box, the
     three slots and the action controls — has to fit 345px at a 390
     window, which leaves 14 and not a pixel more. */
  /* THE GAP BETWEEN SPEC COLUMNS. M4i widened it (32 tablet / 64
     desktop) to spend the width the run was leaving at its right;
     M4L reverses that on Tom's look at the corrected build — the wider
     spacing does not read well and the run goes back to the value it
     had. One number, both bands. */
  --fs-spec-gap: 20px;
  /* the gap's FLOOR when the film table's group has to give (D-216).
     The transfers compress to "4px between adjacent contents"; here every
     value already sits behind an 8px lead, and 5 is what the wide slot
     needs to hold a timecode whole — 86 + 5 − 8 of lead = 83, the
     timecode's measured width — because NO value is ever shortened. */
  --fs-spec-gap-min: 5px;
  /* M4h/O4: 16, not 7. The stacked cell is wider than the grid inside
     it — measured 192.59 against 174 at a 390 window — so there were
     18.59 unused pixels sitting to the right of the duration column
     that the gaps can have. */
  --fs-spec-gap-mobile: 16px;
  /* THE GAP BETWEEN TWO ADJACENT BUTTONS (M4c/P11), one value app-wide.
     Measured off the reference Tom named — the Order popup's
     DELIVER TO CINEMA / CLOSE pair, which is two inline-block buttons
     with an ordinary word-space between them: 5px at the control font.
     The film edit form's Save/Cancel and Create-playlist/Ingest pairs
     already render the same 5. The only surface that had invented its
     own was the homevideo ORDER CONVERSION / RESTART pair at 16. */
  --fs-button-gap: 5px;
  /* THE ACTION ROW (D-295, Tom: production's proportions are the norm, its
     irregularities are not kept; measured on master,
     .probe/d295-master-metrics.mjs). An action's icon ink to its label's
     first letter — master's SCREENER and DELIVER (PLAY had 10.97, ORDER
     10.11) — inside a filled box too, and a clip's × to its title */
  --fs-action-icon-gap: 9.68px;
  /* ONE RHYTHM, INK TO INK: an action's last letter to the next action's
     first ink, master's SCREENER to PLAY, whether the next is bare or in a
     filled box (whose edge lies inside it) */
  --fs-action-rhythm: 27.97px;
  /* a bare action's box end after its label: the small button's 10 */
  --fs-action-end: 10px;
  /* a bare action's box start to its ink: what the rhythm leaves after the
     box end and the button gap (12.97) */
  --fs-action-ink-start: calc(var(--fs-action-rhythm) - var(--fs-action-end) - var(--fs-button-gap));
  /* A FILLED BOX IS SYMMETRIC (DELIVER, ORDER, DOWNLOAD): its left edge to
     the icon's ink, and the label's last letter to its right edge */
  --fs-action-box-ink: 11.67px;
  /* a clip's padlock among its actions (MATERIAL, the timeline's block):
     the closed lock's ink height, larger than the action icons so it reads
     as heavy as they do (D-295, Tom: 14 px to start, judged by eye) */
  --fs-action-lock-size: 14px;
  /* and how far it is lowered below the font's own seat, which already puts
     the bottom of the lock's body ink on the labels' baseline — measured by
     ink on dev 2026-11-16 (.probe/d295-lock-ink.mjs: 0 px at 1x, one device
     row lower at 2x and 4x, the open lock and the closed alike); the one
     value to move if it reads high (Tom) */
  --fs-action-lock-drop: 0px;
  /* the editor's description below the DCP line, as MATERIAL's stands below
     a clip's title — 18.39 px text to text, measured there
     (.probe/d295-desc-gap.mjs); the DCP line and the description's own
     lines leave 2 of it (D-295, Tom) */
  --fs-clip-description-gap: 16.39px;
  /* the capitals' height of the app's type, Gotham's 0.700 em (measured at
     300, 400 and 500 — .probe/d295-capheight.mjs): the film page's icons
     stand that high (Icon `cap`, D-295) */
  --fs-cap-height: 0.7em;
  /* the fixed-width icon slot, FA's fa-fw (.fs-icon--fw); the mobile band's
     action marks keep it with the film page's cap icons too */
  --fs-icon-fw-width: 1.28em;
  /* the heading's pen, a secondary tool beside the title, where master's
     pencil was (D-295, Tom): its ink's height and its bottom above the
     heading's baseline, measured on master */
  --fs-heading-pen-size: 16.91px;
  --fs-heading-pen-rise: 0.87px;
  /* the last timecode's text to the first action's icon, at least (D-295,
     Tom: clearly more than before; THEATRICAL's spacer gives more where the
     row has room) */
  --fs-action-lead: 24px;
  /* M4T/O1: the distance between the target line's DIVIDER and whatever
     stands next to it — the organisation on a cinema delivery, the
     address itself on a web download. One value, both sides of the rule,
     both cases. It used to live on the organisation, so a row without
     one had no gap at all. */
  --fs-detail-divider-gap: 8px;
  /* M4T/O8: the film grid's tile gutter. The grid hangs one gutter
     outside the page content box on each side so the CARDS land on it
     (M4M/O2); anything that spans the grid full-width — the release-date
     heading and its rule — has to put the gutter back or it renders into
     the page margin. Stated once so the three rules cannot drift. */
  --fs-grid-gutter: 8px;
  /* THE CHIP's own lead (G2.3): the sealed D-033 chip draws a 3px
     self-coloured border and 5px of padding before its content. A chip
     field pulls its chip block back by this much, so the chip's content
     edge lands on --fs-control-inset — the same x as the empty state's
     placeholder text. Derived from .fs-chip, not a new hand-set value. */
  --fs-chip-lead: 8px;
  /* THE GRANT FORM'S BLOCK RHYTHM (D-141). One gap between the form's
     blocks — field groups and preview slots alike — replacing a
     .fs-form-group margin and a Tailwind mt-4 that collapsed into each
     other. 24px: more air than the 16 that survived the collapse, which
     is what the salutation was short of. */
  --fs-screener-block-gap: var(--fs-checkbox-gap); /* 24 until D-287 */
  /* …and the tighter one INSIDE the validity pair, which is one control
     read as a unit rather than two blocks. */
  --fs-screener-pair-gap: var(--fs-checkbox-gap); /* 8 until D-287 */
  /* SEAMS THAT CARRY THEIR OWN (D-142/D-143, the owner's correction to
     D-141). A form is not an even stack: one gap as the DEFAULT was
     right and fixed two that had been silently collapsing, but a block
     that belongs to the line above it sits TIGHT against it, and a
     paragraph of prose needs air.
     
     ONE tight value, not one per seam: the remark box under the
     salutation and the validity pair under the line that starts the
     screener are the same relationship, so they read the same. */
  --fs-screener-tight-gap: var(--fs-checkbox-gap); /* 0 until D-287 */
  --fs-screener-closing-gap: var(--fs-checkbox-gap); /* 16 until D-287 */
  /* D-287 (Tom's review on dev, 2026-11-06: one 12 px row rhythm in every
     form and input panel): the four seams above are the one row gap now —
     the remark box and the validity pair stand the gap under their line,
     the pair's two dates the gap apart, the closing prose the gap under
     them, every block the gap under the one before. The names stay so the
     rules in kit-port read as they did. */
  /* THE mobile page edge (promoted, deliver-mobile round 2026-07-26):
     the legacyref-extracted 15px side margin every page uses below
     the 927 master breakpoint. Consumers: .fs-container,
     .fs-container-fluid@mobile, .app-navbar-meta/-main@mobile,
     .app-nav--open, .dt-section@mobile. */
  --fs-page-inset-mobile: 15px;
  /* THE page edge above the master breakpoint (M4f/O2, promoted from
     .fs-container-fluid's literal): the large margin is the normal one
     — it applies at TABLET and above without exception, and the 15 is
     the mobile-only value. Consumers: .fs-container-fluid,
     .fs-container--wide@>=927, .fd-hero-width@>=927. */
  --fs-page-inset: 32px;
  /* THE ROW INSET (M4h/O3): the air a row keeps INSIDE the page's own
     margin — 10px before the first mark on the left, 10px after the
     last one on the right, on every band. It is one value serving both
     sides, so a row can never be tight on one and loose on the other.
     Not the chain's gaps (those are mark-to-mark and mark-to-text
     distances between the row's parts); this is the row's distance from
     the container it sits in. */
  --fs-row-inset: 10px;
  /* THE LIVE-LIST ROW HEIGHT (D-196): one number for a /transfers row
     and a /screeners row, hand-set as the sum of its four whole terms —
     21 line-height (.fs-table td) + 6 padding top + 6 padding bottom
     (.fs-table--list td) + the 2 separator (.ft-list-row), collapsed and
     shared between rows so pitch equals box. It replaced a 36.2 pinned
     on the transfers status cell in July from the legacy page's
     FontAwesome line box, and the 34.19 the screeners rows fell out at
     from a 0.35rem padding; neither was a number anyone chose. Applied
     ONCE, on .ft-list-row > td above the stacked breakpoint, as the
     cell height — a minimum in a table cell, so a wrapped cell still
     grows. The icons stay 20 × 20 inside the 21 line. */
  --fs-list-row-height: 35px; /* 2 + 6 + 21 + 6, the even row as on production (D-256, kit-tables .fs-table--list td); 39 under the withdrawn rhythm of 2026-10-07 */
  /* THE COVER'S TWO FRAME WIDTHS (M4P). The grey ring a cover always
     wears, and the blue band it wears when selected — the second is
     drawn INWARD from the same outer edge, so selecting one changes
     colours and nothing else. Sampled off the pre-M4O build: the blue
     band was 4px there, and it is 4px here. */
  --fs-cover-frame: 2px;
  --fs-cover-select: 4px;
  /* The map's chrome clears the navigation by this much (M4h/O5). It
     lives here because its NAME says page-level, and a --fs-… declared
     on a surface is a token the app cannot check: the boot-time
     resolver reads them off :root. Hand-set; the value is Tom's call. */
  --fs-map-control-drop: 18px;
  /* THE PANE's top padding: the fixed header's band plus the standard page
     air below it (extracted; the header itself measures 105.5). One home,
     because a full-bleed page has to be able to cancel it — the map does
     (kit-misc #map), and a stale second copy of this number was the white
     strip under the bar. */
  --fs-pane-pad-top: 136px;
  /* K0: the closing band's height, hand-set (measured 220px on the
     rendered footer). The page area is a screenful minus the pane's top
     padding minus THIS, so a short page shows the band at the bottom of
     the first viewport instead of one scroll below it. */
  --fs-footer-band: 220px;
  /* THE FIXED HEADER's own height (extracted: meta bar + nav bar measure
     105.5 at every width). The pane's padding above is that plus the
     standard page air; a full-bleed page cancels only the AIR, so it starts
     at the header's edge — flush, with nothing of its own hidden behind the
     bar. The map's zoom control sat half under the bar because it cancelled
     the whole padding instead. */
  --fs-header-height: 105.5px;
  /* THE FILM PAGE'S HERO PULL (D-295, promoted from .fd's own 6.5rem): the
     hero starts this far up, under the fixed header, so its backdrop runs
     behind the bar. The clip editor's stage, laid over the hero, starts
     its picture where the header's edge crosses the hero — the hero's
     first row in view (--fs-hero-visible-top), from the three registers. */
  --fs-hero-pull: 6.5rem;
  --fs-hero-visible-top: calc(var(--fs-header-height) - var(--fs-pane-pad-top) + var(--fs-hero-pull));
  /* THE CLIP EDITOR'S TIMELINE (D-295): the ruler, the track under it, the
     zoom scrollbar under that; the hit width of an In/Out marker and its
     line, the playhead's line, a scrollbar end's grip. Hand-set. */
  --fs-clip-ruler-height: 28px;
  /* Tom's second and fourth additions: taller, so the track reads strong */
  --fs-clip-track-height: 96px;
  --fs-clip-zoombar-height: 12px;
  --fs-clip-marker-hit: 10px;
  --fs-clip-marker-line: 2px;
  --fs-clip-playhead-line: 2px;
  --fs-clip-playhead-hit: 10px;
  --fs-clip-zoombar-edge: 8px;
  /* THE LOGIN GROUND (G4.2) is defined in theme.css, with every raw
     colour value (D-254). */
  /* THE HEADER SEARCH FIELD (G3.3). One width for both layouts: the
     desktop width is also the mobile width, because a bigger field is
     better on a phone and the space is there. It gives way only when the
     air left next to the hamburger would fall below the minimum gap —
     declaratively, through max-width, so nothing is measured at runtime
     and nothing jumps on load.
       width 479  the field (rounds 15/16, production-extracted)
       toggler 52.6  the hamburger's box (D-020)
       gap-min 16    the air between field and hamburger — the HARD
                  constraint at every width; there is deliberately no
                  width floor beside it, because a floor wins over the cap
                  in the cascade and would eat the gap at the narrow end */
  --fs-search-width: 479px;
  --fs-search-toggler: 52.6px;
  --fs-search-gap-min: 16px;
  /* deliver CPL grouping (mobile round 2026-07-26): the lines of ONE
     CPL row, when it wraps — checkboxes -> pulldown -> ZIP icon,
     checkboxes -> name — stand apart by the page's own label-to-control
     distance, the CPL heading over its checkbox line (its mb-3, 12px
     measured; Tom, D-233); rows separate BETWEEN groups by more. */
  --dt-cpl-gap-wrap: 12px;
  --dt-cpl-gap-between: 16px;
  /* THE field box = production's (reviewer verdict 2026-07-27 with
     DevTools measurements, supersedes the v6/D-038 37.5): outer 44,
     padding 8x12 — with the 4px border the VISUAL text inset stays 16
     (4 border + 12 pad). Selects keep their own sealed 37.5 line
     (--fs-select-height below). */
  --fs-field-height: 44px;
  --fs-field-pad-x: 12px;
  --fs-select-height: 37.5px;
  /* the deliver date fields: 162 (the reviewer's FINAL call
     2026-07-27; supersedes 160/175/148). Content box = 162 − 8 border
     − 24 padding = 130px — the pathological zero-heavy "30.12.2026
     20:00" (130px @16/300) fits exactly, the realistic widest
     "28.12.2026 23:59" (125px) with 5px air. */
  --fs-date-field-width: 162px;
  /* THE PICKER PANEL'S OWN TEXT (D-228 review 36). A popup must not
     take its line metrics from the field it hangs off: in the transfer
     dialog the field line carries `line-height: 0` — the rule that
     kills a select wrapper's inline-block strut — and the panel
     inherited it, so the month row measured 0 tall, the weekday row 8
     against the deliver page's 29, and the calendar crushed under
     "September". 14px on the app's 1.5 line, which is what the deliver
     page's panel measures. */
  --fs-dtp-text-size: 14px;
  --fs-dtp-line-height: 21px;
  /* INPUT-FIELD text (reviewer round 2026-07-27, supersedes the D-038
     14: production renders form inputs/textareas/date fields at
     16px/300/20px in BOTH contexts — screener form on white AND the
     deliver grey panel; extracted element-level 2026-07-27). */
  --fs-control-font-size: 16px;
  --fs-control-font-weight: 300;
  --fs-field-line-height: 20px;
  /* SELECTS + BAR CONTROLS stay at production's own values (extracted
     2026-07-27: select 14px/300/17.5, 34px line — production keeps
     selects smaller than inputs; NOT superseded). Own token so the
     16px input bump can never drag them along silently. */
  --fs-select-font-size: 14px;
  /* THE field edge (production, both contexts): the field owns its
     border as part of its ONE definition — reads as a box on white
     (screener) and matches production on the grey panel (deliver).
     The width is its own token: label offsets, the chipfield inset
     math and the deliver select alignment all derive from it. */
  --fs-field-border-width: 4px;
  --fs-field-border: var(--fs-field-border-width) solid var(--color-surface-muted);
  /* THE focus frame (date fields only — see below); its colour,
     --fs-focus-color, is defined in theme.css with every raw colour value
     (D-254) */
  --fs-focus-width: 4px;
  /* THE QUIETER TONE (D-254): a text colour at this opacity — the dark
     search field's placeholder and a disabled date-picker day (a light
     field's placeholder is solid since D-256). 0.54 is bootstrap-alpha's
     placeholder value, which the dark search field carried before anything
     else. */
  --fs-muted-text-opacity: 0.54;
  /* the hint after a candidate's label (D-287: the district beside two
     candidates that read alike), the kit's small text size */
  --fs-option-hint-size: 12px;
  /* THE DISABLED TONE (D-284): the opacity of the kit's disabled pulldown
     (select.fs-select--light:disabled) and of the locked KDM box
     (.fs-toggle--disabled), set on both by the kit, so the two read as one
     disabled state in every browser. 0.7 is the value Chromium's own
     `select:disabled` gave the pulldown before the kit named it (read
     through CDP on the deliver page) — nothing changes in Chromium. */
  --fs-disabled-opacity: 0.7;

  /* ---- component variants (pre-consolidation look, restored) ---- */
  /* filter-bar controls: production 34px line (round 4) */
  --fs-bar-control-height: 34px;
  /* --fs-bar-control-pad-top (2px) RETIRED by D-184: a bar control has no
     vertical padding any more. It was the 2/0 asymmetry that put the
     pulldown's text a pixel off the bar's own line. */
  --fs-bar-select-clearance: 30px; /* text-to-arrow zone */
  --fs-bar-arrow-offset: 12px;     /* arrow inset from the right */
  /* THE HEADER CARET (the bootstrap triangle after a pulldown's word): a
     gap after the word and a triangle whose half-width is its border —
     the room it takes is the gap plus the two borders, 0.9em, and the
     region menu's entries end that far short of the trigger's inset so
     their right edge stands under the right edge of the WORD (Tom's
     third review of 2026-10-28, item 3). */
  --fs-caret-gap: 0.3em;
  --fs-caret-size: 0.3em;
  --fs-caret-room: calc(var(--fs-caret-gap) + 2 * var(--fs-caret-size));
  /* header search (production nav geometry, D-020 context) */
  --fs-search-height: 48px;
  --fs-search-pad-y: 14px;
  /* generic white input (production .form-control impression) */
  --fs-input-pad-y: 8px;
  --fs-input-font-size: 16px;
  /* admin fs-field family (production register) */
  --fs-field-pad-y: 0.5rem;
  --fs-field-font-size: 1rem;
  /* THE GAP BETWEEN TWO FORM BLOCKS (D-223 named it "the row gap"; the
     value is the .fs-form-group margin every form has had). A form ROW
     has no gap since Tom's third review of 2026-10-28 (item 1): its
     rhythm is the checkrow pitch (kit-forms .fs-form-group.fs-row). This
     is what a stacked block keeps below itself — a sign-in fieldset, the
     grant form's blocks, a confirm page — and what the stacked label's
     half gap and the dialog's button bar are written from. A surface
     that needs a different distance gets its own named token beside this
     one (D-252), never a multiple or a fraction of the row gap. */
  --fs-form-row-gap: var(--fs-checkbox-gap); /* 1rem until D-287: one 12 px rhythm, stacked blocks too */
  /* THE SECTION SPACING (Tom's addition after the authorisation round,
     2026-10-28): the room a section keeps — below a page's section title
     (.fs-section-title, the 2.5rem it has had) and ABOVE a section heading
     inside a form (.fs-form-section-title: the film form's Original and
     the region headings CH-D … D), so the heading reads as a new block. */
  --fs-section-gap: 2.5rem;
  /* THE SIGN-IN FORMS' TWO OWN DISTANCES (D-252, Tom's pixel pass): the
     address sits closer to the password than two ordinary rows do (field
     gap), and the action block — the primary button and the link under
     it, shared by the sign-in and the reset form — stands further off
     the element above it (actions gap). THE ACTIONS GAP IS EVERY FORM'S
     since Tom's third review of 2026-10-28 (item 1, the addition): the
     SAVE / CANCEL row of the admin forms and the transfer dialog's button
     bar stand off the form by it (kit-forms .fs-form-actions). */
  --fs-form-field-gap: 12px;
  /* 24 until D-287 (Tom's review on dev, 2026-11-06): the submit sits the
     one row gap under the last row, on every form, the sign-in ones too */
  --fs-form-actions-gap: var(--fs-checkbox-gap);
  /* THE SIGN-IN PANEL'S NOTICE (D-293, Tom's pixel pass): a notice stands
     this far above what follows it — the first label, or the one link —
     two of the form's rows, so it reads as a block of its own */
  --fs-login-notice-gap: 24px;
  /* ...and ITS BUTTON stands this far from the text on either side of it:
     "Forgot password?" above, the one link below. ONE value for both, so
     the two distances cannot drift apart (Tom's pixel pass, D-293) */
  --fs-login-action-gap: 18px;
  /* THE SIGN-IN PANEL'S SMALL TEXT (D-293, Tom's pixel pass): labels,
     links and button in one size. Running text — notices, lead sentences
     — stands in the fields' size (kit-login.css); the logo box and the
     footer's sentence keep their own. */
  --fs-login-font-size: 14px;
  /* THE LABEL COLUMN OF A FIELD-ALIGNED FORM (D-228 review 25) and THE
     HEIGHT OF AN ORDINARY FORM FIELD. Root tokens, because the smoke
     sweep holds every --fs-* var() the stylesheets reference to resolve
     on :root. The width is measured from the longest label the dialog
     draws ("Booked as (content)"), the height is what `.fs-field` has
     always been — 1rem of text on 0.5rem of padding, twice. */
  --fs-form-label-width: 232px;
  /* THE LABEL COLUMN AND ITS GAP, for the shared field-row model
     (D-228 review 35). The deliver page's approved geometry — a 12rem
     label and 16px of air — declared once as tokens, so the transfer
     dialog, whose labels are longer, re-points the width instead of
     writing the rule a second time. (`--fs-dialog-row-gap` was retired
     here: review 32 §7's tighter dialog-only gap gave way to the
     reference's spacing, which is the application's `--fs-form-row-gap`
     on both surfaces.) */
  --fs-row-label-width: 12rem;
  --fs-row-label-gap: 16px;
  /* WHERE A ROW'S LABEL SITS AGAINST ITS VALUE (D-228 review 36). The
     label's first line pairs with the VALUE's first line, so the offset
     is the value's own top inset — border + padding on a bordered
     field (the deliver page), and half the leftover on a control that
     centres its text in a fixed box (the transfer dialog, whose
     controls are one height and have no border). A row is then aligned
     whether its value is one line or eight, which is what the two-mode
     model was for; picking the mode by hand is what got BOOKED WITH
     centred against eight compositions. */
  --fs-row-label-offset: calc(var(--fs-field-pad-y) + var(--fs-field-border-width));
  /* THE FRAME A ROW'S FIELDS PAINT, WHICH IS NONE (review 37 §1). The
     deliver page's fields carried the 4px panel-coloured border and the
     dialog's did not, so every borderless control beside a bordered one
     had to give that width back to stand on the same x (D-073). One
     field definition means one answer: the row model's fields have no
     frame, so nothing is given back anywhere and the rule that did it
     is gone. The token stays because the arithmetic that used it is
     still readable as "give back the frame", and the frame is zero. */
  --fs-row-frame-width: 0px;
  /* ONE ROW HEIGHT FOR THE TRANSFER DIALOG (D-228 review 33 §3), and
     it is TAKEN, not invented: `--fs-bar-control-height` is what every
     control on /transfers, /screeners and the deliver page measures —
     34px on all three, the one height in this application where a
     select, an input and a combobox already agree. The dialog's own
     rows were three numbers (a 44px date picker, a 37.5px select, a
     40px input) because each control brought its own. */
  --fs-form-field-height: var(--fs-bar-control-height);
  /* THE TWO DISTRIBUTOR PULLDOWNS (D-228 review 39 §2). An option is a
     name and the roles that organisation holds on the film, so it is
     longer than any other value on a row in this dialog; the owner's
     number for the pair. */
  --fs-distributor-select-width: 300px;
  /* THE ONE CONTROL WIDER THAN THE ROW'S OWN WIDTH (D-228 review 29 §9;
     it was the whole dialog's width for reviews 35-36, and is the
     parcel number's again since 37 §1 took the row width from the
     deliver page): a Swiss Post number is 21 characters as the post
     office prints it, and 162 cuts it after fifteen. */
  --fs-tracking-id-width: 15rem;
  /* THE ONE CONTROL WIDTH a form row's value column hands to whatever
     control lands in it (D-223). A ROOT token, because the smoke sweep
     holds every --fs-* var() the stylesheets reference to resolve on
     :root — the surface that wants a different one re-points it on its
     own column (the transfer dialog does, to the same value). */
  --fs-row-control-width: var(--fs-date-field-width);
  /* …AND ITS HEIGHT, WHICH IS NOT A SECOND NUMBER EITHER (review 39
     §1). It was the one thing a surface still said for itself —
     production's 44px box on the deliver page against the dialog's 34 —
     and with the width, the frame and the inset all shared, that height
     was the whole of the difference: the same field looked generous on
     one page and tight on the other. The owner looked at both and
     settled on the dialog's, which is what every control on /films,
     /screeners and the bar measures (review 33 §3). One field, one
     number, no surface re-points it. */
  --fs-row-control-height: var(--fs-form-field-height);
  /* the attach row's line (D-215): the input's box, 20 + 2 × 8 = 36 —
     a ROOT token, because the smoke sweep holds every --fs-* var() the
     stylesheets reference to resolve on :root */
  --fs-attach-line: calc(var(--fs-field-font-size) * 1.25 + 2 * var(--fs-field-pad-y));
  /* ported native selects */
  --fs-native-pad-y: 0.375rem;
  --fs-native-clearance: 1.75rem;
  --fs-classic-pad-y: 0.625rem;
  --fs-classic-clearance: 2rem;
  --fs-select-sm-pad-y: 0.375rem;
  /* The DISTRIBUTOR filter pulldown carries NO width definition —
     intrinsic native-select width, sized by its widest option
     ("wichtiges Feld und darf etwas Platz haben", reviewer verdict
     2026-07-26). Deliberate: intrinsic by design, no constant. The
     other bar selects keep their fixed widths. */
  /* --fs-chipbox-pad-y (3px) RETIRED by D-184 with the same rule: the
     chip box's text sits on the bar's line, so the box has no vertical
     padding to centre a shorter line inside. The chip itself is
     unmoved — 27 in 34 still centres at 3.5, which is what
     --fs-chipfield-inset already says. */
  /* chipfield height = THE field height (44) since 2026-07-27.
     THE uniform chip gap (reviewer crop 2026-07-27): one value all
     around the chip block — left inset before the first chip, the
     top/bottom air and the inter-chip gap. 4.5 = (44 field − 8 border
     − 27 chip) / 2, i.e. exactly the centering air of the sealed
     D-033 chip in THE field box; the caret follows the same inset. */
  --fs-chipfield-gap: 4.5px;
  /* THE bar chip/filter field's DEFAULT width (D-111 part 4, third
     review): THE standard is the films Distributor pulldown as it
     renders (measured 220) — one shared token for every bar chip field
     on films, transfers and screeners, so nothing jumps between the
     pages. The floor rule stays: never narrower whatever the content;
     content may widen the field up to its row's space, on ONE line
     forever. Geometry pins the token against the live Distributor. */
  /* D-121: 200, not 220 — the owner's ruling on weight. It is the
     field's RESTING width wherever the element appears, and one chip
     must fit inside it (see --fs-chip-max below). */
  --fs-chipfield-width: 200px;

  /* THE FIELD'S INSET AROUND A CHIP — the same on all four sides
     (D-121, owner's ruling). MEASURED: the field is 34 high and a chip
     is 27, so the air above and below it is (34 - 27) / 2 = 3.5. The
     horizontal inset is now that same number, because the gap left of
     the chip read as far bigger than the gap above it — it was 8px,
     from `--fs-control-inset (16) - --fs-chip-lead (8)`, a rule that
     put the chip's TEXT on the placeholder's 16px inset. That rule is
     superseded: an equal optical inset around the chip wins over
     aligning its text with the placeholder's. */
  --fs-chipfield-inset: 3.5px;
  /* THE LINES A FORM'S CHIP FIELD HOLDS before it grows (D-286 round 8):
     one by default; a field sets its own from the data
     (components/forms/chipLines, on the row's wrapper) */
  --fs-chip-lines: 1;

  /* THE FIELD KEEPS A CLICKABLE STRIP BESIDE THE CHIP (D-122, owner's
     correction of D-121). A chip filling the field to its inner edge
     was too aggressive: a person must be able to click into the field
     next to a chip, and the field's end wants a little more grey than
     one pixel of caret.

     THE RESERVE IS 24px, and it is not a new number — it is the
     clearance the field already carried on its right before D-121 spent
     it, and the width of an ordinary click target. It holds the gap
     after the chip and the caret itself, both clickable:

       field                                    200
       - the inset, both sides   2 x 3.5 =       -7
       - the reserve (gap 4.5 + caret 19.5)     -24
                                               ----
       chip                                     169

     Inside the chip the label takes what is left after the chip's own
     furniture — frame 3+3 border and 5+5 padding = 16, the × 8.19, and
     the word-space before it 3.89 — so the label is cut at 140.92. It
     is the CHIP that carries the cap and the label that ellipsizes
     inside it, so the chip's right edge lands exactly on the field's
     inner right edge rather than near it.

     ONLY SHORTEN, NEVER LENGTHEN: this is a max-width, so a short value
     leaves a narrow chip and nothing is padded out. */
  --fs-chipfield-reserve: 24px;

  --fs-chip-max: calc(
    var(--fs-chipfield-width) - 2 * var(--fs-chipfield-inset) - var(--fs-chipfield-reserve)
  );

  /* THE GAP BEFORE A REMOVE × — one word-space, because that is the
     relationship the reference has (D-121, owner's ruling). The film
     conversions row writes "name@example.com ×" as ONE line of running
     text with a literal space between them; a chip is a flex box and
     has no word-spaces, so the same relationship has to be spelled as a
     gap. Measured in the chip's register (Gotham 300 14/21): a space
     advances 3.89px, i.e. 0.278em — em, so it stays one space at any
     size the surrounding text takes. */
  --fs-remove-x-gap: 0.278em;
}


/* ---- FOCUS (the one scoped definition — no per-page rules) ----
   The blue INSET frame applies EXCLUSIVELY to the date fields: the
   picker opens there, and the frame marks the active popup surface
   (reviewer verdict). Everything else keeps its pre-consolidation
   behavior, restored below. */
.fs-dtp-field:focus,
.fs-dtp-field:focus-visible,
.fs-dtp-field--open {
  outline: none;
  /* the field now owns a real 4px border (2026-07-27) — the frame is
     that border turning blue (production's focus mechanism), not a
     shadow stacked inside the grey border. Same law, same visual:
     a 4px blue frame at the box edge, on date fields ONLY. */
  border-color: var(--fs-focus-color);
}
/* native selects: menu shows focus; UA ring suppressed */
select:focus,
select:focus-visible {
  outline: none;
  box-shadow: none;
}
/* …AND ON A FORM ROW IT GROWS INWARD (D-228 review 37 §1, the owner's
   ruling), painted at the box edge over the field's own white rather
   than outside it. The rule above is the frame a BORDERED field paints,
   which is the picker anywhere outside the row model (the screener
   grant, the playlist form, screens); a field on a form row has no
   border at all since review 37, so the frame is an inset shadow — the
   same 4px in the same blue at the same place. One rule for both
   surfaces that use the row model.

   THE FRAME BELONGS TO THE OPEN CALENDAR AND TO NOTHING ELSE (the
   owner's ruling, review 36 §2). It announces a popup — and a select, a
   text input, a textarea and a combobox open nothing. Review 35 gave it
   to all of them "for consistency", which made a frame that means
   something into decoration; it is off again. */
.fs-row--field .fs-dtp-field:focus,
.fs-row--field .fs-dtp-field--open {
  outline: none;
  box-shadow: inset 0 0 0 var(--fs-focus-width) var(--fs-focus-color);
}
/* icon-anchor family (collapse chevrons, transfer status/type links):
   the UA :focus-visible ring drew a blue rounded frame around the
   version collapse chevron (reviewer defect, Icons_falsch.png rollout
   2) — focus frames exist ONLY on the date fields. */
.ft-toggle:focus,
.ft-toggle:focus-visible,
.ft-arrow:focus,
.ft-arrow:focus-visible,
.ft-arrow-targets:focus,
.ft-arrow-targets:focus-visible,
.transfer-icon:focus,
.transfer-icon:focus-visible,
.transfer-type-icon:focus,
.transfer-type-icon:focus-visible {
  outline: none;
}
/* restored pre-consolidation focus styling (border-color impressions;
   on borderless variants they are inert by design, as before) */
.fs-field:focus {
  color: var(--color-text);
  background-color: var(--color-surface);
  border-color: var(--fs-focus-color);
  outline: none;
}
.fs-input:focus {
  border-color: var(--fs-focus-color);
}
.fs-dtp-time-input:focus {
  border-color: var(--fs-focus-color);
}
.fs-select-native:focus {
  border-color: #51a7e8;
  outline: none;
}
/* ============ THE INNER-CHECK POSITION — ONE DEFINITION ============
   Reviewer verdict 2026-07-27: the /deliver (fs-toggle) check position
   is the reference. Every checkbox centres its check glyph in the box.
   The sealed .fs-toggle paints a centered 16px background (app.css,
   pixel-parity 0-diff — left untouched, it already sits at this same
   centred position). The .fs-check-box family (film-edit, admin/login
   forms, CheckboxRow) centres the SAME 16px <Icon name="check"> HERE,
   so its ink-vs-box centre matches deliver instead of riding ~1px high
   on the inline line-box. ONE place, no per-page nudge, no second
   position value. These boxes are the "control anatomy" census
   exclusion (kept OUT of MarkIcon) — that exclusion does NOT exempt
   them from this no-duplication rule. Loaded last, so this centring
   wins over the block-flow default without touching the variant rules. */
.fs-check-box {
  display: flex;
  align-items: center;
  justify-content: center;
}

/* THE CHECKBOX ROW (G2.1): the paint is .fs-toggle's (sealed, scoped);
   this is the row rhythm and nothing else. A row is at least one pitch
   tall, so a list of them breathes evenly whatever the surface. */
/* :not(--inline) and not a bare .fs-checkrow: the sealed paint rules name
   two classes, so the row's own geometry has to match that weight to say
   "a row is BLOCK-level" over the bar toggle's inline-flex. */
.fs-checkrow:not(.fs-checkrow--inline) {
  min-height: var(--fs-checkrow-pitch);
  /* a row is a row: the box and its label sit on one centred line, and
     the pitch is the row's own height — no stacking margins on top of it
     (the .fs-check--compact nudge is a form-row nudge, not a list one) */
  display: flex;
  align-items: center;
  margin-top: 0;
}
/* THE PITCH FOLLOWS THE ROW'S CONTENT (G2b v2, reviewer rule).
   A row with an interactive CHECKBOX in it gets this airy pitch — the
   box needs the room. A row WITHOUT one keeps its own tight rhythm:
   the theatrical tab's delivery entries carry status ICONS, not checkboxes,
   and neither does a /transfers row. v1 handed the pitch to a shared row
   base and it leaked onto both; the pitch reaches a surface through the
   checkbox ROW alone now.
   Two consumers, and they are the only legal ones (asserted by the
   checkboxPitchOnlyOnCheckboxRows source gate):
     .fs-checkrow          — the row element itself, wherever it renders
     .fd-conversion-row td — the HOMEVIDEO conversion list, whose cell
                             hosts an inline checkbox row and therefore
                             owns its height; conversion checkboxes exist
                             only under HOMEVIDEO.
   O6: the deliver page's 42 IS this token now — it was the living
   reference and the films value moved onto it, so there is one pitch and
   not two. */
/* the selector carries the weight it needs to beat the asset-details
   table's own 4px cell padding — and it still names nothing but the
   conversion row, so the pitch cannot reach a neighbouring icon row */
.fs-table .ft-body--asset-details tr.fd-conversion-row td {
  height: var(--fs-checkrow-pitch);
  padding-top: calc((var(--fs-checkrow-pitch) - var(--fs-checkbox-size)) / 2);
  padding-bottom: calc((var(--fs-checkrow-pitch) - var(--fs-checkbox-size)) / 2);
}
.fs-checkrow input {
  /* the box is the box: a row is a flex container now, and a flex item
     may shrink — the conversion list's 72px name edge squeezed the 34px
     box to 32 before this line. */
  flex: none;
}
.fs-checkrow--inline {
  /* NOT a row in a list: a bar toggle, a table cell, a form row. It takes
     its height from what it sits in and keeps that surface's own paint
     geometry — only list rows carry the pitch. */
  min-height: 0;
  display: inline-flex;
}
