/* STYLES — TA-533 fourth extraction pilot. Every rule dashboard/index.html previously carried in its
   own inline <style> block, moved verbatim (byte-for-byte apart from the extraction itself — no rule
   reordered, renamed, or rewritten). Pre-extraction audit (2026-09-27) confirmed this is safe to move:
   zero url(), @import, or @font-face in the block; the only external font reference is var(--font-num)
   pointing at "Oswald", loaded via separate <link rel="stylesheet" href="https://fonts.googleapis.com/...">
   tags in <head> that are untouched by this move (a Google Fonts URL, not a relative one — nothing here
   depends on this file's own location); no data: URIs; and no test parses this CSS directly out of
   dashboard/index.html (checked test/ for style/.css references before extracting).

   Loaded via <link rel="stylesheet" href="/styles.<hash>.css"> in <head>, BEFORE #app and any rendered
   content — same position the inline block held, so first-paint styling is unchanged.

   ⚠ ROOT-RELATIVE HREF IS REQUIRED, NOT COSMETIC — same reasoning as every extracted JS asset.
   dashboard/index.html is also served at rewritten URLs like /i/<token> (netlify.toml's "/i/*" ->
   /index.html rewrite). A bare "styles.HASH.css" reference resolves against THAT path to
   /i/styles.HASH.css, which the same wildcard rewrite would also match, serving index.html's HTML back
   as the "stylesheet" and breaking every invite link before the app even paints. Always reference this
   file as "/styles.<hash>.css" — test/dashboard-script-url-resolution.test.mjs enforces this generically
   for every local asset (script src AND link href), and test/dashboard-asset-versioning.test.mjs enforces
   it specifically for this file's own <link> tag.

   VERSIONED FILENAME, ON PURPOSE (see scripts/hash-dashboard-asset.mjs's own header for the full
   reasoning). This file's name embeds a short hash of its own content. After editing the CONTENT below,
   run:
     node scripts/hash-dashboard-asset.mjs dashboard/styles.<current-hash>.css
   then `git mv` to the filename it prints and update the matching <link href="..."> in
   dashboard/index.html, in the same commit. test/dashboard-asset-versioning.test.mjs enforces that the
   filename, the file's own content hash, and index.html's reference never drift apart. */
  :root {
    /* ⚠ DECLARED, BECAUSE THE BROWSER PAINTS CONTROLS WE DO NOT. This app is deliberately dark-only —
       every token below is a dark value and there is no light palette. Without this line the UA still
       believes it is in light mode, so anything IT paints comes out light: the timeframe <select>'s
       OPEN dropdown list (the closed control is ours and looks right, the popup is not), scrollbars,
       focus rings, form controls. On the Results page that is the one control the page has. */
    color-scheme: dark;
    --bg:#0B1220; --panel:#141b24; --panel2:#1c2632; --line:#26323f; --txt:#e6edf3; --mut:#8b98a5;
    --accent:#10B981;                                                 /* canonical brand green */
    --accent-bright:#34D399;                                          /* beacon tint (replaces #00d166); live/alive moments ONLY */
    --accent-ink:#06210f;                                             /* text/icon ON an accent fill */
    --accent-glow:color-mix(in srgb, var(--accent) 50%, transparent);
    --accent-dim:color-mix(in srgb, var(--accent) 14%, transparent);
    --accent-faint:color-mix(in srgb, var(--accent) 6%, transparent);
    --warn:#d29922; --bad:#f85149; --blue:#58a6ff;
    --prime:#e8b53d; --prime-ink:#241a02; --prime-glow:color-mix(in srgb, var(--prime) 50%, transparent);  /* gold PRIME — top conviction tier (D2); NOT --warn */
    --font-num:"Oswald", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;  /* SP-6 · big-number display face (Oswald max weight is 700) */
    --tier-strong:#3FA491; --tier-strong-dim:color-mix(in srgb, #3FA491 14%, transparent);  /* SP-314 · Strong-tier signal, deliberately NOT the brand accent */
    /* TA-785/TA-778 — Handicapper's independent lean, new token approved by Design Lead (TA-778 comment
       thread). Violet/indigo is the one hue family nothing else on this card speaks for — never reuse
       --prime/--tier-strong/--accent/--blue/--warn/--bad, each of those already carries a different real
       meaning elsewhere on the same card (see that comment's full audit). Built the exact same way
       --tier-strong/--tier-strong-dim already are. */
    --handicap:#A78BFA; --handicap-dim:color-mix(in srgb, #A78BFA 14%, transparent);
    /* TA-1213 revision — "Opinion changed" note needed more visual presence than plain .muted grey
       footnote text, without becoming an alert or a new recommendation. Design Lead spec: its own
       hue (blue-grey, reads as "record/history", not warn/bad/accent/handicap). */
    --history:#6E8CAD;
    --history-dim:color-mix(in srgb, var(--history) 8%, transparent);

    /* TA-1344 — Game-card feed creative-treatment pass, scoped NEW tokens for the redesigned primary
       Games-tab card (.game-card .gc2-row / .gc2-mobile) ONLY. The legacy Line Shop/My Research/Best
       Angles surfaces keep --prime/--tier-strong/--accent/.conf-chip untouched — these are deliberately
       NEW names, never a redefinition of an existing token, so nothing outside this one card's scope can
       drift. Prime reuses --prime/--prime-ink verbatim (same gold, confirmed identical value) since the
       approved prototype's Prime color IS this app's existing Prime gold — no new token needed there.
       Strong is a NEW green (not --tier-strong's teal) — round-2 prototype's own color audit found
       --tier-strong-bg's originally-proposed emerald sat only ~9° from this card's new --action-teal,
       too close for two large filled surfaces on one card; #22C55E (round-3 resolved value) keeps ~27°
       separation from teal while staying clearly "green," confirmed in 3 rounds of Manager + independent
       GPT-5.1/Grok visual review before this landed in dashboard/index.html. */
    --gc2-strong-bg:#22C55E; --gc2-strong-ink:#052e16;
    --gc2-pass-bg:#2c1a1a; --gc2-pass-fg:#d98a8a; --gc2-pass-line:#6b3636;
    /* TA-1375 round-6 fix #6 (David, live review against the reference image) — round-5's EDGE fix
       (`.stat-cell.edge .stat-value{color:var(--txt)}`, below) was a reasonable interim step but
       departs from the reference, which shows EDGE consistently GREEN regardless of the card's own
       tier (confirmed directly against the reference image — a PRIME card, gold pill, still shows
       green "+2.5 pts edge" text). A plain alias to `--gc2-strong-bg` was already tried and reverted
       in round 5 for being architecturally tied to the Strong tier's own meaning (a Prime card's EDGE
       would silently change if Strong's own green ever did). This is a genuinely INDEPENDENT token —
       same literal hue as `--gc2-strong-bg` today (so it matches the reference exactly), but never
       aliased to it, so EDGE's color and Strong's tier color can diverge later without either one
       accidentally dragging the other along. */
    --edge-value:#22C55E;
    /* TA-1372 Design Lead round 2 (2026-11-14, gap #1) — the Manager's own re-review (plus independent
       GPT-5.1 pass) confirmed --panel (#141b24) vs --bg (#0B1220) is only a ~9-unit-per-channel step,
       invisible at a glance once the old "Our Analytics" bordered tiles (which gave the page a visible
       card anchor nearby) were removed in Task 1. This is a DEDICATED, real step up — not a 1-2% nudge —
       used ONLY for this card's own per-row boundary (never redefines --panel/--panel2, so nothing else
       on the page shifts). Border gets its own lighter token too, since --line read nearly invisible at
       this card's new radius/spacing. Zero box-shadow anywhere in this pair — contrast/border/radius/
       spacing only, per the explicit no-glow instruction. */
    --gc2-card-bg:#1E2B3A; --gc2-card-border:#34485f;
    --action-teal:#3FD9C7; --action-teal-dim:color-mix(in srgb, #3FD9C7 14%, transparent);
    /* TA-1375 round-3 design-polish fix (Grok/GPT-5.1 independent review, 2026-11-15, finding #2 on this
       round) — the round-2 fix above ("Edge gets its own fixed, exclusive accent... pale ice-blue") never
       actually eliminated the stray cyan hue outside this card's gold/green/purple/teal palette; it just
       relocated it from the date pill onto EDGE itself, the card's single most important stat. --edge-accent
       is removed outright (confirmed by grep: nothing else in the live render path references it).
       Round-3 then had EDGE reuse `--gc2-strong-bg` instead — ALSO wrong, corrected in round 5 below:
       `--gc2-strong-bg` is the Strong tier's own color (pill/left-edge bar), so a Prime-tier card (gold)
       still showed green EDGE underneath its gold pill/bar, two tier colors fighting on one card. EDGE's
       `.stat-cell.edge` rule (below) now uses `var(--txt)`, the same neutral token the recommendation
       headline itself uses — tier-independent, no hue at all. */
    /* TA-1375 round-2 design-polish fix (2026-11-15, finding #3) — the per-book brand-accent tokens
       that used to live here (--book-fanduel/--book-draftkings/--book-betmgm/--book-caesars/
       --book-betrivers/--book-fanatics) are removed: `_gc2BookAccent()` (dashboard/index.html) now maps
       the book-row swatch to the real value-tier color (gold/green/neutral/red) instead of book brand
       identity, and nothing else in the live app ever referenced these tokens (confirmed by repo-wide
       grep before deleting) — only the two now-superseded `prototype-cardfeed-v2*.html` files did,
       which are not part of the live render path. */
  }
  * { box-sizing:border-box; }
  /* Backstop, not the fix: every genuinely wide element in this app already scrolls INSIDE itself
     (.tabs, .subtabs, .tscroll, .sv-scroll all use their own overflow-x:auto) — nothing here is meant
     to widen the page. This just makes a future regression like TA's mobile-header overflow fix
     (2026-09-22, see .fresh) fail visibly-contained instead of pushing the whole document sideways. */
  /* ⚠ min-height:100vh IS LOAD-BEARING, NOT COSMETIC (found 2026-10-06, the Scoreboard-tab bell-cutoff
     bug). overflow-x:hidden alone on html/body forces the UA to resolve overflow-y as `auto` too (CSS2.1
     overflow spec: one axis non-visible forces the other off `visible`) — and with neither axis given an
     explicit height, html/body then size to their own CONTENT, not the viewport. Every other tab always
     happened to have enough content to exceed one viewport, so this never surfaced. The Scoreboard tab
     (e.g. a light slate — one CFB game, no NFL) can render shorter than the viewport, and body/html then
     become a short `overflow:auto` box that CLIPS any taller position:absolute descendant painted inside
     it — including #bellMenu (a child of the always-tall-enough header), which measured a correct
     753px-tall box via getBoundingClientRect() while visually cutting off around body's own ~400px
     content height. min-height:100vh keeps body/html at least viewport-tall regardless of how short the
     active tab's content is, so that clip boundary can never sit above the viewport's own bottom edge. */
  html { overflow-x:hidden; min-height:100vh; }
  body { margin:0; background:var(--bg); color:var(--txt); font:15px/1.5 -apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,sans-serif; overflow-x:hidden; min-height:100vh; }
  a { color:var(--blue); }
  /* The invite card is a brand-new player's entire first impression, and the global blue anchor
     was the only blue thing on an otherwise green-and-dark screen. --blue is a real system token,
     so this was not an invented colour, but the app's own in-content action link (see "Ask the
     Sharp") is accent green at 700 — that is the treatment for "here is the other thing you can
     do on this screen", which is exactly what these are. Scoped to the card so the global default
     is untouched everywhere else, and written once rather than inline on each anchor. */
  .invite-card a { color:var(--accent); font-weight:700; }
  /* THE canonical small uppercase label (SP-225). New surfaces use this; the dozen older
     component-scoped variants get retired by attrition when their components are next touched,
     rather than in one sweep that would shift type across the whole product at once. */
  .eyebrow { font-size:12px; letter-spacing:.06em; text-transform:uppercase; color:var(--mut); }
  /* Same label, promoted. Used where the card itself is accent-bordered and the heading leads it. */
  .eyebrow.on { color:var(--accent); }
  /* min-width:0 on both flex children: without it, a flex item's default min-width:auto lets its own
     unbreakable content (e.g. the freshness label) force ITSELF wider than the space header actually has,
     which pushes the whole row — and therefore the document — past the viewport. See TA mobile-header
     overflow fix (2026-09-22): a longer freshness string exposed this same-day the .fresh media query below
     was added. Keep both guards; either alone still lets the other child blow out the row. */
  header { display:flex; align-items:center; justify-content:space-between; gap:10px; padding:11px 14px; border-bottom:1px solid var(--line); background:var(--panel); position:sticky; top:0; z-index:5; min-width:0; }
  @media (min-width:600px){ header { padding:14px 18px; } }
  .brand { font-weight:800; letter-spacing:.3px; font-size:18px; min-width:0; flex:0 1 auto; overflow:hidden; text-overflow:ellipsis; white-space:nowrap; }
  .brand span { color:var(--accent); }
  /* Requirement: logo may scale down on mobile so it never competes with the top-right controls for space.
     ⚠ The wordmark is an <img style="height:51px;width:auto"> INLINE style, swapped in at the edge for the
     new-brand host (netlify/edge-functions/lib/rebrand-html.mjs) — a class-level rule cannot beat an inline
     one without !important, which is the one legitimate use of it here (there is no other way to override
     an inline style).
     ⚠ max-height (an absolute px value), not height:auto alone, is what keeps this SAFE at normal widths.
     First attempt used `height:auto !important` with only `max-width:100%` — at any width with no shrink
     pressure (including ordinary desktop), that resolves the image's flex-basis contribution from its raw
     SOURCE FILE size (700x203 here), not the intended 51px-tall rendering, because max-width is a
     percentage and percentages don't count during max-content sizing — measured live, it rendered the
     wordmark at up to 184x53 in cases that should have stayed 51px tall, and would have rendered it at its
     full ~700px source width on desktop, wide enough to overlap the nav. max-height:51px is an ABSOLUTE
     constraint, so it DOES count during max-content sizing: .brand's natural contribution becomes the
     51px-tall rendering (~176px wide) everywhere there's room for it — i.e. everywhere the header already
     looked exactly as it does today — and only actually shrinks below that once .brand (the sole
     flex-shrink:1, min-width:0 child of header — .topbar's controls are pinned to flex-shrink:0 above) is
     squeezed by real space pressure, with max-width:100% taking over as the binding constraint at that
     point and height following it down (both auto, aspect ratio preserved throughout).
     This can only ever make the header SHORTER than its already-sticky-positioned .tabs-wrap top:74px/80px
     expects (last computed for the full 51px logo, see that comment) — a short header only opens a small
     gap above the tab strip on the very narrowest phones, never an overlap, so those two numbers do not
     need to change. (Recomputing them for real would mean also touching the JS TABS_WRAP_TOP constant,
     which a prior PR deliberately deferred to TA-259 rather than do inside an unrelated change — same
     boundary applies here.) */
  .brand img { max-height:51px; max-width:100%; width:auto !important; height:auto !important; }
  .muted { color:var(--mut); }
  button { cursor:pointer; border:1px solid var(--line); background:var(--panel2); color:var(--txt); padding:8px 14px; border-radius:8px; font-size:14px; }
  button.primary { background:var(--accent); color:var(--accent-ink); border-color:var(--accent); font-weight:700; }
  button:disabled { opacity:.5; cursor:default; }
  input, select { background:var(--panel2); border:1px solid var(--line); color:var(--txt); padding:9px 11px; border-radius:8px; font-size:14px; width:100%; }
  .wrap { max-width:1000px; margin:0 auto; padding:18px 18px 104px; } /* extra bottom cushion so footnotes scroll clear of the fixed "Ask the Sharp" button */
  .center { min-height:70vh; display:flex; align-items:center; justify-content:center; }
  .card { background:var(--panel); border:1px solid var(--line); border-radius:12px; padding:22px; }
  /* TA-ALLPLAYS fix (2026-10-30) — the deep-link flash All Plays' "View" button uses to mark the exact
     NBA Insights card a member just tapped, so a 2-second transition (not a @keyframes pulse — a plain
     box-shadow/border swap that then transitions back off) is enough; .ap-focus is added then removed by
     JS (renderNbaInsightsTab), never left on permanently. Border swaps to --accent, same brand green the
     rest of the page already uses for an "I bet this"/primary-action affordance, never a new color. */
  .ap-focus { border-color:var(--accent); box-shadow:0 0 0 2px var(--accent); transition:box-shadow .6s ease, border-color .6s ease; }
  /* Sticky wrapper holds the scroll-affordance fades (SP-3). The inner .tabs is the horizontal scroller.
     top must track the header's real rendered height (image height + its own vertical padding + its
     1px border), which now moves with the brand logo's size — 74px/80px below reflect the 51px logo
     (11px/14px header padding at the same 600px breakpoint the header itself uses). Recompute both
     numbers (here AND the JS TABS_WRAP_TOP below) any time the header logo's height changes again. */
  .tabs-wrap { position:sticky; top:74px; z-index:4; background:var(--panel); }
  @media (min-width:600px){ .tabs-wrap { top:80px; } }
  /* edge chevrons cue that more tabs are off-screen (a same-color fade is invisible on the dark panel).
     ⚠ SP-4 moved these from .tabs-wrap onto an inner .tabs-fade. They are absolutely positioned
     top:0/bottom:1px, so while they were anchored to .tabs-wrap, adding the contextual .subtabs row
     inside that wrapper stretched both gradients down over BOTH rows — describing a scroll that only
     the top row does. .tabs-fade hugs the scrolling strip alone; .tabs-wrap stays the sticky box. */
  .tabs-fade { position:relative; }
  .tabs-fade::before, .tabs-fade::after { position:absolute; top:0; bottom:1px; width:50px; pointer-events:none; z-index:2; opacity:0; transition:opacity .18s ease; display:flex; align-items:center; color:var(--accent); font-size:28px; font-weight:800; line-height:1; }
  .tabs-fade::before { content:'‹'; left:0;  justify-content:flex-start; padding-left:9px;  background:linear-gradient(to right, var(--panel) 42%, rgba(20,27,36,0)); }
  .tabs-fade::after  { content:'›'; right:0; justify-content:flex-end;   padding-right:9px; background:linear-gradient(to left,  var(--panel) 42%, rgba(20,27,36,0)); }
  .tabs-fade.fade-l::before { opacity:1; }   /* more tabs to the left  */
  .tabs-fade.fade-r::after  { opacity:1; }   /* more tabs to the right */
  .tabs { display:flex; gap:6px; flex-wrap:nowrap; overflow-x:auto; -webkit-overflow-scrolling:touch; scrollbar-width:none; padding:12px 18px 0; border-bottom:1px solid var(--line); background:var(--panel); }
  .tabs::-webkit-scrollbar { display:none; }
  .tab { flex:0 0 auto; white-space:nowrap; padding:9px 14px; border-radius:8px 8px 0 0; border:1px solid transparent; border-bottom:none; color:var(--mut); background:none; }
  .tab.active { color:var(--txt); background:rgba(63,185,80,.16); border-color:rgba(63,185,80,.6); }
  /* ── SP-4 grouped nav ─────────────────────────────────────────────────────────────────────────
     A group button is a .tab that opens a menu. The menu itself is NOT a child of .tabs: .tabs is an
     overflow-x scroller (and carries a mask below 720px), so anything positioned inside it is clipped
     at the strip's edge. The single #navMenu element is appended to <body> and positioned from the
     button's rect, which has no clipping ancestor to escape. */
  .navgroup { flex:0 0 auto; display:inline-flex; }
  .tab-group { display:inline-flex; align-items:center; gap:5px; }
  .tab-group .caret { display:inline-flex; opacity:.7; transition:transform .15s ease; }
  .tab-group[aria-expanded="true"] .caret { transform:rotate(180deg); opacity:1; }
  .nav-menu { position:fixed; z-index:50; background:var(--panel); border:1px solid var(--line); border-radius:12px;
    box-shadow:0 8px 28px rgba(0,0,0,.5); padding:6px; min-width:196px; max-width:min(280px,92vw); }
  /* ⚠ THESE RULES MUST SURVIVE BOTH ELEMENT TYPES. Every entry was a <button> until Weekly Picks arrived
     as an <a> — a real link, because it leaves the app for the public card. The rule set was written for
     buttons and reset nothing a browser applies to anchors, so Weekly Picks rendered underlined and read
     as the odd one out rather than as a peer. `text-decoration` and `font` are declared explicitly for
     that reason; a button does not inherit the page font either, which is why it is stated rather than
     assumed. The menu should look like one list whatever each row happens to be made of. */
  .nav-menu .nav-item { display:block; width:100%; text-align:left; background:none; border:1px solid transparent;
    color:var(--txt); padding:10px 12px; border-radius:8px; font-size:14px; white-space:nowrap; overflow:hidden; text-overflow:ellipsis;
    text-decoration:none; font-family:inherit; font-weight:inherit; cursor:pointer; box-sizing:border-box; }
  .nav-menu .nav-item:hover { background:var(--panel2); }
  .nav-menu .nav-item.on { color:var(--accent); font-weight:700; background:var(--accent-dim); }
  /* TA-1020 — the Plays group dropdown renders the SAME flat list of entitled children (up to 9 rows)
     at every viewport width; there is no existing condensed/grouped mobile nav pattern anywhere else
     in this codebase to reuse (checked .ddwrap's filter dropdown and the account menu — neither
     groups or shrinks on narrow screens either), so this is a purely cosmetic density pass, not a new
     IA. Every row stays, in the same order, reachable the same way (`data-k` click -> goTab) — only
     the row height/type size shrink and the menu gets its own scroll so a short landscape-phone
     viewport can never clip the tail of the list the way the plain flow this element was positioned
     from (`openNavMenu`'s own.offsetHeight/innerHeight flip math) assumed it would always fit. */
  @media (max-width:599px){
    .nav-menu { padding:4px; max-height:min(72vh,420px); overflow-y:auto; }
    .nav-menu .nav-item { padding:8px 10px; font-size:13px; }
  }
  /* Contextual second row — the siblings of whatever you are looking at, so moving between two boards in
     the same group never costs a trip back through the menu. Lives inside .tabs-wrap so the computed
     --nav-h sticky offset picks it up automatically. */
  .subtabs { display:flex; gap:6px; flex-wrap:nowrap; overflow-x:auto; -webkit-overflow-scrolling:touch; scrollbar-width:none;
    padding:8px 18px; border-bottom:1px solid var(--line); background:var(--panel2); }
  .subtabs::-webkit-scrollbar { display:none; }
  .subtab { flex:0 0 auto; white-space:nowrap; background:none; border:1px solid var(--line); color:var(--mut);
    padding:5px 11px; border-radius:999px; font-size:12.5px; font-weight:600; }
  .subtab:hover { color:var(--txt); }
  .subtab.active { color:var(--accent-ink); background:var(--accent); border-color:var(--accent); font-weight:700; }
  /* ── TA-973 admin section tabs ──────────────────────────────────────────────────────────────────
     Scoped to renderAdmin()'s own body only (the admin view is `active==='admin'`, a standalone
     special case — see EXTRA_VALID_ACTIVE in renderApp — so there is no runtime collision with the
     real site nav today). Deliberately its OWN class rather than a literal reuse of .subtabs: a
     distinct class avoids a future specificity surprise if the site nav evolves, per the ticket.
     Sticky offset reuses the SAME --nav-h custom property renderApp() computes for the real nav —
     .rctl above is the existing precedent for a sticky row inside a page body keyed off --nav-h. */
  .admin-tabs-wrap { position:sticky; top:var(--nav-h,101px); z-index:3; margin:0 -18px 16px; padding:0 18px;
    background:var(--bg); border-bottom:1px solid var(--line); }
  .admin-tabs-fade { position:relative; }
  .admin-tabs-fade::before, .admin-tabs-fade::after { position:absolute; top:0; bottom:0; width:38px; pointer-events:none;
    z-index:2; opacity:0; transition:opacity .18s ease; display:flex; align-items:center; color:var(--accent);
    font-size:22px; font-weight:800; line-height:1; }
  .admin-tabs-fade::before { content:'‹'; left:0;  justify-content:flex-start; padding-left:6px;  background:linear-gradient(to right, var(--bg) 42%, rgba(20,27,36,0)); }
  .admin-tabs-fade::after  { content:'›'; right:0; justify-content:flex-end;   padding-right:6px; background:linear-gradient(to left,  var(--bg) 42%, rgba(20,27,36,0)); }
  .admin-tabs-fade.fade-l::before { opacity:1; }   /* more tabs to the left  */
  .admin-tabs-fade.fade-r::after  { opacity:1; }   /* more tabs to the right */
  .admin-tabs { display:flex; gap:6px; flex-wrap:nowrap; overflow-x:auto; -webkit-overflow-scrolling:touch; scrollbar-width:none;
    padding:10px 0; }
  .admin-tabs::-webkit-scrollbar { display:none; }
  .admin-tab { flex:0 0 auto; white-space:nowrap; background:none; border:1px solid var(--line); color:var(--mut);
    padding:6px 13px; border-radius:999px; font-size:13px; font-weight:600; }
  .admin-tab:hover { color:var(--txt); }
  .admin-tab.active { color:var(--accent-ink); background:var(--accent); border-color:var(--accent); font-weight:700; }
  .play { background:var(--panel); border:1px solid var(--line); border-radius:10px; padding:12px 14px; margin:8px 0; }
  .play .top { display:flex; justify-content:space-between; align-items:baseline; gap:10px; flex-wrap:wrap; }
  .play .pick { font-weight:800; font-size:17px; }
  .play .conv { color:var(--accent); font-weight:700; white-space:nowrap; }
  .play .why { color:var(--mut); margin-top:6px; font-size:13.5px; }
  /* TA-1303 §7 — card hierarchy reversal (Game Lines board card only): the matchup (game) line is now
     the bold/primary line, promoted above the pick; the pick line itself is demoted to `.side`, smaller
     and explicitly labeled "Your pick:". `.why` is untouched everywhere else it's reused in this file —
     this is a NEW class, not a restyle of `.why` in place, by design. */
  .play .matchup { font-size:17px; font-weight:700; color:var(--txt); margin-bottom:3px; line-height:1.3; }
  .play .side    { font-size:13.5px; font-weight:500; color:var(--mut); margin-bottom:12px; }
  .play .side b  { color:var(--txt); font-weight:700; }
  /* TA-1328 (David, 2026-11-13) — per-book badge row, re-verified against the actual mockup artifact
     (https://claude.ai/artifact/AFGdiZPSqXQu7EGWFjB3GN): a plain flex-wrap row of always-visible chips,
     each a direct hotlink to the book (one click, no tap-to-expand), followed by ONE always-on
     recommended-price note for the whole row (.badge-reco, mirrors the mockup's `.reco-note`) — never
     duplicated per book, never gated behind a click. Replaces the TA-1303 <details>/<summary>
     click-to-reveal, which required a second click to even see the "Bet at X" link and was never shown
     to David before shipping. Badges reuse .conf-chip/.conf-{tier} verbatim (styling reuse, not a new
     visual language). */
  .badge-row { display:flex; flex-wrap:wrap; gap:6px; margin-top:8px; }
  .badge-row > a.conf-chip, .badge-row > span.conf-chip { text-decoration:none; }
  .badge-reco { margin:6px 2px 2px; font-size:12.5px; }
  /* TA-1303 §4 — market-opinion badges (MONEYLINE/TOTAL/1ST HALF), one per market with real qualifying
     handicapper research. Reuses .handicap-chip's exact color token (--handicap is reserved exclusively
     for Handicapper content) composed with .conf-chip's base pill metrics, same convention as .opin-chip. */
  .mkt-badges { display:flex; flex-wrap:wrap; gap:6px; margin-top:6px; }
  .mkt-badge { display:inline-flex; align-items:center; gap:2px; cursor:pointer; text-decoration:none; border:1px solid color-mix(in srgb, var(--handicap) 45%, transparent); background:var(--handicap-dim); }
  .mkt-badge .chev { font-weight:800; }
  /* TA-1303 §5 — sharp-line comparison, replacing the old `.conv` "+Npt vs Pinnacle" text and oddsFair()'s
     rendered row on this card. Plain text weight (not --accent) — a comparison statement, not a verdict. */
  .sharp-line { color:var(--txt); font-size:13px; margin-top:6px; }
  .sharp-gap { color:var(--accent); font-weight:700; }
  /* TA-725 refinement pass — Games card title is league + full two-team matchup ("NFL · Seattle Seahawks
     @ Denver Broncos"), materially longer than every other `.play .pick` use (a single play name, e.g.
     "UNLV Rebels +1.5"). Reusing `.pick`'s 17px/800 sizing wrapped that content 4-5 lines on mobile,
     which both read as oversized gutters (lots of narrow wrapped lines inside the same real padding every
     other card uses) and produced wildly uneven card heights row to row. SCOPED to `.game-card` only —
     `.play .pick` itself is untouched, so Game Lines/Prop/Teaser cards are byte-for-byte unaffected. */
  /* David, live (2026-11-12) correcting the TA-1315-follow-up mobile-stack fix above, which stacked the
     date chip below the WHOLE left block (badge + title) on narrow viewports only — wrong shape (per
     his reference mockup, confirmed), and keyed to BROWSER viewport width, not the card's own width, so
     a narrow grid COLUMN on a wide desktop browser (3-up grid) triggered the same squeeze even though
     the viewport itself was nowhere near mobile. Correct, constant structure (TA-1294 + same-night
     follow-up), true at every width, no viewport media query involved at all: Row 1 = league badge
     (left) + date chip (right), same line, via `.game-card-headrow` below. Row 2 = the matchup title,
     full width, below Row 1 — always, not conditionally. Since the split is now a fixed two-row
     structure rather than something that only squeezes past a breakpoint, there is no "card narrower
     than N px" case left to special-case with @container either — stretch/column here is width-
     independent. align-items:stretch (was flex-start) so both rows span the full card width; the
     original flex-start was there to stop a wrapped multi-line title from vertically centering unevenly
     against its single-line sibling (TA-725) — moot now that the title is its own row with nothing beside
     it to center against, so this still preserves that original uneven-height fix's intent. */
  .game-card .top { display:flex; flex-direction:column; align-items:stretch; gap:6px; }
  .game-card-headrow { display:flex; justify-content:space-between; align-items:center; gap:8px; }
  .game-card-league { margin-bottom:0; }
  /* TA-725 refinement pass, round 2 (UX review, 2026-10-14) — min-height alone only reserves 2 lines for
     a SHORT title; it never capped a LONG one, so "Western Kentucky Hilltoppers @ Sam Houston State
     Bearkats"-length matchups (common — this slate is mostly NCAA FB, where mascot-heavy full names are
     the norm, not the exception) still ran to 4-5 lines and card heights stayed uneven across a grid row,
     the exact complaint this was supposed to fix. -webkit-line-clamp caps every title at the SAME 2
     lines, truncating with an ellipsis only on the rare matchup that needs it — paired with min-height so
     a short 1-line title still reserves the same 2-line block. The full matchup is never lost: it's still
     the page title one tap away in Game Detail. */
  /* TA-1303 §9 — replaces the viewport-based clamp above with a CONTENT-LENGTH-keyed fix (matchupSizeClass(),
     dashboard/index.html): -webkit-line-clamp silently dropped the opponent entirely on a long first-team
     name, with no visible ellipsis cue anything was missing. Clamp/overflow:hidden removed — nothing is
     ever silently dropped at any screen width again. Named side effect of this ticket (TA-1303 Task 7/9):
     this class lives on Best Angles (:7685-area)/All-Games grid (:8227/:9097-area), NOT on the Game Lines
     board card's own new `.matchup` (no clamp bug there — different class, untouched by this rule).
     Base rule keeps a default 15px (byte-identical to the old flat size) for any caller that doesn't also
     apply one of the three length buckets below. Variable card height on a long name is an accepted
     tradeoff (UX Reviewer flagged, see build plan §9) in exchange for "always fully visible." */
  /* TA-1294 asked to "center the whole card header block (badge/date row + title) as a block, rather
     than left-aligned." Checked directly against the reference mockup's own source (UX Reviewer gate,
     2026-11-13), not just the ticket text: the mockup's `.matchup` rule (font-size:17px; font-weight:700;
     color:var(--ink); margin-bottom:3px; line-height:1.3;) carries no text-align property at all — left-
     aligned by default, same as every other line on the card (`.side`, `.tier-row`, etc.). Nothing in the
     reference design is centered, anywhere. A prior pass here added text-align:center to this rule,
     reading TA-1294's ask as still partially live once Row 1 (`.game-card-headrow`) kept its explicit
     badge-left/chip-right layout — that reconciliation doesn't survive contact with the actual mockup:
     the real answer is "nothing in this header is centered, full stop," so no text-align override at all,
     left-aligned by the browser's own block default like every other line on the card. */
  .game-card-title { font-weight:700; font-size:15px; line-height:1.32; display:block; overflow:visible; }
  .matchup-lg.game-card-title { font-size:17px; }   /* e.g. "Buffalo Bills @ New York Jets" (29 chars) */
  .matchup-md.game-card-title { font-size:15.5px; } /* e.g. "Ole Miss Rebels @ Oklahoma Sooners" (34 chars) */
  .matchup-sm.game-card-title { font-size:14px; }   /* e.g. "Western Kentucky Hilltoppers @ Sam Houston State Bearkats" (57 chars) */
  .badge { font-size:11px; padding:2px 8px; border-radius:999px; border:1px solid var(--line); color:var(--mut); display:inline-block; white-space:nowrap; } /* inline-block+nowrap so the pill never splits its border across a line-wrap (mobile clip fix) */
  /* TA-921 — one small, consistent "this isn't finished yet" marker (docs/specs/design/CARD-SYSTEM-
     MOCKUP-2026-10-25.md §4), plain English per this product's voice ("PREVIEW", never "Beta"). Same
     metrics as .badge (same pill, same nowrap-clip fix) so it never looks like a third, unrelated
     shape next to a tab label — only the warn color is distinct, and warn here means "incomplete",
     never the "real problem" alarm-red this dashboard reserves for staleness/broken feeds elsewhere. */
  .preview-badge { font-size:10px; font-weight:800; letter-spacing:.4px; text-transform:uppercase; padding:1px 7px; border-radius:999px; border:1px solid color-mix(in srgb, var(--warn) 45%, transparent); color:var(--warn); background:color-mix(in srgb, var(--warn) 12%, transparent); display:inline-block; white-space:nowrap; }
  /* BL-61 confidence grade */
  .conf-row { display:flex; align-items:baseline; gap:8px; margin-top:4px; flex-wrap:wrap; }
  /* D2 tier ladder (shared voice — matches .p-tierpill + .potd-prime): PRIME=gold hero · STRONG=dim green ·
     SOLID=teal outline (one step down from Strong's fill, same --tier-strong token — a real qualified
     tier, not lumped with "not qualified") · LEAN/WATCH=neutral (TA-734, 2026-10-16: found live that
     Solid rendered byte-identical to Lean/no-edge, risking a real third-tier pick reading as "nothing
     here" to a fast scanner. Deliberately NOT var(--blue) — that's reserved by .conf-Standard below for a
     genuinely different concept and its own comment explicitly depends on Solid staying out of that
     color). */
  .conf-chip { font-size:11px; font-weight:800; padding:2px 9px; border-radius:999px; border:1px solid var(--line); white-space:nowrap; letter-spacing:1px; color:var(--mut); text-transform:uppercase; }
  /* TA-1196 — the real captured 1st-half total price chip (dashboard/index.html's h1PriceChipHtml()).
     Deliberately NOT .conf-chip's tier-colored treatment, and deliberately NOT given any accent/green —
     this is a raw sportsbook number, not a graded opinion, and must never visually compete with or be
     mistaken for the tier-colored conf-chip pills on the same card. Small, muted-neutral only. */
  .h1-price-chip { display:inline-block; margin-left:6px; font-size:10.5px; font-weight:700; padding:1px 7px; border-radius:999px; border:1px solid var(--line); color:var(--mut); font-variant-numeric:tabular-nums; white-space:nowrap; }
  /* TA-841 — .opin-chip is Our Opinion's own badge shape (docs/specs/handicapper/CONVICTION-BADGE-SHAPES.md
     §2), composed with the EXISTING .conf-Prime/.conf-Strong/.conf-Solid/.conf-Lean tier-color classes
     verbatim (never redefined) — e.g. <span class="opin-chip conf-Prime">PRIME</span>. SAME base metrics
     as .conf-chip (font-size/weight/padding/letter-spacing/case/nowrap) so the two sit flush at equal
     height/baseline when adjacent. MUST be declared BEFORE .conf-Prime/.conf-Strong/.conf-Solid/.conf-Lean
     (it is, right here) so those tier classes still win on background/color/border/box-shadow when
     composed with it — only border-radius ever differs between an Opinion badge and an Analytics badge
     at the same tier.
     REAL VISUAL FINDING, ROUND 1 (2026-10-22, real Chrome render at true 11px size, zoomed screenshot,
     lowest-contrast Lean tier specifically): the Design Lead's proposed subtle corner-radius "tag"
     silhouette (border-radius: 2px 999px 999px 2px) was NOT reliably perceptible at a glance. A single
     cut/rounded corner (a "diamond-B" clip-path tried next) was then shown to David directly in a live
     swatch comparison — his verdict: a single-corner treatment "looks off or like it's been cut off," a
     rendering-glitch read, not an intentional shape.
     REAL VISUAL FINDING, ROUND 2 (2026-10-22, David's own live review of 5 real rendered candidates — Pill
     reference, full-rectangle, compact-boxy, elongated-hexagon, true-octagon): a FULL RECTANGLE with sharp
     square corners on all four sides read as the clearest, most obviously-intentional alternative to the
     pill at every tier tested, including Lean (the lowest-contrast case) — no ambiguity, no clipped-glyph
     risk, and the simplest possible CSS (one property, zero clip-path edge cases, nothing to break across
     browsers or future tier-color changes). Shipped as border-radius: 0 — still passes the spec's §0
     color-first test (a gold rectangle next to a gold pill still reads as "two golds" at a glance), since
     only the corner treatment changed, not fill/icon/size. See the TA-841 build handoff for the actual
     screenshots and the full swatch comparison (6 candidates total) this decision was made from. */
  .opin-chip {
    font-size: 11px;
    font-weight: 800;
    padding: 2px 10px;
    border-radius: 0;
    border: 1px solid var(--line);
    white-space: nowrap;
    letter-spacing: 1px;
    color: var(--mut);
    text-transform: uppercase;
  }
  .conf-Prime { background:var(--prime); color:var(--prime-ink); border:0; box-shadow:0 4px 14px -4px var(--prime-glow); }
  .conf-Strong { background:var(--tier-strong-dim); color:var(--tier-strong); border:1px solid color-mix(in srgb,var(--tier-strong) 45%,transparent); }
  .conf-Solid { background:transparent; color:var(--tier-strong); border:1px solid color-mix(in srgb,var(--tier-strong) 35%,transparent); }
  .conf-Lean { background:transparent; color:var(--mut); border:1px solid var(--line); }
  /* TA-1136 — EXECUTION button (sportsbook deep-link), tier-colored VERBATIM per .conf-Prime/.conf-Strong/
     .conf-Solid/.conf-Lean above (never redefined, never a flat accent) — the David-approved addendum
     correction. Pass intentionally has NO .exec-Pass variant: _execPrimaryHtml() returns '' for a Pass
     tier (see that function's own header — "demote a juice-killed play: dim it, no green, no bet button",
     .play.pass's own comment, confirmed real existing behavior, not new). Deliberately a DIFFERENT
     selector from .ba-bookbtn (the existing per-book shopping-list chip below, left untouched) — this is
     the ONE primary "place it" action per row/strip; everything else stays a plain secondary chip. */
  .exec-btn { display:inline-flex; align-items:center; gap:6px; font-size:12.5px; font-weight:800; padding:7px 11px; border-radius:8px; text-decoration:none; white-space:nowrap; }
  .exec-Prime { background:var(--prime); color:var(--prime-ink); border:0; box-shadow:0 4px 14px -4px var(--prime-glow); }
  .exec-Strong { background:var(--tier-strong-dim); color:var(--tier-strong); border:1px solid color-mix(in srgb,var(--tier-strong) 45%,transparent); }
  .exec-Solid { background:transparent; color:var(--tier-strong); border:1px solid color-mix(in srgb,var(--tier-strong) 35%,transparent); }
  .exec-Lean { background:transparent; color:var(--mut); border:1px solid var(--line); }
  /* Codex review finding, confirmed real — an ungraded offer (no sharp reference) must never claim a
     Lean tier it didn't earn. Neutral, same treatment .ba-bookbtn.t-none already uses for this exact
     case. */
  .exec-None { background:transparent; color:var(--mut); border:1px solid var(--line); }
  .exec-btn.tap:hover { filter:brightness(1.07); }
  /* HALO FRAME (tonight's build) — docs/specs/handicapper/CONVICTION-BADGE-SHAPES.md's own shape split
     (.conf-chip pill = Our Analytics, .opin-chip rectangle = Our Opinion) renders completely unchanged —
     this is a pure OUTER wrapper around the pair, never a redefinition of .conf-chip/.opin-chip or any
     .conf-Prime/.conf-Strong/.conf-Solid/.conf-Lean color rule. It composes around whatever markup the
     caller already builds (JS decides WHEN to apply it — see _haloFrameTier() in dashboard/index.html);
     this stylesheet only owns what it looks like once applied. inline-flex + a little padding gives the
     glow real room to breathe around BOTH chips without touching either chip's own border-radius/shape;
     the wrapper's own radius is generous (999px) purely so the glow silhouette doesn't itself read as a
     hard-edged box — it never clips or reshapes its children. */
  .halo-frame { display:inline-flex; align-items:center; gap:6px; padding:3px 6px; border-radius:999px; }
  .halo-Prime { box-shadow:0 0 0 1px color-mix(in srgb, var(--prime) 55%, transparent), 0 0 16px 2px var(--prime-glow); }
  .halo-Strong { box-shadow:0 0 0 1px color-mix(in srgb, var(--tier-strong) 50%, transparent), 0 0 14px 2px color-mix(in srgb, var(--tier-strong) 45%, transparent); }
  /* TA-731 Game Intelligence — Read/Opinion/Recommendation. Reuses .conf-chip/.conf-Prime etc for the
     Qualified tier badge (same tier vocabulary, same colors, never redefined); these are the NEW
     section/state classes specific to this card. */
  .gi-card { padding:16px 18px; }
  .gi-sec { margin-bottom:14px; }
  .gi-sec:last-child { margin-bottom:0; }
  .gi-sec-h { font-size:11px; font-weight:800; letter-spacing:1.5px; color:var(--mut); margin-bottom:6px; }
  .gi-basis { font-size:10.5px; font-weight:700; letter-spacing:.5px; text-transform:uppercase; color:var(--accent); margin-left:4px; }
  .gi-rec { padding:10px 12px; border-radius:10px; margin-bottom:8px; border:1px solid var(--line); font-size:13.5px; }
  .gi-rec:last-child { margin-bottom:0; }
  .gi-rec-qualified { border-color:var(--accent); background:color-mix(in srgb, var(--accent) 7%, transparent); }
  .gi-rec-lean { border-style:dashed; }
  .gi-rec-none { color:var(--mut); font-style:italic; }
  .gi-rec-cross { color:var(--mut); font-size:12.5px; background:transparent; border-style:dashed; }
  /* TA-813 — THE OPINION is now Handicapper's own independent voice (see renderGameIntelligence's own
     header comment), not Game Intelligence's market-math content. A quiet left-border accent in the
     SAME --handicap token already used by the AGREES/SPLIT chip/1H/TOTAL badges/research dot — never
     a new color, never a tier color — is enough to mark it as a visually distinct voice from the
     neutral THE ANALYSIS section above it, without inventing a new treatment. */
  .gi-sec-handicap { border-left:3px solid var(--handicap); padding-left:10px; margin-left:-10px; }
  /* TA-982 Task 1 — "Two Plays, One Card" new classes ONLY (docs/specs/design/TA-982-TWO-PLAYS-ONE-CARD-
     BUILD-PLAN.md; mockup https://claude.ai/artifact/EC1iPswHXecJJraMY9jQAp, round 3). NOT consumed by any
     render path yet — PRs 2-4 in TA-982's own sequencing wire Game Intelligence, Best Angles/My Research,
     and the All Games grid onto these. This PR changes zero existing selectors; `.conf-chip`/`.opin-chip`/
     `.conf-Prime` etc. and `.game-card`/`.gi-sec*`/`.gi-rec*` are reused verbatim by future PRs, untouched
     here (confirmed already-compatible per the spec's own "what's already real" audit).
     Token mapping: every value below is pulled from the mockup's own `<style>` block, which the mockup's
     footer states was itself "pulled verbatim from dashboard/styles.efdb8cca.css and CONVICTION-BADGE-
     SHAPES.md" — so this is the SAME token set already defined above (--bg/--panel/--panel2/--line/--txt/
     --mut/--accent/--accent-dim/--warn/--bad/--blue/--prime/--prime-glow/--tier-strong/--tier-strong-dim/
     --handicap/--font-num), never a second invented token set.
     `.q-kind` is deliberately ONE muted tone, not a per-kind color — GPT-5.1's round-3 review (relayed in
     the spec) flagged a colored kind-label as a THIRD color system competing with the badge's own tier
     color; the dimension word inline in `.q-dim` carries the distinction instead, same bold weight as the
     question text next to it, per David's "present the work... make it clear" direction.
     NO transition/@keyframes/animation anywhere in this block — TA-1002 (flip-flop/hysteresis, separate
     ticket) means a side/tier can change between board refreshes, and the spec explicitly says nothing
     here should draw a member's eye to that change. Forward note for PRs 2-4 (not acted on in this PR,
     which adds no render path): `.game-card-title`'s own comment two sections above this one documents a
     real fought-before uneven-card-height problem on this exact `.game-card` shell — a future PR stacking
     two `.signal` blocks in one card should re-check that comment's context before assuming the grid
     tolerates the added height variance, per the spec's own Edge Cases section. */
  .signal { padding:14px 0; }
  .signal:first-child { padding-top:0; }
  .signal:last-child { padding-bottom:0; }
  .signal + .signal { border-top:1px dashed color-mix(in srgb, var(--line) 65%, transparent); }
  .sig-q { font-size:15px; font-weight:800; line-height:1.3; margin-bottom:8px; color:var(--txt); }
  .sig-q .q-kind { display:block; font-size:10.5px; font-weight:800; letter-spacing:1.3px; text-transform:uppercase; margin-bottom:3px; color:var(--mut); }
  .sig-q .q-dim { color:var(--accent); }
  /* TA-1035 — Our Analytics grid card ONLY (sigQuestionHtml's `compact` opt): the kind-label folds onto
     the SAME line as the dimension/question instead of its own line above it — two stacked .signal
     blocks (Price-Value + Team-Read) were spending 4 lines on question framing alone before either pick
     was visible. Same words, same information, never a content change — just one line instead of two,
     applied identically to BOTH signal kinds (never asymmetric — see David's "neither outranks the
     other" ruling, PR #1076). Game Detail's own question line (no `compact` passed) is untouched. */
  .sig-q-compact { margin-bottom:5px; }
  .sig-q-compact .q-kind-inline { font-size:10.5px; font-weight:800; letter-spacing:0.6px; text-transform:uppercase; color:var(--mut); margin-right:5px; }
  .sig-row { display:flex; align-items:center; gap:9px; margin-bottom:5px; flex-wrap:wrap; }
  .sig-pick { font-family:var(--font-num); font-size:18px; font-weight:700; font-variant-numeric:tabular-nums; font-feature-settings:"tnum" 1; }
  .sig-price { color:var(--mut); font-size:13px; }
  .sig-engine { color:var(--mut); font-size:11px; margin-left:auto; white-space:nowrap; }
  .sig-why { color:var(--mut); font-size:12px; margin-top:6px; display:flex; align-items:center; gap:5px; cursor:pointer; }
  .sig-why::before { content:"\2039"; display:inline-block; color:var(--accent); font-weight:800; }
  .agree-banner { display:flex; align-items:center; gap:7px; background:var(--accent-dim); border:1px solid color-mix(in srgb, var(--accent) 35%, transparent); border-radius:8px; padding:7px 11px; font-size:12.5px; font-weight:700; color:var(--accent); margin-bottom:10px; }
  .agree-banner .ic { font-size:14px; }
  /* TA-1108 — Design Lead legibility pass: this is the research/opinion long-form reasoning copy
     (Game Detail's Our Analytics/Our Opinion rows AND the Games-list signal cards' "View reasoning"
     reveal share this one class). It was 12px at var(--mut) — 3px under body text (15px) and the
     lowest-contrast gray token on dark panels (~5.2:1 on --panel2 vs --txt's ~14.6:1 on --panel),
     confirmed live on a real rendered game page at 390px: it read smaller AND flatter than every
     surrounding label/header, "nothing that causes it to stand out" (David's own words). Bumped to
     14px/var(--txt) to read near body-base size at full text contrast, same color token the site's
     own highest-legibility body copy (.modal's reasoning paragraph, .sig-q) already uses — no new
     color/size token invented. Chrome (padding/background/border-left accent) is unchanged. */
  .basis-note { font-size:14px; line-height:1.55; color:var(--txt); margin-top:7px; padding:8px 10px; background:var(--panel2); border-radius:7px; border-left:2px solid var(--blue); }
  .basis-note b { color:var(--txt); font-weight:700; }
  .basis-note.model-opinion { border-left-color:var(--tier-strong); }
  /* TA-1213 revision — "Opinion changed" note needed more visual presence than plain .muted grey
     footnote text (David: shipped treatment read as "just a little innocent footnote"), without
     becoming an alert or a new recommendation. Design Lead spec: own --history token (blue-grey,
     reads as "record/time", distinct from --warn/--bad/--tier-strong/--handicap), left border +
     tinted background card instead of bare muted text, label gets its own color + icon. The dated
     entry lines themselves stay .muted grey body text — only the border/background/label change. */
  .opinion-change-log {
    border-left: 2px solid var(--history);
    border-radius: 6px;
    background: var(--history-dim);
    padding: 6px 10px;
    margin-top: 6px;
    margin-left: -10px;
  }
  .opinion-change-log .ocl-label {
    display: inline-flex;
    align-items: center;
    gap: 5px;
    color: var(--history);
    font-weight: 700;
    margin-bottom: 2px;
  }
  /* David, 2026-11-13 — the Games tab's "best play outside your filters" exception strip (TA-1222 Part D
     Task D8, renderFilterExceptionStrip()) shipped as plain 11.5px .muted gray text, which read as
     throwaway and never explained WHY the card above it ignores the member's own League/Tier filters.
     Reuses the SAME --history/--history-dim left-border-card treatment as .opinion-change-log above
     (same underlying idea: a quiet fact worth noticing, not a problem) rather than inventing a new
     color — deliberately NOT --warn/--bad, since this isn't an alert, it's an honest exception to a
     filter the member set themselves. */
  .filter-exception-banner {
    display: flex;
    align-items: flex-start;
    gap: 7px;
    border-left: 2px solid var(--history);
    border-radius: 6px;
    background: var(--history-dim);
    padding: 8px 10px;
    margin: 0 2px 8px;
    font-size: 12.5px;
    line-height: 1.5;
    color: var(--txt);
  }
  .filter-exception-banner .feb-icon {
    color: var(--history);
    flex: 0 0 auto;
    margin-top: 1px;
  }
  .filter-exception-banner .feb-text b {
    color: var(--history);
    font-weight: 700;
  }
  /* TA-1344 (second amendment) — "Angle of the Day" cross-filter teaser. Replaces the old unconditional
     full-card placement above: a thin collapsed line (never a boxed card — deliberately no .panel
     background/14px border-radius shell) sits above the member's own filtered grid only when the
     gating logic in renderFilterExceptionStrip() decides it actually matters; expands in place to
     reveal the SAME real card component, dismissible, never mutating the member's saved filters. */
  .aod-section { margin: 0 2px 14px; }
  .aod-teaser { display:flex; align-items:center; gap:9px; padding:8px 13px; border-radius:9px;
    background:var(--panel2); border:1px solid var(--line); border-left:3px solid var(--action-teal);
    font-size:12.5px; color:var(--mut); margin:0 0 10px; cursor:pointer; max-width:640px; }
  .aod-teaser b { color:var(--txt); font-weight:700; }
  .aod-icon { font-size:13px; line-height:1; flex:0 0 auto; }
  .aod-text { flex:1 1 auto; min-width:0; }
  .aod-chevron { color:var(--mut); font-size:15px; flex:0 0 auto; margin-left:2px; }
  .aod-teaser[aria-expanded="true"] .aod-chevron { transform:rotate(90deg); display:inline-block; }
  .aod-dismiss { background:none; border:none; color:var(--mut); font-size:15px; cursor:pointer;
    padding:0 2px; line-height:1; flex:0 0 auto; opacity:.75; }
  .aod-dismiss:hover { color:var(--txt); opacity:1; }
  .aod-expanded { margin:0 0 16px; padding:12px 14px 4px; border:1px dashed color-mix(in srgb,var(--action-teal) 45%,var(--line)); border-radius:12px; background:color-mix(in srgb,var(--action-teal) 4%,transparent); }
  .aod-expanded-label { font-size:10.5px; font-weight:800; letter-spacing:.4px; text-transform:uppercase; color:var(--action-teal); margin:0 0 8px 2px; }
  .aod-honest-label { font-size:13px; font-weight:700; color:var(--txt); margin:0 2px 10px; }
  /* TA-1214 — My Bets' own "Opinion changed since you placed this bet" flag. Same --history token as
     .opinion-change-log above (same underlying fact, surfaced in a second place) but needed MORE
     visibility than that quiet footnote (David's ask) — achieved via a full-width clickable row +
     bold lead + hover state, NOT a louder color. Body copy stays at normal text contrast (not .muted
     grey) since this one should read as more prominent than the Game Detail note. */
  .mb-opinion-changed {
    display: flex;
    align-items: flex-start;
    gap: 8px;
    width: 100%;
    text-align: left;
    border: none;
    border-left: 2px solid var(--history);
    border-radius: 6px;
    background: var(--history-dim);
    color: var(--txt);
    padding: 8px 10px;
    margin-top: 8px;
    font: inherit;
    font-size: 13px;
    line-height: 1.4;
    cursor: pointer;
  }
  .mb-opinion-changed:hover {
    background: color-mix(in srgb, var(--history) 16%, transparent);
  }
  .mb-opinion-changed .ic {
    color: var(--history);
    flex: 0 0 auto;
    margin-top: 1px;
  }
  .mb-opinion-changed b {
    color: var(--history);
  }
  /* TA-1049 Layer 1 — cushion-integrity disclosure (betting/confidence.mjs's applyCushionIntegrityDisclosure).
     Design Lead review (TA-1049): the FIRST draft of this rule used var(--handicap) — WRONG, caught before
     ship. The-Angle's own Brand-System.md (Palette table) reserves --handicap EXCLUSIVELY for Handicapper's
     own independent-opinion voice (the AGREES/SPLIT chip, 1H/TOTAL/PARLAY badges) and says explicitly: "Any
     future Handicapper-surfacing UI... must use THIS token, never a tier color — reusing [another] token for
     a[nother] conviction level would misrepresent it." This disclosure is Price-Value/spread-math, has
     nothing to do with Handicapper — reusing --handicap here would have misrepresented it as a Handicapper
     read, the exact collision the brand doc warns about. Fixed to --mut (the existing neutral muted-text
     token, already used for this file's own default `.basis-note` text color) instead of any tier/engine
     color: deliberately NOT --warn/--bad (this is an always-true spread-math fact, not an alarm or a tier
     demotion — no evidence a zero-cushion PRIME pick underperforms a wide-cushion one), NOT --blue (whyHtml's
     own default — would blend the two notes together), NOT --tier-strong (Our Opinion's lane) or --handicap
     (Handicapper's lane, as above). A neutral gray reads as "informational," not a signal from any one
     engine — correct, since Layer 1 is independent of Team-Skill/Handicapper/Opinion entirely. */
  .basis-note.cushion-note { border-left-color:var(--mut); }
  /* TA-1049 — Team-Skill Model's own unmistakable card lane. Found live (David, UConn Huskies @ Air
     Force Falcons, then a second confirmed live-member incident on Arizona Wildcats @ Texas Tech Red
     Raiders): the Team-Skill win-prob number rendered with NO badge at all (correct — it has no tier) but
     shared the exact same plain `.signal` row layout AND the same bold accent-green "WINNER" headline
     treatment as Our Opinion's own real picks, so a member could read the percentage as "the site's pick."
     ROUND 1 (container + tag only, amber) got a cold Grok "no sign-off" on the real before/after
     screenshots: amber is visually adjacent to --prime's gold PRIME fill ("will be read as the premium
     call"), and "Independent model" collided with Team-Read's own pre-existing "my own independent read"
     copy. ROUND 2 — blue instead of amber; "Stat model — not a pick" instead of "Independent model"; the
     dimension word is now this kind's own muted "MODEL READ", never the shared accent-green "WINNER" text
     Team-Read's real picks use (see sigQuestionHtml()'s own comment).
     ROUND 4 (Design Lead gate, BLOCKING finding) — blue was ALSO already claimed: `.conf-Standard` (a
     real, live tier, "Standard Angle," ranked between Lean and Solid) renders as a solid blue pill. Since
     Price-Value and Team-Skill compose onto the SAME card for every game, a Standard-tier Price-Value
     pick sits a blue rank pill directly next to this block's own blue "not a pick" tag — a NEW instance
     of the exact rank-vs-non-rank color collision this ticket exists to fix. Every other hue in this
     palette is already claimed too (gold/--prime, green/--accent & --tier-strong, red/--bad, violet/
     --handicap, amber/--warn). Fix: drop the hue entirely — genuinely neutral gray (`--mut`/`--line`,
     the same desaturated tokens used for inert/no-rank UI sitewide, e.g. `.conf-Watch`), never another
     color-wheel hue, so this can never again collide with a future tier color. Design Lead confirmed
     shape + copy + position (the dashed tag, the smaller/lighter number, "win probability" inline) were
     already doing the real work — the fill color was never load-bearing. No tier badge is added here;
     that's correct, not something this ticket changes. */
  .basis-note.model-skill { border-left-color:var(--mut); }
  .signal-model { background:color-mix(in srgb, var(--mut) 7%, transparent); border:1px solid color-mix(in srgb, var(--mut) 28%, transparent); border-radius:10px; padding:12px 12px 10px; margin:4px 0; }
  .signal-model + .signal, .signal + .signal-model { border-top:none; }
  .model-tag { display:inline-block; font-size:10px; font-weight:800; letter-spacing:1.1px; text-transform:uppercase; padding:2px 7px; margin-right:1px; border:1px dashed var(--mut); border-radius:4px; color:var(--mut); background:transparent; white-space:nowrap; }
  /* ROUND 3 — cold Grok re-check on round 2: the percentage was still "a huge bold team name, same
     scale as [a real pick]" — relabeling the tag alone didn't change the HERO LINE's own type weight.
     Deliberately smaller/lighter here, never the same 18px/700/--txt treatment `.sig-pick` (a real pick)
     uses — so even a fast scan reads this number as data, not a verdict. ROUND 4 — color is --mut (see
     this block's own header comment), not --blue. */
  .sig-pick-model { font-size:16px; font-weight:600; color:var(--mut); }
  .sig-pick-model-suffix { font-size:12px; font-weight:600; color:var(--mut); margin-left:6px; text-transform:none; letter-spacing:normal; }
  .sig-q .q-dim-model { color:var(--mut); }
  /* ROUND 3 — the disagreement acknowledgment (both the Team-Skill card's own copy and Team-Read's new
     reciprocal marker) promoted OUT of `.basis-note` — cold Grok re-check found round 2's version "a
     second gray paragraph, same weight as the methodology note above it," easy to scan past. A distinct
     left-accent callout, bold lead so it reads as a flag even in a fast scroll. ROUND 4 (Design Lead gate)
     — neutral gray (`--mut`/`--line`), not `--blue`: see `.signal-model`'s own header comment for why
     every hue, blue included, was ruled out. */
  .model-disagree-note { font-size:12px; line-height:1.5; color:var(--txt); margin-top:7px; padding:8px 10px; background:color-mix(in srgb, var(--mut) 12%, transparent); border-radius:7px; border-left:3px solid var(--mut); font-weight:600; }
  /* TA-1222 Phase 2 (CR-1/CR-7) — Band-1 "Opinion: same side / other side / toss-up" marker. Deliberately
     NEITHER a plain --mut secondary-text treatment (too easy to skim past in a 3-second scan) NOR a
     warning color (--warn/--bad would wrongly imply "don't bet this" — a real Prime/Strong play can
     still disagree with Opinion). --txt at 700 weight, no background/border box (keeps card density down,
     matches the agree-and-disagree-both-present requirement without a chrome box competing with the
     tier pill above it) — prominent-but-neutral, present on every qualifying state. Never a tier hue
     (gold/teal-fill/teal-outline/grey) — CR-7's hard constraint. */
  .opinion-marker { font-size:12.5px; font-weight:700; color:var(--txt); margin:3px 2px 0; }
  /* TA-1222 Phase 2 (CR-2) — market type stated in words as part of the headline text itself (a member
     scanning fast could otherwise grab a 1st-half card thinking it's full-game, or vice versa) — never
     relying on a small badge alone. Muted, same weight class as the rest of the headline's secondary
     detail, never competing with the team/number itself. */
  .market-type-words { color:var(--mut); font-weight:600; font-size:12.5px; }
  /* TA-1035 — Our Analytics grid card: an Opinion (.signal, TEAM_READ) block's reasoning paragraph,
     default CLOSED behind this toggle, so a card carrying a qualifying Opinion read stays visually
     comparable in height to sibling cards in the same row that have no Opinion signal to show (the
     content itself is unchanged, same .basis-note markup inside — just not forced open by default).
     Same native <details>/<summary> progressive-disclosure idiom as .pk-why/.backtest above; styled in
     this card's OWN muted-chevron-link voice (.game-card-cta's "View game insights ›") rather than
     those two's bullet-triangle marker, since this lives inside the card body, not below it.
     TA-1033 round 4 — reused verbatim (same class name, same chevron-link voice) for a non-actionable
     Opinion state (pass-at-price/toss-up) on Game Detail's "The Angle's Read" card (_giSignalBlockHtml)
     and the My Research card (_myResearchCardHtml) — the two surfaces where a model sentence like "I
     like Purdue here" could sit directly under, and contradict, the bold "Pass — lean only..." action
     line.
     TA-1038 — widened further: Game Detail now collapses ALL supporting paragraphs (Price-Value's "why"
     note AND Team-Read's reasoning/scoringLean) behind this SAME toggle, regardless of actionable state
     — see _giSignalBlockHtml's own header for the full writeup. Content is never edited, truncated, or
     reworded by any of this — only whether it starts open or closed. */
  .sig-reasoning { margin-top:6px; }
  .sig-reasoning > summary { cursor:pointer; list-style:none; color:var(--accent); font-size:12px; font-weight:600; user-select:none; }
  .sig-reasoning > summary::-webkit-details-marker { display:none; }
  .sig-reasoning > summary::after { content:' \203A'; }
  .sig-reasoning[open] > summary::after { content:' \2304'; }
  .sig-reasoning[open] > summary { color:var(--mut); font-weight:400; }
  .sig-reasoning > .basis-note { margin-top:6px; }
  /* TA-1033 round 5 — three independent styling-only rounds (muting the pick-row text, reordering the
     action line ahead of it, collapsing the reasoning) each independently failed cold review for the
     SAME root cause: the team name rendered as subject of "<team> to win" still reads as a pick no
     matter how it's de-emphasized, reordered, or boxed. David picked Grok's concrete fix over GPT-5.1's
     (see dashboard/index.html's _noBetBlockHtml() header for the full history): on a non-actionable
     Opinion read, the OLD pick-row component (badge + "<team> to win") is replaced outright by this
     component, never rendered alongside it. `.no-bet-chip` is a deliberately different SHAPE (4px
     corners, not .conf-chip's 999px pill or .opin-chip's 0-radius rectangle) AND a deliberately
     different COLOR (--bad red, never a tier color) from every real Lean/Solid/Strong/Prime chip on
     this app, so it can never visually pass as a graded pick — and it is never, ever the word "Lean"
     (that word names one specific real rung of the Lean→Solid→Strong→Prime ladder elsewhere in this
     product; reusing it here would make a non-pick look like a graded one). */
  .no-bet-top { display:flex; align-items:center; justify-content:space-between; gap:10px; flex-wrap:wrap; margin-bottom:6px; }
  .no-bet-verdict { font-size:21px; font-weight:900; letter-spacing:.5px; line-height:1.15; color:var(--bad); }
  .no-bet-chip { font-size:11px; font-weight:800; letter-spacing:1px; text-transform:uppercase; white-space:nowrap; color:var(--bad); border:1px solid color-mix(in srgb, var(--bad) 45%, transparent); background:color-mix(in srgb, var(--bad) 10%, transparent); padding:3px 10px; border-radius:4px; }
  /* The team-name sentence renders in the page's ordinary muted body copy — deliberately NOT the
     `.sig-pick` slot (18px, var(--font-num), tabular numerals) where every actionable pick's team name
     actually lives, and never bold/large — so it reads as the OBJECT of "No bet on ___", one plain
     sentence, never a second claim competing with the verdict above it. */
  .no-bet-sentence { font-size:13.5px; color:var(--mut); line-height:1.45; }
  .no-bet-sentence b { color:var(--txt); font-weight:700; }
  .no-bet-lean-note { font-size:11.5px; color:var(--mut); margin-top:4px; font-style:italic; }
  /* Standard Angle (Confidence Signal Lab, 2026-10-05) — a validated recommendation CLASS (the production path itself
     has earned a real closing-line-value track record) where we do NOT yet have evidence to differentiate
     individual plays by conviction the way Prime/Strong/Solid/Lean do. Deliberately its OWN visual
     treatment, not borrowed from any existing tier — borrowing Solid's or Lean's color would wrongly imply
     this sits on the SAME graded ladder as a line-shop play that cleared gradePlay()'s actual scoring.
     Blue reads as "real and trustworthy," distinct from the muted/neutral Solid-Lean-Watch family and far
     from Prime's gold hero treatment, matching the explicit "do not invent football conviction this signal
     doesn't earn" guardrail this class was built under. */
  .conf-Standard { background:color-mix(in srgb,var(--blue) 14%,transparent); color:var(--blue); border:1px solid color-mix(in srgb,var(--blue) 45%,transparent); }
  .conf-Watch { background:transparent; color:var(--mut); border:1px solid var(--line); }
  .conf-Pass { color:var(--bad); border-color:var(--bad); } /* juice kills the edge — not a bet (one true brand red) */
  .play.pass { opacity:.62; } /* demote a juice-killed play: dim it, no green, no bet button */
  /* ═══ TA-785/TA-778 — Agreement-Connector Chip Pair ═══════════════════════════════════════════════
     Handicapper's independent lean, shown next to the existing tier chip wherever it already renders
     (Best Angles, Games Grid, Game Detail). Renders nothing at all when there's no cached read for a
     pick — this whole block, byte-identical to not existing, per the same honest-omission convention
     already used elsewhere in this app (an omitted bet control, an omitted untracked book row).
     Chip shell IDENTICAL to .conf-chip (same 11px/800-weight/999px-pill shape), border/bg swapped to
     the new --handicap token — never a smaller "bonus" treatment (David's "common and ordinary"
     correction, TA-778). */
  .handicap-chip { background:var(--handicap-dim); color:var(--handicap); border:1px solid color-mix(in srgb, var(--handicap) 45%, transparent); }
  .ac-pair { display:inline-flex; align-items:center; gap:6px; cursor:pointer; }
  /* Connector — SHAPE (not color) carries agree/diverge, both render in var(--mut), never --warn/--bad:
     a divergence is a feature, not an alarm (the whole reason this exists is the SMU case, where the
     divergence was the valuable signal). Reuses the dashed/solid motifs already in this file
     (.gi-rec-lean/.gi-rec-cross's dashed border, .exec-label .line's thin currentColor divider) rather
     than inventing a new visual idiom. */
  .ac-connector { display:inline-block; width:14px; height:0; border-top:1.5px solid var(--mut); opacity:.55; }
  .ac-connector.diverge { border-top-style:dashed; width:18px; } /* a literal visible gap via the dash pattern itself — reads as "open" even at a glance on a small card */
  /* TA-815 — this used to hold a single short badge word ("AGREES"/"SPLIT"), where the all-caps
     micro-label treatment read fine. It now carries a real phrase with a team name ("Opinion: Virginia
     Cavaliers — different side"), and all-caps on a phrase that long reads as shouting and is genuinely
     harder to scan than sentence case — so this drops the uppercase/letter-spacing treatment and reads
     as normal text instead, same muted color and weight as before. */
  .ac-lbl { font-size:11px; color:var(--mut); font-weight:700; }
  .ac-chevron { color:var(--mut); font-weight:700; opacity:.65; } /* small affordance (same &rsaquo; glyph "View game insights ›" already uses on this card) so a member knows this is tappable without guessing */
  .play.pass .conv { color:var(--mut) !important; }
  /* Odds vs Fair — the book's number beside the sharp fair number (BL-99 #1) */
  /* TA-1222 Phase 2 (CR-3/CR-7) — flattened from a row of colored chip boxes to one plain-text line, per
     Band 3's "plain numbers, one line, no chip row" requirement. The underlying VALUES/calculation this
     markup renders are untouched (oddsFair()'s own header comment) — only presentation changed: no
     box/border/background per number, no --accent color pop on the fair number or the edge figure (CR-7's
     ban on best-book/edge/logged-state reusing tier-ladder-adjacent accent hues for emphasis). The edge
     figure (.of-gap) stays its own distinct, always-visible number — bold in --txt, not colored — so it
     never disappears into the sentence, per Grok's "the delta must be a separate number" requirement. */
  .oddsfair { display:flex; align-items:baseline; gap:7px; flex-wrap:wrap; margin-top:9px; font-size:12px; color:var(--mut); }
  .oddsfair .of-cell { display:inline-flex; align-items:baseline; gap:4px; }
  .oddsfair .of-lbl { font-size:10px; font-weight:700; letter-spacing:.3px; text-transform:uppercase; color:var(--mut); }
  .oddsfair .of-num { font-size:13px; font-weight:700; color:var(--txt); }
  .oddsfair .of-px { font-size:12px; color:var(--mut); font-weight:600; }
  .oddsfair .of-arrow { font-size:11px; color:var(--mut); }
  .oddsfair .of-gap { font-size:12.5px; font-weight:700; color:var(--txt); white-space:nowrap; }
  .oddsfair .of-gap.pass { color:var(--mut); font-weight:600; }
  .oddsfair .of-tail { flex-basis:100%; font-size:11px; color:var(--mut); font-weight:500; }
  .home-play .of-mini { color:var(--accent); font-weight:700; font-size:12px; }
  .home-play .of-mini::before { content:'· '; color:var(--mut); font-weight:400; }
  /* day-lens: filter plays by kickoff day (Home + Game Lines line-shop) */
  .daylens { display:flex; gap:6px; flex-wrap:wrap; margin:2px 2px 10px; }
  .daylens button { font-size:12px; padding:3px 11px; border-radius:999px; border:1px solid var(--line); background:transparent; color:var(--mut); cursor:pointer; }
  .daylens button.on { background:var(--panel2); color:var(--txt); border:1px solid var(--line); box-shadow:inset 0 -2px 0 var(--accent); font-weight:700; } /* D1: neutral raised pill w/ green underline — frees green so it doesn't collide with the PRIME tier badge */
  /* SP-229, Design Lead: the results LEAGUE LENS sits a few pixels under the nav tabs, and an outline-plus-
     underline pill next to a filled tab is two selection idioms on one screen. This matches .tab.active
     exactly. Scoped to .lenspill so every other day-lens in the app keeps D1's treatment untouched.
     ⚠ Note for the Design Lead: D1's comment above says the neutral pill exists specifically to keep green
     away from the PRIME gold badge. This ruling supersedes it HERE only; if the two should agree, that is a
     call about D1, not about this page. */
  .daylens.lenspill button.on { background:rgba(63,185,80,.16); border-color:rgba(63,185,80,.6); color:var(--txt); box-shadow:none; font-weight:700; }
  /* The league pills were 22px tall — half the 44px minimum for a touch target, on the one control that
     governs every number on the page. Padding only; nothing else about them moves. */
  .daylens.lenspill button { min-height:44px; padding:0 16px; font-size:13px; }
  /* TA-341 REOPENED — Design Lead fix: shoppingModeBar (formerly bare .daylens.shoplens) was visually
     IDENTICAL to the plain day-filter pills sitting directly above it — no label, no distinct look, so the
     control read as a continuation of the muted description sentence rather than something that changes
     what's shown (David missed it on four separate looks). This ONE row now carries BOTH the shopping-mode
     toggle AND the Betting State control together — a labeled pill group, a divider, then the state picker
     — never two visually separate bolted-on widgets. `.compact` (Play of the Day) drops the text labels
     and shrinks the control size; the board's full row keeps both labels. */
  .shopmode-row { display:flex; align-items:center; gap:10px; flex-wrap:wrap; background:var(--panel2); border:1px solid var(--line); border-radius:10px; padding:9px 12px; margin:8px 2px 12px; }
  .shopmode-lbl { font-size:11px; letter-spacing:.05em; text-transform:uppercase; color:var(--mut); font-weight:700; white-space:nowrap; }
  /* TA (2026-10-11, Game Lines filter-UX polish) — a label and its control used to be SEPARATE direct
     children of .shopmode-row, so flex-wrap could (and on real boards, did) split them onto different
     lines — "Betting in" stranded at the end of one row with the actual <select> alone on the next.
     .shopmode-group keeps a label+control pair together as ONE unit, same idea as .shopmode-pills
     already applied to the 3 mode buttons.
     ⚠ flex-wrap MUST be wrap, not nowrap — caught live at a real 390px mobile width (2026-10-11): nowrap
     forced the label and the (also-wrapping) pills/select to share one unbroken row, squeezing the pills
     container down to a sliver too narrow for even one pill, so all 3 stacked vertically in a cramped
     column beside a label vertically CENTERED against that whole stack — worse than the bug this was
     fixing. With wrap, a cramped viewport instead drops the label onto its own line directly above the
     control, the same clean pattern .shopmode-row itself already uses one level up. */
  .shopmode-group { display:flex; align-items:center; gap:8px; flex-wrap:wrap; }
  .shopmode-pills { display:flex; gap:6px; flex-wrap:wrap; }
  .shopmode-pills button { font-family:inherit; font-size:13px; font-weight:600; padding:7px 14px; min-height:36px; border-radius:999px; border:1px solid var(--line); background:transparent; color:var(--mut); cursor:pointer; }
  .shopmode-pills button.on { background:rgba(63,185,80,.18); border-color:rgba(63,185,80,.65); color:var(--txt); font-weight:800; box-shadow:none; }
  .shopmode-pills button:hover:not(.on) { color:var(--txt); border-color:color-mix(in srgb, var(--line) 60%, var(--txt) 15%); }
  .shopmode-divider { width:1px; height:22px; background:var(--line); margin:0 2px; }
  /* flex:0 0 auto — without it this <select> was stretching to fill an entire wrapped row by itself
     (measured live: a 2-character state code in a full-width pill, found during the 2026-10-11 polish
     pass). It only ever needs to size to its own content, like every other control in this row. */
  .statectrl { font-family:inherit; font-size:13px; font-weight:600; padding:7px 12px; min-height:36px; border-radius:999px; border:1px solid var(--line); background:transparent; color:var(--txt); cursor:pointer; display:inline-flex; align-items:center; gap:6px; flex:0 0 auto; }
  /* The <select>'s own closed-state box inherits the dark theme fine via the rule above, but its native
     dropdown POPUP list does not automatically follow — Chromium falls back to a white system dropdown
     unless every <option> gets an explicit background/color (found live, David, 2026-09-18: the AR/AK/AZ...
     state list rendered near-illegible light-gray-on-white). */
  .statectrl option { background:var(--panel2); color:var(--txt); }
  .shopmode-row.compact { padding:7px 10px; margin:8px 0 10px; background:rgba(255,255,255,.03); }
  .shopmode-row.compact .shopmode-lbl { font-size:10.5px; }
  .shopmode-row.compact .shopmode-pills button { font-size:12px; padding:5px 11px; min-height:32px; }
  .shopmode-row.compact .statectrl { font-size:12px; padding:5px 10px; min-height:32px; }

  /* TA (2026-10-11, Game Lines filter-UX polish) — progressive disclosure for the tier/"at my books"
     filters (appendTierFilterControl). These are set-and-forget far more often than Shopping As or
     Betting In, so they're now a native <details>, default OPEN (nothing is hidden on first load — see
     objective #7's own "without hiding the primary... or making frequent tasks harder") inside the SAME
     .shopmode-row, closeable by anyone who's set it once and doesn't want to see it every time. The
     closed-state summary still names which tiers are showing (.smf-hint) so collapsing never hides
     information, only the control surface. Reuses .shopmode-lbl's exact label typography — same visual
     language as "Shopping as"/"Betting in", never a new one. */
  .shopmode-filters { flex:1 1 auto; min-width:0; }
  .shopmode-filters > summary { cursor:pointer; list-style:none; display:flex; align-items:center; gap:6px;
    font-size:11px; letter-spacing:.05em; text-transform:uppercase; color:var(--mut); font-weight:700; user-select:none; }
  .shopmode-filters > summary::-webkit-details-marker { display:none; }
  .shopmode-filters > summary::before { content:'▸'; display:inline-block; font-size:9px; color:var(--mut); transition:transform .15s ease; }
  .shopmode-filters[open] > summary::before { transform:rotate(90deg); }
  .smf-hint { text-transform:none; letter-spacing:0; font-weight:600; color:var(--txt); }
  .shopmode-filters-body { display:flex; align-items:center; gap:8px; flex-wrap:wrap; margin-top:8px; padding-top:8px; border-top:1px solid var(--line); }

  /* ═══ SP-258 — THE RESULTS PAGE ═════════════════════════════════════════════════════════════════════
     ⚠ THE PAGE PRINCIPLE THAT GOVERNS EVERY RULE BELOW: on Results, GREEN MEANS "A WIN." Nothing else on
     this page may be green. Four things wanted it — the brand accent, the Strong tier chip, the active
     control, and the winning bar. The bars are the hero, so they keep it and the other three give it up.
     That is why the active control below has a FILL but no HUE and no underline (the underline was the
     green leak), and why .ladder re-skins .conf-Strong off the shipped dim green.
     Everything here is scoped to .rpage / .ladder so no other surface in the app moves. */

  /* THE QUIET STEP — and it goes UP in size, down in contrast. Going smaller is the failure: 10px grey is
     "small print someone hopes you skip", and these lines answer one of the four questions the page exists
     to answer. 12.5px, generous leading, muted ink, measured line length. ⚠ Nothing below 12.5px carries a
     sentence on this page: the season frame, the coverage sentence, the non-reportable bar labels and the
     counting card all speak in this one voice rather than in four near-misses. */
  .rpage { --fs-quiet:12.5px; }
  .rquiet { font-size:var(--fs-quiet); line-height:1.65; color:var(--mut); max-width:62ch; }
  .rquiet b, .rfig { color:var(--txt); font-weight:700; font-variant-numeric:tabular-nums; font-feature-settings:"tnum" 1; }
  /* ⚠ 62ch IS A READING MEASURE, NOT A COMPOSITION. Left alone inside a bordered card it produced a
     418px ribbon in a 964px box at 1000px — 57% of the card empty, which reads as a layout that gave up.
     A text column on the page BACKGROUND is normal and keeps its measure; inside a card the container has
     to do something with the leftover space, so the cap comes off and the card's own width (or its
     columns, below) sets the measure instead. */
  .rpage .card .rquiet { max-width:none; }

  /* ── THE CONTROL ROW. Two DIFFERENT idioms, because they are two different questions. ──────────────
     ⚠ SIX PILLS MEASURE 569px AGAINST A 354px BUDGET AT 390px. Two pill groups is not a taste question;
     it does not fit. League is a fixed three-way choice -> a segmented track. Timeframe has a VARYING
     option count (one surviving week emits two options, not three) -> a native menu button, which
     absorbs that with zero reflow. Measured fit at 390px: 186 + 138 + 10 = 334px, 20px spare.
     ⚠ The sticky offset is COMPUTED into --nav-h (see renderApp) and never hardcoded: .tabs-wrap's own
     top:53px is already ~6px wrong at >=600px, where the header's padding grows. */
  /* ⚠ THE TWO CONTROLS MUST READ AS TWO THINGS. At desktop the space between them says so on its own; on
     a phone they sit close enough to read as one control group, which is the misreading the whole
     two-idiom decision exists to prevent. A hard minimum gap keeps them apart at every width, and the
     grounds already differ (transparent track vs filled menu button). */
  .rctl   { display:flex; align-items:center; justify-content:space-between; gap:18px;
            margin:0 -18px; padding:9px 18px; background:var(--bg);
            border-bottom:1px solid var(--line); position:sticky; top:var(--nav-h,101px); z-index:3; }
  .rseg        { display:inline-flex; background:var(--panel); border:1px solid var(--line);
                 border-radius:999px; padding:3px; gap:2px; }
  .rseg button { min-height:38px; padding:0 14px; font-size:13px; font-weight:600;
                 border-radius:999px; border:1px solid transparent;
                 background:transparent; color:var(--mut); white-space:nowrap; }
  /* ACTIVE STATE: KEEP THE FILL, DROP THE HUE. Four cues carry it — fill, border, ink, weight. No
     underline: that was the green leak, and green is spoken for by the winning bars. */
  .rseg button.on { background:var(--panel2); border-color:var(--line); color:var(--txt);
                    font-weight:700; box-shadow:0 1px 0 rgba(0,0,0,.35); }
  .rtf { position:relative; display:inline-flex; align-items:center; }
  /* ⚠ width:auto must override the global `input,select{width:100%}` — without it the menu eats the row. */
  .rtf select  { appearance:none; -webkit-appearance:none; min-height:44px; padding:0 30px 0 14px; font-size:13px;
                 font-weight:700; border-radius:10px; background:var(--panel2);
                 border:1px solid var(--line); color:var(--txt); width:auto; }
  .rtf::after { content:'⌄'; position:absolute; right:12px; top:46%; transform:translateY(-50%);
                pointer-events:none; color:var(--mut); font-size:14px; line-height:1; }
  /* ⚠ NEVER WRAP, SCROLL, OR DROP A CONTROL — SO THE BREAKPOINT HAS TO BE MEASURED, NOT ESTIMATED.
     The first cut shortened the league values below 359px on an estimate of 186px for the track. It
     renders at 204px, and the row needs seg + gap + menu = 359px against a budget of (width − 36). That
     is 324px at 360 and 339px at 375 — so the row overflowed by 22px and 7px at two of the three most
     common phone widths, and only just fitted at 390 by squashing the track. Measured, with headroom:
       ≤376px  short values + tighter padding → 278px, budget 324 at 360 · 46px spare
       377px+  full values, trimmed padding   → 341px, budget 354 at 390 · 13px spare
     The Design Lead's ruling — `College · NFL · Both` at 390 — is preserved exactly; what changed is
     that it now fits with room instead of by compression. */
  .rseg .lg-short { display:none; }
  @media (max-width:420px){ .rseg button { padding:0 11px; } }
  /* Must come AFTER the block above: same specificity, and this one wins where both apply. */
  @media (max-width:376px){
    .rseg .lg-full { display:none; }
    .rseg .lg-short { display:inline; }
    .rseg button { padding:0 10px; }
    .rtf select { padding:0 26px 0 11px; }
    .rctl { gap:14px; }
  }

  /* ── THE HERO. Three genuinely different facts. ⚠ NOT ROI beside units: at one unit per play
     `units / (W+L)` IS the units figure, so printing both was the same number twice. */
  .rhero { display:flex; gap:10px; margin:14px 0 0; }
  .rhero > div { flex:1 1 0; min-width:0; }
  .rhero .k { font-size:12px; letter-spacing:.06em; text-transform:uppercase; color:var(--mut); }
  .rhero .v { font-family:var(--font-num); font-variant-numeric:tabular-nums; font-feature-settings:"tnum" 1;
              font-size:30px; font-weight:700; line-height:1.15; margin-top:4px; }
  /* ⚠ THREE FACTS, THREE ROWS, BELOW 600px. Wrapping produced a ragged 2+1 with ~50% dead space beside a
     stranded third figure, and the captions are wildly uneven ("430-399-5" against a three-line sentence),
     so the first row also came out tall and lopsided. Stacked full-width they share one left edge and one
     rhythm. Desktop keeps the clean 3-across. */
  @media (max-width:599px){
    .rhero { display:block; }
    .rhero > div { margin-top:16px; }
    .rhero > div:first-child { margin-top:0; }
  }

  /* ── THE LADDER. One arm per cell diverging from a shared centre: length is proportional to |ROI|,
     left+red for a loss, right+green for a win. ⚠ COUNTS WOULD NOT WORK — Prime's 17 bets would be a stub
     beside Solid's 47 and the staircase would be invisible. ROI makes +25.1 -> +7.7 -> -13.2 literally a
     descending staircase. Sample size lives in text beneath each panel. */
  .lpanel { margin-top:12px; padding:16px 18px; }
  /* The panel heading names the bet type on the left, and the two figure columns on the right — it never
     said what those green and red numbers were, on the section that is the whole product. The header grid
     matches the row grid exactly, so "Return" and "Bets" sit over the figures they name. */
  .lhead { display:grid; grid-template-columns:1fr var(--rail-r); column-gap:var(--gap); align-items:baseline; margin:0 0 10px; }
  .lhead h4 { margin:0; font-size:15px; font-weight:700; }
  .lhead .lroi span { font-size:11px; letter-spacing:.05em; text-transform:uppercase; color:var(--mut);
                      font-family:inherit; font-weight:600; }
  /* ⚠ FIXED 58px BOTH SIDES so the centre line lands at exactly 50% and every panel's axis aligns with
     every other panel's. The shared axis has to hold between panels or the whole thing reads as broken. */
  /* ⚠ THE RAILS ARE UNEQUAL NOW, AND THE AXIS IS COMPUTED RATHER THAN ASSUMED. The right rail carries
     BOTH the return and the sample size, so it is wider than the tier rail — and the axis can no longer
     sit at a hardcoded 50%. What the Design Lead's ruling actually requires is that the centre line lands
     at the SAME x in all three panels, not that the rails match each other; identical rails in every
     panel still guarantees that. The position is derived from the rail widths so the two can never drift. */
  /* TA-602 — RIGHT RAIL WIDENED AGAIN, 140px -> 165px (mobile 128px -> 145px), to comfortably hold the
     now-FIXED 9ch + 5.5ch `.lroi` columns (see its own comment) plus their 8px gap with real breathing
     room either side, rather than the 140px that was a tight fit sized before those columns were fixed.
     The axis position below is computed FROM --rail-r, so widening it here is the whole fix; nothing
     else needs to move. */
  .lpanel { --rail-l:58px; --rail-r:165px; --gap:10px; }
  .lbars { position:relative; }
  .lbars::before { content:''; position:absolute; margin-left:-.5px; top:-2px; bottom:-2px; width:1px;
                   left:calc(var(--rail-l) + var(--gap) + (100% - var(--rail-l) - var(--rail-r) - var(--gap) * 2) / 2);
                   background:color-mix(in srgb,var(--txt) 32%,transparent); }
  .lrow { display:grid; grid-template-columns:var(--rail-l) 1fr var(--rail-r); column-gap:var(--gap);
          align-items:center; min-height:26px; }
  @media (max-width:376px){ .lpanel { --rail-l:50px; --rail-r:145px; } }
  .lrow .lrail { text-align:left; }
  .ltrack { position:relative; min-height:26px; display:flex; align-items:center; }
  /* Equal weight, absolutely: same height, same opacity, same radius for red and green. A loss is never
     shrunk, greyed or de-emphasised. */
  /* ⚠ A USABLE MINIMUM. At 390px the half-track is 91px, so a −4.8% arm computed to about 11px and a
     panel of small returns read as ragged stubs rather than as a comparison. The minimum keeps every bar
     legible as a bar — which side of the axis it sits on is the primary read, and that stays exactly
     true. Below roughly 2.5% the LENGTH stops being proportional; the exact figure is printed beside it
     at full weight, so nothing is hidden by the floor and nothing is exaggerated by it either. */
  .lbar { position:absolute; top:50%; transform:translateY(-50%); height:10px; border-radius:2px; min-width:7px; }
  .lbar.win  { left:50%;  background:var(--accent); }
  .lbar.loss { right:50%; background:var(--bad); }
  /* ⚠ OFF-SCALE: a cell too small to set the scale, whose return runs PAST the end of it.
     The first attempt drew it at FULL track length in a lighter wash, and the Design Lead measured what
     that actually produced: Prime +83.3% (3 bets) and Solid +39.3% (25 bets) rendered as bars of
     IDENTICAL LENGTH. A reader scanning length concluded the two were equal when one figure is more than
     double the other. Length is the primary read; a fill opacity is not a length.
     Worse, the wash broke this section's own rule three comments above — "a loss is never shrunk, greyed
     or de-emphasised" — because a muted red bar reads weaker than a full-weight one right below it.
     So: the bar STOPS SHORT of the track end, and a full-strength overflow cue sits past the gap. Length
     now says "further than this chart goes"; nothing is dimmed; red and green stay equal weight. */
  .lbar.off-scale::after { content:""; position:absolute; top:-2px; bottom:-2px; width:3px; border-radius:1px; }
  .lbar.off-scale.win::after  { right:-7px; background:var(--accent); }
  .lbar.off-scale.loss::after { left:-7px;  background:var(--bad); }
  /* Thin and empty rows keep the FULL row height and the axis tick. The label starts 9px right of the axis. */
  /* ⚠ THE LABEL RUNS INTO THE ROI COLUMN AND WRAPS RATHER THAN CLIPPING. The ROI column is COMPLETELY
     EMPTY on both non-reportable states, so the 58px rail plus its 10px gap is free space — and even
     then `No Strong game lines in NFL yet` does not fit on one line at 390px. Clipping a server-authored
     sentence to `No Strong game lin…` would be worse than either state it describes, so the ROW GROWS.
     That does not break the shared axis: the axis is drawn down the whole stack at a fixed x, and a
     taller row moves nothing sideways. It cannot collide with a bar either — a row that has a bar never
     has a label, which is why the bar can stay absolutely positioned and vertically centred. */
  .lnote { margin-left:calc(50% + 9px); margin-right:-68px; padding:5px 0;
           font-size:var(--fs-quiet); line-height:1.35; color:var(--mut); }
  .lnote b { color:var(--txt); font-weight:700; font-variant-numeric:tabular-nums; font-feature-settings:"tnum" 1; }
  /* ⚠ THE SAMPLE SIZE CARRIES EQUAL VISUAL WEIGHT TO THE RETURN — same face, same size, same weight,
     differing only in colour. This is what replaced the 10-bet floor: with no suppression, "+93%" alone
     would be a headline and "2 bets" a footnote, and the reader would take the headline. Side by side at
     one weight they read as a single fact, which is the honest shape of it. It is also why `n` left the
     panel footnote — a count three rows away from the figure it qualifies is not a qualification. */
  /* ⚠ BOTH COLUMNS ARE TRULY FIXED TRACKS NOW, NOT `1fr`/`auto`. Each `.lrow` is its OWN independent grid
     (there is no shared parent grid across the stacked rows), so `1fr` and `minmax(X,auto)` both resize
     PER ROW off that row's own content — the previous `1fr minmax(2.6ch,auto)` looked fixed for a 1- or
     2-digit bet count, where the drift was sub-pixel, but TA-602 put a full W-L-T record ("170-133-4" vs
     "27-22") in the wide column and the same latent flaw became an 8px+ rag every row — David, 2026-10-04:
     "these need to be symmetrical and spaced so they have a consistent vertical alignment." Literal `ch`
     widths are the actual fix: every row's two columns start and end at the SAME x regardless of that
     row's own content length, which is what right-aligned tabular-nums needs to read as a real ledger
     rather than ragged text. 9ch fits the longest realistic record (a full-season "274-201-4"-shaped
     figure); 5.5ch fits "100.0%" with a hair of room. The header below uses the SAME track so the labels
     sit over their columns. */
  .lroi { display:grid; grid-template-columns:9ch 5.5ch; column-gap:8px; align-items:baseline;
          font-family:var(--font-num); font-variant-numeric:tabular-nums; font-feature-settings:"tnum" 1;
          font-weight:700; font-size:16px; text-align:right; }   /* Oswald caps at 700, not 800 */
  @media (max-width:376px){ .lroi { grid-template-columns:8ch 5ch; column-gap:6px; font-size:15px; } }
  .lroi .lroi-n { color:var(--mut); }
  /* The per-panel subtotal. Quieter than a rung and separated by a rule, because it is a SUM of the three
     above it, not a fourth grade. Same figure columns so it lines up with what it totals. */
  .ltotal { display:grid; grid-template-columns:var(--rail-l) 1fr var(--rail-r); column-gap:var(--gap);
            align-items:center; border-top:1px solid var(--line); margin-top:4px; padding-top:8px; }
  .ltotal .ltot-label { font-size:11px; letter-spacing:.04em; text-transform:uppercase; color:var(--mut); }
  .ltotal .lroi { font-size:14px; }
  .ltotal .lnote { font-size:13px; color:var(--mut); }
  /* ⚠ THE TIER LADDER LIVES IN THE LEFT RAIL, NEVER ON THE BARS — bars are result-coded, the rail is
     tier-coded, one meaning per element. A luminance ladder: gold fill -> white outline -> grey outline.
     Strong is re-skinned off the shipped dim-green .conf-Strong because green is spoken for here. */
  .ladder .conf-chip { letter-spacing:.5px; padding:2px 7px; }
  .ladder .conf-Strong { background:transparent; color:var(--txt);
                         border:1px solid color-mix(in srgb,var(--txt) 40%,transparent); }
  /* TA-602 — David, 2026-10-04: "the tier button colors should all be the same, one of the prime looks
     different." The half-opacity step this used to be (the ONLY cue separating an empty cell from a thin
     one) read as a visual bug, not a signal — a reader comparing panels sees Prime gold in one and a
     washed-out Prime in another and reasonably reads that as inconsistency, not as "this one is empty".
     Emptiness is still said in words right next to it (`b.emptyLabel`/"None in range"), so the chip does
     not need to carry the same fact twice. Chips are now full-strength in every row, empty or not. */

  /* ── THE "EVERYTHING WE TRACK" RECONCILIATION — discrete labelled figures, not running prose.
     ⚠ It was six lines of 12.5px grey carrying SEVEN bolded figures packed into a sentence, in the
     second-most prominent position on the page: the densest block on it, and the one a stranger would
     point at and call our spreadsheet. It is a reconciliation. It gets the shape of one. */
  .rall { margin-top:16px; }
  .rall-figs { display:flex; flex-wrap:wrap; gap:10px 26px; margin:8px 0 9px; }
  /* ⚠ MEASURED AT 360 AND 375, NOT ONLY AT 390 — this strip was claimed as "one row" on the strength of a
     390px measurement and still wrapped 3+1 at the two widths below it, orphaning VOIDED on its own line.
     That is the same measure-one-width mistake that put the control-row breakpoint 30px out. The four
     items need ~246px of content; at a 26px gutter that is 324px, which is exactly the budget at 360, so
     it tipped over. A 16px gutter brings it to 294px — 30px of headroom at the narrowest width. */
  @media (max-width:420px){ .rall-figs { gap:10px 16px; } }
  .rall-figs > div { display:flex; flex-direction:column; gap:1px; }
  .rall-figs .l { font-size:11px; letter-spacing:.05em; text-transform:uppercase; color:var(--mut); }
  .rall-figs .f { font-family:var(--font-num); font-variant-numeric:tabular-nums; font-feature-settings:"tnum" 1;
                  font-size:17px; font-weight:700; color:var(--txt); }
  /* ── THE COUNTING CARD. An aside by GROUND, not by shrinking. */
  .rcount { margin-top:12px; background:var(--panel2); }
  .rcount .cline { margin-top:7px; }
  .rcount .cline:first-of-type { margin-top:0; }
  /* Two columns once the card is wide enough to leave a ribbon otherwise — five lines fall 3 + 2, and each
     column is ~60ch, so the reading measure is kept by the column rather than by an arbitrary cap. */
  @media (min-width:720px){
    .rcount .clines { column-count:2; column-gap:34px; }
    .rcount .cline { break-inside:avoid; margin-top:0; margin-bottom:10px; }
    /* The closing card is one sentence, so it caps its OWN width rather than splitting into columns. */
    .rclose { max-width:620px; }
  }
  /* ── THE LAST TEN. A loss renders at exactly the same weight as a win. */
  /* ⚠ THE PAGE BODY MUST NEVER SCROLL HORIZONTALLY. A pick is free text up to ~80 characters
     (`Florida State Seminoles +6.5 …`) and in a 4-column table at 390px that pushed the document to
     431px wide. It wraps instead — a table this narrow has nowhere to scroll to. */
  .rten { width:100%; border-collapse:collapse; font-size:13.5px; }
  .rten td { padding:9px 8px 9px 0; border-top:1px solid var(--line); vertical-align:top; }
  .rten tr:first-child td { border-top:0; }
  /* `width:1%` + nowrap is shrink-to-fit under auto layout: the three short columns take exactly what
     their content needs and the pick column absorbs everything left, wrapping mid-word if it has to.
     ⚠ NOT `table-layout:fixed` — that splits the width evenly regardless, which collapsed the date to
     nothing and set `Lost` one letter per line. */
  /* The date is a group header spanning the row, not a column repeated ten times down the rail. */
  .rten .rt-day td { padding:14px 0 5px; border-top:1px solid var(--line);
                     font-size:11px; letter-spacing:.06em; text-transform:uppercase; color:var(--mut); }
  .rten tr:first-child.rt-day td { padding-top:0; border-top:0; }
  .rten .rt-day + tr td { border-top:0; }
  .rten .rt-pick { overflow-wrap:anywhere; }
  .rten .rt-res  { width:1%; white-space:nowrap; }
  .rten .rt-u { width:1%; text-align:right; white-space:nowrap; font-family:var(--font-num);
                font-variant-numeric:tabular-nums; font-weight:700; }
  /* The one link on the page. A link, not a button — it goes somewhere, it does not do anything. */
  .rmeth { color:var(--txt); font-weight:700; text-decoration:underline; text-underline-offset:3px;
           text-decoration-color:color-mix(in srgb,var(--txt) 35%,transparent); }
  /* backtest / model-validation: minimized by default, one clear divider, self-serve when you want it */
  .backtest { margin-top:16px; border-top:2px dashed var(--line); padding-top:10px; }
  .backtest > summary { cursor:pointer; list-style:none; color:var(--mut); font-size:12.5px; font-weight:700; padding:6px 2px; user-select:none; }
  .backtest > summary::-webkit-details-marker { display:none; }
  .backtest > summary::before { content:'▸ '; }
  .backtest[open] > summary::before { content:'▾ '; }
  /* date-on-every-card: the kickoff day, unmissable at the point of the bet — prevents cross-week mistakes */
  .datechip { display:inline-block; font-size:11px; font-weight:800; letter-spacing:.02em; padding:2px 9px; border-radius:999px;
    background:rgba(88,166,255,.13); color:var(--blue); border:1px solid rgba(88,166,255,.5); vertical-align:middle; white-space:nowrap; }
  .datechip.nodate { background:rgba(210,153,34,.14); color:var(--warn); border-color:var(--warn); } /* no date = verify, don't assume */
  .conf-why { color:var(--txt); font-size:12.5px; line-height:1.45; min-width:0; flex:1; }
  .conf-details { margin-top:6px; }
  .conf-details summary { cursor:pointer; color:var(--mut); font-size:11.5px; list-style:none; }
  .conf-details summary::-webkit-details-marker { display:none; }
  .conf-details summary::before { content:'▸ rationale'; }
  .conf-details[open] summary::before { content:'▾ rationale'; }
  .conf-factors { margin-top:6px; display:flex; flex-direction:column; gap:5px; padding-left:2px; }
  .conf-f { font-size:12px; color:var(--mut); line-height:1.4; }
  .conf-note { font-size:10.5px; color:var(--mut); margin-top:6px; font-style:italic; }
  .noise { color:var(--warn); }
  table { width:100%; border-collapse:collapse; font-size:13.5px; }
  th, td { text-align:left; padding:8px 10px; border-bottom:1px solid var(--line); }
  th { color:var(--mut); font-weight:600; }
  /* ⚠ SP-3, RE-OPENED BY SP-229 — A WIDE TABLE SCROLLS INSIDE ITS CARD. THE BODY NEVER SCROLLS SIDEWAYS.
     Measured at 390x844 before this rule: a 482px grid table inside a 354px card with no overflow-x
     ancestor anywhere up to .wrap, so documentElement.scrollWidth was 523 against a 390 clientWidth and
     scrolling right dragged the header, the tab strip and the section title off-screen with it. A cell
     shredded to "No / pro / Co / yet" does not read as careful, it reads as broken — which defeats the one
     thing this page is for. The scroll belongs to the table, not the document. */
  .tscroll { overflow-x:auto; -webkit-overflow-scrolling:touch; }
  .tscroll::-webkit-scrollbar { height:6px; }
  .tscroll::-webkit-scrollbar-thumb { background:var(--line); border-radius:999px; }
  /* TA-1034 UX FIX #1 — the Our Opinion tier breakdown (renderOpinionTierTable(), dashboard/index.html)
     is only 3 columns, but inherited the `.tscroll > table{min-width:520px}` mobile rule below that was
     sized for OTHER tscroll tables with 4-6 columns. At 390px that forced this table to 520px inside a
     ~296px card — 43% off-screen with no visible scroll affordance on most phones — and the part that
     scrolled away was exactly the third column's own sample-floor honesty caveat ("below this tier's own
     floor (N<30)"), clipped mid-word. Fixed layout + explicit widths lets the third column WRAP instead
     of forcing the table wider; the mobile override just below drops the inherited min-width. */
  .opin-tier-tbl { table-layout:fixed; width:100%; min-width:0; }
  .opin-tier-tbl th:nth-child(1), .opin-tier-tbl td:nth-child(1) { width:28%; }
  .opin-tier-tbl th:nth-child(2), .opin-tier-tbl td:nth-child(2) { width:14%; }
  .opin-tier-tbl th:nth-child(3), .opin-tier-tbl td:nth-child(3) { width:58%; white-space:normal; word-break:break-word; }
  /* ⚠ A SCROLLER WITH NO AFFORDANCE READS AS A LAYOUT BUG. At 390px the grid is 566px inside a 308px
     window — 46% hidden, the whole Teasers column off-screen — and the reader saw "No Prime…", "-2.4%",
     "21-19 · -0" sliced mid-character at the card edge. Worse by proximity: the nav strip 300px above
     scrolls sideways and DOES have a green chevron, so the reader has just been taught "chevron = swipe"
     and then meets a table with none. This is the SAME fade the tab strip uses (SP-3), deliberately —
     reusing the learned signal rather than inventing a second one. */
  .tscroll-wrap { position:relative; }
  .tscroll-wrap::before, .tscroll-wrap::after { content:''; position:absolute; top:0; bottom:0; width:38px; pointer-events:none; z-index:2; opacity:0; transition:opacity .18s ease; display:flex; align-items:center; color:var(--accent); font-size:26px; font-weight:800; line-height:1; }
  .tscroll-wrap::before { content:'‹'; left:0;  justify-content:flex-start; padding-left:5px; background:linear-gradient(to right, var(--panel) 40%, rgba(20,27,36,0)); }
  .tscroll-wrap::after  { content:'›'; right:0; justify-content:flex-end;   padding-right:5px; background:linear-gradient(to left,  var(--panel) 40%, rgba(20,27,36,0)); }
  .tscroll-wrap.fade-l::before { opacity:1; }
  .tscroll-wrap.fade-r::after  { opacity:1; }
  /* Fixed layout + explicit widths: a one-word "Conviction" header was holding desktop width and crushing
     the data columns that carry the actual claim. Narrow label, even thirds for the three bet types. */
  .gridtbl { table-layout:fixed; }
  .gridtbl th:first-child, .gridtbl td:first-child { width:22%; }
  /* Same state must render in the same place. Empty cells were top-aligned in one row and mid-cell in the
     next, on one screen, because the rows differ in height. */
  .gridtbl th, .gridtbl td { vertical-align:top; }
  /* The return and the count are ONE line and ONE size — at these sample sizes the count is part of the
     claim, not a caveat, so nothing may shrink one without shrinking the other. */
  .gridtbl .cellhead { font-size:17px; line-height:1.3; }
  .grid { display:grid; grid-template-columns:1fr 1fr; gap:10px; }
  .chk { display:flex; align-items:center; gap:6px; }
  .empty { color:var(--mut); padding:30px; text-align:center; }
  .filters { display:flex; flex-wrap:wrap; gap:16px; align-items:center; margin:6px 0 4px; padding:10px 12px; background:var(--panel); border:1px solid var(--line); border-radius:10px; }
  .fgroup { display:flex; align-items:center; gap:6px; flex-wrap:wrap; }
  .flabel { color:var(--mut); font-size:11px; text-transform:uppercase; letter-spacing:.6px; margin-right:2px; }
  .fchip { position:relative; padding:5px 11px; border-radius:999px; font-size:13px; border:1px solid var(--line); background:var(--panel2); color:var(--mut); }
  .fchip.on { background:var(--accent); color:var(--accent-ink); border-color:var(--accent); font-weight:700; }
  /* TA-1248 — League "All" is a reset-everything control, not an itemized selection. Must not read as a
     fourth checked chip sitting among the real .tier-toggle picks. Ghost/outline, same idiom as
     .dd[aria-expanded="true"] elsewhere in this file: accent border + text, no fill. Three-class selector
     (.fchip.on.fchip-all) is deliberately more specific than the two-class .fchip.on base rule above it,
     so this wins regardless of source order — same reasoning as the .tier-toggle specificity notes already
     in this file. See docs/specs/TA-1248-filter-chip-visual-hierarchy.md (Design Lead). */
  .fchip.on.fchip-all { background:transparent; border-color:var(--accent); color:var(--accent); font-weight:700; }
  /* TA-1248 — Site/Slate is a second, unrelated filter group sharing the row with League. Scoped by
     ancestor class ONLY — must never touch the bare .fchip.on rule other pages/tabs rely on (DFS lens
     chips, tab strips, Results tier toggle, etc. — a dozen unrelated call sites per this file's own
     .fchip comments). Reuses var(--accent-ink) for the fill's text color: that token is a near-black ink
     chosen for contrast against ANY sufficiently saturated/light fill, not specifically tied to green — same
     value works here without adding a --blue-ink token. */
  .fgroup-accent-blue .fchip.on { background:var(--blue); border-color:var(--blue); color:var(--accent-ink); }
  /* TA-843-follow-up — "My Research" tab pill only (see LIST_MODE_TABS's own comment in index.html):
     echoes .opin-chip's sharp-rectangle silhouette (border-radius:0) since this tab is entirely
     Opinion-type data. Scoped to this ONE button via .fchip-rect — .fchip itself stays pill-shaped
     everywhere else, it's shared by a dozen unrelated filter bars site-wide. */
  .fchip-rect { border-radius:0; }
  /* TA-980 Fix 3 — supersedes the old unlabeled "My Research" presence dot (TA-811, 2026-10-21): a
     worded status line under each Markets tab's own label (Edge found / No edge / Research available /
     Not modeled yet — see renderGameDetail's own TA-980 comment in index.html for exactly which check
     drives each), never a bare dot with no legend. Muted by default so it never reads as a verdict by
     color alone; .has-edge (a real qualifying read, same bar the page's other tier chips already use)
     is the only state that earns an accent color.
     Validator round 1 finding (2026-10-29) — .has-edge used a flat var(--accent) unconditionally, the
     EXACT SAME token .fchip.on's own background uses (line above): whenever a tab was both active AND
     "Edge found" (the common case — Lines is typically both the default-open tab and the qualifying
     one), the text rendered in the same color as its own background and vanished (confirmed via
     computed style, both rgb(16,185,129)). Fixed the same way .fchip.on's OWN text already solves this
     exact contrast problem one line up: var(--accent) reads fine against the inactive .fchip's dark
     var(--panel2) fill, but needs var(--accent-ink) — the dedicated "text/icon ON an accent fill" token
     — once the parent tab is active and its background IS var(--accent). Two rules, not one flat color,
     so each state contrasts against its OWN real background rather than assuming one color works on both. */
  .fchip-status { display:block; font-size:9.5px; font-weight:600; color:var(--mut); margin-top:1px; line-height:1.3; }
  .fchip-status.has-edge { color:var(--accent); }
  .fchip.on .fchip-status.has-edge { color:var(--accent-ink); }
  /* TA-1222 Phase 1 Task 3 follow-up — leagueFilterGroup() (index.html) wraps each league's label in a
     bare `.conf-chip` (no `conf-${tier}` modifier — it's not a confidence tier, just reusing the chip
     shell) so it inherits that class's OWN default color/border (line ~267: muted gray text, dark
     border) instead of the parent `.fchip.on`'s accent-ink text. Same contrast bug as
     `.fchip-status.has-edge` above — a child element with its own `color`/`border` beats the parent's
     fill-aware text color — just never patched for this control. Confirmed live 2026-11-09: muted
     gray-on-green text plus a visible dark inner border read as an unreadable "pill inside a pill."
     Drop the border entirely here (unlike .fchip-status, .conf-chip's border is the visible part of the
     bug, not just the color) so a selected league chip reads as plain accent-ink label text, same as
     every other `.fchip.on` chip on the page. */
  .fchip.on .conf-chip { color:var(--accent-ink); border-color:transparent; }
  /* SP-28 DFS lens system */
  .fchip.off { opacity:.45; cursor:not-allowed; }
  .fchip .whenchip { font-size:9.5px; color:var(--warn); margin-left:5px; font-weight:600; }
  /* TA-846 — shared "Filters" dropdown shell (filtersDropdown() in index.html). Reuses .statectrl's own
     pill/border/color language (same control family, same visual weight) rather than inventing a new
     button shape — this is meant to read as "one more control in this row", not a distinct new idiom. */
  .ddwrap { position:relative; flex:0 0 auto; }
  .dd { display:inline-flex; align-items:center; gap:7px; font-family:inherit; font-size:13px; font-weight:600; padding:7px 13px; min-height:36px; border-radius:999px; border:1px solid var(--line); background:transparent; color:var(--txt); cursor:pointer; }
  .dd[aria-expanded="true"] { border-color:var(--accent); color:var(--accent); }
  .ddcount { background:var(--accent-dim); color:var(--accent); font-size:11px; font-weight:800; padding:1px 7px; border-radius:999px; }
  .ddchev { color:var(--mut); font-size:10px; line-height:1; transition:transform .15s ease; }
  .dd[aria-expanded="true"] .ddchev { transform:rotate(180deg); color:var(--accent); }
  .ddpanel { position:absolute; top:calc(100% + 8px); right:0; z-index:12; width:min(320px, calc(100vw - 32px)); background:var(--panel); border:1px solid var(--line); border-radius:12px; padding:10px; box-shadow:0 14px 34px -10px rgba(0,0,0,.55); display:flex; flex-direction:column; gap:10px; }
  .ddpanel[hidden] { display:none; }
  /* The .filters/.fgroup groups this panel wraps already carry their own background/border/padding/
     margin for standalone use — flattened here so nesting them inside the dropdown's own panel chrome
     never stacks a second visible box-within-a-box. */
  .ddpanel .filters { background:transparent; border:0; padding:0; margin:0; gap:12px; }
  /* TA-602 — the Results tab's tier-counted toggle reuses THIS filter-bar idiom (.filters/.fgroup), not
     a checkbox-plus-label — the existing tier chip itself is the toggle, same affordance as .fchip.off
     above, just scoped to .conf-chip so it never touches the dozen other places that class renders. */
  /* David, 2026-10-04: "I just want them to have their normal size look" — `line-height:0` here was a
     stray inline-flex whitespace-trimming habit that doesn't do anything useful once `display:flex` +
     `align-items:center` already handle vertical centering, but it DOES cascade into `.conf-chip`
     (which sets no line-height of its own), collapsing its text's line box to near zero and squashing
     the normally-round 999px pill into a thin distorted oval. Dropped; `.conf-chip` renders exactly as
     it does everywhere else on the page now. */
  .tier-toggle { display:inline-flex; align-items:center; gap:6px; background:none; border:0; padding:0; margin:0; cursor:pointer; }
  /* TA-1222 Design Lead fix (round 2) — a `.fchip.tier-toggle` combo (the new league multi-select
     chips, sitting in the same row as plain `.fchip` pills like "All") needs `.fchip`'s own padding/
     border restored: `.tier-toggle`'s reset (background:none, border:0, padding:0 above) wins the
     cascade over `.fchip`'s base rule at equal specificity since it's declared later in this file,
     collapsing the unchecked chip to a bare checkbox+label with no pill chrome.
     Round 1 restored background too, unconditionally — but `.fchip.on` (also two classes, declared
     EARLIER at line 956) then lost the cascade to this rule for background/border-color on a SELECTED
     chip (`fchip tier-toggle on`), stripping its accent highlight. Split the restoration: padding/
     border-width/style have no `.fchip.on` equivalent to clash with, so they're safe unconditional;
     border-color/background are scoped to `:not(.on)` so `.fchip.on`'s own rule remains the last,
     highest-specificity word for the selected state, exactly as every other `.fchip.on` control on
     this page already works. */
  .fchip.tier-toggle { padding:5px 11px; border-width:1px; border-style:solid; }
  .fchip.tier-toggle:not(.on) { border-color:var(--line); background:var(--panel2); }
  .tier-toggle[aria-checked="false"] .conf-chip { opacity:.55; }
  .tier-toggle:focus-visible { outline:2px solid var(--accent); outline-offset:3px; border-radius:4px; }
  /* TA-602 — David, 2026-10-04: "put a little checkbox... I think is easier to view." A real drawn
     checkbox (border-trick checkmark, no font-glyph dependency that could render inconsistently) rather
     than relying on the chip's own colour difference to carry "is this selected" — the chip alone read as
     a plain label, not a control. */
  .tt-box { width:15px; height:15px; border-radius:4px; border:1.5px solid var(--line); background:var(--bg); flex:none; position:relative; box-sizing:border-box; }
  .tier-toggle[aria-checked="true"] .tt-box { background:var(--accent); border-color:var(--accent); }
  .tier-toggle[aria-checked="true"] .tt-box::after { content:''; position:absolute; left:4px; top:1px; width:4px; height:8px; border:solid var(--accent-ink); border-width:0 2px 2px 0; transform:rotate(45deg); }
  .lensdesc { color:var(--mut); font-size:12.5px; margin:10px 2px 2px; line-height:1.5; }
  .lensdesc b { color:var(--txt); }
  .prov { font-size:9.5px; font-weight:800; text-transform:uppercase; letter-spacing:.3px; padding:1px 6px; border-radius:5px; margin-left:7px; background:var(--accent-dim); color:var(--accent); border:1px solid color-mix(in srgb,var(--accent) 35%,transparent); white-space:nowrap; }
  tr.lens-changed td { background:color-mix(in srgb,var(--accent) 7%,transparent); }
  .drop { color:var(--mut); text-decoration:line-through; }
  .chg-arrow { color:var(--accent); font-weight:700; margin:0 5px; }
  .lensdelta { margin-top:11px; padding:10px 12px; border-radius:10px; background:var(--accent-dim); border:1px solid color-mix(in srgb,var(--accent) 30%,transparent); font-size:12.5px; line-height:1.5; }
  .lensdelta b { color:var(--txt); }
  /* TA-894 — DFS lineup card stack, replacing the dense 8-column table. One card per roster slot so the
     `why` narrative (methodology) reads as primary content, not crammed into one cell. */
  .dfs-lineup { display:flex; flex-direction:column; gap:8px; margin-top:10px; }
  .dfs-slot { background:var(--panel2); border:1px solid var(--line); border-radius:10px; padding:10px 12px; }
  .dfs-slot.lens-changed { background:color-mix(in srgb,var(--accent) 7%,transparent); border-color:color-mix(in srgb,var(--accent) 30%,transparent); }
  .dfs-slot.empty { color:var(--mut); padding:8px 12px; display:flex; gap:8px; align-items:center; }
  .dfs-slot-head { display:flex; align-items:baseline; gap:8px; flex-wrap:wrap; }
  .dfs-slot-tag { font-size:10.5px; flex:0 0 auto; }
  .dfs-slot-name { font-weight:700; font-size:14.5px; color:var(--txt); flex:1 1 auto; min-width:0; }
  .dfs-slot-sal { font-family:var(--font-num); font-weight:700; font-size:13.5px; color:var(--txt); white-space:nowrap; margin-left:auto; }
  .dfs-slot-inj { color:var(--warn); font-size:12px; font-weight:600; margin-top:4px; display:flex; align-items:center; gap:4px; }
  .dfs-slot-why { color:var(--txt); font-size:13.5px; line-height:1.55; margin-top:7px; }
  .dfs-slot-meta { display:flex; gap:12px; flex-wrap:wrap; margin-top:7px; padding-top:7px; border-top:1px solid var(--line); color:var(--mut); font-size:11.5px; }
  @media (max-width:480px){ .dfs-slot-name { font-size:13.5px; } .dfs-slot-sal { margin-left:0; flex-basis:100%; order:3; } }
  /* TA-516 SLICE 5 — Best Angles / By Game recommendation card. Mobile-first stack, hero-first hierarchy:
     player+market (quiet), HIGHER/LOWER+line (the loudest thing on the card), then operator/game/STRONG/
     market-implied-% as one small secondary line. Deliberately its OWN component, not a `.play` variant —
     `.play` is shared by several unrelated boards on this page and this card's hierarchy is specific to
     "what does The Angle like, which way, at what number" in a way those other boards don't need. */
  .pk-rec { background:var(--panel); border:1px solid var(--line); border-radius:10px; padding:12px 14px; margin:10px 0; }
  /* TA-701 — By Game now shows every captured prop, not just recommended ones; .pk-recommended's accent
     left-border + .pk-rec-tag give the one visual cue that distinguishes "The Angle recommends this" from
     "ordinary evaluated prop" without repeating the full Best Angles card treatment. */
  .pk-rec.pk-recommended { border-left:3px solid var(--accent); }
  .pk-rec-tag { display:inline-flex; align-items:center; gap:3px; font-size:9.5px; font-weight:800; letter-spacing:.3px; padding:1px 6px; border-radius:5px; background:var(--accent); color:var(--accent-ink); white-space:nowrap; }
  .pk-rec-tag svg { width:9px; height:9px; }
  /* TA-704 (TA-516 Phase 2) — the real, tappable Higher/Lower selection control, replacing the old
     decorative circle icon. Deliberately plain outline buttons (not the accent-filled Recommended
     treatment) so a member's OWN selection reads as distinct from The Angle's own recommendation signal
     everywhere else on the card — selecting a prop is never visually confused with Angle endorsing it. */
  .pk-pick-row { display:flex; gap:8px; }
  .pk-pick-btn { font-size:12.5px; font-weight:700; padding:7px 14px; border-radius:8px; border:1px solid var(--line); background:transparent; color:var(--txt); cursor:pointer; min-height:36px; }
  .pk-pick-btn.on { background:var(--accent); color:var(--accent-ink); border-color:var(--accent); }
  .pk-rec.pk-selected { box-shadow:0 0 0 1px var(--accent) inset; }
  /* TA-704 — the entry tray, fixed so it stays reachable while scrolling a long By Game list. Sits ABOVE
     the Ask The Angle pill (not beside it) -- see `body:has(.pk-entry-tray) .sharp-btn` below -- so the
     two controls are vertically stacked, never overlapping, on any viewport width. */
  .pk-entry-tray { position:fixed; left:12px; right:12px; bottom:max(12px, env(safe-area-inset-bottom)); z-index:19; background:var(--panel); border:1px solid var(--accent); border-radius:12px; padding:10px 12px; box-shadow:0 -4px 20px rgba(0,0,0,.4); max-width:460px; margin:0 auto; max-height:45vh; overflow-y:auto; }
  .pk-entry-tray-head { display:flex; justify-content:space-between; align-items:center; font-size:12.5px; font-weight:700; color:var(--txt); margin-bottom:6px; }
  .pk-entry-tray-head button { background:none; border:none; color:var(--mut); font-size:12px; cursor:pointer; text-decoration:underline; padding:4px; }
  .pk-entry-tray-legs { display:flex; flex-direction:column; gap:4px; }
  .pk-entry-tray-leg { display:flex; justify-content:space-between; align-items:center; gap:8px; font-size:12.5px; padding:5px 2px; border-bottom:1px solid var(--line); }
  .pk-entry-tray-leg:last-child { border-bottom:none; }
  .pk-entry-tray-leg .pk-market { font-weight:500; color:var(--mut); margin-left:3px; }
  .pk-entry-tray-dir { color:var(--accent); margin-left:4px; }
  .pk-entry-tray-leg button { background:none; border:none; color:var(--mut); cursor:pointer; padding:4px; display:flex; }
  .pk-entry-tray-leg button svg { width:14px; height:14px; }
  .pk-entry-tray-warn { font-size:11.5px; color:var(--warn,var(--mut)); margin-top:6px; }
  .pk-entry-tray-hint { font-size:11.5px; color:var(--mut); margin-top:6px; }
  .pk-entry-analyze { width:100%; margin-top:8px; padding:10px; border-radius:8px; font-weight:700; font-size:13px; }
  .pk-entry-analyze:disabled { opacity:.5; cursor:not-allowed; }
  /* TA-704 — shift the Ask The Angle pill up above the entry tray rather than letting either cover the
     other. :has() is already used elsewhere on this page (body:has(.logbet) below) for the same reason:
     pure CSS, no manual class bookkeeping, automatically correct the instant the tray appears/disappears. */
  body:has(.pk-entry-tray) .sharp-btn { bottom:calc(max(12px, env(safe-area-inset-bottom)) + 160px); }
  .pk-rec .pk-head { display:flex; justify-content:space-between; align-items:baseline; gap:8px; }
  .pk-rec .pk-player { font-weight:700; font-size:14px; color:var(--txt); }
  .pk-rec .pk-market { font-weight:500; color:var(--mut); font-size:13px; margin-left:4px; }
  .pk-rec .pk-op { font-size:12px; font-weight:700; color:var(--mut); white-space:nowrap; }
  /* the hero: direction + line. Never color-only — an icon (shape) and the word HIGHER/LOWER (text) both
     carry the meaning, so it reads the same to a colorblind user or in a quick black-and-white screenshot. */
  .pk-rec .pk-hero { display:flex; align-items:center; gap:7px; margin:7px 0 6px; }
  .pk-rec .pk-hero svg { width:20px; height:20px; flex:0 0 auto; color:var(--accent); }
  .pk-rec .pk-dir { font-size:22px; font-weight:800; letter-spacing:-.01em; color:var(--txt); line-height:1.1; }
  .pk-rec .pk-dir b { color:var(--accent); } /* the line itself pops a shade brighter within the hero */
  /* TA-702 #3 — the band-strength tag folded directly into the hero line (e.g. "Lower 249.5 Lean Lower"),
     replacing the old second pill that repeated the direction underneath the first one. */
  .pk-dir .pk-band-tag { font-size:13px; font-weight:700; letter-spacing:.2px; margin-left:4px; vertical-align:middle; }
  /* TA-933 — STRONG vs LEAN needed to be tellable apart without reading the text label, now that By Game
     is the primary landing view (not just a secondary/exploratory tab). Same accent hue at two opacities
     was too subtle for that job; LEAN now carries a genuinely distinct, quieter --mut treatment instead
     of a dimmed copy of STRONG's color. Design Lead passed these values at the gate. */
  .pk-dir .pk-band-tag.pk-band-strong { color:var(--accent); font-weight:800; }
  .pk-dir .pk-band-tag.pk-band-lean { color:var(--mut); font-weight:700; }
  /* A neutral card (No Clear Edge / Not Evaluated) communicates "nothing to act on here" — it must never
     borrow the same bright accent treatment a genuine directional call earns, on the icon or the hero
     text, so a member scanning a long By Game list can tell real calls apart from the rest at a glance. */
  .pk-rec.pk-neutral .pk-hero svg { color:var(--mut); }
  .pk-rec.pk-neutral .pk-dir { font-size:15px; font-weight:600; color:var(--mut); letter-spacing:normal; }
  .pk-rec .pk-offers { display:flex; flex-direction:column; gap:4px; margin:7px 0 6px; padding:8px 10px; background:var(--panel2); border-radius:8px; }
  .pk-rec .pk-offer-row { display:flex; justify-content:space-between; align-items:baseline; font-size:13.5px; }
  .pk-rec .pk-offer-row .pk-op-name { color:var(--mut); font-weight:600; }
  .pk-rec .pk-offer-row .pk-op-line { font-weight:800; color:var(--txt); }
  .pk-rec .pk-sub { display:flex; flex-wrap:wrap; align-items:center; gap:5px; font-size:11.5px; color:var(--mut); }
  .pk-rec .pk-sub .pk-strong-sm { font-size:9.5px; font-weight:800; letter-spacing:.3px; padding:1px 6px; border-radius:5px; background:var(--accent-dim); color:var(--accent); border:1px solid color-mix(in srgb,var(--accent) 35%,transparent); }
  .pk-rec .pk-sub .pk-dot { opacity:.6; }
  /* TA-936 — "Why" toggle, Analysis stage only (David's decision, 2026-10-27: the directional Opinion
     badge/side/confidence is NOT surfaced to members yet — the historical backtest showed it isn't
     distinguishable from a coin flip. This renders ONLY real usage/role/injury facts, never a lean word,
     never "Clear"/"Slight"). Same <details>/dashed-divider convention as .backtest above — deliberately
     NOT styled like .pk-band-tag/.pk-rec-tag, so it can never look like a second recommendation. */
  .pk-why { margin-top:8px; border-top:1px dashed var(--line); padding-top:6px; }
  .pk-why > summary { cursor:pointer; list-style:none; color:var(--mut); font-size:11.5px; font-weight:700; padding:2px 0; user-select:none; }
  .pk-why > summary::-webkit-details-marker { display:none; }
  .pk-why > summary::before { content:'▸ '; }
  .pk-why[open] > summary::before { content:'▾ '; }
  .pk-why-analysis { margin-top:6px; font-size:12px; color:var(--mut); line-height:1.5; }
  .pk-why-analysis > div { margin-bottom:3px; }
  .pk-why-gap { font-style:italic; opacity:.85; }
  /* Design Lead finding, 2026-10-27 — quiet orienting line, deliberately NO --accent (that's the
     Recommendation badge's own color) and NO icon, so it never looks like a second recommendation.
     UX Reviewer follow-up, same day: as first shipped this blended into the plain analysis facts below
     it (same muted gray, even dimmer) -- in the exact scenario it exists for (a Recommended/Strong card
     paired with a contradicting trend) a skimming member could miss it entirely. Full text opacity (not
     dimmed), semibold, plus a thin neutral left-accent (var(--line), the same divider gray this
     dashboard already uses for a non-recommendation section break -- see .backtest above) so it reads
     as the one orienting line in the panel, not one more fact in the list, without borrowing the
     Recommendation's own green. */
  .pk-why-disclosure { opacity:1; font-weight:600; color:var(--txt); border-left:2px solid var(--line); padding-left:7px; margin-bottom:5px; }
  @media (min-width:640px){
    /* desktop scales the SAME stack — player/op share a row, hero stays the biggest thing on the card,
       it just stops needing to wrap onto its own visual "section" the way a 390px card does. */
    .pk-rec { padding:14px 18px; }
    .pk-rec .pk-dir { font-size:24px; }
  }
  /* TA-933 — Best Entry is now a FEATURED card (promoted above the search field/view toggle when a
     legitimate entry exists — see dashboard/index.html), not secondary. Solid accent border + a subtle
     accent tint on the head replace the old dashed-border/smaller-header "secondary" treatment (TA-516
     Slice 7). Each leg stays one compact row rather than its own hero card — still a condensed summary,
     just no longer visually demoted. One .pk-entry-card per operator with a built entry; multiple cards
     stack, never collapse into a tab-only view, so both operators' entries stay simultaneously scannable
     while packing. Design Lead passed this treatment at the gate. */
  .pk-entry-card { background:var(--panel); border:1.5px solid var(--accent); border-radius:10px; padding:11px 13px; margin:10px 0; }
  .pk-entry-card .pk-entry-head { display:flex; justify-content:space-between; align-items:baseline; gap:8px; margin-bottom:7px; padding:6px 8px; margin:-4px -4px 7px; border-radius:7px; background:var(--accent-dim); }
  .pk-entry-card .pk-entry-title { font-weight:700; font-size:13px; color:var(--txt); }
  .pk-entry-card .pk-entry-title .pk-entry-size { color:var(--accent); }
  .pk-entry-card .pk-entry-op { font-size:11.5px; font-weight:700; color:var(--mut); white-space:nowrap; }
  /* TA-1104 — size chips, shown only when 2+ sizes are ALSO legal right now (buildEntryLadder, TA-1101).
     Same pill language as .daylens's view toggle, scaled down to sit inline under the card head rather
     than as its own full-width row. Tapping a size swaps which tier's own legs/freshness this ONE card
     shows — it never builds a new combination client-side, same "render the server's own output
     verbatim" discipline the rest of this card already follows. */
  /* UX review (2026-11-02) — PASS WITH FIXES: original chip padding (2px 9px) rendered well under the
     ~40-44px mobile touch-target guideline, five chips packed tight at gap:5px, on a flow David himself
     flagged from a real bad experience (a mis-tap here just shows the wrong size, low stakes, but still
     worth the fix). Bumped padding + gap; row stays compact, each chip is comfortably tappable. */
  .pk-entry-card .pk-entry-sizes { display:flex; align-items:center; gap:8px; margin-bottom:7px; flex-wrap:wrap; }
  .pk-entry-card .pk-entry-sizes-label { font-size:10.5px; color:var(--mut); margin-right:2px; }
  .pk-entry-size-chip { font-size:11px; font-weight:700; padding:6px 11px; border-radius:999px; border:1px solid var(--line); background:transparent; color:var(--mut); cursor:pointer; }
  .pk-entry-size-chip.on { background:var(--accent-dim); color:var(--accent); border-color:var(--accent); }
  .pk-entry-card .pk-entry-legs { display:flex; flex-direction:column; gap:1px; border-radius:8px; overflow:hidden; }
  .pk-entry-leg { padding:6px 8px; background:var(--panel2); font-size:12.5px; }
  .pk-entry-leg .pk-entry-leg-top { display:flex; align-items:baseline; justify-content:space-between; gap:8px; }
  .pk-entry-leg .pk-entry-leg-who { color:var(--txt); font-weight:600; overflow:hidden; text-overflow:ellipsis; white-space:nowrap; min-width:0; }
  .pk-entry-leg .pk-entry-leg-who .pk-market { font-weight:500; color:var(--mut); margin-left:4px; }
  .pk-entry-leg .pk-entry-leg-game { color:var(--mut); font-size:11px; margin-top:2px; }
  .pk-entry-leg .pk-entry-leg-call { display:flex; align-items:center; gap:4px; font-weight:800; white-space:nowrap; flex:0 0 auto; color:var(--txt); }
  .pk-entry-leg .pk-entry-leg-call svg { width:13px; height:13px; color:var(--accent); }
  .pk-entry-leg .pk-entry-leg-call b { color:var(--accent); }
  .pk-entry-card .pk-entry-sub, .pk-entry-card .pk-entry-rarity { font-size:10.5px; color:var(--mut); line-height:1.4; }
  .pk-entry-card .pk-entry-sub { margin-top:7px; }
  /* TA-933 UX FIX — one-line disclosure that the featured card is occasional, not a permanent fixture,
     so a member who sees it today doesn't read a later absence as "broken." */
  .pk-entry-card .pk-entry-rarity { margin-top:2px; }
  .pk-entry-none { margin:8px 0; font-size:12px; color:var(--mut); padding:0 2px; }
  /* TA-931 — render-time freshness disclosure (never a silent re-equate with "right now"). A locked
     leg is flagged in place, never removed; the card itself gets a warn-colored border only when the
     WHOLE entry is expired (one or more legs locked) — a merely-stale-but-not-expired entry keeps the
     normal dashed border and just shows the muted age line below. */
  .pk-entry-card-expired { border-color:var(--bad); }
  .pk-entry-leg-locked { opacity:0.72; }
  .pk-entry-offboard-tag { color:var(--bad); font-weight:700; }
  .pk-entry-offboard-tag svg { width:11px; height:11px; vertical-align:-1px; }
  .pk-entry-expired { margin-top:7px; font-size:11.5px; font-weight:700; color:var(--bad); line-height:1.4; }
  .pk-entry-expired svg { width:13px; height:13px; vertical-align:-2px; }
  .pk-entry-stale { margin-top:7px; font-size:11px; color:var(--warn); line-height:1.4; }
  .pk-entry-age { margin-top:7px; font-size:10.5px; line-height:1.4; }
  @media (min-width:640px){
    .pk-entry-card { padding:13px 16px; }
    .pk-entry-leg { font-size:13px; }
  }
  /* TA-702 #4 — bottom/right now respect the iOS safe area (the home-indicator strip sits inside
     env(safe-area-inset-bottom) on a notched iPhone; without this the pill was already partway into it)
     and the pill shrinks to icon-only under 480px, confirmed on a real iPhone to overlap the lower prop
     cards on Pick'em's By Game list at full size. Shrinking is the general fix (the button is page-level
     chrome, not scoped to one tab); the pickem card list below ALSO gets its own bottom clearance — see
     `.pk-rec:last-child` margin — since a long list still deserves a guaranteed gap regardless of exactly
     how big the pill renders on any given device. */
  .sharp-btn { position:fixed; bottom:max(20px, calc(env(safe-area-inset-bottom) + 12px)); right:max(20px, calc(env(safe-area-inset-right) + 12px)); z-index:20; color:var(--accent-ink); border:none; padding:12px 18px; border-radius:999px; font-weight:800; cursor:pointer;
    background:linear-gradient(100deg,var(--accent) 0%,var(--accent-bright) 26%,#a7f3c4 50%,var(--accent-bright) 74%,var(--accent) 100%); background-size:230% 100%;
    animation:sharpWave 4.6s linear infinite, sharpBreathe 3.4s ease-in-out infinite; }
  @media (max-width:480px){
    .sharp-btn { padding:12px; }
    .sharp-btn .sharp-name { display:none; } /* icon-only below 480px — same tap target, smaller footprint */
  }
  /* a light band flows across the bubble + a soft glow breathes — a subtle beacon, alive but not loud */
  @keyframes sharpWave { 0%{ background-position:200% 0; } 100%{ background-position:0% 0; } }
  @keyframes sharpBreathe { 0%,100%{ box-shadow:0 4px 16px rgba(0,0,0,.45), 0 0 0 0 color-mix(in srgb, var(--accent-bright) 0%, transparent); } 50%{ box-shadow:0 5px 20px rgba(0,0,0,.45), 0 0 20px 2px var(--accent-glow); } }
  @media (prefers-reduced-motion: reduce){ .sharp-btn { animation:none; } }
  /* "Sharp" carries the logo persona — off-white wordmark color + tracking, "Ask the" stays black */
  .sharp-btn .sharp-name { color:var(--txt); letter-spacing:.3px; }
  /* SP-264 / SP-260 — THE FAILURE MESSAGE WAS PAINTED OVER BY THIS BUTTON.
     Measured on the live page at 555px: the .betmsg error rendered at x35 y733 (338px wide) while the
     fixed pill occupies x354-518, y706-750 — 18px of horizontal and 16px of vertical overlap, so the
     tail of the sentence was covered. At a real 390px phone it wraps into the same band and worsens.
     A member who cannot save and cannot read WHY is worse off than before the guard existed.
     While a bet form is open the pill has nothing to do — you are filling in a form, not asking a
     question — so it stands down. Same condition _hasOpenBetForm() already uses to protect an open
     form from the 40s live-score re-render.
     :has() is the whole mechanism; where it is unsupported this rule simply does not apply and we are
     no worse off than today. The general case (the pill covering other content everywhere) is SP-260. */
  /* ⚠ !important IS LOAD-BEARING. The pill ships with an inline style="display:none" and is switched
     to display:block inline at sign-in, and an inline style beats a non-!important rule — so the first
     version of this shipped and did NOTHING. Verified inert before this word was added. */
  body:has(.logbet) .sharp-btn, body:has(.betform) .sharp-btn { display:none !important; }

  /* TA-725 refinement, round 4 — the fixed .sharp-btn pill overlapping Game Detail's Market Angle
     rationale text mid-scroll (not just at page-end, which the TA-702 spacer above already covers).
     Measured live: a 1331px window puts .wrap's right edge at x1158 while .sharp-btn's left edge sits
     at x1126 — a real desktop window size (unmaximized laptop), not a narrow edge case. 600-1399px is
     the band where this physically collides (below 600px the mobile layout + a smaller icon-only pill
     below 480px change the geometry; above 1400px .wrap's 1000px max-width naturally clears the pill).
     TA-260 generalization (2026-10-15): the same mechanism bites on every page, not just Game Detail —
     confirmed live via a standalone headless-Chrome measurement pass (tools/ta260-pill-overlap-check.mjs)
     against production at 390/768/1024/1399/1920px: real overlaps found at 768px (Game Lines' "BET →"
     CTA) and 1024px (Game Lines' "BET →" CTA, Prop Bets' "I placed this bet" button), none at 390, 1399,
     or 1920. That's exactly the predicted 600-1399 band — .wrap's own auto side-margins are what clear
     the pill above ~1036px, same as they do for Game Detail. Moved the rule from the Game Detail-only
     `.gd-board` selector to `.wrap` itself so every tab gets the same safe zone — `.gd-board` sits inside
     `.wrap`, so this fully supersedes (not stacks with) the old scoped rule; no page's card width changes
     beyond this single shared container getting the same right-side breathing room Game Detail already
     had.
     TA-1020 — UX Reviewer failed the first TA-1020 attempt below (a `.signal .basis-note` padding-right
     that didn't come close to the pill's real ~170px width) and in tracking down why, found this band's
     own lower bound was wrong, not just under-padded. `.sharp-btn` only drops to icon-only AT max-width:480px
     (see its own rule above) — so from 481px up through 599px the pill is the SAME full ~170px text pill
     this very rule exists to clear, yet this media query didn't start reserving space until 600px. That
     481-599px gap is exactly where UX measured a basis-note's text running ~150-160px past the pill's
     left edge (confirmed live via a headless-Chrome pass at 479/480/540/599/600px against the preview:
     real overlap at 479-599, none at 600+ once this rule's own reservation takes over). Narrowing the
     band's start to match `.sharp-btn`'s real breakpoint — rather than inventing a second, much larger
     magic padding-right number on `.signal .basis-note` just to cover this one orphaned 118px-wide gap —
     reuses the exact mechanism already proven at 600-1399px instead of tuning a new one. */
  @media (min-width:481px) and (max-width:1399px){ .wrap { padding-right:240px; } }

  /* TA-1150 fix-2 — close the 790-989px column-count regression introduced by the All-Games
     grid's auto-fit/minmax(360px) switch (see docs/specs/design/TA-1150-GAMES-GRID-AUTOFIT.md
     §6). In that band, today's production rule (auto-fill,minmax(260px,1fr)) renders 2 columns
     but the new 360px floor only reaches 1 — this rule forces 2 equal columns back in that exact
     band only, scoped to .game-card-grid--all so My Research/Best Angles (plain .game-card-grid,
     minmax(280px,1fr)) are untouched. !important is required: the base rule is an inline style
     attribute, which outranks any non-!important stylesheet rule regardless of media-query
     specificity (verified empirically — see spec §6b). */
  @media (min-width:790px) and (max-width:989px){
    .game-card-grid--all { grid-template-columns:repeat(2,1fr) !important; }
  }

  /* TA-1020 — the fixed .sharp-btn pill still visually collides with Our Opinion's basis-note
     reasoning text (TA-982's new signal block). The .wrap padding-right rule above (TA-260, now widened
     to start at 481px — see its own TA-1020 note) reserves space at the PAGE level for every width where
     `.sharp-btn` shows its full ~170px text pill (481-1399px), so a signal block's own basis-note text
     never runs out to the card's right edge in that range any more. Below 480px the icon-only pill drops
     to ~38px — small enough that this component-level padding alone clears it (confirmed live: at 390px
     the note's own background box sits ~20px under the pill's footprint, but its TEXT already stops
     ~23px clear of the pill's left edge, so nothing readable is ever covered). Kept as a second,
     component-level layer on top of the page-level fix (not a replacement for it) in case a future
     basis-note is ever rendered somewhere the pill's safe zone doesn't reach — same "belt and suspenders"
     precedent as the Pick'em entry tray (`body:has(.pk-entry-tray) .sharp-btn` above) already set. */
  .signal .basis-note { padding-right:52px; box-sizing:border-box; }
  @media (max-width:479px){ .signal .basis-note { padding-right:44px; } }

  .sharp-drawer { position:fixed; top:0; bottom:0; right:0; width:min(440px,100%); background:var(--panel); border-left:1px solid var(--line); z-index:30; display:flex; flex-direction:column; transform:translateX(105%); transition:transform .2s ease; }
  .sharp-drawer.open { transform:none; }
  .sharp-head { padding:14px 16px; border-bottom:1px solid var(--line); display:flex; justify-content:space-between; align-items:center; }
  .sharp-msgs { flex:1; overflow-y:auto; padding:14px; display:flex; flex-direction:column; gap:10px; }
  .sharp-msg { padding:10px 12px; border-radius:10px; font-size:14px; line-height:1.55; white-space:pre-wrap; }
  .sharp-msg.user { background:var(--panel2); align-self:flex-end; max-width:88%; }
  .sharp-msg.sharp { background:var(--bg); border:1px solid var(--line); align-self:flex-start; max-width:96%; }
  .sharp-msg.hint { color:var(--mut); align-self:center; text-align:center; font-size:13px; }
  /* SP-294 — a Sharp reply is rendered markdown, so its bubble lays out as HTML (pre-wrap would double
     every gap now that paragraphs are real elements). Scoped to .sharp-msg.md so nothing else moves. */
  .sharp-msg.md { white-space:normal; }
  .sharp-msg.md .stext { display:inline-block; max-width:100%; vertical-align:bottom; }
  .sharp-msg.md > :first-child, .sharp-msg.md .stext > :first-child { margin-top:0; }
  .sharp-msg.md > :last-child, .sharp-msg.md .stext > :last-child { margin-bottom:0; }
  .sharp-msg.md .md-p { margin:0 0 8px; }
  .sharp-msg.md .md-h { font-weight:700; margin:12px 0 5px; line-height:1.3; }
  .sharp-msg.md .md-h1 { font-size:15.5px; }
  .sharp-msg.md .md-h2 { font-size:14.5px; }
  .sharp-msg.md .md-h3 { font-size:13.5px; color:var(--mut); }
  .sharp-msg.md .md-l { margin:0 0 8px; padding-left:20px; }
  .sharp-msg.md .md-l li { margin:2px 0; }
  .sharp-msg.md code { background:var(--panel2); border-radius:4px; padding:1px 5px; font-size:12.5px; }
  .sharp-msg.md .md-pre { background:var(--panel2); border:1px solid var(--line); border-radius:8px; padding:9px 11px; margin:0 0 8px; overflow-x:auto; }
  .sharp-msg.md .md-pre code { background:none; padding:0; }
  .sharp-msg.md .md-q { margin:0 0 8px; padding:2px 0 2px 10px; border-left:3px solid var(--line); color:var(--mut); }
  .sharp-msg.md .md-hr { border:0; border-top:1px solid var(--line); margin:10px 0; }
  .sharp-msg.md .md-tw { overflow-x:auto; margin:0 0 8px; }   /* a wide table scrolls inside the bubble — the drawer never widens */
  .sharp-msg.md .md-t { border-collapse:collapse; font-size:13px; }
  /* ⚠ CELLS WRAP, AND THE CAP IS WHAT MAKES THAT WORK. (SP-294 UX pass, 2026-09-16.)
     These were `white-space:nowrap`, which is right for a table of short numbers and catastrophic for
     one with a sentence in it. Measured on the live drawer: a "Why" column of one-line explanations
     rendered 1495px wide, taking the table to 1883px inside a 355px bubble — 81% of it hidden behind a
     thin horizontal scrollbar, including the entire column carrying the reasoning.
     `max-width` is the load-bearing part: without a cap, `white-space:normal` alone still lets one
     prose column take almost all the width under auto layout. With it, long cells wrap at a readable
     measure, short ones stay short, and a genuinely wide table still overflows into the scroll the
     .md-tw wrapper provides. `anywhere` is for the unbroken tokens this content is full of — long
     book names and +19.5 (-110) style prices. */
  .sharp-msg.md .md-t th, .sharp-msg.md .md-t td { border:1px solid var(--line); padding:4px 8px; text-align:left; white-space:normal; overflow-wrap:anywhere; max-width:28ch; }
  .sharp-msg.md .md-t th { background:var(--panel2); font-weight:600; }
  .sharp-msg.md a { color:var(--accent); }
  .sharp-chips { display:flex; flex-wrap:wrap; gap:7px; align-self:flex-start; max-width:96%; margin-top:-2px; }
  .sharp-chip { font-size:12.5px; padding:7px 12px; border:1px solid var(--accent); border-radius:999px; background:var(--accent-dim); color:var(--accent); cursor:pointer; font-weight:600; }
  .sharp-chip:hover { background:color-mix(in srgb,var(--accent) 22%,transparent); }
  /* SP-328 follow-up: David's own feedback — the first-open voice question read as just another chat
     bubble ("I had to look a few times before I saw it"). A plain .sharp-msg looks identical to every
     other line in the thread by design; this needs to interrupt the scan instead of joining it, so it
     gets its own bordered, accent-tinted card, closer to a small in-thread pop-up than a message. Kept
     inline (not a real modal) so it still reads top-to-bottom with the greeting above it and never
     blocks the rest of the chat. Same border/radius/gradient-wash treatment as the Home screen's .dcard
     (Survivor deadline rail) — the existing "this needs your attention" component on this product —
     rather than a bespoke glow. Design Lead review, 2026-09-18: the brand book calls restraint the
     point ("do not turn the interface into a sea of green gradients"); reusing .dcard's own flat
     gradient wash instead of an added box-shadow keeps this reading as the same system, not two
     competing "pay attention" treatments. */
  .sharp-voice-ask { display:flex; gap:11px; align-items:flex-start; align-self:stretch; max-width:96%; margin:2px 0 4px;
    background:linear-gradient(180deg,var(--accent-dim),transparent); border:1px solid var(--accent); border-radius:12px; padding:13px 15px;
    transition:background .3s ease, border-color .3s ease, padding .3s ease; }
  .sharp-voice-ask .sva-ic { color:var(--accent); flex:0 0 auto; margin-top:1px; transition:color .3s ease; }
  .sharp-voice-ask .sva-t { font-weight:700; font-size:15px; margin-bottom:10px; transition:font-weight .3s ease, font-size .3s ease, color .3s ease, margin .3s ease; }
  .sharp-voice-ask .sva-btns { display:flex; gap:8px; flex-wrap:wrap; }
  .sharp-voice-ask button { border-radius:999px; font-size:13.5px; padding:7px 14px; }
  /* UX review, 2026-09-18: once answered, this has done its job — full accent-card weight forever would
     keep competing with the four real next-step chips right below it, especially after "Yes" where the
     card's own text is no longer a question. Settle it down to a plain muted line, same visual register
     as `.sharp-msg.hint`, so attention moves on to what to actually do next. */
  .sharp-voice-ask.sva-done { background:none; border-color:transparent; padding:2px 0 0; }
  .sharp-voice-ask.sva-done .sva-ic { color:var(--mut); }
  .sharp-voice-ask.sva-done .sva-t { font-weight:400; font-size:12.5px; color:var(--mut); margin-bottom:0; }
  .typing { display:inline-flex; gap:5px; padding:2px 0; }
  .typing i { width:7px; height:7px; border-radius:50%; background:var(--mut); display:inline-block; animation:bob 1s infinite ease-in-out; }
  .typing i:nth-child(2){ animation-delay:.16s; } .typing i:nth-child(3){ animation-delay:.32s; }
  @keyframes bob { 0%,70%,100%{transform:translateY(0);opacity:.35} 35%{transform:translateY(-6px);opacity:1} }
  .sharp-input { border-top:1px solid var(--line); padding:12px; display:flex; gap:8px; min-width:0; }
  .sharp-input textarea { flex:1; min-width:0; width:100%; resize:none; height:46px; } /* min-width:0 lets the flex textarea shrink to the drawer instead of overflowing off-screen (mobile clip fix) */
  .sharp-input .mic { flex:0 0 auto; width:46px; height:46px; border:1px solid var(--line); border-radius:10px; background:var(--panel2); font-size:18px; cursor:pointer; }
  .sharp-input .mic.rec { border-color:var(--bad); background:rgba(255,77,79,.14); animation:micpulse 1.1s infinite; }
  @keyframes micpulse { 0%,100%{ box-shadow:0 0 0 0 rgba(255,77,79,.5);} 50%{ box-shadow:0 0 0 6px rgba(255,77,79,0);} }
  #sharpImgPreview:empty { display:none; }
  #sharpImgPreview { display:flex; align-items:center; gap:8px; padding:8px 12px 0; }
  #sharpImgPreview img { height:52px; width:52px; object-fit:cover; border-radius:8px; border:1px solid var(--line); }
  #sharpImgPreview button { flex:0 0 auto; border:1px solid var(--line); background:var(--panel2); border-radius:8px; padding:4px 8px; cursor:pointer; }
  @media (max-width:640px){ .grid{grid-template-columns:1fr;} .filters{gap:10px;} }
  /* bell */
  .bell { position:relative; display:inline-block; }
  #bellBtn { position:relative; padding:8px 11px; }
  .bell-count { position:absolute; top:-6px; right:-6px; background:var(--bad); color:#fff; font-size:10px; font-weight:700; min-width:16px; height:16px; line-height:16px; border-radius:999px; padding:0 4px; text-align:center; }
  .bell-menu { position:absolute; right:0; top:44px; width:min(360px,92vw); max-height:70vh; overflow-y:auto; background:var(--panel); border:1px solid var(--line); border-radius:12px; box-shadow:0 8px 28px rgba(0,0,0,.5); z-index:40; padding:6px; text-align:left; }
  /* PHONE — the panel was rendering off the LEFT edge of the viewport, clipping the first character of every
     line ("Injury update" read as "njury update"). Cause: it is anchored `right:0` to the BELL, and the bell
     is not the rightmost control in the header — refresh and the account avatar sit to its right. So a
     92vw-wide panel hung from a button at ~75vw starts at roughly -17vw, off-screen, and `overflow-y:auto`
     gives no horizontal scroll to recover it.
     Anchoring to the viewport instead of the button is the fix. `position:fixed` is safe here: nothing in the
     ancestor chain sets transform, filter, backdrop-filter, perspective, will-change or contain, so it
     resolves against the viewport and not a containing block. (header is position:sticky, which does NOT
     create one.) Checked before writing this, because a fixed element under a transformed ancestor silently
     anchors to the ancestor and would reproduce the same class of bug. */
  @media (max-width:599px){
    .bell-menu { position:fixed; left:10px; right:10px; top:56px; width:auto; max-height:min(70vh,calc(100vh - 72px)); }
  }
  .bell-menu .n { padding:10px 12px; border-radius:8px; border-bottom:1px solid var(--line); }
  .bell-menu .n:last-child { border-bottom:none; }
  .bell-menu .n.unread { background:var(--panel2); }
  .bell-menu .n-body { font-size:13px; color:var(--mut); margin-top:3px; line-height:1.5; overflow-wrap:anywhere; white-space:normal; }
  /* :not(.n-body-multi) — the multi-item card below needs normal block layout for its rows; the
     webkit-box/line-clamp display here fights that (both targeted .n-body.clamp, so a multi-item card
     used to get BOTH rules at once). */
  .bell-menu .n-body.clamp:not(.n-body-multi) { display:-webkit-box; -webkit-line-clamp:2; -webkit-box-orient:vertical; overflow:hidden; }
  /* a multi-item bundle (several injury updates in one notification) clamps by ROW COUNT, not text lines.
     Layout lives HERE, not as an inline style on the row (core/.../index.html), specifically so this
     nth-child rule can win: an inline style attribute always beats an external stylesheet rule regardless
     of selector specificity, which is what silently broke the first version of this collapse. */
  .bell-menu .n-body-row { display:flex; gap:8px; padding:8px 0; }
  .bell-menu .n-body-row:not(:last-child) { border-bottom:1px solid var(--line); }
  .bell-menu .n-body-multi.clamp .n-body-row:nth-child(n+3) { display:none; }
  .bell-menu .n-more { display:inline-block; margin-top:4px; font-size:11px; font-weight:600; color:var(--accent); cursor:pointer; user-select:none; }
  .bell-menu .n-time { font-size:11px; color:var(--mut); margin-top:5px; }
  .bell-menu .n-link { cursor:pointer; } .bell-menu .n-link:hover { background:var(--panel2); }
  .bell-menu .n-link .n-time { color:var(--accent); }
  .bell-empty { color:var(--mut); padding:18px; text-align:center; font-size:13px; }
  /* DK/FD highlight — the most-used US books (others still shown for users in any state) */
  .play.mybook { border-left:3px solid var(--blue); }
  /* My Bets live tracker */
  .bet-score { font-family:var(--font-num); font-variant-numeric:tabular-nums; font-weight:700; font-size:15px; }
  .bet-live { color:var(--accent); font-weight:700; font-size:11.5px; letter-spacing:.3px; } /* brand green, matching every "good" signal */
  .bet-live .dot { display:inline-block; width:7px; height:7px; border-radius:50%; background:var(--accent-bright); margin-right:5px; animation:sharpBreathe 1.6s ease-in-out infinite; } /* the louder beacon green ONLY on the pulsing dot */
  .ats { font-size:12px; font-weight:800; padding:2px 9px; border-radius:999px; border:1px solid var(--line); white-space:nowrap; }
  .ats.covering, .ats.won { color:var(--accent); border-color:var(--accent); }
  .ats.losing, .ats.lost { color:var(--bad); border-color:var(--bad); }
  .ats.push { color:var(--mut); }
  .mybets-sum { display:flex; gap:14px; flex-wrap:wrap; margin:2px 2px 10px; color:var(--mut); font-size:13px; }
  .mybets-sum b { color:var(--txt); }
  /* performance scoreboard — rolling record / win% / units / ROI over settled bets, honoring the filters */
  .scoreboard { margin:2px 2px 10px; background:var(--panel); border:1px solid var(--line); border-radius:12px; padding:12px 14px; }
  .scoreboard .sb-scope { font-size:11.5px; text-transform:uppercase; letter-spacing:.04em; color:var(--mut); margin-bottom:7px; }
  .scoreboard .sb-row { display:flex; gap:18px; flex-wrap:wrap; align-items:baseline; }
  .scoreboard .sb-stat { display:flex; flex-direction:column; gap:1px; }
  .scoreboard .sb-val { font-size:19px; font-weight:800; color:var(--txt); line-height:1.1; }
  .scoreboard .sb-val.pos { color:var(--accent); } .scoreboard .sb-val.neg { color:var(--bad); }
  .scoreboard .sb-lbl { font-size:11px; color:var(--mut); text-transform:uppercase; letter-spacing:.03em; }
  .scoreboard .sb-note { font-size:11.5px; color:var(--mut); margin-top:7px; }
  .scoreboard .sb-empty { font-size:13px; color:var(--mut); }
  /* league lens chips (All · CFB · NFL) */
  .lg-lens { display:flex; gap:6px; flex-wrap:wrap; margin:0 2px 10px; }
  .lg-lens button { font-size:12.5px; font-weight:700; padding:6px 13px; border-radius:999px; cursor:pointer;
    background:var(--panel2); border:1px solid var(--line); color:var(--mut); }
  .lg-lens button.on { background:var(--accent-dim); border-color:var(--accent); color:var(--txt); }
  /* TA-1244 — a SECOND, independent lens stacked right under a first one (e.g. My Bets' source lens
     under its own origin lens) reads as "one filter split across two rows" unless visually distinguished.
     Smaller + lighter chips + a touch less bottom margin says "a further narrowing lens", without a
     second component/pattern — same .lg-lens shape, just quieter. */
  .lg-lens.lg-lens-sub { margin-top:-2px; }
  .lg-lens.lg-lens-sub button { font-size:11.5px; padding:5px 11px; opacity:.82; }
  .lg-lens.lg-lens-sub button.on { opacity:1; }
  /* Scoreboard tab — the full day's slate (NFL+CFB), live/upcoming/final, independent of any bet */
  .liveboard-controls { display:flex; gap:8px; flex-wrap:wrap; align-items:center; margin:0 2px 12px; }
  .liveboard-daynav { display:flex; gap:4px; }
  .liveboard-daynav button, .liveboard-tz button { font-size:12.5px; font-weight:700; padding:6px 11px; border-radius:999px; cursor:pointer;
    background:var(--panel2); border:1px solid var(--line); color:var(--mut); }
  .liveboard-daynav button.on, .liveboard-tz button.on { background:var(--accent-dim); border-color:var(--accent); color:var(--txt); }
  .liveboard-tz { display:flex; gap:4px; margin-left:auto; }
  .liveboard-row { display:flex; align-items:center; gap:12px; padding:11px 14px; background:var(--panel); border:1px solid var(--line); border-radius:12px; margin:0 2px 8px; }
  .liveboard-row.final { opacity:.72; }
  .liveboard-lg { font-size:10.5px; font-weight:800; letter-spacing:.04em; color:var(--mut); border:1px solid var(--line); border-radius:6px; padding:2px 6px; flex-shrink:0; }
  .liveboard-matchup { flex:1 1 auto; min-width:0; }
  .liveboard-teams { font-weight:700; font-size:14px; color:var(--txt); }
  .liveboard-teams .sc { font-family:var(--font-num); font-variant-numeric:tabular-nums; color:var(--accent); font-weight:800; margin:0 1px; } /* score pops distinct from the team name — was indistinguishable from an AP ranking prefix */
  .liveboard-meta { font-size:11.5px; color:var(--mut); margin-top:2px; }
  .liveboard-status { flex-shrink:0; text-align:right; font-size:12.5px; }
  /* close-game highlight — Q4+/within one score (≤7), bubbled above other live games (see .close sort) */
  .liveboard-row.close { border-color:var(--warn); background:rgba(210,153,34,.08); }
  .close-tag { color:var(--warn); font-weight:700; margin-left:7px; white-space:nowrap; }
  .close-tag .ic { vertical-align:-0.1em; }
  /* Scoreboard's sharp/steam note — one plain-English sentence, entitled Game Lines members only
     (see renderScoreboardTab); "Ask The Angle" opens the chat for the full breakdown. */
  .sharp-note { margin-top:3px; font-size:11.5px; color:var(--mut); line-height:1.4; }
  .sharp-ask { color:var(--accent); font-weight:700; cursor:pointer; white-space:nowrap; }
  /* transient nudge after logging a bet — points to where you can watch it */
  .bet-toast { position:fixed; left:50%; bottom:22px; transform:translateX(-50%) translateY(12px); z-index:40; background:var(--panel); border:1px solid var(--accent); border-radius:999px; padding:9px 16px; font-size:13px; color:var(--txt); box-shadow:0 6px 20px rgba(0,0,0,.4); opacity:0; transition:opacity .25s, transform .25s; pointer-events:none; }
  .bet-toast.show { opacity:1; transform:translateX(-50%) translateY(0); pointer-events:auto; }
  .bet-toast a { color:var(--accent); font-weight:700; cursor:pointer; }
  /* TA-489 follow-up — the PWA path's "verified, tap to continue" card after a slow BetSaracen check:
     this replaces an auto-click the member is used to, so it must read as the primary action still
     pending, not a passive toast — a real button, not small print at the bottom of the screen. */
  .yx-continue-card { position:fixed; left:12px; right:12px; bottom:56px; z-index:50; max-width:420px;
    margin:0 auto; background:var(--panel); border:3px solid #34d399; border-radius:14px;
    padding:14px; box-shadow:0 12px 32px rgba(0,0,0,.5), 0 0 0 1px rgba(52,211,153,.35);
    opacity:0; transform:translateY(16px); transition:opacity .25s, transform .25s; pointer-events:none; }
  .yx-continue-card.show { opacity:1; transform:translateY(0); pointer-events:auto; }
  .yx-continue-card .yx-cc-lbl { font-size:13px; color:var(--mut); margin-bottom:10px; text-align:center;
    padding-right:22px; }
  .yx-continue-card a.primary { display:block; text-align:center; padding:13px; border-radius:10px;
    font-size:15.5px; text-decoration:none; }
  .yx-continue-card .yx-cc-close { position:absolute; top:8px; right:8px; width:28px; height:28px;
    display:flex; align-items:center; justify-content:center; background:transparent; border:none;
    color:var(--mut); cursor:pointer; border-radius:999px; }
  .yx-continue-card .yx-cc-close:hover { color:var(--txt); background:var(--panel2); }
  /* inline SVG icons (Lucide) — inherit color via currentColor, sized in em */
  .ic { display:inline-block; vertical-align:-0.14em; flex:0 0 auto; }
  button .ic, .iconbtn .ic { vertical-align:middle; }
  /* tap-to-learn "?" explainer */
  .help { display:inline-flex; align-items:center; justify-content:center; width:15px; height:15px; border-radius:50%; border:1px solid var(--mut); color:var(--mut); font-size:10px; font-weight:700; margin-left:6px; cursor:pointer; vertical-align:middle; }
  .help:hover { color:var(--txt); border-color:var(--txt); }
  .helpbox { position:absolute; z-index:50; background:var(--panel2); border:1px solid var(--line); border-radius:8px; padding:10px 12px; font-size:12.5px; line-height:1.5; color:var(--txt); box-shadow:0 6px 20px rgba(0,0,0,.5); display:none; }
  /* bet-capture */
  .betwrap { margin-top:9px; }
  /* David, same live screenshot — the Check/+Parlay/+Teaser row that wraps onto its own line under the
     full-width "I placed this bet" button (betbtn-exec, width:100%) was left-aligned by default. Scoped
     to :has(.betbtn-exec) (same :has() pattern already used elsewhere on this page, e.g.
     body:has(.logbet) above) so ONLY this specific exec row centers — the edit/remove .betwrap (My Bets)
     and the teaser-combo .betwrap (single "I bet this teaser" button) are untouched. text-align:center is
     a no-op on betbtn-exec itself (it already fills the full line at width:100%) and only affects the
     mini-button row that wraps below it. */
  .betwrap:has(.betbtn-exec) { text-align:center; }
  /* TA-1294 — same centered treatment extended to the LOGGED state (PR #1404 above only covered the
     not-yet-logged exec row). betControl()'s logged branch (dashboard/index.html) returns
     `.betwrap.on` containing the "You're on this" badge/edit/unbet controls PLUS the identical
     Check/+Parlay/+Teaser mini-button row — `.betwrap.on` is itself `display:flex` (text-align is a
     no-op on a flex container, unlike the plain-block `.betwrap` above, so this needs justify-content
     instead). Scoped to :has(.betmini.betslip) — the +Parlay button's own class, always present once
     logged (TA-1303: unconditional) — so this does NOT also center betBadge()'s other, simpler
     `.betwrap.on` use (no mini-button row, e.g. per-book expand content), which was never reported as
     mis-aligned and stays as-is. */
  .betwrap.on:has(.betmini.betslip) { justify-content:center; }
  .betbtn { padding:5px 10px; font-size:12.5px; border-radius:7px; }
  /* TA-341 final UX piece — betbtn-exec: the "✓ I placed this bet" logging control ONLY, scoped so it
     never touches teaser/parlay/survivor .betbtn usages elsewhere. Kept deliberately NEUTRAL (same
     --panel2/--line/--txt as the base `button` rule, never green) — this is a LOG, not the sportsbook
     handoff, and must never be visually confused with a BET/VIEW/OPEN execution CTA above it. */
  /* David, live screenshot (2026-11-10): the base `button` border (1px var(--line), #26323f on #1c2632
     bg) is too low-contrast against the card's own dark panel — the button was effectively
     invisible/unfindable. Widening to var(--mut) (#8b98a5, the existing neutral/secondary-text token)
     gives a real silver/gray outline without introducing a new color or reading as an accent CTA — still
     neutral, per the comment above. Kept on one line: test/exec-module.test.mjs's own sanity check
     matches this rule with a single-line regex. */
  .betbtn-exec { width:100%; min-height:44px; font-size:13px; font-weight:700; border-color:var(--mut); }
  /* ═══ TA-341 final UX piece — sportsbook EXECUTION MODULE ═══════════════════════════════════════════
     Presentation only: same resolveDeepLink()/sbClickAttrs data every book-row's CTA carries today, just
     laid out as a real "Your Best" / "Best Available" module instead of inline badge text. No card-level
     blue accent — blue lives ONLY inside the module (label + Best Available buttons), per Design Lead
     review of the approved mockup (https://claude.ai/artifact/ELSBADdJiKSbs8e556AevT). */
  .exec { border-top:1px solid var(--line); padding-top:8px; margin-top:8px; display:flex; flex-direction:column; gap:7px; }
  .exec-group { display:flex; flex-direction:column; gap:5px; }
  /* TA-341 REOPENED Priority 1 — Your Angle: visually SEPARATE from the frozen Market Angle tier chip
     (confBlock/.conf-chip/.potd-prime), never merged into it — a distinct labeled row so the two reads
     can never be mistaken for one grade. .na (not executable / juice-killed) mutes the tone; a graded
     read reuses the SAME .conf-chip tier coloring as Market Angle (same tier vocabulary, honestly earned
     fresh) so a matching tier LOOKS the same on purpose, while a differing tier reads at a glance. */
  /* TA-1222 Phase 2 (CR-7) — de-chromed: .your-angle itself (and every one of its former per-state
     border/background variants below) used to render as its own bordered/tinted box. Collapsed into the
     shared --warn/--bad muted-text convention .betclv already uses elsewhere on this file — the
     severity signal lives in the text color and the existing conf-chip/ya-sev-* tier/downgrade markers,
     never in a box of its own. Content/states are unchanged. */
  .your-angle { display:flex; align-items:center; gap:8px; flex-wrap:wrap; margin:6px 2px 2px; padding:1px 2px 0; font-size:12.5px; }
  .ya-lbl { font-size:10px; letter-spacing:.06em; text-transform:uppercase; color:var(--mut); font-weight:800; }
  /* TA-1039 — "Your book" caption always starts its own line inside .your-angle (flex-wrap container),
     so the "whose read is this" signal lands before the tier chip/sentence on every width, never
     sharing a line with them. Scoped to .ya-lbl INSIDE .your-angle only — the sitewide .ya-lbl caption
     used elsewhere (Market Angle, Your Best Now, BetSaracen) is untouched. */
  .your-angle .ya-lbl { flex-basis:100%; margin:0 0 1px; }
  .ya-txt { color:var(--txt); }
  .your-angle.na .ya-txt { color:var(--mut); }
  /* Card UX V2 Phase 2 — Market-vs-Your comparison, split by how much it needs the reader's attention.
     .compact: the two tiers AGREE (cmp==='SAME') — Market Angle's chip above already said the tier once
     and the Your Best row below restates book/point/price with its own chip, so this collapses to one
     quiet confirmation line instead of a second full bordered box (the single biggest repeat offender on
     a matching card). .weaker/.stronger: the two tiers DIFFER (PASS/NOT_EXECUTABLE always count as
     .weaker) — kept at full visual weight and color-coded, because THIS is the comparison David wants
     "immediately understandable" without reading prose first. */
  .your-angle.compact { margin:4px 2px 0; }
  .your-angle.compact .ya-txt { color:var(--mut); font-size:11.5px; }
  /* .weaker/.stronger no longer tint a box (removed per CR-7 above) — the conf-chip/ya-sev-* markers
     already carry the severity signal; no replacement text-color override is needed here. */
  /* TA-1043 — a book-adjusted DOWNGRADE (cmp==='WEAKER') used to reuse .conf-Strong/.conf-Solid's bare
     tier-color classes VERBATIM on the chip itself, so a PRIME->SOLID downgrade chip was pixel-identical
     in color to an ordinary, non-downgraded SOLID chip anywhere else on the site — the only tell was this
     box's own 7% .weaker tint above, easy to miss, especially in dark mode. Real alarm red (.conf-Pass)
     only fired on a fall all the way to Pass; a 1-tier slip got zero chip-level warning.
     DECISION (Builder, TA-1043, justified in the PR): severity SCALES with how many tiers it fell,
     measured by position in the tier ladder (Prime > Strong > Solid > Standard > Lean > Pass) — not by
     TIER_RANK's raw numeric gap, which isn't evenly spaced (Standard sits a half-step off Solid/Lean) and
     would otherwise call a Solid->Lean slip (two ladder positions) "mild" just because its number gap is
     1. A 1-position slip (e.g. Strong->Solid) is a real but survivable repricing — .ya-sev-warn (see its
     own ROUND 3 comment below for the final color/shape, which changed twice after this). A 2+ position
     slip is the SAME category of bad as falling to Pass — .ya-sev-bad, the one true brand red (--bad), matching
     .conf-Pass's own treatment one-for-one. Either way, the chip itself now visibly differs in COLOR from
     a same-tier, non-downgraded chip elsewhere on the site — never just the surrounding box's tint — so a
     member glancing at the number alone (not reading the prose) still sees that something changed from the
     headline. Scoped to .your-angle so .conf-Strong/.conf-Solid/.conf-Lean stay untouched everywhere else
     they're reused verbatim (confBlock, ladder, Best-of-Your-Books, etc. — see their own "never redefine"
     notes above).
     ROUND 2 (cold Grok check on real screenshots) — the first cut's faint amber OUTLINE (16% tint,
     amber text) FAILED on a real PRIME card: sitting directly under .conf-Prime's bright gold fill, it
     read as "a dull gold pill... another tier badge, not an alarm," because amber and gold are both warm/
     yellow and visually adjacent once stacked. Tried a SOLID amber fill + an inline "↓ " text prefix —
     FAILED AGAIN, WORSE: "solid gold fill, same shape/weight/hue family as Prime... down arrow too weak
     to carry direction alone... subordinate to the word" (verbatim). Root cause, confirmed across both
     failures: a filled `.conf-chip` PILL reads as a RANK before any hue or inline glyph gets parsed — no
     recoloring and no inline-text decoration fixes that; the pill SILHOUETTE itself has to go for this
     one case.
     ROUND 3 (two independent consults, Grok + GPT-5.1, converged on the same answer — see
     docs/STRATEGY-LOG.md) — kill the filled-pill shape for ya-sev-warn specifically. Use --blue, the one
     token in this palette nothing else here has claimed: not gold/--prime (the collision source), not
     teal/--tier-strong (Strong/Solid's own color — would read as a THIRD rank), not --bad (reserved for
     the 2-rung/Pass case, already passed, never touch), not --accent (means "stronger than market," the
     opposite direction). No fill at all — a plain word in --txt (the real tier name stays uncolored, so
     it never reads as a second rank claim). The 2-rung/.conf-Pass red treatment already passed cold
     review unchanged every round and is untouched here.
     ROUND 4 (cold Grok re-check on the real round 3 render) — PARTIAL PASS: the no-fill/plain-word fix
     above is CONFIRMED correct ("the pill-shape objection is fixed... hue is also out of the gold/teal
     family" — verbatim) and is UNTOUCHED by this round. Two real defects remained, both in the direction
     marker only: (1) round 3's --blue UNDERLINE read as this card's own hyperlink affordance, not a
     warning — "the blue underline does not mean downgrade. It means link... nothing else in this card
     uses it that way" (verbatim) — REMOVED here, no underline at all; (2) round 3's `::before` "↓" was,
     even enlarged, "subordinate to the type, and competing with a second arrow (→) that already means
     'becomes'" in the same sentence (verbatim) — a thin arrow stroke next to another thin arrow stroke
     reads as the same family of mark. Fixed by swapping the glyph for a SOLID shape ("▼", U+25BC BLACK
     DOWN-POINTING TRIANGLE) instead of another arrow stroke — genuinely different weight/style from the
     sentence's own "→", not just a bigger version of the same character — sized well past the tier
     word's own x-height. The trailing em dash directly after THIS chip (renderYourAngle()'s own `sep`)
     was separately flagged as reading like a broken/floating separator on the real render and is dropped
     for ya-sev-warn only — ya-sev-bad's own separator is untouched, it never drew that complaint. */
  .your-angle .conf-chip.ya-sev-warn {
    display:inline-flex; align-items:center; gap:6px; vertical-align:baseline;
    margin:0; padding:0; background:none; border:0; border-radius:0; box-shadow:none;
    color:var(--txt); font-weight:650; line-height:1.1;
  }
  .your-angle .conf-chip.ya-sev-warn::before {
    content:"\25BC"; /* U+25BC BLACK DOWN-POINTING TRIANGLE — a solid shape, deliberately NOT another thin
       arrow stroke like the sentence's own "→" (round 4 finding: two arrow-family glyphs in one sentence
       compete and the smaller one loses). Never an emoji-presentation character either (could paint
       yellow/red and walk back into the gold/red collisions this whole fix is about). */
    font-size:1.5em; line-height:.6; color:var(--blue); position:relative; top:.04em;
  }
  .your-angle .conf-chip.ya-sev-bad { background:color-mix(in srgb, var(--bad) 14%, transparent); color:var(--bad); border:1px solid var(--bad); }
  /* flex+wrap (not nowrap) — the explanatory sentence now nests INSIDE this span as one continuous
     phrase (see renderYourAngle's own header note), so this must wrap like a normal paragraph on a
     narrow card, never force a single unbroken line that could overflow at 390px. */
  .ya-cmp { display:flex; flex-wrap:wrap; align-items:baseline; gap:5px; font-size:12px; font-weight:700; color:var(--txt); }
  .ya-cmp b { font-weight:800; }
  .ya-cmp .ya-txt { font-weight:400; }
  /* the standalone "MARKET ANGLE" label used to be its own full margin-bearing line above confBlock's
     chip; this inline variant sits tight over the chip instead of claiming a whole line of its own. */
  .mkt-lbl { font-size:10px; letter-spacing:.06em; text-transform:uppercase; color:var(--mut); font-weight:800; margin:6px 2px 0; }
  .qa-note { font-size:10.5px; color:var(--mut); margin:4px 2px 0; }
  .exec-label { display:flex; align-items:center; gap:7px; font-size:10.5px; font-weight:800; letter-spacing:.09em; text-transform:uppercase; }
  .exec-label.mine { color:var(--accent); }
  .exec-label.avail { color:var(--blue); }
  .exec-label .line { flex:1; height:1px; background:currentColor; opacity:.25; }
  .book-row { display:flex; align-items:center; gap:10px; background:var(--panel2); border:1px solid var(--line); border-radius:9px; padding:6px 6px 6px 12px; min-height:44px; flex-wrap:wrap; }
  /* TA-341 REOPENED Priority 2 — the RECOMMENDED row among 2+ of the member's own books, real visual
     weight (not just "first in the list") so the member doesn't have to compare BET buttons themselves. */
  .book-row.rec { border-color:var(--accent); background:color-mix(in srgb, var(--accent) 9%, var(--panel2)); }
  /* TA-1222 Phase 2 (CR-4) — every row but the single recommended one (.rec) demoted: muted/outline
     instead of the same full-weight panel box, a ceiling never a floor. The real tap target
     (min-height:44px above, the real <a href>/sbClickAttrs() below via .cta) is completely untouched —
     this never forces a fake affordance onto a legitimately non-interactive row (see .book-nolink
     below, already its own plain non-link treatment, also untouched). Never a tier hue — CR-7. */
  .book-row:not(.rec) { background:transparent; border-color:color-mix(in srgb, var(--line) 65%, transparent); opacity:.82; }
  .book-row:not(.rec):hover { opacity:1; }
  .book-info { flex:1; min-width:0; }
  .book-name { font-size:13.5px; font-weight:700; display:block; word-break:break-word; }
  .book-price { font-size:12.5px; color:var(--mut); font-variant-numeric:tabular-nums; }
  .book-price b { color:var(--txt); font-weight:700; }
  .owned-tag, .reason-tag, .reason-at { font-size:10.5px; color:var(--mut); font-weight:400; }
  /* Plays Discovery & Availability UX (2026-10-12), decision #4 — the ONE "unmistakable" variant of
     .owned-tag, used only when a card has NO owned-book row at all and this label is the sole thing
     telling the member they can't place this specific bet through their own books. Reuses the same
     warn palette .your-angle.weaker already uses for the identical "not for you" meaning, so the two
     surfaces read as one consistent visual language rather than two different warning styles. */
  .owned-tag.notmine-strong { font-size:11px; font-weight:700; color:var(--warn); }
  .rec-tag { font-size:10.5px; color:var(--accent); font-weight:800; text-transform:uppercase; letter-spacing:.04em; }
  /* real ~44px tap target (Apple HIG / Android both land near 44-48dp) — a genuine <a> button, not an inline text link */
  .cta { flex-shrink:0; display:inline-flex; align-items:center; justify-content:center; gap:4px; font-size:12.5px; font-weight:800; border-radius:8px; padding:0 14px; white-space:nowrap; text-decoration:none; border:1px solid transparent; min-height:44px; min-width:66px; }
  .cta.bet { background:var(--accent); color:#08130a; }
  /* TA-491 (UX Reviewer finding, 2026-09-22) — a runner-up row's BET CTA rendered as the SAME solid,
     equally-weighted green button as the RECOMMENDED row's — paired with its honest "Better price"/
     "Better number" reason tag, this read as a competing steer (a member skimming could tap the row
     LABELED "better" thinking that's the advice, the opposite of the intended meaning). Only the
     RECOMMENDED row keeps the solid primary treatment now; every other row's bet CTA is the SAME
     secondary outline style `.cta.view` already uses elsewhere — still a real, fully working button,
     just visually unambiguous about which one is the actual recommendation. Copy itself (SHOP_REASON_
     LABEL, confirmed with David for TA-341) is untouched — this is a visual fix, not a wording change. */
  .book-row:not(.rec) .cta.bet { background:transparent; border-color:var(--accent); color:var(--accent); }
  .cta.view { background:transparent; border-color:var(--blue); color:var(--blue); }
  .cta.open { background:transparent; border-color:var(--line); color:var(--mut); }
  /* TA-1222 Phase 2 Revision note (round 9) — Game Lines' own "Your Best" book CTA, tier-colored
     VERBATIM per .conf-Prime/.conf-Strong/.conf-Solid/.conf-Lean above (never a new palette) — the
     same already-approved pattern .exec-btn (TA-1136) ships for a different single-button call site.
     Added IN ADDITION to the existing verb-based .cta.bet/.view/.open classes (kept, untouched) —
     these rules override their color only, on rows that carry a real per-book tier. The duplicated
     `.book-row:not(.rec) .cta.bet` selector (TA-491, above) outranks a bare `.cta.cta-tier-*` on
     specificity alone, so it's matched explicitly here too, to still win color on a runner-up row. */
  .cta.cta-tier-Prime, .book-row:not(.rec) .cta.cta-tier-Prime { background:var(--prime); color:var(--prime-ink); border:0; box-shadow:0 4px 14px -4px var(--prime-glow); }
  .cta.cta-tier-Strong, .book-row:not(.rec) .cta.cta-tier-Strong { background:var(--tier-strong-dim); color:var(--tier-strong); border:1px solid color-mix(in srgb,var(--tier-strong) 45%,transparent); }
  .cta.cta-tier-Solid, .book-row:not(.rec) .cta.cta-tier-Solid { background:transparent; color:var(--tier-strong); border:1px solid color-mix(in srgb,var(--tier-strong) 35%,transparent); }
  .cta.cta-tier-Lean, .book-row:not(.rec) .cta.cta-tier-Lean { background:transparent; color:var(--mut); border:1px solid var(--line); }
  /* .cta-tier-Pass reuses .ba-bookbtn.t-pass's own red verbatim (below) rather than inventing a new
     treatment — a Pass-graded own-book row should visibly read as "don't bet this one." */
  .cta.cta-tier-Pass, .book-row:not(.rec) .cta.cta-tier-Pass { background:transparent; border-color:var(--bad); color:var(--bad); }
  .book-nolink { font-size:13px; color:var(--mut); flex-shrink:0; padding:0 6px; }
  .book-nolink-note { flex-basis:100%; font-size:11px; color:var(--mut); opacity:.75; padding:0 12px 2px; }
  /* Best Angles card — compact book buttons (David, 2026-10-17; REBUILT same day after he caught the
     first two cuts not matching what he'd actually approved — see _baBookButtonsHtml()'s own header
     comment and the Already-Bet Card Concept artifact, K24W5Y2UU5fQbZUiqYFU7C, for the exact approved
     shape). ONE outlined button per book — book + line + price inside ONE tap target, border+text tinted
     by that book's own tier, transparent fill, small arrow. Not a row, not a separate chip glued to a
     separately-colored CTA pill — that was the mistake both earlier cuts made. */
  .ba-books { margin-top:8px; display:flex; flex-wrap:wrap; gap:6px; }
  .ba-bookbtn { display:inline-flex; align-items:center; gap:4px; font-size:11.5px; font-weight:600; padding:5px 9px; border-radius:7px; border:1px solid var(--line); color:var(--txt); line-height:1.2; text-decoration:none; }
  .ba-bookbtn .ba-bn { color:var(--mut); font-weight:500; }
  .ba-bookbtn.tap { cursor:pointer; }
  .ba-bookbtn .ba-ar { margin-left:1px; }
  /* Tier is the ONLY color signal here — border + text, same tokens used everywhere else on the site
     (conf-chip's Prime/Strong tokens), transparent fill so it reads as an outline chip, not a filled CTA.
     Solid shares Strong's teal (same as .conf-Solid elsewhere) at a dimmer border — the two are told apart
     by which tier word a member already knows from the card's main chip, same as the rest of the site. */
  .ba-bookbtn.t-prime { border-color:var(--prime); color:var(--prime); }
  .ba-bookbtn.t-prime .ba-bn { color:var(--prime); }
  .ba-bookbtn.t-prime.tap:hover { background:color-mix(in srgb, var(--prime) 14%, transparent); }
  .ba-bookbtn.t-strong { border-color:var(--tier-strong); color:var(--tier-strong); }
  .ba-bookbtn.t-strong .ba-bn { color:var(--tier-strong); }
  .ba-bookbtn.t-strong.tap:hover { background:var(--tier-strong-dim); }
  .ba-bookbtn.t-solid { border-color:color-mix(in srgb, var(--tier-strong) 45%, transparent); color:var(--tier-strong); }
  .ba-bookbtn.t-solid .ba-bn { color:var(--mut); }
  .ba-bookbtn.t-solid.tap:hover { background:var(--tier-strong-dim); }
  /* Pass (the math says no — a real grade, just a bad one) gets the site's one true brand red (--bad,
     same token as .conf-Pass elsewhere) so a member sees a warning on the exact tap target where they'd
     commit to the bet. No-tier (a Props book — no sharp reference to grade against) stays plain grey:
     a missing grade and a bad grade are different states (TA-1053) and must look different. */
  .ba-bookbtn.t-pass { border-color:var(--bad); color:var(--bad); }
  .ba-bookbtn.t-pass .ba-bn { color:var(--bad); }
  .ba-bookbtn.t-none { color:var(--mut); }
  .ba-bookbtn.t-none .ba-bn { color:var(--mut); }
  /* TA-1222 Phase 2 (CR-4/CR-7) — demotes every book row EXCEPT the single best/executable one, across
     all three book-rendering systems (.ba-bookbtn here/Moneyline's own local row(); .book-row below;
     execBookRow()'s own variant). A ceiling (reduced opacity), never a change to color/tap-target — the
     real `<a href>`/sbClickAttrs() destination (where one exists) stays exactly as tappable as it was,
     and a legitimately non-interactive <span> (no destination) stays non-interactive, just visually
     quieter like every demoted row. Never a tier hue (gold/teal-fill/teal-outline/grey) — CR-7's ban on
     reusing the tier ladder's own vocabulary for unrelated emphasis. */
  .ba-bookbtn.ba-demoted { opacity:.68; }
  .ba-bookbtn.ba-demoted:hover { opacity:.9; }
  .ba-books-hint { font-size:10.5px; color:var(--mut); margin-top:5px; }
  /* Home's play row centers its two flex children by default, fine when both sides are one line tall —
     once the left side can grow (bet badge + book buttons), top-align instead so the edge/EV figure on
     the right doesn't float in the middle of a now-taller card. */
  .home-play.ba-home-play { align-items:flex-start; }
  .betform { display:flex; gap:6px; align-items:center; flex-wrap:wrap; }
  .betform input { padding:6px 8px; font-size:13px; width:auto; }
  .betmsg { font-size:12px; }
  /* Manual "+ Log a bet" capture — for teasers/parlays/props/spreads Sharp didn't surface (incl. off-feed books like BetSaracen) */
  .logbet-open { display:inline-flex; align-items:center; gap:7px; font-size:13px; font-weight:700; color:var(--accent); background:var(--accent-dim); border:1px solid var(--accent); border-radius:9px; padding:8px 14px; cursor:pointer; margin:2px 2px 12px; }
  .logbet-open:hover { background:color-mix(in srgb,var(--accent) 20%,transparent); }
  .logbet { background:var(--panel); border:1px solid var(--line); border-radius:12px; padding:14px; margin:2px 2px 14px; }
  .logbet h4 { margin:0 0 10px; font-size:14px; color:var(--txt); }
  .lb-grid { display:grid; grid-template-columns:repeat(auto-fit,minmax(130px,1fr)); gap:9px; }
  .lb-field { display:flex; flex-direction:column; gap:4px; }
  .lb-field label { font-size:11.5px; font-weight:600; color:var(--mut); text-transform:uppercase; letter-spacing:.03em; }
  .lb-field input, .lb-field select { padding:8px 10px; font-size:14px; }
  .lb-seg { display:flex; gap:6px; flex-wrap:wrap; margin-bottom:12px; }
  .lb-seg button { flex:1 1 auto; min-width:74px; padding:8px 6px; font-size:13px; font-weight:600; border-radius:8px; background:var(--panel2); border:1px solid var(--line); color:var(--mut); cursor:pointer; }
  .lb-seg button.on { background:var(--accent-dim); border-color:var(--accent); color:var(--accent); }
  .lb-leg { display:flex; flex-wrap:wrap; gap:8px; align-items:end; margin-bottom:8px; }
  .lb-leg .lb-field { flex:1 1 120px; }
  .lb-leg .lb-rm { padding:8px 0; font-size:15px; line-height:1; background:var(--panel2); border:1px solid var(--line); color:var(--mut); border-radius:8px; cursor:pointer; }
  .lb-addleg { font-size:12.5px; font-weight:600; color:var(--blue); background:none; border:1px dashed var(--line); border-radius:8px; padding:7px 12px; cursor:pointer; margin:2px 0 12px; }
  .lb-actions { display:flex; gap:10px; align-items:center; margin-top:12px; flex-wrap:wrap; }
  .lb-hint { font-size:12px; color:var(--mut); margin:0 0 12px; }
  /* SP-274 — the same in-form hint slot, in the problem colour. A modifier rather than an inline
     style so the size and spacing stay tied to .lb-hint and cannot drift away from its three siblings. */
  .lb-hint.warn { color:var(--warn); }
  /* The one field a completion is about. Cleared on first input (see the edit handler) so the form
     stops flagging a problem the member has just fixed. */
  .logbet input.needs { border-color:var(--warn); }
  /* Sharp-parsed "log this bet?" confirm chip (nothing saves until tapped) */
  .logbet-chips { margin-top:10px; background:var(--panel2); border:1px solid var(--accent); border-radius:10px; padding:11px 12px; }
  .lbc-head { font-size:13px; font-weight:700; color:var(--txt); margin-bottom:6px; }
  .lbc-item { font-size:13px; color:var(--txt); margin:3px 0; }
  .lbc-item.lbc-dup { opacity:.72; }
  .lbc-dupflag { color:var(--warn); font-weight:700; font-size:11.5px; white-space:nowrap; }
  .lbc-actions { display:flex; gap:8px; align-items:center; flex-wrap:wrap; margin-top:9px; }
  .lbc-link { cursor:pointer; color:var(--blue); font-weight:600; font-size:13px; }
  /* Sharp-parsed Survivor pick → an EDITABLE card, not a claim (SP-243 §2).
     Accent border, matching .logbet-chips below. The first cut used a grey --line border to signal
     "this is a question, not a claim"; the Design Lead gate ruled against it and is right — it made the
     card RECEDE into the message bubble rather than read as a sibling of the log-a-bet chip, and the
     form/claim distinction is already carried, far more strongly, by the head copy ("Want to record a
     pick? Here is what I heard"), the "nothing is saved until you press confirm" line, and the labelled
     editable controls. Desaturating the container was paying for that distinction twice, in the one
     currency that also costs legibility.

     ⚠ white-space:normal IS LOAD-BEARING, DO NOT REMOVE IT. .sharp-msg sets white-space:pre-wrap so the
     model's own line breaks survive, and this card is appended INSIDE one. Every newline-and-indent
     between the divs of a multi-line template literal therefore rendered as a LITERAL BLANK LINE: the
     gate measured ~43px of dead space where the CSS asks for 4-9px, on a card already 444px tall next
     to a 140px bet chip, and it grew by five more phantom lines per extra pick row. renderLogbetChips is
     immune only by accident — it happens to be typed as single-line concatenated strings. Resetting the
     property here fixes the whole subtree by construction, so the next person to format this markup
     readably cannot re-introduce it. */
  .svpick { margin-top:10px; background:var(--panel2); border:1px solid var(--accent); border-radius:10px; padding:11px 12px; white-space:normal; }
  .svp-head { font-size:13px; font-weight:700; color:var(--txt); margin-bottom:4px; display:flex; align-items:center; gap:6px; }
  .svp-note { font-size:12px; color:var(--mut); margin-bottom:9px; }
  .svp-single { font-size:12px; margin-bottom:8px; }
  /* ⚠ A GRID, NOT A WRAPPING FLEX ROW. As flex-wrap, the remove control dropped onto a line of its own
     below the week/team pair at the ~304px a 390px phone actually gives this drawer — orphaned from the
     row it removes, and worse with every extra row in a batch. Three columns pin it beside its own
     controls at every width; the team select takes the slack and minmax(0,1fr) lets it actually shrink
     (a bare 1fr floors at the select's content width and overflows instead). */
  .svp-row { display:grid; grid-template-columns:auto minmax(0,1fr) auto; gap:8px; align-items:end; padding:7px 0; border-top:1px solid var(--line); }
  .svp-row:first-child { border-top:none; padding-top:0; }
  .svp-field { display:flex; flex-direction:column; gap:4px; min-width:0; }
  .svp-field label { font-size:11.5px; font-weight:600; color:var(--mut); text-transform:uppercase; letter-spacing:.03em; }
  .svp-field select { padding:7px 9px; font-size:14px; width:100%; }
  .svp-rm { display:inline-flex; align-items:center; justify-content:center; padding:8px 10px; font-size:15px; line-height:1; background:var(--panel); border:1px solid var(--line); color:var(--mut); border-radius:8px; cursor:pointer; }
  .svp-rm:hover { color:var(--txt); border-color:var(--mut); }
  .svp-status { grid-column:1 / -1; font-size:12px; color:var(--mut); display:flex; align-items:center; gap:6px; flex-wrap:wrap; }
  .svp-status.good { color:var(--accent); font-weight:600; }
  .svp-status.warn { color:var(--warn); }
  .svp-status.bad  { color:var(--bad); }
  /* ⚠ 44px MINIMUM ON EVERY TAP TARGET IN THIS CARD. Confirm and Dismiss were 26px — under the touch
     guidance, for the most important tap in the feature — and the replace answers carry a decision that
     is now the primary action of their row, so they get it too. Scoped to .svpick rather than applied to
     .betbtn, which belongs to the bet form and is not this ticket's to resize. */
  .svpick .betbtn { min-height:44px; }
  .svp-status .betbtn { padding:4px 11px; font-size:12.5px; }
  /* ⚠ SAME 44px RULE, SAME REASON, FOR THE ⟦HCNOTIFY⟧ CARD (TA-772 round 5). Measured in a real
     headless render at 375px and 390px before this rule existed: the bell button came out 40px and
     BOTH "Email it to me" and "That's enough, thanks" came out 26px — the identical under-touch-guidance
     miss the .svpick rule above was written to fix, reintroduced simply because this new card reuses
     .betbtn without being .svpick. Scoped the same way, for the same stated reason: .betbtn itself
     belongs to the bet form and is not this ticket's to resize. */
  .hcnotify-chip .betbtn { min-height:44px; }
  .svp-actions { display:flex; gap:8px; align-items:center; flex-wrap:wrap; margin-top:10px; }
  /* "You're on this" badge — persistent signal that you've already logged this bet (idea #2) */
  .betwrap.on { display:flex; align-items:center; gap:8px; flex-wrap:wrap; }
  .beton { display:inline-flex; align-items:center; gap:5px; font-size:12.5px; font-weight:700; color:var(--accent); background:var(--accent-dim); border:1px solid var(--accent); border-radius:7px; padding:4px 9px; }
  /* TA-1222 Phase 2 (CR-3c) — size/footprint evaluated and shrunk per the spec's own "real room to
     change SIZE and FOOTPRINT" allowance: smaller padding/font than before, to fit the new, flatter
     card. The locked constraint (unchanged, not touched by this pass): Check still wins by FILL
     (.betadd's accent-dim background) over Parlay/Teaser's bordered-only treatment (.betslip) — see
     the TA-1283 comments immediately below, which this pass does not alter. */
  .betmini { padding:2px 6px; font-size:11px; border-radius:5px; background:var(--panel2); border:1px solid var(--line); color:var(--mut); cursor:pointer; line-height:1; }
  .betmini:hover { color:var(--txt); border-color:var(--mut); }
  /* TA-594 — "+ Add another": a worded (not icon-only) betmini twin, so it never gets mistaken for the
     icon-only ✎/✕ pair next to it — this one's a deliberate second bet, not an edit or a removal. */
  .betmini.betadd { display:inline-flex; align-items:center; gap:3px; padding:2px 8px; color:var(--accent); border-color:var(--accent); }
  .betmini.betadd:hover { background:var(--accent-dim); color:var(--accent); border-color:var(--accent); }
  /* TA-1283 Design Lead gate, round 2 (2026-11-09) — independent review (GPT-5.1 + Grok, both shown the
     real rendered pixels) caught a real hierarchy inversion the first pass missed: .betmini.betslip's
     100%-var(--txt) border measured ~12.9:1 contrast against the card background, vs. .betadd's own
     accent border at ~6.0:1 — the "equal-footing secondary" was objectively the LOUDEST stroke in the row,
     beating Check for attention rather than sitting clearly behind it (both reviewers independently said
     the fix needed to win on FILL, not just match on legibility). Reusing .beton's existing accent-dim-fill
     pattern (not a new 4th button language) so Check wins by fill the same way every other "on"/positive
     mini-state in this system already does. */
  .betmini.betadd { background:var(--accent-dim); }
  /* TA-1283 — "+Parlay"/"+Teaser" equal-footing treatment (spec: docs/specs/TA-1283-check-bet-visual-
     hierarchy.md, Option 2). Same size/padding as .betadd above, and the same high-contrast bordered
     legibility bet-checker.html's own "+Parlay" reference button uses — but deliberately NOT a clone of
     .betadd's accent color: Check must stay the one "go" action on the row (TA-341 hierarchy), so this
     reads as a real, legible secondary action rather than the washed-out .betmini ghost chip it replaces.
     Round 2 (2026-11-09): border toned from a full var(--txt) stroke (measured as out-contrasting Check,
     see .betadd's own comment above) to a color-mix blend toward --line — keeps the label fully legible at
     var(--txt) text color (fixes the original "I never noticed this" bug) while the BORDER itself is no
     longer the single brightest edge in the row. Still visibly bordered and clickable, never back to the
     pre-PR washed-out var(--mut)/var(--line) ghost chip. */
  .betmini.betslip { padding:2px 8px; color:var(--txt); border-color:color-mix(in srgb, var(--txt) 40%, var(--line)); }
  .betmini.betslip:hover { background:var(--panel2); color:var(--txt); border-color:var(--txt); }
  .betclv { font-size:11.5px; font-weight:600; }
  .betclv.good { color:var(--accent); }
  .betclv.warn { color:var(--warn); }
  /* TA-1222 Phase 2 (CR-5/CR-7) — the signed movement/CLV number, distinct from the qualitative
     good/warn text it sits beside and from Band 3's separately-labeled "edge" figure. Deliberately
     --mut regardless of the good/warn parent — a plain factual readout, not a second emotionally-colored
     chip, and never a tier hue. */
  .betclv-delta { color:var(--mut); font-weight:700; }
  /* UX Reviewer gate (2026-11-10, PR #1402 PASS WITH FIXES #1) — on a logged card, Band 3's edge figure
     (oddsFair's .of-gap, e.g. "+1 pt") and this Band 4 movement figure (e.g. "-1pt") carry matching
     magnitude with only color telling them apart; both are correctly labeled, but a 3-second scan can
     still read them as the same number restated. Breaking .betclv-delta onto its own line with a thin
     top divider (block display is valid here — .betclv, its flex-item parent, is already blockified by
     the flex layout) gives the two figures real spatial separation, not just a color difference. Pure
     styling — the labels/text/values themselves are unchanged. */
  .betclv-delta { display:block; margin-top:4px; padding-top:4px; border-top:1px solid var(--line); }
  /* auto-update chip — a new deploy shipped while this (possibly days-old PWA) page was alive; one tap reloads */
  .update-chip { position:fixed; left:50%; transform:translateX(-50%); bottom:calc(18px + env(safe-area-inset-bottom,0px));
    z-index:9000; background:var(--accent); color:#0b1020; border:none; border-radius:999px; padding:11px 18px;
    font-size:13.5px; font-weight:800; box-shadow:0 6px 22px rgba(0,0,0,.4); cursor:pointer; animation:chipIn .25s ease-out; }
  .update-chip:hover { filter:brightness(1.06); }
  @keyframes chipIn { from { opacity:0; transform:translate(-50%,10px); } to { opacity:1; transform:translate(-50%,0); } }
  /* top-bar cluster (freshness dot · bell · refresh · account avatar) — never wraps. #who is the
     header's other flex child (besides .brand) and has no rule of its own otherwise.
     ⚠ flex-shrink:0 here, NOT min-width:0 — #who must be the flex item that DOESN'T give. Tried
     min-width:0 first: with header's two children at the default flex-shrink:1 each, the browser
     splits the shrink deficit between BOTH of them, proportional to their own max-content size — since
     the logo's natural size (~700px source image, before any of its own shrinking) so outweighs the
     topbar's (~190px), #who still got squeezed below what its flex-shrink:0 children need (measured:
     squeezed to 55px against a 188px minimum), and since #who itself has no overflow:hidden, its
     children just rendered past its shrunk box — the exact overflow this fix exists to remove, just
     moved one level down. flex-shrink:0 removes #who from the shrink calculation entirely, so 100% of
     any deficit lands on .brand (flex-shrink:1, min-width:0), which is the one thing meant to give. */
  #who { flex-shrink:0; }
  .topbar { display:flex; align-items:center; gap:10px; flex-wrap:nowrap; }
  /* Every control in the cluster is a fixed, already-tight size (36px icon/pill buttons, a 32px avatar) —
     none of it should ever be the thing that gives when space runs out. flex-shrink:0 here pairs with
     .brand's flex-shrink:1 (default) below: on a narrow phone the LOGO is the one thing allowed to get
     smaller, never these controls (a squished bell/refresh/avatar would look broken, not responsive). */
  .topbar > * { flex-shrink:0; }
  .fresh { display:inline-flex; align-items:center; gap:5px; min-width:0; cursor:pointer; border-radius:8px; }
  .fresh .dot { width:8px; height:8px; border-radius:50%; flex:0 0 auto; }
  .fresh .lbl { font-size:12px; color:var(--mut); white-space:nowrap; overflow:hidden; text-overflow:ellipsis; }
  /* ⚠ TA mobile-header overflow fix (2026-09-22): this label used to always read a short "Market 5h" —
     safe at any width. #348 (same day) changed it to full sentences ("Markets — freshness warning",
     "Markets — data problem"), up to ~28 chars, with no responsive treatment added alongside — that's
     what pushed the bell/refresh/avatar off the right edge of the viewport on phones (and, because
     nothing on the page stops horizontal growth, widened the whole document, which is what also made
     the second nav row's real edge look clipped mid-tab instead of at its own intentional fade+chevron).
     Below 600px the label collapses to just the colored dot; the full sentence is still reachable by tap
     (or hover on anything with a pointer) via the existing help-chip mechanism, wired in updateFreshness(). */
  @media (max-width:599px){
    .fresh { padding:8px 4px; margin:-8px -4px; } /* enlarge the tap target without changing the box's footprint in the row */
    .fresh .lbl { display:none; }
  }
  .iconbtn { position:relative; width:36px; height:36px; padding:0; display:inline-flex; align-items:center; justify-content:center; font-size:15px; border-radius:8px; }
  .iconbtn.spin { animation:spin 1s linear infinite; }
  @keyframes spin { to { transform:rotate(360deg); } }
  /* "＋ submit a promo" — subtle accent affordance in the top cluster, visible to any signed-in member */
  .iconbtn.promo-add { color:var(--accent); border-color:var(--accent); font-weight:800; }
  .iconbtn.promo-add:hover { background:var(--accent); color:var(--accent-ink); }
  .pillbtn { height:36px; padding:0 12px; display:inline-flex; align-items:center; gap:4px; font-size:13px; font-weight:700; border-radius:18px; white-space:nowrap; }
  .pillbtn.promo-add { color:var(--accent); border-color:var(--accent); }
  .pillbtn.promo-add:hover { background:var(--accent); color:var(--accent-ink); }
  /* ⚠ My Bets reverted to a plain main-nav tab, 2026-09-16 (was SP-4's top-right pill) — it takes the
     standard `.tab.active` styling like every other destination, so no dedicated rule is needed here. */
  /* A labelled Promo pill will not fit beside the bell, refresh and avatar on a phone. Below 600px it
     collapses to its icon (the title attribute carries the name). */
  @media (max-width:599px){
    .topbar .pillbtn { width:36px; padding:0; justify-content:center; border-radius:8px; }
    .topbar .pillbtn .pill-lbl { display:none; }
  }
  /* modal (shared shell for the submit-a-promo flow) */
  .modal-back { position:fixed; inset:0; background:rgba(0,0,0,.6); z-index:60; display:flex; align-items:flex-start; justify-content:center; padding:24px 12px; overflow-y:auto; }
  .modal { background:var(--panel); border:1px solid var(--line); border-radius:14px; width:min(460px,100%); padding:20px; box-shadow:0 12px 40px rgba(0,0,0,.55); }
  .modal h3 { margin:0 0 4px; font-size:18px; }
  .modal .sub { color:var(--mut); font-size:13px; margin-bottom:14px; }
  /* Was a full re-declaration of .eyebrow at .5px instead of .06em. Now it only carries what is
     genuinely its own: it is a block-level form label and needs the vertical rhythm. */
  .modal label.fld { display:block; margin:12px 0 5px; }
  .modal .file-drop { display:block; border:1px dashed var(--line); border-radius:10px; padding:16px; text-align:center; color:var(--mut); font-size:13.5px; line-height:1.5; cursor:pointer; background:var(--panel2); }
  .modal .file-drop.has { border-color:var(--accent); color:var(--txt); }
  .modal .row2 { display:grid; grid-template-columns:1fr 1fr; gap:10px; }
  .modal .pubtoggle { display:flex; gap:8px; margin-top:6px; }
  .modal .pubtoggle button { flex:1; font-size:13px; }
  .modal .pubtoggle button.on { background:var(--accent); color:var(--accent-ink); border-color:var(--accent); font-weight:700; }
  .mid-intro { border:1px solid var(--accent); background:linear-gradient(180deg,var(--accent-dim),transparent); border-radius:10px; padding:11px 13px; }
  .modal .chips { display:flex; flex-wrap:wrap; gap:6px; }
  .modal .fld-group { margin:16px 0 2px; font-size:12px; font-weight:700; color:var(--accent); text-transform:uppercase; letter-spacing:.5px; border-top:1px solid var(--line); padding-top:12px; }
  .modal .tag-input { display:flex; flex-wrap:wrap; gap:6px; align-items:center; border:1px solid var(--line); border-radius:10px; background:var(--panel2); padding:7px 8px; min-height:42px; cursor:text; }
  .modal .tag-input .tag { display:inline-flex; align-items:center; gap:5px; background:var(--panel); border:1px solid var(--line); border-radius:999px; padding:4px 6px 4px 11px; font-size:13px; }
  .modal .tag-input .tag .tx { color:var(--mut); cursor:pointer; font-size:11px; font-weight:400; }
  .modal .tag-input .tag .tx:hover { color:var(--bad); }
  .modal .tag-input .tag-add { flex:1; min-width:90px; border:none; background:transparent; padding:4px; font-size:13.5px; outline:none; }
  .modal .pchip { font-size:12.5px; padding:6px 11px; border:1px solid var(--line); border-radius:999px; background:var(--panel2); color:var(--mut); cursor:pointer; }
  .modal .pchip.on { background:var(--accent); color:var(--accent-ink); border-color:var(--accent); font-weight:700; }
  .modal .m-actions { display:flex; gap:8px; margin-top:18px; }
  .modal .m-actions .primary { flex:1; }
  .modal .m-msg { margin-top:12px; font-size:13.5px; }
  .modal img.shot-preview { max-width:100%; border-radius:8px; margin-top:8px; border:1px solid var(--line); }
  /* ── onboarding (first-login shopping-modes intro) — additive, scoped under .onb so nothing here
     touches the shared .modal rules other flows (promo/profile) depend on. Reuses .mid-intro's
     accent-bordered gradient card for the hero, .fld-group's accent eyebrow-with-rule for step
     dividers, and .pchip for the book multi-select — same visual language as Profile, not a new
     modal chrome system. */
  .onb-hero { display:flex; gap:12px; align-items:flex-start; }
  .onb-hero .onb-hero-ic { flex:0 0 auto; width:38px; height:38px; border-radius:10px; background:var(--accent-dim); color:var(--accent); display:flex; align-items:center; justify-content:center; }
  .onb-hero h3 { margin:0 0 3px; font-size:17px; }
  .onb-hero .sub { margin:0; }
  .onb-step { margin:16px 0 2px; font-size:12px; font-weight:700; color:var(--accent); text-transform:uppercase; letter-spacing:.5px; border-top:1px solid var(--line); padding-top:14px; display:flex; align-items:center; gap:7px; }
  .onb-step .onb-step-n { display:inline-flex; align-items:center; justify-content:center; width:18px; height:18px; border-radius:50%; background:var(--accent); color:var(--accent-ink); font-size:10.5px; font-weight:800; flex:0 0 auto; }
  .onb-step-sub { color:var(--mut); font-size:13px; margin:4px 0 10px; line-height:1.4; }
  .onb-modes { display:flex; flex-direction:column; gap:8px; }
  .onb-mode { border:1px solid var(--line); border-radius:10px; padding:10px 12px; display:flex; gap:10px; align-items:flex-start; }
  .onb-mode .onb-mode-ic { flex:0 0 auto; margin-top:1px; }
  .onb-mode-name { font-size:12.5px; font-weight:800; letter-spacing:.03em; text-transform:uppercase; display:flex; align-items:center; gap:7px; flex-wrap:wrap; }
  .onb-mode-desc { color:var(--mut); font-size:12.5px; line-height:1.4; margin-top:2px; }
  .onb-mode.rec { border-color:var(--accent); background:var(--accent-faint); }
  .onb-mode.rec .onb-mode-name { color:var(--accent); }
  .onb-mode.avail .onb-mode-name { color:var(--blue); }
  .onb-rec-badge { font-size:9.5px; font-weight:800; letter-spacing:.06em; padding:1px 7px; border-radius:999px; border:1px solid var(--accent); color:var(--accent); background:var(--panel); }
  .onb-footnote { color:var(--mut); font-size:12px; margin-top:10px; line-height:1.4; }
  /* promos: two-group layout + pending strip */
  .promo-group-h { font-weight:700; font-size:14px; margin:16px 2px 6px; }
  .promo-card .shot-thumb { max-height:120px; border-radius:8px; margin-top:8px; border:1px solid var(--line); display:block; cursor:zoom-in; transition:border-color .12s, filter .12s; }
  .promo-card .shot-thumb:hover, .promo-card .shot-thumb:focus-visible { border-color:var(--accent); filter:brightness(1.06); outline:none; }
  .shot-light { position:fixed; inset:0; background:rgba(0,0,0,.85); z-index:80; display:flex; flex-direction:column; align-items:center; justify-content:center; padding:24px 12px; cursor:zoom-out; }
  .shot-light img { max-width:min(920px,96vw); max-height:88vh; border-radius:10px; border:1px solid var(--line); box-shadow:0 12px 48px rgba(0,0,0,.6); cursor:default; }
  .shot-light .shot-cap { color:#eaeaea; font-size:13px; margin-top:12px; max-width:min(920px,96vw); text-align:center; }
  .shot-light .shot-close { position:absolute; top:14px; right:18px; background:none; border:none; color:#fff; font-size:30px; line-height:1; cursor:pointer; padding:4px 10px; }
  .promo-state { font-size:11px; }
  .promo-hold { font-size:12px; margin-top:6px; font-style:italic; }
  /* discovery feed cards — visually distinct from Verified (solid) and user tips (plain) */
  .promo-feed { border-left:3px solid var(--accent); background:linear-gradient(90deg,var(--accent-faint),transparent 60%); }
  /* trust badge is ONE intact pill: inline-flex + nowrap so the ✓ and label never split across a wrap (flagship trust signal, mobile-safe) */
  .promo-src { display:inline-flex; align-items:center; gap:3px; font-size:11px; font-weight:600; padding:1px 8px; border-radius:10px; margin-left:6px; vertical-align:middle; white-space:nowrap; line-height:1.5; }
  .promo-src.verified { color:var(--accent-ink); background:var(--accent); border:1px solid var(--accent); }
  .promo-src.single { color:var(--mut); background:var(--panel2); border:1px solid var(--line); }
  /* "Best use of your boost" — an inline, precomputed shortlist that expands in place on a feed card */
  .best-use { margin:10px 0 2px; border-top:1px solid var(--line); padding-top:8px; }
  .best-use > summary { cursor:pointer; font-size:13px; font-weight:600; color:var(--accent); user-select:none; list-style:none; }
  .best-use > summary::-webkit-details-marker { display:none; }
  .best-use[open] > summary { color:var(--txt); }
  .best-use-h { font-weight:700; font-size:13px; margin:8px 0 6px; letter-spacing:.02em; }
  .best-use-row { padding:7px 0; border-top:1px dashed var(--line); }
  .best-use-row:first-of-type { border-top:none; }
  .best-use-pick { font-size:13px; font-weight:600; line-height:1.35; }
  .best-use-ev { font-size:13px; margin-top:2px; }
  .best-use-ev .n { color:var(--mut); }
  .best-use-ev .b { color:var(--accent); font-weight:700; }
  .best-use-approx { display:inline-block; font-size:10px; font-weight:700; color:var(--mut); background:var(--panel2); border:1px solid var(--line); border-radius:8px; padding:0 6px; margin-left:4px; vertical-align:middle; cursor:help; }
  .best-use-exact { display:inline-block; font-size:10px; font-weight:700; color:var(--accent); background:var(--panel2); border:1px solid var(--line); border-radius:8px; padding:0 6px; margin-left:4px; vertical-align:middle; cursor:help; }
  .best-use-wp { font-size:11px; color:var(--mut); font-weight:600; margin-left:8px; white-space:nowrap; }
  .best-use-why { font-size:12px; color:var(--mut); margin-top:3px; line-height:1.4; }
  .best-use-foot { font-size:11px; color:var(--mut); margin-top:8px; font-style:italic; line-height:1.4; }
  .best-use-empty { font-size:13px; color:var(--mut); margin-top:6px; }
  /* collapsible "More details (optional)" — keeps the fast screenshot path uncluttered */
  .promo-more { margin:12px 0 4px; border-top:1px solid var(--line); padding-top:8px; }
  .promo-more > summary { cursor:pointer; font-size:13px; color:var(--mut); user-select:none; }
  .promo-more[open] > summary { color:var(--txt); font-weight:600; }
  .promo-cta { border-color:var(--accent); }
  .promo-cta-btn { width:100%; font-size:15px; font-weight:700; }
  .promo-cta-why { font-size:13px; margin-top:10px; line-height:1.45; }
  .row-actions { white-space:nowrap; }
  .row-actions button { margin-left:6px; }
  .row-actions button:first-child { margin-left:0; }
  .promo-actions { display:flex; gap:8px; margin-top:10px; }
  .promo-actions button { font-size:12.5px; padding:5px 12px; }
  .btn-approve { background:var(--accent); color:var(--accent-ink); border-color:var(--accent); font-weight:700; }
  .btn-reject { color:var(--bad); border-color:var(--bad); }
  .acct { position:relative; display:inline-block; }
  .avatar { width:32px; height:32px; padding:0; border-radius:50%; background:var(--panel2); color:var(--txt); font-weight:700; font-size:13px; display:inline-flex; align-items:center; justify-content:center; }
  .avatar.admin { box-shadow:0 0 0 2px var(--accent); border-color:var(--accent); }
  .acct-menu { position:absolute; right:0; top:44px; width:min(260px,86vw); background:var(--panel); border:1px solid var(--line); border-radius:12px; box-shadow:0 8px 28px rgba(0,0,0,.5); z-index:40; padding:6px; text-align:left; }
  .acct-id { padding:10px 12px; border-bottom:1px solid var(--line); }
  .acct-id b { font-size:13px; word-break:break-all; }
  .acct-role { color:var(--accent); font-size:11px; text-transform:uppercase; letter-spacing:.6px; margin-top:3px; }
  .acct-item { width:100%; text-align:left; margin-top:6px; background:none; border:none; padding:10px 12px; border-radius:8px; color:var(--txt); }
  .acct-item:hover { background:var(--panel2); }
  .acct-signout { width:100%; text-align:left; margin-top:2px; background:none; border:none; padding:10px 12px; border-radius:8px; }
  .acct-signout:hover { background:var(--panel2); color:var(--bad); }
  /* ---------- HOME (the command center) — built ONLY from the captured brand palette ---------- */
  .home { max-width:1080px; margin:0 auto; padding-bottom:88px; } /* clear the fixed "Ask the Sharp" button */
  .num { font-family:var(--font-num); font-variant-numeric:tabular-nums; font-feature-settings:"tnum" 1; } /* terminal-grade figure alignment */
  /* ── SURVIVOR (SP-130) ── two axes, deliberately DIFFERENT SHAPES so a reader cannot merge two
     adjacent pills into one status. Week type = the loud rounded pill; stability = a small square
     tag that names itself. The original pass invented .chip/.good/.warn/.info, none of which exist,
     so DANGER WEEK rendered identically to PLAY IT SAFE — invisible, not alarmist.
     TA-919 — weekType's own pill is GONE (`.sv-week`/`.sv-week.safe`/`.sv-week.danger` deleted); it now
     renders as the real shared `.conf-chip conf-${tier}` (docs/specs/handicapper/CONVICTION-BADGE-
     SHAPES.md), same pill shape/color every other Analytics tier badge on the site uses, carrying
     Survivor's own honest words (see WEEK_TYPE's own comment in dashboard/index.html for the tier
     mapping and why DANGER_WEEK lands on Lean, never conf-Pass's alarm red). `.sv-stab` KEEPS its own
     small-tag shape (the two-shapes-can't-merge reasoning above still holds) — only its color now comes
     from composing a `conf-${tier}` class (`.sv-stab.fragile`'s own bespoke amber rule is gone, replaced
     by Lean's neutral color), same "shape stays, color borrowed from the shared ladder" pattern
     `.opin-chip` itself already uses. */
  /* TA-919 — no own `color`/`border-color` here on purpose: those now come entirely from whichever
     `conf-${tier}` class is composed alongside this one (declared earlier in this file, lines ~291-294)
     — a later same-specificity rule setting the same property here would silently win and defeat the
     whole point of borrowing the tier color. Pure shape/layout only. */
  .sv-stab { font-size:9.5px; font-weight:800; text-transform:uppercase; letter-spacing:.3px; padding:2px 7px; border-radius:5px; border-width:1px; border-style:solid; white-space:nowrap; }
  .sv-eyebrow { color:var(--mut); font-size:11px; text-transform:uppercase; letter-spacing:1px; font-weight:700; margin-bottom:8px; }
  .sv-card { background:var(--panel); border:1px solid var(--line); border-radius:12px; padding:18px; margin:12px 0; }
  .sv-card.alert { border-color:var(--warn); background:rgba(210,153,34,.07); }
  /* lookahead provenance is STRUCTURAL, not typographic — a bold word inside grey text is not
     "distinguishable at a glance". Dashed rule = not real yet, reusing the .backtest convention. */
  .sv-la { padding:6px 0 6px 12px; border-left:3px solid var(--blue); margin:4px 0; }
  .sv-la.partial { border-left-color:var(--warn); }
  .sv-la.proj { border-left:3px dashed var(--warn); }
  .sv-tag { font-size:9.5px; font-weight:800; text-transform:uppercase; letter-spacing:.4px; padding:1px 6px; border-radius:5px; white-space:nowrap; }
  .sv-tag.market { background:color-mix(in srgb,var(--blue) 14%,transparent); color:var(--blue); }
  .sv-tag.proj   { background:rgba(210,153,34,.14); color:var(--warn); }
  .sv-tag.track  { background:rgba(210,153,34,.14); color:var(--warn); }
  .sv-tag.out    { background:rgba(210,153,34,.14); color:var(--warn); }
  /* a tied GROUP is bracketed and internally unordered — same weight, no ranking cue inside it */
  .sv-tie { border-left:2px solid var(--line); padding-left:8px; }
  .sv-teams td.t { font-weight:700; }
  .sv-teams tr.pick td { background:var(--accent-faint); }
  /* ⚠ THE PAGE MUST NEVER SCROLL SIDEWAYS. At 390px this table forced the body to 430px, and the
     "outside the range we tested" badge — the one caveat a reader needs BEFORE trusting a number —
     was clipped mid-word. Wide content scrolls inside its own box, not by dragging the page.
     David works the Sunday slate from his phone. Found by the UX gate at mobile width. */
  .sv-scroll { overflow-x:auto; -webkit-overflow-scrolling:touch; max-width:100%; }
  .sv-teams { width:100%; border-collapse:collapse; }
  .sv-teams td, .sv-teams th { white-space:nowrap; padding:3px 8px 3px 0; }
  .sv-teams td:last-child, .sv-teams th:last-child { white-space:normal; }
  .home-hero { padding:44px 4px 26px; border-bottom:1px solid var(--line); }
  .home-eyebrow { color:var(--mut); font-size:11px; text-transform:uppercase; letter-spacing:2px; font-weight:700; }
  .home-h1 { font-size:clamp(28px,4vw,40px); font-weight:800; letter-spacing:-.4px; line-height:1.08; margin:12px 0 0; }
  .home-h1 .mkt { color:var(--mut); }
  .home-h1 .mine { color:var(--accent); }
  .home-sub { color:var(--mut); font-size:16px; max-width:660px; margin:14px 0 0; line-height:1.55; }
  .home-idea { color:var(--mut); font-size:13px; line-height:1.55; margin:12px 0 0; max-width:60ch; }
  .home-idea-link { color:var(--accent); font-weight:700; white-space:nowrap; cursor:pointer; display:inline-flex; align-items:center; gap:4px; }
  /* first-run "how this works" banner (localStorage onboardSeen0) */
  .onboard { border:1px solid var(--accent); background:linear-gradient(180deg,var(--accent-dim),transparent); border-radius:12px; padding:14px 16px; margin:0 0 18px; }
  .onboard-h { font-weight:800; font-size:15px; margin-bottom:5px; }
  .onboard-b { color:var(--txt); font-size:13.5px; line-height:1.55; }
  .onboard-a { display:flex; gap:14px; align-items:center; margin-top:11px; flex-wrap:wrap; }
  .onboard-go { color:var(--accent); font-weight:700; font-size:13px; cursor:pointer; display:inline-flex; align-items:center; gap:5px; }
  .onboard-x { font-size:12.5px; padding:6px 12px; }
  .home-pulse { display:inline-flex; align-items:center; gap:8px; margin-top:20px; padding:7px 13px; border:1px solid var(--line);
                border-radius:999px; background:var(--panel); font-size:13px; }
  .home-pulse .dot { width:8px; height:8px; border-radius:50%; box-shadow:0 0 0 0 currentColor; animation:pulse 2.4s infinite; }
  @keyframes pulse { 0%{box-shadow:0 0 0 0 var(--accent-glow)} 70%{box-shadow:0 0 0 7px color-mix(in srgb,var(--accent) 0%,transparent)} 100%{box-shadow:0 0 0 0 color-mix(in srgb,var(--accent) 0%,transparent)} }
  /* ── SP-4 · deadline rail ─────────────────────────────────────────────────────────────────────
     Survivor used to sit at position two in the tab strip because it is a once-a-week, hard-deadline
     decision (SP-3). The grouped nav moves it into a menu, so the promoting job moves HERE: while a
     deadline product is live it gets a row on Home, and the menu is the complete index rather than the
     primary path. Weekly Picks has the same shape and plugs into the same rail. */
  .drail { display:grid; gap:10px; margin:18px 0 4px; }
  .dcard { display:flex; align-items:center; gap:13px; padding:13px 15px; border:1px solid var(--accent);
           border-radius:12px; background:linear-gradient(180deg,var(--accent-dim),transparent); cursor:pointer; }
  .dcard:hover { background:var(--accent-dim); }
  .dcard .d-ic { color:var(--accent); display:inline-flex; flex:0 0 auto; }
  .dcard .d-txt { flex:1 1 auto; min-width:0; }
  .dcard .d-t { font-weight:800; font-size:14.5px; }
  .dcard .d-s { color:var(--mut); font-size:12.5px; margin-top:2px; line-height:1.45; }
  .dcard .d-go { color:var(--accent); font-weight:700; font-size:13px; white-space:nowrap; display:inline-flex; align-items:center; gap:5px; }
  @media (max-width:420px){ .dcard .d-go .d-go-t { display:none; } }
  .tiles { display:grid; grid-template-columns:repeat(4,1fr); gap:12px; margin:24px 0; }
  .tile { background:var(--panel); border:1px solid var(--line); border-radius:12px; padding:16px 18px; }
  .tile .k { color:var(--mut); font-size:11px; text-transform:uppercase; letter-spacing:1px; font-weight:700; }
  .tile .v { font-family:var(--font-num); font-variant-numeric:tabular-nums; font-feature-settings:"tnum" 1; font-size:27px; font-weight:700; margin-top:8px; letter-spacing:0; }
  .tile .s { color:var(--mut); font-size:12.5px; margin-top:3px; }
  .tile .v.edge { color:var(--accent); }
  /* TA-830, 2026-10-22 — .statstrip/.stat removed (David: "I don't really think this entire bar has any
     value to a user"). Left no other caller — confirmed via grep before deleting. If a future surface
     wants this exact tile shape again, it existed here; this isn't a generic pattern worth preserving
     speculatively. */
  @media(max-width:560px){
    /* SP lean home — shrink the mobile hero so Play of the Day sits above the fold (weight stays 800) */
    .home-h1 { font-size:20px; line-height:1.12; }
    .home-hero { padding:24px 4px 16px; }
    .home-sub { font-size:14px; margin-top:10px; }
    /* David's mobile review (2026-10-17, real phone, PR #741) — in the 2x2 grid, a cell whose subtitle
       wrapped to 2-3 lines (Market Data's "each board's own timestamp..." was the worst offender) dragged
       its WHOLE ROW to match that height, making its row-mate (Open Edges/Ripe Now) look oversized with
       empty space while that same row-mate's own short label+value looked "compressed" relative to it —
       his exact description. Capping every stat's subtitle to one line, and trimming the value/padding a
       touch, keeps all 4 cells a uniform, compact height instead of two tall rows pushing Best Angles down.
       Never touches the desktop/tablet grid above 560px. */
    .stat { padding:9px 10px; }
    .stat .k { font-size:9px; }
    .stat .v { font-size:19px; }
    .stat .s { white-space:nowrap; overflow:hidden; text-overflow:ellipsis; }
  }
  .home-sec-h { display:flex; align-items:baseline; justify-content:space-between; margin:30px 0 10px; }
  .home-sec-sub { color:var(--mut); font-size:12.5px; line-height:1.5; margin:-4px 0 10px; }
  .home-sec-h h2 { font-size:15px; font-weight:700; margin:0; }
  .home-sec-h .lnk { color:var(--accent); font-size:13px; font-weight:600; cursor:pointer; background:none; border:none; padding:0; }
  .home-play { display:flex; align-items:center; justify-content:space-between; gap:12px; background:var(--panel); border:1px solid var(--line);
               border-radius:10px; padding:13px 16px; margin:8px 0; }
  .home-play.mine { border-left:3px solid var(--blue); }
  .home-play .p-take { font-weight:700; }
  /* D2 tier ladder (shared voice — see also .potd-prime + .conf-chip): PRIME=gold hero · STRONG=dim green ·
     SOLID=teal outline (TA-734, 2026-10-16 — same fix as .conf-Solid, kept in sync) · LEAN/WATCH=neutral */
  .home-play .p-tierpill { display:inline-block; vertical-align:middle; margin-right:8px; font-size:10px; font-weight:800; letter-spacing:.5px; text-transform:uppercase; padding:3px 8px; border-radius:999px; background:transparent; color:var(--mut); border:1px solid var(--line); white-space:nowrap; }
  .home-play .p-tierpill.t-Prime { background:var(--prime); color:var(--prime-ink); border:0; box-shadow:0 4px 14px -4px var(--prime-glow); }
  .home-play .p-tierpill.t-Strong { background:var(--tier-strong-dim); color:var(--tier-strong); border:1px solid color-mix(in srgb,var(--tier-strong) 45%,transparent); }
  .home-play .p-tierpill.t-Solid { background:transparent; color:var(--tier-strong); border:1px solid color-mix(in srgb,var(--tier-strong) 35%,transparent); }
  .home-play .p-tierpill.t-Lean, .home-play .p-tierpill.t-Watch { background:transparent; color:var(--mut); border:1px solid var(--line); }
  .home-play .p-game { color:var(--mut); font-size:12.5px; margin-top:2px; }
  .home-play .p-edge { text-align:right; white-space:nowrap; }
  .home-play .p-edge .p-pts { color:var(--accent); font-weight:700; font-size:15px; }
  .home-play .p-edge .p-net { color:var(--mut); font-weight:600; font-size:11px; margin-top:3px; }
  .home-play .p-edge .p-net b { color:var(--txt); font-weight:700; }
  /* TA-1136 (Codex review finding, confirmed real) — kickoff time was dropped entirely from the Home
     list row's Tier 1 line during the density pass; the addendum's own ASCII shows it alongside the
     edge badge on the row's right side. Restored here, stacked under the edge metric. */
  .home-play .hp-kickoff { margin-top:4px; }
  /* TA-1136 — Home list Tier 2/3 density pass. Tier 2 (.hp-t2/.hp-cta): matchup + agreement chip + your-
     book star, then the CTA — all always visible, just visually quieter than Tier 1 (.p-take above):
     smaller type, muted color, so the eye lands on the headline first. Tier 3 collapses behind the
     existing .sig-reasoning <details> convention (TA-1035) — never the CTA, per the addendum's explicit
     "CTA stays always-visible" decision. */
  .home-play .hp-t2 { color:var(--mut); font-size:12.5px; margin-top:3px; display:flex; align-items:center; gap:7px; flex-wrap:wrap; }
  .home-play .hp-cta { margin-top:8px; }
  /* TA-1136 CTA-label follow-up (David-approved artifact https://claude.ai/artifact/YEJSML9qe97mgFULshPreZ,
     Decision 1) — "make the CTA look considered, not just present." Verbatim .clean-cta-label treatment
     from that artifact's own mock, ported to this file's real tokens (--smut -> --mut). Only rendered when
     a primary execution button exists (see renderHome's ctaLabelHtml) — never a label pointing at nothing. */
  .home-play .hp-cta-label { font-size:9.5px; font-weight:800; letter-spacing:.6px; text-transform:uppercase; color:var(--mut); margin-bottom:5px; }
  .home-play .hp-cta-row { display:flex; align-items:center; gap:7px; flex-wrap:wrap; }
  .home-play .sig-reasoning { margin-top:6px; }
  .home-play .sig-reasoning .of-mini { color:var(--accent); font-weight:700; font-size:12px; }
  /* TA-1136 — Games grid stacked market strips (card = game, one .mstrip per qualifying market, no tabs —
     the David-approved addendum correction over the first-round tab-per-market mockup). Secondary book
     chips (.exec-sec) stay a plain neutral outline — only the ONE primary .exec-btn above gets the real
     tier color, same split as .ba-bookbtn's own untouched list further down. */
  .mstrips { margin-top:8px; }
  .mstrip { padding:9px 0; border-top:1px solid var(--line); }
  .mstrip:first-child { border-top:0; padding-top:0; }
  .mstrip-top { display:flex; align-items:baseline; justify-content:space-between; gap:10px; flex-wrap:wrap; }
  .mstrip .mlab { font-size:10px; font-weight:800; text-transform:uppercase; letter-spacing:.5px; color:var(--mut); white-space:nowrap; cursor:pointer; }
  .mstrip .mval { font-size:13px; font-weight:700; }
  .mstrip.none .mval { color:var(--mut); font-weight:500; font-size:12px; }
  .mstrip-bet { display:flex; align-items:center; gap:6px; margin-top:7px; flex-wrap:wrap; }
  .exec-sec { display:inline-flex; align-items:center; gap:4px; font-size:11px; font-weight:600; padding:5px 9px; border-radius:7px; border:1px solid var(--line); color:var(--txt); }

  /* ============================================================================================
     TA-1344 — Game-card feed creative-treatment pass, LIVE INTEGRATION (Task 3). Everything below is
     scoped under `.game-card` (the markup root `renderGameCard()` alone emits — no other surface uses
     this class), so none of it reaches Line Shop/My Research/Best Angles, which keep .conf-chip/
     --prime/--tier-strong/--accent exactly as before. Ground truth: the Manager-approved round-2/3
     static prototype, dashboard/prototype-cardfeed-v2-round2.html — markup/class names below are ported
     from it directly, not reinvented. Desktop (>=961px) gets the new full-width row-grid board; at
     <=960px the SAME markup collapses to a single stacked column (the "existing mobile pattern" the
     ticket explicitly says to reuse rather than rebuild) via one grid-template-columns swap — one DOM
     tree, no duplicate render path. ============================================================== */

  /* ---- Typography ladder — 3 weights only (round-2 spec §F). Design Lead fix (2026-11-14, round 1):
     these 3 classes had ZERO real CSS rules anywhere in this file — every call site set font-size/
     weight entirely via scattered inline `style=` attributes, which is exactly how the multi-market
     sub-block's recommendation line silently lost its bold weight (no base rule to fall back to when
     an inline style omitted font-weight). These base rules are the real fallback now; a call site may
     still override font-size inline for a specific layout need (e.g. the secondary-market strip's
     smaller 14px recommendation line), but it can no longer silently drop below 800/700/500 weight by
     omission. */
  .game-card .tf-primary{font-weight:800;color:var(--txt)}
  .game-card .tf-secondary{font-weight:700;color:var(--txt)}
  .game-card .tf-tertiary{font-weight:500;color:var(--mut)}
  .game-card .tf-tertiary b{color:var(--txt);font-weight:500}
  /* TA-1372 round 3 fix #2 (real type-scale jump) — this used to be an inline `font-size:17px` tacked
     onto `.tf-primary` at the call site (dashboard/index.html), 17px vs. the matchup team name's
     13.5px (`.gc2-matchup .gc2-team span`) and tertiary's ~12-12.5px (`.our-take`, `.gc2-reasoning-body`,
     `.stat-cell.fairline/.winprob .stat-value`) — a real but modest delta the independent review still
     read as "everything is mid-size... no real size jumps." Pulled into its own named class (so this is
     unambiguously THE primary headline slot, not something that only reads as bold-but-not-bigger) and
     bumped to 19px — a true ~40% jump over the 13.5px secondary tier, not a few-point nudge. */
  .game-card .gc2-rec-line{font-size:19px;font-weight:800;color:var(--txt);line-height:1.25;margin-top:2px}

  /* ---- Tier pill — color (loud only Prime/Strong) + non-color ordinal pip + word. Single markup for
     both card-level (pips shown) and book-level (pips always hidden via .book-level — the enforcement
     mechanism, not a convention, so a future call site can't silently reintroduce the ambiguous-badge
     defect round 2 fixed). Prime reuses --prime/--prime-ink verbatim (identical gold already in this
     file); Strong/Pass use the new TA-1344-scoped tokens defined in :root above. */
  .game-card .tier-pill{display:inline-flex;align-items:center;gap:5px;border-radius:999px;padding:3px 9px;font-size:11px;font-weight:800;letter-spacing:.3px;white-space:nowrap}
  /* TA-1375 round-2 design-polish fix (Grok/GPT-5.1 independent review, 2026-11-15, finding #2) — the
     18%-tint fill below (TA-1375 §1's original pass) was tuned to let the new left-edge bar carry the
     loud tier signal, with the pill demoted to "quiet confirmation." Both independent reviews read the
     result the opposite way at real scan speed: the bar alone can't carry Prime-vs-Strong on its own
     (it's the same 4px width/shape either color), and the pip dots are identical shapes too — color is
     doing 100% of the differentiation work across two separate thin elements, neither of which reads as
     "a badge" on its own. Fix: the headline tier pill itself gets a real, bounded badge treatment —
     bumped size/padding, a solid-color border at ~55% strength, and a richer ~28% fill (up from 18%) —
     so it's legible as a distinct, named badge at a glance, with the bar and pips staying as secondary
     reinforcement rather than the primary carriers. Still zero box-shadow/blur/glow anywhere (the
     standing no-glow rule is untouched) — this is a flat, bordered, filled shape, not a bloom. */
  .game-card .tier-pill.tier-Prime,
  .game-card .tier-pill.tier-Strong{
    padding:4px 11px;
    font-size:12px;
    letter-spacing:.4px;
  }
  .game-card .tier-pill.tier-Prime{background:color-mix(in srgb, var(--prime) 28%, var(--panel));color:var(--prime);border:1.5px solid color-mix(in srgb, var(--prime) 55%, transparent)}
  .game-card .tier-pill.tier-Prime .tier-word{color:var(--prime)}
  .game-card .tier-pill.tier-Strong{background:color-mix(in srgb, var(--gc2-strong-bg) 28%, var(--panel));color:var(--gc2-strong-bg);border:1.5px solid color-mix(in srgb, var(--gc2-strong-bg) 55%, transparent)}
  .game-card .tier-pill.tier-Strong .tier-word{color:var(--gc2-strong-bg)}
  /* David, live review 2026-11-16 — "I'm seeing solid as a white outline. That should be a green outline
     but not filled in, just like what we had before." Was var(--mut) (the same neutral gray Lean uses) —
     the exact "Strong/Solid look the same at a glance" complaint this round is fixing. Now the SAME green
     hue as Strong, still outline-only/transparent (never filled — that's what separates it from Strong). */
  .game-card .tier-pill.tier-Solid{background:transparent;border:1.5px solid var(--gc2-strong-bg);color:var(--gc2-strong-bg)}
  .game-card .tier-pill.tier-Lean{background:transparent;border:1.5px dotted var(--mut);color:var(--mut);opacity:.9}
  .game-card .tier-pill.tier-Pass{background:var(--gc2-pass-bg);color:var(--gc2-pass-fg);border:1px solid var(--gc2-pass-line)}
  /* TA-1375 round-6 fix #1 (David, live review — "the book badges have no outline, color or
     distinguishing features"). Round-2/3 demoted these to thin, low-opacity outlines specifically so
     they wouldn't compete with the card-level headline pill (see the struck-through reasoning below,
     kept for history) — live on a real card, that read as plain text, not a badge. Reversed per David's
     direct instruction, confirmed against the reference image (`Desktop/Angle Concept 2`): every
     book-level tag there is a real, solid-filled, full-opacity badge. Re-filled here at FULL opacity,
     but still kept at book scale (9.5px vs. the headline pill's 12px, tighter padding, pill-radius
     instead of the headline's bigger footprint) so the two stay visually distinct by SIZE even though
     both are now filled — the real mechanism this round uses instead of opacity to keep the headline
     pill the loudest element on the card. */
  /* David, live review 2026-11-16 — "can we make every badge for strong/solid/pass... the same size so
     it's a consistent look all the way down?" Natural text width varies by word length (STRONG=6 chars
     measures ~61px at this scale, PASS=4 chars only ~44px), so badges were visibly different widths down
     the book list. `min-width` set to the longest real word's measured width (STRONG, rounded up) plus
     `justify-content:center` (the base `.tier-pill` is already `display:inline-flex`) so every shorter
     word centers within the SAME fixed-width pill instead of hugging its own tighter content box. */
  .game-card .tier-pill.book-level{font-size:9.5px;padding:2px 8px;opacity:1;font-weight:800;min-width:64px;justify-content:center}
  /* Book-level Pass — solid red fill. Word shortened from "BELOW TIER" to "PASS" (index.html,
     David live review 2026-11-16) so this badge's width matches the other 4-5 char tier words instead
     of visibly stretching wider than PRIME/SOLID/STRONG/LEAN; color/fill treatment unchanged. */
  .game-card .tier-pill.tier-Pass.book-level{background:var(--bad);border:1px solid var(--bad);color:#2a0b0b;opacity:1}
  /* Struck-through history (round-2/3, superseded by round-6 fix #1 above): Prime/Strong book-level
     badges used to be outline-only transparent chips (`background:transparent;border:1px solid
     var(--prime|--gc2-strong-bg);color:var(--prime|--gc2-strong-bg)`), demoted from a full solid fill to
     avoid competing with the card-level headline pill. David's live review called this out as reading
     like plain text with no real distinction — reverted to a solid fill, size-demotion (above) now does
     the "stay secondary" job instead of opacity/outline-only.
     David, live review 2026-11-16 — round-6's fix above went too far the OTHER way for Solid/Lean: Strong,
     Solid, and Lean all rendered as the SAME solid-green-filled chip, with zero distinction between them
     ("we've gotten away from our differentiation between strong, solid, and lean"). Split back out: Strong
     stays the real solid fill (it earned that reversal — Prime/Strong are this product's two loud tiers),
     Solid goes back to outline-only but in the SAME green hue as Strong (not Prime/Strong's old shared
     "outline-only, barely distinguishable" treatment that round-6 was originally reacting to — just Solid,
     on its own), and Lean is its own neutral gray/white outline. Three visually distinct book-level
     treatments now: Prime/Strong filled (gold/green), Solid a green outline, Lean a gray outline. */
  .game-card .tier-pill.tier-Prime.book-level{background:var(--prime);border:1px solid var(--prime);color:var(--prime-ink)}
  .game-card .tier-pill.tier-Strong.book-level{background:var(--gc2-strong-bg);border:1px solid var(--gc2-strong-bg);color:var(--gc2-strong-ink)}
  .game-card .tier-pill.tier-Solid.book-level{background:transparent;border:1px solid var(--gc2-strong-bg);color:var(--gc2-strong-bg)}
  .game-card .tier-pill.tier-Lean.book-level{background:transparent;border:1px solid var(--mut);color:var(--mut)}
  /* Live-review catch — `.tier-pill.tier-Prime .tier-word{color:var(--prime)}` and `.tier-Strong
     .tier-word{color:var(--gc2-strong-bg)}` (above) exist for the card-level pill's tinted-fill
     treatment, where the word needs the full-saturation color over a pale background. Those rules'
     selectors also match the book-level pill (same classes), and `color` doesn't inherit through an
     explicit override — so a book-level Prime/Strong chip rendered its tier word in the SAME color as its
     own solid fill, i.e. invisible text on a same-color badge. Confirmed live (DraftKings/FanDuel "STRONG"
     chip rendering as a blank green pill). Re-asserted here, after the book-level fill rules, so the ink
     color wins for the FILLED book-level case specifically. Solid/Lean.book-level are intentionally NOT
     listed here (2026-11-16 change, above): they're outline-only now, not filled, so `.tier-word` just
     inherits the pill's own `color` naturally — forcing ink-color here would make their text invisible
     against the dark card background instead of the pill's own outline color. */
  .game-card .tier-pill.tier-Prime.book-level .tier-word{color:var(--prime-ink)}
  .game-card .tier-pill.tier-Strong.book-level .tier-word{color:var(--gc2-strong-ink)}
  .game-card .gc2-headline-tier{display:inline-flex}
  /* zero per-card TIER-COLORED glow, any tier, including Prime (David + CD + independent GPT-5.1 consult,
     unanimous) — this card's own box-shadow/halo application is removed below (.game-card .halo-frame),
     and the new .tier-pill never adds one; --prime-glow itself stays defined/used elsewhere (.conf-Prime/
     .exec-Prime, Line Shop/Best Angles — untouched, out of this ticket's scope). TA-1375 §5 adds a
     separate, flat-TONE (never tier-colored) depth shadow to the row itself (`.play.game-card.gc2-row`,
     below) — a deliberate, approved departure from the zero-shadow-of-any-kind state this comment used to
     describe; the zero-GLOW rule here is specifically about tier-colored bloom, which stays zero. */
  .game-card.gc2-row .halo-frame{box-shadow:none !important}
  /* TA-1375 §1 — left-edge 4px tier bar, Prime/Strong only (Solid/Lean/Pass/No-Plays get no bar at all —
     absence of a bar IS the signal). Flush to the row's left inner edge, inset by the row's own 8px
     corner radius (top:8px;bottom:8px — see §5 below for that same 8px value) so the bar never clips into
     two nubs at the rounded corners. Zero box-shadow/blur on the bar itself — it's a crisp, deterministic
     mark, not a glow. */
  .game-card.gc2-row.tier-bar-Prime::before,
  .game-card.gc2-row.tier-bar-Strong::before{
    content:"";
    position:absolute;
    left:0; top:8px; bottom:8px;
    width:4px;
    border-radius:2px;
  }
  .game-card.gc2-row.tier-bar-Prime::before{ background:var(--prime); }
  .game-card.gc2-row.tier-bar-Strong::before{ background:var(--gc2-strong-bg); }

  /* ---- Opinion capsule — purple exclusively (reuses --handicap/--handicap-dim verbatim — the one color
     this redesign never touches). 4-state vocabulary mapped onto the real same-side/different-side/
     toss-up/no-read comparison agreementChipPairHtml() already computes (see opcapHtml() in
     dashboard/index.html). TA-1394/TA-1396 (David, live review 2026-11-15/16) — this used to be its own
     full-height 4th grid column on the far right (round 2-10 of TA-1375); confirmed live via screenshot
     that it was visibly stretching to the card's full height and sticking out from the rest of the card's
     content, disproportionate to what's actually inside it (a verdict + one short sentence, now that
     TA-1396 fixed the reasoning line to always show something real and short instead of being omitted).
     Now nests inside `.gc2-col-matchup`, directly under the team names, as a normal, content-sized block
     — most of the height-stretch/vertical-centering CSS this section used to carry (to counteract filling
     a tall standalone column) is gone below; what's left is just the panel's own look (fill/border/text
     treatment), not its positioning. */
  /* TA-1372 round 3 fix #3 (loudness) — font-weight 700->600: this pill should read as a real but
     QUIET signal, never competing with the 3 elements this round deliberately keeps loud (headline
     tier pill / recommendation line / primary action button). Color/shape/position are unchanged —
     this is weight only, legibility untouched. */
  /* TA-1375 round-2 design-polish fix (Grok/GPT-5.1 independent review, 2026-11-15, finding #1 — "the
     single biggest miss"). Both independent reviews converged on the same root cause: this capsule was
     a small pill ("a status dot") plus a separate gray subtitle line sitting above the matchup like
     metadata, never a visually-bounded container someone would read as "this is our angle in one
     sentence." The fix is structural, not cosmetic: the verdict pill and its reasoning sentence now live
     INSIDE one real, filled/bordered purple panel (`.opcap-panel`) sized and weighted to read as a hero
     element — the loudest thing on the card after the recommendation line itself, not an aside next to
     it. `.opcap`/`.opcap-wrap`/`.opcap-reason` class names are kept exactly as named (test/ta-1375-
     opinion-excerpt-staleness.test.mjs asserts the literal `class="opcap-reason"` string) — only their
     container and sizing change. */
  .game-card .opcap-panel{display:flex;flex-direction:column;gap:4px;padding:9px 14px;border-radius:10px;width:100%;box-sizing:border-box}
  /* TA-1375 round-6 fix #5 (David, live review against the reference image at `Desktop/Angle Concept 2`)
     — the 22%-tint fill read as a pale hint of purple, not the reference's solid, deeply saturated block.
     Bumped the mix to 82% (a real solid fill, not a glow — still zero box-shadow/blur anywhere on this
     panel) and the border to full-strength `--handicap`. Verdict/label/reasoning text inside a LIVE panel
     switch to white/near-white (below) for contrast against the now much darker fill — the "purple-on-
     purple" read David called out. The "No Opinion" neutral panel (below) is untouched. */
  .game-card .opcap-panel.opcap-panel-live{background:color-mix(in srgb, var(--handicap) 82%, var(--panel));border:1px solid var(--handicap)}
  .game-card .opcap-panel-label{font-size:9.5px;font-weight:800;letter-spacing:.5px;text-transform:uppercase;color:var(--handicap)}
  /* round-6 fix #5, cont'd — on the now-solid purple fill, the label/verdict/reasoning all move to
     white/near-white so they read as confident foreground text, not a dim hue-on-hue blend. */
  .game-card .opcap-panel.opcap-panel-live .opcap-panel-label{color:#fff;opacity:.82}
  .game-card .opcap-panel.opcap-panel-live .opcap{color:#fff}
  .game-card .opcap-panel.opcap-panel-live .opcap-reason{color:rgba(255,255,255,.92)}
  .game-card .opcap{display:inline-flex;align-items:center;gap:6px;font-size:14px;font-weight:800;color:var(--handicap);white-space:nowrap}
  /* TA-1375 round-7/9 fix (David, live review). Deliberately DIFFERENT, smaller shape than a real
     opinion's filled `.opcap-panel`: no panel background/border/border-radius, just a thin 2px left
     accent rule and a genuine small header above the honest "No independent opinion yet" note — reads as
     an intentional empty state, not missing/broken content. TA-1394/TA-1396 simplification: this no
     longer needs to counteract a stretched full-column height (it was never a `.opcap-panel` to begin
     with, so the old stretch/centering concern this comment used to describe never actually applied to
     it) — straightforward top-aligned two-line block, natural height. */
  .game-card .opcap-none{display:flex;flex-direction:column;justify-content:flex-start;gap:3px;padding:2px 0 2px 10px;border-left:2px solid var(--line)}
  .game-card .opcap-none-label{font-size:9.5px;font-weight:800;letter-spacing:.5px;text-transform:uppercase;color:var(--mut);white-space:nowrap}
  .game-card .opcap-none-text{font-size:11.5px;font-weight:500;font-style:italic;color:var(--mut)}
  /* TA-1372 round 3 fix #1 (predictable position) — the Opinion capsule used to be absolutely positioned
     INSIDE `.gc2-opn`, so its on-screen position drifted row to row with however tall the surrounding
     content happened to be. TA-1394/TA-1396 (David, live review 2026-11-15/16): it now nests inside
     `.gc2-col-matchup`, directly under the team names — a fixed, predictable position by construction
     (every card's matchup column has the same shape), no longer needing its own dedicated full-width grid
     row/column to pin it in place. Cards with no opinion to show (the No-Plays state) simply render no
     element here — it collapses to 0 height, no placeholder needed. */
  .game-card .gc2-opcap-row{display:block;margin-top:4px}
  .game-card .gc2-opcap-row:empty{display:none;margin-top:0}
  .game-card .opcap-wrap{display:flex;flex-direction:column;gap:4px}
  /* TA-1396 — `nowrap`/`overflow:hidden` assumed the old 52-char hard cap (anything longer was omitted
     entirely, never reaching this rule). gc2ShortReasoningLine() now produces a real sentence up to ~90
     chars (plus ellipsis if trimmed), which can run past one line's width even in the now-wider matchup
     column (see .gc2-col-matchup below) — wrap normally instead of silently clipping real text. */
  .game-card .opcap-reason{font-size:12.5px;font-weight:500;color:var(--txt);white-space:normal;max-width:100%;line-height:1.3}

  /* ---- Stat cluster — EDGE (own exclusive accent, never varies by sign) / FAIR LINE / WIN PROB (both
     neutral). Replaces the old "Edge vs. sharp line:" sentence as the stat-cluster for THIS card only;
     sharpLineCompareHtml()'s own function/output is untouched for any other caller. */
  /* TA-1372 Design Lead round 2 (2026-11-14, gap #4) — margins nudged up a touch (5px/3px -> 7px/5px
     here; stat-cluster/our-take/books/actions/badge-row below) so the card's own internal rhythm reads
     as intentional breathing room rather than compressed/spreadsheet-like, without materially growing
     the row-height budget this scan-board is built around (a few px per gap, not a redesign). */
  .game-card .stat-cluster{display:flex;gap:16px;margin:7px 0 5px;flex-wrap:wrap;align-items:flex-end}
  /* TA-1375 round-4 fix #2 — EDGE's own line, rendered directly under `.gc2-rec-line` by
     gc2StatClusterHtml(), instead of inside the flat 3-cell `.stat-cluster` row. Tight top margin so it
     visually attaches to the pick line above it; a touch more bottom margin than the secondary row gets
     top margin, so EDGE still reads as its own beat before the smaller supporting stats. */
  .game-card .gc2-edge-line{margin:2px 0 3px}
  /* The demoted FAIR LINE/WIN PROB row — same `.stat-cluster` flex row as before, just without EDGE in
     it and with a tighter top margin (it's now visually subordinate to EDGE immediately above, not a
     peer row starting fresh). */
  .game-card .stat-cluster.stat-cluster-secondary{margin:0 0 5px}
  .game-card .stat-cell{display:flex;flex-direction:column;gap:1px}
  .game-card .stat-label{font-size:9.5px;font-weight:800;letter-spacing:.5px;text-transform:uppercase;color:var(--mut)}
  /* TA-1375 round-2 design-polish fix (Grok/GPT-5.1 independent review, 2026-11-15, finding #5) —
     EDGE is the actual product/thesis of the card (the real number this whole system exists to
     surface), but at 13px/700 it read as a small caption indistinguishable in weight from a
     three-stat row of equally-sized numbers. Bumped to a real size jump (now 21px/800, up again from
     round-2's 18px per round-3 finding #2 below — still the same discipline as `.gc2-rec-line`'s own
     size-jump fix) so it reads as the second-loudest number on the card after the recommendation line —
     Fair Line/Win Prob stay small/neutral/subordinate, exactly as before, so the contrast is real, not
     just EDGE growing while everything grows with it.
     TA-1375 round-3 fix (both independent reviews, 2026-11-15, finding #2 this round) — color changed
     from the removed `--edge-accent` (a stray pale-cyan hue, never part of this card's established
     gold/green/purple/teal palette — it had only moved here from the date pill, not been eliminated) to
     `--gc2-strong-bg`, the SAME established green this card already uses for a positive/strong signal
     (tier-Strong pill, left-edge bar). Size also bumped 18px->21px in the same pass, since both reviews
     agreed the round-2 bump was still underpowered relative to EDGE's weight as the card's actual thesis
     stat, relative to Fair Line/Win Prob's unchanged 11.5px/500.
     TA-1375 round-5 fix (UX Reviewer, confirmed live against a real Prime-tier game — Wake Forest @ SMU/
     Michigan @ Oregon/Ole Miss @ Oklahoma) — round-3's green was never actually neutral: it directly
     reused `--gc2-strong-bg`, the SAME token the Strong-tier pill/left-edge bar use, so on a PRIME-tier
     card (gold pill, gold left bar per Item 1) EDGE still rendered green underneath it — two tier colors
     fighting on one card, and a direct violation of round 2 §3's own explicit guardrail ("never the tier
     colors... never a size/weight that rivals .tf-primary" — EDGE borrowing Strong's own green IS a tier
     color). Every round tonight happened to test against a Strong-tier fixture, so this never surfaced
     until a real Prime card was clicked through live. Fixed by making EDGE genuinely neutral: `var(--txt)`,
     the SAME token `.gc2-rec-line` (the recommendation headline) already uses — same color FAMILY as the
     pick line, tier-independent, no new hue. The 21px/800 size bump from round 4 is unchanged and is now
     the only thing carrying EDGE's visual emphasis, exactly as the UX Reviewer specified. The "EDGE"
     caption itself is no longer overridden at all — it falls back to the same base `.stat-label{color:
     var(--mut)}` rule every other stat caption (FAIR LINE, WIN PROB) already uses, so the three captions
     read as one consistent muted label row and only the big EDGE number itself carries the emphasis. */
  /* TA-1375 round-6 fix #6 — EDGE now reads `--edge-value` (a new, dedicated, non-tier-aliased green
     token defined in :root above), not `--txt`. Verified live against both a Prime card (Wake Forest @
     SMU) and a Strong card (William & Mary @ FAU): EDGE renders the same green on both, matching the
     reference, with no clash against either tier's own gold/green pill. */
  .game-card .stat-cell.edge .stat-value{font-size:21px;font-weight:800;color:var(--edge-value);line-height:1.1}
  .game-card .stat-cell.fairline .stat-value,.game-card .stat-cell.winprob .stat-value{font-size:11.5px;font-weight:500;color:var(--mut)}

  /* ---- Our Take — tertiary, 2-line clamp, never mid-word ellipsis (round-3 fix #2: a single-line
     nowrap+ellipsis used to clip every sentence mid-word). */
  .game-card .our-take{display:-webkit-box;-webkit-line-clamp:2;-webkit-box-orient:vertical;overflow:hidden;text-overflow:ellipsis;max-width:100%;margin-top:3px;color:var(--mut);font-size:12.5px;line-height:1.4}

  /* ---- Team logos — light neutral backdrop chip so a dark team mark stays visible against the dark
     card (round-3 fix #5); onerror fallback to a colored-initials badge is built client-side, see
     teamLogoHtml() in dashboard/index.html.
     TA-1375 round-6 fix #2 (David, live review — "the helmets are barely visible and mis-aligned").
     Two real issues, fixed independently:
     (a) Size — 20px (16px of actual mark once the 2px padding is subtracted) was too small to read at a
     glance. Bumped to 28px (24px of actual mark), a real, visible jump, not a 2-3px nudge.
     (b) Alignment — `.gc2-matchup` used to be ONE flex ROW holding away-team/`@`/home-team as three
     siblings with `flex-wrap:wrap`; whichever child wrapped first (usually `@`) could land the home
     team's logo+name on a visually different line/height than the away team's, with no shared left
     edge between them. Switched to a flex COLUMN instead: away team, `@`, and home team each now get
     their own full-width row, left-aligned, so both logos sit at the exact same x position and each
     logo is vertically centered against only its OWN team-name line (`.gc2-team`'s own
     `align-items:center`) — never against the other team's line. No markup change needed; the existing
     3 siblings (`.gc2-team`, `.gc2-at`, `.gc2-team`) simply stack now instead of flowing inline. */
  .game-card .gc2-team{display:inline-flex;align-items:center;gap:7px;min-width:0}
  .game-card .gc2-team img{width:28px;height:28px;border-radius:6px;object-fit:contain;background:#E4E8ED;padding:2px;box-sizing:border-box;flex:0 0 auto}
  /* TA-1372 Task 12 (§A5 Bug 1, root cause B) — explicit margin-right directly on the fallback badge
     itself, cascade-independent of the parent .gc2-team's own gap rule ever changing. Confirmed live
     ("SMGSouthern Mississippi..." concatenation, zero separator) the parent gap alone was not reliably
     separating this badge from the adjacent team-name span; this guarantees spacing regardless of
     parent flex rules, for every future school this table never acquires a logo for too. */
  .game-card .gc2-team-fallback{display:inline-flex;align-items:center;justify-content:center;width:28px;height:28px;border-radius:5px;background:var(--panel2);color:var(--mut);font-size:10px;font-weight:800;flex:0 0 auto;margin-right:6px}
  /* David, live review 2026-11-15/16 — on mobile the "@" (centered via `.gc2-at{align-self:center}`
     below) rendered noticeably right-shifted, away from the actual team-name text, while desktop looked
     correctly centered. Root cause: there was never a real desktop/mobile rule difference here — this
     flex column (a plain block box) stretched to its PARENT's full width at every size, and `align-self:
     center` centers against that stretched box's cross-axis, not against the team names' own rendered
     width. On desktop the parent is the narrow ~220px matchup column, so the stretched width happens to
     stay close to the text's own width and the bug was invisible; on mobile `.gc2-col-matchup` spans the
     full card width, so centering against that much wider box visibly misses the actual text. `width:
     fit-content` shrinks this box to its own content's width (still wrapping long matchups via the
     team-name spans' own `overflow-wrap`, capped by `max-width:100%` so it still respects the column on
     desktop) — centering the "@" now means centering against the team names themselves, correctly, at
     every width. */
  .game-card .gc2-matchup{display:flex;flex-direction:column;align-items:flex-start;gap:4px;width:fit-content;max-width:100%}
  .game-card .gc2-matchup .gc2-team span{font-size:13.5px;font-weight:700;line-height:1.25;color:var(--txt);white-space:normal;overflow:visible;text-overflow:unset;word-break:normal;overflow-wrap:break-word}
  .game-card .gc2-at{color:var(--mut);font-size:12px;font-weight:500;flex:0 0 auto;align-self:center;margin-left:2px}

  /* ---- Book row — single row, book-brand accent swatch (color only, never logo art), 3-book cap +
     honest "+N more" affordance (opens the SAME disclosure the multi-market/reasoning content lives
     in), BEST badge small/monochrome/outline only (never gold/any tier color). */
  /* TA-1375 round-7 fix #2 (David, live review — "the Books column needs the work, with nothing
     separating or distinguishing each book badge"). `.gc2-bookrow` used to be a `flex-wrap` bag of
     individually-bordered chips — at this column's real narrow width the chips stack one per line
     anyway, but each chip's own border is `var(--line)` (#26323f) against a `var(--panel2)` (#1c2632)
     background, a ~2% luminance step that's effectively invisible at normal viewing distance (confirmed
     live). Replaced with an explicit, deliberate list: `.gc2-bookrow` is now the ONE bordered/rounded
     container, and each `.gc2-bchip` row inside it gets a real `border-bottom` divider (never on the
     last row) — a visible, intentional line between every book, not a chip border that happens to be
     nearly invisible against its own neighbor. Stacked with `flex-direction:column` explicitly (not
     relying on wrap to stack them) so this is deterministic at any column width, not a side-effect of
     the column currently being narrow. */
  .game-card .gc2-bookrow{display:flex;flex-direction:column;margin:9px 0 5px;border:1px solid var(--line);border-radius:9px;overflow:hidden;background:var(--panel2)}
  /* TA-1375 round-3 fix — the books column got narrower now that it shares a single desktop row with 4
     other real zones (fix #1, below). A single book chip's content (swatch + name + price + the
     book-level tier badge + BEST, all `white-space` default/nowrap-by-content) doesn't shrink below its
     own min-content width, and this list has no `overflow:hidden` on individual chip CONTENT anywhere
     (deliberately — clipping would hide real data, the one thing this card's own standing rules never
     allow) — `flex-wrap:wrap` on the chip itself lets its content break onto a 2nd internal line instead
     of overflowing sideways — same "wrap, never truncate or clip" discipline this card's own matchup
     column already uses for long team names.
     TA-1375 round-7 fix #3 — the chip's own two children (`.gc2-bchip-main`, `.gc2-bchip-badges`, below)
     are the fixed-slot mechanism for badge consistency; `justify-content:space-between` pins badges to
     the row's right edge regardless of how much room the name/price take on the left. */
  /* David, live review 2026-11-16 — "why is there a blue line under FanDuel and DraftKings stuff and on
     the tier badge that accompanies them?" Root cause: `.gc2-bchip` renders as a real `<a>` (the book's
     own deep link), and the browser's default `text-decoration:underline`/link-blue `color` on an anchor
     paints its decoration line across the FULL inline content of everything inside it — book name, price,
     AND the tier badge — even though each of those already sets its own distinct, non-blue color
     (`.gc2-bname`/`.gc2-bprice`/the tier-pill's own color all computed correctly; only the stray
     underline, drawn in the anchor's own blue, was bleeding through). Reset here, same convention this
     file's own `.ba-bookbtn`/`.cta`/`.exec-btn` book-link buttons already use (`text-decoration:none` at
     the anchor itself) — this app never underlines a book-link button at rest. */
  .game-card .gc2-bchip{display:flex;flex-wrap:wrap;justify-content:space-between;max-width:100%;box-sizing:border-box;align-items:center;gap:6px;row-gap:4px;padding:7px 10px;border:0;background:transparent;min-width:0;font-size:11.5px;text-decoration:none;color:inherit}
  /* Live-review catch (round 7) — the FIRST pass at this divider used `var(--line)` (#26323f) against
     the row's own `var(--panel2)` (#1c2632) background, the exact ~2% luminance step that made the old
     per-chip borders invisible in the first place (see the comment above `.gc2-bookrow`) — reused the
     wrong token right after diagnosing why it was wrong. A real divider needs real contrast against its
     own background, not the ambient border color used for quiet chrome elsewhere on the card; a
     semi-transparent white line reads as a deliberate rule at this dark background regardless of the
     underlying panel token. Alternating row tint (nth-child even) is the second, independent cue, so the
     separation survives even if a viewer's display crushes the thin divider line. */
  .game-card .gc2-bookrow .gc2-bchip:not(:last-child){border-bottom:1px solid rgba(255,255,255,.22)}
  .game-card .gc2-bookrow .gc2-bchip:nth-child(even){background:rgba(255,255,255,.06)}
  /* Fixed-order slot groups (round-7 fix #3) — see gc2BookChipHtml() in dashboard/index.html. Every row
     renders both groups in this same order: identity (swatch/name/price/stale) on the left, then the
     tier-qualification badge's own slot, then the BEST flag's own slot — never positioned relative to
     which of those happens to be present on a given row. */
  .game-card .gc2-bchip-main{display:flex;align-items:center;gap:6px;min-width:0;flex:1 1 auto}
  .game-card .gc2-bchip-badges{display:flex;align-items:center;gap:5px;flex:0 0 auto}
  .game-card .gc2-bchip .gc2-swatch{width:7px;height:7px;border-radius:50%;flex:0 0 auto}
  /* TA-1372 round 3 fix #3 (loudness) — 700->600: the book-name chip read nearly as bold as the
     recommendation headline itself, competing for attention in a 3-4-book row. Still clearly legible,
     no longer peer-weight with the one thing on the card meant to read loudest. */
  .game-card .gc2-bchip .gc2-bname{font-weight:600;color:var(--txt);white-space:nowrap}
  .game-card .gc2-bchip .gc2-bprice{color:var(--mut);font-variant-numeric:tabular-nums;white-space:nowrap}
  .game-card .gc2-bchip.gc2-stale{opacity:.62}
  .game-card .gc2-bchip .gc2-stale-flag{font-size:9.5px;color:var(--warn);font-weight:700;margin-left:1px}
  .game-card .gc2-more-note{font-size:11px;color:var(--mut)}
  /* TA-1375 round-8 Fix 3 — `.gc2-more-note` now also doubles as a `<summary>` for the inline
     "+N more books" expander (see bs.moreNote in index.html). `list-style:none`/`::-webkit-details-
     marker{display:none}` strip the browser's own default disclosure triangle so this reads as the
     same quiet muted-text affordance it always was, just now clickable; the real books list it reveals
     reuses `.gc2-bookrow` verbatim (margin-top only, so it doesn't collide with the visible 3 above it). */
  .game-card .gc2-more-books{margin-top:2px}
  .game-card .gc2-more-books > summary{cursor:pointer;list-style:none}
  .game-card .gc2-more-books > summary::-webkit-details-marker{display:none}
  .game-card .gc2-more-books > summary:hover{color:var(--txt)}
  .game-card .gc2-more-books .gc2-more-books-list{margin-top:6px}
  /* TA-1375 round-6 fix #1, cont'd — BEST used to be monochrome grey outline text (round-2 §4 item 4's
     original "never gold, never any tier color" caution was aimed at avoiding confusion with the
     Prime headline pill). David's live review + the reference image both show a real gold-filled BEST
     chip; it reads unambiguously as "which price" (small, at the book row, word "BEST" not "PRIME") and
     is never adjacent to the headline pill, so the confusion risk that caution was guarding against
     doesn't apply here. Filled solid gold, same `--prime`/`--prime-ink` pair the headline pill itself
     uses, at the same tight book-badge scale as the tier chips above.
     David, live review 2026-11-16 — BEST now renders FIRST in `.gc2-bchip-badges` (index.html), so its
     own `margin-left` no longer sits between it and the tier badge (which it was tuned for) — it would
     instead add an uneven extra gap between it and `.gc2-bchip-main`, on top of the parent's own
     `gap:5px`. Dropped; the parent's gap already spaces every badge consistently regardless of order. */
  .game-card .gc2-best-badge{font-size:8.5px;font-weight:800;letter-spacing:.3px;color:var(--prime-ink);background:var(--prime);border:1px solid var(--prime);border-radius:4px;padding:1px 5px}

  /* ---- Second-market disclosure toggle + sub-block (TA-1344 addendum) — neutral/muted chrome, NEVER
     purple (purple is .opcap-exclusive). Reuses the real .mstrip-top/.tier-pill/.opcap shapes verbatim
     for the second market's own strip — no new shape invented.
     Design Lead fix (TA-1372, 2026-11-14, round 2, gap #2) — this was a bordered/background-filled chip,
     the same pill-adjacent shape family as the real tier/status badges, for what is just a "more exists,
     tap to see it" nudge. Demoted to a plain text+chevron link (same voice as "Compare to market · full
     detail ›" below it) — no background, no border, no radius. */
  .game-card .gc2-more-market-chip{display:inline-flex;align-items:center;gap:2px;font-size:11px;font-weight:700;color:var(--mut);background:transparent;border:0;border-radius:0;padding:0;margin-left:8px}
  .game-card .gc2-more-market-chip:hover{color:var(--txt)}
  .game-card .gc2-secondary-market{margin-top:10px;padding-top:10px;border-top:1px dashed var(--line)}
  .game-card .gc2-secondary-market-label{font-size:11px;letter-spacing:.2px;margin-bottom:6px;color:var(--mut)}

  /* ---- Analysis & Reasoning disclosure — reuses the native <details>/<summary> convention this app
     already relies on for a11y (TA-1299/round-1 decision, carried forward unchanged). */
  .game-card .gc2-disclosure{margin-top:6px}
  .game-card .gc2-disclosure summary{cursor:pointer;font-size:12px;color:var(--mut);font-weight:700;list-style:none}
  .game-card .gc2-disclosure summary::-webkit-details-marker{display:none}
  .game-card .gc2-disclosure summary::before{content:"\25B8\0020";color:var(--mut)}
  .game-card .gc2-disclosure[open] summary::before{content:"\25BE\0020"}
  .game-card .gc2-disclosure .gc2-inner{margin-top:8px;padding-top:8px;border-top:1px solid var(--line);font-size:12px;color:var(--mut)}
  /* round-7 fix #2's `.gc2-extra-books` rule is GONE as of round-8 Fix 3 — the "+N more books" list no
     longer renders inside this disclosure at all; it's inline in the books column now (`.gc2-more-books`,
     above), which reuses `.gc2-bookrow` directly rather than a disclosure-scoped duplicate selector. */
  /* TA-1375 round-6 fix #4 — demoted weight for a disclosure with nothing substantive behind it (see
     `gc2HasRealContent` in dashboard/index.html): smaller, more muted toggle text and a tighter chevron,
     so a card with only the honest "no write-up yet"/"no qualified play" nudges reads as quiet chrome,
     not a promise of real content. Never collapsed/hidden — still one tap away, same as every other
     card; this changes visual weight only. */
  .game-card .gc2-disclosure.gc2-disclosure-quiet summary{font-size:10.5px;font-weight:500;opacity:.68}
  .game-card .gc2-disclosure.gc2-disclosure-quiet summary::before{opacity:.7}

  /* TA-1372 Task 10 — distinct, labeled sub-sections inside the SAME disclosure (General/1st-Half
     Totals/Props real write-ups; Moneyline/Market/Recommendation's own honest no-opinion copy).
     `[data-gc2-section]` is the badge-click retarget anchor (Task 11) — never a new disclosure. */
  .game-card .gc2-reasoning-section{margin-bottom:10px}
  .game-card .gc2-reasoning-section:last-child{margin-bottom:0}
  .game-card .gc2-reasoning-label{font-size:10px;font-weight:800;letter-spacing:.4px;text-transform:uppercase;color:var(--txt);margin-bottom:3px}
  .game-card .gc2-reasoning-body{font-size:12.5px;color:var(--mut);line-height:1.4}

  /* ---- Actions — teal/cyan exclusive to interactive controls on THIS card, once tier fully vacates it
     (tier here uses gold/green/grey/red, never teal — see .tier-pill above). Line Shop/My Research/Best
     Angles keep betControl()'s shared --accent-green styling unchanged; these rules are scoped under
     .game-card so nothing bleeds. */
  .game-card.gc2-row .betmini.betadd{color:var(--action-teal);border-color:var(--action-teal)}
  .game-card.gc2-row .betmini.betadd:hover{background:var(--action-teal-dim);color:var(--action-teal);border-color:var(--action-teal)}
  .game-card.gc2-row .betbtn-exec{background:var(--action-teal);color:#06211d;border-color:var(--action-teal)}
  /* Design Lead fix (TA-1372, 2026-11-14) — root cause confirmed: .betbtn-exec's BASE rule
     (width:100%;min-height:44px;font-size:13px — styles.<hash>.css, the TA-341 sportsbook-execution-module
     rule) was built for that module's own vertical tile layout and was never overridden for this dense
     row-grid card. The gc2-row color override two lines up only ever touched color/background/border —
     it silently inherited the full-width/44px-tall sizing too, making the logging button visually dominate
     everything on the card including the Recommendation headline it's supposed to defer to. Resized here
     to a real, findable action proportionate to its neighbors — same rectangular shape family as Check/
     +Parlay/+Teaser (`.betmini`, 11px/padding:2px 6px), just a clear primary-action step up from them, not
     a hero CTA. The already-correct `.beton{border-radius:999px}` shape-change-on-placed rule (below) is
     unaffected — this only resizes the UNPLACED rectangular button. */
  /* TA-1375 round-2 design-polish fix (Grok/GPT-5.1 independent review, 2026-11-15, finding #4) — the
     first pass (padding:7px 16px;font-size:12.5px;font-weight:800;max-width:150px, below-superseded)
     was still roughly double its real peers (.betmini/.betmini.betadd: 11px, 2px vertical padding) in
     both height and weight, and the 150px cap — tight for the full "I placed this bet" label at that
     type scale — forced the label's own TEXT to wrap internally ("I placed this / bet") at a real 390px
     mobile width, confirmed against the live screenshot. Brought down to the SAME font-size/vertical-
     padding scale as Check/+Parlay/+Teaser so it reads as a genuine peer, not a scaled-down hero button;
     `white-space:nowrap` means a width-constrained row wraps the WHOLE pill onto its own flex line
     (`.betwrap` already sets `flex-wrap:wrap`) instead of breaking the label mid-sentence. The label
     text itself stays the shared "I placed this bet" default (TA-341's own naming — "unmistakably the
     LOGGING control, never confusable with BET") — not shortened, since this card never shows it
     alongside a second, differently-worded log CTA, so there's no risk of two different wordings
     competing on the same card; shape (rectangle pre-placed, pill once logged via .beton) and color
     remain the state signal exactly as already decided. */
  .game-card.gc2-row .betbtn-exec{width:auto;min-height:0;padding:3px 10px;font-size:11px;font-weight:700;white-space:nowrap}
  .game-card.gc2-row .betbtn-exec{max-width:160px}
  /* The exec button no longer fills its own line, so the centering hack built for the old full-width
     button (`.betwrap:has(.betbtn-exec){text-align:center}`, styles.<hash>.css ~:1759) would now center a
     normal-width button + its mini-row inside the action area instead of left-aligning with every other
     element on the card — overridden back to a left-aligned, wrapping flex row, matching the round-2
     spec's own `.actions` layout intent (Check/+Parlay/+Teaser/bet-button as one left-aligned group). */
  .game-card.gc2-row .betwrap{display:flex;align-items:center;flex-wrap:wrap;gap:4px;text-align:left}
  .game-card.gc2-row .betwrap.on{justify-content:flex-start}
  /* TA-1375 round-6 fix #3 (David, live review — "the Check / Parlay / Teaser buttons wrap versus on
     the same line"). Root cause: `.betwrap`'s 4 children (the log control, then Check/+Parlay/+Teaser)
     are plain flex siblings with `flex-wrap:wrap` — by design, so the log control can drop to its own
     line when it doesn't fit (it's first in DOM and the widest item). That's working as intended; the
     actual bug is that Check/+Parlay/+Teaser themselves, as a group, were too wide to share even a
     SECOND line together inside the narrow actions column, so one of them (usually +Teaser) wrapped a
     3rd time on its own. Fixed two ways together: the actions column itself is wider now (135px->160px,
     see `.gc2-content`'s `grid-template-columns` above), and these 3 peer buttons are shrunk further
     here (11px/padding:2px 6px -> 10px/padding:2px 5px, tighter 4px icon gap) so their combined width
     reliably fits one shared line within the wider column — verified live against a real card with all
     3 visible plus the log button. `flex-shrink:0` stops them from being squeezed/overlapping instead of
     wrapping cleanly if a future column resize ever gets tight again; `.betwrap`'s own `overflow-x:auto`
     (scrollbar hidden) is the explicit last-resort safety net for a genuinely extreme case (a very long
     disabled-state title attribute changing nothing here, or a future 4th mini-button) — it only ever
     engages if the row truly can't fit, never visible as a scrollbar in the normal case. */
  .game-card.gc2-row .betwrap{overflow-x:auto;scrollbar-width:none;-ms-overflow-style:none}
  .game-card.gc2-row .betwrap::-webkit-scrollbar{display:none}
  /* Live-measured (real card, Wake Forest @ SMU): at the previous 5px padding/6px gap this sum was
     164px against a 160px column — JUST over, which is exactly why +Teaser alone kept wrapping to its
     own 3rd line while Check+Parlay shared one. Tightened again (4px padding, 4px betwrap gap above,
     2px icon-to-text gap) to a measured ~140-148px total, with real margin this time, not a near-miss. */
  .game-card.gc2-row .betwrap .betmini:not(.betbtn-exec){font-size:10px;padding:2px 4px;gap:2px;flex-shrink:0;white-space:nowrap}
  .game-card.gc2-row .beton{color:var(--action-teal);background:var(--action-teal-dim);border-color:var(--action-teal)}
  /* round-2 defect-fix #5, CORRECTED (Manager, 2026-11-14 — reverts this file's own first pass, which
     wrongly hid Check/+Parlay/+Teaser in the placed state): ONLY the 4th slot (the logging control
     itself) swaps shape — `.beton` ("You're on this" + edit/unbet) renders as a full rounded status
     pill, same filled-teal family, visually distinct from the unplaced rectangular "I placed this bet"
     button. Check/+Parlay/+Teaser are NEVER hidden, placed or not — TA-1317's own fix (David: "members
     should always be able to evaluate or place a bet... don't keep finding new ways to restrict that")
     is non-negotiable and applies on this card exactly as everywhere else. betControl() itself is
     untouched (TA-1317's regression test, test/ta-1317-logged-action-row.test.mjs, stays green). */
  .game-card.gc2-row .beton{border-radius:999px}

  /* ============================================================================================
     DESKTOP ROW-GRID BOARD (round-2 spec §2) — full-width, single-column, aligned-row-per-game board;
     `.game-card-grid--all` switches from the old auto-fit tile grid to a plain block list at >=961px
     (see rule below), with kickoff in its own slim left column and everything else (matchup/opinion/
     tier/recommendation/stats/books/actions/disclosure) stacked in one content column — same reading
     order top-to-bottom as mobile, just arranged left-to-right at the outermost level, per CD's "same
     reading order both platforms, different layout" rule. At <=960px the SAME .game-card markup
     collapses to a single stacked column — the "existing mobile pattern" the ticket explicitly says to
     reuse, never a second render path or a rebuilt mobile structure.

     TA-1372 Design Lead round 2 (2026-11-14) — the round-1 fix above wrapped every row in ONE shared
     panel with hairline dividers ("the row IS the unit, never a boxed per-row card," per the original
     round-2 spec). The Manager's own re-review against David's reference image, plus an independent
     GPT-5.1 visual check, found that approach still reads as a single undifferentiated column at a
     glance — rows never register as distinct, bounded units the way this app's own base `.play` card
     (line ~264) already does for every OTHER surface, including this same card on mobile. Reverting to
     that proven per-row-bounded-card model here too, just with a real, visible contrast step
     (--gc2-card-bg/--gc2-card-border, defined in :root above — a deliberate step up from --panel/
     --line, not another 1-2% nudge) and real margin between rows so the page background visibly shows
     through. Zero TIER-COLORED box-shadow/glow anywhere in this pair — contrast + border + radius +
     spacing only, per the explicit standing no-glow instruction (TA-1344's own twice-independently-
     validated rule). TA-1375 §5 — a real, deliberate, approved departure from round 2's flat-row rule:
     8px radius (was 14px), a restrained flat-TONE depth shadow (never tier-colored, never a glow), and a
     tighter 8px gap between rows (margin-bottom only, same pattern as before — just a smaller number).
     TA-1375 §4 — min-height is now content-driven by tier (qualified Prime/Strong/Solid/Lean rows get a
     spacious 132px; everything else, including No-Plays, gets a compact 96px) instead of one flat number
     — applies at BOTH widths now (previously desktop-only; see the deleted `@media(min-width:961px)`
     override below), since mobile had no min-height rule here at all before this ticket. */
  .game-card.gc2-row{
    display:flex;
    flex-direction:column;
    gap:10px;
    position:relative;
    min-height:96px; /* No-Plays / unqualified default, both widths */
  }
  .game-card.gc2-row.tier-bar-Prime,
  .game-card.gc2-row.tier-bar-Strong,
  .game-card.gc2-row:has(.tier-pill.tier-Solid),
  .game-card.gc2-row:has(.tier-pill.tier-Lean){
    min-height:132px; /* qualified rows — Prime/Strong get the bar too (above); Solid/Lean don't, but are still "qualified" */
  }
  .play.game-card.gc2-row{
    background:var(--gc2-card-bg);
    border:1px solid var(--gc2-card-border);
    border-radius:8px;
    padding:16px 18px;
    margin:0 0 8px;
    box-shadow:0 1px 3px rgba(0,0,0,.3);
  }
  .game-card-grid--all:has(.gc2-row) .play.game-card.gc2-row:last-child{ margin-bottom:0; }
  /* TA-1372 round 3 fix #1 (real column grid) — the independent review's specific finding: "pills,
     buttons, and text don't share clear vertical columns... micro-offsets where pills sit 2-4px higher/
     lower than neighbors." Root cause confirmed live: at >=961px this card was `display:flex;
     flex-direction:row` with exactly TWO flex children (`.gc2-kick` at a fixed 108px, then one single
     `.gc2-content` flex-auto blob) — matchup/opinion/stats/books/actions were all just vertically
     stacked INSIDE that one content blob, never actual sibling columns, so nothing enforced a shared X
     position for any of them across different rows. `.gc2-content` is now a real CSS grid with 4 FIXED
     column tracks (matchup | opinion+tier+rec | books | actions) plus a 5th full-width row underneath
     for supplementary content (badge row / disclosure / CTA) — every row.gc2-row on the board shares
     the identical `grid-template-columns`, so a column's start/width never depends on that row's own
     content (a short vs. long team name, a 2-book vs. 4-book row, the No-Plays state all use the exact
     same 4 tracks; empty cells just render empty, they don't collapse or shift neighbors). Kickoff
     (league badge + date) moves inside the matchup column, stacked above the team names, matching the
     "League/time+matchup" grouping the review called for — it is no longer a separate 5th column. */
  @media (min-width:961px){
    /* TA-1344 rollout flag (migration 096) — `.gc2-row` only ever exists on a card from a member with
       `games_card_v2_enabled:true` (see renderGameCard()'s own flag check). Scoping every rule below to
       `:has(.gc2-row)` means a member whose flag is OFF (everyone, by default) gets the EXACT same
       auto-fit tile grid as today, unchanged — this media query only ever fires for a flagged-in
       member's own grid. Grid is a MIX of flagged/unflagged cards only in the impossible case where the
       same wrapper renders entries for two different members, which never happens (one member per page
       load) — safe by construction, not just by convention. */
    .game-card-grid--all:has(.gc2-row){ display:block !important; background:transparent; border:0; border-radius:0; overflow:visible; }
    .play.game-card.gc2-row{ padding:18px 22px; margin:0 0 8px; }
    /* TA-1394/TA-1396 (David, live review 2026-11-15/16) — REPLACES round-8's 4-column grid (matchup |
       opinion | booksactions | opcap) with a 3-column grid: matchup (now also carries the Research
       Opinion capsule, folded in under the team names) | opinion(tier+pick+EDGE) | booksactions. David's
       direct feedback: "that section could actually move over to the left underneath the teams so that
       you actually only have three columns. You could make each column even wider... it doesn't seem
       like we need the right-hand research opinion column to be so tall if we're limited on how much
       copy we can actually have in that location" — confirmed live via screenshot that the old opcap
       column was visibly stretching to the card's full height, disproportionate to a verdict + one short
       sentence. The ~260px+16px gap the opcap column+gutter used to claim is redistributed: matchup
       170px->220px (room for the team names AND the now-compact opinion pill under them), opinion stays
       the flexible middle track (minmax bumped 170->200 for a bit more breathing room), booksactions
       300px->340px. Mobile (<=960px) is untouched by this desktop-only grid change. */
    .game-card.gc2-row .gc2-content{
      display:grid;
      grid-template-columns: 220px minmax(200px,1fr) 340px;
      column-gap:16px;
      /* TA-1375 round-9 Fix 1 — the old 2nd "extra extra extra extra" row (spanning all columns) is gone:
         `.gc2-extra` is no longer its own grid row at all, it's now packed inside the SAME "opinion" cell
         as `.gc2-opn` via the `.gc2-opn-stack` wrapper (see that selector below) — this is what actually
         closes the gap, not a sizing tweak on the old 2-row layout (any fix that kept opn/extra as
         separately-sized grid tracks would still leave real browsers free to grow the SHORTER track
         instead of the one below it, reopening the same gap). */
      grid-template-areas: "matchup  opinion  booksactions";
      align-items:start;
    }
    .game-card.gc2-row .gc2-col-matchup{ grid-area:matchup; }
    /* TA-1375 round-9 Fix 1 — replaces the old `.gc2-opn{grid-area:opinion}` single-cell rule. The stack
       packs `.gc2-opn` (tier/pick/EDGE/stat cluster) directly above `.gc2-extra` (badge row + Analysis &
       Reasoning + "Compare to market" link), `justify-content:flex-start` (the real mechanism, even
       though it's also flexbox's default — stated explicitly per spec) so the two never get artificial
       space forced between them. `align-items:stretch` (flexbox's own default for a column container —
       left un-overridden deliberately) is what keeps `.gc2-opn`/`.gc2-extra` filling the opinion column's
       full width, matching their old behavior as independent grid-area children; `align-items:flex-start`
       was considered but rejected — it would shrink both to their own content width instead of the
       column's measured width, breaking the badge row's wrap behavior and the rec-line's layout. The
       actual "no bottom-anchoring" fix is one level up: this whole stack is a single grid item placed by
       `grid-area:opinion` inside a grid whose `align-items:start` (above) already keeps grid ITEMS from
       stretching to the row's full height — so when `.gc2-booksactions` (or any other column) is taller,
       the leftover space falls below this whole stack as plain card background, never a gap splitting the
       stat cluster from the badge row/disclosure/CTA underneath it. */
    .game-card.gc2-row .gc2-opn-stack{
      grid-area:opinion;
      display:flex;
      flex-direction:column;
      justify-content:flex-start;
      gap:8px;
      min-width:0;
    }
    /* The shared books+actions column — a real bordered surface (same --panel/--line treatment the
       book list already used individually) so the merge reads as one deliberate container, not books
       and actions just happening to share a grid cell. Books keep their own existing `.gc2-bookrow`
       border (round 2's book-list treatment, unchanged) nested one level in; the divider between the
       book list and the actions row is a plain top border on `.gc2-actions` itself — no new markup. */
    .game-card.gc2-row .gc2-booksactions{
      grid-area:booksactions;
      display:flex;
      flex-direction:column;
      border:1px solid var(--line);
      border-radius:10px;
      background:var(--panel);
      padding:10px;
    }
    .game-card.gc2-row .gc2-booksactions .gc2-books{ margin-top:0; }
    .game-card.gc2-row .gc2-booksactions .gc2-actions{
      margin-top:10px;
      padding-top:10px;
      border-top:1px solid var(--line);
    }
    /* TA-1375 round-9 Fix 1 — `.gc2-extra{grid-area:extra}` removed: `.gc2-extra` is no longer its own
       grid cell, it's packed inside `.gc2-opn-stack` (grid-area:opinion, above) alongside `.gc2-opn`. */
    /* TA-1394/TA-1396 — `.gc2-opcap-row` is no longer a grid-area column of its own (removed: the old
       `grid-area:opcap`/`align-self:stretch`/`align-items:stretch` rules that used to force it to fill a
       full-height standalone track). It now lives inside `.gc2-col-matchup`'s normal flex-column flow
       (that column's own `gap:6px`, below, already spaces it correctly under the team title) — no
       desktop-specific positioning rule needed here at all any more. The matchup column is also wider now
       (220px, up from 170px) specifically to give the opinion capsule's text real room without a special
       smaller font size override — `.opcap-reason` uses its one shared base size (styles.<hash>.css,
       ~line 2696) at every width. */
  }
  /* TA-1375 round-2 design-polish fix (Grok/GPT-5.1 independent review, 2026-11-15, finding #6) — the
     global `.datechip` rule (styles.<hash>.css ~:1120) uses `--blue` (#58a6ff), a 5th hue outside this
     card's own gold/green/purple/teal palette. `.datechip` is a shared, site-wide component (dateChip()
     is called from many surfaces, not just this card — confirmed by grep before touching anything), so
     the fix is scoped to `.gc2-row` only, never a global recolor. Recolored to neutral (the same
     --panel2/--mut/--line triple every other quiet chrome element on this card already uses, e.g.
     `.gc2-bchip`) rather than reusing gold/green/purple/teal, since none of those four carries "this is
     just the date" as a meaning — a neutral chip is the honest choice, not a 5th color standing in for
     a signal that doesn't exist. The LIVE/in-progress state (`style="color:var(--warn)"` inline) is
     untouched — that's a real, loud, inline-applied state, not part of this stray-hue finding. */
  .game-card.gc2-row .datechip{background:var(--panel2);color:var(--mut);border-color:var(--line)}
  .game-card .gc2-kick{display:flex;flex-direction:column;gap:6px}
  .game-card .gc2-content{min-width:0;display:flex;flex-direction:column;gap:10px}
  .game-card .gc2-col-matchup{min-width:0;display:flex;flex-direction:column;gap:6px}
  .game-card .gc2-opn{min-width:0}
  .game-card .gc2-books{min-width:0;margin-top:6px}
  .game-card .gc2-actions{display:flex;align-items:flex-start;margin-top:10px}
  /* TA-1375 round-8 Fix 1 — the new shared books+actions wrapper (see `.gc2-content`'s 3-column
     grid-template-areas at >=961px below: matchup | opinion | booksactions). On mobile this
     wrapper must contribute NOTHING to layout — `.gc2-books`/`.gc2-actions` keep rendering as plain
     stacked flex children of `.gc2-content`, byte-identical to before this ticket (`display:contents`
     removes the wrapper itself from the box tree, leaving only its two real children in flow). Only the
     >=961px rule below turns it back into a real, bordered box. */
  .game-card .gc2-booksactions{display:contents}
  /* TA-1375 round-6 fix #4 — tightened 8px->6px, one of several small height trims this round makes
     across the "bottom half" (badge row / disclosure toggle / CTA) rather than one big restructure. */
  .game-card .gc2-extra{min-width:0;display:flex;flex-direction:column;gap:6px}
  /* TA-1375 round-9 Fix 1 — `.gc2-opn-stack` wraps `.gc2-opn` + `.gc2-extra` as one grid cell at >=961px
     (see the media query below) so they pack together with zero injected space between them, instead of
     being two independently-sized grid rows. `display:contents` here keeps the wrapper invisible at
     every width below that — `.gc2-opn`/`.gc2-extra` stay direct flex children of `.gc2-content`, exactly
     as before this round, same mechanism `.gc2-booksactions` already uses just above. Mobile's visual
     order is restored explicitly below (`order`), since `.gc2-extra` now sits earlier in the DOM (right
     after `.gc2-opn`, inside the shared wrapper) but must still render LAST on a stacked mobile card. */
  .game-card .gc2-opn-stack{display:contents}
  /* TA-1394/TA-1396 — `.gc2-opcap-row{order:2}` removed: it's no longer a direct sibling of
     `.gc2-content` (nested inside `.gc2-col-matchup` now), so an `order` value on it here would be
     meaningless — its position falls out of plain DOM order inside that column instead, every width. */
  .game-card .gc2-col-matchup{order:0}
  .game-card .gc2-opn{order:1}
  .game-card .gc2-books{order:3}
  .game-card .gc2-actions{order:4}
  .game-card .gc2-extra{order:5}

  /* TA-1372 Task 5 — generalized market badge row (up to 5 badges: Spread/Rec, Moneyline, 1st-Half,
     Props, Market). Real-qualifying badges reuse the real .tier-pill color/pip system at reduced badge
     scale (same discipline as the book-level badge treatment above); "no read" badges render visually
     inert — muted/outline, no pointer cursor, aria-disabled — matching the existing .mstrip.none tone,
     never a dead click styled to look live. */
  .game-card .gc2-badge-row{display:flex;flex-wrap:wrap;gap:6px;margin-top:6px}
  /* Design Lead fix (TA-1372, 2026-11-14) — this rule's own comment claimed "reduced badge scale, same
     discipline as the book-level badge treatment" (round-2 spec §1c's `.tier-pill.book-level`: 9.5px,
     opacity:.85) but the shipped values (10.5px/padding:3px 9px, full opacity) never actually applied that
     demotion — they land within half a point of the HEADLINE tier pill itself (11px/800), so the compact
     market-badge summary row visually competed with the one element meant to be loudest on the card. Sized
     down to actually match the book-level badge's own already-approved scale/opacity, restoring "badges =
     a quiet directory into the disclosure, tier pill = the verdict." */
  .game-card .gc2-badge{display:inline-flex;align-items:center;gap:4px;border-radius:999px;padding:2px 8px;font-size:9.5px;font-weight:800;letter-spacing:.2px;white-space:nowrap;border:1px solid var(--line);background:transparent;color:var(--mut);cursor:pointer;opacity:.85}
  .game-card .gc2-badge:hover{border-color:var(--mut)}
  /* TA-1375 round-6 fix #4 (David, live review — "a whole bunch of big empty blank boxes"). A "no read"
     badge used to keep the SAME bordered-pill shape as a real, clickable, qualifying badge — just
     dimmer (opacity:.55) — so a row with 2-3 inert markets next to 1 real one still read as a row of
     several equal-weight boxes, most of them empty. Dropped the border/pill shape entirely for the
     inert case: no border, no background, tighter padding — it reads as a plain muted label (what it
     actually is, "nothing here yet"), not a dead box standing shoulder-to-shoulder with a real badge.
     The one real, qualifying badge nearby keeps its full pill treatment unchanged, so it's now the only
     thing in the row that looks like a clickable chip — exactly the contrast this fix is after. */
  .game-card .gc2-badge[aria-disabled="true"]{cursor:default;opacity:.55;border-color:transparent;background:transparent;padding:2px 2px}
  .game-card .gc2-badge[aria-disabled="true"]:hover{border-color:transparent}
  /* Design Lead fix (TA-1372, 2026-11-14, round 2, gap #2) — Prime/Strong badges here still rendered as
     FULL solid-fill/full-opacity chips (background:var(--prime), opacity:1) — identical color treatment
     to the card-level headline tier pill, just a couple points smaller. Full-saturation color reads as
     "loud" regardless of font-size, so this badge row kept competing with the one element meant to be
     unambiguously loudest on the card. Demoted to the SAME outline-only treatment Solid/Lean already use
     here (color-only accent, no fill) — tier color is still legible (gold/green vs neutral), but only the
     real headline tier pill ever gets the solid fill. */
  .game-card .gc2-badge.gc2-badge-Prime{background:transparent;color:var(--prime);border-color:var(--prime)}
  .game-card .gc2-badge.gc2-badge-Strong{background:transparent;color:var(--gc2-strong-bg);border-color:var(--gc2-strong-bg)}
  .game-card .gc2-badge.gc2-badge-Solid,.game-card .gc2-badge.gc2-badge-Lean{border-color:var(--mut);color:var(--mut)}
  /* David, live review 2026-11-16 — 1st-Half's qualified state (a real boolean lean/no-lean, no tier
     gradient of its own) used to style itself inline with `--accent` (a duller teal-green), visually
     weaker than Spread/Rec/Props' tier-colored badges next to it in the same row. Reuses the SAME
     brighter green `.gc2-badge-Strong` already uses for "a real, positive signal" — the honest nearest
     equivalent, since 1st-Half has no Prime/Strong/Solid/Lean ladder of its own to color by. */
  .game-card .gc2-badge.gc2-badge-qualified{background:transparent;color:var(--gc2-strong-bg);border-color:var(--gc2-strong-bg)}

  /* TA-1372 Task 4/13 — "NO PLAYS" headline state (the shared gc2-opn slot, populated honestly instead
     of staying silently empty). Same tier-pill/tertiary-line/badge-row/actions/CTA shell every has-a-
     pick card uses — this rule only tunes the dense, No-Plays-majority collapsed-row reading per the
     addendum's §A5 Bug 2 layout pass (a 40-55-row CFB Saturday slate is mostly this state). */
  .game-card .gc2-noplay-line{margin-top:4px;font-size:12px;color:var(--mut)}
  /* TA-1375 §4 — No-Plays rows now fall through to the SAME compact 96px default every unqualified row
     gets (see `.game-card.gc2-row`'s own min-height above) — no separate override needed, and no
     separate desktop-only number either (the old 64px desktop-only value predated the tier-conditional
     system and is superseded by it, both widths). */
  /* David's own narrow-width requirement (TA-1136 §D) — the Tier-1 edge badge/take line and the strip's
     top row must never wrap mid-badge or overflow at a real narrow width (~375px); flex-wrap above
     already lets the edge badge/mval drop to its own line instead of clipping, same simple mechanism
     every other wrap-prone row on this page already uses (.ba-books, .busy-books, etc. — no new tab-
     strip-specific breakpoint is needed since there is no tab strip left to scroll horizontally). */
  @media (max-width:420px) {
    .home-play { flex-direction:column; align-items:stretch; }
    .home-play .p-edge { text-align:left; margin-top:4px; }
    .mstrip-top { flex-direction:column; align-items:flex-start; gap:2px; }
    /* TA-1315 follow-up — SUPERSEDED same night by the corrected fix (see `.game-card .top` /
       `.game-card-headrow`, styles.<hash>.css near line 268): that first pass stacked the date chip
       below the WHOLE left block (badge + title), the wrong shape per David's reference mockup, and
       was keyed to this viewport breakpoint rather than the card's own width — so a narrow grid COLUMN
       on a wide (non-mobile) browser triggered the same squeeze. The corrected fix is a constant,
       always-on two-row structure with no viewport media query at all, so there is nothing left to
       stack here — this rule is intentionally removed, not merely edited, to avoid the two fixes ever
       running at once. */
  }
  .potd-wrap { margin-top:6px; }
  /* SP lean home — collapsed Play-of-the-Day bar (default state for signed-in members; expands in place). Reuses .potd-prime tier pills + @keyframes pulse. */
  .potd-bar { width:100%; display:flex; align-items:center; gap:10px; text-align:left; border:1px solid var(--accent); border-radius:12px; padding:12px 14px; background:linear-gradient(180deg,var(--accent-faint),transparent); cursor:pointer; }
  .potd-bar-txt { flex:1 1 auto; min-width:0; white-space:nowrap; overflow:hidden; text-overflow:ellipsis; font-size:14px; }
  .potd-bar-edge { color:var(--accent); font-weight:700; }
  .potd-bar-cta { flex:0 0 auto; color:var(--accent); font-weight:700; font-size:13px; }
  .potd-bar-dot { flex:0 0 auto; width:8px; height:8px; border-radius:50%; background:var(--accent); animation:pulse 2.4s infinite; }
  /* TA-795 follow-up — collapsed POTD bar's opposite-side-bet presence flag. Static (no pulse — this
     isn't a "new" cue), warn-toned to match oppositeSideBetNote()'s own full-card styling. */
  .potd-bar-oppflag { flex:0 0 auto; color:var(--warn); display:flex; align-items:center; }
  .potd-bar-check { flex:0 0 auto; color:var(--accent); font-weight:800; }
  .potd-collapse { flex:0 0 auto; background:none; border:0; color:var(--mut); font-size:21px; line-height:1; cursor:pointer; padding:2px 8px; }
  /* David's mobile review (2026-10-17, real phone, PR #741) — "Angle of the Day truncated so the actual
     selection isn't visible." .potd-bar-txt's single-line nowrap+ellipsis cut the pick's own team/number
     off entirely at phone widths, well before anyone could read it. This is the top-priority content on
     the page (his own words), so the fix widens its budget rather than shrinking it further: drop the
     "tap to open" wording earlier (was 380px, now 480px — covers the common 390-430px phone range) and
     let the pick text wrap up to 2 lines instead of ellipsis-truncating to one. Height stays bounded
     (line-clamp, not unlimited wrap) so the bar can't balloon, but the actual selection is now always
     readable. Desktop/tablet (>480px) is completely unchanged. */
  @media(max-width:480px){
    .potd-bar .cta-txt { display:none; }
    .potd-bar-txt { white-space:normal; display:-webkit-box; -webkit-line-clamp:2; -webkit-box-orient:vertical; overflow:hidden; text-overflow:unset; }
  }
  .potd-reveal { width:100%; padding:16px; border:1px dashed var(--accent); border-radius:14px; background:linear-gradient(180deg,var(--accent-faint),transparent); color:var(--accent); font-weight:700; font-size:15px; cursor:pointer; letter-spacing:.2px; }
  .potd-reveal:hover { background:linear-gradient(180deg,var(--accent-dim),transparent); }
  .potd-card { border:1px solid var(--accent); border-radius:14px; padding:16px 18px; background:linear-gradient(180deg,var(--accent-faint),transparent); }
  .potd-card.none { border-color:var(--line); color:var(--mut); background:var(--panel); font-size:14px; line-height:1.6; }
  .potd-tag { display:inline-block; font-size:11px; font-weight:700; text-transform:uppercase; letter-spacing:.6px; color:var(--accent); margin-bottom:6px; }
  .potd-tag.thin { color:var(--warn); }
  .potd-take { font-size:19px; font-weight:800; line-height:1.25; }
  .potd-game { color:var(--mut); font-size:13px; margin-top:3px; }
  .potd-edge { color:var(--accent); font-weight:700; font-size:15px; margin-top:8px; }
  .potd-why { font-size:12.5px; line-height:1.6; margin-top:8px; }
  /* SP-30 conviction card — centered marquee, prominent unlock reveal, gap strip, book rows. Design+UX gated. */
  .potd-h { flex-direction:column; align-items:center; text-align:center; gap:2px; margin:34px 0 12px; }
  .potd-h h2 { justify-content:center; }
  .potd-h .potd-sub { color:var(--mut); font-size:12.5px; }
  .potd-reveal { position:relative; overflow:hidden; padding:30px 22px; border:1.5px dashed var(--accent); border-radius:16px; text-align:center; transition:transform .15s ease, border-color .15s ease, box-shadow .15s ease; }
  .potd-reveal::before { content:""; position:absolute; inset:-45% -12%; z-index:0; pointer-events:none;
    background:radial-gradient(closest-side, var(--accent-glow), transparent 70%); opacity:.5; animation:potdHalo 3.2s ease-in-out infinite; }
  .potd-reveal:hover { transform:translateY(-2px); border-color:var(--accent-bright); box-shadow:0 16px 44px -22px var(--accent-glow); }
  .potd-reveal:active { transform:translateY(0); }
  .potd-reveal > * { position:relative; z-index:1; }
  .pr-badge { width:44px; height:44px; border-radius:50%; margin:0 auto 12px; display:flex; align-items:center; justify-content:center; background:var(--accent); color:var(--accent-ink); box-shadow:0 6px 18px -6px var(--accent-glow); }
  .pr-cta { font-size:19px; font-weight:800; color:var(--accent-bright); letter-spacing:.2px; }
  .pr-chev { display:inline-block; animation:potdNudge 1.6s ease-in-out infinite; }
  .pr-sub { color:var(--mut); font-size:12.5px; font-weight:400; margin-top:7px; }
  @keyframes potdHalo { 0%,100%{ opacity:.32; } 50%{ opacity:.6; } }
  @keyframes potdNudge { 0%,100%{ transform:translateX(0); } 50%{ transform:translateX(4px); } }
  @media (prefers-reduced-motion:reduce){ .potd-reveal::before{ animation:none; } .pr-chev{ animation:none; } .potd-bar-dot{ animation:none; } }
  .potd-tagrow { display:flex; align-items:center; justify-content:space-between; gap:10px; margin-bottom:6px; }
  .potd-tagrow .potd-tag { margin-bottom:0; }
  /* D2 tier ladder (shared voice): PRIME=gold hero · STRONG=dim green · SOLID=teal outline (TA-734,
     2026-10-16 — same fix as .conf-Solid, kept in sync) · LEAN/WATCH=neutral */
  .potd-prime { flex:0 0 auto; font-size:11px; font-weight:800; letter-spacing:.6px; text-transform:uppercase; padding:4px 10px; border-radius:999px; background:transparent; color:var(--mut); border:1px solid var(--line); white-space:nowrap; }
  .potd-prime.t-Prime { background:var(--prime); color:var(--prime-ink); border:0; box-shadow:0 4px 14px -4px var(--prime-glow); }
  .potd-prime.t-Strong { background:var(--tier-strong-dim); color:var(--tier-strong); border:1px solid color-mix(in srgb,var(--tier-strong) 45%,transparent); }
  .potd-prime.t-Solid { background:transparent; color:var(--tier-strong); border:1px solid color-mix(in srgb,var(--tier-strong) 35%,transparent); }
  .potd-prime.t-Lean, .potd-prime.t-Watch { background:transparent; color:var(--mut); border:1px solid var(--line); }
  .pgap { margin:13px 0 4px; background:var(--panel2); border:1px solid var(--line); border-radius:12px; padding:12px 14px 14px; }
  .pgap-row { display:flex; align-items:flex-end; justify-content:space-between; gap:6px; }
  .pgap-cell { text-align:center; flex:1; }
  .pgap-cell .k { font-size:10px; text-transform:uppercase; letter-spacing:.4px; color:var(--mut); font-weight:700; }
  .pgap-cell .v { font-family:var(--font-num); font-size:21px; font-weight:700; margin-top:2px; font-variant-numeric:tabular-nums; font-feature-settings:"tnum" 1; letter-spacing:.3px; }
  .pgap-cell.fair .v, .pgap-cell.edge .v { color:var(--accent); }
  .pgap-cell.edge .v small { font-size:11px; font-weight:600; letter-spacing:0; }
  .pgap-vs { color:var(--mut); font-size:13px; font-weight:700; padding-bottom:3px; }
  .pgap-bar { height:7px; border-radius:6px; margin-top:11px; position:relative; background:var(--line); overflow:hidden; }
  .pgap-bar .fill { position:absolute; left:0; top:0; bottom:0; background:linear-gradient(90deg,var(--accent-dim),var(--accent)); }
  .pgap-cap { display:flex; justify-content:space-between; font-size:10.5px; color:var(--mut); margin-top:6px; }
  .pmove { display:flex; align-items:flex-start; gap:8px; margin:11px 0 2px; padding:9px 12px; background:var(--accent-dim); border:1px solid color-mix(in srgb,var(--accent) 30%,transparent); border-radius:10px; font-size:12.5px; line-height:1.45; }
  .pmove .ic { color:var(--accent); flex:0 0 auto; margin-top:1px; }
  /* opposite-side bet reconciliation note (oppositeSideBetNote()) — same box shape as .pmove, warn-toned
     instead of accent-toned since this is "pay attention," not routine market context. */
  .ba-opp-note { display:flex; align-items:flex-start; gap:8px; margin:8px 0; padding:9px 12px; background:color-mix(in srgb,var(--warn) 10%,transparent); border:1px solid color-mix(in srgb,var(--warn) 35%,transparent); border-radius:10px; font-size:12.5px; line-height:1.45; }
  .ba-opp-note .ic { color:var(--warn); flex:0 0 auto; margin-top:1px; }
  /* TA-341 final UX piece — .pbooks/.pbook/.pbooks-more (the old separate Play of the Day book list)
     removed: every row it used to render now lives inside the consolidated .exec module. */
  .potd-acts { display:flex; align-items:center; gap:12px; margin-top:13px; padding-top:12px; border-top:1px solid var(--line); flex-wrap:wrap; }
  .potd-acts .betwrap { margin-left:auto; }
  .books-nudge { display:flex; align-items:center; gap:10px; flex-wrap:wrap; margin:14px 0 4px; padding:11px 14px; border:1px solid var(--blue); border-radius:12px; background:linear-gradient(180deg,rgba(90,170,255,.08),transparent); font-size:13.5px; }
  .books-nudge .bn-set { color:var(--blue); font-weight:700; cursor:pointer; text-decoration:underline; }
  .books-nudge .bn-x { color:var(--mut); cursor:pointer; margin-left:auto; font-size:12px; }
  .steps { display:grid; grid-template-columns:repeat(4,1fr); gap:12px; margin:12px 0; }
  .step { background:var(--panel); border:1px solid var(--line); border-radius:12px; padding:16px; }
  .step .n { color:var(--accent); font-weight:800; font-size:13px; letter-spacing:1px; }
  .step .t { font-weight:700; margin:8px 0 4px; }
  .step .d { color:var(--mut); font-size:13px; line-height:1.5; }
  .home-foot { border-top:1px solid var(--line); margin-top:30px; padding:20px 4px 40px; color:var(--mut); font-size:13px; line-height:1.7; }
  .home-foot b { color:var(--txt); font-weight:600; }
  @media(max-width:720px){ .tiles,.steps{ grid-template-columns:repeat(2,1fr);}
    /* SP-3: give the table room to be legible and let it scroll inside its card. Squeezing four columns
       into 354px is what produced the four-line "No / pro / Co / yet" sliver. */
    /* The "Ask the Sharp" bubble is position:fixed at bottom-right, so on a phone it sits over whatever
       happens to be under it — measured over live table cells and section headings. It is pre-existing
       chrome and moving it is a global decision, but nothing on a page we are shipping should be
       permanently unreachable: extra bottom room means every element can be scrolled out from under it. */
    .wrap { padding-bottom:168px; }
    .tscroll > table { min-width:520px; }
    .tscroll > table.gridtbl { min-width:566px; }                        /* 92 + three 158px data columns */
    /* TA-1034 — the 3-column Our Opinion tier table is the deliberate exception to the 520px floor just
       above: it has no 4th+ column to make room for, so forcing it wide only pushed its own sample-floor
       caveat text off-screen with no scroll affordance. Let it stay 100% width and wrap instead. */
    .tscroll > table.opin-tier-tbl { min-width:0; width:100%; }
    .gridtbl th:first-child, .gridtbl td:first-child { width:92px; }
    /* ⚠ FREEZE THE CONVICTION COLUMN. Scrolled right, the reader saw "-8.4% · 16 settled", "-2.4% · 40
       settled", "+25.7% · 35 settled" with NO Prime/Strong/Solid label on screen at all — the ladder
       disappeared at exactly the moment the other bet types became visible. Even a reader who notices the
       new scroll affordance would get unlabelled numbers. The label travels with the row. */
    .gridtbl th:first-child, .gridtbl td:first-child {
      position:sticky; left:0; background:var(--panel);
      box-shadow:1px 0 0 var(--line);
      /* ⚠ ABOVE the edge fade (z-index 2), not below it. At z-index 1 the left gradient painted straight
         over the frozen column and clipped it to "onviction / rime / trong / olid" — the two fixes for B2
         and B3 fighting each other and producing something that looked more broken than either bug.
         Caught by LOOKING at the render: the automated check compared bounding boxes, and a box inside the
         card reads as "visible" while an overlay sits on top of it. Geometry is not legibility. */
      z-index:3;
    }
    /* And the left chevron starts where the frozen column ends, so it marks the scrolled region it actually
       describes instead of covering the one part of the row that never scrolls. */
    .tscroll-wrap.frozen::before { left:92px; }
    /* ⚠ THE SLIVER AT FULL RIGHT SCROLL IS DEFERRED, NOT FORGOTTEN.
       I tried `scroll-snap-align: start` and it did not help: at maximum scroll the scroller is already at
       its limit, so there is no further START edge for it to land on.
       ⚠ CORRECTION to an earlier note of mine, which overstated this: `scroll-snap-align: end`, or a
       trailing `scroll-padding-inline-end`, WOULD make the final position land cleanly. Snap is not
       incapable here — I only proved the one variant I tried does not work. The reason to defer is the
       arithmetic below, which is a layout decision rather than a scrolling one:
         viewport 390 → card 354 → scroller 308, of which the frozen label column holds 92
         → 216px of room beside it, against a 158px data column
         → one full column and a 58px remainder (measured at full scroll: the middle column is 158px wide
           with 100px of it behind the frozen column). 216 is not a multiple of 158, so a partial column at
           the extreme is unavoidable at these widths.
       The only clean fixes are to make the data column 216px (one bet type on screen at a time) or 108px
       (two, but too narrow for "+16.1% · 15 settled" on one line). Both are real layout decisions about
       what a phone reader should see at once, which belongs to the Design Lead rather than to a CSS tweak
       here. Clean at rest and mid-scroll; the frozen label stays legible throughout. */
    /* 158px of column at 15.5px holds "+16.1% · 15 bets" on ONE line. It was wrapping to two, and at the
       pre-fix widths to three, which is what made a confident figure read as a broken one. */
    .gridtbl .cellhead { font-size:15.5px; }
    .tabs{ -webkit-mask-image:linear-gradient(to right,#000 92%,transparent); mask-image:linear-gradient(to right,#000 92%,transparent);} /* hint there are more tabs to scroll */
    /* iOS auto-zooms a focused input whose font is <16px (magnifies the page, cuts off the input + chips) — pin to 16px on mobile so it never zooms */
    .sharp-input textarea, .modal input, .modal textarea, .modal select, .tag-input .tag-add,
    /* SP-223: the auth-family cards (invite / sign in / forced password change) are the most
       phone-heavy screens in the product - an invite link arrives by text - and they were NOT
       covered by the rule above, so every one of them zoomed on focus. */
    .invite-card input, .invite-card select, .card input[type="email"], .card input[type="password"], #code { font-size:16px; } }
  /* SP-312: Weekly Picks framed in-app. Starts at a sane guess so there is no zero-height flash before
     the embedded page's own script reports its real height; grows or shrinks from there. No border/
     shadow — it should read as part of this page, not as a window onto another one. */
  .wp-embed { width:100%; min-height:600px; height:600px; border:0; display:block; background:transparent; transition:height .12s ease-out; }
  /* TA-712 Game Lines <-> Game Totals integration — same embed pattern as .wp-embed just above
     (core/lib/game-totals-render.mjs's own EMBED_SCRIPT reports real height via postMessage). */
  .gt-embed { width:100%; min-height:600px; height:600px; border:0; display:block; background:transparent; transition:height .12s ease-out; }

  /* ════════════════════════════════════════════════════════════════════════════════════════════
     TA-1362 — DAILY ANGLES TIP-SHEET. Collapsed one-row-per-game default view + per-card
     expand-in-place, replacing the old "full write-up first, badge buried at the bottom" card.
     Built from the David-validated Design Lead mockup (round 2, confirmed by UX Reviewer twice):
     https://claude.ai/artifact/748jndtZxh7ofoMhYmUwRe. Generalizes across every league (NFL/CFB/NBA
     today) and any slate size — nothing here is CFB-specific. See dashboard/index.html's
     _dailyAngelsGameRow()/_dailyAngelsConvictionChip() for the markup these classes style.

     Badge system — 4 states, same rule driving every other tier color on this page (red/amber/
     orange means a real problem, never cosmetic staleness; a tier color always carries one real
     meaning): Strong Lean gets a SOLID fill (the one state that should jump off the page at a
     scroll-through glance), same technique `.conf-Prime` already uses for the market board's own
     top tier (solid fill + dark ink text) — just `--tier-strong` teal, never `--prime` gold, so it
     never implies Daily Angles' conviction equals that unrelated devigged-price scale. Lean stays
     outline-only at the SAME hue (fill vs. no-fill is the primary differentiator; hue carries
     direction). Toss-up is muted/dashed/italic, deliberately unfilled — a real coin-flip read, not
     a weak Lean. Info-only (TA-1364's "no qualified wager" case) is a 4th, distinct-blue state so a
     non-featured/no-opinion game never reads as blank or skipped. */
  .da-summary { margin:20px 0; background:var(--panel); border:1px solid var(--line); border-radius:12px; padding:16px 18px; }
  .da-summary-title { font-size:11px; font-weight:800; letter-spacing:.1em; text-transform:uppercase; color:var(--mut); margin-bottom:12px; }
  .da-tier-counts { display:flex; gap:10px; flex-wrap:wrap; margin-bottom:16px; }
  .da-tier-tile { flex:1 1 130px; background:var(--panel2); border-radius:8px; padding:10px 12px; }
  .da-tier-tile .n { font-family:var(--font-num); font-size:26px; font-weight:700; font-variant-numeric:tabular-nums; line-height:1; }
  .da-tier-tile .l { font-size:11px; color:var(--mut); text-transform:uppercase; letter-spacing:.05em; margin-top:4px; }
  .da-tier-tile.strong-lean .n { color:var(--tier-strong); }
  .da-tier-tile.lean .n { color:var(--txt); }
  .da-tier-tile.toss .n { color:var(--mut); }
  .da-tier-tile.info .n { color:var(--blue); }
  .da-jump-list { display:flex; flex-direction:column; gap:6px; }
  .da-jump-row { display:flex; align-items:baseline; gap:10px; font-size:13.5px; text-decoration:none; color:var(--txt); padding:5px 6px; border-radius:6px; }
  .da-jump-row:hover, .da-jump-row:focus-visible { background:var(--panel2); }
  .da-jump-time { font-family:var(--font-num); color:var(--mut); font-size:12px; min-width:70px; font-variant-numeric:tabular-nums; }
  .da-jump-side { color:var(--tier-strong); font-weight:700; }

  /* The mockup's own round-2 chip used a rounded "tag" silhouette (border-radius:2px 999px 999px 2px)
     — that is the SAME shape `.opin-chip`'s own TA-841 build process already tried and rejected
     (see that comment block above, "REAL VISUAL FINDING, ROUND 1": not reliably perceptible). The
     mockup was reviewed before this constraint was back in frame; this build composes with
     `.opin-chip` itself (sharp rectangle, border-radius:0, already-decided base metrics) instead of
     reintroducing the shape TA-841 already ruled out — same rectangle silhouette the rest of the
     site's Opinion badges use, per this ticket's own explicit routing. Apply as
     `<span class="opin-chip da-strong-lean">`, etc. — never `.da-chip` alone. */
  .opin-chip.da-strong-lean { background:var(--tier-strong); color:var(--bg); border:0; box-shadow:0 4px 14px -4px color-mix(in srgb, var(--tier-strong) 50%, transparent); }
  .opin-chip.da-lean { background:transparent; color:var(--tier-strong); border:1px solid color-mix(in srgb, var(--tier-strong) 35%, transparent); }
  /* TA-1371 UX Reviewer finding (RJ Barrett entry, 2026-11-15) — this was the ONE tier whose border used
     the flat --line divider token (#26323f) instead of deriving its color from an accent token via
     color-mix the way every other tier here already does (da-lean off --tier-strong, da-info-only off
     --blue). --line sits so close in luminance to --panel (#141b24) that the dashed border was
     effectively imperceptible — read as "plain italic text, no pill" even though the class WAS applied
     correctly (confirmed: the real _dailyAngelsConvictionChip() output already carried
     class="opin-chip da-toss-up"). Fix is contrast only — same transparent fill, same dashed style, same
     italic text, same border-radius:0 shape TA-841 already decided; only the border's color now derives
     from --mut (already this tier's own text color) via the same color-mix idiom instead of --line, so
     it actually reads as a bordered pill. Shared component — this fixes every existing Toss-up chip on
     the page (PRA, game cards), not just the new Props card that caught it. */
  .opin-chip.da-toss-up { background:transparent; color:var(--mut); border:1px dashed color-mix(in srgb, var(--mut) 45%, transparent); font-style:italic; }
  .opin-chip.da-info-only { background:transparent; color:var(--blue); border:1px solid color-mix(in srgb, var(--blue) 40%, transparent); }

  /* TA-1371 — market tag for a Top Props Tonight row (_dailyAngelsPropsSection). propsOfTheDay spans
     several real markets per entry (Rebounds, Rec Yds, ...), unlike PRA where the market is always
     implicit, so this is the one visual differentiator from the untouched PRA card above it per the
     Design Lead mockup (https://claude.ai/artifact/RKYdXdUjBiZtx89Egk7aue) — no new badge shape, no new
     card chrome, just this small inline label next to the player/team. */
  .mkt-tag { display:inline-block; font-size:11px; font-weight:700; letter-spacing:.03em; text-transform:uppercase; color:var(--mut); background:var(--panel2); border:1px solid var(--line); border-radius:4px; padding:1px 7px; margin-left:6px; white-space:nowrap; }

  .da-row-list { border:1px solid var(--line); border-radius:12px; overflow:hidden; margin-top:10px; }
  .da-row { padding:12px 14px; border-bottom:1px solid var(--line); cursor:pointer; background:var(--panel); }
  .da-row:last-child { border-bottom:none; }
  .da-row:hover { background:var(--panel2); }
  /* Keyboard-focus parity with every other click-row this file already builds (see .shot-thumb,
     the radio-lens group) — a visible outline, never swallowed by the row's own background. */
  .da-row:focus-visible { outline:2px solid var(--accent); outline-offset:-2px; }
  .da-row-top { display:flex; align-items:baseline; gap:10px; flex-wrap:wrap; }
  .da-row-time { font-family:var(--font-num); color:var(--mut); font-size:12.5px; min-width:72px; font-variant-numeric:tabular-nums; }
  .da-row-matchup { font-weight:700; font-size:15px; flex:1 1 240px; }
  .da-row-caret { color:var(--mut); font-size:12px; margin-left:auto; display:inline-block; transition:transform .1s ease-out; }
  .da-row[aria-expanded="true"] .da-row-caret { transform:rotate(90deg); }
  /* The Pick line — the real blocking UX finding this ticket exists to fix: an explicit, bolded
     line built from the structured opinion.side/opinion.market fields, NEVER inferred from prose.
     Sits directly under the matchup at full contrast, bolder than everything else in the row
     except the matchup name — this IS the lede that used to be buried after the full write-up. */
  .da-row-pick { margin-top:5px; padding-left:82px; font-size:14.5px; font-weight:700; color:var(--txt); }
  .da-row-pick .da-pick-market { font-weight:600; color:var(--mut); text-transform:uppercase; font-size:11.5px; letter-spacing:.04em; margin-left:2px; }
  .da-row-pick.muted { font-weight:500; font-style:italic; color:var(--mut); }
  /* Defensive clamp — ONLY for a real, distinct `g.angle` (meant to be 1-2 authored sentences; this
     clamp is a width/overflow safety net for that case, not the main truncation mechanism). TA-1367
     REFIX #2 (per independent review, Grok + GPT): a hard 3-line clamp on the common `writeUp`-
     fallback case produced a mid-sentence "..." that promised more text was one click away in place —
     reader expectation a same-page jump link still broke, since it isn't "right here." That fallback
     case now renders via `.da-row-angle-firstsentence` below instead, which is never clamped because
     `_daFirstSentence()` already guarantees a complete sentence, never a mid-sentence slice. */
  .da-row-angle { margin-top:3px; font-size:13.5px; color:var(--mut); line-height:1.45; padding-left:82px; display:-webkit-box; -webkit-box-orient:vertical; -webkit-line-clamp:3; overflow:hidden; }
  /* TA-1367 REFIX #2 — the writeUp-fallback preview (`_daFirstSentence()`'s output). Deliberately NOT
     clamped: the text is already a complete sentence, so there is nothing to truncate and no "..."
     ever appears here. A long single sentence may still run past 3 lines on a narrow viewport — that
     reads as "a long sentence," which is honest, never as "content got cut off mid-thought." */
  .da-row-angle-firstsentence { margin-top:3px; font-size:13.5px; color:var(--mut); line-height:1.45; padding-left:82px; }

  .da-detail { background:var(--panel2); padding:16px 14px 18px 82px; font-size:15px; line-height:1.6; border-bottom:1px solid var(--line); }
  .da-detail h4 { font-size:11px; font-weight:800; letter-spacing:.08em; text-transform:uppercase; color:var(--mut); margin:14px 0 6px; }
  .da-detail h4:first-child { margin-top:0; }
  .da-detail p { margin:0 0 10px; color:var(--txt); }

  @media (max-width:560px) {
    .da-row-pick, .da-row-angle, .da-row-angle-firstsentence { padding-left:0; }
    .da-detail { padding-left:14px; }
    .da-row-time { min-width:60px; }
  }
