/* ReelTalk stylesheet. Grindhouse / midnight-movie visual identity (M6
   artwork, R60): layered near-black browns, dirty-cream text, and red used as
   theatrical lighting. Typography carries most of the identity — Bebas Neue for
   titles/section headings and the lit red controls, Oswald for metadata and
   small headings, Archivo for body/reviews and the header's own text, Monoton
   only for the neon wordmark, Kaushan Script only for the footer sign-off. The
   owner-supplied poster texture fades inward from the outer edges;
   content panels and body copy stay clean. */

:root {
  /* Palette — near-black browns + dirty cream + theatrical red. Values per the
     owner's brief / mockup reference (adapted, not copied). */
  --black:    #090807;  /* page background */
  --black-2:  #11100e;  /* deeper alt background */
  --panel:    #141210;  /* raised panel (cards, dropdowns) */
  --panel-2:  #1b1713;  /* raised panel / hover */
  --cream:        #e9dfcb;  /* body text */
  --cream-muted:  #b8aa91;  /* secondary text */
  --white:        #ffffff;  /* post prose, dates and header links (owner pass, 2026-10-04) */
  --red:        #d42b26;  /* primary red — fills, display headings */
  --red-bright: #ff4138;  /* neon/bright red — active, glow, key highlights */
  --red-dark:   #721713;  /* dark red — deep fills, shadows */
  --amber:   #e0a52b;  /* amber accent + focus */
  --mustard: #c79836;  /* mustard */
  --teal:    #43868a;  /* teal tertiary */
  --gold:    #f1b51a;  /* star ratings */
  --star-empty: #7d6a50;  /* the unfilled layer of a star row: worn bronze at
     3.86:1 on the page, so the five-star track stays legible as the graphic
     that says what a rating is out of (--line measured 2.17) */
  --line:    #5a432c;  /* thin amber/brown borders */
  --steel:   #5c5852;  /* dirty steel gray — search trim (mockup) */
  --avatar-ring: #d9c3b3;  /* worn cream bezel around an avatar disc */
  --neon-rim: #ff6a5b;  /* hot glass edge on a lit red control (button, step disc) */

  /* Worn crimson fill for lit red controls: an original mottled tile (generated
     for this project) painted over a dark-to-darker red gradient, so the fill is
     uneven like lacquered metal instead of flat paint. */
  --neon-mottle: url("../images/button-mottle.720f44b16379.png");

  /* Typography roles. */
  --display: "Bebas Neue", sans-serif;  /* film titles, section headings, lit red controls */
  --ui:      "Oswald", sans-serif;      /* metadata, tabs, genre pills, small headings */
  --body:    "Archivo", sans-serif;     /* body text + reviews */
  --script:  "Kaushan Script", cursive;  /* the footer sign-off only — neon signage */

  /* Semantic roles — the rest of this sheet references these. */
  --bg: var(--black);
  --fg: var(--cream);
  --muted: var(--cream-muted);
  --accent: #e0554a;   /* theatrical red for focus rings, field borders, watchlist */
  /* Anchor text, resting and hovered (owner pass, 2026-10-05). Split out of
     --accent on purpose: the focus ring and the field borders keep the old
     muted #e0554a, while link text moves to the core of the solid-red
     clapperboard so the two read as the same red. Measured off
     applaud-solid-red.png at alpha>=200, where the mode is fc0a13.
     Hover deliberately equals resting: the old hover went brighter than the
     resting colour, and once resting moved to #fc0a13 a hover back down to
     --accent would have read as de-emphasis. */
  --link: #fc0a13;
  --border: var(--line);
  --error: #ff5a3c;
  --surface: var(--panel);
  --surface-2: var(--panel-2);
  --field: #0d0b09;    /* inset form field, a hair darker than the page */

  /* Aliases kept for existing fill/border rules. */
  --blood-red: var(--red);
  --brown: var(--line);
}

/* Self-hosted SIL OFL fonts (no CDN, no build step — R6). Each font's OFL.txt
   sits alongside it under static/fonts/. */
@font-face {
  font-family: "Monoton";
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url("../fonts/monoton.c6856aa207b4.woff2") format("woff2");
}

@font-face {
  font-family: "Bebas Neue";
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url("../fonts/bebas-neue.5853435d21b1.woff2") format("woff2");
}

@font-face {
  font-family: "Oswald";
  font-style: normal;
  font-weight: 200 700;
  font-display: swap;
  src: url("../fonts/oswald.22c3b00d2e65.woff2") format("woff2");
}

@font-face {
  font-family: "Archivo";
  font-style: normal;
  font-weight: 400 800;
  font-display: swap;
  src: url("../fonts/archivo.cd56e2ec63d7.woff2") format("woff2");
}

@font-face {
  font-family: "Kaushan Script";
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url("../fonts/kaushan-script.4648267a9594.woff2") format("woff2");
}

* {
  box-sizing: border-box;
}

html {
  /* Reserve the scrollbar's width on every page, scrolling or not. Without it
     the scrollbar took its space only when a page overflowed, so a page that
     fitted sat 7px right of one that scrolled -- measured at 1440 as the menu's
     left edge at 84 against 77, and the same 7px on the header's own width. The
     chrome then stepped sideways on the click that crossed the threshold, the
     horizontal twin of the row-inflation jump below. Owner ruling, 2026-11-08.
     On a platform with overlay scrollbars there is no gutter to reserve and this
     is a no-op. The band it reserves paints in the page's own colour because
     `body`'s background propagates to the canvas. */
  scrollbar-gutter: stable;
}

body {
  margin: 0;
  font-family: var(--body);
  line-height: 1.55;
  color: var(--fg);
  min-height: 100vh;
  background-color: var(--black);
}

a {
  color: var(--link);
}

.container {
  max-width: 40rem;
  margin: 0 auto;
  padding: 1rem 1rem 3rem;
}

/* Marquee band (M6 artwork B, R61): a wide strip spanning the viewport —
   top row logo / search / profile, nav row below. The header's inner
   container is wider than the 40rem page column (which stays until
   sub-increment C). No own background since the owner texture pass: it shows
   the site-wide grunge like the rest of the page; a worn chrome rail closes
   the band (see the rail rules in the texture section). */
.site-header {
  position: relative;
  border-bottom: 3px solid var(--black-2);
  box-shadow: 0 4px 10px rgba(0, 0, 0, 0.45);
}

.site-header .container {
  max-width: 72rem;
}

.header-top {
  display: grid;
  grid-template-columns: 1fr minmax(0, 34rem) 1fr;
  align-items: center;
  /* Wide column gap keeps clear air between the wordmark and the search box. */
  gap: 1.25rem 4rem;
  padding-top: 0.9rem;
  padding-bottom: 0.4rem;
}

/* Wordmark — Monoton neon-tube treatment (M6 artwork, R60; relit per R68).

   Two layers, because Monoton cannot be rasterised well at the sizes this bar
   uses. The anchor itself is the *ghost*: its own text is transparent, and it
   reserves the layout box, carries the accessible name, and paints the bloom.
   The visible tubes are a second copy in .brand-tube, rasterised at 4x and
   scaled back down. See the tube rule for why. */
.brand {
  position: relative;
  font-family: "Monoton", sans-serif;
  font-weight: 400;
  /* Sized against MOCKUP.png proportions (owner review of M6 increment 5). */
  font-size: 3.6rem;
  letter-spacing: 0.02em;
  line-height: 1;
  /* Transparent, on purpose: the glyph shapes still cast the text-shadow below,
     so the ghost is all bloom and no tube. The tubes come from .brand-tube. */
  color: transparent;
  text-decoration: none;
  /* Bloom stops stay wide on purpose, and wider here than the tubes alone would
     need. Monoton draws every stroke as three or four parallel bars, and at the
     sizes this wordmark actually ships (2.2rem desktop, 1.65rem below) those bars
     are 1-2px wide with 1px gaps. A bloom stop whose radius is that same order -
     the old 2px white and 5px red - is a light field wider than the gap it falls
     into, so it poured light into every gap and washed the bars to flat pink:
     measured across the wordmark, the darkest pixels inside the letters lifted
     from 8 (page black) to 44 and resolvable bar edges fell from 87 to 52 on
     desktop, and to 19 of 75 on a phone, which is the "the lines run together"
     read. Wide stops spend the light over an area instead of into the gaps.
     The first stop sits at 26px rather than 14 because the supersampled tube layer
     below already costs some gap darkness (the downsample averages each 1px gap
     with the bars either side of it); starting the bloom further out keeps the
     measured gap floor at 34 instead of 42 and buys back bar edges, 76 against 66.
     The hot core does not come from a shadow at all: it is the tube fill, which the
     stroke on .brand-tube carves back down the middle of each bar.
     The radii live here, unscaled, rather than on the 3x tube layer: a transform
     scales its shadows too, so 96px would have to be written as 288px and paid for
     in rasterising a blur three times the size to land on the same pixels. */
  text-shadow:
    0 0 26px rgba(255, 65, 56, 0.75),
    0 0 52px rgba(212, 43, 38, 0.65),
    0 0 96px rgba(255, 40, 25, 0.38);
}

/* The visible tubes, rasterised at three times the size and scaled back to sit
   exactly over the ghost.

   Monoton's bars are about 1px apart on a curve, and a curve cannot be sampled at
   that pitch: the concentric arcs broke into stair-stepped dots, which is the
   moire on the R, the a and the k. Rasterising at 3x and letting the browser
   downsample gives it real subpixel coverage to average, and the isolated
   single-pixel ink inside the wordmark fell from 27.1% of all ink to 9.7% with the
   bloom held constant. A sub-pixel blur was the cheaper candidate and it is not
   the fix: blur(.5px) left that number at 27.9%, softening the dots without
   joining them. Merging the bars with a fat light stroke drives jaggedness to zero
   and is worse still, because it fills the counters and the word stops being
   Monoton.
   This trades, it does not win outright: the same downsample that smooths the
   curves lightens the 1px gaps, so resolvable bar edges land at 76 against the
   1x layer's 87. Taking the wordmark to 2.5rem gets both (83 edges, 3.6% jagged)
   at the cost of five pixels of bar height, which is the owner's call, not this
   rule's.
   Do not add `will-change: transform` here - it hands the layer to the compositor,
   which rasterises at the pre-scale size and downsamples worse than the paint path
   (measured 30.3%, worse than not doing this at all). 4x is smoother still on the
   curves and dimmer in the gaps; 3x is the balance.

   Everything on this layer is in em of the *3x* size, so the stroke is a third of
   the 0.0174em that paints the red glass: painting the stroke last carves red back
   into each bar and leaves a narrow white-hot core, which is what makes the wordmark
   read as lit rather than painted. */
.brand-tube {
  position: absolute;
  left: 0;
  top: 0;
  font-size: 300%;
  transform: scale(0.333333);
  transform-origin: 0 0;
  color: #fff4ee;
  -webkit-text-stroke: 0.0058em var(--red);
}

.header-user {
  /* Pinned to the last column (R80): with the search box gone for anonymous
     visitors this row has only two children, and auto-placement would drop the
     handle into the 34rem middle column, rendering "Log in" centered. */
  grid-column: 3;
  justify-self: end;
  display: flex;
  align-items: center;
  gap: 1.1rem;
}

.header-user a {
  color: var(--white);
  text-decoration: none;
  font-size: 0.88rem;
}

.header-user a:hover {
  color: var(--link);
}

/* The signed-in handle is the only item on this side — kept lit like a
   marquee name, going neon-red on hover. The avatar rides inside the same link
   so the corner stays one tab stop, with the reference's ~12px disc-to-name gap. */
.header-user .user-name {
  display: inline-flex;
  align-items: center;
  gap: 0.7rem;
  color: var(--white);
}

.header-user .user-name:hover {
  color: var(--link);
}

/* The nav row that lived here is retired (N4): the member destinations now
   ride the left menu defined in the "Desktop navigation" section below, and
   the phone surfaces in the "Mobile navigation" section after it. */

/* Narrow screens: the search box drops to its own full-width line so the
   suggest dropdown keeps its shape; the wordmark steps down and the wide
   logo/search gap collapses so the top row never overflows. */
@media (max-width: 40rem) {
  .header-top {
    grid-template-columns: 1fr auto;
    row-gap: 0.6rem;
    column-gap: 1rem;
  }

  .brand {
    font-size: 2.2rem;
  }

  .global-search {
    grid-column: 1 / -1;
    order: 3;
  }

  /* Two columns here, so the handle's last column is 2, not 3 — the base pin
     would open an implicit third track and leave a gap on the right. */
  .header-user {
    grid-column: 2;
    /* The corner truncates instead of widening the grid. Its min-content (a
       long handle is one unbreakable word) used to push the whole header past
       the viewport, and the search row spanning 1 / -1 inherited the overflow:
       measured 399px of content in a 375px viewport. min-width:0 lets the
       track shrink; the text inside each corner link carries the ellipsis. */
    min-width: 0;
  }

  .header-user a {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
  }

  .header-user .user-handle {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
  }
}

/* --- Mobile navigation (N3) --------------------------------------------------
   The approved phone pattern: a compact header (wordmark, unread bell,
   avatar), a fixed bottom bar (Feed, Search, My Films, Lists, More) and a
   More sheet that is a real dialog. Desktop is untouched on purpose: every
   phone part starts hidden here (the bell parts, the bar, the page field),
   and every change to shared chrome lives under the 1024px line where the
   design retires the nav row. The corner rules name the corner's own parts
   and .header-user > a, never the moderator's retired corner link, which
   carries a standing "no CSS was written for it" guard (R101) and stays
   green. The unread badge gained its own rule below by owner ruling
   (2026-11-04), replacing R96's "no CSS" guard. */

/* The unread bell is the corner's phone treatment (owner ruling 2026-11-04,
   replacing N4's all-width corner bell): from 1024px up the desktop menu
   carries the count on its own Notifications row, so the corner bell hides
   and the handle keeps the corner. Below the line the sidebar is gone and
   the bell returns -- restored inside the mobile block. The label stays in
   the DOM, clipped rather than display:none, so the link keeps its
   accessible name. */
.header-user > a {
  /* position:relative is what the count bubble sits on. */
  position: relative;
  min-width: 44px;
  min-height: 44px;
  display: inline-flex;
  align-items: center;
  justify-content: center;
}

/* Two classes deep on purpose: .header-user > a above is (0,1,1) and a bare
   .notifications-link would lose the display fight to it. */
.header-user .notifications-link {
  display: none;
}

.corner-icon {
  display: block;
  width: 22px;
  height: 22px;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.7;
  stroke-linecap: round;
  stroke-linejoin: round;
}

.corner-count {
  display: block;
  position: absolute;
  top: 2px;
  right: 0;
  font: 700 0.68rem/1 var(--ui);
  background: var(--red);
  color: #fff;
  border-radius: 0.6rem;
  padding: 0.18rem 0.35rem;
}

.corner-label {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  overflow: hidden;
  clip: rect(0 0 0 0);
  white-space: nowrap;
  border: 0;
}

.bottom-nav {
  display: none;
}

.page-search {
  display: none;
}

.more-sheet {
  color: #eadbc1;
  background: #201b17;
  border: 1px solid #665344;
  padding: 20px 20px 28px;
  width: min(24rem, calc(100vw - 2rem));
}

.more-sheet::backdrop {
  background: rgba(0, 0, 0, 0.7);
}

.more-sheet-heading {
  display: flex;
  justify-content: space-between;
  align-items: center;
}

.more-sheet-heading h2 {
  font-size: 26px;
  margin: 0 0 10px;
}

/* The sheet's buttons must not arrive pre-lit: the three bare-button blocks
   would otherwise dress the close control and the Log out row in Bebas
   caps with bloom. */
.more-sheet button {
  background: none;
  border: 0;
  box-shadow: none;
  text-transform: none;
  letter-spacing: 0;
  color: #edddc4;
  font-family: var(--body);
}

.more-sheet-close {
  min-width: 44px;
  min-height: 44px;
  padding: 0;
  font: 28px/1 sans-serif;
}

.more-sheet form.inline {
  display: block;
}

.more-sheet a,
.more-sheet form.inline button {
  display: flex;
  gap: 14px;
  align-items: center;
  box-sizing: border-box;
  width: 100%;
  min-height: 54px;
  padding: 0 12px;
  color: #b9ac99;
  font-family: var(--body);
  font-size: 15px;
  text-decoration: none;
}

.more-sheet .nav-label {
  flex: 1;
  /* The Log out row is a <button>, and buttons centre their text; the sheet
     rows are a list and must agree with the anchors beside them. */
  text-align: left;
}

.more-sheet a small {
  margin-left: auto;
  color: #a89c8c;
  font-size: 11px;
}

.more-sheet svg {
  width: 22px;
  height: 22px;
  flex: none;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.7;
  stroke-linecap: round;
  stroke-linejoin: round;
}

.more-sheet hr {
  width: 100%;
  border: 0;
  border-top: 1px solid #54483e;
  margin: 14px 0;
}

/* The informative group (D8, M4) is secondary navigation: the four footer
   links a member can no longer reach from a phone. It keeps the sheet's row
   language at one step down -- 44px targets (the touch floor the close
   control already honours) instead of 54 -- so the sheet still reaches Log
   out without scrolling on a short phone even with the staff rows present. */
.more-sheet a[data-group="info"] {
  min-height: 44px;
  font-size: 14px;
}

.more-sheet a[data-group="info"] svg {
  width: 20px;
  height: 20px;
}

/* The Profile / Settings hub: Import and Export live here now at every
   width, so the destinations outlive the desktop nav row's N4 retirement. */
.settings-links {
  border-top: 1px solid #54483e;
  margin-top: 24px;
}

.settings-links a {
  display: flex;
  align-items: center;
  gap: 16px;
  min-height: 56px;
  padding: 4px 0;
  color: #d8c8b0;
  text-decoration: none;
  border-bottom: 1px solid #54483e;
}

.settings-links a:hover {
  color: var(--link);
}

.settings-links a small {
  display: block;
  font: 13px sans-serif;
  color: #a99a85;
  margin-top: 5px;
}

/* The bio field on the settings form. A bare `<textarea>` renders
   browser-default here — a white plate at its intrinsic 20-column width,
   which both fights the dark theme and measures 397px, so it pushed the page
   past a 375px and a 320px viewport. Same field treatment the reply composer
   and the list editor give theirs; only a browser catches this class of thing. */
.profile-form textarea {
  width: 100%;
  max-width: 42rem;
  padding: 0.45rem 0.6rem;
  font: inherit;
  color: inherit;
  background: var(--field);
  border: 1px solid var(--brown);
  border-radius: 4px;
  margin-top: 0.25rem;
}

@media (max-width: 1023px) {
  /* One compact row: wordmark left, corner right. The search field moves
     into the search page (see .page-search) and the nav row retires -- its
     destinations ride the bar and the sheet now. */
  .header-top {
    grid-template-columns: minmax(0, 1fr) auto;
    gap: 0.5rem 1rem;
    padding-top: 0.55rem;
    padding-bottom: 0.5rem;
  }

  .brand {
    font-size: 1.65rem;
  }

  .global-search {
    display: none;
  }

  .site-nav {
    display: none;
  }

  .header-user {
    grid-column: 2;
    min-width: 0;
    gap: 0.55rem;
  }

  /* The corner bell is the phone's unread surface (owner ruling 2026-11-04):
     the base sheet hides it from 1024px up, where the sidebar carries the
     count instead. Here the sidebar is gone, so the bell comes back. */
  .header-user .notifications-link {
    display: inline-flex;
  }

  .header-user .user-handle {
    display: none;
  }

  .header-user .avatar {
    width: 28px;
    height: 28px;
  }

  .bottom-nav {
    display: grid;
    grid-template-columns: repeat(5, minmax(0, 1fr));
    position: fixed;
    inset: auto 0 0 0;
    z-index: 20;
    background: #211b17;
    border-top: 1px solid #75604e;
    padding: 6px 6px max(8px, env(safe-area-inset-bottom));
  }

  .bottom-nav a,
  .bottom-nav button {
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: center;
    gap: 3px;
    min-height: 50px;
    min-width: 0;
    padding: 0;
    color: #b9aa94;
    background: none;
    border: 0;
    box-shadow: none;
    text-decoration: none;
    text-shadow: none;
    text-transform: none;
    letter-spacing: 0;
    font: 11px/1.2 sans-serif;
  }

  .bottom-nav svg {
    width: 25px;
    height: 25px;
    fill: none;
    stroke: currentColor;
    stroke-width: 1.7;
    stroke-linecap: round;
    stroke-linejoin: round;
  }

  .bottom-nav [aria-current="page"] {
    color: #f2d8a7;
    border-top: 2px solid #c14b37;
  }

  .bottom-nav .more-button[aria-expanded="true"] {
    color: #f2d8a7;
  }

  /* The sheet lands as a bottom sheet, clear of the notch. */
  .more-sheet {
    position: fixed;
    inset: auto 0 0 0;
    margin: 0;
    width: 100%;
    max-width: none;
    box-sizing: border-box;
    border-radius: 14px 14px 0 0;
    max-height: 85dvh;
    overflow-y: auto;
    padding-bottom: max(24px, env(safe-area-inset-bottom));
  }

  /* The fixed bar must not eat the page's last line. */
  body {
    padding-bottom: calc(4.75rem + env(safe-area-inset-bottom));
  }

  /* The search page's own field is the phone entry point; 16px keeps iOS
     from zooming the viewport on focus. */
  .page-search {
    display: block;
    margin: 1.25rem 0 1.5rem;
  }

  .page-search input[type="search"] {
    min-height: 48px;
    font-size: 16px;
  }

  /* A long post URL is one unbreakable word: the ellipsis markup alone still
     pushed a 320px viewport sideways (measured 355px of content), the same
     trap .review-author already carries for remote handles. The N1 mockup
     hit this and carried overflow-wrap into the acceptance. Mobile only, so
     the desktop column keeps its current wrapping. */
  .review-body {
    overflow-wrap: anywhere;
  }
}

/* --- Desktop navigation (N4) -------------------------------------------------
   The approved wide layout: a 280px left menu that is the page's own column,
   a full-bleed header above it, and the reading column centred in what is
   left. The menu is a body child (templates/base.html), so the layout is a
   body grid rather than a padding hack: the header spans both tracks and the
   menu sticks in its own column, which is what keeps a viewport-centred 40rem
   column from sitting under a fixed sidebar at 1024px. Values are the
   approved mockup's (.n1-* in .qwen/tmp/navigation-n1/proposal.js).

   Above 1023px only: the phone surfaces are the other half of the design and
   the 1023px block already hides this menu, so nothing here can reach them. */
@media (min-width: 1024px) {
  body {
    /* The header's own height, re-measured at 75px on 2026-11-08 and stable from
       1024 to 2560. One variable because the menu has to stick exactly below it,
       and one literal because two drift: this one still said 82 after the relit
       wordmark brought the bar back at 75, so the menu hung 7px low on every
       page. Re-measure it after any change to the bar. It is the *member* bar --
       a signed-out visitor has no search box and measures 71px -- which is fine,
       because both consumers here are the menu, and they get no menu at all. */
    --header-h: 75px;
    display: grid;
    /* One track by default. A signed-out visitor gets no menu at all (N1
       decision 8), and a standing 280px first track would leave them an empty
       gutter down the left of the landing page. */
    grid-template-columns: minmax(0, 1fr);
    /* Header, page, footer -- and the middle row is the one that eats the
       leftover viewport height. With the rows left implicit they are all auto,
       and `align-content: normal` stretches *every* auto track with the
       leftover, so a page shorter than the viewport spent its free space
       inflating the header row: measured at 1440x900 the bar stayed 75px inside
       a row that grew to 127px, which pushed the menu, the avatar and the tab
       strip down by the difference -- and by a different difference on each
       page, because each page has different content. Clicking between a profile
       and its films tabs moved the whole chrome (owner report, 2026-11-08). The
       1fr row takes the slack instead, so the header row is exactly the header
       on every page and the footer still lands flush at the bottom of a short
       one. Its minimum stays `auto` rather than 0: on a page taller than the
       viewport the row has to keep its content height or the footer gets pulled
       up over the text. */
    grid-template-rows: auto 1fr auto;
    align-items: start;
  }

  body:has(.site-nav) {
    /* N8: the menu lives *inside* the centred band rather than glued to the
       left window edge. Two auto tracks outside a fixed menu track and a capped
       content track put the free space on both sides of everything, which is
       what the owner's Mastodon reference does (333px of bare window left of
       its leftmost column at a 1880 viewport). Two tracks -- menu then content
       -- could only ever collect the free space on the right. */
    grid-template-columns: minmax(0, 1fr) 280px minmax(0, 62rem) minmax(0, 1fr);
  }

  .site-header {
    grid-column: 1 / -1;
    grid-row: 1;
    /* Owner, 2026-10-28: the search box and the profile corner have to stay
       reachable, or reading a long feed means scrolling all the way back up for
       them. Sticky rather than fixed: it keeps its grid row, so nothing needs a
       spacer, and it still travels inside the body's grid area. The background
       is the page's own colour -- the band was transparent only because nothing
       ever passed under it -- and the worn rail below it rides along. */
    position: sticky;
    top: 0;
    z-index: 30;
    background: var(--black);
  }

  main {
    grid-column: 1 / -1;
    grid-row: 2;
    /* `.container` centres itself with `margin: 0 auto`, and auto margins on a
       grid item defeat the default stretch: the item shrink-wraps to its
       content's max-content instead. So the reading column sized itself to the
       text on the page -- measured at 1440px, the Local feed rendered 486px wide
       against Following's 721px for the same layout, purely because those posts
       had fewer words. As a block child of a block body the same declaration was
       simply centring, which is why this only surfaced once body became a grid.
       Width 100% restores the fill; `max-width` still caps the column and the
       auto margins still centre it once it is capped. */
    width: 100%;
  }

  /* body > because home puts its footer inside the rail instead (R131), and
     .rail is a grid of its own -- an unscoped rule would place the rail's
     footer in the body's tracks and drop it out of the column it belongs to. */
  body > .site-footer {
    grid-column: 1 / -1;
    grid-row: 3;
  }

  /* With a menu, the content and the footer move into the capped content track
     and the menu takes the track to its left; the two auto tracks on the outside
     are the gutters (N8). */
  body:has(.site-nav) main,
  body:has(.site-nav) > .site-footer {
    grid-column: 3;
  }

  /* Slim, and full-bleed in its paint: the texture and the worn rail underneath
     it still span the viewport. Its *content* is capped to the band (menu track
     plus content track) and centred, so the wordmark sits above the menu and the
     profile corner above the rail's right edge instead of out at the window
     edges -- the N8 pick. Uncapped, the corner would float away from the column
     it belongs to at wide widths. */
  .site-header .container {
    max-width: calc(280px + 62rem);
    margin: 0 auto;
  }

  .header-top {
    grid-template-columns: 252px minmax(200px, 480px) 1fr;
    gap: 1.25rem 1.75rem;
    padding: 0.75rem 1.75rem;
  }

  /* 2.6rem, not the 2.2rem this bar shipped with. Monoton's bars are about 1px
     apart on a curve, and at 2.2rem that is below what the pixel grid can hold,
     so the arcs stair-step no matter how the bloom is tuned — the moire on the R,
     the a and the k. The tube layer already rasterises at 3x and scales back;
     giving it more real pixels is what actually closes the artifact. Measured with
     the bloom held constant (resolvable bar edges / isolated single-pixel ink):
     2.2rem 75 / 9.5%, 2.4rem 79 / 2.7%, 2.5rem 81 / 4.0%, 2.6rem 83 / 0.5%.
     It is free, which is why it is here rather than being a design argument: the
     bar's height is set by the profile corner at 44px, not by the wordmark at 35px,
     and measured on the live page the header stays 71px all the way to 2.6rem and
     only grows at 3rem. What does bound this size is the menu column — 252px wide,
     and the wordmark's ink is 231px here — so do not push past about 2.7rem without
     widening that track. */
  .brand {
    font-size: 2.6rem;
  }

  .header-user {
    gap: 1.25rem;
  }

  .site-nav {
    display: flex;
    flex-direction: column;
    grid-column: 2;
    grid-row: 2;
    /* The column scrolls with the page until the menu fills the viewport,
       then sticks -- the approved behaviour, and the reason the menu is a
       column rather than a fixed overlay. It sticks below the sticky header,
       not under it: at top:0 the header painted over the Feed row. */
    position: sticky;
    top: var(--header-h);
    align-self: start;
    box-sizing: border-box;
    max-height: calc(100vh - var(--header-h));
    overflow-y: auto;
    padding: 16px 0;
    background: rgba(22, 19, 17, 0.94);
    border-right: 1px solid #40372f;
  }

  /* One row shape for both kinds of destination: an anchor navigates, the Log
     out row acts, and a reader must not be able to tell them apart. The bare
     <button> blocks would otherwise dress the Log out row in Bebas caps with
     bloom, so it is un-dressed here the way the More sheet un-dresses its rows. */
  .site-nav a,
  .site-nav form.inline button {
    display: flex;
    align-items: center;
    gap: 18px;
    width: 100%;
    box-sizing: border-box;
    min-height: 54px;
    padding: 0 28px;
    color: #c8bdad;
    background: none;
    border: 0;
    box-shadow: none;
    font-size: 1rem;
    text-align: left;
    text-decoration: none;
    text-transform: none;
    letter-spacing: normal;
  }

  .site-nav svg {
    width: 23px;
    height: 23px;
    flex: none;
    fill: none;
    stroke: currentColor;
    stroke-width: 1.7;
    stroke-linecap: round;
    stroke-linejoin: round;
  }

  /* The unread count rides the Notifications bell (owner ruling
     2026-11-04): the wrapper is what the bubble sits on, and the bubble
     repeats the phone corner's treatment -- red pill, white numeral --
     so one visual language names unread everywhere. */
  .site-nav .nav-icon {
    position: relative;
    display: inline-flex;
    flex: none;
  }

  .site-nav .nav-count {
    position: absolute;
    top: -7px;
    right: -12px;
    font: 700 0.62rem/1 var(--ui);
    background: var(--red);
    color: #fff;
    border-radius: 0.6rem;
    padding: 0.16rem 0.34rem;
  }

  .site-nav a:hover,
  .site-nav form.inline button:hover {
    background: #2b241e;
    color: #f5e4ca;
  }

  /* The lit row is amber text only. The retired row's active state was a neon
     tube under the label, which has no meaning in a vertical column. */
  .site-nav a.active {
    color: #f1c88d;
    text-shadow: none;
  }

  /* A rule opens each new group (NavItem.group); the partial draws it, this
     gives it the mockup's spacing. */
  .site-nav hr {
    width: 100%;
    border: 0;
    border-top: 1px solid #493d32;
    margin: 16px 0;
  }
}

h1 {
  font-size: 1.6rem;
  margin: 1.5rem 0 1rem;
}

form p {
  margin: 0 0 0.25rem;
}

form label {
  display: block;
  font-weight: 600;
  margin-bottom: 0.25rem;
}

.find-form {
  display: grid;
  gap: 0.75rem;
  justify-items: start;
}

input[type="text"],
input[type="email"],
input[type="password"] {
  width: 100%;
  padding: 0.45rem 0.6rem;
  font: inherit;
  color: inherit;
  background: var(--field);
  border: 1px solid var(--brown);
  border-radius: 4px;
}

input:focus {
  outline: 2px solid var(--accent);
  outline-offset: 0;
  border-color: var(--accent);
}

button,
.btn {
  display: inline-block;
  margin-top: 1rem;
  padding: 0.5rem 1.1rem;
  font: inherit;
  font-weight: 600;
  color: var(--cream);
  background: var(--blood-red);
  border: none;
  border-radius: 4px;
  cursor: pointer;
  /* An anchor dressed as a control must not keep the link's underline: the
     browser default applies to <a> and nothing here overrode it, so every
     <a class="btn"> (Edit profile, Edit, Sign up) read as underlined text
     while its <button class="btn"> siblings did not — same control, two
     looks. Set on the shared rule so the tag stops mattering. */
  text-decoration: none;
}

button:hover {
  filter: brightness(1.1);
}

/* Small inline form (header log-out button). */
form.inline {
  display: inline;
  margin: 0;
}

form.inline button {
  margin: 0;
  padding: 0.25rem 0.7rem;
  font-size: 0.9rem;
  background: none;
  color: var(--muted);
  border: 1px solid var(--border);
  box-shadow: none;
}

form.inline button:hover {
  color: var(--accent);
  border-color: var(--accent);
  filter: none;
  box-shadow: none;
}

ul.messages {
  list-style: none;
  padding: 0;
  margin: 1rem 0;
}

ul.messages li {
  padding: 0.5rem 0.75rem;
  border-radius: 4px;
  margin-bottom: 0.5rem;
  background: var(--surface);
  border: 1px solid var(--border);
}

ul.messages li.error {
  background: rgba(212, 43, 38, 0.2);
  border-color: var(--red);
  color: #e9a58f;
}

ul.errorlist {
  color: var(--error);
  font-size: 0.9rem;
  margin: 0.25rem 0 0;
  padding-left: 1.2rem;
}

/* --- Film page (M1 increment 5) ------------------------------------------ */

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

.film {
  display: flex;
  gap: 1.25rem;
  margin-top: 1.5rem;
}

.film-poster img,
.poster-placeholder {
  width: 10rem;
  height: 15rem;
  object-fit: cover;
  border-radius: 4px;
  border: 1px solid var(--border);
}

.poster-placeholder {
  display: flex;
  align-items: center;
  justify-content: center;
  background: var(--surface);
  color: var(--muted);
  font-size: 0.85rem;
}

.film-meta h1 {
  margin-top: 0;
}

.meta-list div {
  display: flex;
  gap: 0.5rem;
  margin: 0.15rem 0;
}

.meta-list dt {
  font-weight: 600;
  min-width: 6rem;
  color: var(--muted);
}

.meta-list dd {
  margin: 0;
}

/* Narrow screens (owner pass, 2026-09-20): side by side, the 6rem label column
   left the value only 74px at a 390px viewport, so the cast wrapped to thirteen
   lines down the right edge. The poster and title become a centred plate and each
   field stacks label-over-value across the full column. Scoped to `.film` so the
   About page's short meta-list keeps the two-column shape it reads fine in. */
@media (max-width: 40rem) {
  .film {
    flex-direction: column;
    gap: 1.15rem;
  }

  .film-poster {
    align-self: center;
  }

  .film-meta h1 {
    text-align: center;
  }

  .film .meta-list div {
    display: block;
    margin: 0.8rem 0 0;
  }

  .film .meta-list dt {
    min-width: 0;
    font-size: 0.72rem;
    letter-spacing: 0.14em;
    text-transform: uppercase;
  }

  .film .meta-list dd {
    margin-top: 0.2rem;
    line-height: 1.55;
  }
}

/* Star rating: a dim background row with a gold foreground row clipped to the
   rating's width. Shared by read-only display and the interactive widget. */
.stars {
  position: relative;
  display: inline-block;
  font-size: 1.25rem;
  line-height: 1;
  white-space: nowrap;
}

.stars-bg,
.stars-fg {
  letter-spacing: 0;
}

.stars-bg {
  color: var(--star-empty);
}

.stars-fg {
  color: var(--gold);
  position: absolute;
  top: 0;
  left: 0;
  width: 0;
  overflow: hidden;
}

.review-list {
  list-style: none;
  padding: 0;
  margin: 1rem 0;
}

.review {
  padding: 0.75rem 0;
  border-bottom: 1px solid var(--border);
  /* Containing block for the row's stretched open-the-post link. Without it
     the overlay would size itself to the nearest positioned ancestor and
     cover whatever else wears that name. */
  position: relative;
}

/* The whole feed row opens its post (owner ask, restated 2026-09-28). A real
   anchor stretched over the row rather than a JS click handler on the <li>:
   a list item is not focusable, so a scripted row would be unreachable by
   Tab and would lose middle-click / ctrl-click open-in-a-new-tab. The anchor
   carries no content, so no control can be nested inside it — which also
   keeps this out of invalid-HTML territory, since review prose is rendered
   markdown and can contain links of its own. */
.review-open {
  position: absolute;
  inset: 0;
  z-index: 0;
  cursor: pointer;
}

/* Everything interactive inside the row paints above that overlay, or the
   overlay swallows its clicks. Scoped to the three containers a row is made
   of rather than listed control by control, so a control added to a row
   later is covered by the rule instead of silently losing its click. */
.review-head a,
.review-head button,
.feed-item a,
.review-body a {
  position: relative;
  z-index: 1;
}

/* Post prose reads white, not cream (owner pass, 2026-10-04). Site-wide by the
   owner's explicit choice, so a feed row and the post it opens agree. Links
   inside the rendered markdown keep --accent: prose and links must not match. */
.review-body {
  color: var(--white);
}

/* The row deliberately carries no hover treatment on its prose — the owner
   removed the underline-on-hover signal on 2026-10-04. The overlay still has
   cursor: pointer, so the row reads as clickable without the text lighting up.
   Do not re-add it: it is the one thing here that was taken away on purpose. */

/* The way forward at the foot of the feed (§2I increment 2, R132 decision 6).
   Deliberately NOT `.btn`: this is a link to more of what the reader is already
   looking at, not a command, and a solid lit-red block under every page of the
   feed would outshout the rows it follows. Quiet centred text link, with the
   same underline-on-hover signal the row's own links use. */
.feed-more {
  text-align: center;
  margin: 1.25rem 0 0;
}

.feed-older {
  color: var(--cream-muted);
  font-weight: 600;
  text-decoration: none;
  border-bottom: 1px solid var(--border);
  padding-bottom: 2px;
}

.feed-older:hover,
.feed-older:focus-visible {
  color: var(--link);
  border-bottom-color: var(--link);
}

/* The end of the feed (§2I increment 3, R132 decision 7). It lives inside the
   list as a sibling of the rows, so it sheds the row chrome and reads as a
   closing line rather than another post. */
.feed-end {
  padding: 1.25rem 0 0.25rem;
  color: var(--cream-muted);
  text-align: center;
  border-bottom: none;
}

/* The scroll sentinel (§2I increment 3). It has to occupy a little height to
   cross the viewport edge while scrolling, and nothing else: the observer is
   watching when it appears, not what it looks like. */
.feed-sentinel {
  height: 1px;
  margin-top: 0.5rem;
}

.review-head {
  display: flex;
  flex-wrap: wrap;
  gap: 0.75rem;
  align-items: center;
  margin-bottom: 0.25rem;
  font-size: 0.95rem;
}

/* A post's date is plain text, never a link (owner pass, 2026-10-04). On the
   feed the row already opens through .review-open, so the linked date was a
   second way to the same page — and it read as red underlined text. White
   rather than --muted so it sits with the prose instead of receding from it. */
.post-date {
  color: var(--white);
}

/* The audience marker (visibility V1). A member has to be able to tell at a
   glance which audience a post went to, and a drawing is the cheapest way to
   say it without a sentence. Only rows the reader is allowed to read ever
   carry one - a private row is invisible to everyone but its author - so the
   marker never advertises a post nobody may open.

   It was a word inside a bordered label until the owner's pass of 2026-11-07,
   which took the rule off and left the bare drawing in the row's metadata
   line, in the muted brown the date and every other small fact on the row
   already uses. The word survives as the tooltip and the accessible name on the
   wrapper, so the drawing never has to be memorised to be read. The three
   drawings are inline in ``templates/_audience_tag.html`` and take this colour
   through ``currentColor``, which is why nothing here sets a fill. */
.audience {
  align-items: center;
  color: var(--muted);
  display: inline-flex;
  flex: none;
}

.audience svg {
  display: block;
  height: 1rem;
  width: 1rem;
}

/* The audience choice in the finish modal (visibility V1). The modal's other
   controls are a star row and a textarea, so this stays a plain fieldset: two
   options, one legend, nothing to learn. The thin brown rule and the small
   uppercase legend are the treatment every other metadata label in the app
   already wears, so the control does not arrive as a new kind of chrome. */
.audience-choice {
  border: 1px solid var(--line);
  margin: 0.75rem 0;
  padding: 0.4rem 0.75rem 0.5rem;
}

.audience-choice legend {
  color: var(--muted);
  font-family: var(--ui);
  font-size: 0.78rem;
  letter-spacing: 0.06em;
  padding: 0 0.4rem;
  text-transform: uppercase;
}

.audience-choice label {
  align-items: center;
  display: inline-flex;
  gap: 0.35rem;
  margin: 0.15rem 1.25rem 0 0;
}

/* The one line the New list page puts under its radios (W-arc W3): there the
   audience is fixed at creation and the edit page offers no control, so the
   fieldset has to carry the caveat itself. Small and muted because it is a
   caveat and not a fourth option, and it sits inside the box's own padding
   rather than on a paragraph's default margins. */
.audience-choice .audience-note {
  font-size: 0.82rem;
  margin: 0.45rem 0 0.1rem;
}

/* The report box's free-text field (_report_form.html, on the post page and
   the profile). It has never had a rule of its own, so it opens as a
   browser-default white plate with black text in the middle of a page built
   out of near-black browns. Same field treatment as every other textarea on
   this theme; the layout was already fine, this is the colour. */
.report-form textarea {
  width: 100%;
  max-width: 42rem;
  padding: 0.45rem 0.6rem;
  font: inherit;
  color: inherit;
  background: var(--field);
  border: 1px solid var(--brown);
  border-radius: 4px;
  margin-top: 0.25rem;
}

.review-author {
  font-weight: 600;
  /* Remote handles like fedb@192.168.1.138:3031 are one unbreakable word —
     let it break so narrow screens don't scroll sideways. */
  overflow-wrap: anywhere;
}

/* Delete-review control (M5 increment 4): right-aligned in the head row. The
   more specific selector overrides form.inline's `margin: 0`. */
.review-head form.review-delete {
  margin-left: auto;
}

/* The notifications ledger (M3, owner ruling D6). An unseen row is one newer
   than the member's mark-read timestamp — the same comparison the bell counts
   with, drawn here as an amber left rule and brighter text, so "new since you
   last looked" reads without anyone having to count the badge.

   The rule is on every row, transparent until lit: a border that appeared only
   on an unseen row would shove that row's own text sideways, so the list would
   stutter between seen and unseen rows. Amber is the accent the house already
   uses for "this one is lit" (the active nav row, the focus ring), not the red
   that names an action. */
.notifications-feed .review {
  border-left: 3px solid transparent;
  padding-left: 0.75rem;
}

.notifications-feed .review--unseen {
  border-left-color: var(--amber);
}

.notifications-feed .review--unseen .review-head {
  color: var(--white);
}

/* The film a row is about (owner ruling D7). The row's sentence is cream and
   its links are red; the film sits between the two — the white of post prose
   at the weight the row's own author name uses — so it reads as the subject of
   the line rather than a second door to the same post. */
.notif-film {
  color: var(--white);
  font-weight: 600;
}

/* Applaud control (owner pass, 2026-10-05 — icon-only, replacing the pill).

   The resting icon reports THREE states, not two, because it is read as
   reporting who has applauded:

     you applauded              -> solid red      data-state="mine"
     others applauded, not you  -> red outline    data-state="others"
     nobody applauded           -> white outline  data-state="idle"

   Hover is a uniform scale(1.08) across all three states. The supplied
   white-glow art is NOT used — the owner rejected the outside glow, and a
   brightness lift cannot stand in for it on the idle icon because that art
   is already at 253,253,253 and clamps at 255.

   Both facts the state needs are already on the row (liked_by_viewer and
   like_count), so this needed no model change. data-state is derived in the
   template and recomputed by likes.js after each toggle.

   The base `button` rule paints a lit red mottle with a neon rim and a
   four-stop bloom, and carries margin-top: 1rem. Both are reset here — the
   pill version's first render showed that glow sitting around the art, and
   without the margin reset the control hangs 16px below the avatar.

   The three shipped PNGs were NOT drawn the same size. At alpha>=200 the
   clapperboard bodies measured 1059x973 (white outline), 1028x976 (red
   outline) and 1023x989 (solid red). They are registered by core AREA,
   centred on the core centre, so changing state never resizes the
   clapperboard. Registering by ink bbox instead would have shifted it. */
.applaud {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  vertical-align: middle;
}

.applaud-btn {
  width: 26px;
  height: 26px;
  padding: 0;
  border: 0;
  background: url("../images/applaud-icon-idle.e2a8ed789dfa.png") center / contain no-repeat;
  background-color: transparent;
  box-shadow: none;
  text-shadow: none;
  margin-top: 0;
  cursor: pointer;
}

.applaud-btn[data-state="others"] {
  background-image: url("../images/applaud-icon-others.d60c399aa187.png");
}

.applaud-btn[data-state="mine"] {
  background-image: url("../images/applaud-icon-mine.714c4d113b92.png");
}

/* Uniform scale, not a brightness lift. The idle art is already at
   253,253,253, so brightness() clamps at 255 and is invisible on it — a
   lift would have registered on the red states only, leaving the three
   states feeling inconsistent. transform is paint-only, so the row never
   reflows.

   The box-shadow and filter resets here are load-bearing, not decoration.
   `button:hover, .btn:hover` paints a five-stop red bloom and `button:hover`
   adds filter: brightness(1.1); both are (0,1,1) and therefore OUTSPECIFY the
   (0,1,0) `.applaud-btn` resets in the base rule. Without repeating them on
   the hover selector the icon lights up with the site's button halo the moment
   the cursor arrives. */
.applaud-btn:hover {
  transform: scale(1.08);
  box-shadow: none;
  filter: none;
}

.applaud-btn:disabled {
  filter: saturate(0.5) brightness(0.7);
  cursor: default;
  box-shadow: none;
}

/* Mono on purpose: the digits are the one piece of this control that is real
   text, and the site's lettering is a typewriter face. The number is always
   white and never tracks the icon: the icon alone carries who applauded, so a
   red number would be a second, redundant copy of that signal. */
.applaud-count {
  font-family: ui-monospace, "DejaVu Sans Mono", "Liberation Mono", monospace;
  font-weight: 700;
  font-size: 1rem;
  color: var(--white);
}

/* Reply control (owner pass, 2026-10-05). Sits immediately after the applaud
   control and follows the same visual contract — 26px icon, plain monospace
   count, no border, uniform scale(1.08) on hover with the same load-bearing
   box-shadow/filter resets against the base `button:hover` bloom.

   TWO states, not three. The owner chose these over the applaud's three on the
   grounds that the third state would have had to mean "you replied", and a
   reply is not reversible the way a like is — nothing this control does can
   take one back, so an icon claiming authorship of a reply would be a claim
   the control cannot act on.

     post has replies  -> red outline  data-state="others"
     no replies yet    -> white outline data-state="idle"

   The solid-red artwork was therefore NOT shipped: ManifestStaticFilesStorage
   hashes and serves every file in the static tree whether or not a rule
   points at it, so an unused PNG is dead weight on every deploy.

   Unlike the applaud this is an <a>, not a <button> — it navigates rather
   than toggling, so it must be a real link for middle-click, open-in-new-tab
   and Tab order. Two consequences handled here rather than in the template:
   `transform` does not apply to a non-replaced inline element, hence
   display: inline-block; and the base `a` rule gives it --link, which must
   be overridden to keep the icon's own ink as the only colour on it. */
.reply {
  display: inline-flex;
  align-items: center;
  gap: 6px;
  vertical-align: middle;
}

.reply-btn {
  display: inline-block;
  width: 26px;
  height: 26px;
  padding: 0;
  border: 0;
  background: url("../images/reply-icon-idle.c9a537437ff3.png") center / contain no-repeat;
  background-color: transparent;
  box-shadow: none;
  text-shadow: none;
  margin-top: 0;
  cursor: pointer;
}

.reply-btn[data-state="others"] {
  background-image: url("../images/reply-icon-others.a2e0ad62b9e1.png");
}

.reply-btn:hover,
.reply-btn:focus-visible {
  transform: scale(1.08);
  box-shadow: none;
  filter: none;
}

/* Same mono treatment and the same always-white rule as .applaud-count: the
   number is a count, not a status, and the icon carries the status. */
.reply-count {
  font-family: ui-monospace, "DejaVu Sans Mono", "Liberation Mono", monospace;
  font-weight: 700;
  font-size: 1rem;
  color: var(--white);
}

/* Shelve/edit controls under the film header. */
.film-actions {
  display: flex;
  gap: 0.75rem;
  align-items: center;
  flex-wrap: wrap;
  margin-top: 1rem;
}

.film-actions form {
  margin: 0;
}

/* Interactive star rating: the read-only .stars fill plus a layer of ten
   invisible half-star hit zones (see reeltalk.js). */
.star-rating {
  position: relative;
  display: inline-block;
}

.star-hits {
  position: absolute;
  inset: 0;
  display: flex;
  cursor: pointer;
}

.star-hits span {
  flex: 1 1 0;
  height: 100%;
}

/* Finish-flow modal (mark watched / edit review). */
.modal {
  position: fixed;
  inset: 0;
  z-index: 100;
  display: flex;
  align-items: center;
  justify-content: center;
  padding: 1rem;
}

.modal[hidden] {
  display: none;
}

.modal-backdrop {
  position: absolute;
  inset: 0;
  background: rgba(0, 0, 0, 0.72);
}

.modal-dialog {
  position: relative;
  background: var(--surface);
  border: 1px solid var(--border);
  border-radius: 6px;
  padding: 1.25rem 1.5rem 1.5rem;
  width: 100%;
  max-width: 26rem;
}

.modal-dialog h2 {
  margin-top: 0;
  font-size: 1.2rem;
}

.modal-dialog .star-rating .stars {
  font-size: 2rem;
}

/* The reply composer (feed interactions increment 4). Deliberately no new
   look: the textarea takes the identical field treatment the review modal
   gives its own — a bare `<textarea>` on this dark theme otherwise renders
   as a browser-default white box, which is the same class of trap as the
   caps face on a bare `<button>`. Nothing here is invisible in the diff and
   only a browser catches it. */
.reply-form {
  margin-top: 1.25rem;
}

.modal-dialog textarea,
.reply-form textarea {
  width: 100%;
  padding: 0.45rem 0.6rem;
  font: inherit;
  color: inherit;
  background: var(--field);
  border: 1px solid var(--brown);
  border-radius: 4px;
  margin-top: 0.25rem;
}

.modal-dialog button {
  margin-top: 1rem;
}

.reply-form button {
  margin-top: 0.75rem;
}

/* "replying to @x" on a flat thread row, and the orphan line on a reply
   whose parent is a tombstone. Both are metadata, so both take the muted
   metadata face at the row's own size rather than the body size. */
.reply-to,
.reply-parent-deleted {
  font-family: var(--ui);
  font-size: 0.85rem;
}

.required {
  color: var(--error);
}

/* Inline error line (e.g. a failed /find/ lookup). */
.error {
  color: var(--error);
}

/* --- User films page (M1 increment 6) ------------------------------------- */

.profile-head {
  display: flex;
  align-items: center;
  gap: 0.75rem;
  /* At a 320px viewport the avatar, the handle and the Follow control cannot
     share one row, and the control was pushed 33px past the window edge. The
     row wraps instead; nothing about the desktop row changes. */
  flex-wrap: wrap;
}

/* Every avatar disc, at every size: a worn cream bezel with saturated red hugging
   the portrait inside it — the same hot-core-in-coloured-glass family as the nav
   tube and the wordmark. Sizes are rem so they scale with the root font. */
.avatar {
  width: 3rem;
  height: 3rem;
  border-radius: 50%;
  object-fit: cover;
  flex: none;
  border: 2px solid var(--avatar-ring);
  box-shadow: inset 0 0 0 2px rgba(196, 30, 24, 0.85), 0 0 7px rgba(255, 65, 56, 0.25);
}

/* Row heads are compact; the marquee corner and the profile pages share the base size. */
.avatar-row {
  width: 2.05rem;
  height: 2.05rem;
}

.profile-head h1 {
  margin: 0.5rem 0 0;
}

/* --- Profile page (M5) ---------------------------------------------------- */

/* No uploaded avatar — every new account and most remote mirrors: a hand-drawn
   silhouette on a distressed red-to-black plate, so an empty disc still reads as
   lit rather than broken. */
.avatar-placeholder {
  display: inline-block;
  background: radial-gradient(circle at 50% 34%, #d9b78e 0 15%, transparent 16%),
    radial-gradient(ellipse 78% 46% at 50% 96%, #d9b78e 0 52%, transparent 53%),
    linear-gradient(160deg, #7e1a15, #14100e);
}

.profile-id {
  display: flex;
  flex-direction: column;
}

/* Follow / edit control, right-aligned on the profile head row. */
.profile-actions {
  margin-left: auto;
}

.handle {
  margin: 0.25rem 0 0;
  color: var(--muted);
  font-size: 0.9rem;
}

/* Audience size under the handle (reviewer-discovery increment): reads as
   quiet metadata beside it, with the numbers a shade brighter so they carry
   the glance. */
.profile-counts {
  margin: 0.2rem 0 0;
  color: var(--muted);
  font-size: 0.9rem;
}

.profile-count {
  color: var(--cream-muted);
}

.profile-count-sep {
  margin: 0 0.3rem;
}

.profile-summary {
  margin: 1rem 0;
}

.tabs {
  display: flex;
  gap: 0.25rem;
  border-bottom: 1px solid var(--border);
  margin-top: 1.25rem;
}

.tabs a {
  padding: 0.4rem 0.9rem;
  color: var(--muted);
  /* The nav row's size, so the two read as one type (owner pass, 2026-10-04). */
  font-size: 0.88rem;
  text-decoration: none;
  border-bottom: 2px solid transparent;
  margin-bottom: -1px;
}

.tabs a:hover {
  color: var(--link);
}

.tabs a.active {
  color: var(--fg);
  font-weight: 600;
  border-bottom-color: var(--accent);
}

.film-list {
  list-style: none;
  padding: 0;
  margin: 1rem 0;
}

.film-row {
  display: flex;
  align-items: center;
  gap: 0.75rem;
  padding: 0.5rem 0;
  border-bottom: 1px solid var(--border);
}

.film-row .thumb,
.feed-item .thumb,
.list-strip-poster,
.thumb-placeholder {
  width: 2.5rem;
  height: 3.75rem;
  object-fit: cover;
  border-radius: 3px;
  border: 1px solid var(--border);
  flex-shrink: 0;
}

.thumb-placeholder {
  background: var(--surface);
}

.film-row a {
  text-decoration: none;
}

.film-row a:hover {
  color: var(--link);
}

/* --- Home feed (M1 increment 6) -------------------------------------------- */

.feed h2 {
  margin-top: 1.5rem;
}

/* R34: poster thumb beside the event text on film-anchored rows. */
.feed-item {
  display: flex;
  align-items: center;
  gap: 0.75rem;
  margin: 0.25rem 0;
}

.feed-film {
  margin: 0.25rem 0;
  font-weight: 600;
}

.feed-item .feed-film {
  margin: 0;
}

/* --- The list row (lists increment 4, R139) ---------------------------------
   Three lines: the verb in the head row, the title here, then the poster
   strip. Nothing about the row is new chrome — it reuses the head, the tile
   size and the text colours every other feed row already wears. */
.feed-verb {
  color: var(--cream);
}

.list-strip {
  margin: 0.25rem 0;
}

.list-strip-title {
  margin: 0.25rem 0;
  font-weight: 600;
  color: var(--white);
}

/* The strip never wraps. The cap is what keeps the row short, so a wrapped
   strip would be the worst of both: the tiles it has room for on line one,
   and the +N stranded on a line of its own reading as a count of nothing.
   overflow:hidden is the backstop for a column narrower than five tiles,
   which the cap makes a corner case rather than the normal render. */
.list-strip-posters {
  display: flex;
  flex-wrap: nowrap;
  align-items: center;
  gap: 0.5rem;
  margin-top: 0.4rem;
  overflow: hidden;
}

/* Secondary colour, vertically centred against the tiles: it reads as "and
   more in here", not as a sixth tile. */
.list-strip-count {
  flex-shrink: 0;
  color: var(--cream-muted);
  font-weight: 600;
  font-size: 0.9rem;
}

/* --- Landing/about + footer (M1 increment 7) --------------------------------- */

.landing-desc {
  font-size: 1.05rem;
}

.about-instance h2 {
  margin-top: 1.5rem;
  font-size: 1.2rem;
}

/* --- Footer (owner pass, 2026-09-19) ---------------------------------------
   Three zones on the worn chrome rail: the wordmark and tagline bottom-left,
   the wayfinding links in the middle, and a lit neon sign-off with a film reel
   on the right. The band runs as wide as the marquee above it (72rem) so its
   edges line up with the header and the home rail. */
.site-footer {
  position: relative;
  border-top: 3px solid var(--black-2);
  margin-top: 2rem;
}

.site-footer .container {
  max-width: 72rem;
  display: grid;
  grid-template-columns: 1fr auto 1fr;
  align-items: center;
  gap: 1.5rem;
  padding-top: 1.6rem;
  padding-bottom: 2.4rem;
}

.site-footer a {
  color: var(--muted);
  text-decoration: none;
  font-size: 0.9rem;
}

.site-footer a:hover {
  color: var(--cream);
}

.footer-brand {
  display: flex;
  align-items: baseline;
  flex-wrap: wrap;
  gap: 0.25rem 0.9rem;
  min-width: 0;
}

.footer-wordmark {
  font-family: var(--display);
  font-size: 2.4rem;
  line-height: 1;
  letter-spacing: 0.03em;
  text-transform: uppercase;
  color: var(--cream);
}

.footer-tagline {
  font-size: 0.72rem;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--muted);
}

.footer-links {
  display: flex;
  align-items: center;
  justify-content: center;
  flex-wrap: wrap;
  gap: 0.7rem;
}

/* nowrap on the link, not the row: when the row runs out of room it breaks
   between links instead of inside one, so "About This Site" never becomes
   "About This" over "Site". */
.footer-links a {
  font-size: 0.82rem;
  white-space: nowrap;
}

.footer-sep {
  color: #4a3a2c;
  user-select: none;
}

.footer-signoff {
  display: flex;
  align-items: center;
  justify-content: flex-end;
  gap: 0.55rem;
}

/* Neon script sign-off: the same hot-core-in-coloured-glass reading as the nav
   tube (R67) and the wordmark (R68), set at a slight tilt like bent tubing. */
.footer-neon {
  font-family: var(--script);
  font-size: 1.9rem;
  line-height: 1;
  color: #ff5f4d;
  transform: rotate(-3deg);
  text-shadow:
    0 0 3px rgba(255, 130, 110, 0.9),
    0 0 10px rgba(255, 65, 56, 0.75),
    0 0 24px rgba(255, 45, 32, 0.5),
    0 0 46px rgba(255, 30, 20, 0.3);
}

.footer-reel {
  width: 2rem;
  height: 2rem;
  flex: none;
  color: var(--red-bright);
  filter: drop-shadow(0 0 4px rgba(255, 65, 56, 0.8)) drop-shadow(0 0 12px rgba(255, 45, 32, 0.45));
}

@media (max-width: 40rem) {
  .site-footer .container {
    grid-template-columns: 1fr;
    justify-items: center;
    gap: 1rem;
    padding-top: 1.3rem;
    padding-bottom: 2rem;
  }

  .footer-brand {
    justify-content: center;
    text-align: center;
  }

  .footer-wordmark {
    font-size: 2rem;
  }

  .footer-signoff {
    justify-content: center;
  }

  /* Below this width the row cannot promise a pipe always lands between two
     links — at 320px one strands at the end of the first line. The separators
     are dropped here for the same reason they are dropped in the rail. */
  .footer-sep {
    display: none;
  }

  .footer-neon {
    font-size: 1.6rem;
  }

  .footer-reel {
    width: 1.7rem;
    height: 1.7rem;
  }
}

/* --- Global search + suggest dropdown (M2 increment 4) ---------------------- */

.global-search {
  position: relative;
}

/* Wide centered search box (M6 artwork B); the suggest dropdown anchors to
   its bottom edge via the form's position:relative. */
.global-search input[type="search"] {
  width: 100%;
  padding: 0.5rem 0.9rem;
  font: inherit;
  color: inherit;
  background: var(--field);
  border: 1px solid var(--steel);
  border-radius: 4px;
}

.suggest-list {
  position: absolute;
  top: calc(100% + 4px);
  left: 0;
  right: 0;
  z-index: 50;
  list-style: none;
  margin: 0;
  padding: 0.25rem 0;
  background: var(--surface);
  border: 1px solid var(--border);
  border-radius: 4px;
  box-shadow: 0 4px 16px rgba(0, 0, 0, 0.55);
}

.suggest-list a {
  display: flex;
  align-items: center;
  gap: 0.5rem;
  padding: 0.35rem 0.75rem;
  color: var(--fg);
  text-decoration: none;
}

.suggest-list a:hover,
.suggest-list a.active {
  /* R32: keyboard highlight matches the mouse hover. */
  background: var(--surface-2);
}

/* R31: poster thumbnail in the dropdown rows (placeholder when missing). */
.suggest-thumb {
  width: 1.6rem;
  height: 2.4rem;
  object-fit: cover;
  border-radius: 2px;
  border: 1px solid var(--border);
  flex-shrink: 0;
}

.suggest-thumb-placeholder {
  background: var(--surface);
}

.search-row-main {
  flex: 1;
}

.search-row .watchlist-btn {
  margin-top: 0;
  padding: 0.25rem 0.7rem;
  font-size: 0.9rem;
  background: none;
  color: var(--accent);
  border: 1px solid var(--border);
  box-shadow: none;
}

.search-row .watchlist-btn:hover {
  border-color: var(--accent);
  filter: none;
  box-shadow: none;
}

.search-row .watchlist-btn:disabled {
  color: var(--muted);
  cursor: default;
  border-color: var(--border);
  box-shadow: none;
  filter: none;
}

.pager {
  display: flex;
  gap: 1rem;
  margin-top: 1rem;
}

/* --- File import/export (M3) ----------------------------------------------- */

table.results {
  width: 100%;
  border-collapse: collapse;
  font-size: 0.9rem;
  margin: 1rem 0;
}

table.results th,
table.results td {
  text-align: left;
  padding: 0.35rem 0.6rem;
  border-bottom: 1px solid var(--border);
}

table.results th {
  color: var(--muted);
  font-weight: 600;
}

/* --- Welcome / getting-started page (M6) ----------------------------------- */

.welcome-steps {
  margin-top: 1.5rem;
}

.step {
  display: flex;
  gap: 0.9rem;
  padding: 0.9rem 0;
  border-bottom: 1px solid var(--border);
}

/* The step discs carry the same lit-red recipe as the buttons (owner pass,
   2026-09-19): mottled crimson under a hot rim, bloom scaled to the disc and
   kept as tight as the reference's halo. */
.step-num {
  flex-shrink: 0;
  width: 2rem;
  height: 2rem;
  display: flex;
  align-items: center;
  justify-content: center;
  font-weight: 700;
  color: var(--cream);
  background-color: #861713;
  background-image: var(--neon-mottle), radial-gradient(circle at 50% 28%, #a0221b, #6d1210);
  border: 2px solid var(--neon-rim);
  border-radius: 50%;
  box-shadow:
    inset 0 0 7px rgba(255, 74, 52, 0.5),
    0 0 3px rgba(255, 96, 74, 0.8),
    0 0 8px rgba(255, 45, 32, 0.42);
  text-shadow: 0 1px 2px rgba(46, 2, 2, 0.8);
}

.step-body h2 {
  margin: 0.1rem 0 0.35rem;
  font-size: 1.15rem;
}

.step-body p {
  margin: 0;
  color: var(--muted);
}

/* --- Help, the member FAQ (2026-11-06) --------------------------------------
   The contents box is the only chrome this page needs: a member arrives holding
   a question, so the groups are listed up front and each one carries the id the
   listing points at. Two columns where there is room for two, one on a phone,
   and nothing that needs JavaScript to work. */

.help-contents {
  margin: 1.5rem 0 2rem;
  padding: 1rem 1.2rem;
  border: 1px solid var(--border);
  border-radius: 4px;
}

.help-contents h2 {
  margin: 0 0 0.6rem;
  font-family: var(--ui);
  font-size: 0.85rem;
  letter-spacing: 0.08em;
  text-transform: uppercase;
  color: var(--muted);
}

.help-toc {
  columns: 2;
  column-gap: 2rem;
  margin: 0;
  padding: 0;
  list-style: none;
}

/* A group stays whole rather than splitting across a column break. */
.help-toc > li {
  break-inside: avoid;
  margin-bottom: 0.4rem;
}

@media (max-width: 40rem) {
  .help-toc {
    columns: 1;
  }
}

.help-section {
  margin-top: 2.2rem;
}

.help-section h3 {
  margin: 1.6rem 0 0.4rem;
  font-size: 1.05rem;
}

/* The first question under a group heading needs no gap above it; the heading
   already carries its own. */
.help-section h3:first-of-type {
  margin-top: 0.8rem;
}

/* --- Not found (W4, F-W4-1) -------------------------------------------------
   The page a reader lands on when a URL answers nothing. The audience rules made
   this a common page rather than a rare one: a list whose audience excludes the
   reader is refused here on purpose.

   The numeral wears the header wordmark's neon-tube treatment (R60, relit R68)
   and for the same measured reason. Monoton draws every stroke as three or four
   parallel bars, so the h1 is a transparent ghost carrying only the bloom and a
   second copy rasterised at 3x and scaled back is the copy that is seen. The "0"
   is one whole curve, which is exactly where the concentric bars stair-step into
   dots without the supersample - the moire the wordmark rule documents.

   The bloom radii are in em, not px. The wordmark's are px because its size is
   fixed by the bar; this one steps down on a phone, and keeping the *ratio* of
   bloom to glyph is the part that keeps the 1px gaps dark. The ratio here is the
   wordmark's own measured one (26/52/96px against a 2.2rem mark), so the numeral
   lights the same way the header does instead of approximating it. */
.neon-404 {
  position: relative;
  font-family: "Monoton", sans-serif;
  font-weight: 400;
  font-size: 7rem;
  line-height: 1;
  letter-spacing: 0.04em;
  margin: 1rem 0 2.4rem;
  color: transparent;
  text-shadow:
    0 0 0.74em rgba(255, 65, 56, 0.75),
    0 0 1.49em rgba(212, 43, 38, 0.65),
    0 0 2.74em rgba(255, 40, 25, 0.38);
}

.neon-404-tube {
  position: absolute;
  left: 0;
  top: 0;
  font-size: 300%;
  transform: scale(0.333333);
  transform-origin: 0 0;
  color: #fff4ee;
  -webkit-text-stroke: 0.0058em var(--red);
}

@media (max-width: 40rem) {
  .neon-404 {
    font-size: 4.4rem;
  }
}

/* The page is two lines, and left alone they are glued under the header with the
   whole of a viewport's slack pooling empty underneath them. Centring the pair
   puts the numeral roughly where the eye already is, and makes the button read
   as the numeral's caption rather than a stray control to its left.

   Both halves need a hand, and each width needs a different one.

   Horizontal is the same everywhere: a column flexbox with the items centred.

   Vertical needs the box to *have* height to distribute, which it does not have
   on either width by default. On desktop, body's rows are `auto 1fr auto` with
   `align-items: start`, so main shrink-wraps; `align-self: stretch` hands it the
   1fr row, which is the leftover viewport height by design. Below the menu
   breakpoint body is plain block flow with nothing to stretch, so the box gets a
   floor instead. 45vh is measured, not guessed: it is the largest that still
   leaves the whole site footer above the fixed bottom bar at 390x844 (footer
   ending at 665 of 844), where 58vh pushed it flush against the bar and started
   a scroll. */
.notfound-page {
  display: flex;
  flex-direction: column;
  align-items: center;
  text-align: center;
}

@media (max-width: 1023px) {
  .notfound-page {
    min-height: 45vh;
    justify-content: center;
  }
}

@media (min-width: 1024px) {
  body:has(.site-nav) .notfound-page {
    align-self: stretch;
    justify-content: center;
  }
}

/* --- Texture pass (M6 artwork, R60; site-wide grunge 2026-09-16) -----------
   Owner-supplied worn paper now lives only at the desktop outer edges (see
   body pseudo-elements). Thin amber/brown trim and dark content surfaces
   keep body copy clean. */

/* Header band: none since the owner texture pass (2026-09-16) — the halftone
   + red-glow marquee treatment was removed so the header carries the same
   site-wide grunge as the rest of the page. */

/* Grungy chrome rails (owner request, 2026-09-18): the header/footer rules are
   a worn chrome bar rather than a flat line — bright bevelled metal eaten by
   corrosion pits, re-polished in short streaks, warm rust stains and grime
   bleeding past the edges. Painted from an original strip (generated for this
   project, so rule 4 of REWRITE.md is satisfied) because CSS blend modes could
   not do it: the grunge tile is a dark texture, so every blend that eats metal
   (hard-light / overlay / multiply) crushed the whole rail to black instead of
   pitting it, and soft-light against the page backdrop was far too faint. The
   3px borders under/over these strips are now near-black (--black-2) so the
   pits read as dark gaps; the light steel lives in the strip itself. */
.site-header::after,
.site-footer::before {
  content: "";
  position: absolute;
  left: 0;
  right: 0;
  height: 17px;
  background-image: url("../images/chrome-rail.e386a286d4c9.png");
  background-repeat: repeat-x;
  filter: drop-shadow(0 2px 3px rgba(0, 0, 0, 0.55));
  pointer-events: none;
}

.site-header::after {
  bottom: -10px;
}

.site-footer::before {
  top: -10px;
  /* Start mid-strip so the footer rail is not a copy of the header's pattern. */
  background-position: -1150px 0;
}

/* Content panels stay dark and nearly opaque over the grunge (owner texture
   pass): feed rows and review blocks keep text legible while the texture
   shows through the gaps between them. */
.feed-item,
.review {
  background: rgba(14, 12, 10, 0.88);
  border-radius: 4px;
}

.feed-item {
  padding: 0.5rem 0.6rem;
}

.review {
  padding-left: 0.6rem;
  padding-right: 0.6rem;
}

/* Buttons: lit red controls (owner pass, 2026-09-19; bloom tightened to the
   reference 2026-09-19). The reference button is not flat paint — sampling its
   interior gives luminance ~42 with dark and light blotching, wrapped in a ~2px
   rim that peaks at (245,120,118). Its glow is a *tight* halo, not a wide one:
   the mockup's luminance sits at flat backdrop until ~3px out and only lifts at
   the rim (2px above / 4px below at backdrop+4). So the fill is a mottled
   crimson tile over a dark-to-darker red gradient (the light lives in the edge,
   not the middle), and the rim carries hot glass plus three close bloom stops,
   same motif as the nav tube (R67) and the relit wordmark (R68). */
button,
.btn {
  background-color: #861713;
  background-image: var(--neon-mottle),
    linear-gradient(180deg, #9c1d17 0%, #861713 45%, #6b100e 100%);
  border: 2px solid var(--neon-rim);
  border-radius: 7px;
  box-shadow:
    inset 0 0 10px rgba(255, 74, 52, 0.5),
    inset 0 1px 0 rgba(255, 205, 195, 0.3),
    0 0 3px rgba(255, 96, 74, 0.8),
    0 0 7px rgba(255, 45, 32, 0.45),
    0 0 12px rgba(255, 30, 20, 0.18);
  text-shadow: 0 1px 2px rgba(46, 2, 2, 0.8);
}

button:hover,
.btn:hover {
  box-shadow:
    inset 0 0 12px rgba(255, 96, 70, 0.6),
    inset 0 1px 0 rgba(255, 205, 195, 0.35),
    0 0 4px rgba(255, 110, 86, 0.9),
    0 0 9px rgba(255, 55, 40, 0.52),
    0 0 15px rgba(255, 35, 24, 0.22);
}

/* A disabled control must not read as lit. */
button:disabled {
  border-color: #93504a;
  box-shadow: inset 0 0 8px rgba(120, 30, 22, 0.5);
  filter: saturate(0.55) brightness(0.8);
  cursor: default;
}

/* Poster / thumbnail placeholders: halftone dot fill (borders stay warm-brown). */
.poster-placeholder,
.thumb-placeholder,
.suggest-thumb-placeholder {
  background-image: radial-gradient(circle at center, rgba(233, 223, 203, 0.09) 1px, transparent 1.7px);
  background-size: 8px 8px;
}

/* --- Home 2-pane + rail (M6 artwork C, R64; measure set by N8) --------------
   The home page runs wider than the reading column so the feed's left edge
   sits under the wordmark and the rail's right edge under the profile corner;
   every other page keeps the 40rem reading column. Below the stack point the
   rail falls in from the right and its two panels sit side by side.

   N8 (owner pick, 2026-10-28): the band is 62rem, not 72rem. Measured on the
   deployed stack the old 72rem cap left 16px between the rail's right edge and
   the window at a 1440 viewport, so the page read as spread across the whole
   window instead of centred in it. 62rem keeps a visible gutter at that width
   (84px each side beside the menu) and gives the feed a 600px column, which is
   the measure the owner's Mastodon reference uses. The rail pays for it at
   20rem: the ticket art scales with the column, so the stubs step down ~9%. */
.container.wide-main {
  max-width: 62rem;
}

.home-grid {
  display: grid;
  grid-template-columns: minmax(0, 1fr) 20rem;
  gap: 2.5rem;
  align-items: start;
}

.rail {
  display: grid;
  gap: 1.5rem;
  /* The rail and feed share the document scroll. */
  position: static;
  max-height: none;
  overflow: visible;
}

/* The footer's second home (R131): the same partial the wide band uses,
   restacked for the 20rem column. One zone per row, each centred, instead of
   three zones spread across 72rem. The wrapper class is the only difference at
   the call site — which is the point: one body, two placements. Values are the
   ones the owner approved in the browser prototype, including the lighter top
   border: inside the rail the footer follows the genres panel, so a 3px seam
   reads as a second band boundary. */
.site-footer--rail {
  margin-top: 1.25rem;
  border-top-width: 2px;
}

.site-footer--rail .container {
  max-width: none;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 0.7rem;
  padding-top: 1.1rem;
  padding-bottom: 1.2rem;
}

.site-footer--rail .footer-signoff {
  justify-content: center;
}

/* Four links and three pipes need roughly 340px; the rail gives the row about
   290px, so the inline row broke each link's own text in half — "Getting" over
   "Started", "About This" over "Site" — with the pipes left floating at
   mid-height between the fragments. Two rows of two fixes it: the columns are
   auto-sized to the wider label in each, so the pairs align, and the
   separators go, because a pipe separates items on a line and says nothing
   once they are stacked. */
.site-footer--rail .footer-links {
  display: grid;
  grid-template-columns: auto auto;
  justify-content: center;
  gap: 0.35rem 1.25rem;
}

.site-footer--rail .footer-sep {
  display: none;
}

/* The brand block centres on the tagline, not on itself. The single auto column
   is sized by the tagline (the wider line) and centred; the wordmark is placed
   at that column's left edge, so REELTALK's left edge meets the beginning of
   the phrase instead of the pair floating as one shrink-wrapped box with dead
   space after the tagline. Live dependency, not a coincidence: it holds while
   the tagline is wider than the wordmark. Shorten the tagline below the
   wordmark's width and the column sizes to the wordmark instead, the tagline
   centres inside it, and the two left edges stop meeting. */
.rail .footer-brand {
  display: grid;
  justify-content: center;
}

.rail .footer-wordmark {
  grid-row: 1;
  grid-column: 1;
  justify-self: start;
}

.rail .footer-tagline {
  grid-row: 2;
  grid-column: 1;
  justify-self: center;
}

/* Pane heading with the red hairline running out toward the rail. */
.pane-title {
  display: flex;
  align-items: center;
  gap: 1rem;
  margin: 1.25rem 0 1rem;
  font-size: 2.5rem;
  line-height: 1;
  text-transform: uppercase;
  color: var(--cream);
}

.pane-title::after {
  content: "";
  flex: 1;
  height: 2px;
  background: linear-gradient(90deg, var(--red-bright), rgba(212, 43, 38, 0));
  box-shadow: 0 0 8px rgba(255, 65, 56, 0.4);
}

.pane-sub {
  margin: -0.6rem 0 1.25rem;
  font-size: 0.9rem;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  color: var(--muted);
}

/* The owner-supplied ticket graphics head each rail card and print its title
   themselves (R64), so the cards under them need no heading of their own. */
.rail-banner {
  width: 100%;
  height: auto;
  transform: rotate(-0.8deg);
  filter: drop-shadow(0 7px 14px rgba(0, 0, 0, 0.55));
}

/* The trending card is a plain list on the dark rail surface: rank chip, title,
   review count. */
.trending-list {
  list-style: none;
  margin: 0;
  padding: 0;
  display: grid;
  gap: 0.5rem;
}

.trending-list li {
  display: grid;
  grid-template-columns: 1.5rem minmax(0, 1fr);
  align-items: baseline;
  column-gap: 0.55rem;
  padding-bottom: 0.45rem;
  border-bottom: 1px solid rgba(233, 223, 203, 0.12);
}

.trending-list li:last-child {
  border-bottom: none;
  padding-bottom: 0;
}

.trending-rank {
  width: 1.4rem;
  height: 1.4rem;
  border: 1px solid var(--line);
  border-radius: 50%;
  font-size: 0.72rem;
  line-height: 1.35rem;
  text-align: center;
  color: var(--cream-muted);
}

.trending-film {
  font-weight: 600;
  text-decoration: none;
  color: var(--cream);
}

/* Scoped to the anchor: the anonymous rail renders the same text in a <span>,
   and :hover matches spans too — an unscoped rule would make the dead text
   light up as if it were clickable. */
a.trending-film:hover {
  color: var(--link);
  text-decoration: underline;
}

.trending-year {
  font-weight: 400;
  color: var(--muted);
}

.trending-count {
  grid-column: 2;
  font-size: 0.7rem;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  color: var(--muted);
}

/* The Top Reviews card (reviewer-discovery increment): the trending card's
   list feel with no rank chip - the order is the ranking. Each row is one
   link to the review, stacking the owner's three lines: reviewer and stars,
   film and year, the opening words. */
.top-reviews-list {
  list-style: none;
  margin: 0;
  padding: 0;
  display: grid;
  gap: 0.6rem;
}

.top-reviews-list li {
  padding-bottom: 0.55rem;
  border-bottom: 1px solid rgba(233, 223, 203, 0.12);
}

.top-reviews-list li:last-child {
  border-bottom: none;
  padding-bottom: 0;
}

.top-review {
  display: grid;
  gap: 0.12rem;
  text-decoration: none;
}

.top-review-who {
  /* The owner's sizing rule from the browser review: the name and stars read
     at the feed row's sizes - 0.95rem identity, stars at the shared 1.25rem
     the .stars class already carries. */
  font-weight: 700;
  font-size: 0.95rem;
  color: var(--cream);
}

a.top-review:hover .top-review-who {
  color: var(--link);
}

.top-review-stars {
  vertical-align: -1px;
}

.top-review-film {
  color: var(--muted);
  font-size: 0.95rem;
}

.top-review-film-name {
  font-weight: 700;
}

.top-review-excerpt {
  color: var(--cream-muted);
  font-size: 0.85rem;
  font-style: italic;
}

/* Heading a graphic already shows sighted readers (the ticket banner). */
.visually-hidden {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  overflow: hidden;
  clip: rect(0 0 0 0);
  white-space: nowrap;
  border: 0;
}

/* Popular Genres: dark panel matching the feed panels, amber-lit pills on hover. */
.rail-panel {
  padding: 0.9rem 1rem 1.1rem;
  border: 1px solid var(--border);
  border-radius: 4px;
  background: rgba(14, 12, 10, 0.88);
}

.rail-panel h2 {
  margin: 0 0 0.7rem;
  font-size: 1.5rem;
  text-transform: uppercase;
  color: var(--cream);
}

.genre-pills {
  list-style: none;
  margin: 0;
  padding: 0;
  display: flex;
  flex-wrap: wrap;
  gap: 0.45rem;
}

/* One class on both the member's <a> and the visitor's <span>, so the pill
   looks identical either way; only the anchor gets the hover treatment. */
.genre-pill {
  display: inline-block;
  padding: 0.2rem 0.65rem;
  border: 1px solid var(--line);
  border-radius: 999px;
  background: rgba(27, 23, 19, 0.85);
  font-size: 0.78rem;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  text-decoration: none;
  color: var(--cream-muted);
}

a.genre-pill:hover {
  border-color: var(--amber);
  background: var(--amber);
  color: #12100d;
}

@media (max-width: 64rem) {
  .home-grid {
    grid-template-columns: minmax(0, 1fr);
    gap: 2rem;
  }

  .rail {
    grid-template-columns: repeat(auto-fit, minmax(15rem, 1fr));
    /* Below the stack point the rail falls in under the feed and goes back to
       ordinary document flow — the narrow-layout mapping §2I records for
       Mastodon (`layout-single-column { height: auto }`). A viewport-capped
       sticky scroller under a long feed would hide the footer behind its own
       scrollbar and make the reader hunt for it. */
    position: static;
    max-height: none;
    overflow: visible;
    overscroll-behavior: auto;
  }
}

/* The left menu takes 280px out of the page, so the home 2-pane needs width
   the retired nav row never demanded: the feed pane would fall to ~350px at
   1024px. Below 1280px the feed is the only pane and the rail falls in under
   it. Placed after the block above and mirroring its declarations on purpose
   -- below either stack point the narrow layout is the same layout -- and not
   folded into it, because that block is the 64rem stack point the rail's own
   placement tests read as its single definition. */
@media (min-width: 1024px) and (max-width: 1279px) {
  .home-grid {
    grid-template-columns: minmax(0, 1fr);
    gap: 2rem;
  }

  .rail {
    grid-template-columns: repeat(auto-fit, minmax(15rem, 1fr));
  }
}

/* D8 (moderation/notifications arc M4): for a member the rail is a desktop
   surface. Below 1280px the member's home hides it -- the modules moved to
   the Search page and the rail footer's links moved to the More sheet, so
   nothing strands. The anonymous rail keeps every width: a stranger has no
   Search page (R80) and no More sheet (N1 decision 8), so the rail is their
   only wayfinding. One cap, 1279px, so the hide covers both the 64rem stack
   and the tablet band above it -- the same line the band block above ends at.
   The hide is CSS because the server does not know the viewport; the markup
   carries the class at every width and the browser decides. Proven in browser
   QA at 375/768/1100/1440, not pinned here (plan M4's test note). */
@media (max-width: 1279px) {
  .rail--member {
    display: none;
  }
}

/* The Search page's rail (D8): the same modules partial the home rail
   renders, in a grid of its own under the search box. It does not wear the
   .rail class on purpose -- .rail is the home rail's column, with a member
   hide and stack-point restacks that belong to that surface; this one wants
   the same look the restacked rail gets: modules side by side when the
   column has the width, one per row when it does not. align-items:start so a
   short panel does not stretch to its taller neighbour's row. */
.search-rail {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(15rem, 1fr));
  gap: 1rem;
  align-items: start;
  margin-top: 2rem;
}

/* --- Typography roles (M6 artwork, R60) ------------------------------------
   Placed last so these win over the `font: inherit` shorthands above. Bebas
   Neue for titles/section headings and the lit red controls; Oswald for
   metadata/small headings; Archivo (the body default) is used everywhere else,
   including the header's own text — see the rules below. */
h1,
h2 {
  font-family: var(--display);
  letter-spacing: 0.02em;
}

.meta-list,
table.results th,
.search-row .watchlist-btn,
.pane-sub,
.trending-rank,
.trending-count,
.genre-pill {
  font-family: var(--ui);
}

/* The profile head names a person, not a fact, so its handle and counts wear the
   body face at the nav-row weight instead of the metadata Oswald above. Owner
   pass, 2026-11-05: the handle sat directly over the tab strip and read as a
   different system from it. Face, weight and size move together for the same
   reason the feed scope tabs did on 2026-11-03 - at 400 weight the body face
   alone still read as a third voice. */
.handle,
.profile-counts {
  font-family: var(--body);
  font-weight: 600;
  font-size: 0.88rem;
}

/* The lit red controls take the marquee face (owner pass, 2026-09-19): Bebas
   Neue in caps, which is what the reference's button label reads as. Bebas
   ships a single weight, so 400 is explicit — leaving the inherited 600 would
   synthesise faux-bold — and it runs condensed, so the size and tracking step up
   to hold the control's presence; line-height holds the box at the height it had
   under Oswald. */
button,
.btn {
  font-family: var(--display);
  font-weight: 400;
  font-size: 1.1rem;
  line-height: 1.4;
  letter-spacing: 0.05em;
  text-transform: uppercase;
}

/* Ghost controls (Block / Follow / one-click Add to watchlist) share the
   `button` element but are not lit red, so they keep the metadata face and their
   own sentence case, weight, tracking and leading rather than inheriting the
   marquee label above. The reply composer's submit joins for the same reason: it
   is a bare `<button>` in a form that is not `form.inline`, and a caps marquee
   label on a reply box would read as a lit CTA rather than a small inline
   control. The applaud control left this list on the 2026-10-05 pass — it carries
   no text at all now, the word being baked into the artwork, so there is no
   label here for it to get wrong. */
form.inline button,
.search-row .watchlist-btn,
.reply-form button {
  font-family: var(--ui);
  font-weight: 600;
  line-height: 1.55;
  letter-spacing: normal;
  text-transform: none;
}

/* The header's text takes the film-title face (owner pass, R69): the nav row, its
   borderless Log out control and the profile link read in Archivo at the trending
   card's weight, so the marquee speaks the same voice as the rail it leads into.
   Log out is listed because the `button` role above claims it otherwise.
   The films-page tabs join here on the owner's pass of 2026-10-04 — "the same
   font as the nav bar type". They keep their own padding and active underline,
   which is what makes them tabs rather than nav links; only the voice changes. */
.site-nav a,
.site-nav form.inline button,
.header-user a,
.tabs a {
  font-family: var(--body);
  font-weight: 600;
}

/* House focus ring, site-wide (V4b/N7 filed note 1, owner-approved
   2026-11-03; widened to every link the same day when the owner found feed
   rows and list titles still wearing the browser's default). Before this,
   focus rings were the browser's decision surface by surface: measured fine
   on the build we swept, invisible-by-choice on another. One global rule is
   the deterministic answer - every link, button and disclosure summary on
   the site paints the same ring, and a new surface is covered the day it is
   written rather than waiting to be enumerated. The recipe is the lit
   controls' (2px, offset 3px) in the deeper cream - the owner found --cream
   too white against the dark; --cream-muted is the house's cream at 8.8:1
   on the page, well over the 3:1 bar for a focus indicator. :focus-visible
   only, so a mouse click paints nothing. Two surfaces keep their own extra
   treatment on top of the ring: the feed row's identity links also
   underline (the N7 pass), and form fields have their own border rule -
   inputs are deliberately not in this list. */
a:focus-visible,
button:focus-visible,
summary:focus-visible {
  outline: 2px solid var(--cream-muted);
  outline-offset: 3px;
}

/* --- Invite box (R82) -------------------------------------------------
   The pitch and the INVITE control on one's own profile, with the freshly
   minted single-use link under it once generated. Panel treatment matches
   the home rail's panels so it reads as an object the site already has.
   The Invite control deliberately sits in a plain <form>, NOT form.inline:
   form.inline strips the lit red fill and forces sentence case, and the
   label here is the caps control. */
.invite-box {
  margin: 1.5rem 0;
  padding: 0.9rem 1rem 1.1rem;
  border: 1px solid var(--border);
  border-radius: 4px;
  background: rgba(14, 12, 10, 0.88);
}

.invite-pitch {
  margin: 0;
  font-family: var(--ui);
  font-size: 1.05rem;
  font-weight: 600;
  color: var(--cream);
}

.invite-form {
  margin: 0;
}

.invite-result {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 0.5rem;
  margin-top: 0.9rem;
}

/* flex-basis instead of the base input's width:100%, so the copy button sits
   beside the link and the pair wraps rather than overflowing under 40rem.
   min-width:0 is what lets a long URL shrink instead of shoving the button
   out of the row. */
.invite-url {
  flex: 1 1 16rem;
  min-width: 0;
  font-family: var(--ui);
  font-size: 0.78rem;
}

.invite-result .btn {
  margin-top: 0;
  white-space: nowrap;
}

.invite-note {
  flex-basis: 100%;
  margin: 0.15rem 0 0;
  font-size: 0.75rem;
  color: var(--muted);
}

/* --- User lists (§2K increment 2) -----------------------------------------
   The list page and the lists page. Deliberately small: the control row, the
   thread and the composer are all borrowed from the post page, so only the
   two shapes nothing else on this site has — a ranked film row and a card
   of lists — needed new rules. The starting point from the 2026-10-06 mock,
   not a settled design. */

.list-page-head {
  margin-bottom: 0.25rem;
}

/* The title is the page's own voice, so it takes the display face the
   generic h1 rule already gives it. overflow-wrap rather than the default
   so a long unbroken title cannot push the page sideways. */
.list-name {
  margin: 1.25rem 0 0.3rem;
  line-height: 1.05;
  overflow-wrap: anywhere;
}

/* The head's control row is the post page's .review-head, reused rather
   than restyled — only its bottom margin changes, because the title sits
   directly above it here instead of the row opening the article. */
.list-page-head .review-head {
  margin-bottom: 0;
}

.list-length {
  font-family: var(--ui);
  font-size: 0.82rem;
  letter-spacing: 0.05em;
  text-transform: uppercase;
}

/* A ranked film row: poster + title + year and nothing more (L8). Same
   metrics as .film-row so a list reads as the same kind of object as a
   films list, with the rank column the only thing added in front. */
.rank-list {
  list-style: none;
  padding: 0;
  margin: 1rem 0;
}

.rank-row {
  display: flex;
  align-items: center;
  gap: 0.75rem;
  padding: 0.5rem 0;
  border-bottom: 1px solid var(--border);
}

/* The number comes from forloop.counter in the template, never from
   ListItem.rank — a removal leaves its gap behind, so rank is an ordering
   key and this is the ordinal the member reads. */
.rank-num {
  flex: 0 0 1.75rem;
  font-family: var(--ui);
  font-size: 0.95rem;
  font-weight: 600;
  color: var(--muted);
  text-align: right;
}

/* Repeated rather than added to the shared .film-row .thumb group so this
   section stays self-contained; the four values are that group's, so a
   poster in a list is the same size as one on the films page. */
.rank-row .thumb {
  width: 2.5rem;
  height: 3.75rem;
  object-fit: cover;
  border-radius: 3px;
  border: 1px solid var(--border);
  flex-shrink: 0;
}

.rank-film {
  text-decoration: none;
  overflow-wrap: anywhere;
}

.rank-film:hover {
  color: var(--link);
}

.rank-empty {
  padding: 0.5rem 0;
  font-size: 0.9rem;
}

/* The lists page's cards. auto-fill rather than a fixed column count so the
   row reflows on its own instead of needing a breakpoint per width. */
.list-mosaic {
  list-style: none;
  padding: 0;
  margin: 1rem 0;
  display: grid;
  grid-template-columns: repeat(auto-fill, minmax(14rem, 1fr));
  gap: 0.75rem;
}

.list-card {
  display: flex;
  flex-direction: column;
  gap: 0.3rem;
  padding: 0.85rem 1rem;
  background: var(--panel);
  border: 1px solid var(--border);
  border-radius: 4px;
}

.list-card:hover {
  background: var(--panel-2);
  border-color: var(--line);
}

.list-card-name {
  font-family: var(--display);
  font-size: 1.35rem;
  line-height: 1.1;
  color: var(--cream);
  text-decoration: none;
  overflow-wrap: anywhere;
}

.list-card-name:hover {
  color: var(--link);
}

.list-card-meta {
  font-family: var(--ui);
  font-size: 0.78rem;
  letter-spacing: 0.05em;
  text-transform: uppercase;
  color: var(--muted);
}

/* --- List authoring (§2K increment 3) -------------------------------------
   The create page, the editor, and the maker's link into it. Two traps here
   are the same class the reply composer's comment calls out: a bare
   <textarea> and a bare input[type=search] both render browser-default on
   this dark theme, and neither shows up in a diff — only a browser catches
   it. Both are given the field treatment explicitly below. */

.list-edit-section {
  margin: 1.75rem 0;
}

.list-edit-section h2 {
  margin: 0 0 0.5rem;
  font-size: 1.5rem;
}

/* The description field. Same values as .reply-form textarea, copied rather
   than shared so this section stays self-contained. */
.list-text-form textarea {
  width: 100%;
  max-width: 42rem;
  padding: 0.45rem 0.6rem;
  font: inherit;
  color: inherit;
  background: var(--field);
  border: 1px solid var(--brown);
  border-radius: 4px;
  margin-top: 0.25rem;
}

.list-text-form .btn {
  margin-top: 0.9rem;
}

.list-cancel {
  margin-left: 0.75rem;
  font-family: var(--ui);
  font-size: 0.9rem;
  color: var(--muted);
}

.list-cancel:hover {
  color: var(--accent);
}

/* The maker's "Edit list" on the list page. Pushed to the right edge of the
   borrowed .review-head so it cannot crowd the applause and reply counts it
   sits beside. */
.list-edit-link {
  margin-left: auto;
  font-family: var(--ui);
  font-size: 0.82rem;
  letter-spacing: 0.05em;
  text-transform: uppercase;
  color: var(--muted);
  text-decoration: none;
  white-space: nowrap;
}

.list-edit-link:hover {
  color: var(--accent);
}

/* The editor's ranked row: the read page's .rank-row plus a control
   cluster. flex-wrap on the editing row only — three controls beside a
   poster and a title do not fit a phone width, and letting them drop to
   their own line beats shrinking any of the four. */
.rank-edit {
  flex-wrap: wrap;
}

.rank-controls {
  margin-left: auto;
  display: flex;
  align-items: center;
  gap: 0.35rem;
  flex-shrink: 0;
}

/* The up/down/remove controls sit in form.inline, whose
   ``form.inline button`` rule (0,1,2) pins them to 0.9rem --muted, so a
   bare ``.rank-btn`` (0,1,0) loses and the arrows stay at the secondary-text
   colour. The owner's pass of 2026-10-07 took them off that: at
   --cream-muted they read as disabled rather than as available, which is
   the wrong signal for the main way you reorder a list. Scoping to
   ``.rank-controls`` outranks the form rule the same way
   ``.search-row .watchlist-btn`` does elsewhere in this file. */
.rank-controls .rank-btn {
  padding: 0.15rem 0.5rem;
  font-size: 1rem;
  font-weight: 700;
  line-height: 1.3;
  color: var(--cream);
}

.rank-controls .rank-btn:hover:not(:disabled) {
  color: var(--white);
  border-color: var(--accent);
  filter: none;
  box-shadow: none;
}

.rank-controls .rank-btn:disabled {
  color: var(--muted);
}

/* The add-film search box. */
.list-add-search {
  display: flex;
  align-items: center;
  gap: 0.5rem;
  margin: 0.5rem 0 1rem;
}

/* The typeahead wrapper. position:relative is what the shared .suggest-list
   anchors to, exactly as the header's .global-search does — the dropdown is
   the same component, not a copy of it. */
.list-add-picker {
  position: relative;
  flex: 1 1 auto;
  min-width: 0;
  max-width: 28rem;
}

.list-add-search input[type="search"] {
  width: 100%;
  padding: 0.45rem 0.6rem;
  font: inherit;
  color: inherit;
  background: var(--field);
  border: 1px solid var(--brown);
  border-radius: 4px;
}

.list-add-search button {
  margin-top: 0;
  flex-shrink: 0;
}

/* The dropdown's rows are <button>s, not <a>s, because picking one is an
   action rather than a navigation. That means they arrive wearing the lit
   crimson control chrome and the marquee face, and both have to come off —
   otherwise every suggestion row is a big glowing red slab. The hover rule
   repeats the filter/shadow resets for the same reason the base ones do
   (R135). */
.list-add-picker .suggest-row {
  display: flex;
  width: 100%;
  align-items: center;
  gap: 0.5rem;
  padding: 0.35rem 0.75rem;
  margin: 0;
  font: inherit;
  text-align: left;
  text-decoration: none;
  text-transform: none;
  letter-spacing: normal;
  color: var(--fg);
  background: none;
  border: none;
  border-radius: 0;
  box-shadow: none;
  text-shadow: none;
}

.list-add-picker .suggest-row:hover:not(:disabled),
.list-add-picker .suggest-row.active:not(:disabled) {
  /* Matches the header dropdown's own hover, so the two boxes highlight alike. */
  background: var(--surface-2);
  filter: none;
  box-shadow: none;
}

.list-add-picker .suggest-row:disabled {
  color: var(--muted);
  cursor: default;
  filter: none;
  box-shadow: none;
}

.suggest-row-title {
  flex: 1 1 auto;
  min-width: 0;
  overflow-wrap: anywhere;
}

.suggest-row-state {
  flex-shrink: 0;
  font-family: var(--ui);
  font-size: 0.75rem;
  letter-spacing: 0.05em;
  text-transform: uppercase;
  color: var(--muted);
  white-space: nowrap;
}

/* The per-row Add control: the same ghost the search page's one-click
   watchlist button is, so adding to a list and adding to a watchlist look
   like the same kind of action in the same kind of row. */
.add-row .add-btn {
  margin-top: 0;
  padding: 0.25rem 0.7rem;
  font-family: var(--ui);
  font-size: 0.9rem;
  font-weight: 600;
  line-height: 1.55;
  letter-spacing: normal;
  text-transform: none;
  background: none;
  color: var(--accent);
  border: 1px solid var(--border);
  box-shadow: none;
}

.add-row .add-btn:hover {
  border-color: var(--accent);
  filter: none;
  box-shadow: none;
}

.add-state {
  font-family: var(--ui);
  font-size: 0.78rem;
  letter-spacing: 0.05em;
  text-transform: uppercase;
  white-space: nowrap;
}

/* The delete sits last and quietest. Every primary control on this site is
   lit crimson, so a destructive one styled as a primary would be the
   loudest thing on the page and the easiest to hit by accident; it takes
   the ghost look and only picks up the accent on hover. The hover rule
   repeats the filter/shadow resets because button:hover outspecs a bare
   class-level reset the moment the cursor arrives (R135). */
.list-delete-section {
  margin-top: 2.5rem;
  padding-top: 1.25rem;
  border-top: 1px solid var(--border);
}

.btn-danger {
  font-family: var(--ui);
  font-weight: 600;
  font-size: 0.9rem;
  line-height: 1.55;
  letter-spacing: normal;
  text-transform: none;
  padding: 0.3rem 0.85rem;
  background: none;
  color: var(--muted);
  border: 1px solid var(--border);
  box-shadow: none;
  text-shadow: none;
}

.btn-danger:hover {
  color: var(--accent);
  border-color: var(--accent);
  filter: none;
  box-shadow: none;
}

/* The "New list" entry on one's own lists page. */
.list-toolbar {
  margin: 1.25rem 0 0.5rem;
}

.list-toolbar .btn {
  margin-top: 0;
}

/* --- Saving a list (§2K increment 5, L2 / R140) -------------------------
   The Save control and the notice a deleted list wears on the Saved tab. */

/* The Save control is `.btn` and nothing more — R140 2 ruled that lit
   crimson weight and explicitly parked any further design work on it for a
   future whole-UI pass, so the only line here is the reset R134 #6 demands
   of anything dropped into `.review-head`: `button, .btn` carries
   `margin-top: 1rem` and that rule is not opt-in. */
.list-save-btn {
  margin-top: 0;
}

/* A saved list whose maker deleted it stays on the Saved tab until its saver
   dismisses the notice (R140 1). What it must NOT do is read as navigable:
   the title is a plain span because `/list/<id>/` 404s, and the hover
   background is exactly what sells a card as a link. So the hover is pinned
   back to the resting paint — same specificity as `.list-card:hover`, later
   in the file, which is what makes it win — and the whole card sits at
   reduced emphasis to match being a record rather than a destination. */
.list-card-deleted {
  opacity: 0.62;
}

.list-card-deleted:hover {
  background: var(--panel);
  border-color: var(--border);
}

.list-card-deleted .list-card-name {
  color: var(--muted);
}

/* The notice line: the sentence and its Dismiss control together, wrapping
   onto a second line at narrow widths rather than overflowing the card. The
   Dismiss button rides in `form.inline`, which already gives it the small
   muted ghost look — deliberately NOT `.btn`, whose lit fill would make
   dismissing louder than the fact being dismissed. */
.list-deleted-notice {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 0.3rem 0.6rem;
  margin: 0.3rem 0 0;
  font-family: var(--ui);
  font-size: 0.8rem;
  line-height: 1.4;
  color: var(--cream);
}

/* Home feed polish (owner approved): larger avatars, clean continuous rows,
   and film posters aligned beneath the author with prose alongside. */
.feed .review-list {
  background: #0e0c0a;
  border-top: 1px solid var(--line);
}

.feed .review {
  padding: 18px 18px 18px 76px;
  border-radius: 0;
  background: transparent;
  min-height: 88px;
}

.feed .review-head {
  gap: 10px;
  margin-bottom: 8px;
  min-height: 28px;
}

.feed .avatar-row {
  position: absolute;
  left: 16px;
  top: 18px;
  width: 44px;
  height: 44px;
}

.feed .review-head .applaud {
  margin-left: auto;
}

.feed .feed-item {
  background: transparent;
  border-radius: 0;
  padding: 0;
  margin: 4px 0 8px;
}

.feed .review:has(> .feed-item) {
  display: grid;
  grid-template-columns: 64px minmax(0, 1fr);
  column-gap: 16px;
  min-height: 164px;
  align-content: start;
  grid-template-rows: auto auto 1fr;
}

.feed .review:has(> .feed-item) > .review-head {
  grid-column: 1 / -1;
}

.feed .review > .feed-item {
  display: contents;
}

.feed .feed-item .thumb {
  position: static;
  grid-column: 1;
  grid-row: 2 / 4;
  width: 64px;
  height: 96px;
  border-radius: 2px;
}

.feed .feed-item .feed-film {
  grid-column: 2;
  grid-row: 2;
  align-self: start;
}

.feed .review:has(> .feed-item) > .review-body {
  grid-column: 2;
  grid-row: 3;
  min-width: 0;
}

.feed .review-body p {
  margin: 8px 0;
}

.feed .list-strip {
  margin: 4px 0 0;
}

.feed .list-strip-title {
  margin: 4px 0 10px;
}

@media (max-width: 600px) {
  .feed .review {
    padding: 16px 12px 16px 62px;
  }

  .feed .avatar-row {
    left: 12px;
    top: 16px;
    width: 36px;
    height: 36px;
  }

  .feed .review:has(> .feed-item) {
    grid-template-columns: 48px minmax(0, 1fr);
    column-gap: 12px;
    min-height: 132px;
  }

  .feed .feed-item .thumb {
    width: 48px;
    height: 72px;
  }

  .feed .review-head {
    gap: 6px 10px;
  }

  .feed .review-head .applaud {
    margin-left: 0;
  }

}
/* Home-feed identity and metadata hierarchy. */
.feed .review-author {
  color: var(--cream);
  font-weight: 700;
  text-decoration: none;
}

.feed .feed-film a {
  text-decoration: none;
  text-underline-offset: 3px;
}

.feed .review-author:hover,
.feed .review-author:focus-visible,
.feed .feed-film a:hover,
.feed .feed-film a:focus-visible {
  text-decoration: underline;
  text-underline-offset: 3px;
}

.feed .review-head {
  column-gap: 14px;
  row-gap: 8px;
  font-family: var(--body);
  font-size: 0.95rem;
}

.feed .review-head .feed-verb {
  font-family: inherit;
  font-size: inherit;
  font-weight: 400;
}

.feed .post-date {
  font-family: inherit;
  font-size: inherit;
  font-weight: 400;
  letter-spacing: normal;
  color: var(--white);
}

.feed .feed-film {
  font-weight: 400;
  line-height: 1.45;
}

.feed .feed-film a {
  font-weight: 650;
}

@media (max-width: 600px) {
  .feed .review-head {
    column-gap: 10px;
    row-gap: 8px;
  }
}
/* Home feed section heading: compact display type and a restrained red rule. */
.feed .pane-title {
  font-size: 2rem;
  gap: 18px;
}

.feed .pane-title::after {
  max-width: 350px;
  background: linear-gradient(90deg, var(--red-bright), rgba(255, 65, 56, 0));
  box-shadow: none;
}
/* Feed prose links, including mentions: consistent with author/film links. */
.feed .review-body a {
  text-decoration: none;
  text-underline-offset: 3px;
}

.feed .review-body a:hover,
.feed .review-body a:focus-visible {
  text-decoration: underline;
}
/* Home rail: closer grouping and a restrained shadow beneath ticket artwork. */
.rail {
  gap: 1rem;
}

.rail-banner {
  filter: drop-shadow(0 3px 6px rgba(0, 0, 0, 0.4));
}
/* Genre tags: compact rectangular labels beside the ticket artwork. */
.genre-pill {
  border-radius: 4px;
  background: #100e0c;
}
/* Trending rank markers: filled discs with clearly weighted numerals. */
.trending-list li {
  grid-template-columns: 32px minmax(0, 1fr);
  column-gap: 9px;
}

.trending-rank {
  width: 27px;
  height: 27px;
  display: grid;
  place-items: center;
  background: #4b3b2c;
  border: 1px solid var(--cream);
  color: #f3e3c7;
  font-family: var(--ui);
  font-weight: 700;
  font-size: 0.85rem;
  line-height: 1;
}
/* Header search: decorative cream magnifier with a clear text gutter. */
.global-search input[type="search"] {
  padding-left: 2.6rem;
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='20' height='20' viewBox='0 0 24 24' fill='none' stroke='%23e9dfcb' stroke-width='1.8' stroke-linecap='round'%3E%3Ccircle cx='10.5' cy='10.5' r='6.5'/%3E%3Cpath d='m15.5 15.5 5 5'/%3E%3C/svg%3E");
  background-repeat: no-repeat;
  background-position: 0.9rem center;
  background-size: 18px 18px;
}

/* Shared cinema controls: keep after legacy component rules so all opt-in
   controls use the same typography, rim, hover and touch dimensions. */
.film-actions button,
.film-actions .btn,
.btn.cinema-button {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 0.4rem;
  min-height: 38px;
  margin-top: 0;
  padding: 0.45rem 0.9rem;
  border: 1px solid var(--cream-muted);
  border-radius: 4px;
  background: linear-gradient(180deg, #171410, #090807);
  color: var(--cream);
  box-shadow: inset 0 0 0 1px rgba(233, 223, 203, 0.08);
  font-family: var(--body);
  font-size: 0.875rem;
  font-weight: 600;
  line-height: 1.4;
  letter-spacing: normal;
  text-transform: none;
  transition: background-color 150ms ease, border-color 150ms ease;
  text-shadow: none;
}

.film-actions button:hover,
.film-actions .btn:hover,
.btn.cinema-button:hover {
  background: linear-gradient(180deg, #282118, #15110d);
  border-color: var(--cream);
  color: var(--cream);
  box-shadow: inset 0 0 0 1px rgba(233, 223, 203, 0.12);
  filter: none;
}

.film-actions .film-watched,
.btn.cinema-button--primary {
  background: linear-gradient(180deg, #891c18, #60100e);
  border: 1px solid #df5a50;
  color: #fff2e4;
  box-shadow:
    inset 0 0 6px rgba(255, 74, 52, 0.14),
    0 0 3px rgba(255, 45, 32, 0.22);
}

.film-actions .film-watched:hover,
.btn.cinema-button--primary:hover {
  background: linear-gradient(180deg, #a42620, #761411);
  border-color: #ef7368;
  color: #fff2e4;
  box-shadow:
    inset 0 0 6px rgba(255, 74, 52, 0.2),
    0 0 5px rgba(255, 45, 32, 0.3);
}

/* The lit controls' focus ring is the site-wide `button:focus-visible` rule
   above - it was listed here first, but the global rule made this redundant. */

.film-actions svg,
.cinema-button svg {
  width: 16px;
  height: 16px;
  flex: none;
  fill: none;
  stroke: currentColor;
  stroke-width: 1.7;
  stroke-linecap: round;
  stroke-linejoin: round;
}

@media (max-width: 600px), (pointer: coarse) {
  .film-actions button,
  .film-actions .btn,
  .btn.cinema-button {
    min-height: 44px;
  }
}


.btn.cinema-button:disabled {
  opacity: 0.55;
  filter: none;
  box-shadow: none;
  cursor: default;
}

/* --- Feed scope tabs (N5) --------------------------------------------------
   The strip under "Now Playing" naming which feed is on screen. Links with
   aria-current, not role=tab: the scope is a URL that survives reload, Back
   and sharing (N1 Q6), not a JS panel switch. Only live scopes render, so
   every tab shown goes somewhere. The active marker is the bottom bar's red
   rule turned horizontal, so the two markers read as one system; 44px
   targets per the N1 package. The voice - face, weight, size - is the
   profile tab strip's (owner pass, 2026-11-03), so the two tab strips on
   the site read as one type; padding and the 44px target stay their own. */
.feed-scopes {
  display: flex;
  gap: 24px;
  margin: 0 0 1.25rem;
  border-bottom: 1px solid var(--border);
}

.feed-scope {
  display: inline-flex;
  align-items: center;
  min-height: 44px;
  padding: 0 4px;
  border-bottom: 2px solid transparent;
  color: var(--muted);
  font-family: var(--body);
  font-weight: 600;
  font-size: 0.88rem;
  text-decoration: none;
}

.feed-scope:hover {
  color: var(--cream);
}

.feed-scope[aria-current="page"] {
  color: var(--cream);
  border-bottom-color: #c14b37;
}
