html, body {
    font-family: 'Roboto', sans-serif;
}

#blazor-error-ui {
    background: lightyellow;
    bottom: 0;
    box-shadow: 0 -1px 2px rgba(0, 0, 0, 0.2);
    display: none;
    left: 0;
    padding: 0.6rem 1.25rem 0.7rem 1.25rem;
    position: fixed;
    width: 100%;
    z-index: 1000;
}

#blazor-error-ui .dismiss {
    cursor: pointer;
    position: absolute;
    right: 0.75rem;
    top: 0.5rem;
}

.valid.modified:not([type=checkbox]) {
    outline: 1px solid #26b050;
}

.invalid {
    outline: 1px solid red;
}

.validation-message {
    color: red;
}

/* A player the member has nicknamed (Phase 15 deferral, finished 2026-08-04). Styled as the name it
   replaces, plus the faintest dotted underline and a help cursor to say "there is a real name behind
   this" — the element carries it as a title. Deliberately not a color or a badge: a board of 200 rows
   should not turn into a patchwork because someone named six players. */
.ff-player-nick {
    text-decoration: underline dotted rgba(var(--mud-palette-text-secondary-rgb, 150, 150, 150), .45);
    text-underline-offset: 2px;
    cursor: help;
}

/* ------------------------------------------------------------
   Owner report (2026-08-04): a focus ring painted itself around the page HEADING
   after navigation, most visibly on the public/auth pages, and cleared only after a
   couple of taps elsewhere.

   It is not a style of ours. `App.razor` renders <FocusOnNavigate Selector="h1" />,
   the framework's accessibility component: after every client-side navigation it
   moves focus to the first <h1> so a screen reader announces the new page instead of
   leaving the user's cursor stranded on the link they just followed. Blazor's interop
   makes the heading focusable to do that (it stamps tabindex="-1" when the element has
   no tabindex of its own), and WebKit then draws its focus ring around a heading the
   visitor never interacted with.

   The announcement is worth keeping, so suppress the RING rather than the focus. This
   is not the "never remove outlines" anti-pattern: tabindex="-1" keeps the heading out
   of the tab order entirely, so no keyboard user can reach it and no focus indicator is
   owed for it (WCAG 2.4.7 governs elements that receive focus through interaction).
   Every real control is untouched and keeps its :focus-visible ring, and the selector is
   deliberately narrow (headings that Blazor made focusable) rather than a blanket
   [tabindex="-1"]:focus, which would also silence dialogs and other genuine
   programmatic focus targets that DO want a visible landing point.
   ------------------------------------------------------------ */
h1[tabindex="-1"]:focus,
h2[tabindex="-1"]:focus {
    outline: none;
}

/* ============================================================
   Dashboard / panel layer (Path A visual pass).
   Built on MudBlazor's own --mud-palette-* variables so every
   surface adapts automatically to light/dark themes.
   ============================================================ */

.ff-page-head { margin-bottom: 20px; }
.ff-page-head h1 { font-size: 1.7rem; font-weight: 700; letter-spacing: -.01em; margin: 0; line-height: 1.15; }
.ff-page-sub { color: var(--mud-palette-text-secondary); font-size: .9rem; margin-top: 4px; }

/* Phase 21D: section divider heading on the rebuilt /stats league-history grid. Named distinctly from
   .ff-records-section-head so the two pages' section counts never collide in tests. */
.ff-stats-section-head {
    display: flex; align-items: center; gap: 8px;
    margin: 20px 0 2px; font-size: 1.02rem; font-weight: 700;
}

/* KPI tiles */
.ff-tile {
    background: var(--mud-palette-surface);
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 14px;
    padding: 16px 18px;
    height: 100%;
    display: flex;
    flex-direction: column;
    gap: 5px;
    min-height: 104px;
}
.ff-tile-label {
    font-size: .7rem; letter-spacing: .09em; text-transform: uppercase;
    color: var(--mud-palette-text-secondary); font-weight: 600;
    display: flex; align-items: center; gap: 6px;
}
.ff-tile-value {
    font-size: 1.85rem; font-weight: 700; line-height: 1.05;
    font-variant-numeric: tabular-nums; color: var(--mud-palette-text-primary);
}
.ff-tile-value .u { font-size: .95rem; font-weight: 500; color: var(--mud-palette-text-secondary); }
/* A date, not a number: it needs to wrap inside a half-width tile at 360px rather than run past the
   tile edge, so it drops the big display size and is allowed to break between the date and the time. */
.ff-tile-value-date { font-size: 1.15rem; line-height: 1.2; overflow-wrap: break-word; }
@media (min-width: 600px) { .ff-tile-value-date { font-size: 1.25rem; } }
.ff-tile-sub { font-size: .76rem; color: var(--mud-palette-text-secondary); margin-top: auto; }
/* A second caption line (the per-game lock's close instant). margin-top:auto on BOTH would split the
   tile's free space between them and leave a gap in the middle, so the follow-on line sits tight under
   the first and only the pair as a whole is pushed to the bottom. */
.ff-tile-sub + .ff-tile-sub { margin-top: 0; }

/* Section panels */
.ff-panel {
    background: var(--mud-palette-surface);
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 14px;
    overflow: hidden;
}
.ff-panel-head {
    display: flex; align-items: center; justify-content: space-between; gap: 12px;
    padding: 13px 16px; border-bottom: 1px solid var(--mud-palette-lines-default);
}
.ff-panel-head .ttl { font-size: .98rem; font-weight: 600; display: flex; align-items: center; gap: 8px; }
.ff-panel-body { padding: 6px; }
.ff-panel-body.pad { padding: 16px; }

/* Standings rows */
.ff-standing {
    display: grid; grid-template-columns: 30px 1fr auto; align-items: center; gap: 12px;
    padding: 9px 10px; border-radius: 9px;
}
.ff-standing.me { background: rgba(var(--mud-palette-primary-rgb), .13); }
.ff-standing .rank {
    width: 26px; height: 26px; border-radius: 7px; display: flex; align-items: center; justify-content: center;
    font-size: .78rem; font-weight: 700; font-variant-numeric: tabular-nums;
    background: var(--mud-palette-background); color: var(--mud-palette-text-secondary);
}
.ff-standing.lead .rank { background: var(--mud-palette-primary); color: #fff; }
.ff-standing .who { font-weight: 600; font-size: .89rem; display: flex; align-items: center; gap: 8px; min-width: 0; }
.ff-standing .who .who-name { overflow: hidden; text-overflow: ellipsis; white-space: nowrap; min-width: 0; }
.ff-standing .who .metag { font-size: .68rem; font-weight: 700; color: var(--mud-palette-primary); margin-left: 6px; letter-spacing: .04em; }
/* Phase 15B: keep the scoreboard avatar compact so the row height doesn't grow. */
.ff-standing .ff-standing-av { width: 26px; height: 26px; min-width: 26px; font-size: .68rem; }

/* Phase 15B: the shared member chip (avatar + resolved team name), used across surfaces. */
.ff-member-chip { display: inline-flex; align-items: center; gap: 8px; min-width: 0; }
.ff-member-chip .ff-member-chip-name { overflow: hidden; text-overflow: ellipsis; white-space: nowrap; min-width: 0; }
/* Batch B (B2): a linkified member chip stays visually quiet (inherits color/weight) and only
   reveals its linkiness on hover, so dense member lists don't turn loud. */
.ff-member-chip.ff-link { color: inherit; font-weight: inherit; }
.ff-member-chip.ff-link:hover { text-decoration: none; }
.ff-member-chip.ff-link:hover .ff-member-chip-name { text-decoration: underline; color: var(--mud-palette-primary); }

/* Phase 15C: public profile + the Account-Settings public-profile editor. */
.ff-profile-hero { display: flex; align-items: center; gap: 16px; flex-wrap: wrap; }
.ff-profile-hero-text { min-width: 0; }
.ff-profile-name { margin: 0; font-size: 1.4rem; line-height: 1.2; }
.ff-profile-teams { display: flex; flex-direction: column; gap: 10px; }
.ff-profile-team { display: flex; flex-direction: column; }
.ff-profile-team-name { font-weight: 600; }
.ff-profile-avatar-row { display: flex; align-items: center; gap: 16px; flex-wrap: wrap; }
.ff-profile-avatar-actions { display: flex; align-items: center; gap: 10px; flex-wrap: wrap; }
.ff-file-btn { display: inline-flex; align-items: center; gap: 6px; cursor: pointer; padding: 6px 12px; border-radius: 8px;
    border: 1px solid var(--mud-palette-lines-default); font-size: .85rem; font-weight: 500; }
.ff-file-btn:hover { background: rgba(var(--mud-palette-primary-rgb), .08); }
.ff-nick-list { display: flex; flex-direction: column; gap: 6px; }
.ff-nick-row { display: flex; align-items: center; gap: 8px; }
.ff-nick-row .ff-nick-player { font-weight: 600; }
.ff-nick-row .ff-nick-arrow { opacity: .6; }
.ff-nick-row .ff-nick-value { flex: 1; min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-nick-add { display: flex; gap: 10px; align-items: flex-start; flex-wrap: wrap; }
.ff-nick-add > * { flex: 1 1 160px; }
.ff-nick-add > button, .ff-nick-add .mud-button-root { flex: 0 0 auto; }

/* Phase 15D: Records Book + career pages. */
.ff-records-grid { display: grid; grid-template-columns: 1fr; gap: 16px; }
@media (min-width: 720px) { .ff-records-grid { grid-template-columns: 1fr 1fr; } }
.ff-record-row { display: flex; align-items: center; gap: 10px; padding: 6px 0; border-bottom: 1px solid var(--mud-palette-lines-default); }
.ff-record-row:last-child { border-bottom: none; }
.ff-record-row .ff-member-chip { flex: 1 1 auto; min-width: 0; }
.ff-record-meta { font-size: .78rem; color: var(--mud-palette-text-secondary); white-space: nowrap; }
.ff-record-val { font-variant-numeric: tabular-nums; font-weight: 700; min-width: 44px; text-align: right; }
/* Phase 21D: name cell for the merged record-performance rows (player/defense game lists). */
.ff-record-name { flex: 1 1 auto; min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; font-weight: 600; font-size: .89rem; }
.ff-record-name .ff-record-sub { font-weight: 400; font-size: .78rem; color: var(--mud-palette-text-secondary); }
.ff-records-perf-head { display: flex; align-items: center; gap: 8px; margin: 0 0 12px; font-size: 1.05rem; font-weight: 800; }
.ff-stat-tiles { display: grid; grid-template-columns: repeat(auto-fill, minmax(150px, 1fr)); gap: 12px; }
.ff-stat-tile { display: flex; flex-direction: column; gap: 2px; padding: 12px 14px; border-radius: 10px;
    background: var(--mud-palette-background-gray); }
.ff-stat-tile .v { font-size: 1.4rem; font-weight: 700; font-variant-numeric: tabular-nums; }
.ff-stat-tile .k { font-size: .74rem; color: var(--mud-palette-text-secondary); }
.ff-career-table { width: 100%; border-collapse: collapse; }
.ff-career-table th, .ff-career-table td { text-align: left; padding: 8px 10px; border-bottom: 1px solid var(--mud-palette-lines-default); white-space: nowrap; }
.ff-career-table th { font-size: .78rem; color: var(--mud-palette-text-secondary); font-weight: 600; }

/* Phase 15E: rivalry page + picker, and the activity feed. */
.ff-rivalry-head { display: flex; align-items: center; justify-content: center; gap: 20px; margin: 8px 0 20px; flex-wrap: wrap; }
.ff-rivalry-side { display: flex; flex-direction: column; align-items: center; gap: 6px; min-width: 0; }
.ff-rivalry-name { font-weight: 600; text-align: center; max-width: 160px; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-rivalry-wins { font-size: 2rem; font-weight: 800; font-variant-numeric: tabular-nums; line-height: 1; }
.ff-rivalry-vs { font-size: 1.1rem; color: var(--mud-palette-text-secondary); font-weight: 600; }
.ff-rivalry-picker { display: flex; align-items: center; gap: 12px; flex-wrap: wrap; }
.ff-rivalry-picker > .mud-input-control { flex: 1 1 180px; min-width: 140px; }
.ff-feed { display: flex; flex-direction: column; gap: 12px; }
.ff-feed-item { display: flex; align-items: flex-start; gap: 10px; }
.ff-feed-item .ff-feed-icon { margin-top: 2px; flex: 0 0 auto; }
.ff-feed-item .ff-md { min-width: 0; }
/* Batch B (B2): a feed row that links to its week's scoreboard. */
a.ff-feed-item { color: inherit; text-decoration: none; border-radius: 6px; margin: -4px -6px; padding: 4px 6px; }
a.ff-feed-item:hover { background: rgba(var(--mud-palette-primary-rgb), .08); }

/* Batch B (B2): the shared linkified-entity affordance (names, week references). Theme-aware. */
.ff-link { color: var(--mud-palette-primary); text-decoration: none; font-weight: 600; cursor: pointer; }
.ff-link:hover { text-decoration: underline; }

/* ---- 18G: activity feed ---- */
/* Name-level links now render inline inside the entry (member â†’ career, player â†’ hub, week â†’
   scoreboard) rather than the whole row being one link, so entries wrap and each link stays tappable
   at 360px. break-word keeps a long player/team name from overflowing the narrow column. */
.ff-feed-body { overflow-wrap: break-word; }
.ff-feed-body .ff-feed-name { font-weight: 700; }

/* Phase 15F: co-manager surfaces. */
.ff-comanaged { display: flex; align-items: center; gap: 6px; margin-top: 6px; font-size: .8rem; color: var(--mud-palette-text-secondary); }
.ff-comanager-add { display: flex; gap: 10px; align-items: flex-start; flex-wrap: wrap; }
.ff-comanager-add > .mud-input-control { flex: 1 1 180px; min-width: 140px; }
.ff-comanager-list { display: flex; flex-direction: column; gap: 6px; }
.ff-comanager-row { display: flex; align-items: center; justify-content: space-between; gap: 10px; padding: 6px 0; border-bottom: 1px solid var(--mud-palette-lines-default); }
.ff-comanager-row:last-child { border-bottom: none; }

/* T-23: league-settings time-zone picker rows. Friendly label on top, raw IANA id underneath, so the
   commissioner recognizes the zone and can still see exactly what is stored. Stacked (not side by
   side) so a long id wraps instead of pushing the row wide at 360px. */
.ff-tz-option { display: flex; flex-direction: column; gap: 2px; min-width: 0; }
.ff-tz-label { font-weight: 600; font-size: .9rem; }
.ff-tz-id { font-size: .75rem; color: var(--mud-palette-text-secondary); overflow-wrap: anywhere; }
.ff-tz-none { padding: 8px 12px; font-size: .85rem; color: var(--mud-palette-text-secondary); }
.ff-standing .pts { font-variant-numeric: tabular-nums; font-weight: 600; font-size: .9rem; }

/* Roster rows */
.ff-roster-row {
    display: grid; grid-template-columns: 52px 1fr auto; align-items: center; gap: 12px;
    padding: 11px 14px; border-bottom: 1px solid var(--mud-palette-lines-default);
}
.ff-roster-row:last-child { border-bottom: 0; }
.ff-roster-row.total { font-weight: 700; }
.ff-pos {
    font-size: .66rem; font-weight: 700; letter-spacing: .04em; text-align: center;
    padding: 3px 0; border-radius: 6px; color: #fff; text-transform: uppercase;
}
.ff-pos.qb { background: #3b82f6; }
.ff-pos.rb { background: #10b981; }
.ff-pos.wr { background: #f59e0b; }
.ff-pos.flex { background: #8b5cf6; }
.ff-pos.def { background: #ef4444; }
.ff-roster-row .name { font-size: .89rem; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-roster-row .name.empty { color: var(--mud-palette-text-secondary); font-style: italic; }
.ff-roster-row .pt { font-variant-numeric: tabular-nums; font-weight: 600; }

/* Shared empty-state */
.ff-empty-state {
    display: flex; flex-direction: column; align-items: center; justify-content: center;
    text-align: center; gap: 8px; padding: 34px 20px; color: var(--mud-palette-text-secondary);
}
.ff-empty-state .mud-icon-root { opacity: .5; }

/* Rank medals for the top three */
.ff-standing.r1 .rank { background: #d4af37; color: #231d00; }
.ff-standing.r2 .rank { background: #aab2bd; color: #1b1f24; }
.ff-standing.r3 .rank { background: #cd7f4a; color: #fff; }

/* Page toolbar (year / week selectors etc.) */
.ff-toolbar { display: flex; flex-wrap: wrap; gap: 12px; align-items: center; margin-bottom: 20px; }

/* Segmented control â€” the Draft hub's section switcher. Sticky under the page head, horizontally
   scrollable/swipeable on phones with generous tap targets. */
.ff-segtabs { display: flex; gap: 4px; padding: 4px; margin-bottom: 4px; border-radius: 12px;
    background: var(--mud-palette-background-gray); position: sticky; top: 0; z-index: 3;
    overflow-x: auto; scrollbar-width: none; -webkit-overflow-scrolling: touch; }
.ff-segtabs::-webkit-scrollbar { display: none; }
.ff-segtab { display: inline-flex; align-items: center; gap: 6px; flex: 1 0 auto; justify-content: center;
    min-height: 44px; padding: 6px 16px; border: none; border-radius: 9px; cursor: pointer;
    background: transparent; color: var(--mud-palette-text-secondary); font-size: .9rem; font-weight: 600;
    white-space: nowrap; transition: background .15s, color .15s; }
.ff-segtab:hover { color: var(--mud-palette-text-primary); }
.ff-segtab.active { background: var(--mud-palette-surface); color: var(--mud-palette-primary);
    box-shadow: 0 1px 3px rgba(0,0,0,.18); }
.ff-segtab-ico { flex: 0 0 auto; }
.ff-segtab-dot { width: 8px; height: 8px; border-radius: 50%; background: var(--mud-palette-success);
    animation: ff-seg-pulse 1.6s ease-in-out infinite; }
@keyframes ff-seg-pulse { 0%,100% { opacity: 1; transform: scale(1); } 50% { opacity: .45; transform: scale(.8); } }
.ff-seg-body { margin-top: 16px; }

/* Phone: full-width equal segments, tighter padding, label under nothing (icon + short label). */
@media (max-width: 640px) {
    .ff-segtab { flex: 1 1 0; padding: 6px 8px; font-size: .82rem; gap: 4px; }
    .ff-segtab-lbl { overflow: hidden; text-overflow: ellipsis; }
}

/* Two-column panel layout that stacks on narrow screens */
.ff-cols { display: grid; grid-template-columns: 1fr 1fr; gap: 16px; align-items: start; }
@media (max-width: 960px) { .ff-cols { grid-template-columns: 1fr; } }

/* Draft pick rows */
.ff-pick-row {
    display: grid; grid-template-columns: 40px 44px 1fr auto; align-items: center; gap: 12px;
    padding: 10px 14px; border-bottom: 1px solid var(--mud-palette-lines-default);
}
.ff-pick-row:last-child { border-bottom: 0; }
.ff-pick-row .pick {
    font-variant-numeric: tabular-nums; font-weight: 700; font-size: .8rem;
    color: var(--mud-palette-text-secondary); text-align: center;
}
.ff-pick-row .pick-main { min-width: 0; }
.ff-pick-row .pick-main .nm { font-weight: 600; font-size: .9rem; }
.ff-pick-row .pick-sub {
    font-size: .74rem; color: var(--mud-palette-text-secondary);
    overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}
.ff-pick-row .pick-pts { font-variant-numeric: tabular-nums; font-weight: 600; font-size: .9rem; }
.ff-pos.inrow { display: inline-block; width: 100%; }

/* My Team reads as a capped column instead of a half-width grid that left the desktop right half empty. */
.ff-team-wrap { max-width: 720px; }

/* Board "by member" grid â€” one roster card per member, auto-fitting columns (1-up on phones).
   Owner round 2026-08-31 (post-#748, rides the next release): 210px let a wide monitor cram all nine
   league cards into one row of ellipsized names, and the points column the cards gained in #744 needs
   real width beside the name. 300px wraps a nine-member league to two readable rows on a desktop and
   changes nothing on phones, which were already 1-up. */
.ff-board-view { display: inline-flex; gap: 6px; }
.ff-board-grid { display: grid; grid-template-columns: repeat(auto-fill, minmax(300px, 1fr));
    gap: 16px; align-items: start; }

/* Phone tightening for the Board pick rows, the roster, and the Room's team strip. */
@media (max-width: 640px) {
    .ff-pick-row { grid-template-columns: 28px 38px 1fr auto; gap: 8px; padding: 8px 4px; }
    .ff-pick-row .pick-main .nm { font-size: .85rem; }
    /* T-33: the chips wrap onto as many lines as the roster needs instead of squeezing five truncated
       names onto one. Tighter gaps and padding so two or three still fit per line at 360px. */
    .ff-teamstrip { gap: 5px 6px; padding: 6px 8px; }
    .ff-teamstrip-slot { padding: 2px 7px 2px 3px; gap: 5px; }
    .ff-teamstrip-slot .ff-pos { min-width: 28px; padding: 2px 5px; font-size: .6rem; }
    .ff-teamstrip-name { font-size: .78rem; }
}

/* Detail-page title (position chip + name) */
.ff-detail-title { display: flex; align-items: center; gap: 12px; flex-wrap: wrap; }
.ff-detail-title h1 { margin: 0; }
/* Base .ff-pos is written to FILL a fixed grid track (width:100%, no horizontal padding), so every
   surface that shows it beside a name has to give it back its natural size. The second selector is the
   page hero's heading (wave H4): the Player hub's pill moved inside the h1 with the rest of the name's
   cluster, and the chip is still the page's own content, styled from here as it always was. */
.ff-detail-title .ff-pos,
.ff-ph-title .ff-pos { width: auto; min-width: 46px; padding: 5px 12px; font-size: .78rem; }

/* Key/value rows (profile account info etc.) */
.ff-kv { display: flex; justify-content: space-between; gap: 16px; padding: 8px 0; border-bottom: 1px solid var(--mud-palette-lines-default); }
.ff-kv:last-child { border-bottom: 0; }
.ff-kv .k { color: var(--mud-palette-text-secondary); font-size: .85rem; }
.ff-kv .v { font-weight: 600; font-size: .9rem; }

/* ============================================================
   Live Game Day layer (CFBD /scoreboard overlay).
   ============================================================ */
@keyframes ff-pulse { 0%, 100% { opacity: 1; } 50% { opacity: .25; } }

/* "LIVE" badge (page head / panel heads) */
.ff-live-badge {
    display: inline-flex; align-items: center; gap: 6px;
    background: #ef4444; color: #fff; font-size: .68rem; font-weight: 700;
    letter-spacing: .09em; text-transform: uppercase; padding: 3px 9px; border-radius: 999px;
}
.ff-live-badge .dot { width: 7px; height: 7px; border-radius: 50%; background: #fff; animation: ff-pulse 1.4s ease-in-out infinite; }

/* Game-day roster slot: pos chip | name + game chip | points */
.ff-gd-slot {
    display: grid; grid-template-columns: 52px 1fr auto; align-items: center; gap: 12px;
    padding: 11px 14px; border-bottom: 1px solid var(--mud-palette-lines-default);
}
.ff-gd-slot:last-child { border-bottom: 0; }
.ff-gd-slot.total { font-weight: 700; }
.ff-gd-main { min-width: 0; display: flex; flex-direction: column; gap: 3px; }
.ff-gd-name { font-size: .89rem; font-weight: 600; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-gd-name.empty { color: var(--mud-palette-text-secondary); font-style: italic; font-weight: 400; }
.ff-gd-pts { font-variant-numeric: tabular-nums; font-weight: 700; font-size: .95rem; }

/* Per-slot game chip */
.ff-gd-chip { display: inline-flex; align-items: center; gap: 6px; font-size: .72rem; font-weight: 600; color: var(--mud-palette-text-secondary); min-width: 0; }
.ff-gd-chip .score { font-variant-numeric: tabular-nums; color: var(--mud-palette-text-primary); font-weight: 700; }
.ff-gd-chip .opp { overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-gd-chip.live { color: #ef4444; }
.ff-gd-chip .live-dot { width: 7px; height: 7px; border-radius: 50%; background: #ef4444; animation: ff-pulse 1.4s ease-in-out infinite; flex: none; }
.ff-gd-chip .poss { color: #10b981; font-weight: 700; } /* has the ball */

/* League board rows (expandable) */
.ff-gd-board-row {
    display: grid; grid-template-columns: 34px 1fr auto; align-items: center; gap: 12px;
    padding: 10px 12px; border-radius: 9px; cursor: pointer;
}
.ff-gd-board-row:hover { background: rgba(var(--mud-palette-primary-rgb), .06); }
.ff-gd-board-row.me { background: rgba(var(--mud-palette-primary-rgb), .13); }
.ff-gd-board-row .rk {
    width: 28px; height: 28px; border-radius: 7px; display: flex; align-items: center; justify-content: center;
    font-size: .78rem; font-weight: 700; font-variant-numeric: tabular-nums;
    background: var(--mud-palette-background); color: var(--mud-palette-text-secondary);
}
.ff-gd-board-row.r1 .rk { background: #d4af37; color: #231d00; }
.ff-gd-board-row.r2 .rk { background: #aab2bd; color: #1b1f24; }
.ff-gd-board-row.r3 .rk { background: #cd7f4a; color: #fff; }
.ff-gd-board-main { min-width: 0; }
.ff-gd-board-main .who { font-weight: 600; font-size: .9rem; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-gd-board-main .who .metag { font-size: .68rem; font-weight: 700; color: var(--mud-palette-primary); margin-left: 6px; letter-spacing: .04em; }
.ff-gd-board-main .sub { font-size: .72rem; color: var(--mud-palette-text-secondary); margin-top: 2px; display: flex; flex-wrap: wrap; gap: 4px 10px; }
.ff-gd-board-main .sub .live { color: #ef4444; font-weight: 700; }
.ff-gd-board-row .pts { font-variant-numeric: tabular-nums; font-weight: 700; font-size: .95rem; }
.ff-gd-board-slots { padding: 2px 6px 10px 40px; }

/* Player-hub form badge (hot / cold) + panel note */
.ff-form-badge {
    display: inline-flex; align-items: center; gap: 4px;
    font-size: .68rem; font-weight: 700; letter-spacing: .06em; text-transform: uppercase;
    padding: 3px 10px; border-radius: 999px; color: #fff;
}
.ff-form-badge.hot { background: #f97316; }
.ff-form-badge.cold { background: #3b82f6; }
.ff-form-badge .mud-icon-root { font-size: 1rem; }
.ff-panel-sub-note { font-size: .75rem; color: var(--mud-palette-text-secondary); }
.ff-splits-label { font-size: .7rem; text-transform: uppercase; letter-spacing: .06em; color: var(--mud-palette-text-secondary); margin: 12px 0 4px; font-weight: 600; }
.ff-splits-label:first-child { margin-top: 0; }

/* Draft Board (Phase L2) */
.ff-rank-player { display: inline-flex; align-items: center; gap: 8px; cursor: pointer; }
.ff-rank-player:hover .nm { text-decoration: underline; }
.ff-rank-player .nm { font-weight: 600; }
.ff-rank-player .muted { font-size: .8rem; }
.ff-tier { display: inline-block; font-size: .68rem; font-weight: 700; padding: 2px 7px; border-radius: 6px; letter-spacing: .03em; }
.ff-tier.t1 { background: #d4af37; color: #231d00; }
.ff-tier.t2 { background: rgba(var(--mud-palette-primary-rgb), .18); color: var(--mud-palette-primary); }
.ff-tier.t3 { background: var(--mud-palette-background); color: var(--mud-palette-text-secondary); }
.ff-tier.t4, .ff-tier.t5 { background: var(--mud-palette-background); color: var(--mud-palette-text-secondary); opacity: .7; }

/* AI forecast (Phase L3) */
.ff-forecast { font-size: .92rem; line-height: 1.6; color: var(--mud-palette-text-primary); }
.ff-forecast strong { color: var(--mud-palette-primary); }
.ff-forecast-foot { margin-top: 12px; font-size: .72rem; color: var(--mud-palette-text-secondary); font-style: italic; }

/* Hub tiles (Phase 13C) â€” the Admin/Commissioner dashboards */
.ff-hub-tile { padding: 14px 16px; height: 100%; cursor: pointer; transition: transform .12s ease, box-shadow .12s ease; }
.ff-hub-tile:hover { transform: translateY(-2px); box-shadow: 0 4px 14px rgba(0, 0, 0, .25); }

/* Weekly draft-conference chips (13F) â€” wrap cleanly at 360px */
.ff-conf-chips { display: flex; flex-wrap: wrap; gap: 6px; }

/* Platform settings console rows (Phase 13D) */
.ff-setting-row { display: flex; align-items: center; justify-content: space-between; gap: 12px; padding: 10px 16px; flex-wrap: wrap; }
.ff-setting-main { flex: 1 1 320px; min-width: 0; }
.ff-setting-editor { display: flex; align-items: center; gap: 4px; flex: 0 0 auto; }

/* AI league content markdown (Phase 11D) â€” the MarkdownLite output on League Buzz */
.ff-md { font-size: .95rem; line-height: 1.65; color: var(--mud-palette-text-primary); }
.ff-md p { margin: 0 0 10px; }
.ff-md p:last-child { margin-bottom: 0; }
.ff-md h5 { margin: 12px 0 6px; font-size: 1rem; font-weight: 700; color: var(--mud-palette-primary); }
.ff-md h5:first-child { margin-top: 0; }
.ff-md ol, .ff-md ul { margin: 0 0 10px; padding-left: 22px; display: flex; flex-direction: column; gap: 6px; }
.ff-md li { line-height: 1.55; }
.ff-md strong { color: var(--mud-palette-primary); }

/* Structured AI forecast (Phase L3 Part 2) */
.ff-fc-top { display: flex; align-items: center; gap: 16px; flex-wrap: wrap; margin-bottom: 10px; }
.ff-fc-proj { display: flex; flex-direction: column; line-height: 1.1; }
.ff-fc-proj-val { font-size: 1.7rem; font-weight: 700; color: var(--mud-palette-primary); }
.ff-fc-proj-val.sm { font-size: 1.05rem; font-weight: 600; }
.ff-fc-proj-lbl { font-size: .7rem; color: var(--mud-palette-text-secondary); text-transform: uppercase; letter-spacing: .05em; margin-top: 2px; }
.ff-fc-reason { font-size: .9rem; line-height: 1.55; color: var(--mud-palette-text-primary); margin-bottom: 10px; }
.ff-fc-drivers { margin: 0; padding-left: 18px; display: flex; flex-direction: column; gap: 6px; }
.ff-fc-drivers li { font-size: .88rem; line-height: 1.5; color: var(--mud-palette-text-primary); }
.ff-fc-drivers li::marker { color: var(--mud-palette-primary); }

/* In-draft intelligence (Phase 8) */
.ff-draft-intel { border-left: 3px solid var(--mud-palette-primary); }
.ff-draft-rec { display: flex; align-items: center; gap: 14px; padding: 10px 12px; border-radius: 8px;
    background: var(--mud-palette-background-gray); flex-wrap: wrap; }
.ff-draft-rec-body { flex: 1 1 200px; min-width: 0; }
.ff-draft-rec-lbl { font-size: .68rem; text-transform: uppercase; letter-spacing: .05em; color: var(--mud-palette-text-secondary); }
.ff-draft-rec-name { font-size: 1.15rem; font-weight: 700; color: var(--mud-palette-text-primary); line-height: 1.2; }
.ff-draft-rec-meta { font-size: .8rem; color: var(--mud-palette-text-secondary); margin-top: 2px; }
.ff-draft-slot { font-weight: 700; color: var(--mud-palette-primary); margin-right: 4px; }
.ff-draft-src { font-style: italic; }
.ff-draft-rec-reason { font-size: .82rem; color: var(--mud-palette-text-primary); margin-top: 4px; }
.ff-draft-board { display: flex; flex-direction: column; margin-top: 4px; }
/* Fixed grid tracks so tier / name / position / school / trend / value / action line up down
   every row, regardless of how long a school name is. name + school flex; the rest are fixed. */
.ff-draft-row { display: grid; align-items: center; gap: 8px; padding: 4px 2px;
    grid-template-columns: 30px minmax(0, 1.4fr) 46px minmax(0, 1fr) 46px 50px 84px;
    border-bottom: 1px solid var(--mud-palette-lines-default); font-size: .85rem;
    border-left: 2px solid transparent; }
.ff-draft-row:last-child { border-bottom: none; }
.ff-draft-row.sel { background: rgba(118, 120, 237, .12); border-left-color: var(--mud-palette-success); }
/* Audit F9: the ellipsis trio MOVED to .ff-draft-pname-txt (see the appended block at the end of this
   file). It stayed here while the T2 class mark rode inside this element, so a long name truncated the
   mark first. Only the type and the width behaviour belong to the anchor now. */
.ff-draft-pname { font-weight: 600; color: var(--mud-palette-text-primary); text-decoration: none;
    min-width: 0; }
.ff-draft-pname:hover { color: var(--mud-palette-primary); text-decoration: underline; }
/* T-34: a row the viewer can no longer roster stays VISIBLE (the landscape is worth scanning) but its
   controls are off and the reason is spelled out under the name â€” a title tooltip alone is invisible
   on the phones members actually draft from. The name cell becomes a two-line stack for that. */
.ff-draft-nmcell { display: flex; flex-direction: column; justify-content: center; min-width: 0; line-height: 1.15; }
.ff-draft-why { font-size: .62rem; color: var(--mud-palette-text-secondary);
    min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-draft-row.blocked .ff-draft-pname,
.ff-draft-row.blocked .ff-draft-pos,
.ff-draft-row.blocked .ff-draft-team,
.ff-draft-row.blocked .ff-draft-val { opacity: .6; }
.ff-draft-pos { font-weight: 700; color: var(--mud-palette-text-secondary); }
.ff-draft-team { color: var(--mud-palette-text-secondary);
    min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-draft-trend { font-size: .66rem; font-weight: 700; text-transform: uppercase; text-align: center;
    padding: 1px 0; border-radius: 4px; }
.ff-draft-trend.hot { color: var(--mud-palette-error); background: rgba(244, 67, 54, .14); }
.ff-draft-trend.cold { color: var(--mud-palette-info); background: rgba(33, 150, 243, .14); }
.ff-draft-trend:empty { background: none; }
.ff-draft-val { font-weight: 700; color: var(--mud-palette-primary); text-align: right; }
.ff-draft-action { display: flex; align-items: center; justify-content: flex-end; gap: 2px; }
/* 41: the action cell can hold the quick-add (+) and, on your turn, the select control. Tighten the
   icon buttons so both fit the fixed track without widening the row. */
.ff-draft-action .mud-icon-button { padding: 4px; }
.ff-draft-recdot { color: #f2b807; font-size: .9rem; line-height: 1; }
.ff-draft-recbadge { display: inline-block; margin-left: 8px; padding: 1px 7px; border-radius: 10px;
    font-size: .62rem; font-weight: 700; letter-spacing: .03em; color: #f2b807;
    background: rgba(242, 184, 7, .14); vertical-align: middle; }
.ff-draft-reset { margin-top: 4px; text-transform: none; }
.ff-trend-short { display: none; }
.ff-back-btn { text-transform: none; }

/* Draft-pool typeahead options: fixed position chip, name, then muted school/conf Â· value. */
.ff-pool-opt { display: flex; align-items: baseline; gap: 8px; width: 100%; min-width: 0; }
.ff-pool-pos { flex: 0 0 34px; font-weight: 700; font-size: .72rem; color: var(--mud-palette-text-secondary); }
.ff-pool-name { font-weight: 600; color: var(--mud-palette-text-primary);
    min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-pool-meta { margin-left: auto; padding-left: 8px; font-size: .78rem; white-space: nowrap;
    color: var(--mud-palette-text-secondary); }

/* Autodraft opt-in row in the draft-intelligence card. */
.ff-autodraft-row { display: flex; align-items: center; flex-wrap: wrap; gap: 2px 12px;
    padding: 4px 10px; border-radius: 8px; background: rgba(118, 120, 237, .06); }

/* "Your team so far" strip in the draft Room â€” the 5 slots filling as you draft.
   T-33: each slot is a CHIP that sizes to its own content and wraps onto another line rather than
   truncating a drafted name to "Devon...". No fixed name width any more; the only cap is the strip
   itself, so a pathological surname ellipsizes instead of overflowing. */
.ff-teamstrip { display: flex; flex-wrap: wrap; align-items: center; gap: 6px 8px; padding: 8px 12px;
    margin-bottom: 16px; border-radius: 10px; background: var(--mud-palette-background-gray); }
.ff-teamstrip-lbl { font-size: .72rem; font-weight: 700; text-transform: uppercase; letter-spacing: .04em;
    color: var(--mud-palette-text-secondary); }
.ff-teamstrip-slot { display: inline-flex; align-items: center; gap: 6px; min-width: 0; max-width: 100%;
    padding: 2px 9px 2px 3px; border-radius: 999px; background: var(--mud-palette-surface);
    border: 1px solid var(--mud-palette-lines-default); }
/* The position badge keeps its natural size inside the chip (the shared .ff-pos.inrow rule stretches
   it to 100% for the fixed-grid rows it was written for). */
.ff-teamstrip-slot .ff-pos { flex: 0 0 auto; width: auto; min-width: 32px; padding: 2px 6px; }
.ff-teamstrip-name { font-size: .82rem; font-weight: 600; color: var(--mud-palette-text-primary);
    min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-teamstrip-slot.empty { background: none; border-style: dashed; }
.ff-teamstrip-slot.empty .ff-teamstrip-name { color: var(--mud-palette-text-disabled); font-weight: 400; }

/* Mobile: keep every player on ONE row â€” smaller text, tighter columns, and H/C instead of HOT/COLD.
   Name + position stay full-size priority; school truncates. */
@media (max-width: 640px) {
    .ff-draft-row {
        grid-template-columns: 24px minmax(0, 2fr) 30px minmax(0, 0.8fr) 20px 40px 64px;
        gap: 5px; font-size: .78rem; padding: 5px 2px;
    }
    /* 41: keep the two action controls on one row at phone widths. */
    .ff-draft-action { gap: 1px; }
    .ff-draft-action .mud-icon-button { padding: 2px; }
    .ff-draft-action .mud-icon-button .mud-icon-root { font-size: 1.05rem; }
    .ff-draft-trend { padding: 0; }
    .ff-trend-full { display: none; }
    .ff-trend-short { display: inline; }
    .ff-draft-row .ff-tier { padding: 1px 4px; font-size: .62rem; }
    .ff-draft-why { font-size: .58rem; }
    .ff-draft-rec { padding: 8px 10px; }
    .ff-draft-rec-name { font-size: 1.05rem; }
}
.ff-kv .muted { color: var(--mud-palette-text-secondary); font-weight: 400; font-size: .74rem; }

/* Compact data tables (player hub game log / season summary) */
.ff-table-scroll { overflow-x: auto; }
.ff-table { width: 100%; border-collapse: collapse; font-size: .84rem; }
.ff-table th, .ff-table td { padding: 8px 12px; text-align: left; white-space: nowrap; border-bottom: 1px solid var(--mud-palette-lines-default); }
.ff-table th { color: var(--mud-palette-text-secondary); font-weight: 600; font-size: .72rem; text-transform: uppercase; letter-spacing: .04em; }
.ff-table td.num, .ff-table th.num { text-align: right; font-variant-numeric: tabular-nums; }
.ff-table td.strong { font-weight: 700; }
.ff-table tbody tr:last-child td { border-bottom: 0; }
.ff-table tbody tr:hover { background: rgba(var(--mud-palette-primary-rgb), .05); }

/* ============================================================
   Data-Viz Foundation â€” chart host.
   ============================================================ */
.ff-chart { position: relative; width: 100%; }
.ff-chart-empty {
    display: flex; align-items: center; justify-content: center; height: 100%;
    color: var(--mud-palette-text-secondary); font-size: .85rem; text-align: center; padding: 12px;
}
.ff-spark-empty { color: var(--mud-palette-text-secondary); }
.ff-table td.spark { width: 120px; padding-top: 2px; padding-bottom: 2px; }

/* League onboarding + switcher (Phase 9E1) */
.ff-league-head { display: flex; align-items: flex-start; justify-content: space-between; gap: 16px; flex-wrap: wrap; }
.ff-league-actions { display: flex; align-items: center; gap: 8px; flex-wrap: wrap; }
.ff-league-grid { display: grid; grid-template-columns: repeat(auto-fit, minmax(min(100%, 280px), 1fr)); gap: 16px; }
.ff-league-card { min-width: 0; }
.ff-league-card-head { display: flex; align-items: flex-start; justify-content: space-between; gap: 12px; }
/* .ff-league-empty removed 2026-07-31: the My Leagues empty card joined the shared NoLeagueState
   funnel (scoped styling in NoLeagueState.razor.css). */
.ff-league-switcher { margin-left: 12px; min-width: 0; max-width: min(34vw, 280px); }
.ff-league-switcher .mud-button-label { min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-onboarding { margin-top: 24px; }
.ff-wizard-steps { display: flex; gap: 8px; flex-wrap: wrap; margin-bottom: 16px; }
.ff-wizard-steps span { color: var(--mud-palette-text-secondary); border: 1px solid var(--mud-palette-lines-default); border-radius: 999px; padding: 5px 11px; font-size: .78rem; }
.ff-wizard-steps span.active { color: var(--mud-palette-primary); border-color: var(--mud-palette-primary); font-weight: 700; }
.ff-wizard-steps span.done { color: var(--mud-palette-success); border-color: var(--mud-palette-success); }
.ff-slot-grid { display: grid; grid-template-columns: repeat(auto-fit, minmax(110px, 1fr)); gap: 12px; }
.ff-review-grid { display: grid; grid-template-columns: repeat(auto-fit, minmax(130px, 1fr)); gap: 12px; }
.ff-review-grid div { display: flex; flex-direction: column; padding: 12px; border-radius: 9px; background: var(--mud-palette-background-gray); }
.ff-review-grid span { color: var(--mud-palette-text-secondary); font-size: .72rem; text-transform: uppercase; letter-spacing: .04em; }
.ff-wizard-actions { padding: 0 16px 16px; }
.ff-unpaid-gate { max-width: 620px; }
.ff-invite-code { letter-spacing: .14em; font-family: ui-monospace, SFMono-Regular, Consolas, monospace; }
.ff-commissioner-dashboard { margin-bottom: 28px; }
.ff-league-stat-grid { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 12px; }
.ff-league-stat-grid div { display: flex; flex-direction: column; padding: 10px; border-radius: 8px; background: var(--mud-palette-background-gray); }
.ff-league-stat-grid span { color: var(--mud-palette-text-secondary); font-size: .72rem; text-transform: uppercase; }
.ff-form-grid { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 16px; }
.ff-league-admin-grid { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 16px; }
.ff-member-list { display: grid; grid-template-columns: repeat(auto-fit, minmax(min(100%, 300px), 1fr)); gap: 12px; }
.ff-member-card { min-width: 0; }
.ff-member-head { display: flex; align-items: flex-start; justify-content: space-between; gap: 12px; }
.ff-member-ident { display: flex; align-items: center; gap: 12px; min-width: 0; } /* Phase 15B: avatar + name */
.ff-member-ident > div { min-width: 0; }
.ff-member-badges { display: flex; justify-content: flex-end; gap: 6px; flex-wrap: wrap; }
.ff-member-actions { flex-wrap: wrap; }
.ff-invite-list { display: grid; gap: 10px; }
.ff-invite-row .mud-card-content { display: flex; align-items: center; justify-content: space-between; gap: 12px; }

@media (max-width: 600px) {
    .ff-app-title { display: none; }
    .ff-league-switcher { margin-left: 2px; max-width: 42vw; }
    .ff-onboarding { margin-top: 8px; padding-left: 0; padding-right: 0; }
    .ff-league-actions { width: 100%; }
    .ff-league-actions .mud-button-root { flex: 1; }
    .ff-form-grid, .ff-league-admin-grid { grid-template-columns: 1fr; }
    .ff-invite-row .mud-card-content { align-items: flex-start; flex-direction: column; }
}

/* ============================================================
   Phase 18A â€” shared refresh kit: attribution rows, week-vs-average
   strip, Player Detail hero total, and the MatchupChip label toggle.
   ============================================================ */

/* Attribution rows â€” the compact "stat Â· value Â· +pts" successor to the zero-tile wall.
   Single column at every width; points column is fixed-width so the +/- signs line up. */
.ff-attr-list { margin: 4px 0 8px; }
.ff-attr-row {
    display: grid; grid-template-columns: 1fr auto auto; align-items: baseline; gap: 14px;
    padding: 9px 2px; border-bottom: 1px solid var(--mud-palette-lines-default);
}
.ff-attr-row:last-child { border-bottom: 0; }
.ff-attr-stat { color: var(--mud-palette-text-secondary); font-size: .85rem; min-width: 0; }
.ff-attr-val { font-weight: 600; font-size: .95rem; font-variant-numeric: tabular-nums; text-align: right; }
.ff-attr-pts {
    font-variant-numeric: tabular-nums; font-weight: 700; font-size: .85rem;
    min-width: 62px; text-align: right; cursor: default;
}
.ff-attr-pts.pos { color: var(--mud-palette-success); }
.ff-attr-pts.neg { color: var(--mud-palette-error); }

/* Week-vs-season-average strip â€” three cells (this week / season avg / Î”), wrapping on phones. */
.ff-wva { display: flex; flex-wrap: wrap; gap: 10px; margin: 16px 0; }
.ff-wva-cell {
    flex: 1 1 92px; text-align: center; padding: 10px 12px; border-radius: 10px;
    background: var(--mud-palette-background-gray); border: 1px solid var(--mud-palette-lines-default);
}
.ff-wva-cell .k {
    display: block; color: var(--mud-palette-text-secondary); font-size: .68rem;
    text-transform: uppercase; letter-spacing: .05em;
}
.ff-wva-cell .v { display: block; font-weight: 700; font-size: 1.2rem; font-variant-numeric: tabular-nums; margin-top: 4px; }
.ff-wva-cell .v.pos { color: var(--mud-palette-success); }
.ff-wva-cell .v.neg { color: var(--mud-palette-error); }
.ff-wva-note { color: var(--mud-palette-text-secondary); font-size: .82rem; margin: 12px 2px; }

/* Player Detail hero: the season total sits at the trailing edge of the title row. */
.ff-detail-total { margin-left: auto; text-align: right; line-height: 1.05; }
.ff-detail-total .n { display: block; font-size: 1.9rem; font-weight: 800; font-variant-numeric: tabular-nums; }
.ff-detail-total .l { display: block; color: var(--mud-palette-text-secondary); font-size: .68rem; text-transform: uppercase; letter-spacing: .05em; }

.ff-attr-head { font-size: .72rem; text-transform: uppercase; letter-spacing: .04em; color: var(--mud-palette-text-secondary); font-weight: 600; margin: 18px 2px 2px; }

/* MatchupChip responsive label (the Â§2.3 fix): the full band word shows â‰¥600px, glyph+score below.
   Without these rules both spans rendered together â€” the documented toggle was never wired. */
.ff-matchup-short { display: none; }
@media (max-width: 599.98px) {
    .ff-matchup-full { display: none; }
    .ff-matchup-short { display: inline; }
}

/* ============================================================
   ---- 18D: scoreboard ----
   The league-race board (ScoreboardBoard.razor) across all three tabs: medal ranks + avatars +
   linkified (career) names, a gap-to-leader + signed delta-vs-last-week caption, an expandable
   lineup (Q7), a Season-tab sparkline, and a Total-Wins streak flame. Mobile-first at 360px:
   one-line rows, tap-to-expand; the sparkline appears only â‰¥600px where the row has room. Built on
   the MudBlazor palette vars so it auto-themes; medal + roster idioms mirror the ff-standing/
   ff-roster-row layers this page used to render flat.
   ============================================================ */

.ff-sb-list { display: flex; flex-direction: column; gap: 3px; }
.ff-sb-row { border-radius: 10px; }

/* Row header: a flex line so the optional sparkline slots in without breaking alignment. */
.ff-sb-main {
    width: 100%; display: flex; align-items: center; gap: 10px;
    padding: 9px 10px; border-radius: 10px;
    background: none; border: 0; text-align: left; color: inherit; font: inherit;
}
.ff-sb-main.clickable { cursor: pointer; }
.ff-sb-main.clickable:hover { background: rgba(var(--mud-palette-primary-rgb), .06); }
.ff-sb-main:focus-visible { outline: 2px solid var(--mud-palette-primary); outline-offset: -2px; }
.ff-sb-row.me .ff-sb-main { background: rgba(var(--mud-palette-primary-rgb), .13); }

.ff-sb-rank {
    flex: 0 0 auto; width: 26px; height: 26px; border-radius: 7px;
    display: flex; align-items: center; justify-content: center;
    font-size: .78rem; font-weight: 700; font-variant-numeric: tabular-nums;
    background: var(--mud-palette-background); color: var(--mud-palette-text-secondary);
}
/* Medals for the top three (same palette as the ff-standing medals). */
.ff-sb-rank.r1 { background: #d4af37; color: #231d00; }
.ff-sb-rank.r2 { background: #aab2bd; color: #1b1f24; }
.ff-sb-rank.r3 { background: #cd7f4a; color: #fff; }

.ff-sb-who { flex: 1 1 auto; display: flex; align-items: center; gap: 9px; min-width: 0; }
.ff-sb-av { width: 30px; height: 30px; min-width: 30px; font-size: .7rem; }
.ff-sb-whotext { min-width: 0; display: flex; flex-direction: column; gap: 1px; }
.ff-sb-nameline { display: flex; align-items: center; gap: 6px; min-width: 0; }
.ff-sb-namewrap { min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-sb-name { font-weight: 600; font-size: .9rem; }
/* The name links to a career page but stays visually quiet in a dense list (Batch B convention). */
.ff-sb-name.ff-link { color: inherit; font-weight: 600; }
.ff-sb-name.ff-link:hover { color: var(--mud-palette-primary); }
.ff-sb-you { font-size: .62rem; font-weight: 700; color: var(--mud-palette-primary); letter-spacing: .04em; flex: 0 0 auto; }
.ff-sb-flame { font-size: .72rem; font-weight: 700; flex: 0 0 auto; white-space: nowrap; }

.ff-sb-meta { display: flex; flex-wrap: wrap; gap: 2px 10px; font-size: .72rem; color: var(--mud-palette-text-secondary); }
.ff-sb-delta { font-variant-numeric: tabular-nums; }
.ff-sb-delta.pos { color: var(--mud-palette-success); }
.ff-sb-delta.neg { color: var(--mud-palette-error); }

.ff-sb-spark { display: none; flex: 0 0 66px; width: 66px; }
.ff-sb-val { flex: 0 0 auto; font-variant-numeric: tabular-nums; font-weight: 700; font-size: .95rem; text-align: right; }
.ff-sb-chev { flex: 0 0 auto; display: flex; justify-content: center; width: 22px; color: var(--mud-palette-text-secondary); transition: transform .15s ease; }
.ff-sb-chev.open { transform: rotate(180deg); }
.ff-sb-chev-spacer { flex: 0 0 auto; width: 22px; }

/* Expanded lineup â€” indented under the row, reusing the ff-roster-row idiom. */
.ff-sb-panel { padding: 2px 8px 10px 44px; }
.ff-sb-lineup-loading { display: flex; justify-content: center; padding: 12px; }
.ff-sb-lineup-empty { padding: 10px 2px; color: var(--mud-palette-text-secondary); font-size: .85rem; }

/* The sparkline only earns its place where the row has width (matrix: rows + sparkline at â‰¥600px). */
@media (min-width: 600px) { .ff-sb-spark { display: block; } }
/* ---- 18E: leagues pages ---- */
/* Richer My Leagues cards + a hero on the League overview. Everything here is composed from data
   already on the read DTOs (member fill, current-league identities, the current-week lock) â€” no new
   server aggregates (Â§11 Q2). One self-contained block per CSS discipline. */

/* Membership card: stacked, evenly-spaced content so the meter/avatars/draft line breathe. */
.ff-league-card-rich .mud-card-content { display: flex; flex-direction: column; gap: 12px; }
.ff-league-card-current { border-color: var(--mud-palette-primary); }
.ff-lc-title { min-width: 0; }
.ff-lc-meta { display: flex; align-items: center; flex-wrap: wrap; gap: 6px; font-size: .8rem; margin-top: 2px; }
.ff-lc-sep { opacity: .55; }
.ff-lc-team { min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }

/* Members-fill meter â€” MemberCount / MaxMembers straight off the DTO. */
.ff-lc-fill { display: flex; flex-direction: column; gap: 6px; }
.ff-lc-fill-head { display: flex; align-items: baseline; justify-content: space-between; }
.ff-lc-fill-head span { text-transform: uppercase; letter-spacing: .05em; font-size: .68rem; }
.ff-lc-fill-head strong { font-size: .82rem; font-variant-numeric: tabular-nums; }
.ff-lc-bar { height: 6px; border-radius: 999px; background: var(--mud-palette-lines-default); overflow: hidden; }
.ff-lc-bar > span { display: block; height: 100%; border-radius: inherit; background: var(--mud-palette-primary); transition: width .3s ease; }
.ff-lc-bar-lg { height: 8px; }

/* Overlapping avatar preview (current league only â€” identities are current-league-scoped). */
.ff-lc-avatars { display: flex; align-items: center; }
.ff-lc-av { margin-left: -6px; border: 2px solid var(--mud-palette-surface); }
.ff-lc-av:first-child { margin-left: 0; }
.ff-lc-av-more { margin-left: 8px; font-size: .75rem; color: var(--mud-palette-text-secondary); font-weight: 600; }

.ff-lc-draft { display: flex; align-items: center; gap: 6px; margin-top: auto; }
.ff-lc-draft-icon { font-size: 1rem !important; }

/* Overview hero â€” a primary gradient banner replacing the plain page head. */
.ff-league-hero {
    border-radius: 16px; padding: 22px 24px; margin-bottom: 22px; color: #fff;
    background: linear-gradient(135deg, var(--mud-palette-primary), var(--mud-palette-primary-darken, #C74A00));
}
.ff-league-hero-body { display: flex; align-items: flex-start; justify-content: space-between; gap: 16px; flex-wrap: wrap; }
.ff-league-hero-id { min-width: 0; }
.ff-league-hero-name { color: #fff; font-weight: 700; letter-spacing: -.01em; }
.ff-league-hero-meta { display: flex; align-items: center; flex-wrap: wrap; gap: 8px; margin-top: 6px; color: rgba(255, 255, 255, .85); font-size: .9rem; }
.ff-league-hero-avatars { display: flex; align-items: center; margin-top: 14px; }
.ff-league-hero .ff-lc-av { border-color: rgba(255, 255, 255, .55); }
.ff-league-hero .ff-lc-av-more { color: rgba(255, 255, 255, .9); }
.ff-league-hero .ff-league-actions .mud-button-outlined { color: #fff; border-color: rgba(255, 255, 255, .55); }
/* White CTA reads clearly on the indigo gradient (primary-on-primary would vanish). */
.ff-league-hero .ff-league-actions .mud-button-filled { background: #fff; color: var(--mud-palette-primary); }

.ff-league-card-accent { border-color: var(--mud-palette-primary); }

/* Invite code + copy button on one line, wrapping on phones. */
.ff-invite-row2 { display: flex; align-items: center; gap: 14px; flex-wrap: wrap; margin: 4px 0 2px; }

@media (max-width: 599.98px) {
    .ff-league-hero { padding: 18px; }
    .ff-league-hero-body { flex-direction: column; }
    .ff-league-hero .ff-league-actions { width: 100%; }
    .ff-league-hero .ff-league-actions .mud-button-root { flex: 1; }
}

/* ---- 18B: draft hub segments ---- */
/* My Team â€” the "your week" metrics panel below the lineup card (rank + delta, best/worst slot, season
   sparkline). All theme-var driven; wraps to one column on phones. */
.ff-mt-week { max-width: 720px; margin-top: 16px; }
.ff-mt-tiles { display: flex; flex-wrap: wrap; gap: 10px; }
.ff-mt-tile {
    flex: 1 1 120px; padding: 10px 12px; border-radius: 10px;
    background: var(--mud-palette-background-gray); border: 1px solid var(--mud-palette-lines-default);
}
.ff-mt-tile .k {
    display: block; color: var(--mud-palette-text-secondary); font-size: .68rem;
    text-transform: uppercase; letter-spacing: .05em;
}
.ff-mt-tile .v { display: block; font-weight: 800; font-size: 1.35rem; font-variant-numeric: tabular-nums; margin-top: 2px; }
.ff-mt-tile .v .of { font-size: .8rem; font-weight: 600; color: var(--mud-palette-text-secondary); }
.ff-mt-tile .v.pos { color: var(--mud-palette-success); }
.ff-mt-tile .v.neg { color: var(--mud-palette-error); }
.ff-mt-tile .v.even { color: var(--mud-palette-text-secondary); }
.ff-mt-callouts { display: flex; flex-wrap: wrap; gap: 8px; margin-top: 12px; }
.ff-mt-callout {
    display: inline-flex; align-items: center; gap: 6px; padding: 5px 10px; border-radius: 999px;
    font-size: .8rem; border: 1px solid var(--mud-palette-lines-default);
}
.ff-mt-callout .ff-pos { width: auto; min-width: 30px; padding: 2px 7px; font-size: .58rem; }
.ff-mt-callout b { font-variant-numeric: tabular-nums; }
.ff-mt-callout.best { background: rgba(76, 175, 80, .10); }
.ff-mt-callout.worst { background: rgba(244, 67, 54, .08); }
.ff-mt-spark { display: flex; align-items: center; gap: 12px; margin-top: 16px; }
.ff-mt-spark .k {
    flex: 0 0 auto; color: var(--mud-palette-text-secondary); font-size: .68rem;
    text-transform: uppercase; letter-spacing: .05em;
}
.ff-mt-spark-wrap { flex: 1 1 auto; min-width: 0; }

/* Queue â€” card rows: [drag] [pos pill] [name + meta (+ matchup chip)] [up / down / delete]. Queue
   behavior is unchanged; this block only restyles the row (18B is visual-only for the queue). */
.ff-q-list { display: flex; flex-direction: column; gap: 8px; }
.ff-q-row {
    display: grid; grid-template-columns: 22px 44px 1fr auto; align-items: center; gap: 10px;
    padding: 8px 12px; border-radius: 10px; background: var(--mud-palette-surface);
    border: 1px solid var(--mud-palette-lines-default);
}
.ff-q-drag { flex: 0 0 auto; cursor: grab; }
.ff-q-row > .ff-pos { min-width: 44px; }
.ff-q-main { min-width: 0; }
.ff-q-name { font-weight: 600; font-size: .9rem; white-space: nowrap; overflow: hidden; text-overflow: ellipsis; }
.ff-q-meta {
    display: flex; align-items: center; gap: 8px; flex-wrap: wrap;
    font-size: .74rem; color: var(--mud-palette-text-secondary);
}
.ff-q-meta > span { overflow: hidden; text-overflow: ellipsis; white-space: nowrap; min-width: 0; }
.ff-q-actions { display: inline-flex; align-items: center; flex: 0 0 auto; }
@media (max-width: 400px) {
    .ff-q-row { grid-template-columns: 18px 38px 1fr auto; gap: 6px; padding: 8px 8px; }
    .ff-mt-tile { flex-basis: 100px; }
}

/* ---- 18C: game day ----
   The Game Day facelift (Phase 18.4). Layers over the existing .ff-gd-* live layer (Â§2.1): a league
   mini-ticker, a rich pre-kickoff / off-season hero, rank-movement chips (Â§11 Q5), avatars on the
   board rows, and a projected-vs-actual pace strip + per-slot "projected remaining" (research-on
   only, Â§3.2/Â§3.4). All theme-var-driven; mobile-first (single column, chips wrap) at 360px. */

/* League mini-ticker â€” a compact strip of live/final/upcoming counts + the current leader. */
.ff-gd-ticker {
    display: flex; flex-wrap: wrap; align-items: center; gap: 8px 14px;
    margin: 0 0 18px; padding: 11px 14px; border-radius: 12px;
    background: var(--mud-palette-background-gray); border: 1px solid var(--mud-palette-lines-default);
}
.ff-gd-ticker .tk {
    display: inline-flex; align-items: center; gap: 6px;
    font-size: .95rem; font-weight: 700; font-variant-numeric: tabular-nums;
}
.ff-gd-ticker .tk em { font-style: normal; font-weight: 500; font-size: .78rem; color: var(--mud-palette-text-secondary); }
.ff-gd-ticker .tk .dot { width: 8px; height: 8px; border-radius: 50%; background: var(--mud-palette-text-disabled); }
.ff-gd-ticker .tk.live.on { color: #ef4444; }
.ff-gd-ticker .tk.live.on .dot { background: #ef4444; animation: ff-pulse 1.4s ease-in-out infinite; }
.ff-gd-ticker .tk.lead { margin-left: auto; font-weight: 500; font-size: .82rem; color: var(--mud-palette-text-secondary); }
.ff-gd-ticker .tk.lead strong { color: var(--mud-palette-text-primary); }
.ff-gd-ticker .tk.lead .mud-icon-root { font-size: 1.05rem; color: #d4af37; }
@media (max-width: 599.98px) {
    .ff-gd-ticker .tk.lead { margin-left: 0; flex-basis: 100%; }
}

/* Pre-kickoff / off-season hero â€” the first-class case (most visits are non-gameday). */
.ff-gd-hero {
    display: flex; gap: 18px; align-items: flex-start;
    padding: 22px; border-radius: 16px; margin-bottom: 20px;
    background: linear-gradient(135deg,
        rgba(var(--mud-palette-primary-rgb), .12), rgba(var(--mud-palette-primary-rgb), .03));
    border: 1px solid rgba(var(--mud-palette-primary-rgb), .22);
}
.ff-gd-hero-badge {
    flex: none; width: 56px; height: 56px; border-radius: 14px;
    display: flex; align-items: center; justify-content: center;
    background: rgba(var(--mud-palette-primary-rgb), .16); color: var(--mud-palette-primary);
}
.ff-gd-hero-badge .mud-icon-root { font-size: 2rem; }
.ff-gd-hero.prekick .ff-gd-hero-badge { animation: ff-pulse 2s ease-in-out infinite; }
.ff-gd-hero-body { min-width: 0; }
.ff-gd-hero-body h2 { margin: 2px 0 6px; font-size: 1.25rem; font-weight: 800; }
.ff-gd-hero-body p { margin: 0; color: var(--mud-palette-text-secondary); font-size: .9rem; line-height: 1.5; }
.ff-gd-hero-actions { display: flex; flex-wrap: wrap; align-items: center; gap: 12px; margin-top: 14px; }
.ff-gd-hero-hint { color: var(--mud-palette-text-secondary); font-size: .82rem; }
.ff-gd-hero-proj { display: flex; flex-wrap: wrap; gap: 10px; margin-top: 14px; }
.ff-gd-hero-proj span {
    display: flex; flex-direction: column; gap: 2px; padding: 8px 16px; border-radius: 10px;
    background: var(--mud-palette-surface); border: 1px solid var(--mud-palette-lines-default);
}
.ff-gd-hero-proj em { font-style: normal; font-size: .66rem; text-transform: uppercase; letter-spacing: .05em; color: var(--mud-palette-text-secondary); }
.ff-gd-hero-proj b { font-size: 1.3rem; font-weight: 800; font-variant-numeric: tabular-nums; }
@media (max-width: 599.98px) {
    .ff-gd-hero { flex-direction: column; gap: 12px; padding: 18px; }
    .ff-gd-hero-badge { width: 48px; height: 48px; }
}

/* Rank-movement chip (My Team head + board rows) â€” up/down/flat vs the last completed week. */
.ff-gd-rankwrap { display: inline-flex; align-items: center; gap: 6px; }
.ff-rankmove {
    display: inline-flex; align-items: center; font-size: .7rem; font-weight: 700;
    font-variant-numeric: tabular-nums; padding: 1px 6px; border-radius: 999px; line-height: 1.4;
}
.ff-rankmove.up { color: #10b981; background: rgba(16, 185, 129, .14); }
.ff-rankmove.down { color: #ef4444; background: rgba(239, 68, 68, .14); }
.ff-rankmove.flat { color: var(--mud-palette-text-secondary); background: var(--mud-palette-background-gray); }

/* My Team projected-vs-actual pace strip (research on): now / projected / on the field. */
.ff-gd-pace {
    display: flex; gap: 10px; margin: 4px 14px 10px; padding-top: 12px;
}
.ff-gd-pace .cell {
    flex: 1 1 0; text-align: center; padding: 8px 6px; border-radius: 10px;
    background: var(--mud-palette-background-gray); border: 1px solid var(--mud-palette-lines-default);
}
.ff-gd-pace .cell.hi { background: rgba(var(--mud-palette-primary-rgb), .1); border-color: rgba(var(--mud-palette-primary-rgb), .28); }
.ff-gd-pace .cell .k { display: block; font-size: .64rem; text-transform: uppercase; letter-spacing: .05em; color: var(--mud-palette-text-secondary); }
.ff-gd-pace .cell .v { display: block; font-weight: 800; font-size: 1.15rem; font-variant-numeric: tabular-nums; margin-top: 3px; }
.ff-gd-pace .cell.hi .v { color: var(--mud-palette-primary); }

/* Per-slot points column: banked total, with projected-remaining beneath it when present. */
.ff-gd-ptcol { display: flex; flex-direction: column; align-items: flex-end; gap: 1px; }
.ff-gd-proj { font-size: .66rem; font-weight: 600; color: var(--mud-palette-primary); font-variant-numeric: tabular-nums; white-space: nowrap; }

/* Board rows gain an avatar column (rk | avatar | who/sub | pts). */
.ff-gd-board-row { grid-template-columns: 30px auto 1fr auto; }
.ff-gd-board-av { flex: none; }
.ff-gd-board-main .sub .proj { color: var(--mud-palette-primary); font-weight: 600; }
/* ---- end 18C ---- */

/* ---- 18H: league buzz ---- */
/* Member League Buzz is a week-at-a-time archive: a bounded week picker, then recap + power ranking
   side-by-side on desktop (.ff-cols already stacks at <=960px), with the awards card beneath. */
.ff-buzz { max-width: 980px; }

.ff-buzz-nav {
    display: flex; align-items: center; gap: 8px; flex-wrap: wrap; margin-bottom: 8px;
}
.ff-buzz-count { margin-left: 4px; }

.ff-buzz-head { margin: 4px 0 12px; font-weight: 700; }

.ff-buzz-cols { margin-bottom: 16px; }
.ff-buzz-awards { max-width: 640px; }

.ff-buzz-card { height: 100%; display: flex; flex-direction: column; }
.ff-buzz-missing { padding: 8px 0; font-style: italic; }

.ff-buzz-loading { display: flex; justify-content: center; padding: 32px 0; }
/* ---- end 18H ---- */

/* ---- 18J: research surfaces ----
   Breakouts (risers + decliners side-by-side on desktop, stacked at <md) and Pool changes (an
   on-page pool-scope banner + one-line per-section explainers). Reuses the global .ff-cols grid
   (2-col â‰¥960px, single column below); the additions here are the 18J-specific hooks. Mobile-first,
   all theme-var-driven; the banner wraps and the columns stack at 360px. */

/* Breakouts two-column board â€” the panels stretch to equal height so the two sides line up. */
.ff-breakouts-cols { margin-bottom: 12px; }
.ff-breakouts-cols > .ff-panel { height: 100%; display: flex; flex-direction: column; }
.ff-breakouts-cols > .ff-panel > .ff-panel-body { flex: 1 1 auto; }

/* Pool-changes scope banner â€” the week's draftable pool, stated on-page. */
.ff-scope-banner {
    display: flex; align-items: center; flex-wrap: wrap; gap: 4px 10px;
    margin: 0 0 16px; padding: 11px 14px; border-radius: 12px;
    background: rgba(var(--mud-palette-primary-rgb), .09);
    border: 1px solid rgba(var(--mud-palette-primary-rgb), .22);
    font-size: .9rem; line-height: 1.4;
}
.ff-scope-banner .mud-icon-root { color: var(--mud-palette-primary); font-size: 1.15rem; flex: none; }
.ff-scope-banner .lbl { color: var(--mud-palette-text-secondary); }
.ff-scope-banner strong { font-weight: 700; }

/* One-line section explainer â€” sits between a panel head and its list. */
.ff-section-explainer {
    padding: 8px 16px; font-size: .8rem; line-height: 1.45;
    color: var(--mud-palette-text-secondary);
    border-bottom: 1px solid var(--mud-palette-lines-default);
}
/* ---- end 18J ---- */

/* ---- 18K: draft board ---- */
/* The Draft Board overhaul (Phase 18.12): equal-height Top-N / movers panels, stronger
   heating-up / cooling-off styling, and a virtualized, filterable, sortable rankings table.
   Client-side only over the already-fetched board (0 new endpoints, Â§11 Q11). Mobile-first:
   filters stack at 360px and the table keeps a horizontal scroll with a sticky first column. */

/* Equal-height top panels â€” the shorter of the two stretches to the row's tallest (MudGrid items
   are align-items:stretch), so the chart and movers panels always match on desktop. */
.ff-18k-eqpanel { height: 100%; display: flex; flex-direction: column; }
.ff-18k-eqpanel > .ff-panel-body { flex: 1 1 auto; min-height: 0; }
.ff-18k-eqpanel .ff-chart { min-height: 320px; }

/* Risers & fallers â€” clear color-blocked headers separate the two sections from their rows. */
.ff-18k-movers { display: flex; flex-direction: column; gap: 14px; }
.ff-18k-mv { border: 1px solid var(--mud-palette-lines-default); border-radius: 12px; overflow: hidden; }
.ff-18k-mv-head {
    display: flex; align-items: center; gap: 7px;
    padding: 8px 12px; font-size: .74rem; font-weight: 800;
    text-transform: uppercase; letter-spacing: .05em;
}
.ff-18k-mv-head .mud-icon-root { font-size: 1.05rem; }
.ff-18k-mv.up .ff-18k-mv-head { color: #0f9d6b; background: rgba(16, 185, 129, .14); border-bottom: 1px solid rgba(16, 185, 129, .28); }
.ff-18k-mv.down .ff-18k-mv-head { color: #d64545; background: rgba(239, 68, 68, .13); border-bottom: 1px solid rgba(239, 68, 68, .26); }
.ff-18k-mv-rows { padding: 2px 12px; }
.ff-18k-mv-row {
    display: flex; align-items: center; justify-content: space-between; gap: 12px;
    padding: 8px 0; border-bottom: 1px solid var(--mud-palette-lines-default); cursor: pointer;
}
.ff-18k-mv-row:last-child { border-bottom: 0; }
.ff-18k-mv-row:hover .who { text-decoration: underline; }
.ff-18k-mv-row .who { font-size: .86rem; font-weight: 600; min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-18k-mv-row .who .muted { color: var(--mud-palette-text-secondary); font-weight: 400; font-size: .76rem; }
.ff-18k-mv-row .delta { font-weight: 700; font-size: .9rem; font-variant-numeric: tabular-nums; flex: none; }
.ff-18k-mv-row .delta.pos { color: var(--mud-palette-success); }
.ff-18k-mv-row .delta.neg { color: var(--mud-palette-error); }
.ff-18k-mv-empty { padding: 8px 0; color: var(--mud-palette-text-secondary); font-size: .8rem; font-style: italic; }

/* Filter toolbar â€” a row of controls that wraps, then stacks full-width on small screens. */
.ff-18k-filters { display: flex; flex-wrap: wrap; align-items: center; gap: 10px; padding: 6px 6px 12px; }
.ff-18k-filters .ff-18k-f-search { flex: 2 1 220px; min-width: 160px; }
.ff-18k-filters .ff-18k-f-conf { flex: 1 1 170px; min-width: 150px; }
.ff-18k-filters .ff-18k-f-min { flex: 0 1 120px; min-width: 100px; }
.ff-18k-filters .ff-18k-f-reset { flex: none; text-transform: none; margin-left: auto; }

/* Bounded, scrollable table body so virtualization keeps the DOM small; header sticks on scroll. */
.ff-18k-tablewrap { max-height: 68vh; overflow: auto; border-top: 1px solid var(--mud-palette-lines-default); }
.ff-18k-table thead th {
    position: sticky; top: 0; z-index: 2;
    background: var(--mud-palette-surface);
    box-shadow: inset 0 -1px 0 var(--mud-palette-lines-default);
}
.ff-18k-table th.sortable { cursor: pointer; user-select: none; }
.ff-18k-table th.sortable:hover { color: var(--mud-palette-text-primary); }
.ff-18k-table th.sortable.active { color: var(--mud-palette-primary); }
.ff-18k-table .ff-18k-ar { display: inline-block; width: 1em; margin-left: 2px; font-size: .7em; }

.ff-18k-noresults {
    display: flex; align-items: center; gap: 8px; justify-content: center;
    padding: 28px 12px; color: var(--mud-palette-text-secondary); font-size: .9rem;
}

/* 360px: table stays a clean horizontal scroll with a sticky first column so the name never
   scrolls out of view; filters stack full-width. */
@media (max-width: 599.98px) {
    .ff-18k-filters { gap: 8px; }
    .ff-18k-filters .ff-18k-f-search,
    .ff-18k-filters .ff-18k-f-conf,
    .ff-18k-filters .ff-18k-f-min { flex: 1 1 100%; min-width: 0; }
    .ff-18k-filters .ff-18k-f-reset { margin-left: 0; align-self: flex-end; }
    .ff-18k-table thead th:first-child,
    .ff-18k-table tbody td:first-child {
        position: sticky; left: 0; z-index: 1; background: var(--mud-palette-surface);
    }
    .ff-18k-table thead th:first-child { z-index: 3; }
}
/* ---- end 18K ---- */

/* ---- 18F: member profile ---- */
/* Career teaser tiles â€” reuse the ff-stat-tile look but pack tighter (auto-fit, smaller min) so the
   strip is 2-up at 360px and 4-up on desktop without a wall of whitespace. */
.ff-profile-teaser {
    display: grid; grid-template-columns: repeat(auto-fit, minmax(120px, 1fr)); gap: 10px;
}
.ff-profile-teaser .ff-stat-tile { padding: 10px 12px; }

/* A small "full career â†’" affordance on the teaser panel head (head is already space-between). */
.ff-profile-career-link { font-size: .82rem; font-weight: 600; color: var(--mud-palette-primary); white-space: nowrap; }
.ff-profile-career-link:hover { text-decoration: underline; }

/* Shared-league chips + badge chips share a wrapping flex row. */
.ff-profile-chips { display: flex; flex-wrap: wrap; gap: 8px; }

/* A shared-league chip: icon + team name + muted league name, wraps cleanly at 360px. */
.ff-profile-chip {
    display: inline-flex; align-items: center; gap: 8px; max-width: 100%;
    padding: 6px 12px; border-radius: 999px;
    background: var(--mud-palette-background-gray); border: 1px solid var(--mud-palette-lines-default);
}
.ff-profile-chip .mud-icon-root { color: var(--mud-palette-primary); flex: none; }
.ff-profile-chip-main { font-weight: 600; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; min-width: 0; }
.ff-profile-chip-sub { font-size: .8rem; color: var(--mud-palette-text-secondary); overflow: hidden; text-overflow: ellipsis; white-space: nowrap; min-width: 0; }

/* A badge chip: a real, career-derived accolade in the primary tint (never a fake placeholder). */
.ff-profile-badge {
    display: inline-flex; align-items: center; gap: 6px;
    padding: 6px 12px; border-radius: 999px; font-weight: 600; font-size: .85rem;
    color: var(--mud-palette-primary);
    background: rgba(var(--mud-palette-primary-rgb), .1);
    border: 1px solid rgba(var(--mud-palette-primary-rgb), .28);
}
.ff-profile-badge .mud-icon-root { color: var(--mud-palette-primary); flex: none; }
/* A badge that links (the career page's head-to-head edges) reads exactly like its static siblings. */
a.ff-profile-badge { text-decoration: none; }
a.ff-profile-badge:hover { border-color: rgba(var(--mud-palette-primary-rgb), .6); }

/* The career page's share menu: pinned to the end of the hero row, brand-tinted trigger. Colored
   here rather than through a component parameter so the hero owns its own look. */
.ff-share-menu { margin-left: auto; flex: none; }
.ff-share-menu .mud-icon-button { color: var(--mud-palette-primary); }
/* ---- end 18F ---- */

/* ---- 18I: records first-season ----
   The Records Book first-season experience (Phase 18.10): a warm empty state for a league with no
   scored weeks, section headers separating "this season" from "all-time", and the head-to-head
   picker's disabled/explained state when fewer than two members have scored. Mobile-first â€” the
   welcome card and H2H explainer stack at 360px; theme-var driven. */

/* Section header above a records grid (only shown when both this-season and all-time blocks render). */
.ff-records-section + .ff-records-section { margin-top: 26px; }
.ff-records-section-head {
    display: flex; align-items: center; gap: 8px;
    margin: 0 0 12px; font-size: 1.05rem; font-weight: 800;
}

/* First-season welcome â€” replaces the bare "no records yet" line for a zero-scored-week league. */
.ff-first-season {
    display: flex; gap: 18px; align-items: flex-start;
    padding: 22px; border-radius: 16px; margin: 4px 0;
    background: linear-gradient(135deg,
        rgba(var(--mud-palette-primary-rgb), .12), rgba(var(--mud-palette-primary-rgb), .03));
    border: 1px solid rgba(var(--mud-palette-primary-rgb), .22);
}
.ff-first-season-badge {
    flex: none; width: 56px; height: 56px; border-radius: 14px;
    display: flex; align-items: center; justify-content: center;
    background: rgba(var(--mud-palette-primary-rgb), .16); color: var(--mud-palette-primary);
}
.ff-first-season-badge .mud-icon-root { font-size: 2rem; }
.ff-first-season-body { min-width: 0; }
.ff-first-season-body h2 { margin: 2px 0 6px; font-size: 1.25rem; font-weight: 800; }
.ff-first-season-body p { margin: 0; color: var(--mud-palette-text-secondary); font-size: .9rem; line-height: 1.5; }
.ff-first-season-actions { display: flex; flex-wrap: wrap; align-items: center; gap: 12px; margin-top: 14px; }
.ff-first-season-hint { color: var(--mud-palette-text-secondary); font-size: .82rem; }
@media (max-width: 599.98px) {
    .ff-first-season { flex-direction: column; gap: 12px; padding: 18px; }
    .ff-first-season-badge { width: 48px; height: 48px; }
}

/* Head-to-head picker disabled/explained state (fewer than two members with a scored week). */
.ff-h2h-empty { display: flex; gap: 14px; align-items: flex-start; }
.ff-h2h-empty > .mud-icon-root { flex: none; margin-top: 2px; }
.ff-h2h-empty-ttl { font-weight: 700; margin-bottom: 2px; }
/* ---- end 18I ---- */

/* ---- 21A: analytics fallback ---- */
/* Per-board chip shown when a scouting board falls back to an older cached year (offseason, the
   selected year hasn't published yet). Sits above the board body; wraps its note on narrow phones
   so 360px never overflows. */
.ff-fallback-chip { margin: 4px 8px 8px; }
.ff-fallback-chip .mud-chip { height: auto; max-width: 100%; white-space: normal; }
.ff-fallback-chip .mud-chip .mud-chip-content { white-space: normal; line-height: 1.3; padding-top: 3px; padding-bottom: 3px; }

/* ---- 21G/21H: new scouting boards (wepa value + projection accuracy) ---- */
/* The one-line explainer captions above each new board: muted, tight, and full-width so they wrap
   cleanly at 360px instead of crowding the filters. */
.ff-wepa-explainer,
.ff-projacc-explainer {
    font-size: .78rem;
    line-height: 1.35;
    color: var(--mud-palette-text-secondary);
}

/* ---- C1: tabs-native + scroll-top + chart host ---- */

/* #37: native touch scroll for MudTabs strips on phones (no prev/next chevrons).
   Opt-in via Class="ff-tabs-native" on a MudTabs. MudBlazor clips the strip with
   .mud-tabs-tabbar-content { overflow: hidden } and scrolls it by JS-translating
   .mud-tabs-tabbar-wrapper through the (now hidden) arrows; hiding the arrows alone
   would strand the overflow, so we also expose native overflow scroll and neutralize
   the transform. The active-tab slider uses left, not transform, so it stays aligned. */
@media (max-width: 599.98px) {
    .ff-tabs-native .mud-tabs-scroll-button { display: none; }
    .ff-tabs-native .mud-tabs-tabbar-content {
        overflow-x: auto; overflow-y: hidden;
        -webkit-overflow-scrolling: touch; scrollbar-width: none; /* Firefox */
    }
    .ff-tabs-native .mud-tabs-tabbar-content::-webkit-scrollbar { display: none; }
    .ff-tabs-native .mud-tabs-tabbar-wrapper { transform: none !important; }
}

/* #40: the floating scroll-to-top FAB (ScrollToTopButton.razor). FF has no competing
   FAB, so it stays bottom-right at every width; on phones it lifts a little to clear
   the iOS Safari accessory strip. */
.ff-scroll-top {
    position: fixed; right: 1.25rem; bottom: 1.5rem;
    z-index: 1200; box-shadow: 0 4px 12px rgba(0, 0, 0, .25);
}
@media (max-width: 599.98px) {
    .ff-scroll-top { bottom: 1rem; }
}

/* #50: chart host reset. ECharts injects a wrapper div and a <canvas>; without a
   block/line-height reset the canvas carries an inline baseline gap (a few-pixel
   overflow) that trips an ancestor's overflow:auto into a short internal scrollbar and
   breaks equal-height panels. Clip any residual sub-pixel bleed too. Safe with ECharts
   tooltips because the interop sets confine:true, keeping tooltip DOM inside the box.
   Scoped off .ff-chart-empty (the empty state AND the error overlay both carry that
   class) so their centered flex text keeps a normal line-height and layout. */
.ff-chart { overflow: hidden; }
.ff-chart > div:not(.ff-chart-empty) { line-height: 0; }
.ff-chart > div:not(.ff-chart-empty), .ff-chart canvas { display: block; }

/* ---- 22A: stats tabs ---- */

/* #42 Â§3.3: on the /stats tabs a chosen tab must show its boards expanded at every width.
   AnalyticsPanel (the shell behind every RankedStatCard) starts collapsed on phones â€” its body div
   carries `d-none d-sm-block` and a `d-inline-flex d-sm-none` chevron toggles it. Once the boards are
   split across five tabs (one to three per tab) that per-card collapse is redundant friction, so within
   the stats tab body we force the body visible and hide the now-dead chevron. Scoped to .ff-stats-body
   so no other AnalyticsPanel caller is affected (the shared InitiallyOpen param is 22B's job). */
.ff-stats-body .mud-card > .d-none.d-sm-block { display: block !important; }
.ff-stats-body .mud-card-header .d-inline-flex.d-sm-none { display: none !important; }

/* ---- 22F: point types ---- */
/* The filter row above the editable list: search grows, "Active only" sits to its right. */
.ff-pt-filters { display: flex; flex-wrap: wrap; gap: 12px; align-items: center; margin-bottom: 12px; }
.ff-pt-search { flex: 1 1 240px; min-width: 200px; }

/* The value cell pairs the numeric field with an unsaved-change dot. */
.ff-pt-valcell { display: inline-flex; align-items: center; gap: 8px; }
.ff-pt-dirty { width: 8px; height: 8px; border-radius: 50%; flex: 0 0 auto;
    background: var(--mud-palette-warning); }

/* Sticky bottom save bar: full-width fixed on phones, inline-right on wider screens. It only
   asserts itself (border + shadow) when there are unsaved changes. */
.ff-pt-savebar { display: flex; align-items: center; justify-content: space-between; gap: 12px;
    position: sticky; bottom: 0; z-index: 4; margin-top: 16px; padding: 10px 14px; border-radius: 12px;
    background: var(--mud-palette-surface); border: 1px solid transparent; transition: border-color .15s, box-shadow .15s; }
.ff-pt-savebar.dirty { border-color: var(--mud-palette-lines-default);
    box-shadow: 0 -2px 10px rgba(0, 0, 0, .16); }
.ff-pt-savecount { font-size: .85rem; color: var(--mud-palette-text-secondary); font-weight: 600; }
.ff-pt-saveactions { display: flex; gap: 8px; align-items: center; }

@media (max-width: 599.98px) {
    .ff-pt-savebar { position: fixed; left: 0; right: 0; bottom: 0; margin: 0; border-radius: 0;
        border-left: 0; border-right: 0; }
    .ff-pt-savebar.dirty { border-color: var(--mud-palette-lines-default); }
}

/* ---- 22E: draft order ---- */
/* Inline add-member row (no expansion panel) — select grows, button hugs. */
.ff-do-add { display: flex; align-items: center; gap: 8px; margin: 8px 0 4px; }
.ff-do-add-select { flex: 1 1 auto; max-width: 340px; }
/* Reorderable pick list: drag handle, big pick number, avatar+name, row actions. */
.ff-do-list { display: flex; flex-direction: column; }
.ff-do-row {
    display: grid; grid-template-columns: 24px 30px 1fr auto; align-items: center; gap: 10px;
    padding: 8px 10px; border-bottom: 1px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-surface);
}
.ff-do-row:last-child { border-bottom: 0; }
.ff-do-row.on-clock { background: var(--mud-palette-success-hover); border-radius: 8px; }
.ff-do-drag { cursor: grab; }
.ff-do-pick {
    font-variant-numeric: tabular-nums; font-weight: 700; font-size: .9rem; text-align: center;
    color: var(--mud-palette-text-secondary);
}
.ff-do-main { display: flex; align-items: center; gap: 10px; min-width: 0; }
.ff-do-name { font-weight: 600; font-size: .92rem; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-do-actions { display: inline-flex; align-items: center; flex: 0 0 auto; }
/* T-29: the start/status panel. Status text on the left, the one action on the right; both stack and
   the button goes full width at 360px so it stays a one-thumb tap. */
.ff-do-start {
    display: flex; flex-wrap: wrap; align-items: center; justify-content: space-between;
    gap: 10px; padding: 12px 14px;
}
.ff-do-start-main { display: flex; align-items: center; gap: 10px; min-width: 0; }
.ff-do-clock-mark { margin-right: 6px; }
@media (max-width: 640px) {
    .ff-do-start { flex-direction: column; align-items: stretch; }
}
/* Sticky action bar so Randomize/Save stay reachable one-handed on long lists. */
.ff-do-bar {
    display: flex; flex-wrap: wrap; align-items: center; gap: 8px; margin-top: 12px;
    padding: 10px 4px; position: sticky; bottom: 0; z-index: 3;
    background: var(--mud-palette-surface); border-top: 1px solid var(--mud-palette-lines-default);
}
@media (max-width: 640px) {
    .ff-do-row { grid-template-columns: 20px 26px 1fr auto; gap: 6px; padding: 8px 4px; }
    .ff-do-add-select { max-width: none; }
}

/* ---- 23A: ai working indicator ---- */

/* ============================================================
   AI working indicator (Phase 23) — the "it's doing cool work"
   state. Purple sparkle + orbit + text sheen; status text is
   rotated from C#. Motion is CSS-only and yields to reduced-motion.
   ============================================================ */
.ff-ai-working { display: inline-flex; align-items: center; gap: 10px; }
/* Punch 2026-07-25: the Block variant is full-width flex so the stack CENTERS in its host card
   instead of hugging the left edge (the root's inline-flex shrinks to content width otherwise). */
.ff-ai-working.block { display: flex; width: 100%; flex-direction: column; text-align: center; gap: 12px; padding: 20px 16px; }
.ff-ai-text { display: inline-flex; flex-direction: column; min-width: 0; }
.ff-ai-working.block .ff-ai-text { align-items: center; }
.ff-ai-cancel { flex: none; }

/* Mark: a breathing core sparkle + a small orbiting satellite. */
.ff-ai-spark { position: relative; width: 26px; height: 26px; flex: none; color: var(--mud-palette-primary); }
.ff-ai-working.block .ff-ai-spark { width: 40px; height: 40px; }
.ff-ai-spark .core { position: absolute; inset: 0; display: grid; place-items: center;
    animation: ff-ai-breathe 2s ease-in-out infinite; }
.ff-ai-spark .core .mud-icon-root { font-size: inherit; width: 100%; height: 100%; }
.ff-ai-spark .sat { position: absolute; top: 50%; left: 50%; width: 6px; height: 6px; margin: -3px 0 0 -3px;
    border-radius: 50%; background: var(--mud-palette-primary); opacity: .85;
    animation: ff-ai-orbit 2.6s linear infinite; }

@keyframes ff-ai-breathe {
    0%, 100% { opacity: .55; transform: scale(.92) rotate(-4deg); }
    50%      { opacity: 1;   transform: scale(1.12) rotate(6deg); }
}
@keyframes ff-ai-orbit {
    from { transform: rotate(0deg) translateX(12px) rotate(0deg); }
    to   { transform: rotate(360deg) translateX(12px) rotate(-360deg); }
}

/* Status line: a clipped gradient sheen sweeps the text. */
.ff-ai-status { font-size: .9rem; font-weight: 600; line-height: 1.35;
    background: linear-gradient(90deg,
        var(--mud-palette-text-secondary) 30%,
        var(--mud-palette-primary) 50%,
        var(--mud-palette-text-secondary) 70%);
    background-size: 220% 100%;
    -webkit-background-clip: text; background-clip: text; color: transparent;
    animation: ff-ai-sheen 2.4s ease-in-out infinite; }
@keyframes ff-ai-sheen { 0% { background-position: 160% 0; } 100% { background-position: -60% 0; } }

/* Fallback: where background-clip:text is unsupported the text would clip to transparent
   and vanish, so paint it solid primary instead (risk #2). */
@supports not ((-webkit-background-clip: text) or (background-clip: text)) {
    .ff-ai-status { background: none; color: var(--mud-palette-primary);
        -webkit-text-fill-color: currentColor; animation: none; }
}

.ff-ai-sub { font-size: .74rem; color: var(--mud-palette-text-secondary); }

/* Block-variant indeterminate track. */
.ff-ai-track { position: relative; width: min(260px, 70%); height: 3px; border-radius: 3px; overflow: hidden;
    background: rgba(var(--mud-palette-primary-rgb), .16); }
.ff-ai-track::after { content: ""; position: absolute; top: 0; bottom: 0; left: -40%; width: 40%;
    border-radius: inherit; background: var(--mud-palette-primary);
    animation: ff-ai-slide 1.4s ease-in-out infinite; }
@keyframes ff-ai-slide { 0% { left: -40%; } 100% { left: 100%; } }

/* Opt-in busy sweep a parent can add to its own MudButton. */
.ff-ai-btn-busy {
    background: linear-gradient(110deg,
        var(--mud-palette-primary) 20%,
        var(--mud-palette-primary-darken, #C74A00) 50%,
        var(--mud-palette-primary) 80%) !important;
    background-size: 200% 100% !important;
    animation: ff-ai-btn-sheen 2.2s ease-in-out infinite;
}
@keyframes ff-ai-btn-sheen { 0% { background-position: 100% 50%; } 100% { background-position: -100% 50%; } }

/* Better than the reference: honor reduced-motion. Text still rotates
   (a content change is not vestibular motion); the visuals settle. */
@media (prefers-reduced-motion: reduce) {
    .ff-ai-spark .core, .ff-ai-track::after, .ff-ai-btn-busy { animation: none; }
    .ff-ai-spark .sat { display: none; }
    .ff-ai-status { animation: none; background: none;
        -webkit-text-fill-color: currentColor; color: var(--mud-palette-primary); }
    .ff-ai-track::after { left: 0; width: 100%; opacity: .5; }
}

/* ---- 22D: scoring analysis ---- */
/* #44: the generated member Scoring Analysis page. The optional AI "how this league scores" summary
   sits in a soft callout above the per-category rule tables; the point value reads as a compact,
   emphasized number in each row. */
.ff-scoring-summary { padding: 12px 14px; border-radius: 12px;
    background: var(--mud-palette-background-gray); border: 1px solid var(--mud-palette-lines-default); }
.ff-scoring-summary-head { display: flex; align-items: center; gap: 8px; margin-bottom: 4px;
    color: var(--mud-palette-text-secondary); }
.ff-scoring-pts { font-weight: 600; font-variant-numeric: tabular-nums; }

/* ---- punch-A ---- */

/* #(buzz) League Buzz desktop: recap, power ranking, and weekly awards go three-across at desktop
   widths (>=961px), overriding the shared 2-col .ff-buzz-cols/.ff-cols grid. Mobile keeps the
   single-column stack from .ff-cols (max-width:960px). */
@media (min-width: 961px) {
    .ff-buzz-cols { grid-template-columns: 1fr 1fr 1fr; }
}

/* #62 (a): the Scouting season boards are fixed-height scrolling cards laid out two-across. Clip each
   card so a table's sticky header / wide row can never paint outside its rounded box and overlap the
   neighboring board (or the sticky segmented tabs). The .ff-chart-empty/tooltip overlays render in a
   portal, so this does not clip them. */
.ff-scout-boards .mud-card { overflow: hidden; }

/* #55: the Teams-hub "By season" table sparklines live in a td.spark host that the #50 .ff-chart clip
   did not fully tame (the cell's own line-height left a baseline gap that tripped a residual internal
   scrollbar in the Trend column). Zero the host line-height and reinforce the chart clip here. */
.ff-table td.spark { line-height: 0; }
.ff-table td.spark .ff-chart,
.ff-table td.spark .ff-chart > div { overflow: hidden; line-height: 0; }

/* ---- 25A: conference hub ---- */
/* The per-season membership note under the conference hero (realignment honesty). Muted, small, and
   aligned with its info icon, matching the page-sub tone without competing with the headline. */
.ff-conf-note {
    display: flex;
    align-items: center;
    gap: 4px;
    color: var(--mud-palette-text-secondary);
    font-size: 0.8rem;
}
.ff-conf-note .mud-icon-root { font-size: 1rem; }

/* ---- batch-D ---- */

/* #1: League Buzz — the three-across recap / power-ranking / awards row was capped at ~980px, so it
   left dead space on wider desktops. Let the whole buzz column (and thus the equal 1fr 1fr 1fr grid
   inside it) use the full content width at desktop; the mobile single-column stack (.ff-cols at
   <=960px) is unchanged. */
@media (min-width: 961px) {
    .ff-buzz { max-width: none; }
}

/* #2: Draft "My Team" — the weekly lineup card and the "Your week" metrics panel stacked because the
   wrap was a single capped column. Lay them out as two equal columns that fill the row on desktop
   (mirroring the .ff-cols grid), stacking on phones; the card internals are untouched, and the
   "Your week" panel drops its stacked-era cap and top margin so the two tops line up. */
.ff-team-wrap { max-width: none; display: grid; grid-template-columns: 1fr 1fr; gap: 16px; align-items: start; }
@media (max-width: 960px) { .ff-team-wrap { grid-template-columns: 1fr; } }
.ff-team-wrap > .ff-mt-week { max-width: none; margin-top: 0; }

/* #4: /stats player cells — keep the player-page link and the compact weekly-breakdown toggle on one
   line, with the toggle reading as a quiet secondary control. */
.ff-stats-name-cell { display: inline-flex; align-items: center; gap: 2px; }
.ff-stats-drill { opacity: .65; }
.ff-stats-drill:hover { opacity: 1; }

/* ---- 26: public shell ---- */

/* Most public chrome lives in scoped .razor.css (PublicLayout / Landing); this block holds only the
   genuinely GLOBAL public concern: the single-source brand accent colour.

   --ff-brand is the one place the public brand accent is defined (owner item 21). The public brand
   mark accents, hero eyebrow/glyph, and how-it-works step badges all key off it. It is the ratified
   logo orange (#F85B01), a fixed brand constant that reads on both light and dark surfaces. The
   MudBlazor theme primary is also this orange, so accents stay consistent with buttons/links.

   Swappable brand pipeline (owner item 21): the canonical mark is wwwroot/brand/mark-square.png and
   the full lockups are logo-dark.png (white text, dark surfaces) / logo-light.png (black text, light
   surfaces). Swap those assets and rerun tools/brand/Generate-BrandAssets.ps1 to re-derive every
   favicon / PWA icon / OG share card; retint here and in App.razor's MudTheme to change the accent. */
:root {
    --ff-brand: #F85B01;
}

/* Public marketing pages must never introduce horizontal overflow at any width (mobile-first
   guard); the scoped layouts size with relative units, this is the belt-and-braces backstop.

   MUST be `clip`, not `hidden` (owner report 2026-07-31: double scrollbar on desktop, and a phone
   swipe that moved a couple of pixels and rubber-banded back to the top). Per the CSS overflow spec,
   when one axis is `visible` and the other is not, the `visible` axis computes to `auto` instead.
   So `overflow-x: hidden` alone silently turned this element into a VERTICAL scroll container that
   was scrollable by ~2px, sitting inside the real page scroll: two scrollbars on desktop, and on
   touch the inner container swallowed the gesture until scroll chaining handed off. `clip` clips
   without establishing a scroll container, so overflow-y stays genuinely `visible`. Verified in the
   browser against production: nested scrollers drop from one to zero, document scrolling unchanged. */
.ff-public .ff-public-body {
    overflow-x: hidden; /* fallback for engines without `clip` */
    overflow-x: clip;
}

/* ---- Auth surfaces (Login / Register / Forgot / Reset / Verify) ----
   Single-source card so every auth page reads as a sibling: one branded card centered on the dark
   base, orange brand hairline, sporty eyebrow, consistent typography and rhythm. All five live under
   PublicLayout, so the site banner + footer wrap them. Global (not scoped) on purpose: one definition
   keeps the pages identical, replacing the duplicated per-page recovery CSS. Rides MudBlazor palette
   vars so light and dark both read; accents key off --ff-brand (the ratified logo orange). Mobile-first,
   verified usable at 375px. No em dashes in copy (CI guard). */
.ff-auth {
    padding-top: 40px;
    padding-bottom: 56px;
}

.ff-auth-card {
    position: relative;
    background: var(--mud-palette-surface);
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 16px;
    padding: 32px 22px 26px;
    overflow: hidden;
    box-shadow: 0 12px 34px rgba(0, 0, 0, .18);
}

/* Orange brand hairline across the top of every auth card (the small brand touch). */
.ff-auth-card::before {
    content: "";
    position: absolute;
    top: 0;
    left: 0;
    right: 0;
    height: 4px;
    background: var(--ff-brand, var(--mud-palette-primary));
}

.ff-auth-eyebrow {
    display: inline-flex;
    align-items: center;
    gap: 6px;
    margin: 0 0 10px;
    font-size: .72rem;
    font-weight: 700;
    letter-spacing: .08em;
    text-transform: uppercase;
    color: var(--ff-brand, var(--mud-palette-primary));
}

.ff-auth-eyebrow .mud-icon-root {
    font-size: 1.05rem;
}

.ff-auth-title {
    margin: 0 0 6px;
    font-size: 1.6rem;
    line-height: 1.15;
    font-weight: 800;
    letter-spacing: -.02em;
    color: var(--mud-palette-text-primary);
}

.ff-auth-lede,
.ff-auth-help {
    margin: 0 0 22px;
    font-size: .95rem;
    line-height: 1.55;
    color: var(--mud-palette-text-secondary);
}

.ff-auth-help {
    margin-top: 4px;
}

.ff-auth-footer {
    margin-top: 22px;
    text-align: center;
    font-size: .9rem;
    color: var(--mud-palette-text-secondary);
}

.ff-auth-legal {
    margin-top: 16px;
    text-align: center;
    font-size: .78rem;
    line-height: 1.5;
    color: var(--mud-palette-text-secondary);
}

@media (min-width: 600px) {
    .ff-auth {
        padding-top: 56px;
    }

    .ff-auth-card {
        padding: 40px 34px 32px;
    }

    .ff-auth-title {
        font-size: 1.85rem;
    }
}

/* ---- sticky footer (owner fix, final) ----
   Standard sticky footer: .mud-main-content is a min-height:100dvh flex column and the content region
   (.ff-public-body / .ff-appshell-body, scoped) grows (flex:1) to fill, so <SiteFooter/> is pinned to
   the VIEWPORT BOTTOM with no gap below it on short pages, and is pushed down naturally on long pages.
   (An earlier 60dvh "trail the content" variant left dead space BELOW the footer on tall screens; this
   restores the footer to the bottom, which is what an "actual footer" means.)
   Legacy notes below kept for history.
   ---- original notes ----
   Problem (original): <SiteFooter/> renders in normal content flow. MudBlazor's .mud-layout is
   height:100% and is NOT a flex container, so .mud-main-content's own `flex:1 1 auto` is inert and the
   content area collapses to its content height. On SHORT pages that left the footer floating
   mid-viewport with dead space beneath it. First fix: promote .mud-main-content to a flex column with
   `min-height:100vh` and grow the content region (flex:1 0 auto) to fill it, which pinned the footer to
   the exact viewport bottom. That killed the float but introduced #37: on short / sparse pages the
   grown content region left a large EMPTY VOID between the top-anchored content and the bottom-pinned
   footer.

   Refined model (#37): do NOT force the full viewport (that is what jammed the footer to the very
   bottom and opened the void above it). Instead .mud-main-content is a plain flex column and the content
   region (.ff-public-body / .ff-appshell-body, in each layout's scoped sheet) carries a SENSIBLE
   min-height (60dvh) plus a comfortable bottom margin. Result: on a short page the content keeps a
   reasonable presence and the footer trails it a comfortable, intentional distance below (footer lands
   in the lower third, ~70% down on a laptop) instead of being jammed to the bottom with a huge void
   above it, and instead of floating up mid-screen. On a normal / long page the content exceeds the
   60dvh floor, so the footer simply trails the content and is pushed down / below the fold naturally
   (never fixed, never overlaid). Any leftover slack on a very tall monitor sits below the footer as
   ordinary, seamless page background rather than as an ugly hole above it.

   Why global (not the scoped .razor.css files): .mud-main-content is emitted by the MudMainContent
   child component, so it carries no parent scope id and cannot be reached from PublicLayout /
   MainLayout scoped CSS. The content-region items (.ff-public-body, .ff-appshell-body) DO live in
   their layouts' scope and carry the min-height + margin there.

   box-sizing:border-box + the column flex keep the appbar padding-top and the content stacking
   predictable; the fixed appbar/drawer are out of normal flow and add no document height. The content
   region uses 60dvh with a 60vh fallback so it tracks the real viewport under mobile browser chrome.
   Mobile-first: verified at 375px (content taller than the floor there, so the footer just trails it;
   column flex, no fixed widths, no horizontal overflow). */
.ff-public .mud-main-content,
.ff-appshell .mud-main-content {
    display: flex;
    flex-direction: column;
    box-sizing: border-box;
    min-height: 100vh;
    min-height: 100dvh;
}

/* #72: DESKTOP-ONLY app-bar height bump so the 48px wordmark lockup breathes and never clips; the
   phone bar (square mark, owner-ratified) keeps its default height. Moved here from
   MainLayout.razor.css in the 2026-07-31 scoped-CSS sweep: .ff-appbar sits on the MudAppBar root,
   which carries no isolation scope attribute, so the scoped version of this rule was silently dead
   and the desktop bar stayed at the default height. Global CSS reaches component roots fine (the
   .ff-appshell rule above is the standing precedent). */
@media (min-width: 601px) {
    .ff-appbar .mud-toolbar {
        min-height: 72px;
        height: 72px;
    }
}

/* ---- 30E: ownership transfer ---- */

/* The commissioner-retirement panel on the members page and the nominee's Accept/Decline prompt.
   Both reuse the existing MudCard/MudAlert chrome; these rules only handle the responsive layout of
   the prompt row so the action buttons wrap under the copy on narrow viewports. */
.ff-transfer-panel {
    margin-bottom: 1.5rem;
}

.ff-transfer-prompt-body {
    display: flex;
    flex-wrap: wrap;
    gap: 0.75rem;
    align-items: center;
    justify-content: space-between;
}

.ff-transfer-prompt-actions {
    display: flex;
    gap: 0.5rem;
    flex-shrink: 0;
}

@media (max-width: 600px) {
    .ff-transfer-prompt-actions {
        width: 100%;
    }
}

/* 28H: account danger zone (self-service delete + export). A subtle error-tinted panel edge marks the
   destructive section; the goodbye state centers on the post-deletion sign-out. Reuses palette vars so
   it tracks light/dark automatically. */
.ff-danger-zone { border: 1px solid var(--mud-palette-error); }
.ff-danger-zone .ff-panel-head { border-bottom-color: var(--mud-palette-error); }
.ff-delete-confirm {
    border-left: 3px solid var(--mud-palette-error);
    padding-left: 12px;
    margin-top: 8px;
}
.ff-goodbye { max-width: 560px; margin-left: auto; margin-right: auto; }

/* ============================================================
   Wave 2 mobile polish (#54): app-bar league-name truncation.
   The switcher control is capped (max-width: 42vw on <=600px, above). These rules let the whole
   MudButton chain shrink below its content so a long league name TRUNCATES with an ellipsis
   ("Gridiron Test Le...") instead of overflowing and being clipped on both ends. The name is wrapped
   in .ff-league-switcher-name (LeagueSwitcher.razor) so text-overflow has a single-line target.
   These reach MudBlazor internals, so they live here (global) rather than in scoped CSS.
   ============================================================ */
.ff-league-switcher.mud-button-root,
.ff-league-switcher .mud-button-root {
    min-width: 0;
    max-width: 100%;
}
.ff-league-switcher .mud-button-label {
    min-width: 0;
    overflow: hidden;
    flex-wrap: nowrap;
}
.ff-league-switcher-name {
    display: block;
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

/* ============================================================================================
   WAVE 2 PUBLIC REDESIGN — shared motion utilities (single appended block; owner-ratified).

   These are GLOBAL because the scroll-reveal state is gated behind html.ff-js-motion (an ancestor
   of the scoped page elements), which Blazor scoped sheets cannot own, and because the same reveal
   utility + shared keyframes are reused across every public page. Page-specific look (hero, cards,
   badges) stays in each page's scoped .razor.css. Nothing here bleeds into the authed app: the
   .ff-reveal / .ff-hero-* hooks only exist on the public marketing markup.

   Motion contract (js/public-motion.js): markup is authored VISIBLE. The module adds .ff-js-motion
   only when it is safe to animate, so SSR / crawlers / no-JS / prefers-reduced-motion all render the
   fully visible page with zero movement. The reduced-motion @media below is belt-and-braces.
   ============================================================================================ */

/* Scroll-reveal: hidden pre-state applies ONLY once JS has opted in via html.ff-js-motion. */
.ff-js-motion .ff-reveal {
    opacity: 0;
    transform: translateY(26px);
    transition: opacity .6s cubic-bezier(.22, .61, .36, 1),
                transform .6s cubic-bezier(.22, .61, .36, 1);
    will-change: opacity, transform;
}

.ff-js-motion .ff-reveal.is-visible {
    opacity: 1;
    transform: none;
}

/* Staggered reveal within a section so grouped items cascade rather than snap in together. */
.ff-js-motion .ff-reveal.ff-reveal--d1 { transition-delay: .08s; }
.ff-js-motion .ff-reveal.ff-reveal--d2 { transition-delay: .16s; }
.ff-js-motion .ff-reveal.ff-reveal--d3 { transition-delay: .24s; }
.ff-js-motion .ff-reveal.ff-reveal--d4 { transition-delay: .32s; }

/* Shared entrance keyframe for on-load hero content (plays once, no observer needed). Uniquely
   named so it never collides with a MudBlazor / scoped animation. */
@keyframes ffFadeUp {
    from { opacity: 0; transform: translateY(22px); }
    to   { opacity: 1; transform: none; }
}

/* Respect the user's motion preference everywhere: kill reveals, on-load entrances, and the hero
   accent sweep. (public-motion.js already skips hiding under this preference; this covers the pure
   CSS on-load animations too.) */
@media (prefers-reduced-motion: reduce) {
    .ff-js-motion .ff-reveal {
        opacity: 1 !important;
        transform: none !important;
        transition: none !important;
    }
    .ff-anim-load,
    .ff-anim-load > * {
        animation: none !important;
        opacity: 1 !important;
        transform: none !important;
    }
    .ff-hero-streak,
    .ff-hero-orb { animation: none !important; }
}

/* ============================================================================================
   AI + MOBILE REFINEMENT (M1, 2026-07-24) — hub header single row + AI prose link affordance.
   The campaign's only append to this sheet (single-owner rule), covering two items:

   R1 — the Player / Team / Conference hub headers keep every action button on ONE row at 360px.
   The rules that did it (.ff-hub-title, .ff-title-name, .ff-title-actions and their 599.98px
   clamp) MOVED to Shared/PageHero.razor.css in wave H4 (2026-08-19) when the six pages that used
   them adopted the shared hero band, which learned a TitleContent fragment and a TitleNoWrap row
   for exactly this shape. The behaviour is unchanged and is described in full there: the elastic
   name zone (now the h1 itself) carries min-width:0 so it can shrink below its min-content width,
   which is what stops a long school name from pushing the action cluster onto a second row, and
   the cluster is flex:none so it can never be squeezed. Nothing about it belongs in this sheet any
   more: the classes had six consumers, all six are converted, and a scoped stylesheet is where the
   band's own structure lives.

   The base .ff-detail-title rule above (~:296) was never modified by M1 and still is not: six
   OTHER surfaces (PlayerDetailPage x2, GameDay, PlayerCompare, TeamCompareView,
   ConferenceCompareView) share it and carry a value block or a status badge rather than an action
   cluster.

   R2 — prose links inside .ff-md (assistant, stat search, League Buzz, Home recap, constitution,
   member bio, activity feed) get an underline. On touch there is no hover, so the underline is the
   affordance; it also satisfies "not by color alone" independently of the brand orange.
   ============================================================================================ */

/* R2: touch-visible link affordance for rendered markdown (MarkdownLite emits allow-listed
   internal links only, so no external URL can ever pick this up). */
.ff-md a {
    text-decoration: underline;
    text-decoration-thickness: 1px;
    text-underline-offset: 3px;
}

/* ============================================================================================
   Punch 2026-07-25 (P-12) — page-level loading rows center in their host card, matching the AI
   working indicator's centering fix. The spinner + "Loading x" text used to hug the card's left
   edge; ff-loading is the one shared treatment for every block-level loading state. (The tiny
   inline spinners beside section titles are a different, deliberate pattern and keep their spot;
   LeagueBuzz's ff-buzz-loading was already centered and now shares this class family.)
   ============================================================================================ */
.ff-loading {
    display: flex;
    align-items: center;
    justify-content: center;
    gap: 10px;
    padding: 20px 16px;
    text-align: center;
}

/* ============================================================================================
   Punch 2026-07-26 (P-13 / P-16) — the ResponsiveList mobile card, opt-in refinements.

   P-13: CompactMobile packs the card's stat columns TWO PER LINE as label-over-value mini cells
   (the .ff-tile label/value idiom, shrunk). One full-width labeled line per stat left the middle of
   every row empty and capped a card at ~4 stats; the grid fits ~6 in the same height, which is what
   lets the conference/team lists un-hide their previously desktop-only detail columns. An odd stat
   count spans its last cell (.span2) across both columns so the grid never ends on a ragged half row.

   P-16: FullWidthOnMobile renders a long explainer column (Breakouts "Why", Pool changes "What
   happened") as an unlabeled caption-size muted line under the name lines, instead of a label/value
   pair whose right-aligned value wrapped into a split. Both boards now share the one row idiom.

   Both blocks only ever render inside the card container (.d-sm-none), so they are mobile-only by
   construction and need no media query of their own.
   ============================================================================================ */
.ff-rl-stats {
    display: grid;
    grid-template-columns: 1fr 1fr;
    gap: 6px 14px;
    margin-top: 4px;
}

.ff-rl-stat { display: flex; flex-direction: column; min-width: 0; }
.ff-rl-stat.span2 { grid-column: 1 / -1; }

.ff-rl-stat .k {
    font-size: .68rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
    line-height: 1.3;
    color: var(--mud-palette-text-secondary);
}

.ff-rl-stat .v {
    font-size: .9rem;
    font-weight: 600;
    line-height: 1.35;
    overflow-wrap: anywhere;   /* a long school or player name must never widen the card */
}

.ff-rl-note {
    margin-top: 6px;
    font-size: .78rem;
    line-height: 1.45;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* ============================================================================================
   Punch 2026-07-27 (P-24) — the research boards' structured context row. Breakouts and Pool
   changes each render their existing prose line, then a wrapping row of tiny label+value chips
   built from NULLABLE DTO fields, so a row with no numbers renders no chip row at all. Shared
   classes on purpose: the owner reads the two boards as one family.

   On mobile the chips live inside the card's full-width .ff-rl-note caption line (P-16), on
   desktop inside a left-aligned table cell — both start-aligned, so no breakpoint flip is
   needed. flex-wrap keeps the row inside 360px; each chip is nowrap so a "share 7.4% to 50%"
   value never breaks mid-number.
   ============================================================================================ */
/* Spans, not divs: the desktop cell may sit inside inline flow; display promotes them here. */
.ff-ctx-why { display: block; line-height: 1.4; }

.ff-ctx-chips {
    display: flex;
    flex-wrap: wrap;
    gap: 4px;
    margin-top: 4px;
    justify-content: flex-start;
}

.ff-ctx-chip {
    display: inline-flex;
    align-items: baseline;
    gap: 4px;
    max-width: 100%;
    padding: 1px 7px;
    border-radius: 999px;
    background: var(--mud-palette-background);
    border: 1px solid var(--mud-palette-lines-default);
    font-size: .68rem;
    line-height: 1.7;
    white-space: nowrap;
}

.ff-ctx-chip .lbl {
    font-size: .62rem;
    text-transform: uppercase;
    letter-spacing: .04em;
    color: var(--mud-palette-text-secondary);
}

.ff-ctx-chip .val { font-weight: 600; }

/* The reference-scoring disclaimer that sits above either board whenever a points chip can show. */
.ff-ctx-note {
    margin: 0 0 12px;
    font-size: .75rem;
    line-height: 1.45;
    color: var(--mud-palette-text-secondary);
}


/* ============================================================================================
   Punch 2026-07-27 (P-20) — My Team "Your week" enrichment. Extends the 18B .ff-mt-* idiom with
   three additions: a section rule (.ff-mt-sec) that groups the panel into scannable blocks, the
   slot-vs-league-average bars (.ff-mt-slots), and the denser season strip (.ff-mt-strip).
   Mobile first: the strip is 2-up at 360px and 4-up from 600px, and the bar row is a grid whose
   only elastic column is the track, so the pos pill and the numbers never shrink into slivers.
   ============================================================================================ */

.ff-mt-sec {
    display: flex;
    align-items: baseline;
    justify-content: space-between;
    gap: 8px;
    margin: 16px 0 8px;
    border-top: 1px solid var(--mud-palette-lines-default);
    padding-top: 12px;
}

.ff-mt-sec .k {
    color: var(--mud-palette-text-secondary);
    font-size: .68rem;
    text-transform: uppercase;
    letter-spacing: .05em;
}

.ff-mt-sec .sub { color: var(--mud-palette-text-secondary); font-size: .7rem; flex: 0 0 auto; }

/* One bar row: [pos pill] [elastic track] [numbers]. */
.ff-mt-slots { display: flex; flex-direction: column; gap: 8px; }

.ff-mt-slot {
    display: grid;
    grid-template-columns: 44px minmax(0, 1fr) auto;
    align-items: center;
    gap: 10px;
}

.ff-mt-slot > .ff-pos { min-width: 44px; }

.ff-mt-bar {
    position: relative;
    height: 10px;
    border-radius: 999px;
    background: var(--mud-palette-background-gray);
    border: 1px solid var(--mud-palette-lines-default);
    overflow: hidden;
}

.ff-mt-bar .fill { position: absolute; inset: 0 auto 0 0; border-radius: 999px; }
.ff-mt-bar .fill.over { background: var(--mud-palette-success); }
.ff-mt-bar .fill.under { background: var(--mud-palette-warning); }

/* The league-average tick sits on top of the fill, so "am I over or under" is readable without
   relying on the fill color alone. */
.ff-mt-bar .tick {
    position: absolute;
    top: 0;
    bottom: 0;
    width: 2px;
    margin-left: -1px;
    background: var(--mud-palette-text-primary);
    opacity: .65;
}

.ff-mt-slot .nums { font-size: .78rem; font-variant-numeric: tabular-nums; white-space: nowrap; }
.ff-mt-slot .nums b { font-weight: 700; }
.ff-mt-slot .nums i { font-style: normal; color: var(--mud-palette-text-secondary); }

/* Season strip: denser than .ff-mt-tile so eight numbers on one panel still scan. */
.ff-mt-strip { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 10px; }

.ff-mt-stat {
    padding: 8px 10px;
    border-radius: 10px;
    background: var(--mud-palette-background-gray);
    border: 1px solid var(--mud-palette-lines-default);
    min-width: 0;
}

.ff-mt-stat .k {
    display: block;
    color: var(--mud-palette-text-secondary);
    font-size: .64rem;
    text-transform: uppercase;
    letter-spacing: .05em;
}

.ff-mt-stat .v {
    display: block;
    font-weight: 700;
    font-size: 1.05rem;
    font-variant-numeric: tabular-nums;
    margin-top: 2px;
    overflow-wrap: anywhere;
}

.ff-mt-stat .v .of { font-size: .72rem; font-weight: 600; color: var(--mud-palette-text-secondary); }

.ff-mt-note { color: var(--mud-palette-text-secondary); font-size: .78rem; padding: 4px 0; }

@media (min-width: 600px) {
    .ff-mt-strip { grid-template-columns: repeat(4, minmax(0, 1fr)); }
}

@media (max-width: 400px) {
    .ff-mt-slot { grid-template-columns: 38px minmax(0, 1fr) auto; gap: 6px; }
    .ff-mt-slot > .ff-pos { min-width: 38px; }
    .ff-mt-slot .nums { font-size: .72rem; }
}

/* ============================================================================================
   Punch 2026-07-27 (P-17) - Scoreboard Season Total row expansion (ScoreboardSeasonPanel).
   The Season tab used to expand into the same current-week lineup the This Week tab shows; it now
   expands into a season summary. Deliberately reuses the ff-sb-panel indent and the ff-sb-lineup-*
   loading/empty treatments above, so only the season-specific rows are new here. Mobile-first: the
   contributor row is a 3-column grid that collapses to name + points at 360px, and the stat line
   wraps rather than scrolling.
   ============================================================================================ */
.ff-sb-season { display: flex; flex-direction: column; gap: 2px; }

.ff-sb-season-head {
    font-size: .68rem; font-weight: 700; letter-spacing: .05em; text-transform: uppercase;
    color: var(--mud-palette-text-secondary); padding: 2px 2px 4px;
}

.ff-sb-carry {
    display: grid; grid-template-columns: 20px 1fr auto; align-items: center; gap: 10px;
    padding: 6px 2px; border-bottom: 1px solid var(--mud-palette-lines-default);
}
.ff-sb-carry-rank {
    font-size: .68rem; font-weight: 700; font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary); text-align: center;
}
.ff-sb-carry-main { min-width: 0; display: flex; flex-direction: column; gap: 1px; }
.ff-sb-carry-main .name {
    font-size: .87rem; font-weight: 600;
    overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}
.ff-sb-carry-sub { font-size: .68rem; color: var(--mud-palette-text-secondary); }
.ff-sb-carry .pt { font-variant-numeric: tabular-nums; font-weight: 700; font-size: .87rem; }

/* The compact season line: best week, average per week, weeks won. The last contributor row's own
   bottom border is the divider, so this block adds spacing rather than a second rule. */
.ff-sb-season-line {
    display: flex; flex-wrap: wrap; gap: 6px 16px;
    margin-top: 8px;
}
.ff-sb-season-stat { display: flex; flex-direction: column; gap: 1px; min-width: 0; }
.ff-sb-season-stat .k {
    font-size: .62rem; font-weight: 700; letter-spacing: .04em; text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}
.ff-sb-season-stat .v { font-size: .84rem; font-weight: 600; font-variant-numeric: tabular-nums; }

/* ============================================================================================
   Punch 2026-07-27 (P-25) — Records Book head-to-head picker. The wrap-based row let the two
   member selects land on different lines with different partners (A beside "vs", B beside the
   Compare button), so they rendered at different widths on a phone. Under 600px each control
   takes its own full-width line: both selects identical, the "vs" divider centered, the button
   full width. Desktop keeps the single-row layout above.
   ============================================================================================ */
@media (max-width: 599.98px) {
    .ff-rivalry-picker > .mud-input-control { flex: 1 1 100%; min-width: 0; }
    .ff-rivalry-picker .ff-rivalry-vs { flex: 1 1 100%; text-align: center; }
    .ff-rivalry-picker > .mud-button-root { flex: 1 1 100%; }
}

/* ============================================================================================
   Moat on Display MD-D - the /leaders full-landscape leaderboard.

   The board is intentionally a wide table (rank, player, team, position, games, points, the picked
   stat, and the headline stat line), so at phone widths it scrolls INSIDE its own container and the
   page body never scrolls sideways. The rank and player columns stay pinned while the numbers scroll
   past, so a value is always attached to a name. The pinned cells carry the surface background (and
   a hairline on the right edge of the name column) so scrolled content passes underneath cleanly.
   ============================================================================================ */
.ff-leaders-note { margin-top: -8px; }
.ff-leaders-toolbar { align-items: flex-end; }
.ff-leaders-scroll { overflow-x: auto; -webkit-overflow-scrolling: touch; }
.ff-leaders-table { min-width: 100%; }
.ff-leaders-table td.muted { color: var(--mud-palette-text-secondary); }
/* Fixed and box-sized so the sticky offset of the name column below is exact, whatever the ambient
   box model. 40px holds a two-digit rank at the table's 8px cell padding. */
.ff-leaders-table th.rankcol, .ff-leaders-table td.rankcol {
    width: 40px; min-width: 40px; box-sizing: border-box; padding-left: 8px; padding-right: 8px;
}

@media (max-width: 599.98px) {
    /* The one-control-per-line stack that used to live here is superseded by .ff-filter-grid (triage
       T-1, in the appended block at the end of this file): six full-width rows consumed the whole
       first phone viewport before any data rendered. */

    .ff-leaders-table th.rankcol, .ff-leaders-table td.rankcol {
        position: sticky; left: 0; z-index: 2;
        background: var(--mud-palette-surface);
    }
    .ff-leaders-table th.namecol, .ff-leaders-table td.namecol {
        position: sticky; left: 40px; z-index: 2;
        background: var(--mud-palette-surface);
        box-shadow: 1px 0 0 0 var(--mud-palette-lines-default);
    }
    /* The striped/hover rows would otherwise show through the pinned cells. */
    .ff-leaders-table tbody tr:hover td.rankcol,
    .ff-leaders-table tbody tr:hover td.namecol { background: var(--mud-palette-surface); }
}
/* ============================================================================================
   Wake the Rails B1 (FI-16) - bulk invite outcomes on the league members page. One row per
   pasted address: status icon, the address, and a short note. The address column shrinks and
   ellipsizes before the note wraps, so a long address never pushes the note off a 360px screen.
   ============================================================================================ */
.ff-bulk-invite-results { display: grid; gap: 6px; }
.ff-bulk-invite-row {
    display: flex; align-items: center; gap: 8px; flex-wrap: wrap;
    font-size: .82rem; line-height: 1.35; min-width: 0;
}
.ff-bulk-invite-email {
    font-weight: 600; min-width: 0; max-width: 100%;
    overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}
.ff-bulk-invite-note { color: var(--mud-palette-text-secondary); }

/* ============================================================================================
   Saturday Habit C1 (2026-07-27) — install-to-notify onboarding.
   .ff-push-notice is the notification center's quiet "alerts are off on this device" line: a
   caption-weight row that wraps onto its own lines at 360px rather than squeezing the button off
   the edge. .ff-pwa-inline-icon lets the iOS Share glyph sit on the text baseline inside the
   add-to-home-screen instructions.
   ============================================================================================ */
.ff-push-notice {
    display: flex; flex-wrap: wrap; align-items: center; gap: 4px 8px;
    margin: 0 0 12px; min-width: 0;
}
.ff-push-notice .mud-typography { flex: 1 1 220px; min-width: 0; }
.ff-pwa-inline-icon { vertical-align: text-bottom; margin: 0 2px; }

/* ============================================================================================
   Saturday Habit C5 (FI-26) - the Game Day "watch your roster" TV slate. Two additive surfaces
   over the already-cached CFBD media feed, both invisible when that feed knows nothing about a
   school (the normal pre-warm state): a per-slot line under the player name ("Sat 3:30 PM on
   ABC") and the compact by-kickoff "Your slate" block on the My Team card. Everything keys off
   the MudBlazor palette vars so light and dark both read; the slate rows collapse to a stacked
   two-line layout under 400px so a 360px phone never scrolls sideways.
   ============================================================================================ */

/* Per-slot line. Sits under the name/game chip inside .ff-gd-main's column flow, so it inherits
   that stack's 3px gap and never widens the grid (min-width:0 + ellipsis do the clamping). */
.ff-gd-slate {
    display: inline-flex; align-items: center; gap: 5px;
    font-size: .7rem; font-weight: 600;
    color: var(--mud-palette-text-secondary);
    min-width: 0; max-width: 100%;
}
.ff-gd-slate .ff-gd-slate-ico { font-size: .95rem; flex: none; opacity: .7; }
/* The clamp lives on the text child, not the flex container: text-overflow only applies to a block
   box, so a bare text node in a flex row would overflow instead of ellipsizing (the same reason
   .ff-gd-chip puts its ellipsis on .opp). Matters for long networks ("Big Ten Network") at 360px. */
.ff-gd-slate .txt { min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }

/* The compact by-kickoff block on the member card. */
.ff-gd-slate-list {
    margin: 4px 6px 10px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 10px;
    overflow: hidden;
}
.ff-gd-slate-list .hd {
    display: flex; align-items: center; gap: 6px;
    padding: 7px 10px;
    font-size: .66rem; font-weight: 700; letter-spacing: .08em; text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
    background: var(--mud-palette-background);
}
/* MudBlazor's Size.Small icon is 1.25rem, which dwarfs a .66rem uppercase label; pull it back. */
.ff-gd-slate-list .hd .mud-icon-root { font-size: 1rem; }
.ff-gd-slate-list .row {
    display: grid; grid-template-columns: minmax(80px, auto) minmax(44px, auto) 1fr;
    align-items: center; gap: 4px 10px;
    padding: 7px 10px;
    border-top: 1px solid var(--mud-palette-lines-default);
    font-size: .76rem;
}
.ff-gd-slate-list .row .tm { font-weight: 700; font-variant-numeric: tabular-nums; white-space: nowrap; }
.ff-gd-slate-list .row .net { font-weight: 600; color: var(--mud-palette-primary); white-space: nowrap; }
.ff-gd-slate-list .row .who {
    min-width: 0; color: var(--mud-palette-text-secondary);
    overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}

/* Phone: time + network stay on one line, the player names wrap to their own full-width line. */
@media (max-width: 399.98px) {
    .ff-gd-slate-list .row { grid-template-columns: 1fr auto; }
    .ff-gd-slate-list .row .who { grid-column: 1 / -1; }
}

/* ============================================================================================
   Regret Engine RE-B - the member draft-efficiency surfaces.

   Three blocks, all appended here so parallel slices merge cleanly:
     1. Pool spotlight card (Scoreboard, above the tabs): two tiles, stacked on a phone and
        side by side from 600px, with the shared-denominator footnote as desktop-only detail.
     2. Capture chip on every standings row (decision D1): the compact percent always shows;
        its points-left detail earns the meta line only from 600px up.
     3. Personal efficiency panel (expanded own row) and the My Team regret replay rows.

   Percent values are NOT clamped at 100: a member who started a player the computed pool missed
   can honestly capture more than the pool's best legal roster, so nothing here assumes a 0..100
   range or draws a fill bar that would break past it.
   ============================================================================================ */

/* -- 1. Pool spotlight card ---------------------------------------------------------------- */
.ff-eff-card { margin-bottom: 16px; }
.ff-eff-week { font-size: .78rem; color: var(--mud-palette-text-secondary); font-variant-numeric: tabular-nums; }
.ff-eff-loading { display: flex; justify-content: center; padding: 18px; }

.ff-eff-spot { display: grid; grid-template-columns: 1fr; gap: 12px; }
.ff-eff-tile {
    display: flex; flex-direction: column; gap: 3px; min-width: 0;
    padding: 12px 14px; border-radius: 12px;
    border: 1px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-background);
}
.ff-eff-tile.mvp { border-left: 3px solid var(--mud-palette-success); }
.ff-eff-tile.away { border-left: 3px solid var(--mud-palette-warning); }
.ff-eff-tile .k {
    display: flex; align-items: center; gap: 6px;
    font-size: .62rem; font-weight: 700; letter-spacing: .05em; text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}
.ff-eff-tile .nm { font-size: 1rem; font-weight: 700; min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-eff-tile .nm.muted { color: var(--mud-palette-text-secondary); }
.ff-eff-tile .pts { font-size: .9rem; font-weight: 600; font-variant-numeric: tabular-nums; }
.ff-eff-tile .sub { font-size: .72rem; color: var(--mud-palette-text-secondary); }

/* The shared denominator is context, not the headline: it earns its line only at desktop width. */
.ff-eff-note { display: none; margin-top: 12px; font-size: .74rem; color: var(--mud-palette-text-secondary); }

/* Entity-linked names stay visually quiet inside a dense card (the Batch B link convention). */
.ff-eff-name.ff-link { color: inherit; }
.ff-eff-name.ff-link:hover { color: var(--mud-palette-primary); }

@media (min-width: 600px) { .ff-eff-spot { grid-template-columns: 1fr 1fr; } }
@media (min-width: 960px) { .ff-eff-note { display: block; } }

/* -- 2. Capture chip on the standings rows -------------------------------------------------- */
.ff-sb-chip {
    flex: 0 0 auto; white-space: nowrap;
    font-size: .62rem; font-weight: 700; font-variant-numeric: tabular-nums;
    padding: 1px 6px; border-radius: 999px;
    background: rgba(var(--mud-palette-primary-rgb), .16); color: var(--mud-palette-primary);
}
/* Phone rows keep the compact badge only; the points-left detail returns with the room for it. */
.ff-sb-chipdetail { display: none; font-variant-numeric: tabular-nums; }
@media (min-width: 600px) { .ff-sb-chipdetail { display: inline; } }

/* -- 3. Personal panel + regret replay ------------------------------------------------------ */
.ff-eff-panel { display: flex; flex-direction: column; gap: 10px; padding: 8px 2px 12px; }
.ff-eff-none { font-size: .82rem; color: var(--mud-palette-text-secondary); }
.ff-eff-headline { display: flex; align-items: baseline; gap: 10px; flex-wrap: wrap; }
.ff-eff-pct { font-size: 1.6rem; font-weight: 800; line-height: 1; font-variant-numeric: tabular-nums; }
.ff-eff-of { font-size: .78rem; color: var(--mud-palette-text-secondary); font-variant-numeric: tabular-nums; }

.ff-eff-stats { display: flex; flex-wrap: wrap; gap: 8px; }
.ff-eff-stat {
    flex: 1 1 120px; min-width: 0; display: flex; flex-direction: column; gap: 2px;
    padding: 8px 10px; border-radius: 10px; background: var(--mud-palette-background);
}
.ff-eff-stat .k {
    font-size: .6rem; font-weight: 700; letter-spacing: .04em; text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}
.ff-eff-stat .v { font-size: .95rem; font-weight: 700; font-variant-numeric: tabular-nums; }
.ff-eff-stat .v.good { color: var(--mud-palette-success); }

.ff-eff-away { display: flex; align-items: baseline; gap: 8px; flex-wrap: wrap; font-size: .8rem; }
.ff-eff-away .k { color: var(--mud-palette-text-secondary); font-size: .72rem; }
.ff-eff-away .nm { font-weight: 600; min-width: 0; }
.ff-eff-away .pts { font-variant-numeric: tabular-nums; font-weight: 700; }
.ff-eff-footnote { font-size: .7rem; color: var(--mud-palette-text-secondary); }

.ff-eff-replay { max-width: 720px; margin-top: 16px; }
.ff-eff-replay-sub {
    padding: 10px 14px 6px; font-size: .78rem;
    color: var(--mud-palette-text-secondary); font-variant-numeric: tabular-nums;
}

/* One line per slot at phone width (played on row 1, the comparison wrapped under it), two
   columns from 600px. The position chip keeps the ff-roster-row rhythm either way. */
.ff-eff-rr {
    display: grid; grid-template-columns: 52px 1fr; gap: 4px 12px; align-items: center;
    padding: 11px 14px; border-bottom: 1px solid var(--mud-palette-lines-default);
}
.ff-eff-rr:last-child { border-bottom: 0; }
.ff-eff-rr .played { grid-column: 2; display: flex; align-items: baseline; gap: 8px; min-width: 0; }
.ff-eff-rr .played .nm { font-size: .89rem; min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.ff-eff-rr .played .nm.empty { color: var(--mud-palette-text-secondary); font-style: italic; }
.ff-eff-rr .played .pts { font-variant-numeric: tabular-nums; font-weight: 600; margin-left: auto; }
.ff-eff-rr .best {
    grid-column: 2; display: flex; align-items: baseline; gap: 6px; flex-wrap: wrap;
    font-size: .76rem; color: var(--mud-palette-text-secondary); min-width: 0;
}
.ff-eff-rr .best .nm { font-weight: 600; color: var(--mud-palette-text-primary); min-width: 0; }
.ff-eff-rr .best .pts { font-variant-numeric: tabular-nums; font-weight: 700; }
/* Fallback rgb triple so the praise tint still lands if the theme ever stops emitting the var. */
.ff-eff-rr.optimal { background: rgba(var(--mud-palette-success-rgb, 0, 200, 83), .07); }

.ff-eff-praise { font-weight: 700; color: var(--mud-palette-success); white-space: nowrap; }
.ff-eff-gain { font-weight: 700; color: var(--mud-palette-warning); font-variant-numeric: tabular-nums; }
.ff-eff-tag {
    font-size: .6rem; font-weight: 700; letter-spacing: .04em; text-transform: uppercase;
    padding: 1px 5px; border-radius: 6px;
    background: var(--mud-palette-background); color: var(--mud-palette-text-secondary);
}

/* A league-configurable slot label outside the shipped five gets a neutral chip rather than
   borrowing another position's colour. */
.ff-pos.slot { background: #64748b; }

@media (min-width: 600px) {
    .ff-eff-rr { grid-template-columns: 52px minmax(0, 1fr) minmax(0, 1fr); }
    .ff-eff-rr .best { grid-column: 3; justify-content: flex-end; }
}

/* ============================================================================================
   Moat MD-B (2026-07-27) - defense-vs-position surfaces.
   The band chip (DvpBandChip), the per-team card row (DvpGrid, Teams hub Defense tab), the Player
   Hub scouting line, and the draft-board row chip. Colour comes from the BAND only, and it reuses
   the 16C trap/boom palette on purpose so DvP and matchup tags read as one research language:
   a stingy defense is the hard end (red/amber), a soft one is the opportunity end (blue/green).
   Breakpoints follow the plan matrix: 360 = chip glyph only, 600 = chip + "vs WR", 960 = chip +
   the full phrase; the card row stacks at 360, goes three-across at 600, and shows the landscape
   rank line at 960. Nothing here can widen the page (the card row is its own grid).
   ============================================================================================ */
.ff-dvp-chip {
    display: inline-flex; align-items: center; gap: 3px; flex-shrink: 0;
    font-size: .6rem; font-weight: 700; line-height: 1.7; padding: 0 6px;
    border-radius: 8px; white-space: nowrap;
}
.ff-dvp-chip.top10 { color: var(--mud-palette-error); background: rgba(244, 67, 54, .16); }
.ff-dvp-chip.tough { color: var(--mud-palette-warning); background: rgba(255, 152, 0, .16); }
.ff-dvp-chip.average { color: var(--mud-palette-text-secondary); background: rgba(158, 158, 158, .16); }
.ff-dvp-chip.soft { color: var(--mud-palette-info); background: rgba(3, 169, 244, .16); }
.ff-dvp-chip.bottom10 { color: var(--mud-palette-success); background: rgba(76, 175, 80, .16); }
.ff-dvp-chip.none { color: var(--mud-palette-text-secondary); background: transparent; padding: 0 4px; font-weight: 600; }
.ff-dvp-chip .ff-dvp-pos { opacity: .75; }

/* Full band word from 600px; the 3-letter form below it (the matchup-chip idiom). */
.ff-dvp-short { display: none; }
@media (max-width: 599.98px) {
    .ff-dvp-full { display: none; }
    .ff-dvp-short { display: inline; }
}

/* ---- DvpGrid: one defense's QB/RB/WR cards ---- */
.ff-dvp-cards { display: grid; grid-template-columns: minmax(0, 1fr); gap: 10px; }
.ff-dvp-card {
    border: 1px solid var(--mud-palette-lines-default); border-radius: 10px;
    padding: 10px 12px; min-width: 0;
}
.ff-dvp-card-head { display: flex; align-items: center; gap: 8px; flex-wrap: wrap; }
.ff-dvp-card-val {
    margin-top: 6px; font-size: 1.25rem; font-weight: 700; font-variant-numeric: tabular-nums;
    display: flex; align-items: baseline; gap: 5px;
}
.ff-dvp-card-val.muted { color: var(--mud-palette-text-secondary); font-weight: 600; }
.ff-dvp-card-val .u { font-size: .68rem; font-weight: 600; color: var(--mud-palette-text-secondary); }
.ff-dvp-card-sub { font-size: .72rem; color: var(--mud-palette-text-secondary); margin-top: 2px; }
.ff-dvp-card-rank { display: none; font-size: .72rem; color: var(--mud-palette-text-secondary); margin-top: 2px; }
.ff-dvp-explainer { font-size: .72rem; color: var(--mud-palette-text-secondary); margin-top: 10px; }

@media (min-width: 600px) {
    .ff-dvp-cards { grid-template-columns: repeat(3, minmax(0, 1fr)); }
}
@media (min-width: 960px) {
    .ff-dvp-card-rank { display: block; }
}

/* ---- Player Hub scouting line ---- */
.ff-dvp-scout { display: flex; align-items: center; gap: 8px; flex-wrap: wrap; }
.ff-dvp-scout-phrase { font-size: .85rem; font-weight: 600; min-width: 0; }

/* ---- Draft board row chip ----
   The chip shares the existing pick-main cell (no new grid column), so the row keeps its four
   columns at every width and the team/owner line still ellipsizes instead of pushing the chip out. */
.ff-pick-row .pick-subline { display: flex; align-items: center; gap: 6px; min-width: 0; }
.ff-pick-row .pick-subline > .pick-sub { min-width: 0; flex: 0 1 auto; }
.ff-dvp-inline { display: inline-flex; align-items: center; gap: 5px; flex-shrink: 0; }
.ff-dvp-inline-pos, .ff-dvp-inline-full { display: none; }
.ff-dvp-inline-pos, .ff-dvp-inline-full {
    font-size: .68rem; color: var(--mud-palette-text-secondary); white-space: nowrap;
}
@media (min-width: 600px) {
    .ff-dvp-inline-pos { display: inline; }
}
@media (min-width: 960px) {
    .ff-dvp-inline-pos { display: none; }
    .ff-dvp-inline-full { display: inline; }
}
/* ---- Regret Engine RE-D: League Buzz gains the Pool Spotlight card ----
   The base .ff-buzz-cols grid is 3-across at >=961px (recap / power ranking / weekly awards). When a
   week also has a Pool Spotlight card the row would leave a lone fourth card stranded, so the grid
   drops to a clean 2x2. The modifier only lands when the card is actually present, which means a
   deploy with Features:DraftEfficiencyEnabled dark keeps today's exact three-across layout. Mobile is
   untouched: .ff-cols already stacks to one column at <=960px, so every card is full width at 360px. */
@media (min-width: 961px) {
    .ff-buzz-cols.has-spotlight { grid-template-columns: 1fr 1fr; }
}
/* ---- end RE-D ---- */

/* ============================================================================================
   Regret Engine RE-C (2026-07-27) - the season draft-efficiency leaderboard, the Scoreboard's
   fourth tab.

   The board is a seven-column table (rank, member, average capture, weeks counted, best, worst,
   trend), which is wider than a 360px phone. It therefore scrolls INSIDE its own container and the
   page body never scrolls sideways (the MD-D /leaders rule, reused verbatim): below 600px the rank
   and member columns pin to the left edge so a percent is always attached to a name, and the pinned
   cells carry the surface background so scrolled content passes underneath cleanly.

   The trend column is desktop detail (plan §9 breakpoint matrix: sparkline hidden at 360, present
   from 600). Hiding the CELL rather than the chart keeps the header and body column counts in step,
   so the pinned offsets stay exact at every width.

   Nothing here is loaded while Features:DraftEfficiencyEnabled is dark: the tab that mounts the
   board does not render at all, so these rules simply never match.
   ============================================================================================ */
.ff-eff-season-note {
    display: flex; align-items: center; gap: 6px; flex-wrap: wrap;
    padding: 6px 6px 10px; font-size: .78rem; color: var(--mud-palette-text-secondary);
}
.ff-eff-season-scroll { overflow-x: auto; -webkit-overflow-scrolling: touch; }
.ff-eff-season-table { min-width: 100%; }
.ff-eff-season-table td.muted { color: var(--mud-palette-text-secondary); }
/* The week under a best/worst percent is context, not a second number to scan. */
.ff-eff-season-table .wk {
    display: block; font-size: .66rem; font-weight: 400;
    color: var(--mud-palette-text-secondary);
}
/* Fixed and box-sized so the sticky offset of the member column below is exact, whatever the
   ambient box model. 40px holds a two-digit rank at the table's 8px cell padding. */
.ff-eff-season-table th.rankcol, .ff-eff-season-table td.rankcol {
    width: 40px; min-width: 40px; box-sizing: border-box; padding-left: 8px; padding-right: 8px;
}
.ff-eff-season-table th.sparkcol, .ff-eff-season-table td.sparkcol {
    width: 130px; padding-top: 2px; padding-bottom: 2px;
}

@media (max-width: 599.98px) {
    .ff-eff-season-table th.sparkcol, .ff-eff-season-table td.sparkcol { display: none; }

    .ff-eff-season-table th.rankcol, .ff-eff-season-table td.rankcol {
        position: sticky; left: 0; z-index: 2;
        background: var(--mud-palette-surface);
    }
    .ff-eff-season-table th.namecol, .ff-eff-season-table td.namecol {
        position: sticky; left: 40px; z-index: 2;
        background: var(--mud-palette-surface);
        box-shadow: 1px 0 0 0 var(--mud-palette-lines-default);
    }
    /* The hover row would otherwise show through the pinned cells. */
    .ff-eff-season-table tbody tr:hover td.rankcol,
    .ff-eff-season-table tbody tr:hover td.namecol { background: var(--mud-palette-surface); }
}
/* ---- end RE-C ---- */

/* ================================================================================================
   Owner testing triage (2026-07-27) - phone findings from the owner's live dev session on an
   iPhone. Two surfaces, one theme: a phone viewport is a budget, and these two spent it on chrome.

   T-1  /leaders filter row. Five or six outlined selects at one per line filled the entire first
        viewport before a single leader rendered. .ff-filter-grid packs them TWO PER ROW below
        600px, which is the density idiom the app already settled on for phones (P-13's
        .ff-rl-stats two-column mobile card, and the .ff-rivalry-picker flex-basis collapse). Six
        rows become three (measured at 360px: the six pickers occupy 190px of height instead of the
        ~400px the stack cost); an odd control count spans its last cell so the grid never ends
        ragged (P-13's .span2 rule, expressed structurally so no markup has to know its parity). It is
        a named, reusable class rather than a page rule so the next filter-heavy surface can adopt
        it without a second invention. Desktop is untouched: above 600px the element is still the
        plain .ff-toolbar flex row it has always been.

   T-3/T-4  Draft Efficiency season board. Two problems with one cause, the row box. Every number
        below is MEASURED in a 360px viewport against this stylesheet, before and after:
        - Density. The best/worst cells stacked a percent over a "Week 3" caption, so EVERY row was
          47px tall whether or not those columns were even on screen. Below 600px the caption rides
          INLINE after the percent instead ("92% Week 3"), which is the same information on one line,
          and the cell padding tightens to 5px/8px. A row measures 36px, so a ten member league costs
          about a quarter less scrolling.
        - Tap targets do not shrink with the rows. The member link's hit box was only ever its text
          line (the old row height was cell padding, which sits OUTSIDE the anchor), so the anchor is
          given its own vertical padding here: measured, the hit box GROWS from 17px to 25px while
          the row still shrinks by 11px.
        - The clipped WEEKS column. At 360px the four columns that matter measured 380px wide
          (40 rank + 163 member + 105 capture + 72 weeks), so "11 of 14" was cut 20px short at the
          viewport edge and the in-container scroll (which is by design) had to be used just to read
          the headline number. Three trims fix it without hiding anything: the 8px horizontal cell
          padding above, the member column capped and ellipsized, and the "Avg capture" header
          abbreviating to "Avg" below 600px (the .ff-dvp-full / .ff-dvp-short idiom, reused
          verbatim). Measured after: 40 + 124 + 41 + 64 = 269px, so all four land inside a 360px
          viewport with room to spare and best/worst/trend are what the member scrolls to. The table
          is still 443px wide, so the horizontal scroll stays where the design put it (inside the
          container, never the page body).

   T-5  is a copy change in the component, not CSS: .ff-eff-season-scope is the line that names the
        pool a capture is measured against, so a season whose weeks carry no conference restriction
        reads as "measured against all of FBS", not as a broken number.
   ================================================================================================ */

/* ---- T-1: the two-per-row phone filter grid ---- */
/* Above 600px this class contributes nothing; the element is its .ff-toolbar flex row. */
@media (max-width: 599.98px) {
    .ff-filter-grid {
        display: grid;
        grid-template-columns: repeat(2, minmax(0, 1fr));
        gap: 8px 10px;
        align-items: end;
        margin-bottom: 12px;
    }
    /* The pickers carry per-control inline max-widths sized for the desktop row; in the grid the
       track is the width, so they must be free to fill it. The selector is the direct child, whatever
       it is: a MudSelect's OWN root is div.mud-select and it carries the inline Style, while
       .mud-input-control is a level further in. (The stack rule this block replaces targeted
       .mud-input-control as a direct child, which never matched anything.) !important is required
       because the width being beaten is an inline style. */
    .ff-filter-grid > * {
        max-width: 100% !important;
        width: 100%;
        min-width: 0;
    }
    /* An odd control count (the Week picker only exists in single-week view) would otherwise leave a
       ragged half row, so the last control spans both tracks. */
    .ff-filter-grid > *:last-child:nth-child(odd) { grid-column: 1 / -1; }
}

/* ---- T-5: the line that names the pool a capture is measured against ---- */
/* Sits directly under .ff-eff-season-note (which carries its own 10px bottom pad), reads as a
   caption rather than a second headline, and wraps to two lines at 360px without crowding. */
.ff-eff-season-scope {
    margin-top: -8px;
    padding: 0 6px 10px;
    font-size: .72rem;
    line-height: 1.45;
    color: var(--mud-palette-text-secondary);
}

/* ---- T-3 / T-4: season efficiency board density at phone widths ---- */
/* The short column header is hidden by default and swaps in below 600px (DvP chip idiom). */
.ff-eff-dense .ff-col-short { display: none; }

@media (max-width: 599.98px) {
    .ff-eff-dense .ff-col-full { display: none; }
    .ff-eff-dense .ff-col-short { display: inline; }

    /* The row box. 8px horizontal is what buys the WEEKS column its place inside 360px. */
    .ff-eff-season-table.ff-eff-dense th,
    .ff-eff-season-table.ff-eff-dense td { padding: 5px 8px; }

    /* The best/worst week caption stops being a second line. Same words, one line, muted. */
    .ff-eff-season-table.ff-eff-dense .wk {
        display: inline;
        margin-left: 5px;
        font-size: .68rem;
    }

    /* The member column is capped and ellipsized so one long display name cannot push the capture
       and weeks columns off the viewport. It is a pinned column, so the cap also fixes how much of
       the row the pinned block eats. */
    .ff-eff-season-table.ff-eff-dense td.namecol,
    .ff-eff-season-table.ff-eff-dense th.namecol { max-width: 108px; }
    .ff-eff-season-table.ff-eff-dense td.namecol > * {
        display: inline-block;
        max-width: 100%;
        overflow: hidden;
        text-overflow: ellipsis;
        white-space: nowrap;
        vertical-align: middle;
        /* The tap target the tightened row must not cost: the anchor's own box, not the cell's. */
        padding: 4px 0;
    }
}
/* ---- end owner testing triage 2026-07-27 ---- */

/* ---- Season Readiness SR-B: the shared preseason / fallback note (plan §9) ----
   PreseasonNote reuses the ff-empty-state chrome, so this block only adds what the note needs on top
   of it: a readable measure and copy that WRAPS instead of truncating at 360px, which is the §6 SR-B
   acceptance line. No new panel type, no new colors, nothing that renders while the surrounding
   ff-empty-state is absent. Reused as-is by SR-C (Home / Welcome) and SR-D (the research fallback
   note), so keep it generic. */
.ff-season-note {
    /* Two comfortable lines at phone width rather than one long ellipsized one. */
    max-width: 46ch;
    margin: 0 auto;
    /* ff-empty-state centers its children; long sentences still need explicit wrapping because a
       school or member name inside the copy can be a single unbreakable token. */
    overflow-wrap: anywhere;
}

.ff-season-note .ff-season-note-link {
    /* Sits directly under the copy as its own tap target, at the 44px thumb-target guidance rather
       than MudButton Small's default height, because on a phone this is the note's only control. */
    margin-top: 4px;
    min-height: 44px;
}

@media (max-width: 599.98px) {
    .ff-season-note {
        max-width: 100%;
        /* ff-empty-state's 34px/20px is generous for a note that is the whole panel on a phone. */
        padding: 22px 14px;
    }
}
/* ---- end Season Readiness SR-B ---- */

/* ============================================================================================
   Season Readiness SR-D — the research fallback note (.ff-research-note).

   The line every research board shows while the picker is on the new season and the data is still
   last season's. It is a NOTE, not an alert: muted text, a small leading icon, and the same visual
   weight as .ff-ctx-note, because for the next month this is the normal state rather than a problem.

   360px: the icon is pinned (flex: 0 0 auto) and the sentence wraps under itself instead of
   truncating or pushing the row wider than the viewport, per the §9 breakpoint matrix.
   ============================================================================================ */

.ff-research-note {
    display: flex;
    align-items: flex-start;
    gap: 6px;
    margin: 0 0 12px;
    font-size: .78rem;
    line-height: 1.4;
    color: var(--mud-palette-text-secondary);
}

.ff-research-note .mud-icon-root {
    flex: 0 0 auto;
    font-size: 1rem;
    margin-top: 1px;
}

.ff-research-note > span {
    flex: 1 1 auto;
    min-width: 0;
    overflow-wrap: anywhere;
}

/* Inside a panel body the note sits under the head, so it carries the body's own gutter. */
.ff-panel-body > .ff-research-note { margin-bottom: 8px; }
/* ---- end Season Readiness SR-D ---- */

/* ---- DR-0: staleness + turn attention ---- */
/* The freshness affordance the Room already had, given to the Board (plan §9). It rides inside the
   existing .ff-toolbar flex row, so it wraps to a second line on phones instead of pushing the
   Year/Week selects off screen. */
.ff-draft-fresh {
    display: flex;
    align-items: center;
    gap: 4px;
    min-width: 0;
}

.ff-draft-updated {
    font-size: .72rem;
    line-height: 1.2;
    white-space: nowrap;
    color: var(--mud-palette-text-secondary);
}

/* Below 400px the caption is noise next to a 120px select pair: the stale strip carries the signal
   and the Refresh icon button stays. */
@media (max-width: 399.98px) {
    .ff-draft-updated { display: none; }
}

/* The stale strip. Deliberately NOT an error alert: the board underneath still holds good data, and
   replacing it with an error would be a worse lie than the staleness itself. Full-width above the
   content on phones, an inline chip from 600px up. */
.ff-draft-stale {
    display: flex;
    align-items: center;
    gap: 8px;
    width: 100%;
    padding: 6px 10px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 8px;
    background: var(--mud-palette-background-gray);
    color: var(--mud-palette-text-secondary);
    font-size: .78rem;
    line-height: 1.35;
}

.ff-draft-stale-txt {
    min-width: 0;
    flex: 1 1 auto;
}

@media (min-width: 600px) {
    .ff-draft-stale {
        width: auto;
        display: inline-flex;
    }
    .ff-draft-stale-txt { flex: 0 1 auto; }
}
/* ---- end DR-0 ---- */

/* ---- Season Readiness SR-F: the commissioner readiness checklist ---- */
/* Plan §9: at 360px the checklist is a VERTICAL LIST, one row per line, never a table. A table here
   would either overflow horizontally or truncate the detail sentence, and the detail sentence is the
   entire value of the row. The mark stays in its own fixed column so the labels line up; everything
   else is a single wrapping text column that grows downward instead of sideways. */

.ff-srf-score {
    font-size: .75rem;
    color: var(--mud-palette-text-secondary);
    white-space: nowrap;
}

/* The shared panel head is a single non-wrapping row. On the narrowest phones let the "n of 7 ready"
   counter drop under the title rather than squeeze it, since neither is worth truncating. */
@media (max-width: 419.98px) {
    .ff-srf-head {
        flex-wrap: wrap;
        row-gap: 2px;
    }
}

.ff-srf-lede {
    margin: 0 0 10px;
    color: var(--mud-palette-text-secondary);
}

.ff-srf-list {
    list-style: none;
    margin: 0;
    padding: 0;
    display: flex;
    flex-direction: column;
    gap: 2px;
}

.ff-srf-row {
    display: flex;
    align-items: flex-start;
    gap: 10px;
    padding: 9px 10px;
    border-radius: 10px;
    border: 1px solid transparent;
    background: var(--mud-palette-background-gray);
}

/* Status is carried by the icon's color AND by a left border, so the panel does not depend on color
   alone to say "this one needs you" (the same belt-and-braces the draft stale strip uses). */
.ff-srf-row.is-action { border-left: 3px solid var(--mud-palette-error); }
.ff-srf-row.is-attention { border-left: 3px solid var(--mud-palette-warning); }
.ff-srf-row.is-ready { border-left: 3px solid var(--mud-palette-success); }

.ff-srf-mark {
    flex: 0 0 auto;
    margin-top: 1px;
}

.ff-srf-txt {
    display: flex;
    flex-direction: column;
    gap: 2px;
    min-width: 0;
    flex: 1 1 auto;
}

.ff-srf-label {
    font-size: .84rem;
    font-weight: 600;
    line-height: 1.3;
}

.ff-srf-detail,
.ff-srf-when,
.ff-srf-who {
    font-size: .76rem;
    line-height: 1.4;
    color: var(--mud-palette-text-secondary);
    /* Long conference lists and week lists must wrap, not push the panel wide. */
    overflow-wrap: anywhere;
}

.ff-srf-when { font-variant-numeric: tabular-nums; }

.ff-srf-link {
    font-size: .76rem;
    align-self: flex-start;
    /* A 32px-tall tap target on a phone without stretching the row on desktop. */
    padding: 3px 0;
}

/* From tablet up the rows can breathe: the detail sits on one line beside a wider label column. */
@media (min-width: 600px) {
    .ff-srf-row { padding: 10px 12px; gap: 12px; }
    .ff-srf-label { font-size: .88rem; }
}
/* ---- end Season Readiness SR-F ---- */

/* ============================================================================================
   T-30: ambient live-draft indicator (LiveDraftIndicator.razor). ONE appended block.

   Two placements off the same state: a compact pill in the app bar and a bare dot beside the Draft
   drawer link. Global rather than scoped because the nav dot is rendered INSIDE MudNavLink's anchor,
   which a scoped sheet cannot reach.

   Colour carries the meaning: a live draft is the info accent, and YOUR turn is the success accent
   and pulses (the pulse is reserved for the state that actually needs the member to act). Both accents
   come from the MudBlazor palette variables, so light mode and dark mode are correct by construction.

   Mobile: from 600px down the pill drops its label and becomes a dot-sized target, so it can never
   crowd the brand mark, the league switcher, or the user menu at 360px. The nav dot is inline and 8px
   and therefore cannot wrap the Draft link at any width.
   ============================================================================================ */

.ff-livedraft {
    display: inline-flex;
    align-items: center;
    flex: 0 0 auto;
}

.ff-livedraft-dot {
    width: 8px;
    height: 8px;
    border-radius: 50%;
    background: var(--mud-palette-info);
    flex: none;
}

/* Your turn: the accent changes AND it pulses, so the two states are distinguishable without colour
   alone (the label and the tooltip carry the same distinction for anyone who cannot see it). */
.ff-livedraft.mine .ff-livedraft-dot {
    background: var(--mud-palette-success);
    animation: ff-pulse 1.4s ease-in-out infinite;
}

/* MudTooltip wraps the pill in its own inline-block root, which would sit on the toolbar's text
   baseline instead of its centre line. Make that wrapper a plain flex item so the pill is centred at
   both bar heights (the desktop bar is 72px, the phone bar is the MudBlazor default). */
.ff-appbar .mud-tooltip-root {
    display: inline-flex;
    align-items: center;
    flex: 0 0 auto;
}

/* --- app-bar pill --- */
.ff-livedraft-pill {
    gap: 6px;
    height: 30px;
    padding: 0 11px;
    margin-right: 4px;
    border-radius: 999px;
    text-decoration: none;
    border: 1px solid rgba(255, 255, 255, .28);
    background: rgba(255, 255, 255, .10);
    color: inherit;
    font-size: .72rem;
    font-weight: 700;
    letter-spacing: .07em;
    text-transform: uppercase;
    white-space: nowrap;
    transition: background .15s, border-color .15s;
}

.ff-livedraft-pill:hover {
    background: rgba(255, 255, 255, .18);
    text-decoration: none;
}

.ff-livedraft-pill.mine {
    border-color: var(--mud-palette-success);
    color: var(--mud-palette-success);
}

/* Phone: the label goes, the dot stays. A 30px round target still clears the tap minimum next to the
   bell, and the app bar keeps the layout the owner already signed off on. */
@media (max-width: 600px) {
    .ff-livedraft-pill {
        width: 30px;
        padding: 0;
        justify-content: center;
        margin-right: 0;
    }

    .ff-livedraft-pill .ff-livedraft-label {
        display: none;
    }
}

/* --- nav-drawer dot --- */
.ff-livedraft-navdot {
    margin-left: 8px;
    vertical-align: middle;
}
/* ---- end T-30 live-draft indicator ---- */

/* ============================================================================================
   LANDING BOOT STALL (2026-07-28) — scroll-reveal arming.

   Appended block, single owner. The Wave 2 reveal rules further up hide EVERY .ff-reveal element
   the moment html.ff-js-motion appears. public-motion.js is lazy-imported after PublicLayout's
   first render, so on a cold load that class arrived roughly 700ms AFTER the landing page had
   already painted (measured on a 4x-throttled main thread) and sections the visitor was looking at
   faded back out to opacity 0 before fading in again. That blink is the owner's "the bottom half of
   the page takes a few seconds to appear".

   Hiding is now opt-in per element: public-motion.js adds .ff-reveal--armed, and only ever to an
   element whose top edge is still below the fold, from a MutationObserver callback that runs before
   the next paint. This rule neutralises the pre-state for everything it has not armed. Specificity
   (0,3,0) beats the (0,2,0) rules above, so the Wave 2 block needs no edit, and the no-JS / crawler
   / prefers-reduced-motion contracts are untouched: without JS neither class is ever added and the
   markup stays authored visible.
   ============================================================================================ */

.ff-js-motion .ff-reveal:not(.ff-reveal--armed) {
    opacity: 1;
    transform: none;
    /* Only an armed element is ever promoted; unarmed ones never animate, so no layer for them. */
    will-change: auto;
}

/* Arming must SNAP, never fade out. The late init sweep arms whatever is still below the fold, and
   with the Wave 2 transition in force that read as a 0.6s fade to nothing just off-screen, which a
   visitor scrolling at that moment could catch. Transitions are governed by the after-change style,
   so dropping the transition only while armed-and-not-yet-revealed still leaves the reveal itself
   animating: adding .is-visible stops this rule matching and the Wave 2 transition takes over. */
.ff-js-motion .ff-reveal.ff-reveal--armed:not(.is-visible) {
    transition: none;
}
/* ---- end LANDING BOOT STALL ---- */

/* ============================================================================================
   33A: DRAFT CLOSED — the post-lock closing state in the draft room.

   The Complete branch keeps the inline button row it has always had (its rendered markup has to stay
   byte-identical to what shipped). The Closed branch is new, so it gets a class instead, and one rule
   the inline version never had: below 400px the two onward buttons stack to full width rather than
   wrapping to a lonely second row. 360px is the primary drafting width and "My Team" / "The Board" are
   the only actions left on a closed draft, so they are worth a full-width tap target each.
   ============================================================================================ */

.ff-draft-closed-actions {
    display: flex;
    flex-wrap: wrap;
    gap: 8px;
    margin-top: 8px;
}

@media (max-width: 399.98px) {
    .ff-draft-closed-actions {
        flex-direction: column;
        align-items: stretch;
    }
}
/* ---- end 33A draft closed ---- */

/* ============================================================================================
   33D: DRAFT RECAP — the post-draft surfaces shared by the room panel, the /draft/recap route,
   and the career page.

   These classes are SHARED between components, which is why they live here rather than in
   DraftRecap.razor.css: a scoped stylesheet only reaches the markup authored in its own file, and
   the grade card and the tendencies card are rendered from three different hosts.

   Two house rules are expressed in the CSS itself. Nothing here can make the page body scroll
   horizontally (the league board owns its own overflow container, in the page's scoped file), and
   every interactive target stays at or above 44px at 360px, which is the width members draft at.
   ============================================================================================ */

/* ---------------------------------------------------------------- the room panel ---- */

.ff-recap-panel {
    display: flex;
    flex-direction: column;
    gap: 10px;
    padding: 12px 14px;
    margin-bottom: 16px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 10px;
    background: var(--mud-palette-surface);
}

.ff-recap-panel.pending {
    font-size: .85rem;
    opacity: .75;
}

.ff-recap-panel-head {
    display: flex;
    align-items: center;
    gap: 6px;
}

.ff-recap-panel-head .ttl {
    font-size: .72rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    opacity: .75;
}

.ff-recap-panel-none {
    font-size: .84rem;
    opacity: .75;
}

/* A real link, sized as a tap target rather than a line of text with a hit box the height of its
   own font. 44px is the floor at every width, not only the small one. */
.ff-recap-panel-more {
    display: inline-flex;
    align-items: center;
    min-height: 44px;
    font-size: .82rem;
    font-weight: 600;
    text-decoration: none;
    color: var(--mud-palette-primary);
}

.ff-recap-panel-more:hover {
    text-decoration: underline;
}

/* ----------------------------------------------------------------- the grade card ---- */

.ff-recap-grade {
    display: flex;
    flex-direction: column;
    gap: 10px;
}

/* 360px stacks the letter above the number; 600px and up sets them side by side. The grade is the
   headline, so it never competes for width with the sentence explaining it. */
.ff-recap-grade-head {
    display: flex;
    flex-direction: column;
    align-items: flex-start;
    gap: 8px;
}

.ff-recap-grade-lines {
    display: flex;
    flex-direction: column;
    gap: 2px;
    min-width: 0;
}

.ff-recap-letter {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    min-width: 56px;
    min-height: 44px;
    padding: 4px 14px;
    border-radius: 10px;
    font-size: 1.5rem;
    font-weight: 800;
    line-height: 1;
    color: #fff;
    background: #64748b;
}

/* The board's inline form. Still a comfortable row target, just not a headline. */
.ff-recap-letter.sm {
    min-width: 40px;
    min-height: 28px;
    padding: 2px 8px;
    font-size: .9rem;
    border-radius: 6px;
}

/* Absolute bands, never curved, so a letter's colour is a property of the letter alone and two
   surfaces can never disagree about what a B looks like. */
.ff-recap-letter.great { background: #10b981; }
.ff-recap-letter.good  { background: #3b82f6; }
.ff-recap-letter.fair  { background: #f59e0b; }
.ff-recap-letter.poor  { background: #ef4444; }

.ff-recap-capture {
    font-size: .95rem;
    font-weight: 600;
    line-height: 1.35;
}

.ff-recap-rank {
    font-size: .82rem;
    opacity: .78;
}

.ff-recap-lens,
.ff-recap-unfilled,
.ff-recap-projected {
    font-size: .74rem;
    opacity: .65;
    line-height: 1.45;
}

.ff-recap-grade.compact .ff-recap-lens {
    font-size: .7rem;
}

/* The picks. One column at 360px, two from 960px: a five-slot roster reads as one glance on a
   phone and as a block on a desktop. */
.ff-recap-picks {
    display: grid;
    grid-template-columns: 1fr;
    gap: 6px;
    margin: 0;
    padding: 0;
    list-style: none;
}

.ff-recap-pick {
    display: flex;
    align-items: center;
    gap: 8px;
    min-height: 44px;
    padding: 4px 8px;
    border-radius: 8px;
    background: var(--mud-palette-background-gray);
    min-width: 0;
}

.ff-recap-pick-name {
    flex: 1 1 auto;
    min-width: 0;
    font-weight: 600;
    font-size: .85rem;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

.ff-recap-pick-team {
    flex: 0 1 auto;
    min-width: 0;
    font-size: .72rem;
    opacity: .65;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

.ff-recap-pick-value {
    flex: 0 0 auto;
    display: flex;
    align-items: baseline;
    gap: 6px;
    margin-left: auto;
}

.ff-recap-pick-value .rk {
    font-size: .66rem;
    opacity: .6;
}

.ff-recap-pick-value .vl {
    font-size: .85rem;
    font-weight: 700;
    font-variant-numeric: tabular-nums;
}

.ff-recap-gap,
.ff-recap-ai {
    display: flex;
    flex-direction: column;
    gap: 2px;
    padding: 8px 10px;
    border-radius: 8px;
    background: var(--mud-palette-background-gray);
}

.ff-recap-gap .k,
.ff-recap-ai .k {
    font-size: .64rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    opacity: .6;
}

.ff-recap-gap .v,
.ff-recap-ai .v {
    font-size: .82rem;
    line-height: 1.45;
}

.ff-recap-forward {
    display: inline-flex;
    align-items: center;
    min-height: 44px;
    font-size: .8rem;
    font-weight: 600;
    text-decoration: none;
    color: var(--mud-palette-primary);
}

.ff-recap-forward:hover {
    text-decoration: underline;
}

/* ------------------------------------------------------------ the tendencies card ---- */

.ff-recap-tend {
    display: flex;
    flex-direction: column;
    gap: 8px;
    padding: 12px 14px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 10px;
    background: var(--mud-palette-surface);
}

.ff-recap-tend.error {
    font-size: .82rem;
    opacity: .7;
}

.ff-recap-tend-head {
    display: flex;
    align-items: center;
    gap: 6px;
}

.ff-recap-tend-head .ttl {
    font-size: .72rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    opacity: .75;
}

.ff-recap-tend-lead {
    font-size: .95rem;
    font-weight: 600;
    line-height: 1.35;
}

/* The first-timer line is a DESIGNED state, so it reads as a welcome and not as a shrunken error. */
.ff-recap-tend-first {
    font-size: .9rem;
    line-height: 1.45;
}

/* One tendency per row at 360px: these are sentences, and sentences do not sit side by side. */
.ff-recap-tend-list {
    display: flex;
    flex-direction: column;
    gap: 6px;
    margin: 0;
    padding-left: 18px;
    font-size: .82rem;
    line-height: 1.5;
}

.ff-recap-tend-skel {
    height: 14px;
    border-radius: 4px;
    background: var(--mud-palette-background-gray);
    opacity: .6;
}

.ff-recap-tend-skel:last-child {
    width: 62%;
}

/* --------------------------------------------------------------- 600px and wider ---- */

@media (min-width: 600px) {
    .ff-recap-grade-head {
        flex-direction: row;
        align-items: center;
        gap: 14px;
    }
}

@media (min-width: 960px) {
    .ff-recap-picks {
        grid-template-columns: 1fr 1fr;
    }
}
/* ---- end 33D draft recap ---- */

/* ============================================================================================
   34C: PRACTICE DRAFT ROOM (/mock).

   Two jobs. First, make practice unmistakable: an info-accent banner and a 2px info-accent left
   border on every practice card, so a screenshot pasted into the league chat can never be mistaken
   for the live room. Second, hold the §9 breakpoint matrix, which differs from the live board on
   purpose: the practice board drops the school at 360px (a practice pool has no matchup context to
   scan for) and the trend below 960px, where the live board keeps the school and shrinks instead.

   Everything here is prefixed ff-practice- and the board rows are scoped under .ff-practice-board,
   so the live draft room's own rules are untouched.
   ============================================================================================ */

/* --- the banner: a landmark, and the one element that renders in every state ----------------- */

.ff-practice-banner {
    border-left: 3px solid var(--mud-palette-info);
    background: rgba(33, 150, 243, .12);
}

/* Sticky from 600px so it stays on screen while the board scrolls. Deliberately STATIC at phone
   widths: a pinned bar there costs a fifth of the viewport members actually draft from. */
@media (min-width: 600px) {
    .ff-practice-banner {
        position: sticky;
        top: 0;
        z-index: 5;
    }
}

/* --- the practice card accent ---------------------------------------------------------------- */

.ff-practice-card {
    border-left: 2px solid var(--mud-palette-info);
}

/* --- setup panel ----------------------------------------------------------------------------- */

.ff-practice-setup-grid {
    display: grid;
    grid-template-columns: 1fr;
    gap: 12px;
}

/* One column of full-width selects on a phone, with tap targets that survive a thumb. */
.ff-practice-setup-grid .mud-input-control {
    min-height: 44px;
}

.ff-practice-setup-hint {
    display: block;
    margin-top: 10px;
}

.ff-practice-setup-actions {
    margin-top: 16px;
}

@media (min-width: 600px) {
    .ff-practice-setup-grid {
        grid-template-columns: repeat(2, minmax(0, 1fr));
    }
}

@media (min-width: 960px) {
    .ff-practice-setup-grid {
        max-width: 640px;
        margin: 0 auto;
    }

    .ff-practice-setup-actions {
        max-width: 640px;
        margin-left: auto;
        margin-right: auto;
    }
}

/* --- on-the-clock header --------------------------------------------------------------------- */

.ff-practice-clockhead {
    display: flex;
    flex-wrap: wrap;
    align-items: flex-start;
    gap: 8px;
}

.ff-practice-clockhead-who {
    flex: 1 1 200px;
    min-width: 0;
}

.ff-practice-clockhead-clock {
    flex: 0 0 auto;
    margin-left: auto;
}

/* 360px: the seat and the pick counter stack, and the clock drops below them. */
@media (max-width: 599.98px) {
    .ff-practice-clockhead {
        flex-direction: column;
    }

    .ff-practice-clockhead-clock {
        margin-left: 0;
    }
}

/* --- the selected pick ------------------------------------------------------------------------ */

/* "Draft <name> (practice)" is a long label by design, so let it wrap rather than overflow, and give
   it the full width on a phone where it is the only action that matters. */
.ff-practice-rec .mud-button-root {
    white-space: normal;
}

@media (max-width: 599.98px) {
    .ff-practice-rec {
        flex-direction: column;
        align-items: stretch;
    }

    .ff-practice-rec .mud-button-root {
        width: 100%;
    }
}

/* --- the board: head, filter chips, rows ------------------------------------------------------ */

.ff-practice-bahead {
    display: flex;
    align-items: center;
    gap: 8px;
    flex-wrap: wrap;
}

/* The #55 behaviour, unscoped (the live room's copy lives in a component-scoped stylesheet): the head
   may wrap to two ROWS, but the chip group itself never wraps. It scrolls horizontally as a last
   resort so DEF never drops to a lonely second line at 360px. */
.ff-practice-filters {
    display: flex;
    flex-wrap: nowrap;
    gap: 6px;
    margin-left: auto;
    min-width: 0;
    max-width: 100%;
    overflow-x: auto;
    -webkit-overflow-scrolling: touch;
    scrollbar-width: none;
    padding-bottom: 1px;
}

.ff-practice-filters::-webkit-scrollbar {
    display: none;
}

.ff-practice-filters .mud-button-root {
    flex: 0 0 auto;
    min-width: 0;
    padding: 1px 11px;
}

/* One action per row (select), not the live board's two, so the action track is narrower. */
.ff-practice-board .ff-practice-row {
    grid-template-columns: 30px minmax(0, 1.6fr) 46px minmax(0, 1fr) 46px 52px 44px;
}

/* Below 960px the trend chip goes: it is the least load-bearing cell, and a practice pool is often
   off-season, where a weekly trend means very little. */
@media (max-width: 959.98px) {
    .ff-practice-board .ff-practice-row {
        grid-template-columns: 30px minmax(0, 1.6fr) 46px minmax(0, 1fr) 52px 44px;
    }

    .ff-practice-board .ff-practice-row .ff-draft-trend {
        display: none;
    }
}

/* 360px: tier, name, position, value, action. The school goes too, so a long name gets the room and
   the row never forces the page to scroll sideways. */
@media (max-width: 599.98px) {
    .ff-practice-board .ff-practice-row {
        grid-template-columns: 26px minmax(0, 1fr) 34px 46px 38px;
        gap: 6px;
    }

    .ff-practice-board .ff-practice-row .ff-draft-team {
        display: none;
    }
}

/* --- recent picks ----------------------------------------------------------------------------- */

.ff-practice-recent {
    margin-top: 16px;
}

.ff-practice-recent-list {
    display: flex;
    flex-direction: column;
}

.ff-practice-recent-row {
    display: grid;
    align-items: center;
    gap: 8px;
    grid-template-columns: 36px 48px minmax(0, 1fr) minmax(0, .8fr);
    padding: 4px 2px;
    font-size: .82rem;
    border-bottom: 1px solid var(--mud-palette-lines-default);
    border-left: 2px solid transparent;
}

.ff-practice-recent-row:last-child {
    border-bottom: none;
}

.ff-practice-recent-row.mine {
    border-left-color: var(--mud-palette-success);
    background: rgba(76, 175, 80, .10);
}

.ff-practice-recent-no {
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
}

.ff-practice-recent-name {
    font-weight: 600;
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

.ff-practice-recent-seat {
    color: var(--mud-palette-text-secondary);
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

/* 360px: three rows, no seat column. The trim is CSS so the markup is identical at every width. */
@media (max-width: 599.98px) {
    .ff-practice-recent-row {
        grid-template-columns: 32px 42px minmax(0, 1fr);
        font-size: .78rem;
    }

    .ff-practice-recent-seat {
        display: none;
    }

    .ff-practice-recent-list .ff-practice-recent-row:nth-child(n+4) {
        display: none;
    }
}

/* --- abandon and completion actions ------------------------------------------------------------ */

/* Outside the room card and below the board, so a mis-tap while scanning cannot end the session. */
.ff-practice-abandon {
    display: flex;
    justify-content: center;
    margin: 4px 0 24px;
}

.ff-practice-complete-actions {
    display: flex;
    flex-wrap: wrap;
    gap: 8px;
    margin-top: 16px;
}

/* The stack is the LAST resort, not the phone default: at 399.98px it was firing at 360px, where the
   owner found two two-word buttons spending two rows of a phone. The compact sizing that holds them on
   one line lives in the practice-polish block at the end of this file. */
@media (max-width: 339.98px) {
    .ff-practice-complete-actions {
        flex-direction: column;
        align-items: stretch;
    }
}
/* ---- end 34C ---- */

/* ================================================================================================
   34D: PRACTICE CLOCK, AUTO-PICK, AND ABANDON.

   Appended after the 34C block rather than woven into it, so the two slices merge cleanly and a
   reviewer can see exactly what the clock pass added. Three small surfaces, and all three are phone
   cases: the note that says the clock picked for you, the confirmation in front of the one
   irreversible action on the page, and the on-the-clock header with a live countdown beside it.
   ================================================================================================ */

/* --- the "your clock ran out" note ------------------------------------------------------------ */

/* Two lines on purpose: the sentence names WHAT happened, the line under it names what was taken.
   A member reading this was looking somewhere else a moment ago, so neither half can be a glance. */
.ff-practice-autopick-head {
    font-weight: 600;
}

.ff-practice-autopick-detail {
    margin-top: 2px;
    font-size: .85rem;
    opacity: .92;
}

/* --- the abandon confirmation ----------------------------------------------------------------- */

/* 360px: stack the actions and reverse them, so the destructive button sits at the bottom where a
   thumb lands deliberately and "keep practicing" is not one mis-tap away from it. Full width so
   neither of them is a small target. */
@media (max-width: 599.98px) {
    .ff-practice-abandon-dialog .mud-dialog-actions {
        flex-direction: column-reverse;
        align-items: stretch;
        gap: 8px;
    }

    .ff-practice-abandon-dialog .mud-dialog-actions .mud-button-root {
        width: 100%;
        margin: 0;
    }
}

/* --- the header with a live countdown in it --------------------------------------------------- */

/* PickClock renders a chip once the deadline passes; MudBlazor's own chip margin would push it out
   of line with the seat text it sits beside. */
.ff-practice-clockhead-clock .mud-chip {
    margin: 0;
}

/* 360px: the clock is already stacked under the seat line by the 34C rule, so give it the full
   width there instead of letting a long countdown wrap against the card edge. */
@media (max-width: 599.98px) {
    .ff-practice-clockhead-clock {
        width: 100%;
    }
}
/* ---- end 34D ---- */

/* ================================================================================================
   34E: THE PRACTICE COMPLETION RECAP.

   Appended at the tail, after 34D, so the four practice slices merge cleanly and a reviewer can see
   exactly what the closing moment added.

   ONE FAMILY, TWO DENOMINATIONS. This deliberately borrows the 33D recap's visual language rather
   than inventing a parallel one: the same gray row plate, the same tabular-numeric value weight, the
   same tiny uppercase key over its value. The practice recap and the live recap are the same
   argument (what you took, against what was there), so they should not look like two products.

   THE ROW SHAPE IS THE §9 BREAKPOINT MATRIX, exactly. 360px stacks the pair vertically, your pick
   above and the best available below, because a side-by-side comparison in 160px of width is not a
   comparison. 600px puts them in two columns. 960px adds the delta as its own column: it is the
   pair's conclusion, and it only earns a column once there is room to read the pair beside it.
   ================================================================================================ */

.ff-practice-recap {
    margin-top: 16px;
}

/* --- the headline number, and why there is no grade beside it -------------------------------- */

/* The 33D house rule, carried across: the captured total never renders without the total it is
   measured against, so this line is a number a member can check rather than a claim. */
.ff-practice-recap-capture {
    font-size: .95rem;
    font-weight: 600;
    line-height: 1.35;
}

.ff-practice-recap-lens {
    margin-top: 2px;
    font-size: .74rem;
    opacity: .65;
    line-height: 1.45;
}

/* --- the per-pick rows ------------------------------------------------------------------------ */

.ff-practice-recap-rows {
    display: flex;
    flex-direction: column;
    gap: 6px;
    margin: 12px 0 0;
    padding: 0;
    list-style: none;
}

/* 360px: one column. Slot line, then what you took, then what was still there. */
.ff-practice-recap-row {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    align-items: center;
    gap: 4px 10px;
    padding: 8px 10px;
    border-radius: 8px;
    background: var(--mud-palette-background-gray);
    min-width: 0;
}

.ff-practice-recap-where {
    display: flex;
    align-items: center;
    gap: 8px;
    min-width: 0;
}

.ff-practice-recap-where .rd {
    font-size: .7rem;
    opacity: .6;
    white-space: nowrap;
}

/* Your pick and the best that was there share one shape on purpose: the comparison is only honest if
   neither side is presented more prominently than the other. */
.ff-practice-recap-took,
.ff-practice-recap-best {
    display: flex;
    align-items: baseline;
    gap: 6px;
    min-width: 0;
}

.ff-practice-recap-took .k,
.ff-practice-recap-best .k {
    flex: 0 0 auto;
    font-size: .62rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    opacity: .6;
}

.ff-practice-recap-took .v,
.ff-practice-recap-best .v {
    flex: 1 1 auto;
    min-width: 0;
    font-size: .85rem;
    font-weight: 600;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

.ff-practice-recap-took .tm {
    margin-left: 6px;
    font-size: .72rem;
    font-weight: 400;
    opacity: .65;
}

.ff-practice-recap-took .vl,
.ff-practice-recap-best .vl {
    flex: 0 0 auto;
    margin-left: auto;
    font-size: .85rem;
    font-weight: 700;
    font-variant-numeric: tabular-nums;
}

/* --- the delta chip: 960px and up only (§9) --------------------------------------------------- */

.ff-practice-recap-delta {
    display: none;
}

.ff-practice-recap-delta .chip {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    width: 100%;
    padding: 2px 6px;
    border-radius: 6px;
    font-size: .7rem;
    font-weight: 700;
    font-variant-numeric: tabular-nums;
    text-align: center;
    line-height: 1.25;
}

/* Calm on purpose. Practice is exactly where leaving value on the board is supposed to happen, so
   the gap is stated, not scolded; only taking the top of the board earns a colour. */
.ff-practice-recap-delta .chip.top {
    background: rgba(76, 175, 80, .18);
    color: var(--mud-palette-success);
}

.ff-practice-recap-delta .chip.off,
.ff-practice-recap-delta .chip.none {
    background: rgba(158, 158, 158, .16);
    color: var(--mud-palette-text-secondary);
}

/* --- the "no summary came down" state --------------------------------------------------------- */

.ff-practice-recap-missing {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 8px;
    margin-top: 16px;
}

/* --- 600px: the pair sits side by side -------------------------------------------------------- */

@media (min-width: 600px) {
    .ff-practice-recap-row {
        grid-template-columns: 118px minmax(0, 1fr) minmax(0, 1fr);
        gap: 6px 12px;
    }
}

/* --- 960px: and the delta gets its own column ------------------------------------------------- */

@media (min-width: 960px) {
    .ff-practice-recap-row {
        grid-template-columns: 126px minmax(0, 1fr) minmax(0, 1fr) 104px;
    }

    .ff-practice-recap-delta {
        display: block;
    }
}
/* ---- end 34E ---- */

/* ================================================================================================
   Audit 2026-07-29 (finding G8): the member's finished practice drafts, under the setup panel.

   One row per session: date and size on the left, the captured value pair on the right. The whole row
   is the link, because a date and a value pair are both things a thumb will aim at, and it carries a
   44px minimum height so the tap target is honest on a phone.

   THE SHAPE ITSELF MOVED to the practice-polish block at the end of this file, under the
   ff-practice-history-* names it should have had from the start. It shipped calling its rows
   ff-practice-recent-*, which the room's recent-PICKS list had already defined as a rigid four-track
   grid a few hundred lines above; the picks grid won, this row's anchor was laid out inside its 36px
   first track, and the captured value rendered one character per line on every width. Nothing is left
   here on purpose: the two lists must not share a selector again, and an empty block is a clearer
   record of that than a deleted one.
   ================================================================================================ */
/* ---- end audit 2026-07-29 ---- */

/* ================================================================================================
   PRACTICE POLISH (owner walk-through on a real phone, 2026-07-29).

   Appended at the tail so the four practice slices above stay readable as what each of them shipped.
   Four items, and three of them are the same phone.

   THE ROOT CAUSE BEHIND THE DEAD VERTICAL SPACE, because it is worth naming once. Two practice
   containers flip to `flex-direction: column` below 600px while their main child still carries
   `flex: 1 1 200px`, written back when the axis was horizontal. flex-basis is a MAIN-axis size, so the
   flip silently re-reads "200px wide" as "200px tall", and an auto-height column container has no free
   space to redistribute, so the child is laid out at exactly 200px whatever its content measures.
   Measured at 360px: the on-the-clock block rendered 200px tall around ~50px of text (about 150px of
   nothing between the pick counter and the clock line) and the selected-pick body rendered 200px tall
   around ~66px (about another 134px). That is the whole band the owner photographed, and because it is
   fixed geometry rather than anything data-driven it was there with and without picks made. The fix is
   to give the basis back to the content on the axis where a fixed one means nothing.
   ================================================================================================ */

/* --- P3: the dead band, and the rhythm underneath it ------------------------------------------ */

@media (max-width: 599.98px) {
    /* Both halves of the axis-flip above. The 600px-and-up rules keep their 200px basis, which is
       correct there: the axis is horizontal and it is what stops the clock crowding the seat line. */
    .ff-practice-clockhead-who {
        flex: 0 0 auto;
    }

    .ff-practice-rec .ff-draft-rec-body {
        flex: 0 0 auto;
    }

    /* With the false 200px gone, the header's own gap is all that is left between the seat line and the
       countdown, and 8px there is a gap between columns rather than between two lines of one thought. */
    .ff-practice-clockhead {
        gap: 2px;
    }

    /* Same argument inside the selected pick: 14px was the gap between the pick and its button while
       the two sat side by side, and it reads as a hole once they are stacked. */
    .ff-practice-rec {
        gap: 8px;
    }
}

/* --- P4: what the other seats did while you waited -------------------------------------------- */

/* A CHILD of .ff-practice-clockhead, so one element sits in the right place on both layouts: between
   the seat line and the countdown on a phone (where the header is a column, and the order rule below
   puts it there), and on its own full-width row under both from 600px (where it is a row).

   width:100% rather than a percentage flex-basis on purpose. It means the same thing on either axis,
   which is precisely the property the bug above did not have. */
.ff-practice-since {
    order: 0;
    flex: 0 0 auto;
    width: 100%;
    min-width: 0;
    margin-top: 2px;
}

@media (max-width: 599.98px) {
    .ff-practice-clockhead-clock {
        order: 1;
    }
}

.ff-practice-since-lbl {
    font-size: .72rem;
    font-weight: 600;
    line-height: 1.3;
    opacity: .75;
}

/* ONE line, always. The chips scroll sideways as a last resort rather than wrapping, so the strip costs
   the room exactly two lines at 360px and can never push the member's own pick card below the fold,
   which is the one thing it must not do. Same behaviour as the board's filter chips further up. */
.ff-practice-since-chips {
    display: flex;
    flex-wrap: nowrap;
    align-items: center;
    gap: 6px;
    margin-top: 3px;
    min-width: 0;
    max-width: 100%;
    overflow-x: auto;
    -webkit-overflow-scrolling: touch;
    scrollbar-width: none;
    padding-bottom: 1px;
}

.ff-practice-since-chips::-webkit-scrollbar {
    display: none;
}

.ff-practice-since-chip {
    display: inline-flex;
    flex: 0 0 auto;
    align-items: center;
    gap: 5px;
    min-width: 0;
    padding: 2px 8px 2px 6px;
    border-radius: 999px;
    background: var(--mud-palette-background-gray);
    font-size: .7rem;
    line-height: 1.4;
}

.ff-practice-since-chip .st {
    flex: 0 0 auto;
    font-variant-numeric: tabular-nums;
    opacity: .6;
}

/* The shared slot chip at its natural size: .ff-pos was written to fill a fixed grid track, and this is
   a pill. */
.ff-practice-since-chip .ff-pos {
    flex: 0 0 auto;
    width: auto;
    min-width: 24px;
    padding: 1px 5px;
    font-size: .56rem;
    border-radius: 5px;
}

.ff-practice-since-chip .nm {
    flex: 0 1 auto;
    min-width: 0;
    max-width: 16ch;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
    font-weight: 600;
}

.ff-practice-since-more {
    flex: 0 0 auto;
    align-self: center;
    font-size: .68rem;
    font-variant-numeric: tabular-nums;
    opacity: .6;
    white-space: nowrap;
}

/* --- P4, the other half: the list below counts the same story --------------------------------- */

/* The strip says what happened since your last turn; this says how much has happened at all. A member
   who scrolls down to check the strip should find the two agreeing rather than a second, shorter tale. */
.ff-practice-recent-head {
    display: flex;
    align-items: baseline;
    justify-content: space-between;
    gap: 8px;
    margin-bottom: 4px;
}

.ff-practice-recent-total {
    flex: 0 0 auto;
    font-size: .72rem;
    font-variant-numeric: tabular-nums;
    opacity: .65;
    white-space: nowrap;
}

/* --- P1: the finished-sessions list, in its own class family ---------------------------------- */

/* Moved here from the G8 block above, which named these rows ff-practice-recent-* and so handed them to
   the room's recent-PICKS grid: the anchor landed in that grid's 36px first track and "140.8 of 141.1"
   wrapped one character per line, on desktop and phone alike. The picks grid is correct for its own
   component and is untouched.

   Deliberately flex rather than a grid with breakpoints. The date and the size are one group that goes
   to a second line only when it genuinely will not fit, and the value keeps its own width and its place
   at the right on every width, with no media query deciding for it. */
.ff-practice-history-rows {
    display: flex;
    flex-direction: column;
    gap: 6px;
    margin: 8px 0 0;
    padding: 0;
    list-style: none;
}

.ff-practice-history-row {
    min-width: 0;
}

.ff-practice-history-link {
    display: flex;
    align-items: center;
    gap: 4px 12px;
    min-height: 44px;
    padding: 8px 10px;
    border-radius: 8px;
    background: var(--mud-palette-background-gray);
    color: inherit;
    text-decoration: none;
    min-width: 0;
}

.ff-practice-history-link:hover,
.ff-practice-history-link:focus-visible {
    background: var(--mud-palette-action-default-hover);
}

.ff-practice-history-meta {
    display: flex;
    flex: 1 1 auto;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 1px 10px;
    min-width: 0;
}

.ff-practice-history-meta .wh {
    font-weight: 600;
    white-space: nowrap;
}

.ff-practice-history-meta .wt {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
    font-size: .72rem;
    opacity: .65;
}

/* The one hard rule of this row: the captured value and the total it is measured against are a single
   number, and it does not break on any width. */
.ff-practice-history-link .vl {
    flex: 0 0 auto;
    margin-left: auto;
    font-size: .8rem;
    font-variant-numeric: tabular-nums;
    white-space: nowrap;
    opacity: .85;
}

/* --- P2: both ways onward at 360px (CORRECTED, owner testing round 2026-07-29) ----------------- */

/* THIS BLOCK PREVIOUSLY TRIED TO HOLD THE TWO ACTIONS ON ONE ROW AND COULD NOT. Kept as a correction
   in place rather than as a fresh override, because the reasoning is what was wrong, not the selector.

   The measurement that justified the compact chrome ("115px + 8px + 160px = 283px") was wrong by about
   139px: it counted the label text only. Re-measured in a browser at a true 360px viewport, against the
   real MudBlazor 8 button rules and the app's own Roboto:

     content box of the card         294px   (360 - 32 pa-4 - 2 card border - 32 card-content padding)
     "Practice again"                172.6px
     "Back to the draft room"        241.8px
     + the 8px gap                   422.4px total, i.e. 128px MORE than there is

   The omissions were MudBlazor's own button typography (text-transform: uppercase and the .02857em
   letter-spacing both come from --mud-typography-button-*, so the label is measured in caps, not in
   the sentence case the markup is written in) and the start-icon box (.mud-button-icon-start is a 16.8px
   glyph plus 8px margin-inline-end less 4px margin-inline-start, so 20.8px a button).

   AND THE COMPACT SIZING COULD NEVER HAVE WORKED ANYWAY, whatever the numbers were. The container is
   flex-wrap: wrap, and flexbox assigns items to lines from their HYPOTHETICAL main sizes before any
   flex-shrink is resolved (CSS Flexbox 9.3 line breaking, then 9.7 per line). So flex: 0 1 auto shrinks
   an item only against the other items that landed on its own line: once the pair is too wide it is
   already on two lines, and every item is then alone on a line with nothing to shrink against. That is
   exactly what shipped, and it is what the owner kept photographing: not the <340px stack rule (which
   does not match at 360px) but a WRAP, rendering two ragged left-aligned rows of unequal width (145.8px
   and 207.7px) in shrunken .78rem type.

   The decisive number: the wrap already cost 96px of height. A deliberate stack costs 96px too. The
   compact chrome bought exactly zero vertical space; it only made the two rows look accidental and the
   labels and tap targets smaller. So the honest fix is to stop pretending and stack them properly,
   full width and at the sizing every other button in the app has. It is also robust in the way the old
   rule was not: it holds at 320px, at any label length, and under any font fallback.

   (One row is not reachable at 360px by any means worth having. Even stripping BOTH icons AND the
   uppercase AND cutting the padding to 8px measures 273px, leaving 21px of slack on the exact current
   strings, and it costs the buttons their icons and the house Material look to get there. Shortening
   the secondary label does not rescue it either: "Live draft", at ten characters, still measures 314.6px
   against the 294px box. Two icon-bearing Material buttons simply do not fit a 294px row.)

   This supersedes the <340px column rule in the 34C block above, which is now merely a narrower case of
   the same thing and is left in place as-is. */
@media (max-width: 599.98px) {
    .ff-practice-complete-actions {
        flex-direction: column;
        align-items: stretch;
    }

    /* No shrink and no squeeze: each button owns the full 294px row, keeps the app's standard button
       type and padding, and clears the 44px thumb target on its own. */
    .ff-practice-complete-actions .mud-button-root {
        flex: 0 0 auto;
        min-height: 44px;
    }
}
/* ---- end practice polish ---- */

/* ================================================================================================
   ROUND FIXES: PRACTICE ROOM (owner testing round on the prod-restored dev database, 2026-07-29).

   Appended at the tail so the polish block above still reads as what that round shipped. Three items
   here (the fourth, the completion actions, is a correction inside the block above because it is that
   block's own reasoning that was wrong). Every number quoted below was measured in a browser at a real
   360px viewport against the app's own Roboto and the real MudBlazor 8.15 rules, not estimated.
   ================================================================================================ */

/* --- A1: the since-picks chip is anchored on the overall pick number --------------------------- */

/* Leading and the only bold thing in the chip. The seat beside it keeps the dimmed .st treatment it
   already had, so the pair reads as "#23" first and "which seat" second at a glance, which is the order
   the questions actually arrive in. Tabular figures so a scrolling run of chips does not jitter. */
.ff-practice-since-chip .pk {
    flex: 0 0 auto;
    font-weight: 700;
    font-variant-numeric: tabular-nums;
}

/* The chip now carries four things instead of three, and it lives on a line that scrolls rather than
   wraps, so the two number tokens give some of their room back to the name. */
.ff-practice-since-chip {
    gap: 4px;
}

/* --- A2: the auto-pick alert, as small as it can honestly be at 360px -------------------------- */

/* TWO LINES, AND IT TOOK BOTH A TRIM AND A REWRITE. Measured as shipped at 360px the alert was FOUR
   text lines and 102px tall: the MudAlert gives the message a 228px box (294px card, less 16px+16px
   alert padding, less a 22px icon and its 12px margin), and BOTH sentences overflowed it.

   The width this block recovers is 46px, all of it: 34px of icon gutter plus 6px a side of alert
   padding, taking the message box to 274px. That was enough for the second sentence (measured: 4 of 5
   sample "We took X for your Y slot." lines now hold one line, against 1 of 5 at 228px) and nowhere
   near enough for the first, which read "Your practice pick clock ran out, so we picked for you." and
   needed 388px. No trim reaches 388px, and shrinking type to close a 114px gap would land near 11px on
   the one alert in the app that exists to be read by somebody who was looking away.

   So the sentence itself was shortened, in PracticeDraftService.ClockRanOutMessage and its identical
   client fallback in PracticeRoomPanel: "Your practice clock ran out." at 197.7px, which is one line in
   the 274px box at 360px and still one line in the 234px box at 320px. The clause that went is the one
   the second line already states concretely, so the alert lost redundancy rather than information.
   Result: 102px and four lines become 60px and two.

   The icon is the biggest single lever (34px of the 46px) and the one worth spending: the warning
   severity band and the bold first sentence both still say "something happened while you were away".
   Scoped to .ff-practice-autopick so the room's other alerts keep the stock chrome. */
@media (max-width: 599.98px) {
    .ff-practice-autopick {
        padding-left: 10px;
        padding-right: 10px;
    }

    .ff-practice-autopick .mud-alert-icon {
        display: none;
    }

    .ff-practice-autopick .mud-alert-message {
        padding-top: 4px;
        padding-bottom: 4px;
    }

    /* Two sentences of one thought, so they sit closer than the stock 1.5 leading puts them. */
    .ff-practice-autopick .ff-practice-autopick-head {
        line-height: 1.28;
    }

    .ff-practice-autopick .ff-practice-autopick-detail {
        line-height: 1.35;
    }
}

/* --- A3: the whole pick history, on request ---------------------------------------------------- */

/* Expanded, the list defeats the phone trim (the 34C rule hides every row past the third below 600px)
   and becomes a bounded scroll region instead. 260px is about six rows on a phone and seven on a
   desktop: enough that the reveal obviously revealed something, capped so a 40-pick draft cannot push
   the board and the abandon control off the bottom of the room. */
.ff-practice-recent-list.all {
    max-height: 260px;
    overflow-y: auto;
    -webkit-overflow-scrolling: touch;
}

@media (max-width: 599.98px) {
    .ff-practice-recent-list.all .ff-practice-recent-row:nth-child(n+4) {
        display: grid;
    }
}

.ff-practice-recent-more {
    display: flex;
    justify-content: center;
    margin-top: 2px;
}

/* The session is short enough that only the phone trim is hiding anything, so the control is real on a
   phone and would be a button that does nothing from 600px up. */
@media (min-width: 600px) {
    .ff-practice-recent-more.phone-only {
        display: none;
    }
}
/* ---- end round fixes: practice room ---- */

/* ================================================================================================
   TESTING ROUND 2026-07-29, SLICE B - the live room and the recap surfaces.

   Appended at the tail in its own block, so the slices above stay readable as what each of them
   shipped and a parallel slice's block can land beside this one without a merge conflict.

   Four items: the Buzz grid gains a fifth card, the on-the-clock banner gains a pick counter, the room
   gains a recent-picks strip, and the dashboard gains a draft-grade teaser. Every selector here is new;
   nothing above is redefined. (The 2026-07-29 audit note a few hundred lines up is the reason for the
   ff-room-* prefix on the strip: the practice room's ff-practice-recent-* grid is a rigid four-track
   layout, and the two lists must never share a selector again.)
   ================================================================================================ */

/* ---- B1: League Buzz gains the draft-recap card ------------------------------------------------
   The base .ff-buzz-cols grid is 3-across from 961px. A fourth or fifth card would strand a lone card
   on a second row, so a week carrying an extra card drops the grid to a clean two columns, exactly as
   the Pool Spotlight modifier already does. The modifier only lands when the card is actually present,
   so a deploy with Features:PostDraftRecapEnabled dark keeps today's exact three-across layout. Mobile
   is untouched: .ff-cols already stacks to one column at 960px and below. */
@media (min-width: 961px) {
    .ff-buzz-cols.has-draft-recap { grid-template-columns: 1fr 1fr; }
}

/* ---- B3a: the on-the-clock banner's pick counter -----------------------------------------------
   The counter is a caption UNDER the name rather than a parenthetical after it, because at 360px the
   old "(Pick #2)" pushed a long display name onto a second line inside an h6. min-width:0 is what lets
   the name ellipsize inside the flex row instead of forcing the alert wider than the card. */
.ff-draft-onclock {
    min-width: 0;
    display: flex;
    flex-direction: column;
    gap: 2px;
}

/* ---- B3b: the room's recent-picks strip --------------------------------------------------------
   Four tracks: slot chip, name, school, owner. The name is the only elastic one, so a long school or a
   long display name can never squeeze it out of the row. */
.ff-room-recent {
    margin: 0 0 16px;
}

.ff-room-recent-head {
    display: flex;
    align-items: baseline;
    justify-content: space-between;
    gap: 8px;
    margin-bottom: 2px;
}

.ff-room-recent-total {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    white-space: nowrap;
    font-variant-numeric: tabular-nums;
}

.ff-room-recent-list {
    display: flex;
    flex-direction: column;
}

.ff-room-recent-row {
    display: grid;
    align-items: center;
    gap: 8px;
    grid-template-columns: 48px minmax(0, 1fr) minmax(0, .7fr) minmax(0, .7fr);
    padding: 4px 2px;
    font-size: .82rem;
    border-bottom: 1px solid var(--mud-palette-lines-default);
}

.ff-room-recent-row:last-child {
    border-bottom: none;
}

.ff-room-recent-name {
    font-weight: 600;
}

.ff-room-recent-team,
.ff-room-recent-by {
    color: var(--mud-palette-text-secondary);
}

.ff-room-recent-name,
.ff-room-recent-team,
.ff-room-recent-by {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

/* 360px: the school goes rather than the owner. WHO took it is the point of the strip (a run is made of
   who is taking what), and the school is already on every board row below it. The trim is CSS, so the
   markup is identical at every width.

   The row-count trim that used to live here (nth-child(n+4), display:none) is gone: BH-2 scrolls the
   complete history inside the same three-row visible height instead of deleting rows four onward, so
   the picks the strip counts are the picks a phone can actually reach. See the BH-2 tail block. */
@media (max-width: 599.98px) {
    .ff-room-recent-row {
        grid-template-columns: 42px minmax(0, 1fr) minmax(0, .8fr);
        font-size: .78rem;
    }

    .ff-room-recent-team {
        display: none;
    }
}

/* ---- B5: the dashboard's draft-grade teaser ----------------------------------------------------
   The letter and the capture line sit on one row from 600px and stack at 360px, where a 56px badge
   plus a full sentence does not fit beside itself. The sentence carries its own denominator, which is
   the one rule every grade surface keeps. */
.ff-home-grade {
    display: flex;
    align-items: center;
    gap: 12px;
    flex-wrap: wrap;
}

.ff-home-grade-line {
    min-width: 0;
    flex: 1 1 220px;
    font-size: .9rem;
    font-weight: 600;
    line-height: 1.35;
}
/* ---- end testing round slice B ---- */

/* ================================================================================================
   New-league polish (2026-07-29): the post-activation league page at /leagues/{id}
   ------------------------------------------------------------------------------------------------
   The "Get your league rolling" panel is the first screen a PAYING commissioner sees after checkout,
   so it is styled as a designed step sequence: numbered markers threaded on a connecting rail, a
   primary-tinted card that reads as a moment rather than another outlined tile, and three FILLED
   action buttons whose hierarchy comes from colour (one primary, two neutral) instead of from mixing
   variants.

   WHY THIS LIVES IN app.css AND NOT IN A SCOPED CommissionerChecklist.razor.css: Blazor CSS isolation
   only stamps its b-<hash> scope attribute on plain HTML elements written in the .razor file. Child
   COMPONENTS do not receive it, so a scoped rule can never reach the element MudCard, MudText or
   MudButton renders. The component previously carried a scoped file in which every rule aimed at a Mud
   component (the card margin, the 44px CTA tap target, the marker, the done-state title) silently did
   nothing. That file was deleted and its intent rebuilt here, where the selectors actually match.
   app.css is the last stylesheet loaded (after MudBlazor.min.css and the scoped bundle), so these
   equal-specificity rules win on cascade order without needing !important.
   ================================================================================================ */

.ff-checklist {
    /* The hero above contributes its own 22px bottom margin, so only the gap DOWN to the Roster /
       Season cards is set: a little wider than the 16px grid gutter, so the onboarding panel reads as
       its own moment instead of merging into the rhythm of the standing info cards. */
    margin: 0 0 24px;
    border-color: var(--mud-palette-primary);
    /* Fades out above the buttons, so the card is tinted at the top without washing the CTAs. */
    background-image: linear-gradient(180deg,
        rgba(var(--mud-palette-primary-rgb), .08),
        rgba(var(--mud-palette-primary-rgb), 0) 190px);
}

.ff-checklist-head {
    display: flex;
    flex-direction: column;
    gap: 2px;
    margin-bottom: 20px;
}

.ff-checklist-eyebrow {
    color: var(--mud-palette-primary);
    font-weight: 700;
    letter-spacing: .09em;
}

.ff-checklist-title {
    font-weight: 700;
    letter-spacing: -.01em;
}

.ff-checklist-lede {
    color: var(--mud-palette-text-secondary);
    max-width: 52ch;
}

.ff-checklist-steps {
    list-style: none;
    margin: 0;
    padding: 0;
    display: flex;
    flex-direction: column;
    gap: 22px;
}

.ff-checklist-step {
    position: relative;
    display: flex;
    align-items: flex-start;
    gap: 14px;
}

/* The rail that turns three rows into one sequence. It runs from just below a marker to the top of
   the next one, so it never pokes out past the final step. */
.ff-checklist-step:not(:last-child)::before {
    content: "";
    position: absolute;
    left: 14px;
    top: 34px;
    bottom: -26px;
    width: 2px;
    border-radius: 1px;
    background: var(--mud-palette-lines-default);
}

.ff-checklist-mark {
    position: relative;
    z-index: 1;
    flex: 0 0 auto;
    width: 30px;
    height: 30px;
    box-sizing: border-box;
    border-radius: 50%;
    display: inline-flex;
    align-items: center;
    justify-content: center;
    border: 2px solid var(--mud-palette-primary);
    /* Opaque, so the rail passes behind the marker rather than through it. */
    background: var(--mud-palette-surface);
    color: var(--mud-palette-primary);
    font-size: .88rem;
    font-weight: 700;
    line-height: 1;
}

/* "Members joined" is the only step that can prove its own completion, so it is the only marker that
   swaps its number for a check. Steps that have no completion signal keep their number rather than
   showing a checkbox that never ticks. */
.ff-checklist-step.done .ff-checklist-mark {
    background: var(--mud-palette-success);
    border-color: var(--mud-palette-success);
    color: #fff;
}

.ff-checklist-body {
    display: flex;
    flex-direction: column;
    align-items: flex-start;
    gap: 3px;
    min-width: 0;
    /* Optically centres the title against the 30px marker. */
    padding-top: 2px;
}

.ff-checklist-step-title {
    font-weight: 600;
    line-height: 1.3;
}

.ff-checklist-step-sub {
    color: var(--mud-palette-text-secondary);
    max-width: 52ch;
}

.ff-checklist-step.done .ff-checklist-step-title {
    opacity: .85;
}

.ff-checklist-cta {
    align-self: flex-start;
    margin-top: 9px;
    min-height: 44px;
    box-shadow: none;
}

.ff-checklist-cta:hover {
    box-shadow: none;
}

/* Steps 2 and 3 stay FILLED (the ask was buttons, not links) and drop one level of emphasis through
   colour alone. MudBlazor's default-coloured filled button is already a neutral tonal fill; the border
   is what keeps it reading as a deliberate button against the tinted card, in both themes. */
.ff-checklist-cta-quiet {
    border: 1px solid var(--mud-palette-lines-default);
}

/* 360px: each step ends in one confident full-width thumb target, and the marker column tightens to
   buy back horizontal room for the copy. */
@media (max-width: 599.98px) {
    .ff-checklist-steps { gap: 20px; }
    .ff-checklist-step { gap: 12px; }

    .ff-checklist-cta {
        align-self: stretch;
        width: 100%;
    }
}

/* ---- the open invite code, below the panel ----
   The code is 16 characters (Guid "N" slice). Measured at 360px: at Typo.h5 with .14em tracking it
   renders 264px wide inside the 295px of content width a phone actually has after MudContainer and
   MudCard padding. It fits, barely, at 90% of the row: COPY is squeezed off to its own line anyway and
   the code crowds both card edges. Below 600px the code steps down to ~168px, is allowed to wrap
   rather than overflow if a future code is longer, and COPY takes a deliberate full-width 44px row
   instead of an accidental one. */
@media (max-width: 599.98px) {
    .ff-invite-row2 { gap: 10px; }

    .ff-invite-card .ff-invite-code {
        font-size: 1.05rem;
        letter-spacing: .08em;
        overflow-wrap: anywhere;
        min-width: 0;
    }

    .ff-invite-card .ff-invite-row2 .mud-button-root {
        width: 100%;
        min-height: 44px;
    }
}
/* ---- end new-league polish ---- */

/* ================================================================================================
   ConfirmDangerDialog: the one destructive-action confirmation
   ------------------------------------------------------------------------------------------------
   Appended as its own block so parallel slices merge cleanly. Every selector here keys off a class
   the component renders itself, never MudBlazor's .mud-dialog-* internals: the dialog is hosted
   through MudDialogProvider, so styling its host's classes would be betting on where MudBlazor
   chooses to put them.

   Supersedes the 34D .ff-practice-abandon-dialog rule further up this file. That rule is now dead
   (MockDraft confirms through this component instead and no longer emits the class); it is left in
   place rather than deleted from the middle of the file so concurrent branches do not conflict.
   ================================================================================================ */

/* The warning icon and the title read as one line, and the icon never shrinks the title's measure. */
.ff-danger-dialog-head {
    display: flex;
    align-items: center;
    gap: 10px;
}

.ff-danger-dialog-head .mud-icon-root {
    flex: 0 0 auto;
}

/* The question is the loud part; the consequence is a quieter second line under it rather than a
   run-on sentence, so "what am I about to do" and "what else goes with it" are separately scannable. */
.ff-danger-dialog-consequence {
    display: block;
    margin-top: 8px;
    opacity: .85;
}

/* Desktop: Cancel left, the destructive button right, both at the trailing edge. The wrapper carries
   the layout (not .mud-dialog-actions) and spans the row so the phone rules below have something to
   stretch against. */
.ff-danger-dialog-actions {
    display: flex;
    align-items: center;
    justify-content: flex-end;
    gap: 8px;
    width: 100%;
}

/* 360px: one full-width button per row, and NOT reversed. DOM order is Cancel then Confirm, so a
   plain column leaves the destructive button bottom-most, furthest from where a thumb already sits
   after tapping whatever opened this. 44px keeps both of them real touch targets. */
@media (max-width: 599.98px) {
    .ff-danger-dialog-actions {
        flex-direction: column;
        align-items: stretch;
        gap: 8px;
    }

    .ff-danger-dialog-actions .mud-button-root {
        width: 100%;
        margin: 0;
        min-height: 44px;
    }
}
/* ---- end ConfirmDangerDialog ---- */

/* ---- PD-20 (2026-07-30): league hero action row at phone width ----
   At a 360px viewport the action row measures 260px (360 minus the pa-4 shell, the MudContainer
   gutters, and the hero's own 18px phone padding). The rule at line 788 gives all three buttons
   flex:1, so they split into 81.3px thirds, which leaves a ~49px label box. "MEMBERS" and
   "SETTINGS" are single words and simply overflow it, but "ENTER LEAGUE" has a space to break on,
   so its label wraps to two lines and that one button renders 61px tall against its neighbours'
   36.5px. nowrap on its own would only convert the wrap into an overflow. So the two outlined
   controls keep the shared row (126px each), and the primary action takes a full-width row of its
   own (260px), which is also the prominence it should have. All three then measure 36.5px tall and
   nothing overflows. Enter League is already last in source order in LeagueOverview.razor, so a
   100% flex-basis wraps it down with no markup reordering.
   Specificity: the .mud-button-root rule ties with the line-788 rule at (0,3,0) and wins on source
   order; the .ff-league-enter rule is a compound (0,4,0) and wins outright, so neither depends on
   the order of the two lines inside this block. Every selector is prefixed .ff-league-hero, so the
   non-hero .ff-league-actions uses (line 609) are untouched. Plain members render one button, where
   the block is a no-op that still yields a full-width primary. */
@media (max-width: 599.98px) {
    .ff-league-hero .ff-league-actions {
        flex-wrap: wrap;
    }

    .ff-league-hero .ff-league-actions .mud-button-root {
        flex: 1 1 0;
        white-space: nowrap;
    }

    .ff-league-hero .ff-league-actions .mud-button-root.ff-league-enter {
        flex: 1 0 100%;
    }
}
/* ---- end PD-20 league hero action row ---- */

/* =========================================================================================   36B: the practice reveal
   ------------------------------------------------------------------------------------------------
   Appended as its own block at the tail so parallel slices merge cleanly (36C appends below this
   one). Everything here is scoped to a class PracticeRoomPanel / PracticeSincePicks renders itself,
   so nothing in it can reach the live draft room, which reuses PickClock and the ff-draft-* row
   furniture unmodified.

   Three things, and only three: the seat that is about to pick, the chip that lands when it does,
   and the control that ends the show. There is deliberately NO spinner and no progress bar (Q11):
   the pick is already made and stored server-side, so a loading indicator would be a lie. The seat
   name plus a chip that appears is the same information without the false claim, and it survives
   reduced motion and a screen reader, neither of which a spinner does.
   ================================================================================================ */

/* The seat on the clock while the room is still catching up. The INFO accent, because that is
   practice's whole visual identity in this app (the banner and the room card's 2px left border are
   both info), and because the one thing this surface must never do is borrow the live product's
   primary orange. A colour change only: the sentence itself already says who is picking, so a member
   with a monochrome display or a screen reader loses nothing. */
.ff-practice-pending {
    color: var(--mud-palette-info);
}

/* One beat, one chip. The strip renders newest-first and the chips are keyed on the pick number, so
   the arriving element is genuinely new and genuinely at the head of the line; a short slide in from
   the right is then the whole animation, and it reads as "this just happened" rather than as motion
   for its own sake. */
.ff-practice-since-chip {
    animation: ff-practice-chip-in 220ms ease-out both;
}

@keyframes ff-practice-chip-in {
    from {
        opacity: 0;
        transform: translateX(8px);
    }

    to {
        opacity: 1;
        transform: none;
    }
}

/* Reduced motion: the chips simply appear. The reveal's information is the text, not the movement,
   so removing the movement removes nothing. */
@media (prefers-reduced-motion: reduce) {
    .ff-practice-since-chip {
        animation: none;
    }
}

/* "Skip to my pick" stands in for the draft button until the reveal ends, in its own row rather than
   inside the recommendation card, so it exists in the states that card does not render. Trailing edge
   from 600px, where the draft button also sits at the right of the card. */
.ff-practice-skiprow {
    display: flex;
    align-items: center;
    justify-content: flex-end;
}

.ff-practice-skiprow .mud-button-root {
    min-height: 44px;
}

/* 360px: full width and a real 44px touch target, matching the draft button it replaces (the
   .ff-practice-rec phone rule further up this file does the same for that one). */
@media (max-width: 599.98px) {
    .ff-practice-skiprow {
        align-items: stretch;
    }

    .ff-practice-skiprow .mud-button-root {
        width: 100%;
        margin: 0;
    }
}
/* ---- end 36B ---- */

/* ---- 36C: practice setup ---- */
/* ================================================================================================
   Phase 36C (PD-6): the practice setup surface reads as an invitation rather than a settings form.

   Appended as one clearly-commented block at the tail so the parallel 36B slice (the reveal in the
   room) merges cleanly beside it; neither block names a selector the other owns.

   Three rules run through everything here:
     - The accent is INFO, never the app's primary orange. .ff-league-hero owns the orange gradient
       and it is the loudest "this is your real league" signal in the product; practice must never be
       mistakable for the live room (34C section 5.8), so the hero borrows that structure and none of
       its palette.
     - No horizontal PAGE scroll at 360px. The three chip rows scroll inside themselves, which is what
       lets the twelve-seat "your seat" row show its whole decision space without wrapping.
     - Every tap target is at least 44px.

   The 34C .ff-practice-setup-grid rules further up this file are now dead (the four MudSelects they
   laid out are gone). They are left in place rather than deleted from the middle of the file, the same
   way the 34D abandon-dialog rule was, so a concurrent branch does not have to resolve a conflict in a
   region neither slice is really editing. .ff-practice-setup-hint and .ff-practice-setup-actions are
   still live and still used.
   ================================================================================================ */

/* --- the hero: replaces the page head in the setup state only --------------------------------- */

.ff-practice-hero {
    border-radius: 16px;
    padding: 22px 24px;
    color: #fff;
    background: linear-gradient(135deg, var(--mud-palette-info), var(--mud-palette-info-darken, #1976D2));
}

/* The gradient runs the full width like every other hero; only the TEXT is capped, so it lines up with
   the 640px column the setup card's own contents take at desktop widths. */
.ff-practice-hero-inner {
    min-width: 0;
}

.ff-practice-hero-eyebrow {
    display: block;
    font-size: .72rem;
    font-weight: 700;
    letter-spacing: .08em;
    text-transform: uppercase;
    color: rgba(255, 255, 255, .85);
}

.ff-practice-hero-title {
    margin: 4px 0 0;
    font-size: 1.7rem;
    font-weight: 700;
    line-height: 1.15;
    letter-spacing: -.01em;
    color: #fff;
}

.ff-practice-hero-sell {
    margin: 8px 0 0;
    max-width: 52ch;
    font-size: .95rem;
    color: rgba(255, 255, 255, .9);
}

/* The hook and its link sit on one row and wrap to two on a narrow phone, rather than the link being
   dragged onto a line of its own by a number that happens to be long. */
.ff-practice-hero-hook {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 2px 12px;
    margin: 14px 0 0;
    font-size: .95rem;
}

.ff-practice-hero-hook .vl {
    font-weight: 700;
    font-variant-numeric: tabular-nums;
}

.ff-practice-hero-link {
    display: inline-flex;
    align-items: center;
    min-height: 44px;
    color: #fff;
    font-weight: 600;
    text-decoration: underline;
}

@media (max-width: 599.98px) {
    .ff-practice-hero {
        padding: 18px;
    }

    .ff-practice-hero-title {
        font-size: 1.45rem;
    }
}

@media (min-width: 960px) {
    .ff-practice-hero-inner {
        max-width: 640px;
        margin: 0 auto;
    }
}

/* --- the four choices ------------------------------------------------------------------------- */

.ff-practice-choices {
    display: flex;
    flex-direction: column;
    gap: 14px;
}

.ff-practice-choice {
    min-width: 0;
}

.ff-practice-choice-label {
    display: block;
    margin-bottom: 6px;
    font-size: .72rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

/* The board's own filter-row behaviour (.ff-practice-filters), reused for a decision rather than a
   filter: one line, never wrapping, scrolling horizontally as a last resort. Twelve seats is thirteen
   chips, and a wrap there would push the card taller than the viewport on a phone. */
.ff-practice-chiprow {
    display: flex;
    flex-wrap: nowrap;
    gap: 6px;
    min-width: 0;
    max-width: 100%;
    overflow-x: auto;
    -webkit-overflow-scrolling: touch;
    scrollbar-width: none;
    padding-bottom: 2px;
}

.ff-practice-chiprow::-webkit-scrollbar {
    display: none;
}

.ff-practice-chiprow .mud-button-root {
    flex: 0 0 auto;
    min-width: 44px;
    min-height: 44px;
    padding: 4px 12px;
    white-space: nowrap;
}

/* The pool is the one choice that changes what you are practising, so it is the one that gets words.
   Stacked full width on a phone, two columns from 600px. */
.ff-practice-pool {
    display: grid;
    grid-template-columns: 1fr;
    gap: 10px;
}

.ff-practice-pooltile {
    display: flex;
    flex-direction: column;
    gap: 4px;
    width: 100%;
    min-height: 44px;
    padding: 12px 14px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 10px;
    background: var(--mud-palette-background-gray);
    color: inherit;
    font: inherit;
    text-align: left;
    cursor: pointer;
}

.ff-practice-pooltile:hover:not(:disabled),
.ff-practice-pooltile:focus-visible {
    border-color: var(--mud-palette-info);
}

/* Selected is the info accent again, and the padding compensates for the thicker border so choosing a
   tile cannot shift the one beside it. */
.ff-practice-pooltile.sel {
    border: 2px solid var(--mud-palette-info);
    padding: 11px 13px;
    background: rgba(33, 150, 243, .12);
}

.ff-practice-pooltile:disabled {
    opacity: .6;
    cursor: default;
}

.ff-practice-pooltile .t {
    font-weight: 700;
    font-size: .95rem;
}

.ff-practice-pooltile .d {
    font-size: .78rem;
    opacity: .75;
}

@media (min-width: 600px) {
    .ff-practice-pool {
        grid-template-columns: repeat(2, minmax(0, 1fr));
    }
}

/* --- what a practice rep gives you ------------------------------------------------------------ */

.ff-practice-rep-strip {
    display: grid;
    grid-template-columns: 1fr;
    gap: 10px;
    margin: 10px 0 0;
    padding: 0;
    list-style: none;
}

.ff-practice-rep-strip li {
    display: flex;
    align-items: flex-start;
    gap: 8px;
    min-width: 0;
    font-size: .85rem;
}

.ff-practice-rep-strip .mud-icon-root {
    flex: 0 0 auto;
    color: var(--mud-palette-info);
}

@media (min-width: 600px) {
    .ff-practice-rep-strip {
        grid-template-columns: repeat(3, minmax(0, 1fr));
    }
}

/* Desktop: the choices and the rep strip take the same 640px column the setup grid always did, so the
   card contents stay one measure instead of three. */
@media (min-width: 960px) {
    .ff-practice-choices,
    .ff-practice-rep-strip {
        max-width: 640px;
        margin-left: auto;
        margin-right: auto;
    }
}

/* --- the history rows lead with the number ---------------------------------------------------- */

/* Overrides the P1 rules above rather than replacing them: the row is still a flex anchor whose value
   pair sits outside the wrapping meta group and never breaks. What changed is which of the two reads
   first, and at what size. On a phone the pair takes its own line above the meta; from 600px it goes
   back to the right-hand end of a single row, where it has always been. */
.ff-practice-history-link {
    flex-direction: column;
    align-items: stretch;
    gap: 2px;
}

.ff-practice-history-link .vl {
    margin-left: 0;
    font-size: 1.05rem;
    font-weight: 700;
    opacity: 1;
}

/* The date stops being the loud part of the row. */
.ff-practice-history-meta .wh {
    font-weight: 400;
    font-size: .72rem;
    opacity: .65;
}

@media (min-width: 600px) {
    .ff-practice-history-link {
        flex-direction: row;
        align-items: center;
        gap: 4px 12px;
    }

    .ff-practice-history-meta {
        order: 1;
    }

    .ff-practice-history-link .vl {
        order: 2;
        margin-left: auto;
    }
}
/* ---- end 36C ---- */
/* ============================================================
   Phase 35C: Draft Order provenance banner + rollover bar.
   Appended block, added 2026-07-30. Two surfaces on
   /commissioner/draft-order:

   1. The provenance banner (.ff-do-prov) inside a MudAlert. On a
      desktop the sentence and Undo share a row; at 360px Undo
      drops to its own full-width 44px line so the fact and the
      action never compete for the same thumb.
   2. The sticky bar, which lost "Clear all queues" (PD-10) and
      gained "Set from last week's finish". Desktop keeps all
      three controls on one row with the finish button trailing;
      at 360px randomize + save share a row and the finish button
      takes a full-width row of its own. The caption is always a
      full-width line under both, so the reason a disabled button
      is disabled sits directly beneath it.
   ============================================================ */
.ff-do-prov {
    display: flex;
    align-items: center;
    flex-wrap: wrap;
    gap: 8px;
    width: 100%;
}

.ff-do-prov-text {
    flex: 1 1 240px;
    min-width: 0;
}

.ff-do-prov-undo {
    flex: 0 0 auto;
}

.ff-do-bar-main {
    display: flex;
    align-items: center;
    flex-wrap: wrap;
    gap: 8px;
}

/* Trailing edge on a desktop, which is where the old clear-queues button sat, so the muscle memory for
   "the occasional action lives at the far end of this bar" is unchanged. */
.ff-do-bar-finish {
    margin-left: auto;
}

.ff-do-bar-hint {
    flex-basis: 100%;
    min-width: 0;
}

@media (max-width: 599.98px) {
    .ff-do-prov-undo {
        flex: 1 1 100%;
    }

    .ff-do-prov-undo .mud-button-root {
        width: 100%;
        min-height: 44px;
    }

    .ff-do-bar-main {
        flex: 1 1 100%;
    }

    .ff-do-bar-main .mud-button-root {
        flex: 1 1 0;
        min-width: 0;
        min-height: 44px;
    }

    .ff-do-bar-finish {
        flex: 1 1 100%;
        margin-left: 0;
    }

    .ff-do-bar-finish .mud-button-root {
        width: 100%;
        min-height: 44px;
    }
}
/* ---- end Phase 35C draft order provenance ---- */
/* ============================================================================================
   Phase 35D/35E - the winner's conference pick (/draft/conferences)
   Appended as one commented tail block, per the phase's CSS convention. The page reuses
   .ff-conf-chips from the commissioner's picker on purpose: two surfaces that lay the same
   conference list out differently would read as two different lists.
   ============================================================================================ */

/* 360px is the width members actually draft at, so the chips are sized as real touch targets
   first and allowed to grow, rather than shrunk to fit. Two per row at the narrowest width. */
.ff-conf-pick-chips .mud-chip {
    min-height: 44px;
    margin: 0;
}

/* The submit column. Full width and stacked at every width below tablet: the feasibility line
   above it is the thing a member reads last before committing, so nothing shares its row. */
.ff-conf-pick-actions {
    display: flex;
    flex-direction: column;
    align-items: stretch;
    gap: 8px;
}

.ff-conf-pick-actions .mud-button-root {
    min-height: 44px;
    margin: 0;
}

/* The matchup list is the one long payload here. It scrolls inside its own container so the
   page body never scrolls sideways, whatever a conference decides to name its teams. */
.ff-conf-pick-matchups {
    max-width: 100%;
    overflow-x: auto;
    overflow-wrap: anywhere;
}

/* Tablet and up: the submit button stops being a full-width slab and sits at the trailing edge,
   which is where every other confirm control in the app already is. */
@media (min-width: 600px) {
    .ff-conf-pick-actions {
        flex-direction: row-reverse;
        justify-content: flex-start;
        align-items: center;
    }

    .ff-conf-pick-actions .mud-button-root {
        width: auto;
        flex: 0 0 auto;
    }
}
/* ---- end conference pick ---- */

/* ============================================================================================
   Phase 35E - the Home card and the commissioner note for the winner's conference pick
   Appended as one commented tail block, per the phase's CSS convention. The card is a MudAlert,
   so nearly all of its layout is already correct; what is NOT correct by default at 360px is
   the call to action, which MudBlazor renders at its natural width and at a height below the
   44px the rest of this app treats as the minimum touch target.
   ============================================================================================ */

/* The one control on the card is the way into the picker, and the card only ever renders while a
   deadline is running, so it is sized as a real target first: full width on a phone, natural width
   from tablet up where it sits inline like every other card action. */
.ff-conf-pick-card .mud-button-root {
    min-height: 44px;
}

@media (max-width: 599.98px) {
    .ff-conf-pick-card .mud-button-root {
        width: 100%;
        margin: 0;
    }
}

/* The commissioner note under a schedule week's conference value. Caption size, muted, and allowed
   to wrap anywhere, so a long member name cannot push the schedule table sideways at 360px. */
.ff-sched-pick-note {
    font-size: 0.75rem;
    line-height: 1.4;
    opacity: 0.75;
    overflow-wrap: anywhere;
}
/* ---- end 35E ---- */

/* ============================================================================================
   League subpage polish (2026-07-30) - Members & Invites and League Settings page headers
   --------------------------------------------------------------------------------------------
   Appended as one commented tail block, per convention. Both pages open with the same compact
   brand-gradient band, borrowing .ff-league-hero's language (16px radius, primary gradient,
   white text, white outlined back action) without its class: the hero's phone rules are tuned
   for LeagueOverview's three-button action row (PD-20), which these pages do not have. The
   member pages render ONE back control, so the phone rule here is simply "full width, 44px". */
.ff-subpage-head {
    border-radius: 16px;
    padding: 20px 22px;
    margin-bottom: 20px;
    color: #fff;
    background:
        radial-gradient(115% 140% at 88% 0%, rgba(255, 255, 255, .16) 0%, rgba(255, 255, 255, 0) 58%),
        linear-gradient(135deg, var(--mud-palette-primary), var(--mud-palette-primary-darken, #C74A00));
    box-shadow: 0 14px 34px -24px rgba(0, 0, 0, .6);
}

.ff-subpage-head-body {
    display: flex;
    align-items: flex-start;
    justify-content: space-between;
    gap: 12px 16px;
    flex-wrap: wrap;
}

.ff-subpage-id { min-width: 0; }

.ff-subpage-title {
    color: #fff;
    font-weight: 800;
    letter-spacing: -.02em;
}

.ff-subpage-sub {
    margin-top: 4px;
    color: rgba(255, 255, 255, .85);
    font-size: .9rem;
    overflow-wrap: anywhere;
}

.ff-subpage-head .mud-button-outlined {
    color: #fff;
    border-color: rgba(255, 255, 255, .55);
    white-space: nowrap;
}

@media (max-width: 599.98px) {
    .ff-subpage-head { padding: 16px; }

    .ff-subpage-head .mud-button-outlined {
        width: 100%;
        min-height: 44px;
    }
}

/* The open invite code is a 16-character monospace slug. Everywhere it renders it must be ALLOWED
   to wrap rather than push the whole page into horizontal scroll (the Members & Invites card did
   exactly that at phone width; the letter-spacing makes the run wider than a 360px viewport).
   Later-in-file at equal specificity, so it composes with the base rule at line 588. */
.ff-invite-code {
    overflow-wrap: anywhere;
    min-width: 0;
}

@media (max-width: 599.98px) {
    /* Step the code down wherever it renders at heading size, mirroring the measured treatment
       the new-league card already ships (the .ff-invite-card rule above). */
    .ff-invite-code {
        font-size: 1.05rem;
        letter-spacing: .08em;
    }
}
/* ---- end league subpage polish ---- */

/* ---- CountStepper in the roster slot grid (owner report 2026-07-31) ----
   The slot grid's 110px column minimum was sized for the old compact MudNumericField spinners.
   A CountStepper is three parts (44px button + labeled value field + 44px button, ~200px all in),
   so under the old minimum a phone packed three columns and the value field collapsed to a sliver
   with a clipped label. 210px keeps the stepper whole: two columns on a large phone, one at 360px,
   three or four on desktop. Later-in-file at equal specificity, so it supersedes the base rule. */
.ff-slot-grid {
    grid-template-columns: repeat(auto-fit, minmax(min(100%, 210px), 1fr));
    gap: 12px 10px;
}
/* ---- end slot-grid stepper sizing ---- */

/* ---- Phase 38C: the commissioner's draft schedule (/commissioner/draft-schedule) and the one-line
   status strip on /commissioner/draft-order (plan §9.1, §9.3, §9.4).
   Appended as one block at the END of the file so parallel slices merge cleanly. Mobile first: every
   rule below is the 360px layout, and the two media queries only widen it. Touch targets on this page
   are 44px, because a commissioner setting a weekly start time is doing it on a phone. ---- */

.ff-ds-card { min-width: 0; }

.ff-ds-zone { margin-top: 2px; }

/* The day select and the time picker stack at 360px and share a row from 600px up; MudGrid handles
   the split, this only guarantees the field spacing and the touch height at both sizes. */
.ff-ds-fields { margin-top: 4px; }

.ff-ds-fields .mud-input-control { min-width: 0; }

/* Owner test 2026-07-31: the 44px touch floor belongs on the input CONTAINER, not on the value slot.
   MudBlazor 8 styles `.mud-input-slot`/`.mud-input-root` with `box-sizing: content-box` and, for the
   outlined variant, `padding: 18.5px 14px` — so a min-height there sized the CONTENT box and the 37px
   of vertical padding was added on top of it: a 56px field rendered at 81px, and because a MudSelect's
   value slot is a block-level div rather than a vertically centered input, all of the extra space
   collected UNDER the value. `.mud-input` is the bordered box itself: border-box, inline-flex and
   already center-aligned, so a floor here is the whole field's height and the value stays centred.
   With Margin.Dense on the two controls the intrinsic field is 40px, so this lifts it to exactly 44px:
   a normal dense outlined field that is still a 44px target on a phone. */
.ff-ds-fields .mud-input { min-height: 44px; }

.ff-ds-resolved {
    margin-top: 10px;
    overflow-wrap: anywhere;
}

.ff-ds-headline {
    margin-top: 2px;
    font-weight: 600;
    overflow-wrap: anywhere;
}

.ff-ds-actions {
    display: flex;
    flex-wrap: wrap;
    gap: 8px;
    margin-top: 12px;
}

.ff-ds-actions .mud-button-root { min-height: 44px; }

/* The preview's facts: one per line at 360px, two columns from 600px (plan §9.4). */
.ff-ds-facts {
    display: grid;
    grid-template-columns: 1fr;
    gap: 8px 16px;
    margin-top: 10px;
}

.ff-ds-fact {
    display: flex;
    flex-direction: column;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-ds-fact-label {
    font-size: .75rem;
    text-transform: uppercase;
    letter-spacing: .04em;
    opacity: .7;
}

/* Gap alerts and the load error: the sentence wraps and the action link drops to its own line at
   360px, then shares the row once there is space. */
.ff-ds-alert {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 4px 10px;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-ds-gap-link { white-space: nowrap; }

.ff-ds-override .mud-expand-panel-header { min-height: 44px; }

/* The Draft Order strip: wraps to two lines at 360px with the link on line 2, one line above that. */
.ff-do-sched {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 4px 8px;
    min-width: 0;
}

.ff-do-sched-text {
    min-width: 0;
    overflow-wrap: anywhere;
}

@media (min-width: 600px) {
    .ff-ds-facts { grid-template-columns: repeat(2, minmax(0, 1fr)); }
}

@media (max-width: 599.98px) {
    .ff-ds-actions .mud-button-root { width: 100%; }
}
/* ---- end Phase 38C draft schedule ---- */

/* ---- Phase 38D: scheduled draft start (the room countdown and the Home card) ----
   Appended at the END of the file so parallel slices merge cleanly. Two surfaces, one instant.

   The countdown is a single line wherever it renders (the room's pre-open banner and the dashboard
   card), so at 360px it never wraps a "Starts in 2d 4h" onto a second row beside its icon. */
.ff-start-countdown {
    display: inline-flex;
    align-items: center;
    white-space: nowrap;
}

/* The dashboard card: fact and countdown stack on a phone and share a row from 600px up (plan §9.4),
   with the link on its own line at 44px so it is a real touch target rather than a text sliver. */
.ff-sched-start-card .ff-sched-start-body {
    display: flex;
    flex-direction: column;
    gap: 2px;
    min-width: 0;
}

.ff-sched-start-card .ff-sched-start-link {
    display: inline-flex;
    align-items: center;
    min-height: 44px;
    /* Owner polish 2026-08-01: the 44px touch target stays, but its dead space overlaps the row gap
       above instead of stacking under it, so the card reads two tight lines plus a link rather than
       three roomy rows. */
    margin-top: -8px;
    margin-bottom: -6px;
}

@media (min-width: 600px) {
    .ff-sched-start-card .ff-sched-start-body {
        flex-direction: row;
        align-items: baseline;
        flex-wrap: wrap;
        gap: 4px 12px;
    }
}
/* ---- end scheduled draft start ---- */

/* ================================================================================================
   Owner phone pass (2026-08-01) - two surfaces where the chrome outgrew the viewport. Appended at
   the END of the file so parallel slices merge cleanly, and so these rules win the later-wins tie
   against the base .ff-page-head / .ff-breakouts-cols declarations they narrow.

   ITEM 1  /research/breakouts. Stacked, "decliners" sat an entire riser list below the fold, so the
        board had to be scrolled past to be found at all. Below 960px (the exact width where .ff-cols
        stops being two columns, so the two treatments meet with no gap and no overlap) the two panels
        become a two-segment toggle. Both panels still RENDER: the toggle only moves .ff-stack-off, so
        there is no second markup path to drift, no viewport probe, and no flash - the control is
        display:none by default and only the media query turns it on, so desktop never paints it.

   ITEM 2  /leaders. Measured at 360px against this stylesheet, the head + note + filter row cost
        roughly 300px before a single leader rendered, which is most of the first viewport.
        - The head. 95px -> 72px: the title drops from 1.7rem to 1.35rem, the subtitle to caption
          size, and the trailing margin halves. Scoped to .ff-leaders-head, not the global page head,
          because this is one page's finding and every other page keeps its own rhythm.
          SUPERSEDED 2026-08-19 (wave H4): /leaders now opens with the shared PageHero band, whose
          own phone rules already ARE this tightening (a 1.35rem title, tightened further to M1's
          clamp under TitleNoWrap, and a sub-line a size down from the page head's). The hook and
          its three rules are gone rather than left to fight the band for the same numbers; the
          filter-row half of this item below is untouched and still does the larger share.
        - The filter row. Margin.Dense in the markup takes each outlined box from 56px to 40px, so the
          three grid rows go 184px -> 136px. Collapsed (the phone default) only the first two grid
          cells render (Season and View) and the row is ONE line, ~40px plus a 36px button: ~136px ->
          ~76px. Nothing is removed. The folded pickers are display:none, so they leave the grid flow
          entirely and the two that remain fill the row cleanly; the existing "span the odd last
          child" rule is unaffected because it counts DOM children, and the child it targets is
          hidden while collapsed.
   ================================================================================================ */

/* ---- Item 1: the stacked-layout section toggle (breakouts) ---- */
/* Off everywhere by default. Only the stacked breakpoint turns it on, which is what guarantees a
   desktop render never shows it, not even for a frame. */
.ff-stack-tabs { display: none; }

@media (max-width: 960px) {
    .ff-stack-tabs { display: block; margin-bottom: 10px; }
    /* The segment that is not selected. Above 960px this class has no rule at all, so both columns
       render exactly as they did before this block existed. */
    .ff-breakouts-cols > .ff-panel.ff-stack-off { display: none; }
}

/* ---- Item 2: the collapsible filter row (the head half moved into PageHero, wave H4) ---- */
/* Off by default (media queries add no specificity, so the base rule has to come FIRST or it would
   win the later-wins tie and blank the button on the very screens that need it). Above 600px there
   is no disclosure at all: every picker is in the row, so the button would have nothing to do. */
.ff-more-filters-row { display: none; }

@media (max-width: 599.98px) {
    /* The four narrowing pickers, while the row is collapsed. The selector is POSITIONAL rather than
       the .ff-more-filter marker the markup carries, because a MudSelect puts its Class one level in
       (on .mud-input-control) while the grid places its OWN root: hiding the marker would blank the
       field and leave an empty cell holding its place. The marker still names which pickers fold, and
       a test pins the two to agree, so a reorder cannot silently fold the wrong two. */
    .ff-filter-grid.ff-more-collapsed > *:nth-child(n+3) { display: none; }
    /* Collapsed the row is one line, so it sits tight against its own toggle button. */
    .ff-filter-grid.ff-more-collapsed { margin-bottom: 4px; }

    .ff-more-filters-row { display: block; margin-bottom: 12px; }
    /* Flush left with the pickers above it, and a real 36px touch target rather than a text sliver. */
    .ff-more-filters-row .mud-button-root { margin-left: -8px; min-height: 36px; }
}
/* ---- end owner phone pass ---- */

/* ================================================================================================
   Phase 39G - the Freshman Watch segment (plan §6 39G). Appended at the END of the file so parallel
   slices merge cleanly, and so this rule wins the later-wins tie against the base .ff-cols /
   .ff-breakouts-cols declarations it narrows.

   The board grew a third panel, and .ff-cols is a hard `1fr 1fr`. Three panels in a two-column grid
   strand the third alone on row two at every desktop width, which reads as "and also this one"
   rather than as a third segment of one board. .ff-breakouts-cols therefore takes an auto-fit track
   list of its own: three panels side by side where there is room for three, two where there is room
   for two, and the third wraps under them.

   WHY min-width:961px and not an unqualified rule. Below 960px the board is a one-at-a-time segment
   toggle (the owner phone pass above): exactly one panel is displayed and the rest are display:none.
   An auto-fit grid there would size that single visible panel into the first ~320px track and leave
   the rest of a 700px tablet blank, so the stacked tier keeps .ff-cols' single column untouched. The
   961px floor is the exact complement of the toggle's `max-width: 960px`, so the two treatments meet
   with no gap and no overlap.

   `minmax(min(320px, 100%), 1fr)` rather than `minmax(320px, 1fr)`: the plain form cannot go below
   its 320px floor, so a container narrower than that overflows horizontally instead of shrinking.
   The min() form is the guard, and it costs nothing at any width where the floor already fits.
   ================================================================================================ */

@media (min-width: 961px) {
    .ff-breakouts-cols { grid-template-columns: repeat(auto-fit, minmax(min(320px, 100%), 1fr)); }
}

/* The phone toggle now carries THREE segments instead of two, and the acceptance is that none of the
   three labels truncates to an ellipsis at 360px. Measured against the shared .ff-segtab phone rule
   (6px/8px padding, .82rem, 4px gap): three segments leave ~64px of label width, and "Decliners" at
   that size wants ~65px, so the longest label was landing right on the ellipsis. Tightening the
   padding and dropping a notch of type buys ~7px of room on each. Scoped to .ff-stack-tabs, which is
   this board's toggle and nothing else: the Draft hub's and Compare's segmented controls carry fewer,
   shorter labels and keep the shared sizing. (.ff-segtabs is overflow-x:auto regardless, so the
   failure mode was never a page-wide horizontal scroll.) */
@media (max-width: 640px) {
    .ff-stack-tabs .ff-segtab { padding: 6px 5px; gap: 3px; font-size: .76rem; }
}
/* ---- end Phase 39G ---- */

/* ================================================================================================
   Phase 39L - the signal readiness strip (plan §6 39L). Appended at the END of the file so parallel
   slices merge cleanly.

   NO NEW PANEL TYPE. Every value here is borrowed from the two note families the research surfaces
   already ship: the muted flex row of .ff-research-note (Season Readiness SR-D) and the pill
   geometry of .ff-ctx-chip (P-24). A member should read the strip as the same kind of line they
   already read under these boards, because it is: for the whole preseason and the first four weeks
   of a season, "that number arrives in week 3" is the NORMAL state, not a problem, and an alert
   treatment would say the opposite.

   THE 360px SHAPE (acceptance: one wrapped chip row, no horizontal overflow, and the page's primary
   content stays above the fold). Three rules do it, and all three are CSS only so the markup is
   byte-identical at every width:
     1. The lead takes the full row below 600px, so the chips wrap onto their own line instead of
        trailing off the end of the sentence.
     2. The LIVE chips are hidden below 600px. The lead already states the live count ("4 of 6
        numbers are live this week."), so what is left is exactly the chips that need attention.
        Six chips wrapped three deep is the thing that pushes a board below the fold on a phone; one
        or two is a line.
     3. Chips wrap their own text rather than nowrap, so a long label can never push the row wider
        than the viewport. The trailing state word is the one thing pinned to a single line, because
        "week 3" broken across two lines reads as two facts.

   Color never carries meaning alone: every chip states its state in words ("live", "week 3", "off")
   and the palette token is decoration on top of that.
   ================================================================================================ */

.ff-signal-strip {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 6px 8px;
    margin: 0 0 12px;
    font-size: .78rem;
    line-height: 1.4;
    color: var(--mud-palette-text-secondary);
}

/* The lead is the affordance: a phone has no hover, so the sentences behind the chips have to be one
   tap away. A real 32px target, but with no button chrome, because it is a line of text. */
.ff-signal-lead {
    display: inline-flex;
    align-items: center;
    gap: 4px;
    flex: 0 1 auto;
    min-width: 0;
    min-height: 32px;
    padding: 2px 4px 2px 0;
    background: none;
    border: 0;
    color: inherit;
    font: inherit;
    text-align: left;
    cursor: pointer;
}

.ff-signal-lead:hover .ff-signal-sum { color: var(--mud-palette-text-primary); }

.ff-signal-lead .mud-icon-root { flex: 0 0 auto; font-size: 1rem; }

.ff-signal-sum {
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-signal-chips {
    display: flex;
    flex-wrap: wrap;
    gap: 4px;
    min-width: 0;
}

.ff-signal-chip {
    display: inline-flex;
    align-items: baseline;
    gap: 4px;
    max-width: 100%;
    padding: 1px 7px;
    border-radius: 999px;
    background: var(--mud-palette-background);
    border: 1px solid var(--mud-palette-lines-default);
    font-size: .68rem;
    line-height: 1.7;
    /* Wraps rather than nowrap: at 360px an overflowing pill is a horizontal scrollbar on the whole
       page, which the breakpoint matrix forbids. */
    white-space: normal;
    overflow-wrap: anywhere;
}

.ff-signal-chip .nm { color: var(--mud-palette-text-secondary); }
.ff-signal-chip .st { font-weight: 600; white-space: nowrap; }

.ff-signal-chip.is-live .st { color: var(--mud-palette-success); }
.ff-signal-chip.is-warming .st { color: var(--mud-palette-warning); }
.ff-signal-chip.is-off .st { color: var(--mud-palette-text-disabled); }

/* The expanded reasons. One sentence per signal, in the server's order, straight from the DTO. */
.ff-signal-detail {
    display: flex;
    flex-direction: column;
    gap: 6px;
    margin: 0 0 12px;
    font-size: .75rem;
    line-height: 1.45;
    color: var(--mud-palette-text-secondary);
}

.ff-signal-row {
    display: flex;
    flex-wrap: wrap;
    gap: 2px 6px;
    min-width: 0;
}

.ff-signal-row .nm { flex: 0 0 auto; font-weight: 600; }

/* flex-basis, not a width: the sentence sits beside its label where there is room for both and drops
   under it where there is not, which is what happens at 360px. */
.ff-signal-row .dt {
    flex: 1 1 220px;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-signal-row.is-live .nm { color: var(--mud-palette-success); }
.ff-signal-row.is-warming .nm { color: var(--mud-palette-warning); }

/* The draft room's shape (ratified Q8): one chip until tapped, and tighter under the segment strip
   because the room's next element is the board a member came to read. */
.ff-signal-strip.compact { margin-bottom: 8px; }

/* Inside a panel body the strip carries the body's own gutter, exactly as .ff-research-note does. */
.ff-panel-body > .ff-signal-strip { margin-bottom: 8px; }

@media (max-width: 599.98px) {
    .ff-signal-strip { gap: 4px; }
    /* 1. the lead owns its row, so the chips become a chip ROW rather than a tail */
    .ff-signal-lead { width: 100%; }
    /* 2. the live chips fold: the lead already counts them */
    .ff-signal-strip .ff-signal-chip.is-live { display: none; }
}
/* ---- end Phase 39L ---- */

/* ================================================================================================
   Phase 40A - the signal grammar (plan §5.1, §9.1). Appended at the END of the file so parallel
   slices merge cleanly.

   EXTENDS .ff-ctx-chip, DOES NOT REPLACE IT. Every pill in a SignalChip row carries BOTH classes, so
   the geometry, the label/value typography and the 360px wrapping come from the pill family the
   breakout and pool-change boards have shipped since P-24. Everything below is only what the grammar
   ADDS: the band tint, the compact fold, and the note's gap.

   CLASS NAMING, and why it is not .ff-signal-chip. Phase 39L already owns .ff-signal-strip /
   .ff-signal-chips / .ff-signal-chip for the readiness strip, which is a DIFFERENT component with a
   different job (it renders six signal STATES; this renders one number's four ATTRIBUTES). Reusing
   those selectors would have silently restyled the strip on five shipped pages, so the grammar's row
   is .ff-signal-attrs and its pill is .ff-signal-attr. The two families are deliberately adjacent in
   name because a member reads them as one language, and deliberately distinct in selector because
   they are not one component.

   COLOUR IS DERIVED FROM SignalCopy.BandClass AND FROM NOTHING ELSE (plan §9.1, and the 40A
   acceptance). Every colour-bearing rule in this block is anchored on a .band-* token, and the set of
   those tokens is exactly SignalCopy.BandClasses. There is no rule here whose selector is driven by a
   magnitude, a threshold or a percentage, because a thin sample must never be coloured into
   confidence. SignalGrammarStylesheetTests walks this block and fails on a token outside that
   vocabulary. The five band tints are the shipped .ff-dvp-chip palette, so a band reads the same
   whether it arrives as a DvP chip or as a grammar attribute.

   THE 360px SHAPE. The row wraps (it inherits .ff-ctx-chips-style flex-wrap here rather than reusing
   that class, because a grammar row also appears inside a page-head note where the board's top margin
   would be wrong). A pill wraps at SPACES so a long basis such as "recruiting pedigree and returning
   production" can never push the page wider than the viewport, and never inside a token, so a value
   like "1,840 player weeks" or "7.4% to 21.0%" cannot break mid-number. Below 600px the lens chip
   folds away by default: the page head carries the lens once, and repeating it on every row is the
   "wall of context" the chip cap exists to prevent.
   ================================================================================================ */

.ff-signal-attrs {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 4px;
    min-width: 0;
}

.ff-signal-attr {
    /* .ff-ctx-chip is nowrap, which is right for a two-word chip inside a table cell and wrong for a
       five-word basis at 360px: an overflowing pill is a horizontal scrollbar on the whole page. */
    white-space: normal;
    /* ...but only at spaces. overflow-wrap: anywhere here would split "1,840" across two lines. */
    overflow-wrap: normal;
    word-break: normal;
}

.ff-signal-attr .lbl { white-space: nowrap; }

/* The band tint, from the band WORD only (SignalCopy.BandClass). Same palette as .ff-dvp-chip. */
.ff-signal-attr.band-top10 .val { color: var(--mud-palette-error); }
.ff-signal-attr.band-tough .val { color: var(--mud-palette-warning); }
.ff-signal-attr.band-average .val { color: var(--mud-palette-text-secondary); }
.ff-signal-attr.band-soft .val { color: var(--mud-palette-info); }
.ff-signal-attr.band-bottom10 .val { color: var(--mud-palette-success); }
/* The insufficient state and the unknown band share one neutral treatment: a suppressed number is not
   a bad number, it is an absent one, so it is never tinted as if it carried a verdict. */
.ff-signal-attr.band-none .val { color: var(--mud-palette-text-secondary); font-weight: 600; }

/* A warming signal names the week it arrives; the week itself never wraps ("week 3" split over two
   lines reads as two facts). */
.ff-signal-attr.is-arrives .val { white-space: nowrap; }

/* The 360px short form, also available explicitly through Compact="true". */
.ff-signal-attrs.compact .ff-signal-attr.is-lens { display: none; }

@media (max-width: 599.98px) {
    .ff-signal-attrs .ff-signal-attr.is-lens { display: none; }
}

/* ---- SignalNote: the page-head prose line plus its chip row ---- */
/* The wrapper already carries .ff-ctx-note, so the type, colour and bottom margin are the shipped
   caption's. This only puts the sentence and the chips on one wrapping line. */
.ff-signal-note {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 4px 8px;
    min-width: 0;
}

.ff-signal-note > .txt {
    min-width: 0;
    flex: 1 1 auto;
}

/* ---- Placements ---- */
/* The breakout board's per-section basis row, directly under the section explainer and sharing its
   16px gutter so the chips line up with the sentence above them. */
.ff-section-signal { padding: 8px 16px 0; }

/* The player hub's projection accuracy caption. It is a .ff-ctx-note, so it only needs its own
   in-panel spacing and a wrapping row for the sentence plus its link. */
.ff-signal-accuracy {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 6px;
    margin-bottom: 0;
}
/* ---- end Phase 40A ---- */

/* =====================================================================================
   Phase 40C: the Research home (/research)
   Appended as its own commented tail block so parallel slices merge cleanly, and authored
   entirely on ELEMENTS THIS SLICE WRITES rather than on MudBlazor component roots (the
   scoped-CSS-anchor trap ScopedCssAnchorGuardTests exists to catch: a rule anchored on a
   component root silently never applies).

   No new panel type and no new tile geometry. The hero is the shipped .ff-panel, and the
   tile is the shipped .ff-hub-tile on the shipped MudItem xs/sm/md/lg grid, so the tiles
   go one per row at 360px, two at 600px and three at 960px with nothing here to say. The
   only additions are the two lines a research tile has that a launcher tile does not.
   ===================================================================================== */

/* The hero's own two lines. Deliberately typographic rather than structural: 40D fills this
   panel with the Edge sheet summary, and it should not have to undo a layout first. */
.ff-research-hero .ff-hero-head {
    font-size: 1.05rem;
    font-weight: 600;
    line-height: 1.25;
}

.ff-research-hero .ff-hero-sub {
    font-size: .8rem;
    color: var(--mud-palette-text-secondary);
    margin-top: 2px;
}

/* The strip sits directly under the hero's sentences, sharing the panel's own padding. */
.ff-research-hero .ff-signal-strip { margin-top: 10px; margin-bottom: 0; }

/* ---- The tile's fact line ----
   One line under the description. The FACT (a real count) and the READINESS sentence (why
   there is no count yet) are two different elements on purpose: it is what makes "a warming
   tile prints no digit in its fact line" assertable on the markup. They read alike because
   to a member both are simply what this surface has to say today; the readiness line is
   only slightly quieter, because "arrives in week 4" is the normal state for most of a
   season rather than a problem. */
.ff-tile-fact,
.ff-tile-readiness {
    font-size: .75rem;
    line-height: 1.35;
    margin-top: 6px;
    overflow-wrap: anywhere;
}

.ff-tile-fact {
    color: var(--mud-palette-text-primary);
    font-weight: 500;
}

.ff-tile-readiness {
    color: var(--mud-palette-text-secondary);
}

/* The n, in the shared signal grammar (Phase 40A). It renders nothing without a sample, so
   this only has to give it room when there is one. */
.ff-research-tile .ff-tile-signal { margin-top: 6px; }

/* ---- end Phase 40C ---- */

/* ================================================================================================
   Owner phone pass 2026-08-01: the readiness strip's phone geometry (39L follow-up).

   Two asks from the owner's live dev walk, both CSS only so every strip host inherits them:
     1. Less air above the strip. The page head keeps its 20px gutter for every page that does NOT
        carry a strip; where the strip directly follows the head, it pulls itself up to a 10px gap.
        Screen height is the scarce resource on game day.
     2. Denser pills below 600px. Six chips at .68rem wrapped three rows deep; the tightened type
        and padding pack the same six into two rows on a 390px phone without dropping the state
        word off its pill (the .st nowrap rule is 39L's and is untouched).
   ================================================================================================ */

.ff-page-head + .ff-signal-strip { margin-top: -10px; }

@media (max-width: 599.98px) {
    .ff-signal-chips { gap: 3px; }
    .ff-signal-strip .ff-signal-chip { font-size: .62rem; padding: 0 5px; gap: 3px; line-height: 1.65; }
}
/* ---- end owner phone pass 2026-08-01 ---- */


/* =====================================================================================
   Phase 40D: the week's Edge sheet (/draft/edge) and the Research home's hero
   Appended as its own commented tail block at the END of the file so parallel slices
   merge cleanly (plan §6.0 hands app.css to 40A, then 40C, then 40D, each adding its
   own banner and never editing into an earlier one).

   NO NEW PANEL TYPE, NO NEW CHIP, NO NEW COUNTDOWN. The blocks are the shipped .ff-panel,
   the rows are the shipped ResponsiveList (dense table at 600px and up, cards below it),
   the attributes are Phase 40A's .ff-signal-attr pills, the matchup token is the shipped
   .ff-matchup-chip and the countdown is the shipped .ff-start-countdown. Everything here
   is spacing and wrapping: the sheet is a composition of things that already exist.

   THE 360px SHAPE, which is the width members actually draft at. Every block is full
   width and stacks in payload order, so the seven read as a list rather than a grid. The
   pool line is the one long sentence on the page and it wraps at SPACES to at most three
   lines at 360px (about 44 characters a line, and the longest real sentence, an unrestricted
   week with four digit counts, is ~95 characters), never inside a token, so "1,842" can
   never break across two lines. Nothing here is horizontally scrollable and nothing here
   sets a width, which is what keeps the page free of the nested scroller trap the owner
   reported on 2026-07-31.

   Authored entirely on ELEMENTS THIS SLICE WRITES rather than on MudBlazor component roots
   (the scoped-CSS-anchor trap ScopedCssAnchorGuardTests exists to catch).
   ===================================================================================== */

/* Each of the seven blocks is a panel in one column. The gap is the page's own rhythm
   rather than a margin on the panel, so a block that renders nothing (block 6 with no
   instant, block 7 while the assistant is dark) leaves no hole behind it. */
.ff-edge-sheet {
    display: flex;
    flex-direction: column;
    gap: 12px;
}

.ff-edge-block { margin: 0; }

/* Block heads: a title and the link into the surface that owns the block. They share a
   row when there is room and wrap when there is not, so the link never shrinks below a
   tappable target at 360px. */
.ff-edge-head {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    justify-content: space-between;
    gap: 4px 12px;
    margin-bottom: 6px;
}

.ff-edge-title {
    font-size: .95rem;
    font-weight: 600;
    line-height: 1.3;
}

/* The pool line: the sheet's one sentence, and the only thing on the page that can run
   long. It wraps at spaces only. */
.ff-edge-pool-line {
    font-size: 1rem;
    font-weight: 600;
    line-height: 1.35;
    overflow-wrap: normal;
    word-break: normal;
}

/* The week's conferences, as links, under the sentence that named them. */
.ff-edge-conferences {
    display: flex;
    flex-wrap: wrap;
    gap: 4px 10px;
    margin-top: 6px;
    font-size: .8rem;
}

.ff-edge-conference { white-space: nowrap; }

/* A block's own sentence: the warming line, the unavailable reason, or the empty state.
   Quieter than a fact, because for most of a season it is the normal thing to say. */
.ff-edge-note {
    font-size: .8rem;
    line-height: 1.4;
    color: var(--mud-palette-text-secondary);
    margin-top: 6px;
}

/* The grammar row under a block head sits closer to it than a note does. */
.ff-edge-signal { margin: 2px 0 8px; }

/* The breakout board's "why" line, on the mobile card's full width line. */
.ff-edge-why {
    display: block;
    font-size: .78rem;
    line-height: 1.4;
    margin-bottom: 2px;
}

.ff-edge-queue-line {
    font-size: .9rem;
    font-weight: 600;
    line-height: 1.35;
}

/* The out of pool list: one name per line at 360px, name and reason on one line when the
   viewport can carry both. */
.ff-edge-list {
    list-style: none;
    margin: 8px 0 0;
    padding: 0;
    font-size: .8rem;
}

.ff-edge-list li {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 2px 8px;
    padding: 3px 0;
}

.ff-edge-list .nm { font-weight: 600; }

.ff-edge-list .rs { color: var(--mud-palette-text-secondary); }

.ff-edge-start-fact {
    font-size: .9rem;
    font-weight: 600;
    line-height: 1.35;
    margin-bottom: 4px;
}

/* Full width and 44px tall at 360px, which is the tap target the rest of the product uses. */
.ff-edge-ask { min-height: 44px; }

/* ---- The Research home's hero, filled ----
   The hero is the same payload in miniature, so it borrows the sheet's type and adds only
   its own spacing. */
.ff-research-hero .ff-hero-chips {
    display: flex;
    flex-wrap: wrap;
    gap: 4px;
    margin-top: 8px;
}

.ff-research-hero .ff-hero-queue {
    font-size: .8rem;
    line-height: 1.4;
    margin-top: 6px;
}

.ff-research-hero .ff-hero-cta {
    margin-top: 10px;
    min-height: 44px;
}

@media (min-width: 600px) {
    /* Above 360px the call to action rides at the end of the hero's own line rather than
       spanning it: the hero is a summary, and a full width button reads as the page's
       primary action rather than the block's. */
    .ff-research-hero .ff-hero-cta { margin-top: 12px; }
}

/* ---- end Phase 40D ---- */

/* ================================================================================================
   Phase 40E - the entry points (plan §4.5, §9.6). Appended at the END of the file so parallel
   slices merge cleanly, and authored on real elements rather than on a MudBlazor component root,
   which is the dead-rule class ScopedCssAnchorGuardTests exists to catch.

   Two rules only, because this slice's whole visual footprint is one dashboard card and one text
   link. The card deliberately borrows the scheduled-start card's geometry: the two sit adjacent on
   Home and a second spacing vocabulary between them would read as a layout bug.
   ================================================================================================ */

/* ---- The Home pointer at the week's Edge sheet ---- */

.ff-edge-pointer-card .ff-edge-pointer-body {
    display: flex;
    flex-direction: column;
    gap: 2px;
    /* Lets the pool sentence wrap instead of forcing the alert wider than 360px. */
    min-width: 0;
}

.ff-edge-pointer-card .ff-edge-pointer-link {
    display: inline-flex;
    align-items: center;
    /* The product's tap target, with its dead space folded into the row gap above rather than
       stacked under it (the same correction the scheduled-start card took on 2026-08-01). */
    min-height: 44px;
    margin-top: -8px;
    margin-bottom: -6px;
}

@media (min-width: 600px) {
    /* Above 360px the fact and the queue caption share a line, so the card is two rows rather
       than three and the tile grid below it does not move down a step. */
    .ff-edge-pointer-card .ff-edge-pointer-body {
        flex-direction: row;
        align-items: baseline;
        flex-wrap: wrap;
        gap: 4px 12px;
    }
}

/* ---- The draft room's pre-open pointer ----
   It rides inside an existing sentence, so it needs a leading space it cannot get from markup
   (razor collapses the whitespace around a component) and nothing else. */
.ff-room-edge-link { margin-left: 4px; }

/* ---- end Phase 40E ---- */

/* ================================================================================================
   Owner phone pass 2026-08-02: the ask pills and the Home pointer's breathing room.

   1. The suggested-question pills (assistant follow-ups, stat-search follow-ups and examples)
      render like the sent-message bubble they imitate: symmetric padding, text centered both
      ways, wrapping instead of clipping. MudChip's stock geometry sets a fixed height and a
      baseline-ish line box, which is why the pills read subtly off next to the perfectly
      symmetric orange bubble above them.
   2. The Home Edge pointer card gets real separation from the tile grid below it, paid for by
      trimming the same amount above so the page's total height barely moves.
   ================================================================================================ */

.ff-ask-pill.mud-chip {
    height: auto;
    min-height: 32px;
    padding: 6px 14px;
    border-radius: 16px;
    white-space: normal;
    text-align: center;
}

.ff-ask-pill.mud-chip .mud-chip-content {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    line-height: 1.35;
}

.ff-edge-pointer-grid { margin-top: -6px; }
.ff-edge-pointer-card { margin-bottom: 14px; }
/* ---- end owner phone pass 2026-08-02 ---- */

/* ================================================================================================
   Owner phone pass 2026-08-03: every readiness reason row wears the same shape.

   39L let each row's sentence sit beside its label on a 220px flex basis, which read fine until a
   long label ("Preseason team opportunity") pushed its sentence to a full-width second line while
   the five short-labeled rows kept the side-by-side shape. One row in a different format reads as
   a mistake, so all six now share the hanging layout: a fixed label column that wraps internally,
   and the sentence beside it at every width. Overrides 39L's .nm/.dt rules by cascade order.
   ================================================================================================ */

.ff-signal-row { flex-wrap: nowrap; }
.ff-signal-row .nm { flex: 0 0 148px; }
.ff-signal-row .dt { flex: 1 1 auto; }

@media (max-width: 419.98px) {
    /* The narrowest phones give the sentence a fairer share. */
    .ff-signal-row .nm { flex-basis: 124px; }
}
/* ---- end owner phone pass 2026-08-03 ---- */

/* ================================================================================================
   R7 (Numbers Round, 2026-08-03): the member-facing upside signal.

   Two surfaces render the SAME server-composed sentence, so they get one look: the player hub's
   "This week" panel (a clause beside the projected range) and the Edge sheet's riser rows (a clause
   under the "why"). It is a qualifier rather than a headline, so it rides at the caption weight the
   basis line beside it already uses, and it wraps rather than truncating at 360px, because the
   second half of the sentence is the honest half.

   No colour is derived here. The upside is a number with a history behind it, not a band, and the
   signal grammar's rule is that colour comes from a band class and from nothing else.
   ================================================================================================ */

.ff-proj-upside {
    font-size: .78rem;
    line-height: 1.4;
    opacity: .85;
}

.ff-edge-upside {
    display: block;
    margin-top: 3px;
    font-size: .74rem;
    line-height: 1.4;
    opacity: .85;
}
/* ---- end R7 upside signal ---- */

/* ================================================================================================
   T1 to T4 ride-along (2026-08-03): the class / departed mark, the chip legend, and the practice
   position chips that were clipped. One appended block so parallel slices merge cleanly.
   ================================================================================================ */

/* ---- T2: the class / departed superscript beside a player's name ------------------------------

   THE CONSTRAINT IS THAT IT MOVES NOTHING. It is rendered by exactly one component
   (PlayerClassMark.razor) into a dozen lists that were already tight at 360px, so: no horizontal
   padding, no margin except the hair before it, a font small enough to ride above the cap height, and
   a zero line-height contribution so a row's height is decided by the name and never by this.

   COLOUR COMES FROM THE STATED KIND, never from the text. A class mark is muted (it is context); a
   departed mark is warning coloured (it is a warning). The SHAPE differs too ("Jr" against "'25"), so
   the distinction survives a colour blind reader and a greyscale screenshot. */

.ff-class-mark {
    margin-left: 2px;
    font-size: .6em;
    font-weight: 700;
    letter-spacing: .02em;
    line-height: 0;
    vertical-align: super;
    white-space: nowrap;
    color: var(--mud-palette-text-secondary);
}

.ff-class-mark.is-departed {
    color: var(--mud-palette-warning);
}

/* ---- T3: the chip legend ---------------------------------------------------------------------

   Chrome borrowed wholesale from the readiness strip (.ff-signal-lead is reused verbatim, caret and
   all), because this is the same affordance in the same place: a quiet line under the page head that
   opens into sentences. A second panel style for the same job would be its own small inconsistency. */

.ff-chip-legend {
    display: flex;
    flex-direction: column;
    min-width: 0;
    margin: 0 0 4px;
    font-size: .8rem;
    color: var(--mud-palette-text-secondary);
}

.ff-chip-legend.compact {
    font-size: .75rem;
}

.ff-chip-legend-body {
    display: flex;
    flex-direction: column;
    gap: 12px;
    margin: 0 0 12px;
    font-size: .75rem;
    line-height: 1.45;
    color: var(--mud-palette-text-secondary);
}

.ff-chip-legend-sec {
    display: flex;
    flex-direction: column;
    gap: 4px;
    min-width: 0;
}

.ff-chip-legend-sec > .ttl {
    font-weight: 700;
    color: var(--mud-palette-text-primary);
}

.ff-chip-legend-sec > .intro,
.ff-chip-legend-sec > .foot {
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-chip-legend-sec > .foot {
    font-style: italic;
    opacity: .8;
}

/* The label and its sentence sit side by side where there is room and stack where there is not, which
   is what happens at 360px. flex-basis, not a width (the readiness row's rule, verbatim). */
.ff-chip-legend-sec > .row {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 2px 8px;
    min-width: 0;
}

.ff-chip-legend-sec > .row > .lbl {
    flex: 0 0 auto;
    min-width: 54px;
    padding: 1px 6px;
    border-radius: 8px;
    font-size: .62rem;
    font-weight: 700;
    letter-spacing: .03em;
    text-align: center;
    background: rgba(158, 158, 158, .16);
    color: var(--mud-palette-text-secondary);
}

.ff-chip-legend-sec > .row > .mean {
    flex: 1 1 200px;
    min-width: 0;
    overflow-wrap: anywhere;
}

/* The legend's swatches use the SAME colours the chips do, so the row a member reads looks like the
   chip they were looking at. Matchup bands mirror MatchupChip.razor. */
.ff-chip-legend-sec > .row > .lbl.band-smash { color: var(--mud-palette-success); background: rgba(76, 175, 80, .16); }
.ff-chip-legend-sec > .row > .lbl.band-boom { color: var(--mud-palette-info); background: rgba(3, 169, 244, .16); }
.ff-chip-legend-sec > .row > .lbl.band-trap { color: var(--mud-palette-error); background: rgba(244, 67, 54, .16); }

/* Form trends mirror .ff-draft-trend. */
.ff-chip-legend-sec > .row > .lbl.trend-hot { color: var(--mud-palette-error); background: rgba(244, 67, 54, .16); }
.ff-chip-legend-sec > .row > .lbl.trend-cold { color: var(--mud-palette-info); background: rgba(3, 169, 244, .16); }

/* DvP bands mirror the shipped band chip: stingy defenses read as a warning to the drafter, generous
   ones as an opportunity. Colour is keyed off SignalCopy.BandClass and off nothing else. */
.ff-chip-legend-sec > .row > .lbl.dvp-top10 { color: var(--mud-palette-error); background: rgba(244, 67, 54, .16); }
.ff-chip-legend-sec > .row > .lbl.dvp-tough { color: var(--mud-palette-warning); background: rgba(255, 152, 0, .16); }
.ff-chip-legend-sec > .row > .lbl.dvp-soft { color: var(--mud-palette-info); background: rgba(3, 169, 244, .16); }
.ff-chip-legend-sec > .row > .lbl.dvp-bottom10 { color: var(--mud-palette-success); background: rgba(76, 175, 80, .16); }

/* ---- T4: the practice position chips that were clipped ---------------------------------------

   ROOT CAUSE. Base .ff-pos carries `padding: 3px 0` (ZERO horizontal padding) because it was authored
   to FILL a fixed grid track, where the track supplies the width. Every FLEX context therefore has to
   restore a natural width itself, and the house pattern for that is width:auto plus a min-width plus
   real horizontal padding (see .ff-teamstrip-slot .ff-pos, and the Rankings table's inline override).

   Three practice side renderings never got that override, so their labels sat flush against the pill
   edge. These restore it at the base .66rem, "like they are in every other place". The since-picks
   strip is an overflow-x scroller, so a full size chip there is safe: it scrolls, it never wraps.
   PracticeRecentPicks is deliberately NOT in this list: it renders .ff-pos.inrow inside a fixed 48px
   grid track, which is the shape the base rule was written for and is already wider than these. */

.ff-practice-recap-where .ff-pos,
.ff-recap-pick > .ff-pos,
.ff-practice-since-chip .ff-pos {
    flex: 0 0 auto;
    width: auto;
    min-width: 32px;
    padding: 2px 6px;
    font-size: .66rem;
    border-radius: 6px;
}
/* ---- end T1 to T4 ride-along ---- */

/* ================================================================================================
   NUMBERS ROUND AUDIT FIXES (2026-08-03) — appended block so parallel slices merge cleanly.
   ================================================================================================ */

/* ---- F9: the class / departed superscript must not be the thing that gets clipped --------------

   .ff-draft-pname carried the ellipsis trio (overflow:hidden, text-overflow:ellipsis,
   white-space:nowrap) and the T2 mark rides INSIDE it, so on the draft board and the practice board a
   long name pushed the superscript past the box and the browser truncated the mark first. The mark is
   the shortest and most information dense thing in the row, and its tooltip went with it.

   The fix keeps the row exactly one line at 360px and moves the truncation onto the NAME: the anchor
   becomes a single-line flex row (min-width:0 preserved so it can still shrink inside its grid track),
   the new inner .ff-draft-pname-txt owns the ellipsis, and the mark is flex:0 0 auto so it is laid out
   at its natural width and never squeezed. A row that carries no mark renders as it did before: one
   flex child, ellipsised the same way.

   THE MARK IS RE-RAISED EXPLICITLY, and that is not cosmetic pedantry. A flex item ignores
   vertical-align, so the base .ff-class-mark rule's "vertical-align: super" (and its 0 line height,
   which only makes sense for inline content) stop applying the moment the anchor becomes a flex
   container. Aligning the items to flex-start and giving the mark a real line height puts the small
   glyph at the TOP of the name's line box, which is what a superscript looks like, and keeps the row's
   height decided by the name exactly as before. The override is scoped to .ff-draft-pname, so the
   dozen other surfaces that render this mark as ordinary inline content are untouched. */

.ff-draft-pname {
    display: flex;
    align-items: flex-start;
    flex-wrap: nowrap;
    min-width: 0;
    overflow: hidden;
}

.ff-draft-pname-txt {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

.ff-draft-pname .ff-class-mark {
    flex: 0 0 auto;
    align-self: flex-start;
    line-height: 1;
    vertical-align: baseline;
}
/* ---- end Numbers Round audit fixes ---- */

/* ================================================================================================
   MOBILE POLISH (2026-08-03) — appended tail block so parallel slices merge cleanly.

   Two defects the owner caught on an iPhone at roughly 390px of CSS width: the app bar's unread badge
   was cut off by the top of the screen, and the readiness strip and the chip legend each spent a full
   width row on nothing but a toggle.
   ================================================================================================ */

/* ---- 1. the app bar's unread badge was clipped by the top of the viewport ----------------------

   ROOT CAUSE, in MudBlazor 8's own geometry, and it is arithmetic rather than opinion. The bell is a
   default MudIconButton: a 24px glyph with 12px of padding on every side, so its box is 48px. MudBadge
   anchors TopRight with Overlap against THAT box, using
   `inset: auto auto calc(100% - 12px) calc(100% - 12px)`, which places the badge's BOTTOM edge 12px
   below the button's top edge. The badge is 20px tall (height:20px under the global border-box reset,
   so the 2px Bordered ring is inside it), so its TOP edge lands 8px ABOVE the button. The phone app
   bar's toolbar is 56px (--mud-appbar-height, 64px, less an eighth), so a vertically centred 48px
   button leaves only 4px of slack above it, and MudAppBar is fixed at top:0. The badge therefore
   overhangs the viewport's own top edge by 4px and the browser simply cannot paint that strip. Desktop
   escapes it by accident: .ff-appbar bumps the toolbar to 72px above 600px, which leaves 12px of slack
   and puts the badge's top edge at +4px.

   THE FIX BOUNDS THE BADGE BY THE THING IT DECORATES rather than by the bar. 20px is the badge's own
   height, so `bottom: calc(100% - 20px)` lands its top edge flush with the icon button's top edge: any
   bar tall enough to hold the 48px button is now tall enough to hold the badge, with 4px of clearance
   at the 56px phone bar and 12px at the 72px desktop bar. The bell row does not move and the bar does
   not grow.

   HORIZONTAL PLACEMENT IS DELIBERATELY UNTOUCHED. The badge keeps `left: calc(100% - 12px)`, which
   starts it exactly where the 24px glyph box ends, so it cannot drift inward onto the bell at ANY
   width. Scoped to the app bar, so every other MudBadge in the product is unchanged; four class
   selectors so it beats MudBlazor's own four-class overlap rule on its own terms. */

.ff-appbar .mud-badge.mud-badge-top.right {
    bottom: calc(100% - 20px);
}

/* ---- 2. one row for the readiness lead and the chip legend toggle ------------------------------

   Four surfaces stacked SignalReadinessStrip and a standalone ChipLegend, and each spent a full width
   row on a toggle. Merged, the strip's first row is [readiness lead][legend toggle] and the chips wrap
   under it, which is one whole row (plus its margins) back on a phone.

   FLEX BASIS 0 ON THE LEAD IS THE LOAD BEARING PART. .ff-signal-strip is a WRAPPING flex container,
   and a wrapping container breaks lines on its items' hypothetical sizes, BEFORE any shrinking is
   applied: at the shipped `flex: 0 1 auto` a long readiness sentence would push the legend toggle onto
   a row of its own and undo the merge, no matter how shrinkable the lead is. At basis 0 the two
   toggles always collect onto the first line, and the lead then GROWS into whatever the toggle leaves
   (min-width:0 plus .ff-signal-sum's overflow-wrap already let its sentence wrap inside its own box).
   The 360px arithmetic, with the longest real lead sentence ("5 of 6 numbers are live this week.") and
   the page's own 16px gutters: 328px of content width, less the phone-shaped legend toggle (the word
   plus the caret, about 55px) and the 4px flex gap, leaves about 269px for a sentence that measures
   about 256px at .78rem. It fits on one line, and if a wider font ever makes it not fit, the sentence
   wraps INSIDE the lead and the row still holds two controls rather than becoming two rows.

   max-width:fit-content keeps the desktop hit area honest: without it the invisible lead button would
   grow across the whole row and a click on empty space would open the reasons. */

.ff-signal-strip.has-legend .ff-signal-lead {
    /* outranks the 39L phone rule that gives every lead a full width row of its own, at any width */
    width: auto;
    flex: 1 1 0;
    max-width: fit-content;
}

.ff-signal-strip.has-legend .ff-legend-toggle {
    flex: 0 0 auto;
    margin-left: auto;
}

/* The chips are their own flex LINE. A 100% basis can never share a line with anything, so the merged
   row is exactly [readiness lead][legend toggle] at every width and the chips wrap under it, which is
   what the phone already did with them. */
.ff-signal-strip.has-legend .ff-signal-chips {
    flex: 1 1 100%;
}

/* The merged toggle's two labels. The long one is the standalone legend's wording verbatim and is the
   button's accessible name at every width; the short one is the phone shape, and it is a substring of
   that name so a voice-control member can still say what they see. Only the MERGED row shortens: the
   legend-only row (a surface whose readiness read answered nothing) has the width to spare and keeps
   the full question, exactly as the standalone legend does. */
.ff-legend-short {
    display: none;
}

@media (max-width: 599.98px) {
    .ff-signal-strip.has-legend .ff-legend-toggle .ff-signal-ico { display: none; }
    .ff-signal-strip.has-legend .ff-legend-long { display: none; }
    .ff-signal-strip.has-legend .ff-legend-short { display: inline; }
}
/* ---- end mobile polish 2026-08-03 ---- */

/* Owner phone pass (2026-08-03): the DvP card head is a FLEX row, and the base .ff-pos was authored
   to fill fixed grid tracks (padding 3px 0, zero horizontal). Every flex context must supply the
   full-size override or the chip renders squished with the text touching its edges, which is exactly
   what the team hub's Defense vs position cards did. Same numbers as the practice-surface fix. */
.ff-dvp-card-head .ff-pos { flex: 0 0 auto; width: auto; min-width: 34px; padding: 2px 7px; }

/* ---- IN-16: the draft advisor's reason chain (2026-08-06) ---- */
/* The recommended pick states what it ranked on, one step per line. It is deliberately a list rather
   than a sentence: the room is the phone surface of this product, and a four-clause sentence wraps
   into an unreadable paragraph at 360px, where a short stack of lines still scans. Bulletless, because
   the steps are a sequence of statements and not a set of options, and the marker would spend width
   the phone does not have. Colours and size follow .ff-draft-rec-reason exactly, so the chain and the
   single sentence it replaces read as the same voice. */
.ff-draft-rec-chain {
    list-style: none;
    margin: 4px 0 0;
    padding: 0;
    font-size: .82rem;
    color: var(--mud-palette-text-primary);
}

.ff-draft-rec-chain li {
    margin: 0;
    padding: 0 0 0 10px;
    position: relative;
    line-height: 1.35;
    overflow-wrap: anywhere;
}

/* A hairline lead-in rather than a bullet glyph: it groups the steps as one chain at a glance and
   costs 10px instead of a full marker column. */
.ff-draft-rec-chain li::before {
    content: "";
    position: absolute;
    left: 0;
    top: .55em;
    width: 4px;
    height: 1px;
    background: var(--mud-palette-text-secondary);
    opacity: .7;
}

.ff-draft-rec-chain li + li {
    margin-top: 2px;
}
/* ---- end IN-16 reason chain ---- */

/* ================================================================================================
   Nav consolidation (owner greenlit 2026-08-06) - the consolidated Research drawer rows. Appended at
   the END of the file so parallel slices merge cleanly.

   ONE rule, and it exists because of where MudBlazor puts the class. A consolidated row stands for a
   SET of routes ("Players & Teams" covers /players and /teams), and MudNavLink resolves its own
   highlight from its single Href, so no Match value can light /players up while the member is on
   /teams. NavMenu therefore computes that itself - but MudNavLink's Class parameter lands on the
   wrapper .mud-nav-item, not on the .mud-nav-link anchor the active styling keys off, so the marker
   has to be forwarded down one level.

   The declarations are MudBlazor's own default-variant active values (color: primary on the
   action-default-hover background), quoted rather than invented, so a consolidated row that is lit
   for a sibling route is pixel-identical to one MudBlazor lit itself. Theme-aware for free: both
   values are palette variables, which light and dark each supply.
   ================================================================================================ */
.mud-navmenu .mud-nav-item.ff-nav-row-active > .mud-nav-link:not(.mud-nav-link-disabled) {
    color: var(--mud-palette-primary);
    background-color: var(--mud-palette-action-default-hover);
}
/* ---- end nav consolidation ---- */

/* ================================================================================================
   Nav consolidation, second section (2026-08-06) - the section strip at 360px. Appended at the END of
   the file so parallel slices merge cleanly.

   ACCEPTANCE: none of a section's segment labels truncates to an ellipsis at 360px. The boards section
   is the case that needs help, because its labels are the ledger's words rather than short invented
   ones: "Draft Board", "Leaders", "Pool changes".

   THE ARITHMETIC, measured the same way the breakout board's own toggle was (Phase 39G above). At
   360px the content column is about 328px, and .ff-segtabs spends 4px of padding a side plus a 4px gap
   between segments, so three segments get about 104px each. On the shared .ff-segtab phone rule that
   104px pays for 16px of horizontal padding, a 20px Size.Small icon and a 4px gap before the label,
   leaving about 64px - and "Pool changes" at .82rem wants about 78px. It would ellipsis.

   TWO CHANGES BUY IT BACK, both scoped to .ff-research-tabs so the Draft hub, Compare and the breakout
   board keep the sizing they were measured on:
     1. Drop the icon below 640px. It is decoration here: the drawer row this strip replaced carries the
        same icon, and the label is the thing a member reads. That alone returns 24px.
     2. Drop a notch of type, which returns another few px and keeps the two-segment Players and Teams
        strip comfortable rather than merely fitting.
   Together that is about 92px of label room against about 74px of longest label, which is margin rather
   than a coin flip. Above 640px nothing changes at all.

   (.ff-segtabs is overflow-x:auto regardless, so the failure mode was never a page-wide horizontal
   scroll: it was a truncated word.)
   ================================================================================================ */
@media (max-width: 640px) {
    .ff-research-tabs .ff-segtab { padding: 6px 6px; font-size: .78rem; }
    .ff-research-tabs .ff-segtab-ico { display: none; }
}
/* ---- end nav consolidation section strip ---- */

/* ================================================================================================
   Conference resting state (2026-08-06) - the season strip on /draft/conferences. Appended at the END
   of the file so parallel slices merge cleanly.

   THE PAGE BECAME A DESTINATION. It gained a permanent drawer row, so a member can now walk into it on
   any Tuesday in March, and its answer then was two sentences. The four blocks it answers with instead
   are all the shipped .ff-panel: no new panel type, no new tile geometry, nothing to re-measure. The
   ONE thing that needed geometry of its own is the season strip, because it is a three-column record
   (week, its conferences, who chose it) and the middle column holds a list of proper nouns of
   unbounded length.

   360px FIRST. At the narrowest width a three-column grid would give the conference list about 120px,
   which is one conference name and an ellipsis, so the strip stacks: the week label and the chooser
   share the top row (short, both of them), and the conference list takes a full row under them. From
   600px up there is room for the real three-column record and it becomes one.

   The list column wraps with overflow-wrap:anywhere for the same reason the matchup browser above does:
   a conference name this app has never seen must not be able to push the page sideways.
   ================================================================================================ */
.ff-conf-history {
    display: flex;
    flex-direction: column;
}

.ff-conf-history-row {
    display: grid;
    grid-template-columns: auto 1fr;
    grid-template-areas:
        "wk by"
        "pool pool";
    gap: 2px 12px;
    padding: 8px 2px;
    border-bottom: 1px solid var(--mud-palette-lines-default);
}

.ff-conf-history-row:last-child { border-bottom: none; }

.ff-conf-history-row .wk {
    grid-area: wk;
    font-weight: 600;
    font-size: .84rem;
    white-space: nowrap;
}

.ff-conf-history-row .pool {
    grid-area: pool;
    font-size: .84rem;
    overflow-wrap: anywhere;
}

/* The chooser is the secondary fact on the row, and it is also where the lone "no data" glyph lands
   for a week whose provenance the data genuinely does not determine. */
.ff-conf-history-row .by {
    grid-area: by;
    font-size: .78rem;
    color: var(--mud-palette-text-secondary);
    text-align: right;
    overflow-wrap: anywhere;
}

@media (min-width: 600px) {
    .ff-conf-history-row {
        grid-template-columns: 84px 1fr auto;
        grid-template-areas: "wk pool by";
        align-items: baseline;
    }
}
/* ---- end conference resting state ---- */

/* ================================================================================================
   Conference pool preview (IN-19, 2026-08-06) - what each conference puts in next week's pool, on
   /draft/conferences. Appended at the END of the file so parallel slices merge cleanly.

   THE LAYOUT IS THE PRODUCT RULE. The ratified rule is pool composition, never a recommendation, and
   a table with a sortable-looking numeric column reads as a leaderboard whatever the copy says. So
   there is no column grid, no alignment that invites an eye to run down it comparing, and no colour
   scale: each conference is a row of its own with its three counts written out as words beside the
   number. A member reads "14 in the top 50" as a fact about the SEC, not as a cell in a race.

   360px FIRST. The conference name takes its own line and the three counts wrap under it, so the
   longest name this app knows ("American Athletic") never competes with a number for width. From
   600px the name takes a fixed leading column and the counts sit beside it on one line.

   No new panel type: the block is the shipped .ff-panel, like every other block on this page.
   ================================================================================================ */
.ff-conf-preview {
    display: flex;
    flex-direction: column;
}

.ff-conf-preview-row {
    display: flex;
    flex-direction: column;
    gap: 2px;
    padding: 8px 2px;
    border-bottom: 1px solid var(--mud-palette-lines-default);
}

.ff-conf-preview-row:last-child { border-bottom: none; }

.ff-conf-preview-row .name {
    font-weight: 600;
    font-size: .88rem;
    overflow-wrap: anywhere;
}

/* The counts wrap rather than scroll: they are three short phrases, and a horizontal scroller for
   three short phrases is worse than a second line. */
.ff-conf-preview-row .metrics {
    display: flex;
    flex-wrap: wrap;
    gap: 4px 14px;
}

.ff-conf-preview-row .metrics .m {
    font-size: .8rem;
    color: var(--mud-palette-text-secondary);
    white-space: nowrap;
}

.ff-conf-preview-row .metrics .m b { color: var(--mud-palette-text-primary); }

@media (min-width: 600px) {
    .ff-conf-preview-row {
        flex-direction: row;
        align-items: baseline;
        gap: 14px;
    }

    .ff-conf-preview-row .name { flex: 0 0 150px; }

    .ff-conf-preview-row .metrics { flex: 1 1 auto; }
}
/* ---- end conference pool preview ---- */

/* ---- reigning week winner crown (appended block: keep at the END of this file) ----
   One small glyph marking the member who won the latest scored week, in the same idiom as the
   scoreboard's win-streak flame (.ff-sb-flame): no color wash, no badge chrome, no border.

   Two placements, and both are built to cost NO layout:

   1. On an avatar (.ff-crowned) the wrapper stands in for the avatar as the parent's child, so a
      four-column grid row stays four columns and a gapped flex row keeps its gaps. The glyph itself
      is absolutely positioned, so it adds zero width even at 360px. The wrapper is inline-flex and
      flex:0 0 auto so it measures exactly like the avatar it replaces.
   2. After a name (the chip, and MemberName when a surface opts in) it is an inline mark, sized
      below the surrounding text and kept off the name's ellipsis with flex:0 0 auto.

   Only the reigning winner renders any of this, so on every other row the markup is not there at
   all and nothing about that row changes. */
.ff-crowned {
    position: relative;
    display: inline-flex;
    flex: 0 0 auto;
    /* Keeps the wrapper sitting where the bare avatar sat in an inline context (no descender gap), and
       is simply ignored when the parent is a flex or grid container. Deliberately NOT line-height:0,
       which would inherit into the avatar and squash its initials. */
    vertical-align: middle;
}

.ff-crowned > .ff-crown {
    position: absolute;
    top: -3px;
    right: -3px;
    margin-left: 0;
    /* Absolute, so the mark costs no width; a fixed size, so it reads the same on a 26px standings
       avatar and on a Large profile hero. */
    font-size: .68rem;
    /* A halo in the page's own surface color so the glyph stays legible over a light photo, in both
       the dark default and the light theme. */
    text-shadow: 0 0 2px var(--mud-palette-surface), 0 0 3px var(--mud-palette-surface);
}

.ff-crown {
    font-size: .78em;
    line-height: 1;
    flex: 0 0 auto;
    white-space: nowrap;
    margin-left: 3px;
    /* The glyph is decorative next to a name that is already there; the accessible text is on the
       element's aria-label/title, so it never needs to steal a pointer event. */
    pointer-events: none;
}

/* The chip places its crown after the name, so the name's ellipsis must not eat the mark: the name
   flexes, the crown does not. */
.ff-member-chip .ff-crown { margin-left: 4px; }

/* The dashboard hero's reigning-winner fact line. Same secondary weight as .ff-page-sub (it is a
   fact, not a card) and it wraps rather than overflowing when two co-winners have long team names. */
.ff-page-fact {
    color: var(--mud-palette-text-secondary);
    font-size: .9rem;
    margin-top: 4px;
    overflow-wrap: anywhere;
}
/* ---- end reigning week winner crown ---- */

/* ---- multi-league onboarding CTAs (2026-08-06) -------------------------------------------------
   The "Want to run another league?" row on the league overview. Compact by design: it is an offer,
   not a task, so it never takes the visual weight of the commissioner checklist above it. Phone
   first (stacked, full-width button), side by side from 600px up. Appended at the end of the sheet
   so parallel work merges cleanly. */

.ff-another-league-row {
    display: flex;
    flex-direction: column;
    align-items: flex-start;
    gap: 12px;
}

/* min-width:0 lets the sentence wrap inside the flex row instead of forcing the card wider than a
   360px viewport. */
.ff-another-league-text { min-width: 0; }

.ff-another-league-btn { width: 100%; }

@media (min-width: 600px) {
    .ff-another-league-row {
        flex-direction: row;
        align-items: center;
        justify-content: space-between;
        gap: 20px;
    }

    .ff-another-league-text { flex: 1 1 auto; }

    .ff-another-league-btn {
        width: auto;
        flex: 0 0 auto;
        white-space: nowrap;
    }
}
/* ---- end multi-league onboarding CTAs ---- */

/* ---- Create a League, Roster rules step: one surface per slot (owner report 2026-08-06) ----
   Appended as one block at the END of the file so parallel slices merge cleanly.

   The five slot steppers used to share .ff-slot-grid with the league-settings roster editor. That
   grid's column minimum (210px) packed three of them across a desktop card, and its 10px column gap
   was barely wider than the 6px gap INSIDE a stepper, so WR's plus button sat right beside FLEX's
   minus and the row read as one undifferentiated strip of buttons. Phone width was never the problem;
   one column hides the collision.

   Two fixes, both about grouping rather than size:
     1. A 300px column minimum. Two columns on a desktop card, one below roughly 620px of usable
        width, which at 360px is the only thing that fits anyway. min(100%, 300px) keeps the track from
        overflowing a narrow card.
     2. Every slot sits on its own surface, the same treatment .ff-review-grid already gives the review
        step's tiles on this very page. The gap BETWEEN fields is now always larger than the gap within
        one, and each field reads as a single pill: label, minus, value, plus.

   .ff-slot-grid is deliberately untouched, because LeagueSettings still shares it.

   The stepper's own geometry is NOT here. It lives in the shared NumericStepper.razor.css, and these
   rules only place and dress the grid cell. */

.ff-roster-slot-grid {
    display: grid;
    grid-template-columns: repeat(auto-fit, minmax(min(100%, 300px), 1fr));
    gap: 14px 20px;
}

.ff-roster-slot-grid > .ff-stepper {
    padding: 10px 12px;
    border-radius: 9px;
    background: var(--mud-palette-background-gray);
}
/* ---- end roster rules step ---- */

/* ---- draft room, rehearsal fixes (2026-08-06) --------------------------------------------------
   Three small blocks from the owner's staged week-2 dress rehearsal. Appended at the end of the sheet
   so parallel work merges cleanly.

   1. The recent-picks strip gains a per-row pick ordinal (#1..#40). It takes its own narrow track at
      the head of the existing grid rather than riding inside the slot chip, so a two digit and a one
      digit number line up and the name column keeps every pixel it had. The track is repeated in the
      360px rule below, where the strip already drops the school.
   2. The best-available board gets an empty state, because a position tab with nothing behind it used
      to render an empty box under a "Best available" heading, which reads as broken rather than as an
      answer.
   3. The post-draft recap's waiting line gets three crunching dots. CSS only, reusing the shipped
      ff-seg-pulse keyframe (the live-draft segtab dot) so the room has one idiom for "working", not
      two. Staggered by delay alone, and silenced entirely under prefers-reduced-motion. */

.ff-room-recent-num {
    font-size: .72rem;
    font-weight: 700;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
    white-space: nowrap;
}

/* The ordinal is a new FIRST track on both of the strip's grids. Kept here rather than edited into the
   B3b block above so this whole slice is one appended region. */
.ff-room-recent-row {
    grid-template-columns: 34px 48px minmax(0, 1fr) minmax(0, .7fr) minmax(0, .7fr);
}

@media (max-width: 599.98px) {
    .ff-room-recent-row {
        grid-template-columns: 30px 42px minmax(0, 1fr) minmax(0, .8fr);
    }
}

.ff-draft-empty {
    padding: 12px 2px;
    font-size: .84rem;
    color: var(--mud-palette-text-secondary);
}

/* The waiting recap: dots beside the sentence, never over it. min-width:0 keeps the sentence wrapping
   inside the row at 360px instead of pushing the panel wider than the viewport. */
.ff-recap-pending-row {
    display: flex;
    align-items: center;
    gap: 8px;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-recap-crunch {
    display: inline-flex;
    align-items: center;
    gap: 3px;
    flex: 0 0 auto;
}

.ff-recap-crunch i {
    width: 5px;
    height: 5px;
    border-radius: 50%;
    background: var(--mud-palette-primary);
    animation: ff-seg-pulse 1.4s ease-in-out infinite;
}

.ff-recap-crunch i:nth-child(2) { animation-delay: .18s; }
.ff-recap-crunch i:nth-child(3) { animation-delay: .36s; }

@media (prefers-reduced-motion: reduce) {
    .ff-recap-crunch i { animation: none; opacity: .6; }
}
/* ---- end draft room rehearsal fixes ---- */

/* ---- unscored-week notice (rehearsal 2026-08-06) ----
   Between a draft landing and its games being played every member sits on 0.0. The surfaces that
   would otherwise rank or compare that all-zero week say so instead, in one shared style: the My Team
   "Your week" panel and the Scoreboard's This Week tab. Deliberately quiet (secondary text, a hairline
   rule, no colour) because it is an explanation, not a warning, and it wraps cleanly at 360px. */
.ff-week-unscored {
    color: var(--mud-palette-text-secondary);
    font-size: .78rem;
    line-height: 1.45;
    padding: 8px 0 4px;
    border-top: 1px solid var(--mud-palette-lines-default);
    margin-top: 8px;
}

/* The "lead" variant heads a panel instead of following a tile row (the Scoreboard's This Week tab),
   so it drops the rule above it and keeps its spacing below. */
.ff-week-unscored.lead {
    border-top: none;
    margin-top: 0;
    padding: 0 0 10px;
}
/* ---- end unscored-week notice ---- */

/* ---- notifications feed: per row dismiss + clear read (2026-08-06) ----
   The feed could mark read but never delete. The row is a flex line rather than a MudListItem Href so
   the dismiss control is a real button BESIDE the link instead of a button nested inside an anchor.
   min-width:0 on the body is what lets a long title wrap instead of pushing the dismiss button off a
   360px screen, and the button keeps a 36px hit target at every width. */
.ff-notify-head { display: flex; align-items: center; flex-wrap: wrap; gap: 8px; }

.ff-notify-row { display: flex; align-items: flex-start; gap: 10px; width: 100%; }

.ff-notify-icon { margin-top: 3px; flex: 0 0 auto; color: var(--mud-palette-text-secondary); }

.ff-notify-body { flex: 1 1 auto; min-width: 0; overflow-wrap: anywhere; }

.ff-notify-dismiss { flex: 0 0 auto; align-self: flex-start; }
/* ---- end notifications feed dismiss ---- */

/* ---- season-readiness folded summary (2026-08-06 game-day round) ----
   The commissioner readiness panel is fourteen rows and growing, and most are green most of the year.
   The rows that want something stay in the open; the settled ones fold behind one summary row, which is
   a MudBlazor expansion panel stripped back to a quiet list row so it reads as part of the list rather
   than as a card sitting on top of it. Every row inside keeps its own .ff-srf-row styling untouched.
   At 360px the summary text and the chevron share one line and the folded rows stack exactly as the
   open ones do. */
.ff-srf-ready { background: transparent; }

.ff-srf-ready .mud-expand-panel {
    background: transparent;
    border-radius: 8px;
    margin-top: 2px;
}

/* MudBlazor draws a divider above a panel that follows another block; the open list already has its
   own spacing, so the rule would double up. */
.ff-srf-ready .mud-expand-panel::before { content: none; }

.ff-srf-ready .mud-expand-panel-header {
    padding: 9px 10px;
    border-left: 3px solid var(--mud-palette-lines-default);
    border-radius: 8px;
    min-height: 0;
}

.ff-srf-ready .mud-expand-panel-text {
    font-size: .8rem;
    font-weight: 600;
    color: var(--mud-palette-text-secondary);
}

/* The folded rows sit flush with the open ones above them, not indented inside a panel body. */
.ff-srf-ready .mud-expand-panel-content { padding: 0; }
.ff-srf-ready .mud-expand-panel-content .ff-srf-list { padding: 2px 0 4px; }
/* ---- end season-readiness folded summary ---- */

/* The Game Day league board reuses the shared unscored-week notice, but that board is not inside a
   padded panel body: its rows carry their own 12px inset. Match it so the sentence lines up with the
   member names under it at every width. */
.ff-gd-board-unscored { padding-left: 12px; padding-right: 12px; }

/* ============================================================================================
   Game Day enrichments (2026-08-06 game-day round, stacked on the readiness polish slice).
   Appended as one block at the END of the file so parallel slices merge cleanly.

   Five additions, all mobile-first and theme-var driven, all verified to wrap rather than scroll
   at 360px:
     1. .ff-gd-next   - the "Next up" strip (what kicks off next + a live countdown), and its
                        quiet "that's a wrap" twin once the last game is final.
     2. .ff-gd-race   - the one-sentence close-race line under it.
     3. .daygrp       - the day header that chunks "Your slate" into local days (only rendered
                        when the slate actually spans more than one).
     4. .ff-gd-wx     - the advisory weather chip on a slate row (the draft board's chip idiom,
                        which carried its styling inline; this is the same look as a class).
     5. .ff-gd-watch  - the "from your watchlist today" row, and .sub .gm, the member row's
                        finished / live / to-play chips.
   ============================================================================================ */

/* ---- 1. Next up + the week's wrap ---- */
.ff-gd-next {
    display: flex; align-items: center; flex-wrap: wrap; gap: 4px 10px;
    margin: 0 0 12px; padding: 9px 12px;
    border: 1px solid var(--mud-palette-lines-default);
    border-left: 3px solid var(--mud-palette-primary);
    border-radius: 10px;
    background: var(--mud-palette-background-gray);
    font-size: .84rem;
}

.ff-gd-next > .mud-icon-root { font-size: 1.05rem; color: var(--mud-palette-primary); flex: none; }

.ff-gd-next .lbl {
    font-size: .64rem; font-weight: 700; letter-spacing: .08em; text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

/* The game itself is the sentence's subject, so it takes the weight and the room. min-width:0 is
   what lets a long "Player Name at Some Long School" wrap instead of pushing the countdown off a
   360px screen. */
.ff-gd-next .who { font-weight: 700; min-width: 0; overflow-wrap: anywhere; }
.ff-gd-next .when { font-variant-numeric: tabular-nums; color: var(--mud-palette-text-secondary); }

/* The countdown is the only part that moves, so it gets the pill and sits at the end of the line
   (and at the start of its own line once the strip wraps). */
.ff-gd-next .cd {
    margin-left: auto; flex: none;
    padding: 2px 9px; border-radius: 999px;
    font-size: .74rem; font-weight: 700; font-variant-numeric: tabular-nums;
    color: var(--mud-palette-primary);
    background: rgba(var(--mud-palette-primary-rgb), .12);
}

.ff-gd-next.done { border-left-color: var(--mud-palette-lines-default); }
.ff-gd-next.done > .mud-icon-root { color: var(--mud-palette-text-secondary); }
.ff-gd-next.done .who { font-weight: 500; color: var(--mud-palette-text-secondary); }

@media (max-width: 479.98px) {
    /* Phone: the game gets its own full-width line, the countdown rides back up beside the label. */
    .ff-gd-next .who { flex-basis: 100%; order: 3; }
    .ff-gd-next .when { order: 4; }
    .ff-gd-next .cd { order: 2; }
}

/* ---- 2. The close-race line ---- */
.ff-gd-race {
    margin: -4px 0 12px; padding: 0 2px;
    font-size: .86rem; line-height: 1.45;
    color: var(--mud-palette-text-secondary);
}

.ff-gd-race strong { color: var(--mud-palette-text-primary); font-weight: 700; }

/* ---- 3. Slate day headers ---- */
.ff-gd-slate-list .daygrp {
    padding: 6px 10px 5px;
    border-top: 1px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-background);
    font-size: .64rem; font-weight: 700; letter-spacing: .08em; text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

/* ---- 4. Weather chip on a slate row ----
   The names cell becomes a flex row so the chip can sit beside the names without being swallowed
   by their ellipsis; the clamp moves onto .nm, which is the same fix .ff-gd-slate made for its
   own text child (text-overflow needs a block box, not a bare text node in a flex row). */
.ff-gd-slate-list .row .who { display: flex; align-items: center; gap: 6px; }

.ff-gd-slate-list .row .who .nm {
    min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}

.ff-gd-wx {
    display: inline-flex; align-items: center; gap: 2px; flex: none;
    padding: 0 5px; border-radius: 8px; white-space: nowrap;
    font-size: .6rem; font-weight: 700; line-height: 1.6;
    color: var(--mud-palette-warning); background: rgba(255, 152, 0, .16);
}

/* Wind AND precipitation, the draft board's Color.Error case. */
.ff-gd-wx.sev { color: var(--mud-palette-error); background: rgba(244, 67, 54, .16); }
.ff-gd-wx .mud-icon-root { font-size: .8rem; }

/* ---- 5. Watchlist row + member-row game chips ---- */
.ff-gd-watch {
    display: flex; align-items: baseline; flex-wrap: wrap; gap: 4px 8px;
    margin: -4px 6px 10px; padding: 0 4px;
    font-size: .76rem;
}

.ff-gd-watch .lbl {
    display: inline-flex; align-items: center; gap: 4px;
    font-size: .64rem; font-weight: 700; letter-spacing: .06em; text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-gd-watch .lbl .mud-icon-root { font-size: .9rem; }
.ff-gd-watch .names { display: inline-flex; flex-wrap: wrap; gap: 4px 10px; min-width: 0; }
.ff-gd-watch a { color: var(--mud-palette-primary); font-weight: 600; text-decoration: none; }
.ff-gd-watch a:hover { text-decoration: underline; }
.ff-gd-watch .more { color: var(--mud-palette-text-secondary); }

/* The board row's finished / live / to-play triptych. Chips rather than bare words so the count
   that carries the tension (what is still coming) is findable at a glance; .sub is already a
   wrapping flex row, so these stack instead of scrolling at 360px. */
.ff-gd-board-main .sub .gm {
    padding: 1px 6px; border-radius: 7px;
    font-weight: 700; font-variant-numeric: tabular-nums;
    background: var(--mud-palette-background-gray);
    border: 1px solid var(--mud-palette-lines-default);
}

.ff-gd-board-main .sub .gm.final { color: var(--mud-palette-text-secondary); }
.ff-gd-board-main .sub .gm.up { color: var(--mud-palette-text-primary); }

.ff-gd-board-main .sub .gm.live {
    color: #ef4444; border-color: rgba(239, 68, 68, .45); background: rgba(239, 68, 68, .12);
}
/* ---- end Game Day enrichments ---- */

/* ================================================================================================
   OWNER WALKTHROUGH 2026-08-06: the merged Game Day row line, and the practice recap's best-pick
   verdict.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into an
   earlier block: every rule below is either a new class or a deliberate later override of a shipped
   one, and a later slice adds its own bannered block after this one.
   ================================================================================================ */

/* ---- 1. Game Day: one line per lineup row before kickoff --------------------------------------
   The pre-kickoff row printed the same instant twice (the chip's "Sat 6:00 PM vs Missouri State"
   over the slate line's "Sat 6:00 PM on ABC"). They are one line now, which makes that line roughly
   twice as long, and the shipped .ff-gd-slate .txt clamp is a nowrap ellipsis written for a long
   NETWORK name ("Big Ten Network"). Applied to the merged line it would cut the sentence off mid
   opponent on a 360px phone, so the merged variant wraps instead. Only the merged variant: the short
   network-only line keeps its single-line clamp. */

.ff-gd-slate.merged {
    align-items: flex-start;
    line-height: 1.35;
}

/* Wrapping at spaces is the point; overflow-wrap only catches a single unbroken token, which would
   otherwise push the row sideways instead of folding. */
.ff-gd-slate.merged .txt {
    white-space: normal;
    overflow: visible;
    text-overflow: clip;
    overflow-wrap: anywhere;
}

/* The icon leads the line, so it stays on the first row rather than centring itself against a two
   line block. */
.ff-gd-slate.merged .ff-gd-slate-ico {
    margin-top: 2px;
}

/* ---- 2. Practice recap: the round that was the best pick on the board --------------------------
   A correct pick used to print the same player twice, once as "you took" and once as "best still
   there". The repeat is gone; what is left is the star on the round and one green sentence, which is
   the thing a practice draft exists to teach. */

.ff-practice-recap-star {
    display: inline-flex;
    align-items: center;
    color: var(--mud-palette-success);
}

.ff-practice-recap-star .mud-icon-root {
    font-size: 1rem;
}

/* Sits in the cell the dropped line used to occupy, so a best round and a missed one line up at
   every breakpoint instead of one of them collapsing the row. */
.ff-practice-recap-verdict {
    display: flex;
    align-items: baseline;
    min-width: 0;
    font-size: .8rem;
    font-weight: 700;
    color: var(--mud-palette-success);
}

/* The earned sentence beside the captured pair. Inline so it reads as part of that line on a wide
   screen, and it simply wraps to its own line on a phone. */
.ff-practice-recap-perfect {
    display: inline-flex;
    align-items: center;
    gap: 4px;
    margin-left: 6px;
    font-weight: 700;
    color: var(--mud-palette-success);
}

.ff-practice-recap-perfect .mud-icon-root {
    font-size: 1rem;
}

/* ---- 3. The verdict chip now earns its line on a phone -----------------------------------------
   34E hid this cell below 960px, and that was right when it held a bare signed number: the pair
   above it said the same thing and a phone had better uses for the row. It holds a sentence now
   ("6.5 points left on the board"), which is the row's lesson rather than its arithmetic, so it is
   visible at every width. It spans the full row under the pair at 360px and 600px, and keeps its own
   column at 960px exactly as the breakpoint matrix intended. */

.ff-practice-recap-delta {
    display: block;
}

.ff-practice-recap-delta .chip {
    width: auto;
    justify-content: flex-start;
    text-align: left;
    padding: 2px 8px;
}

@media (min-width: 600px) {
    .ff-practice-recap-delta {
        grid-column: 1 / -1;
    }
}

@media (min-width: 960px) {
    /* A sentence needs more than the 104px a signed number needed. */
    .ff-practice-recap-row {
        grid-template-columns: 126px minmax(0, 1fr) minmax(0, 1fr) 176px;
    }

    .ff-practice-recap-delta {
        grid-column: auto;
    }

    .ff-practice-recap-delta .chip {
        width: 100%;
        justify-content: center;
        text-align: center;
    }

    /* A best round has no gap chip, so its verdict takes the space the chip would have used. Columns
       1 and 2 stay identical to every other row, which is what keeps the picks and their values
       reading down the list as one column rather than jogging left and right. */
    .ff-practice-recap-row.best .ff-practice-recap-verdict {
        grid-column: 3 / -1;
    }
}
/* ---- end owner walkthrough 2026-08-06 ---- */

/* ================================================================================================
   UIDN-7 (Draft Experience Campaign 1): the Game Day member row's game-unit label.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into an
   earlier block: the rule below is a new class, and a later slice adds its own block after it.
   ================================================================================================ */

/* The chips beside this label count GAMES, not picks (a member's two players in one game are one
   game to watch), and a row that never said so read as a missing player. It is sized and cased like
   the page's other small labels (.ff-gd-next .lbl, .ff-gd-watch .lbl) so it reads as the run's
   caption rather than as a fourth chip. .sub is already a wrapping flex row, so the label wraps
   with the chips at 360px instead of pushing them off the screen; align-self keeps it on the chips'
   centre line rather than stretching to their padded height. */
.ff-gd-board-main .sub .gmlbl {
    align-self: center;
    flex: none;
    font-size: .64rem; font-weight: 700; letter-spacing: .06em; text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}
/* ---- end UIDN-7 ---- */

/* ================================================================================================
   TIMING-5 (Draft Experience Campaign 1): the pick clock's disclosure line and the operator panel.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into an
   earlier block: both selectors are new classes, and a later slice adds its own block after this one.
   ================================================================================================ */

/* The one-line "why is this clock this long" note under the countdown, inside the on-the-clock alert.
   The icon is fixed width and the text is the flexible half, so the sentence wraps under itself at
   360px instead of pushing the alert wider; align-items:flex-start keeps the icon on the FIRST line
   of a wrapped sentence rather than floating to its vertical centre. It inherits the caption's own
   colour and size from MudText, so nothing here restates typography. */
.ff-pick-clock-why {
    display: flex;
    align-items: flex-start;
    gap: 4px;
    margin-top: 2px;
}

.ff-pick-clock-why .mud-icon-root {
    flex: none;
    margin-top: 1px;
}

/* The operator panel's label/value rows. One column on a phone (label above its value, which is the
   only shape that survives a long localized instant at 360px) and a two-column definition list from
   600px up, where the labels line up and the eye can run down the values. minmax(0, 1fr) rather than
   1fr so a long unbroken value shrinks instead of forcing the page to scroll sideways. */
.ff-clock-diag-rows {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    row-gap: 2px;
    column-gap: 12px;
}

.ff-clock-diag-rows .lbl {
    font-size: .64rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
    align-self: center;
}

.ff-clock-diag-rows .val {
    font-size: .9rem;
    margin-bottom: 8px;
    overflow-wrap: anywhere;
}

@media (min-width: 600px) {
    .ff-clock-diag-rows {
        grid-template-columns: 12rem minmax(0, 1fr);
    }

    .ff-clock-diag-rows .val {
        margin-bottom: 4px;
    }
}

/* The load-failure alert: message and retry sit on one line where there is room and stack where there
   is not, matching the draft schedule page's own alert shape. */
.ff-clock-diag-alert {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 8px;
}
/* ---- end TIMING-5 ---- */

/* ================================================================================================
   CFBD-3 (Draft Experience Campaign 1): the weekly detail page's game-state line.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into an
   earlier block: the rules below are new classes, and a later slice adds its own block after this.
   ================================================================================================ */

/* The line that sits between the week-vs-average strip and the scoring breakdown when the game
   behind the numbers has not finished. It is a quiet note, not an alert: the breakdown is still the
   page's subject, and this only explains why its numbers are provisional. Block display and normal
   wrapping keep the sentence inside 360px without a horizontal scrollbar (it is a full sentence,
   which is exactly why it must not be a nowrap chip). */
.ff-live-note {
    margin: 12px 2px 0;
    padding: 8px 10px;
    border-radius: 8px;
    border-left: 3px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-background-gray);
    color: var(--mud-palette-text-secondary);
    font-size: .82rem;
    line-height: 1.35;
}

/* A game in progress is the one state worth the accent and the full-strength text: it is the case
   the page used to get wrong ("held scoreless" over a live first quarter). */
.ff-live-note.live {
    border-left-color: var(--mud-palette-error);
    color: var(--mud-palette-text-primary);
}

/* Still to play reads as anticipation rather than alarm; unknown and final stay on the default
   neutral border, because neither is news. */
.ff-live-note.upcoming {
    border-left-color: var(--mud-palette-primary);
}
/* ---- end CFBD-3 ---- */

/* ================================================================================================
   TIMING-4 (Draft Experience Campaign 1): the automation console's weekly handoff timeline.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into an
   earlier block: every rule below is scoped under .ff-chain, and a later slice adds its own block
   after it.
   ================================================================================================ */

/* The chain is an ordered list, because it IS one: eight steps that only make sense in sequence, and
   a screen reader should say so. The marker column is a fixed 24px so the connecting rail lines up
   whatever a step's body wraps to, and the whole thing is a two column grid rather than a float so
   the body can wrap freely at 360px without ever pushing the rail off centre. */
.ff-chain {
    list-style: none;
    margin: 0 0 12px;
    padding: 0;
}

.ff-chain-step {
    display: grid;
    grid-template-columns: 24px minmax(0, 1fr);
    gap: 10px;
    padding: 0 0 12px;
    position: relative;
}

/* The rail between the markers. It is drawn on the step rather than behind the list so the LAST step
   has none, which is what makes the end of the chain read as an end. */
.ff-chain-step:not(:last-child)::before {
    content: "";
    position: absolute;
    left: 11px;
    top: 22px;
    bottom: 2px;
    width: 2px;
    background: var(--mud-palette-divider);
}

.ff-chain-step .mark {
    display: flex;
    align-items: flex-start;
    justify-content: center;
    /* Above the rail, so the rail runs behind the icon rather than through its gap. */
    position: relative;
    z-index: 1;
    background: var(--mud-palette-surface);
}

.ff-chain-step .head {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 8px;
}

.ff-chain-step .ttl {
    font-weight: 600;
    font-size: .92rem;
}

/* The state word is the glanceable half, so it is cased and tracked like the app's other small
   labels rather than competing with the step title. */
.ff-chain-step .state {
    font-size: .64rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-chain-step.late .state,
.ff-chain-step.failed .state {
    color: var(--mud-palette-error);
}

.ff-chain-step .why {
    font-size: .82rem;
    color: var(--mud-palette-text-primary);
}

.ff-chain-step .when {
    font-size: .76rem;
    color: var(--mud-palette-text-secondary);
    margin-top: 2px;
}

/* The job's own next due sentence and the claim key it ran under. Operator diagnostics, so they are
   the quietest thing in the row, and they wrap rather than scroll: a cycle key is short enough to
   break at 360px and an overflow box would hide the end of it. */
.ff-chain-step .detail {
    font-size: .72rem;
    color: var(--mud-palette-text-disabled);
    margin-top: 2px;
    overflow-wrap: anywhere;
}

/* A step that does not apply is still worth reading (it says WHY it does not apply), but it should
   not draw the eye past the steps that do. */
.ff-chain-step.skipped .why {
    color: var(--mud-palette-text-secondary);
}
/* ---- end TIMING-4 ---- */

/* BH-4 (Draft Experience Campaign 1): the Board's labeled week-breakdown affordance.
   The Board's fourth column used to be a bare points span while the player's NAME carried the weekly
   attribution route. Ratified audit Q16 split those two jobs, so the column is now the labeled action
   ("Week breakdown") and the name is the canonical profile handoff.
   It deliberately reuses the row's existing .pick-pts cell rather than adding a fifth grid column, so
   the row keeps the same four tracks at every width and the 360px layout is byte-identical apart from
   the icon. The tap target is grown with a minimum HEIGHT and padding; the only minimum width is on
   the icon-only defense variant, which has no number beside it to make the target. */
.ff-pick-row .ff-pick-breakdown {
    display: inline-flex;
    align-items: center;
    justify-content: flex-end;
    gap: 5px;
    min-height: 36px;
    padding: 2px 0 2px 8px;
    color: inherit;
    text-decoration: none;
    cursor: pointer;
}

/* Icon-only (a defense row: this board carries no weekly total for one), so the icon has to be the
   whole 36px target by itself. 36px is a tap target, not a layout width: the column is auto-sized and
   the name cell beside it is the 1fr track that absorbs the difference. */
.ff-pick-row .ff-pick-breakdown.icon-only {
    min-width: 36px;
    justify-content: center;
    padding: 2px;
}

.ff-pick-row .ff-pick-breakdown .pts {
    font-variant-numeric: tabular-nums;
}

/* Quiet by default so the board still reads as a list of picks, and it colours up on hover/focus so
   the affordance announces itself as one. Focus-visible carries the keyboard half. */
.ff-pick-row .ff-pick-breakdown .mud-icon-root {
    font-size: 1.05rem;
    color: var(--mud-palette-text-secondary);
}

.ff-pick-row .ff-pick-breakdown:hover .mud-icon-root,
.ff-pick-row .ff-pick-breakdown:focus-visible .mud-icon-root {
    color: var(--mud-palette-primary);
}

.ff-pick-row .ff-pick-breakdown:hover .pts,
.ff-pick-row .ff-pick-breakdown:focus-visible .pts {
    text-decoration: underline;
}

.ff-pick-row .ff-pick-breakdown:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
    border-radius: 4px;
}

/* The "By member" roster rows link their names now too. The cell already ellipsizes its overflow, so
   the link inherits the row's colour and weight instead of turning five names per card blue. */
.ff-roster-row .name .mud-typography {
    color: inherit;
    font-weight: inherit;
    font-size: inherit;
}
/* ---- end BH-4 ---- */

/* ---- ASST-4: assistant entity-chip badges ---- */

/* The chip's small state words (rostered / queued / no open slot / drafted). They were an inline style
   on the one rostered badge; ASST-4 gives the reason badges the same shape, so it becomes a class rather
   than the same declaration written four times. flex-shrink:0 keeps the badge whole at 360px: the chip's
   name is the part with an ellipsis budget, and a half-cut "no open slot" would be worse than a wrapped
   chip row. */
.ff-entity-chip .ff-entity-badge {
    font-size: .65rem;
    font-weight: 700;
    text-transform: uppercase;
    letter-spacing: .03em;
    line-height: 1.4;
    padding: 0 5px;
    border-radius: 8px;
    white-space: nowrap;
    flex-shrink: 0;
    color: var(--ff-brand, var(--mud-palette-primary));
    border: 1px solid var(--ff-brand, var(--mud-palette-primary));
}

/* A reason badge replaces an action rather than decorating a name, so it reads as secondary text instead
   of borrowing the brand accent the rostered badge uses. */
.ff-entity-chip .ff-entity-badge-reason {
    color: var(--mud-palette-text-secondary);
    border-color: var(--mud-palette-lines-default);
}
/* ---- end ASST-4 ---- */

/* ================================================================================================
   SI-8 (Draft Experience Campaign 1): the affected-pick audit report at /commissioner/affected-picks.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into an
   earlier block: every rule below is a new class, and a later slice adds its own block after this.
   ================================================================================================ */

/* The report's summary rows. Same shape and the same reasoning as the pick-clock panel's rows: one
   column on a phone (label above its value, the only shape that survives a long localized instant at
   360px) and a two-column definition list from 600px up. Its own class rather than a shared one
   because the two panels are separate surfaces and a later change to either must not silently move
   the other. */
.ff-affected-rows {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    row-gap: 2px;
    column-gap: 12px;
}

.ff-affected-rows .lbl {
    font-size: .64rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
    align-self: center;
}

.ff-affected-rows .val {
    font-size: .9rem;
    margin-bottom: 8px;
    overflow-wrap: anywhere;
}

@media (min-width: 600px) {
    .ff-affected-rows {
        grid-template-columns: 12rem minmax(0, 1fr);
    }

    .ff-affected-rows .val {
        margin-bottom: 4px;
    }
}

/* One flagged pick. Deliberately a stacked block rather than a table row: the report carries a name, a
   member, two schools, one to three full sentences and sometimes a graded value, and no honest table of
   that at 360px exists. The left rule is what makes a run of them read as a list. */
.ff-affected-pick {
    padding: 8px 0 8px 10px;
    border-left: 3px solid var(--mud-palette-lines-default);
    margin-bottom: 10px;
}

.ff-affected-pick:last-child {
    margin-bottom: 0;
}

/* Name and its metadata wrap independently: the metadata line is long (family, ordinal, member) and
   must be allowed to fall under the name on a phone rather than push the row sideways. */
.ff-affected-pick .who {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    column-gap: 8px;
}

.ff-affected-pick .who .name {
    font-weight: 600;
    overflow-wrap: anywhere;
}

.ff-affected-pick .who .meta {
    font-size: .74rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-affected-pick .schools {
    font-size: .82rem;
    margin-top: 2px;
    overflow-wrap: anywhere;
}

/* The reasons are prose, so they wrap normally and keep the page inside 360px without a horizontal
   scrollbar. List markers are dropped in favour of the block's own left rule. */
.ff-affected-pick .reasons {
    list-style: none;
    margin: 4px 0 0;
    padding: 0;
    font-size: .82rem;
    color: var(--mud-palette-text-secondary);
}

.ff-affected-pick .reasons li {
    margin-top: 2px;
    overflow-wrap: anywhere;
}

/* The divergence line is the one number on the row, so it is the one part that is not secondary text. */
.ff-affected-pick .graded {
    font-size: .82rem;
    margin-top: 4px;
    overflow-wrap: anywhere;
}

/* The load-failure alert: message and retry on one line where there is room, stacked where there is not. */
.ff-affected-alert {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 8px;
}
/* ---- end SI-8 ---- */

/* ================================================================================================
   AU-L5 (Draft Experience Campaign 1, audit fix): the Game Day "games:" caption owns its own run.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into an
   earlier block: the rule below is a new class, and a later slice adds its own block after it.
   ================================================================================================ */

/* The caption and the three GAME chips are one element now, with the projection chip ("12.3 on the
   field", which is points) left outside it. They were flat siblings in .sub, so the label captioned
   whatever happened to follow it and a row could read "games: 4 final 12.3 on the field".

   It inherits .sub's own wrapping flex layout with the same gaps, so the chips still wrap under
   each other at 360px exactly as they did while they were direct children, and the whole run wraps
   as a unit rather than orphaning its caption on the line above. */
.ff-gd-board-main .sub .gmrun {
    display: inline-flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 4px 10px;
    min-width: 0;
}
/* ---- end AU-L5 ---- */

/* ================================================================================================
   UIDN-4 (Draft Experience Campaign, Wave J): My Team's two-area wide grid.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into the
   batch-D block that built the wrap; these rules extend it from a later position in the cascade.

   The defect: .ff-team-wrap holds THREE sibling panels (the lineup card, "Your week", and the
   regret replay) but batch-D only gave it "grid-template-columns: 1fr 1fr" and only released the
   "Your week" panel from its stacked-era 720px cap. The replay auto-placed into row 2 column 1, so
   it began below the taller of the two row-1 panels (a dead band under the lineup) and rendered at
   720px inside a column roughly 900px wide (a narrow orphan card). Naming the areas fixes both: the
   replay follows the lineup directly down the left column while "Your week" spans the right.

   Everything below is inside the 961px query, which is the exact complement of the batch-D
   "max-width: 960px" stack rule, so the single-column phone/tablet layout is untouched.
   ================================================================================================ */

@media (min-width: 961px) {
    /* Place by name rather than by source order: the DOM order stays lineup, week, replay, which is
       also the reading order the sub-960 stack depends on. */
    .ff-team-wrap { grid-template-areas: "lineup week" "replay week"; }

    /* Naming the areas alone still leaves a gap, because a spanning item taller than the rows it
       spans grows BOTH of them equally: measured at 1440px with a 300px lineup, an 820px "Your week"
       and a 380px replay, that pushed 62px of dead space between the two left-column cards and left
       another 62px under the replay. Sizing row 2 flexibly takes the whole remainder out of the row
       BELOW the replay instead, so the replay sits exactly one 16px gap under the lineup and the
       left column's slack collects at the bottom where nothing reads it as a separator. A short
       "Your week" panel is unaffected: the flexible row still resolves to the replay's own height.
       Only the two-row shape needs this, so it is gated on both panels being present. */
    .ff-team-wrap.has-week.has-replay { grid-template-rows: auto 1fr; }

    .ff-team-wrap > .ff-mt-lineup { grid-area: lineup; }
    .ff-team-wrap > .ff-mt-week { grid-area: week; }

    /* The replay joins the grid contract the way the "Your week" panel did: scoped to the wrap, so a
       replay panel rendered anywhere else keeps its own cap, and scoped to this query, so the phone
       stack keeps the cap and the 16px top margin it ships with today. */
    .ff-team-wrap > .ff-eff-replay { grid-area: replay; max-width: none; margin-top: 0; }

    /* Degradation, driven by the razor-computed wrap state classes rather than :has(), so a bUnit
       render can assert which shape the page asked for.

       No replay (the efficiency flag is dark, or its read has not answered yet): one row of two
       columns, which is exactly what this pair rendered before this block existed. A PENDING week
       is not this case: the panel mounts and holds its own "scores are still coming in" state, so
       it takes its area like any other replay.

       No "Your week" panel (no roster at all): the right column has nothing to span, so the survivor
       pair shares the single row. When BOTH are absent these two rules tie on specificity and the
       later one wins, which is the same single row with an empty second column: the lone lineup card
       keeps the half-width it has today rather than stretching an empty state across the monitor. */
    .ff-team-wrap:not(.has-replay) { grid-template-areas: "lineup week"; }
    .ff-team-wrap:not(.has-week) { grid-template-areas: "lineup replay"; }
}
/* ---- end UIDN-4 ---- */

/* ================================================================================================
   BH-2 (Draft Experience campaign, Wave J; hoisted to Campaign 1 by owner direction 2026-08-30):
   the room's recent-picks strip scrolls through the WHOLE draft.

   The strip used to render six rows and hide all but three on a phone, directly under a head that
   said "45 picks so far". Everything past row six (or row three) was simply unreachable from the
   room. The component no longer trims, and the phone's nth-child hide is gone from the B3b block
   above; what is left to CSS is the part that was always CSS: how tall the strip is.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into an
   earlier block, and a parallel slice adds its own block after this one.
   ================================================================================================ */

/* The row's line box is pinned to MudBlazor's own default body line-height, which is exactly what these
   rows already inherited, so no row changes height. What it buys is arithmetic: a row becomes a KNOWN
   height, which is the only way the container below can promise "about six rows" rather than "however
   many happen to fit". flex-shrink is off for the same reason: these are the flex items of a column
   container that now has a bounded height, and a shrunk row is a row the height maths cannot predict.

   Measured, and it is the SLOT CHIP that sets the height, not the name: the chip's .66rem line box at
   1.43 is 15.1px and it carries 3px + 3px of its own padding, which is 21.1px, taller than the .82rem
   name cell's 18.8px. Add the row's own 4px + 4px and the 1px rule under it: 30.1px. The phone shrinks
   the NAME (.78rem) and not the chip, so a phone row is the same 30.1px, which is why one row constant
   serves both breakpoints below. */
.ff-room-recent-row {
    line-height: 1.43;
    flex: 0 0 auto;
}

/* The scroll region itself, holding the strip's shipped compact footprint: six rows from 600px and
   three below it, which is what the strip showed before it started scrolling.

   The + 4px is a deliberate sliver of the next row. A scrollbar is the desktop cue, but a phone's
   overlay scrollbar is invisible until a finger already moved, so a row cut off at the fold is the only
   cue a member gets that there is more history underneath.

   overscroll-behavior-y keeps a flick that reaches the end of the list inside the list, so scrolling
   the picks never scrolls the draft room out from under the member's thumb, and overflow-x:hidden
   guarantees the strip can only ever own a VERTICAL scroller: the row is a grid of minmax(0, ...)
   tracks with truncating cells, so it has nothing to scroll sideways, and the page keeps its width. */
.ff-room-recent-list {
    --ff-recent-row: calc(.66rem * 1.43 + 6px + 9px);
    max-height: calc(var(--ff-recent-row) * 6 + 4px);
    overflow-y: auto;
    overflow-x: hidden;
    overscroll-behavior-y: contain;
    scrollbar-width: thin;
}

/* Reachable from the keyboard (the markup carries tabindex and the label), so it has to be visible
   when it is focused. Offset outward, because an inset ring inside a scroller gets scrolled away. */
.ff-room-recent-list:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
    border-radius: 4px;
}

/* Three rows plus the same sliver, which is the height the phone strip has always had. Rows four
   onward are now under the fold instead of deleted, which is the whole point of the slice. */
@media (max-width: 599.98px) {
    .ff-room-recent-list {
        max-height: calc(var(--ff-recent-row) * 3 + 4px);
    }
}
/* ---- end BH-2 ---- */

/* ================================================================================================
   BH-3 (audit DX-10, §4.5): the chip legend, opened beside the board it explains.

   The legend moved out of the room's readiness strip and down to the Best available header, so the
   toggle is now next to the chips. That placement carries one obligation the top-of-page mount never
   had: opening it must not push the board off the screen. The legend's two sections run to roughly
   300px, which on a 360x640 phone is most of a viewport, and a member who taps "What do these mean?"
   to read a row and then cannot see any row has been answered into a corner.

   So the body is capped and scrolls itself, but only where it has to. The cap is a fraction of the
   VIEWPORT, so on a laptop 40vh is larger than the body ever gets and no scroller appears at all,
   while on a phone it keeps the Best available header and the first rows in the same screen as the
   definition. overscroll-behavior contains a flick that reaches the end, so reading the legend can
   never scroll the room out from under the member's thumb (the same rule BH-2's picks list uses).

   overflow-x is pinned to hidden for the reason BH-2's picks list pins it: a box that sets overflow-y
   computes overflow-x to auto as well, and this cap must only ever be able to own a VERTICAL scroller.
   Nothing inside it can overflow sideways in the first place (every legend row wraps and carries
   min-width:0), so this forecloses a sideways scrollbar rather than hiding content.

   Scoped to the intelligence card on purpose: the standalone legends on TeamHub, the Edge sheet and
   the practice board own a full page width and are unchanged. */
.ff-draft-intel .ff-chip-legend-body {
    max-height: 40vh;
    overflow-y: auto;
    overflow-x: hidden;
    overscroll-behavior-y: contain;
    scrollbar-width: thin;
}
/* ---- end BH-3 ---- */

/* ==========================================================================================
   UIDN-8 (Draft Experience Campaign 2): the recap's numerator caption.

   The one new rule this slice needs. It reads as the same quiet aside the lens line, the unfilled
   line and the projected line already are, so it sits at their weight rather than competing with the
   picks it explains; the shared selector above is left alone on purpose, because appending here is
   what keeps parallel slices merging cleanly. No width, no overflow and no nowrap: it is a paragraph
   that wraps, which is all a 360px column asks of it.
   ========================================================================================== */
.ff-recap-picks-note {
    font-size: .74rem;
    opacity: .65;
    line-height: 1.45;
    margin-top: 8px;
}
/* ---- end UIDN-8 ---- */



/* ================================================================================================
   TURN-1 — the compact turn line, and the Board roster it links to
   (Draft Experience campaign 2, audit §4.4 / owner decision Q18)

   The audit's constraint is the whole design: the next drafter is useful strategy context and is worth
   exactly ONE text fragment, not another vertical panel, avatar, countdown or mobile row. So there is no
   card here. The line is a wrapping flex row of small secondary text that sits under a segment's
   description, and the only thing it can grow is the member names inside it.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into an
   earlier block, and a parallel slice adds its own block after this one.
   ================================================================================================ */

/* The row wraps rather than scrolling: at 360px "On clock: Longteamname · Next: Otherlongname" does not
   fit on one line, and a second line of 12px text is cheaper than either truncating both names to
   nothing or letting the page grow a horizontal scroller. The names carry their own ellipsis below, so
   a single pathological name still cannot push the layout out. */
.ff-turn-status {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 6px;
    margin: -8px 0 16px;
    font-size: .8rem;
    line-height: 1.5;
    color: var(--mud-palette-text-secondary);
}

/* "On clock:" / "Next:" — the labels, deliberately quieter than the names they introduce. */
.ff-turn-status-key {
    opacity: .75;
}

/* The names. max-width is a percentage of the line rather than a fixed em count so the two names share
   the row proportionally at every width; the title attribute on each carries the full label, which is
   what makes the ellipsis accessible rather than lossy. */
.ff-turn-status-name {
    max-width: 45%;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
    font-weight: 600;
    color: var(--mud-palette-text-primary);
}

/* MudLink paints its own color; the next name is a link, and it should still read as the same kind of
   name as the one beside it rather than as a call to action. */
a.ff-turn-status-name {
    color: var(--mud-palette-primary);
}

.ff-turn-status-sep {
    opacity: .55;
}

/* "again" at a snake corner: an explanation, not a second name, so it stays at label weight. */
.ff-turn-status-again {
    opacity: .75;
    font-style: italic;
}

/* The Board panel an "Up next" link asked for. A ring rather than a fill, because the panel underneath
   already carries the member's roster and a wash would fight the slot chips inside it. */
.ff-board-member-focus {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
}
/* ---- end TURN-1 ---- */

/* ================================================================================================
   TURN-2 — the personal turn companion ("You pick in 4 picks · overall #16 · Round 2")
   Appended as its own tail block so parallel slices merge cleanly: nothing above is edited.
   ================================================================================================ */

/* Sits directly under TurnStatusLine on Board / My Team / Queue and under the on-clock banner in the
   Room, so it wraps on the same terms and carries the same quiet weight: this is a fact beside what the
   member is reading, not a second panel competing with it. The negative top margin pulls it up against
   the line above rather than opening a third gap between them. */
.ff-turn-companion {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 6px;
    margin: -10px 0 16px;
    font-size: .8rem;
    line-height: 1.5;
    color: var(--mud-palette-text-secondary);
}

/* The phrase a member reads first ("You pick in 4 picks"). Heavier than the coordinates beside it,
   because the distance is the decision and the ordinal is the detail. */
.ff-turn-companion-lead {
    font-weight: 600;
    color: var(--mud-palette-text-primary);
}

.ff-turn-companion-sep {
    opacity: .55;
}

/* "overall #16 · Round 2": exact, and deliberately quieter. tabular-nums keeps the ordinal from
   shifting the line's width as it counts up through a draft. */
.ff-turn-companion-detail {
    font-variant-numeric: tabular-nums;
    opacity: .85;
}

/* Inside the dashboard's draft alert and the Room's on-clock alert the line is one more row of an
   existing block, so it drops the margins it uses as a standalone strip. */
.mud-alert .ff-turn-companion {
    margin: 4px 0 0;
}
/* ---- end TURN-2 ---- */

/* ---- POOLS-3: per-game pool locks ----
   Appended block (parallel-slice merge convention). Two rules only: a row whose game has kicked off
   reads as settled rather than broken, and the lock line under it stays a quiet caption at 360px. */

/* A locked pick'em row. MudBlazor already dims the disabled control, so this only takes the CARD's
   emphasis down: the row is still readable (it is the member's committed pick) and no longer invites
   a tap. No layout properties, so the row's height and wrapping are unchanged. */
.pool-row--locked {
    opacity: .72;
}

/* The per-row countdown ("Locks in 2h 15m" / "Locked, this game has kicked off"). inline-flex so the
   lock glyph sits on the text baseline, and wrapping is allowed because at 360px a long matchup name
   above it has already used the width. */
.kickoff-lock {
    display: inline-flex;
    align-items: center;
    gap: .25rem;
    flex-wrap: wrap;
}

.kickoff-lock__ico {
    font-size: 1rem;
    opacity: .8;
}

/* Locked reads as settled, not as an error: the same secondary weight the caption around it carries. */
.kickoff-lock--locked {
    opacity: .85;
}
/* ---- end POOLS-3 ---- */


/* ================================================================================================
   UIDN-5 (Draft Experience Campaign, Wave J; audit DX-21, §2.18, §4.3, §4.7): the Room's wide-screen
   status and action grids.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits a rule above
   it; these rules place the Room's existing blocks from a later position in the cascade.

   THE DEFECT (owner direction 2026-08-28, from two live Week 0 captures at roughly 2000px content
   width). The Room is one full-width stack at every width: the on-clock banner, the roster strip, the
   recent-picks strip, the draft intelligence card and the pool-search card are five siblings in one
   column, and the stylesheet had no wide-screen placement rule for any of them. So a wide monitor
   spends most of every row on empty space, six recent-pick rows stretch ordinal to member across the
   whole screen under an equally wide alert, and the short search card lands BELOW the tall intelligence
   panel: a member who wants one specific player mid draft scrolls past the entire best-available board
   to reach the box. The mobile answer already existed (the sub-600px trim, and BH-2's scrolling
   history), which is why this is a placement gap and not a responsive defect.

   THE SHAPE. Two pairs share one two-column grid: the on-clock cell beside the recent picks, and the
   intelligence panel beside the pool-search card, both at about 2fr / 1fr and aligned start so the
   short search card does not stretch to the panel's height. Every other child spans both columns and
   keeps the full width it has today.

   NOTHING MOVES IN THE DOM (plan rejection R57). The razor source order is unchanged, which is what
   keeps the sub-960px reading order exactly as it ships; the pairs are PLACED by column. The status
   pair is additionally pinned to row 1, because the pick-result alert, the acting-team switcher and
   the roster strip all sit between the banner and the picks list in source order: sparse auto-placement
   walks a cursor that never moves backwards, so without an explicit row the picks list would land
   under the roster strip rather than beside the banner. The action pair needs no such pin, because
   those two cards ARE adjacent in source order and their columns run left to right.

   THE SURVIVOR RULE, driven by the razor-computed state classes rather than :has(), so a bUnit render
   can assert which shape the page asked for (the choice UIDN-4 made for My Team's wrap one slice
   earlier). A pair forms only when both halves rendered: no active draft means no on-clock cell, a
   week before its first pick means no picks list, and a complete, closed or waiting Room has no
   intelligence panel. In each of those states the survivor falls back to the full-width default below,
   because a half-width lone card beside empty space is the orphan shape audit §4.7 exists to avoid.

   Everything is inside the 960px query, so the phone and tablet stack is untouched at every width it
   has ever been read at. Every track is minmax(0, ...) and every paired item carries min-width: 0: a
   grid item's automatic minimum is its min-content width, and this Room holds two fixed-track grids
   (the board row and the picks row) that would otherwise push a column past its share and hand the
   PAGE a horizontal scrollbar, which is exactly what BH-7 is about to probe for.
   ================================================================================================ */

@media (min-width: 960px) {
    .ff-room-grid {
        display: grid;
        grid-template-columns: minmax(0, 2fr) minmax(0, 1fr);
        /* The short card must not stretch to its tall partner's height (audit §4.7). */
        align-items: start;
        /* Column gap only. The vertical rhythm still comes from the children's own mb-4 margins, so a
           full-width row sits exactly as far from its neighbour as it does today; a row-gap here would
           silently double every gap in the Room. */
        gap: 0 16px;
    }

    /* The default every child gets: the full width it has now. The four placement rules under it are
       the only things that opt anything out of it, which is what makes an absent partner degrade for
       free: no state class, no placement, and the survivor lands back here. */
    .ff-room-grid > * {
        grid-column: 1 / -1;
    }

    /* The status pair: the on-clock cell (banner + TURN-2's personal line) and the complete scrolling
       pick history beside it. */
    .ff-room-grid.has-onclock.has-recent > .ff-room-onclock {
        grid-column: 1;
        grid-row: 1;
        min-width: 0;
    }

    .ff-room-grid.has-onclock.has-recent > .ff-room-recent {
        grid-column: 2;
        grid-row: 1;
        min-width: 0;
    }

    /* The action pair: the intelligence panel and the search box that used to sit under it. */
    .ff-room-grid.has-intel > .ff-draft-intel {
        grid-column: 1;
        min-width: 0;
    }

    .ff-room-grid.has-intel > .ff-pool-card {
        grid-column: 2;
        min-width: 0;
    }

    /* The typeahead's suggestion list, in the narrower column it now opens in. MudBlazor renders the
       popover into the app-level MudPopoverProvider and restricts it to the anchor's width, so the list
       tracks the search column and can never widen the page. The option ROW is the part that needed
       this: the school/conference and value fragment is white-space:nowrap, and a flex item's automatic
       minimum is its whole min-content width, so a long conference name could give a roughly 270px
       dropdown a sideways scrollbar of its own. It truncates instead, the way the name beside it
       already does. Inside the query with everything else, because the column only gets narrow here;
       scoped by the Room's own popover class, so the Queue page's identical option row is untouched. */
    .ff-pool-popover .ff-pool-meta {
        min-width: 0;
        overflow: hidden;
        text-overflow: ellipsis;
    }
}
/* ---- end UIDN-5 ---- */

/* ================================================================================================
   TURN-3 - the live-draft dock, and the one bottom-action coordination rule

   The dock is the only thing in the app frame that is fixed to the BOTTOM of the viewport, which is
   why this block is two halves. The first styles the dock itself. The second is the coordination
   rule the campaign asked for (§9.4): every other bottom-anchored affordance in the product lifts by
   exactly the dock's height while a dock exists, so the scroll-to-top FAB, a snackbar, the point-type
   save bar, the framework's own error strip, and the last row of the page (the assistant's composer
   and the site footer among them) are never underneath it.

   HOW THE COORDINATION IS SCOPED, AND WHY THAT MATTERS. Every rule in the second half hangs off
   body:has(.ff-draft-dock). The dock renders no element at all with Features:DraftDockEnabled dark,
   with no live draft, or on a /draft route, so in each of those states nothing below matches and the
   layout is byte-identical to the one that shipped before this block existed. That is the flag's
   guarantee expressed in CSS rather than asserted in prose. :has() is the only selector that can
   reach the snackbar container, which the framework portals out to the document body, so it is used
   uniformly rather than mixing three mechanisms for one idea.

   360px FIRST (§9.4, checked in reasoning at 320 / 360 / 390 / 430). The dock declares no width and
   no min-width: left:0/right:0 makes it exactly as wide as the viewport at every one of those, and
   the pill inside is capped at 100% of that and wraps at its gaps. Its copy is short and numeric by
   construction ("Draft live", "4 picks away", "31:09", "Draft now"), so there is no member name or
   school here that could need an ellipsis. Both states clear the 44 to 48px touch target, and the
   bar reserves the iOS home-indicator inset rather than sitting under it.

   Appended as its own bannered tail block. app.css is append only, so nothing here edits into an
   earlier block, and a parallel slice adds its own block after this one.
   ================================================================================================ */

:root {
    /* The home-indicator inset on an iPhone, 0 everywhere else. Named once so the bar's own padding
       and the clearance every other affordance lifts by cannot drift apart. */
    --ff-dock-safe-bottom: env(safe-area-inset-bottom, 0px);
    /* The tallest state the dock can reach (a 48px target with 8px above and below it) plus a 12px
       breathing gap. One constant for both states: a clearance that changed as the dock changed
       state would make the page jump under the member's thumb every time a pick landed. */
    --ff-dock-clearance: calc(76px + var(--ff-dock-safe-bottom));
}

/* The fixed slot. It spans the viewport so the pill inside can centre itself, but it is transparent
   and click-through: only the link inside it takes a tap, so the bar never steals a press meant for
   the page behind it. */
.ff-draft-dock {
    position: fixed;
    left: 0;
    right: 0;
    bottom: 0;
    z-index: 1150;
    box-sizing: border-box;
    display: flex;
    justify-content: center;
    padding: 8px 12px calc(8px + var(--ff-dock-safe-bottom));
    pointer-events: none;
}

/* The waiting state: a compact pill, quiet enough to sit under a page a member is reading. */
.ff-draft-dock-link {
    pointer-events: auto;
    box-sizing: border-box;
    display: inline-flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: center;
    gap: 2px 8px;
    max-width: 100%;
    min-height: 44px;
    padding: 8px 18px;
    border-radius: 999px;
    border: 1px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-surface);
    color: var(--mud-palette-text-primary);
    font-size: .85rem;
    line-height: 1.3;
    text-decoration: none;
    box-shadow: 0 4px 14px rgba(0, 0, 0, .28);
}

.ff-draft-dock-link:hover {
    border-color: var(--mud-palette-primary);
}

/* The member's own turn: a prominent bar rather than a pill. It stretches to the slot, squares off,
   grows to the 48px target and takes the success accent the room's on-clock banner uses, so the two
   surfaces agree about what "you are up" looks like. */
.ff-draft-dock[data-dock-state="mine"] .ff-draft-dock-link {
    flex: 1 1 auto;
    justify-content: space-between;
    min-height: 48px;
    border-radius: 12px;
    border-color: var(--mud-palette-success);
    background: var(--mud-palette-success);
    color: var(--mud-palette-success-text);
    font-size: .95rem;
    font-weight: 600;
}

/* The live dot, in the same language as the app bar's ambient pill. It pulses only on the member's
   own turn, where the urgency is real. */
.ff-draft-dock-dot {
    flex: 0 0 auto;
    display: inline-block;
    border-radius: 50%;
    background: var(--mud-palette-info);
    width: 8px;
    height: 8px;
}

.ff-draft-dock[data-dock-state="mine"] .ff-draft-dock-dot {
    background: var(--mud-palette-success-text);
    animation: ff-draft-dock-pulse 1.6s ease-in-out infinite;
}

@keyframes ff-draft-dock-pulse {
    0%, 100% { opacity: 1; }
    50% { opacity: .35; }
}

@media (prefers-reduced-motion: reduce) {
    .ff-draft-dock[data-dock-state="mine"] .ff-draft-dock-dot {
        animation: none;
    }
}

.ff-draft-dock-lead {
    font-weight: 600;
}

.ff-draft-dock-sep {
    opacity: .55;
}

/* The distance to the member's next turn. Quieter than the phrase it follows: the distance is the
   fact, the phrase is the headline. */
.ff-draft-dock-detail {
    opacity: .85;
    font-variant-numeric: tabular-nums;
}

/* The counting clock. tabular-nums is not cosmetic here: without it the pill's width shifts every
   second as the digits change, which on a phone reads as the bar twitching. */
.ff-draft-dock-clock {
    font-variant-numeric: tabular-nums;
    font-weight: 700;
}

.ff-draft-dock-action {
    text-decoration: underline;
    text-underline-offset: 3px;
}

/* ---- the bottom-action coordination rule (§9.4) ---- */

/* The page's own last row used to be handled here, with padding-bottom on .ff-appshell .mud-main-content.
   That rule was REMOVED on 2026-09-16 (owner report, FOOT-1). The site footer is the last item inside
   the content area, so padding on the content area landed BELOW the footer as a strip of page
   background, and the owner reads a strip under the footer as the footer not being at the bottom of
   the page (the same call they made on the FAB on 2026-08-03: a slight overlap beats an empty band).
   Stacking a second bar's reservation the same way would have pushed the footer about 152px off the
   bottom of a phone screen. The clearance is now reserved INSIDE the footer's own padding instead, in
   the FOOT-1 block at the tail of this file, which clears the bar while the footer still reaches the
   bottom of the page. Everything the page puts above the footer, the assistant composer included, is
   above the footer's margin, height and padding and so clears the bar by more than it did before. */

/* The floating scroll-to-top FAB, lifted by the dock's height at each of its own two offsets so it
   keeps the spacing it was tuned to (see the #40 block above). */
body:has(.ff-draft-dock) .ff-scroll-top {
    bottom: calc(1.5rem + var(--ff-dock-clearance));
}

@media (max-width: 599.98px) {
    body:has(.ff-draft-dock) .ff-scroll-top {
        bottom: calc(1rem + var(--ff-dock-clearance));
    }
}

/* Snackbars. The container is portalled to the document body, which is why the whole coordination
   rule is written with :has() rather than a sibling selector: nothing inside the layout can reach
   it. Matched on the location fragment so every bottom placement is covered. */
body:has(.ff-draft-dock) [class*="mud-snackbar-location-bottom"] {
    padding-bottom: var(--ff-dock-clearance);
}

/* The point-type editor's save bar, the product's other bottom-anchored action. It is sticky on a
   desktop and fixed on a phone, and both forms resolve their offset against the same bottom edge the
   dock occupies. */
body:has(.ff-draft-dock) .ff-pt-savebar {
    bottom: var(--ff-dock-clearance);
}

/* The framework's own unhandled-error strip. It is hidden until something has gone badly wrong, and
   when it appears it must not be the thing hiding behind a draft bar. */
body:has(.ff-draft-dock) #blazor-error-ui {
    bottom: var(--ff-dock-clearance);
}
/* ---- end TURN-3 ---- */

/* ---- POOLS-4: attributed pool picks (2026-08-31) ----------------------------------------------
   Appended block (parallel-slice merge convention). One rule: the AUTO marker that rides a pick the
   opt-in safety net made. It lives here rather than in a scoped stylesheet because three surfaces
   render it (the survivor panel, the pick'em slate rows, and the leaderboard sub line), and a chip
   that means one thing must not be defined three times. */

/* Deliberately quiet: this is attribution, not a warning. An auto pick scores exactly like a member's
   own (D16), so it reads as a small neutral label rather than an alert colour, and it sits inline in a
   caption at 360px without forcing a wrap of its own. */
.pool-auto-chip {
    display: inline-block;
    font-size: .6rem;
    font-weight: 700;
    letter-spacing: .06em;
    line-height: 1.5;
    padding: 0 5px;
    margin-left: 5px;
    border-radius: 4px;
    white-space: nowrap;
    vertical-align: middle;
    color: var(--mud-palette-text-secondary);
    background: rgba(var(--mud-palette-text-secondary-rgb, 160, 160, 160), .18);
}
/* ---- end POOLS-4 ---- */


/* ================================================================================================
   TURN-4 - the draft-to-assistant loop, both directions

   Two affordances and one coordination rule. The Room's "Ask assistant" sits inside the pool-search
   card with the sentence that promises nothing is sent; the assistant's "Back to draft" sits above
   its panel with TURN-2's picks-away line beside it.

   THE COORDINATION RULE IS THE INTERESTING ONE. TURN-3's dock also carries a "Back to draft" verb
   while it is on the assistant, and two of the same instruction on one screen is worse than either
   alone. The page itself already stands the chip down when it knows the dock is up (its Suppressed
   parameter, which is where the cost saving lives: no chip means no personal turn read for a line
   nobody would see). This rule is the same guarantee expressed against the dock's OWN presence, the
   way every other bottom affordance in the block above is, so it also covers the moment where the two
   are still settling on whether a draft is live. With Features:DraftDockEnabled dark, with no live
   draft, or on a /draft route the dock renders no element, nothing matches, and the in-page chip is
   simply the only one there is, which is the state of every deployment until the flip.

   360px. Both rows are wrapping flex with no declared width, so the button drops onto its own line
   above its sentence rather than pushing the card sideways; the note is a normal-wrapping caption and
   the turn line beside the return button already wraps on its own terms (TURN-2). Both buttons are
   MudBlazor smalls, which clear the touch target the campaign named.

   Appended as its own bannered tail block. app.css is append only, so nothing above is edited and a
   parallel slice adds its block after this one.
   ================================================================================================ */

/* The Room's escape hatch, under the pool search. Wrapping so the promise sentence sits beside the
   button on a desktop card and under it on a phone. */
.ff-room-ask {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 2px 8px;
    margin-top: 8px;
}

/* The "nothing is sent" promise. A caption, because the button is the action and this is the thing
   that makes tapping it feel free. */
.ff-room-ask-note {
    font-size: .75rem;
    line-height: 1.5;
    color: var(--mud-palette-text-secondary);
}

/* The assistant's way back, above the panel. Same wrapping shape: the button and the picks-away line
   share a row where there is room and stack where there is not. */
.ff-draft-return {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 2px 8px;
    margin-bottom: 8px;
}

/* TURN-2's line is built as a standalone strip with margins that pull it up under a banner. Inside
   this row it is one of two things sharing a baseline, so it drops them. */
.ff-draft-return .ff-turn-companion {
    margin: 0;
}

/* The one coordination rule: while the dock is on screen it owns this verb. */
body:has(.ff-draft-dock) .ff-draft-return {
    display: none;
}
/* ---- end TURN-4 ---- */

/* ---- CHAT-1: the league room (2026-08-31) -----------------------------------------------------
   Appended block (parallel-slice merge convention). Everything here is scoped to .ff-chat-*, so it
   touches no existing surface. 360px is the design width rather than the fallback: members are going
   to read this on a phone during a draft, so the list is a single column at every width and the
   composer never puts its counter and its button on a line that can overflow. */

/* Owner round 2026-08-31 (post-#748): the conversation column. Message bars stretched the full width
   of a large monitor, and every affordance that once might have wanted the width (the pickers, the
   poll builder) stacks above the composer inside this same column now. 900px reads like a chat;
   smaller viewports are untouched because a max-width is inert below it.

   Owner round 2026-09-02: centered. A capped column pinned to the left edge left the right half of a
   wide monitor empty beside it; auto side margins put the conversation under the middle of the hero,
   and below 900px the margins collapse to zero so a phone sees no change. */
.ff-chat-shell {
    max-width: 900px;
    margin-left: auto;
    margin-right: auto;
}

.ff-chat-list {
    display: flex;
    flex-direction: column;
    gap: 6px; /* owner test round 2026-08-31: the room reads denser, so more of it fits one screen */
    /* A tall room scrolls INSIDE its own box, so the composer below stays reachable without a trip to
       the bottom of the document. The height is viewport-relative with a floor, so a short room does
       not reserve a screen of emptiness and a long one never grows the page. */
    max-height: min(60vh, 560px);
    /* Owner round 2026-08-31 (post-#748): a tall desktop window left dead space under the composer
       while the room clipped at 560px. The modern line lets the list absorb the viewport's spare
       height (viewport minus the app bar, hero, tabs and composer) up to a ceiling, while phones keep
       the 60vh floor they had; the line above stays as the fallback for engines without dvh. */
    max-height: min(max(60vh, calc(100dvh - 430px)), 960px);
    overflow-y: auto;
    padding: 4px 2px;
}

.ff-chat-row {
    border-radius: 10px;
    padding: 6px 10px; /* owner test round 2026-08-31: was 8px, part of the density pass */
    background: var(--mud-palette-background-gray, rgba(128, 128, 128, .08));
    border: 1px solid var(--mud-palette-lines-default, rgba(128, 128, 128, .25));
    /* The one rule that matters most on a phone: a long unbroken string (a pasted URL, a wall of
       characters) must wrap inside the bubble rather than widening the page. */
    overflow-wrap: anywhere;
    word-break: break-word;
}

/* The member's own messages, marked by weight rather than by a second column. A left/right split is
   the familiar chat idiom and the wrong one at 360px, where it halves the usable width of every line. */
.ff-chat-row--mine {
    border-color: var(--mud-palette-primary, #776be7);
}

.ff-chat-row__head {
    display: flex;
    align-items: center;
    gap: 8px;
    flex-wrap: wrap;
    margin-bottom: 0; /* owner test round 2026-08-31: density pass (was 2px under a 24px min-height) */
    min-height: 20px;
}

/* Owner test round 2026-08-31, density pass: the head's own delete/moderate icon buttons carried
   MudBlazor's default padding, which set the whole head's height. Smaller padding, same icons, same
   tap order; the buttons stay comfortably tappable because the head row is their whole hit area. */
.ff-chat-row__head .mud-icon-button {
    padding: 3px;
}

.ff-chat-row__who {
    font-size: .8rem;
    font-weight: 700;
    color: var(--mud-palette-text-primary);
}

.ff-chat-row__when {
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
}

/* The commissioner's authority badge (owner round 2, 2026-08-31): a small shield beside the name,
   amber for the owner, the theme's secondary for an admin. Sized to the head's cap height so it never
   grows the row, and carrying its words in title/aria rather than in the column 360px cannot spare. */
.ff-chat-row__role {
    font-size: .85rem;
    color: #d4af37; /* the rank-medal gold the standings already use for first place */
    flex: none;
}

.ff-chat-row__role[data-role="admin"] {
    color: var(--mud-palette-text-secondary);
}

/* Pushed to the trailing edge so it never sits between the name and the time, and it is the only
   thing in the row that may shrink to nothing. */
.ff-chat-row__del {
    margin-left: auto;
}

.ff-chat-row__body {
    font-size: .9rem;
    line-height: 1.4; /* owner test round 2026-08-31: density pass (was 1.45) */
    white-space: pre-wrap; /* a member's own line breaks are content */
}

/* A retracted or hidden message keeps its place in the room, quietly. Losing the row entirely would
   make the conversation around it read as a non sequitur. */
.ff-chat-row__gone {
    font-size: .85rem;
    font-style: italic;
    color: var(--mud-palette-text-disabled, var(--mud-palette-text-secondary));
}

.ff-chat-row__link {
    font-size: .8rem;
}

.ff-chat-composer {
    margin-top: 12px;
}

.ff-chat-composer__foot {
    display: flex;
    align-items: center;
    justify-content: space-between;
    gap: 8px;
    margin-top: 6px;
}

.ff-chat-composer__count {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums; /* the counter must not jitter the button as it counts */
}

/* The launch-day normal state, and it has to read as an invitation rather than as a failure: on the
   day chat is switched on, every league in the product is looking at this. */
.ff-chat-empty {
    display: flex;
    flex-direction: column;
    align-items: center;
    text-align: center;
    gap: 6px;
    padding: 28px 16px;
}

.ff-chat-empty__ico {
    color: var(--mud-palette-text-secondary);
    opacity: .7;
}

.ff-chat-empty__t {
    font-weight: 700;
    font-size: 1rem;
}

.ff-chat-empty__d {
    font-size: .85rem;
    color: var(--mud-palette-text-secondary);
    max-width: 46ch;
}
/* ---- end CHAT-1 ---- */


/* ================================================================================================
   BH-7 (Draft Experience Campaign, Wave J; audit DX-12 and the §7.4 protocol) — the one offender
   the mobile horizontal-overflow probe actually convicted.

   THE PROBE. Every Draft segment state (live room, first turn, legend open, loading, complete, no
   intel, waiting, board, my team, queue with four items) and every Assistant state (empty, markdown
   table answer, chart answer), plus the snackbar and the app frame itself, were rendered at 320, 360,
   390 and 430 CSS pixels and measured two ways: the document's own
   `scrollWidth - clientWidth`, and a walk of every visible element whose right edge passes the
   viewport (skipping anything inside a deliberate inner scroller, so `.ff-segtabs`, the picks list,
   the board and the markdown tables keep their own horizontal scrollers). Page markup came back clean
   at every width. Exactly one element failed, and it is app-frame chrome rather than page content.

   THE OFFENDER. The app bar's profile menu is the last item in a nowrap flex row and the only one
   carrying free text. `MemberName` resolves the member's TEAM name first (100 characters, server
   cap) and their display name second (60 characters), and nothing constrained either here, while
   MudBlazor puts `min-width: 64px` on the button and leaves the flex item at `min-width: auto` (its
   content's min-content width). So the item could not shrink:

     - a long SINGLE-TOKEN name has a min-content width as wide as the word, so the button ran clean
       off the right edge of a 320px viewport and took its dropdown caret, the only affordance for
       the profile / leagues / theme / logout menu, off screen with it;
     - a long MULTI-WORD name wrapped instead, to three lines, and spilled out of the bar's own
       height over the page beneath it.

   THE ROOT CAUSE is one missing constraint, and both symptoms come from it. Note that NEITHER shows
   up in `document.documentElement.scrollWidth`: the app bar is `position: fixed`, so it contributes
   nothing to the document's scrollable area and a page-scroll-only probe reports a clean page while
   the control is off screen. That is why §7.4 asks for the element walk as well as the delta.

   THE FIX mirrors the app bar's own precedent one control to the left: the "Wave 2 mobile polish
   (#54)" block above does exactly this for the league switcher's long league name, down to the
   wrapper span that gives `text-overflow` a single-line target. These rules reach MudBlazor
   internals, so like that block they are global rather than scoped, and they are scoped to
   `.ff-appbar-user` so the switcher, the notification bell and the drawer toggle are untouched.

   NOT a blanket `overflow-x: hidden` on a container, and no `overflow-x: clip` shell backstop:
   plan rejection R89 rules the first out, and the second was not needed because the convicted child
   is genuinely fixed. Nothing here can hide a future offender.
   ================================================================================================ */

/* The flex item, and MudBlazor's 64px button floor inside it. Without BOTH, the automatic minimum
   size keeps the item at its content width and it simply does not shrink. */
.ff-appbar .ff-appbar-user {
    min-width: 0;
}

.ff-appbar .ff-appbar-user.mud-button-root,
.ff-appbar .ff-appbar-user .mud-button-root {
    min-width: 0;
    max-width: 100%;
}

/* The label row holds avatar, name and caret. It must not wrap (that is the three-line spill) and it
   must be allowed to shrink so the name inside it is the part that gives way. */
.ff-appbar .ff-appbar-user .mud-button-label {
    min-width: 0;
    flex-wrap: nowrap;
}

/* The name itself. MemberName renders a bare text node, which as an anonymous flex item no rule can
   reach, so MainLayout wraps it in this span purely to give truncation something to bite on. The
   avatar keeps carrying the member's identity when the room runs out entirely. */
.ff-appbar-username {
    display: block;
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}
/* ---- end BH-7 ---- */


/* ================================================================================================
   CHAT-4: reaction chips (2026-08-31) ------------------------------------------------------------
   Appended block (parallel-slice merge convention). Everything here is scoped to .ff-chat-react* /
   .ff-chat-picker, so it touches no existing surface, CHAT-1's block included.

   360px is the design width, and it drives two decisions that would look arbitrary otherwise.

   ONE: the chip row and the glyph picker both WRAP. A message with six distinct reactions on a
   360px phone is a row that has to become two rows, and the only alternative to wrapping is a
   horizontal scroller inside a bubble that is itself inside the room's scroller, which is a
   gesture nobody wins.

   TWO: the "this is mine" state is BORDER AND BACKGROUND ONLY. No weight change, no size change,
   no extra glyph. Every one of those alters the chip's width, so lighting a chip would reflow the
   row it sits in and, at 360px, can push the chip after it onto the next line. A member tapping a
   reaction must see it light up, not see the row rearrange itself around their thumb.
   ================================================================================================ */

.ff-chat-reacts {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 4px;
    margin-top: 4px; /* owner test round 2026-08-31: density pass (was 6px) */
}

/* The chip. Sized by a min-height rather than a fixed one so a large system font grows it instead
   of clipping it, and laid out with the count in a tabular column so a tally going 9 to 10 does
   not shove its neighbours. Owner test round 2026-08-31: the 32px chip made every message a tall
   card, so the whole row shrank one notch (28px is still a real thumb target on a 6px-gapped row). */
.ff-chat-react {
    display: inline-flex;
    align-items: center;
    gap: 4px;
    min-height: 28px;
    padding: 2px 8px;
    border-radius: 14px;
    border: 1px solid var(--mud-palette-lines-default, rgba(128, 128, 128, .25));
    background: transparent;
    color: var(--mud-palette-text-primary);
    font: inherit;
    font-size: .8rem;
    line-height: 1;
    cursor: pointer;
}

.ff-chat-react:disabled {
    opacity: .5;
    cursor: default;
}

.ff-chat-react__e {
    font-size: .9rem; /* owner test round 2026-08-31: density pass (was .95rem) */
}

.ff-chat-react__n {
    font-variant-numeric: tabular-nums;
    font-weight: 600;
}

/* The member's own reaction. Colour and border, nothing that changes the box (see TWO above).

   The text colour is `primary`, deliberately NOT `primary-text`: that token is the colour for text on a
   SOLID primary surface (white), and this background is `primary-hover`, a translucent tint over
   whatever the page is. White on that tint is fine in dark mode and close to invisible in light mode.
   Primary on the tint reads in both, and it is the same token CHAT-1's own-message border already uses. */
.ff-chat-react--mine {
    border-color: var(--mud-palette-primary, #776be7);
    background: var(--mud-palette-primary-hover, rgba(119, 107, 231, .12));
    color: var(--mud-palette-primary, #776be7);
}

/* The add affordance is square rather than pill-shaped so it never reads as an empty tally, and it
   keeps the same height as the chips beside it so the row has one baseline. */
.ff-chat-react--add {
    padding: 2px 6px;
    min-width: 34px; /* owner test round 2026-08-31: density pass (was 40px), still a tap target */
    justify-content: center;
    color: var(--mud-palette-text-secondary);
}

/* The picker: eight targets, inline under the row rather than in a popover. An overlay at 360px
   covers the message being reacted to, which is the one thing the member is looking at. */
.ff-chat-picker {
    display: flex;
    flex-wrap: wrap;
    gap: 4px;
    margin-top: 6px;
    padding: 6px;
    border-radius: 10px;
    border: 1px solid var(--mud-palette-lines-default, rgba(128, 128, 128, .25));
    background: var(--mud-palette-background-gray, rgba(128, 128, 128, .08));
}

/* A real touch target: eight of these fit two rows at 360px with room to spare. */
.ff-chat-picker__b {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    min-width: 40px;
    min-height: 40px;
    padding: 0;
    border-radius: 8px;
    border: 1px solid transparent;
    background: transparent;
    font-size: 1.15rem;
    line-height: 1;
    cursor: pointer;
}

.ff-chat-picker__b:hover:not(:disabled) {
    border-color: var(--mud-palette-primary, #776be7);
}

.ff-chat-picker__b:disabled {
    opacity: .5;
    cursor: default;
}
/* ---- end CHAT-4 ---- */
/* ---- CHAT-3: chat moderation (2026-08-31) -----------------------------------------------------
   Appended block (parallel-slice merge convention), and appended AFTER CHAT-4's so the chain reads in
   the order the slices landed. Everything here is scoped to .ff-chat-row__mod*, so it touches no
   existing surface, CHAT-1's and CHAT-4's blocks above included.

   Two things need styling and neither is a member's normal view of the room: the marker a commissioner
   sees over a hidden message they are entitled to read, and the inline reason form. Both are stacked
   single-column at every width, because the row they live in is already the narrow column on a phone
   and a side-by-side layout there would put the reason box at about twelve characters wide. */

.ff-chat-row__mod-btn {
    /* Sits beside the delete button when both are present. Only the FIRST trailing control claims the
       auto margin, or the two would be pushed apart to opposite ends of the head row. */
    margin-left: auto;
}

.ff-chat-row__del + .ff-chat-row__mod-btn {
    margin-left: 0;
}

/* The commissioner's marker. Deliberately quiet rather than alarming: it explains the state of a row
   they are looking at, it is not a warning about the member who wrote it. */
.ff-chat-row__mod {
    display: flex;
    align-items: flex-start;
    gap: 6px;
    font-size: .78rem;
    line-height: 1.4;
    color: var(--mud-palette-warning, #ff9800);
    margin-bottom: 4px;
}

/* The reason, when there is one. Its own line so a long note never crowds the sentence above it, and
   it wraps like a body does: it is free text somebody typed. */
.ff-chat-row__mod-why {
    display: block;
    font-style: italic;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
    word-break: break-word;
}

.ff-chat-row__mod-form {
    margin-top: 8px;
}

.ff-chat-row__mod-actions {
    display: flex;
    justify-content: flex-end;
    gap: 8px;
    margin-top: 6px;
}
/* ---- end CHAT-3 ---- */

/* ==== CHAT-5: event-anchored system rows =====================================================
   A beat's row (a pick landing, the grades publishing, the week's high) is the LEAGUE talking, not a
   member. It needs to read as a different voice while staying the same object: still reply-able, still
   react-able, still moderatable, and still one bubble in one column. So the treatment is deliberately
   minimal and additive on top of .ff-chat-row rather than a second row style, which is how the two
   would drift.

   Everything below is scoped to .ff-chat-row--system, so it touches no member row and no other page. */

.ff-chat-row--system {
    /* Quieter than a member's bubble: flatter fill, dashed edge. A system row punctuates the
       conversation, it does not compete with it. */
    background: transparent;
    border-style: dashed;
    border-color: var(--mud-palette-lines-default, rgba(128, 128, 128, .25));
}

/* "League" reads as a label rather than as somebody's name, so it is set apart from an author's. */
.ff-chat-row--system .ff-chat-row__who {
    font-weight: 600;
    letter-spacing: .02em;
    text-transform: uppercase;
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
}

/* Platform copy is one sentence, never a member's own line breaks, so it wraps as prose. */
.ff-chat-row--system .ff-chat-row__body {
    white-space: normal;
    color: var(--mud-palette-text-primary);
}

/* The deep link is the point of a system row, so it gets its own line and a real tap target at 360px
   instead of trailing the sentence it belongs to. */
.ff-chat-row--system .ff-chat-row__link {
    display: inline-block;
    margin-top: 6px;
    min-height: 24px;
    font-weight: 600;
}
/* ---- end CHAT-5 ---- */

/* ==== CHAT-6: game-day threads ===============================================================
   Two things: the chat page's room switcher, and the Game Day page's way into the week's room.

   The switcher is a wrapping flex row of plain buttons rather than a tab component, and that is the
   whole 360px argument. A tab bar reserves a fixed track and grows a horizontal scroller when its labels
   do not fit, which on a phone means a member can end up with a room they cannot see. These wrap onto a
   second line instead, each one shrinks to its own text, and the unread badge rides inside the button so
   it can never be the thing that pushes the row over the edge.

   Everything below is scoped to its own classes and appends to the end of this file, so it touches no
   other surface and merges cleanly beside the other slices' tails. */

.ff-chat-threads {
    display: flex;
    flex-wrap: wrap;
    gap: 8px;
    margin: 0 0 10px;
}

.ff-chat-thread {
    display: inline-flex;
    align-items: center;
    gap: 6px;
    /* 36px plus the border clears the 44px target once the row's own gap is counted, and keeps two
       tabs plus a badge on one line at 360px. */
    min-height: 36px;
    padding: 6px 12px;
    border: 1px solid var(--mud-palette-lines-default, rgba(128, 128, 128, .25));
    border-radius: 999px;
    background: transparent;
    color: var(--mud-palette-text-secondary);
    font: inherit;
    font-size: .82rem;
    font-weight: 600;
    line-height: 1.2;
    cursor: pointer;
    /* A long week name is truncated rather than allowed to widen the strip past the viewport. */
    max-width: 100%;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

.ff-chat-thread:disabled {
    opacity: .6;
    cursor: default;
}

.ff-chat-thread--on {
    background: var(--mud-palette-primary);
    border-color: var(--mud-palette-primary);
    color: var(--mud-palette-primary-text);
}

/* The unread count on a room you are not in. Kept inside the button so the tap target is the whole
   thing, and sized off the text so it never dictates the row's height. */
.ff-chat-thread__n {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    min-width: 1.4em;
    padding: 0 .35em;
    border-radius: 999px;
    background: var(--mud-palette-primary);
    color: var(--mud-palette-primary-text);
    font-size: .72rem;
    font-weight: 700;
    line-height: 1.6;
}

/* Game Day's way into the week's room. Its own line under the ticker, because at 360px a chip appended
   to that row is the chip that wraps awkwardly on its own. */
.ff-gd-chat {
    display: flex;
    margin: 0 0 10px;
}
/* ---- end CHAT-6 ---- */

/* ==== CHAT-7: the labeled AI seed ============================================================
   The league's one opt-in weekly seed. It is an unowned row like a beat's, so it INHERITS the whole
   CHAT-5 system treatment (flat fill, dashed edge, label-cased author, prose wrapping) and this block
   only adds what makes it a different promise: a badge that says a model wrote it, and enough of an
   accent that the badge is not the only thing carrying that message.

   Everything below is scoped to .ff-chat-row--ai and .ff-chat-row__ai, so it touches no member row, no
   system row, and no other page. */

.ff-chat-row--ai {
    /* A single accent edge, on the side the eye already scans. Enough to read as "not one of us" at a
       glance on a phone, and nowhere near loud enough to outrank the members talking around it. The
       shorthand deliberately re-states the style, because the system rule above it dashes all four
       borders and this edge is the one that has to stay solid. */
    border-left: 3px solid var(--mud-palette-info, #2196f3);
}

/* The badge. Small, upper case, and set in the head row beside the author label so a member reads
   "League assistant AI" before they read the sentence, not after. */
.ff-chat-row__ai {
    display: inline-flex;
    align-items: center;
    flex: 0 0 auto;
    margin-left: 6px;
    padding: 0 6px;
    min-height: 16px;
    border-radius: 8px;
    border: 1px solid var(--mud-palette-info, #2196f3);
    color: var(--mud-palette-info, #2196f3);
    background: transparent;
    font-size: .62rem;
    font-weight: 700;
    letter-spacing: .08em;
    line-height: 1.5;
    text-transform: uppercase;
    /* The badge is a label, never a wrapping word: at 360px the head row is author, badge, time, and a
       badge that broke across two lines would push the timestamp off the row. */
    white-space: nowrap;
}

/* The commissioner card's second consent. Separated from the chat toggle above it by a rule rather than
   by spacing alone: they are two different permissions and the card must not read as one setting with a
   long caption. */
.ff-chat-seed-toggle {
    margin-top: 16px;
    padding-top: 12px;
    border-top: 1px solid var(--mud-palette-lines-default, rgba(128, 128, 128, .25));
}
/* ---- end CHAT-7 ---- */

/* ==== CHAT-8: the ambient unread badge ========================================================
   The app frame's "your league is talking" marker, in two placements off one service:

     .ff-chatunread-pill    - the app bar, beside the live-draft pill and the notification bell. The
                              word "Chat" from 600px up; below that the pill collapses to the count (or
                              the dot) alone so it cannot crowd the brand mark, the league switcher or
                              the user menu at 360px. Deliberately the SAME geometry as
                              .ff-livedraft-pill: two pills of different heights sitting next to each
                              other in the bar would read as an accident.
     .ff-chatunread-navdot  - the drawer, riding the Chat link's label the way the live dot rides
                              Draft's. Inline and small, so it can never wrap the link.

   Two states, and the difference is the whole product decision: a NUMBER means members said that many
   things, a DOT means the only new rows are the platform's own (a pick landing, the week's high, the
   opt-in seed). Both come from one palette variable, so light and dark are correct by construction.
   ============================================================================================ */

.ff-chatunread {
    display: inline-flex;
    align-items: center;
    flex: 0 0 auto;
}

/* The count. Sized off the text so it never dictates the height of whatever it is sitting in, and
   capped at "99+" in the component so it cannot grow the app bar either. */
.ff-chatunread-n {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    min-width: 1.5em;
    padding: 0 .4em;
    border-radius: 999px;
    background: var(--mud-palette-primary);
    color: var(--mud-palette-primary-text);
    font-size: .68rem;
    font-weight: 700;
    line-height: 1.6;
    white-space: nowrap;
}

/* The marker for "something landed, but nobody said it". Same size as the live-draft dot so the two
   signals in the same bar read as one family. */
.ff-chatunread-dot {
    width: 8px;
    height: 8px;
    border-radius: 50%;
    background: var(--mud-palette-primary);
    flex: none;
}

/* --- app-bar pill --- */
.ff-chatunread-pill {
    gap: 6px;
    height: 30px;
    padding: 0 11px;
    margin-right: 4px;
    border-radius: 999px;
    text-decoration: none;
    border: 1px solid rgba(255, 255, 255, .28);
    background: rgba(255, 255, 255, .10);
    color: inherit;
    font-size: .72rem;
    font-weight: 700;
    letter-spacing: .07em;
    text-transform: uppercase;
    white-space: nowrap;
    transition: background .15s, border-color .15s;
}

.ff-chatunread-pill:hover {
    background: rgba(255, 255, 255, .18);
    text-decoration: none;
}

/* Phone: the label goes, the signal stays. A 30px-tall target still clears the tap minimum beside the
   bell, and the bar keeps the layout it already had. */
@media (max-width: 600px) {
    .ff-chatunread-pill {
        padding: 0 8px;
        margin-right: 0;
    }

    .ff-chatunread-pill .ff-chatunread-label {
        display: none;
    }
}

/* --- nav-drawer marker --- */
.ff-chatunread-navdot {
    margin-left: 8px;
    vertical-align: middle;
}

/* The room's own tab strip gains the same two-state treatment, so a tab and the badge in the frame
   above it can never be saying different things about the same room. */
.ff-chat-thread__d {
    display: inline-block;
    width: 8px;
    height: 8px;
    border-radius: 50%;
    background: var(--mud-palette-primary);
    flex: none;
}
/* ---- end CHAT-8 ---- */

/* ==== FIX-CHAT: the two chat surfaces the campaign audit found geometry bugs on ================
   Appended as its own tail block, never edited into CHAT-6 or CHAT-8 above: app.css is append only, so
   a fix to an earlier slice's rule is an overriding rule down here where the cascade can see it and
   where parallel branches merge cleanly.

     1. The thread tab's truncation promise. .ff-chat-thread declares overflow/text-overflow, but it is
        a FLEX container, and text-overflow does nothing on one: it is inherited by the flex ITEMS,
        which are a label span and a badge span that have no rules of their own. A flex item's default
        min-width is auto, so the label refuses to shrink below its own text and the item that actually
        got clipped by the button's overflow was the UNREAD BADGE on the end. A long week name therefore
        cost a member the count the tab exists to show. The label is where the ellipsis belongs, so it
        gets the min-width:0 that lets it shrink and the rules that make it truncate; the badge and the
        dot are pinned out of the shrink entirely.

     2. The chat unread pill's phone geometry. .ff-livedraft-pill pins width:30px at 600px and below so
        the collapsed pill is a 30x30 round target beside the bell. Its twin dropped the label and the
        padding but never pinned the width, leaving roughly 24x30: the smallest tap target in the bar,
        and visibly not the circle sitting next to it. The CHAT-8 block says in so many words that the
        two are meant to be the same geometry, so this is the declaration that was missing rather than a
        new decision.
   ============================================================================================== */

.ff-chat-thread__t {
    /* The default min-width:auto is what stops a flex item shrinking below its content, so the
       ellipsis can never engage without this line. */
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

.ff-chat-thread__n,
.ff-chat-thread__d {
    /* The signal is the one thing on the tab that must never be the part that gets clipped. */
    flex: none;
}

@media (max-width: 600px) {
    .ff-chatunread-pill {
        /* The same 30px circle .ff-livedraft-pill collapses to, so the two signals in one bar are one
           family and both clear the tap minimum. */
        width: 30px;
        padding: 0;
        justify-content: center;
        margin-right: 0;
    }
}
/* ---- end FIX-CHAT ---- */

/* ================================================================================================
   CHAT-9: mentions, player tags, the poll ballot (2026-08-31) -------------------------------------
   Appended as its own tail block, after FIX-CHAT and never edited into CHAT-1/3/4/6/8 above:
   app.css is append only, which is what lets parallel slices merge and what puts a later slice's
   rules where the cascade can see them. Everything here is scoped to .ff-chat-mention*,
   .ff-chat-mentions*, .ff-chat-poll* and .ff-chat-row--at-me, so no existing surface changes.

   360px is the design width again, and it drives three decisions.

   ONE: a mention chip is INLINE and wraps with the sentence around it. It is not a pill with its own
   line and not a nowrap box: a chip that refuses to break puts a member's own long team name off the
   right edge of a 360px bubble, which is the exact class of overflow BH-7 convicted the app bar for.
   So it inherits the bubble's wrapping and only decorates.

   TWO: the picker is a SINGLE COLUMN that scrolls inside itself, and it sits ABOVE the composer.
   Above, because a software keyboard already owns the bottom of a phone screen and a list rendered
   under the box would open behind it. Its own scroller, because a roster plus six players is taller
   than the room is, and growing the page would push the box the member is typing in off screen.

   THREE: a poll option is a full-width button with the count pinned to the trailing edge. Not a grid
   and not a bar chart: at 360px an option's TEXT is the thing that needs the room, and a proportional
   bar would take a third of the line to say what a number says in two characters. The count column is
   tabular so a tally going 9 to 10 does not shove the option text.
   ================================================================================================ */

/* ---- the chips ---- */

.ff-chat-mention {
    /* Inline, so it flows and breaks with the sentence it is part of (see ONE above). */
    display: inline;
    border-radius: 4px;
    padding: 0 3px;
    font-weight: 600;
    color: var(--mud-palette-primary, #776be7);
    background: var(--mud-palette-primary-hover, rgba(119, 107, 231, .12));
    /* A long single-token name must break inside the bubble rather than widen it. */
    overflow-wrap: anywhere;
}

/* A mention of the member who is reading, and every @everyone. Colour only: nothing here changes the
   box, so lighting a chip can never reflow the line it sits in. */
.ff-chat-mention--me {
    color: var(--mud-palette-warning, #ff9800);
    background: var(--mud-palette-warning-hover, rgba(255, 152, 0, .12));
}

/* The player tag is a link, and reads as one without the underline that would fight the chip shape.
   The underline comes back on hover and on focus, so a keyboard member is never left guessing. */
.ff-chat-mention--player {
    text-decoration: none;
    cursor: pointer;
}

.ff-chat-mention--player:hover,
.ff-chat-mention--player:focus-visible {
    text-decoration: underline;
}

/* The row a message names you in. A ring plus a tint, deliberately a DIFFERENT colour from
   .ff-chat-row--mine (which is the primary border): "I wrote this" and "this is about me" are two
   different facts, and a member has to tell them apart at a glance in one scroll. */
.ff-chat-row--at-me {
    border-color: var(--mud-palette-warning, #ff9800);
    box-shadow: inset 0 0 0 1px var(--mud-palette-warning, #ff9800);
    background: var(--mud-palette-warning-hover, rgba(255, 152, 0, .08));
}

/* ---- the composer's picker ---- */

.ff-chat-mentions {
    display: flex;
    flex-direction: column;
    gap: 2px;
    margin-bottom: 6px;
    padding: 4px;
    border-radius: 10px;
    border: 1px solid var(--mud-palette-lines-default, rgba(128, 128, 128, .25));
    background: var(--mud-palette-surface, var(--mud-palette-background));
    /* Its own scroller (see TWO above): a long roster must never grow the page under the composer. */
    max-height: min(40vh, 280px);
    overflow-y: auto;
}

.ff-chat-mentions__o {
    display: flex;
    align-items: baseline;
    gap: 8px;
    width: 100%;
    /* Declared rather than inherited. This is a width:100% element with padding AND a border, so under
       content-box it is 18px wider than its parent and pushes the composer sideways at 360px. The
       stylesheet leans on MudBlazor's reset for this everywhere else, but MudBlazor 8 puts content-box
       back on some of its own inner elements (see the note above .mud-input-slot), so the two places in
       this block that would actually break are pinned rather than assumed. */
    box-sizing: border-box;
    min-height: 40px;
    padding: 6px 8px;
    border: 1px solid transparent;
    border-radius: 8px;
    background: transparent;
    color: var(--mud-palette-text-primary);
    font: inherit;
    text-align: left;
    cursor: pointer;
}

.ff-chat-mentions__o:hover:not(:disabled),
.ff-chat-mentions__o:focus-visible {
    border-color: var(--mud-palette-primary, #776be7);
}

.ff-chat-mentions__o:disabled {
    opacity: .5;
    cursor: default;
}

.ff-chat-mentions__n {
    font-size: .85rem;
    font-weight: 600;
    /* The name is the half that gives way when the row runs out, never the detail beside it: the
       detail is what tells two players with the SAME name apart. */
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

.ff-chat-mentions__d {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    margin-left: auto;
    flex: none;
}

.ff-chat-mentions__none {
    padding: 8px;
    font-size: .78rem;
    color: var(--mud-palette-text-secondary);
}

/* ---- the poll ---- */

.ff-chat-poll {
    display: flex;
    flex-direction: column;
    gap: 4px;
    margin-top: 2px;
}

.ff-chat-poll__q {
    font-size: .9rem;
    font-weight: 700;
    line-height: 1.45;
    overflow-wrap: anywhere;
}

.ff-chat-poll__o {
    display: flex;
    align-items: center;
    gap: 8px;
    width: 100%;
    /* The second of the two, and the same reason: width:100% plus padding plus a border. */
    box-sizing: border-box;
    min-height: 36px;
    padding: 6px 10px;
    border-radius: 8px;
    border: 1px solid var(--mud-palette-lines-default, rgba(128, 128, 128, .25));
    background: transparent;
    color: var(--mud-palette-text-primary);
    font: inherit;
    font-size: .85rem;
    text-align: left;
    cursor: pointer;
}

.ff-chat-poll__o:disabled {
    opacity: .5;
    cursor: default;
}

/* The member's own vote. Border and background only, the CHAT-4 rule: voting must not resize the row
   under the thumb that pressed it. */
.ff-chat-poll__o--mine {
    border-color: var(--mud-palette-primary, #776be7);
    background: var(--mud-palette-primary-hover, rgba(119, 107, 231, .12));
    color: var(--mud-palette-primary, #776be7);
}

.ff-chat-poll__i {
    flex: none;
    font-size: .95rem;
    line-height: 1;
}

.ff-chat-poll__t {
    /* The option text is what gets the room, and it wraps rather than truncating: an option a member
       cannot read in full is an option they cannot vote on. */
    flex: 1 1 auto;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-chat-poll__c {
    flex: none;
    font-variant-numeric: tabular-nums;
    font-weight: 600;
}
/* ---- end CHAT-9 ---- */

/* ================================================================================================
   CHAT-9R: the owner's refinement round on CHAT-9 (2026-08-31) ------------------------------------
   Appended as its own tail block after CHAT-9's, never edited into it: app.css is append only, which
   is what lets parallel slices merge and what puts a later slice's rules where the cascade can see
   them. Everything here is scoped to .ff-chat-mention*, .ff-chat-mentions*, .ff-chat-pollbuild* and
   .ff-chat-list, so no surface outside the league room changes.

   Three of the owner's six items are visible here.

   PLAYERS READ DIFFERENTLY FROM MEMBERS ("highlight players differently than users, that would
   distinguish quicker"). A member chip stays exactly the primary-hued chip CHAT-9 shipped; a player
   chip moves to the INFO family and grows a dotted underline at rest. Two changes rather than one,
   because hue alone is a colour-only distinction and the two facts being told apart ("somebody in my
   league" against "somebody playing on Saturday") are worth a second channel. It is deliberately NOT
   a leading glyph: the chip's text content is what a member copies out of a message, and the token
   grammar already keeps the label to the name that was said. @everyone keeps the member family,
   because it addresses the room rather than naming a player. The same split runs in the picker, so
   the list a member chooses from and the message it produces agree about what a player looks like.

   THE ROVING HIGHLIGHT ("on desktop we should be able to arrow over this list"). It has to be legible
   in dark mode, which is the default here, and it must not move anything: a highlight that changed a
   row's box would reflow the list under an arrow key. So it is a background, a left rail and a border
   colour, all inside the border the row already declares.

   THE POLL BUILDER stacks at 360px and never scrolls sideways. Its option rows are a flex row whose
   field takes every pixel the remove button does not, and the actions wrap.
   ================================================================================================ */

/* ---- the player chip, told apart from a member's ---- */

.ff-chat-mention--player {
    color: var(--mud-palette-info, #2196f3);
    background: var(--mud-palette-info-hover, rgba(33, 150, 243, .12));
    /* Reads as a link at rest without the solid underline that would fight the chip shape. The solid
       one still comes back on hover and on focus (CHAT-9's rule above, which still applies). */
    border-bottom: 1px dotted currentColor;
}

/* ---- the picker ---- */

/* The player rows in the list carry the same hue as the chip they produce, on the NAME only: the
   detail line beside it is secondary text everywhere else in this picker and stays that way. */
.ff-chat-mentions__o--player .ff-chat-mentions__n {
    color: var(--mud-palette-info, #2196f3);
}

/* The row Enter would take. Colour and a rail, never geometry. */
.ff-chat-mentions__o--on {
    border-color: var(--mud-palette-primary, #776be7);
    background: var(--mud-palette-primary-hover, rgba(119, 107, 231, .12));
    box-shadow: inset 3px 0 0 0 var(--mud-palette-primary, #776be7);
}

/* ---- the poll builder ---- */

.ff-chat-pollbuild {
    display: flex;
    flex-direction: column;
    gap: 6px;
    margin-top: 8px;
    padding: 8px;
    border-radius: 10px;
    /* Sized like the picker's rows, and for the same reason: it is a full-width box with padding and a
       border inside a column that is 360px wide on the device most members use. */
    box-sizing: border-box;
    width: 100%;
    border: 1px solid var(--mud-palette-lines-default, rgba(128, 128, 128, .25));
    background: var(--mud-palette-surface, var(--mud-palette-background));
}

.ff-chat-pollbuild__t {
    font-size: .8rem;
    font-weight: 700;
    color: var(--mud-palette-text-secondary);
}

.ff-chat-pollbuild__row {
    display: flex;
    align-items: center;
    gap: 4px;
    /* The field takes the room and the remove button takes what it needs, so an option row never grows
       a horizontal scroller of its own. */
    min-width: 0;
}

.ff-chat-pollbuild__row > .mud-input-control {
    flex: 1 1 auto;
    min-width: 0;
}

.ff-chat-pollbuild__x {
    flex: none;
}

.ff-chat-pollbuild__actions {
    display: flex;
    /* Wraps rather than scrolls: three buttons and a phone is exactly the width where one of them has
       to go to a second line. */
    flex-wrap: wrap;
    align-items: center;
    justify-content: flex-end;
    gap: 4px;
}

/* NOTHING IS DECLARED HERE FOR .ff-chat-list, and that is worth saying out loud. The scroll management
   this round adds needs the list to be a bounded box with its own overflow, and CHAT-1 already made it
   one (max-height plus overflow-y, tuned again in the owner's density pass). Re-declaring either from a
   tail block would silently outrank that tuning from the bottom of the cascade, which is exactly the
   failure an append-only stylesheet invites. The interop scrolls what is already there. */
/* ---- end CHAT-9R ---- */

/* ================================================================================================
   CHAT-10: replying to a message (2026-08-31) ----------------------------------------------------
   Appended as its own tail block after CHAT-9R's, never edited into it: app.css is append only,
   which is what lets parallel slices merge and what puts a later slice's rules where the cascade can
   see them. Everything here is scoped to .ff-chat-quote*, .ff-chat-replybar* and
   .ff-chat-row__reply-btn, so no surface outside the league room changes.

   THE QUOTATION IS ONE LINE AND STAYS ONE LINE. That is the whole geometry decision, and it is a
   360px decision rather than a taste one: the excerpt is already bounded on the server
   (LeagueChat.ReplyExcerptMaxLength, 90 characters), but 90 characters of a long word still overruns
   a phone column, so the block truncates with an ellipsis and never wraps. Two rules do that together
   and both are required: min-width: 0 on the flex child (a flex item's default min-width is auto,
   which refuses to shrink below its content and is the classic reason text-overflow does nothing),
   and overflow: hidden with text-overflow: ellipsis on the text itself.

   THE STRIP IS NOT A PANEL. It sits above the composer's one panel slot rather than inside it,
   because a member has to be able to open the mention picker or the poll builder while a reply is
   pending (Q11). Nothing here positions it absolutely or overlays anything: it is one more row in the
   composer's column, so a picker opening below it pushes nothing around.

   NO NEW COLOURS, NO HEX LITERALS. Both surfaces are built from theme tokens with rgba fallbacks, the
   way every other .ff-chat-* rule is, because dark mode is this product's default and a literal that
   reads in one theme is the standard way to fail the other.

   NOTHING IS DECLARED HERE FOR .ff-chat-list, .ff-chat-row OR .ff-chat-composer. The reply affordance
   rides the row's existing action line and the strip rides the composer's existing column, so both
   inherit the density pass rather than re-tuning it from the bottom of the cascade.
   ================================================================================================ */

/* The reply affordance. It joins the head row's existing icon buttons, so it takes the same padding
   the density pass gave them (.ff-chat-row__head .mud-icon-button, already declared above) and adds
   no height of its own. */
.ff-chat-row__reply-btn {
    flex: none;
}

/* ---- the quoted block ---- */

.ff-chat-quote {
    display: flex;
    align-items: center;
    gap: 6px;
    width: 100%;
    /* Padding and border sized IN, because MudBlazor 8 puts content-box back on some of its own inner
       elements and a width:100% box with padding is wider than its column under it. */
    box-sizing: border-box;
    margin: 0 0 4px;
    padding: 2px 6px;
    border: 0;
    border-radius: 6px;
    background: transparent;
    color: var(--mud-palette-text-secondary);
    font: inherit;
    font-size: .75rem;
    text-align: left;
    /* The quotation must never be wider than the row it sits in: an unbounded one is a second body. */
    min-width: 0;
}

/* The left rule, which is what makes the line read as a quotation rather than as a caption. Its own
   element rather than a border-left on the block, so the rule keeps its full height while the text
   beside it is the thing that ellipsizes. */
.ff-chat-quote__b {
    flex: none;
    align-self: stretch;
    width: 2px;
    min-height: 1em;
    border-radius: 2px;
    background: var(--mud-palette-lines-default, rgba(128, 128, 128, .45));
}

.ff-chat-quote__t {
    display: flex;
    align-items: baseline;
    gap: 5px;
    /* THE rule that makes the ellipsis work: a flex item defaults to min-width: auto, which refuses to
       shrink below its content, so without this the block widens the row instead of truncating. */
    min-width: 0;
    overflow: hidden;
    white-space: nowrap;
}

.ff-chat-quote__w {
    flex: none;
    font-weight: 700;
    color: var(--mud-palette-text-secondary);
}

.ff-chat-quote__x {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

/* A quotation whose target is loaded is a real button. It gets a pointer and a hover, and nothing that
   moves: a hover that changed the box would nudge the whole row under the finger. */
.ff-chat-quote--live {
    cursor: pointer;
}

.ff-chat-quote--live:hover,
.ff-chat-quote--live:focus-visible {
    background: var(--mud-palette-action-default-hover, rgba(128, 128, 128, .12));
}

/* ---- the composer's reply strip ---- */

.ff-chat-replybar {
    display: flex;
    align-items: center;
    gap: 6px;
    width: 100%;
    box-sizing: border-box;
    margin-bottom: 6px;
    padding: 4px 6px;
    border: 1px solid var(--mud-palette-lines-default, rgba(128, 128, 128, .25));
    border-radius: 8px;
    background: var(--mud-palette-background-gray, rgba(128, 128, 128, .08));
    font-size: .75rem;
    color: var(--mud-palette-text-secondary);
    min-width: 0;
}

.ff-chat-replybar__i {
    flex: none;
    font-size: 1rem;
}

.ff-chat-replybar__t {
    display: flex;
    align-items: baseline;
    gap: 5px;
    /* Same shrink-to-fit rule as the quotation above, for the same reason. */
    min-width: 0;
    overflow: hidden;
    white-space: nowrap;
}

.ff-chat-replybar__w {
    flex: none;
    font-weight: 700;
}

.ff-chat-replybar__x {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

/* The dismiss button keeps a real tap target at 360px, where it is the only way out of the strip that
   does not need a keyboard. */
.ff-chat-replybar__c {
    flex: none;
    margin-left: auto;
    min-width: 44px;
    min-height: 44px;
}
/* ---- end CHAT-10 ---- */

/* =================================================================================================
   CHAT-11: loading earlier messages

   Appended as its own commented tail block, per the parallel-slice merge convention, and scoped to the
   two elements this slice adds. It declares nothing about .ff-chat-list, .ff-chat-row or the composer:
   a tail block outranks everything above it, so re-declaring a surface somebody else owns is how the
   owner's density pass silently loses from the bottom of the cascade.

   BOTH ROWS ARE THE SAME HEIGHT, and that is a correctness rule rather than a tidiness one. The three
   states of this affordance (offered, in flight, the beginning of the room) all sit at the TOP of the
   scroller, above the prepend the member just asked for, and the restore arithmetic corrects their
   position by however much the list grew. A control that changed height when it swapped state would add
   its own few pixels to that growth and put the restore out by exactly that much, on every press. One
   min-height on both is the whole fix, and it is also the 44px tap target a thumb needs.
   ================================================================================================= */

.ff-chat-earlier {
    display: flex;
    align-items: center;
    justify-content: center;
    gap: 6px;
    /* A full-width ROW rather than a floating control: on a 360px column anything floating covers the
       conversation it is trying to reach. */
    width: 100%;
    /* Padding and border sized IN, because MudBlazor 8 puts content-box back on some of its own inner
       elements and a width:100% box with padding is wider than its column under it. */
    box-sizing: border-box;
    min-height: 44px;
    margin: 0 0 2px;
    padding: 4px 10px;
    border: 1px dashed var(--mud-palette-lines-default, rgba(128, 128, 128, .35));
    border-radius: 10px;
    background: transparent;
    color: var(--mud-palette-text-secondary);
    font: inherit;
    font-size: .8125rem;
    cursor: pointer;
    /* The label is one line whatever the column is: a wrapped affordance would change the list's height
       between renders, which is the thing the banner above is about. */
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

/* Colour only. A hover that resized the row would nudge the whole list under the finger that caused
   it, and this row in particular is the one every prepend is measured across. */
.ff-chat-earlier:hover:not(:disabled),
.ff-chat-earlier:focus-visible {
    background: var(--mud-palette-action-default-hover, rgba(128, 128, 128, .12));
}

.ff-chat-earlier:disabled {
    cursor: default;
    opacity: .7;
}

.ff-chat-earlier__s {
    flex: none;
}

/* The end state, and the honest one for a room shorter than a page. Muted and centred, and exactly as
   tall as the button it replaces. */
.ff-chat-begin {
    display: flex;
    align-items: center;
    justify-content: center;
    width: 100%;
    box-sizing: border-box;
    min-height: 44px;
    margin: 0 0 2px;
    padding: 4px 10px;
    color: var(--mud-palette-text-disabled, rgba(128, 128, 128, .7));
    font-size: .75rem;
    text-align: center;
}
/* ---- end CHAT-11 ---- */

/* =================================================================================================
   Phase 42 MU-6: the matchups slate (/research/matchups, plan §9.1, §9.3).

   Appended as its own commented tail block, per the parallel-slice merge convention, and it declares
   NOTHING about a surface another slice owns: every selector below is .ff-mu-*, on elements this page
   authors itself. MU-8 and MU-9 append their own blocks after this one, in that order.

   NO SCOPED CSS, deliberately (the standing trap, plan §10 Risk 9). Blazor CSS isolation only stamps
   its scope attribute on elements authored in the razor file, so a rule anchored on a MudBlazor
   component root silently never applies. Everything here is anchored on a plain element of ours.

   THE CARD IS A CARD ON A PHONE AND A ROW ON A DESKTOP, OUT OF ONE DOM. §9.1 asks for a four line card
   below 960px and aligned columns above it, because the sort controls are only worth reading against
   alignment. A second table rendering would define every cell twice and drift, which is the exact
   duplication ResponsiveList was built to end, so the card becomes a four track GRID at 960px instead:
   same markup, same order, same content, one place to change it. That is also why the bands element is
   emitted even when a game has no tag, since a card that dropped a child would slide its market column
   into the band column on that row alone.

   NO DIGIT WHERE A SIGNAL IS NOT LIVE is a razor rule rather than a css one, but the layout has to
   survive it: every line here is a wrapping flex row that collapses to nothing when its chips are
   absent, so a game with no line, no total, no tv and no forecast renders a short card and not a
   ragged one.
   ================================================================================================= */

/* ---- the controls row ---- */

/* Below 960px the toolbar folds and a toggle appears; above it everything is inline and the toggle is
   gone. The fold is POSITIONAL rather than by marker, which is the shipped /leaders mechanism: a
   MudSelect puts its Class one level in (on .mud-input-control) while the grid places its own root, so
   hiding the marker would blank the field and leave an empty cell holding its place. Sort is child one
   and is never folded, because a slate with no sort control is a slate with no controls. */
.ff-mu-filters-row { display: none; }

@media (max-width: 959.98px) {
    .ff-mu-filters-row { display: block; margin-bottom: 12px; }
    /* Flush left with the pickers above it, and a real touch target rather than a text sliver. */
    .ff-mu-filters-row .mud-button-root { margin-left: -8px; min-height: 36px; }

    .ff-mu-toolbar.ff-mu-collapsed { margin-bottom: 4px; }
    /* Tablet: sort and the first filter stay inline, the rest fold. */
    .ff-mu-toolbar.ff-mu-collapsed > *:nth-child(n+3) { display: none; }
}

@media (max-width: 599.98px) {
    /* Phone: the sort alone, and it takes the whole width rather than sitting in one half of the
       two-per-row grid it inherits from .ff-filter-grid with an empty cell beside it. */
    .ff-mu-toolbar.ff-mu-collapsed > *:nth-child(n+2) { display: none; }
    .ff-mu-toolbar.ff-mu-collapsed { grid-template-columns: minmax(0, 1fr); }
}

/* ---- the slate ---- */

.ff-mu-slate {
    display: flex;
    flex-direction: column;
    gap: 10px;
    margin-bottom: 16px;
}

.ff-mu-card {
    /* Padding and border sized IN: MudBlazor 8 puts content-box back on some inner elements, and a
       100% wide box with padding is wider than the column under it. */
    box-sizing: border-box;
    display: flex;
    flex-direction: column;
    gap: 6px;
    padding: 12px 14px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 14px;
    background: var(--mud-palette-surface);
    cursor: pointer;
    /* The whole card is the tap target, so it never falls under the 44px a thumb needs, even for a game
       with nothing but a kickoff on it. */
    min-height: 44px;
    /* A long school name gives before the page does: nothing here may produce a horizontal page scroll
       at 360px. */
    min-width: 0;
    overflow-wrap: anywhere;
    transition: background .15s, border-color .15s;
}

.ff-mu-card:hover,
.ff-mu-card:focus-visible {
    background: var(--mud-palette-action-default-hover, rgba(128, 128, 128, .08));
    border-color: var(--mud-palette-primary);
}

/* The card advertises role="link", so it has to look focused when it is. */
.ff-mu-card:focus-visible { outline: 2px solid var(--mud-palette-primary); outline-offset: 2px; }

/* ---- line one: who ---- */

.ff-mu-teams {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 8px;
    min-width: 0;
    font-size: .95rem;
    font-weight: 600;
}

.ff-mu-team { display: inline-flex; align-items: baseline; gap: 5px; min-width: 0; }

/* The conference is context, never the headline. */
.ff-mu-teams .cf {
    font-size: .68rem;
    font-weight: 500;
    color: var(--mud-palette-text-secondary);
    white-space: nowrap;
}

/* The word, never a dash (the hard copy rule). Muted, so the two school names read as the row. */
.ff-mu-at {
    font-size: .78rem;
    font-weight: 500;
    color: var(--mud-palette-text-secondary);
}

/* ---- line two: when, and on what ---- */

.ff-mu-when,
.ff-mu-bands,
.ff-mu-market {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 6px;
    min-width: 0;
}

/* CFBD has not timed this game yet. It says so in words rather than borrowing a midnight, and it is
   muted because it is an absence rather than a value. */
.ff-mu-tbd {
    font-size: .72rem;
    font-style: italic;
    color: var(--mud-palette-text-secondary);
}

/* The advisory forecast flag, in the two severities AnalyticsFormat already publishes. Colour is
   carried by palette tokens, and the label beside it says the same thing in words, so the chip is
   never colour alone. */
.ff-mu-wx .val { color: var(--mud-palette-warning); }
.ff-mu-wx.sev .val { color: var(--mud-palette-error); }

/* ---- line three: both sides' trap and boom read ---- */

.ff-mu-band { display: inline-flex; align-items: center; gap: 5px; min-width: 0; }

/* Which side the chip belongs to. Two chips with no owners is the ambiguity this label exists to
   remove; it ellipsizes rather than pushing the chip off a 360px row. */
.ff-mu-band .who {
    max-width: 11ch;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
}

@media (min-width: 600px) {
    .ff-mu-band .who { max-width: 18ch; }
}

/* ---- line four: the market, and who it expects to win ---- */

.ff-mu-pills { display: inline-flex; flex-wrap: wrap; gap: 6px; min-width: 0; }

/* One honest sentence in place of two empty pills. */
.ff-mu-nomarket {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

.ff-mu-wp { display: flex; flex-direction: column; gap: 3px; width: 100%; min-width: 0; }

/* Two sided, because the question is "who is expected to win" and a single fill answers only half of
   it. The halves are a percentage and its complement, so they always sum to a hundred and the bar can
   never render a gap that means nothing. */
.ff-mu-wp-bar {
    display: flex;
    width: 100%;
    height: 8px;
    border-radius: 999px;
    overflow: hidden;
    background: var(--mud-palette-lines-default);
}

.ff-mu-wp-bar .away { background: var(--mud-palette-secondary); }
.ff-mu-wp-bar .home { background: var(--mud-palette-primary); }

/* The numbers under the bar, and the caption that says what the bar IS. Colour is never the only
   carrier: each side is named in text beside its own figure. */
.ff-mu-wp-legend {
    display: flex;
    align-items: baseline;
    justify-content: space-between;
    gap: 8px;
    min-width: 0;
    font-size: .66rem;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
}

.ff-mu-wp-legend .away,
.ff-mu-wp-legend .home {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

.ff-mu-wp-legend .away { color: var(--mud-palette-secondary); }
.ff-mu-wp-legend .home { color: var(--mud-palette-primary); }

/* At 360px the caption is what gives: the two figures are the fact and the caption is only their
   label. It returns as soon as there is room. */
.ff-mu-wp-legend .cap { display: none; }

@media (min-width: 600px) {
    .ff-mu-wp-legend .cap { display: inline; }
}

.ff-mu-ask { margin-bottom: 16px; }

/* ---- 960px and up: the same card, aligned into columns ---- */

@media (min-width: 960px) {
    .ff-mu-card {
        display: grid;
        grid-template-columns: minmax(0, 2.1fr) minmax(0, 1.5fr) minmax(0, 1.2fr) minmax(0, 1.7fr);
        align-items: center;
        column-gap: 16px;
        row-gap: 0;
    }

    /* Each line becomes a cell, so a sort reads down a column instead of down a stack of cards. The
       four children are always present, which is what keeps a game with no tag from shifting its
       market column one track to the left.

       The teams cell stays a single wrapping line rather than stacking: "away at home" is the sentence
       a member reads, and breaking it into three stacked lines to save width would cost the reading to
       buy space the track already has. */
    .ff-mu-market { flex-direction: column; align-items: stretch; gap: 4px; }
}
/* ---- end Phase 42 MU-6 ---- */

/* =================================================================================================
   Phase 42 MU-8: the matchup game page (/research/matchups/{y}/{w}/{id}, plan §9.2, §9.3, §9.4).

   Appended as its own commented tail block after MU-6's, per the parallel-slice merge convention.
   MU-9 appends its own after this one (plan §6.0), so nothing here may be edited by a later slice.

   A DISTINCT PREFIX ON PURPOSE. MU-6 claimed .ff-mu-* for the slate, broadly. Everything this slice
   authors is .ff-mg-* ("matchup game"), so a tail block appended after that one cannot silently win
   a cascade against a selector it did not know about. Shared chrome is reused by its own shipped
   class (.ff-panel, .ff-ctx-chip, .ff-empty-state, .ff-research-note) and never redefined here.

   NO SCOPED CSS, deliberately (the standing trap, plan §10 Risk 9). Blazor CSS isolation only stamps
   its scope attribute on elements authored in the razor file, so a rule anchored on a MudBlazor
   component root silently never applies. Every selector below is on a plain element of ours.

   THE TWO TABLES SCROLL INSIDE THEMSELVES, AND NOTHING ELSE DOES (plan §9.3). A factor detail string
   ("Georgia D at the 92nd percentile") and a nine row metric pairing are the two things on this page
   that genuinely want more width than a 360px phone has. Each lives in its own .ff-mg-scroll, which
   is the ONLY element in this block carrying an overflow-x, so a long value scrolls its own table and
   can never push the page body sideways.

   COLOUR IS NEVER THE ONLY CARRIER. The factor rows are tinted by the shipped three bucket severity
   rule, and every one of them also prints the severity in a word beside the reading. The paired
   metric leader is a word too. Every colour is a MudBlazor palette token, so the theme the member
   picked is the theme this block paints in.
   ================================================================================================= */

/* ---- block 1: the header ---- */

/* Flush with the hero's own leading edge rather than indented into it. */
.ff-mg-back { margin-left: -8px; }

/* The two schools and the word between them, inside the hero's h1. It wraps rather than widening the
   band, and a long school name gives before the page does. */
.ff-mg-title {
    display: inline-flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 8px;
    min-width: 0;
    overflow-wrap: anywhere;
}

/* The word, never a dash (the hard copy rule). Muted and smaller, so the two school names read as the
   heading and the preposition reads as connective tissue. */
.ff-mg-at {
    font-size: .72em;
    font-weight: 500;
    color: var(--mud-palette-text-secondary);
}

/* ---- block 2: the context strip and the market ---- */

.ff-mg-ctx,
.ff-mg-market {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 6px;
    min-width: 0;
    margin-bottom: 8px;
}

/* CFBD has not timed this game yet. Words rather than a borrowed midnight, and muted because it is an
   absence rather than a value. */
.ff-mg-tbd {
    font-size: .74rem;
    font-style: italic;
    color: var(--mud-palette-text-secondary);
}

/* The advisory forecast flag, in the two severities AnalyticsFormat already publishes. The label beside
   it says the same thing in words, so the chip is never colour alone. */
.ff-mg-wx .val { color: var(--mud-palette-warning); }
.ff-mg-wx.sev .val { color: var(--mud-palette-error); }

/* One honest sentence in place of two empty pills. */
.ff-mg-nomarket {
    font-size: .74rem;
    color: var(--mud-palette-text-secondary);
}

/* The two sided win probability bar. The halves are a percentage and its complement, so they always sum
   to a hundred and the bar can never render a gap that means nothing. */
.ff-mg-wp {
    display: flex;
    flex-direction: column;
    gap: 3px;
    min-width: 0;
    margin-bottom: 12px;
}

.ff-mg-wp-bar {
    display: flex;
    height: 8px;
    border-radius: 999px;
    overflow: hidden;
    background: var(--mud-palette-lines-default);
}

.ff-mg-wp-bar .away { background: var(--mud-palette-secondary); }
.ff-mg-wp-bar .home { background: var(--mud-palette-primary); }

.ff-mg-wp-legend {
    display: flex;
    align-items: baseline;
    justify-content: space-between;
    gap: 8px;
    min-width: 0;
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
}

.ff-mg-wp-legend .away,
.ff-mg-wp-legend .home {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

.ff-mg-wp-legend .away { color: var(--mud-palette-secondary); }
.ff-mg-wp-legend .home { color: var(--mud-palette-primary); }

/* At 360px the caption is what gives: the two figures are the fact and the caption is only their
   label. It returns as soon as there is room. */
.ff-mg-wp-legend .cap { display: none; }

@media (min-width: 600px) {
    .ff-mg-wp-legend .cap { display: inline; }
}

/* ---- block 3: the seven factor read ---- */

/* Stacked on a phone, side by side once there is room for two readable columns. The plan's §9.3 asks
   for "both sides side by side" at 960px and that is exactly where two of these fit without either
   table starting to scroll on ordinary content. */
.ff-mg-factors {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    gap: 10px;
    margin-bottom: 16px;
}

@media (min-width: 960px) {
    .ff-mg-factors { grid-template-columns: minmax(0, 1fr) minmax(0, 1fr); }
}

.ff-mg-factorside {
    box-sizing: border-box;
    min-width: 0;
    padding: 10px 12px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 14px;
    background: var(--mud-palette-surface);
}

/* Which school this half is about, which slot it is, and its band chip. Two factor tables with no
   owners is the ambiguity this row exists to remove. */
.ff-mg-sidehead {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 6px;
    min-width: 0;
    margin-bottom: 6px;
}

.ff-mg-sidehead .who {
    min-width: 0;
    font-size: .9rem;
    font-weight: 700;
    overflow-wrap: anywhere;
}

/* The slot word ("away" / "home"), which is the declared column order made visible. */
.ff-mg-sidehead .slot {
    font-size: .64rem;
    font-weight: 600;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

/* Every explanatory sentence on the page: the evidence line, the insufficient reason, an empty block's
   own note, and the head to head coverage label. One treatment, so they all read as the same kind of
   line rather than four. */
.ff-mg-note {
    margin-bottom: 8px;
    font-size: .74rem;
    line-height: 1.45;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* ---- the two tables ---- */

/* THE ONLY overflow-x in this block. A long factor detail or a wide metric pairing scrolls its own
   table; the page body never moves. */
.ff-mg-scroll {
    overflow-x: auto;
    min-width: 0;
    -webkit-overflow-scrolling: touch;
}

.ff-mg-table {
    width: 100%;
    border-collapse: collapse;
    font-size: .74rem;
}

.ff-mg-table th,
.ff-mg-table td {
    padding: 5px 8px 5px 0;
    text-align: left;
    vertical-align: top;
    border-bottom: 1px solid var(--mud-palette-lines-default);
}

.ff-mg-table thead th {
    font-size: .62rem;
    font-weight: 600;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
    white-space: nowrap;
}

.ff-mg-table tbody tr:last-child th,
.ff-mg-table tbody tr:last-child td { border-bottom: 0; }

/* The row label: the factor or metric name, with its basis or direction under it. */
.ff-mg-table .nm { display: block; font-weight: 600; }

.ff-mg-table .bs {
    display: block;
    font-size: .64rem;
    font-weight: 400;
    color: var(--mud-palette-text-secondary);
}

.ff-mg-table .dt { display: block; overflow-wrap: anywhere; }

/* The severity word beside a factor's reading. It is what keeps the row's tint from being the only
   carrier of the same fact. */
.ff-mg-table .sv {
    display: block;
    font-size: .62rem;
    font-weight: 600;
    letter-spacing: .03em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

/* A factor whose input was not cached this week. Muted and italic: it is an ABSENCE, and it carries no
   severity tint at all, because an undefined severity painted as zero would read as the easiest thing
   on the board. */
.ff-mg-table .na {
    font-style: italic;
    color: var(--mud-palette-text-disabled, var(--mud-palette-text-secondary));
}

/* The three shipped severity buckets, as a leading edge rather than a fill, so the tint never competes
   with the text for legibility in either theme. */
.ff-mg-frow th[scope="row"] { border-left: 3px solid transparent; padding-left: 8px; }
.ff-mg-frow.hard th[scope="row"] { border-left-color: var(--mud-palette-error); }
.ff-mg-frow.mid th[scope="row"] { border-left-color: var(--mud-palette-lines-default); }
.ff-mg-frow.easy th[scope="row"] { border-left-color: var(--mud-palette-success); }
.ff-mg-frow.na th[scope="row"] { border-left-color: transparent; }

.ff-mg-frow.hard .sv { color: var(--mud-palette-error); }
.ff-mg-frow.easy .sv { color: var(--mud-palette-success); }

/* ---- block 4: the paired metrics ---- */

.ff-mg-teams { margin-bottom: 16px; }

.ff-mg-pairs .num { text-align: right; font-variant-numeric: tabular-nums; white-space: nowrap; }

.ff-mg-pairs .vl { display: block; font-weight: 600; }

/* Which side leads this row, under the row's own direction. The word is the fact; the weight and the
   colour are emphasis on top of it. */
.ff-mg-pairs .ld {
    display: block;
    font-size: .6rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-primary);
}

/* A tie is a RESULT and an absent value is not, so it is marked in the neutral tone rather than in the
   leader's. */
.ff-mg-pairs .ld.tie { color: var(--mud-palette-text-secondary); }

.ff-mg-pairs td.lead .vl { color: var(--mud-palette-primary); }

/* ---- block 7: the prior meetings ---- */

.ff-mg-h2h { margin-bottom: 16px; }

.ff-mg-meetings {
    list-style: none;
    margin: 0;
    padding: 0;
    display: flex;
    flex-direction: column;
    gap: 8px;
}

/* A wrapping row on a phone, an aligned four track row once there is room. Same DOM either way: a
   second rendering would define every cell twice and drift. */
.ff-mg-meeting {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 10px;
    min-width: 0;
    padding-bottom: 8px;
    border-bottom: 1px solid var(--mud-palette-lines-default);
    font-size: .78rem;
    overflow-wrap: anywhere;
}

.ff-mg-meetings .ff-mg-meeting:last-child { border-bottom: 0; padding-bottom: 0; }

.ff-mg-meeting .wk {
    font-size: .66rem;
    font-weight: 600;
    letter-spacing: .03em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
    white-space: nowrap;
}

.ff-mg-meeting .mt {
    display: inline-flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 6px;
    min-width: 0;
}

.ff-mg-meeting .sc { font-variant-numeric: tabular-nums; font-weight: 600; white-space: nowrap; }

.ff-mg-meeting .op { font-size: .7rem; }

@media (min-width: 600px) {
    .ff-mg-meeting {
        display: grid;
        grid-template-columns: auto minmax(0, 1fr) auto auto;
        align-items: baseline;
        column-gap: 12px;
    }
}

/* ---- block 8: the ask ---- */

/* Full width and a real thumb target on a phone, which is the shape every other ask row on the product
   already has. */
.ff-mg-ask { margin-bottom: 16px; min-height: 44px; }
/* ---- end Phase 42 MU-8 ---- */

/* =================================================================================================
   Phase 42 MU-9: the three lenses on the matchup game page (plan §4.4 blocks 4 to 6, §5.7, §9.3).

   Appended as its own commented tail block after MU-8's, which is the phase's declared tail order
   (§6.0: MU-6, then MU-8, then MU-9). Nothing above this line is edited by this slice.

   ITS OWN PREFIX. MU-6 claimed .ff-mu-* for the slate and MU-8 claimed .ff-mg-* for the game page.
   Everything this slice authors is .ff-ml-* ("matchup lens"), so a block appended last cannot win a
   cascade against a selector it did not know about, and every selector below names at least one
   .ff-ml- class. Shipped chrome (.ff-panel, .ff-ctx-chip, .ff-pos, .ff-research-note, .ff-segtab and
   MU-8's .ff-mg-note / .ff-mg-table) is reused BY ITS OWN CLASS and never redefined here.

   NOT ONE COLOUR IS SELECTED BY A NUMBER. The bands on this surface are painted entirely by the
   shipped chips: DvpBandChip and DvpGrid tint from DvpCopy.BandClass, SignalChip tints from
   SignalCopy.BandClass, and neither is restyled below. That is why there is no band token and no digit
   in any selector in this block: a rule that could be reached by a magnitude is how a thin sample gets
   coloured into confidence, and here there is no such rule to reach.

   NO OVERFLOW-X AND NO PIXEL WIDTH ANYWHERE IN THIS BLOCK. MU-8 owns the page's only two horizontal
   scrollers (its factor and metric tables, inside .ff-mg-scroll). Everything this slice adds wraps or
   stacks instead, which is what keeps 360px honest without a second scroll surface to get trapped in.

   ONE DOM AT EVERY BREAKPOINT. The player rows and the two defense grids get more columns as there is
   room, never a second rendering: MU-8's meeting row already recorded why (a second markup shape
   defines every cell twice and the two drift). Section 9.3 words the widest player arrangement as a
   table; this is that arrangement as a denser grid of the same cards, which is a deliberate reading.
   ================================================================================================= */

/* ---- the lens strip ---- */

/* The shared segmented control, placed. The three labels ("Team", "Position", "Players") are short by
   design and take the SHARED .ff-segtab phone sizing rather than a tightened one: at 360px the content
   column is about 328px and the strip spends 4px of padding a side plus two 4px gaps, so each segment
   gets about 104px, of which the shared rule spends 16px of padding, a 20px icon and a 4px gap. That
   leaves about 64px of label, and the longest of the three wants about 55px at .82rem. A longer word
   would ellipsize, which is why the labels are pinned by test against this arithmetic. */
.ff-ml-tabs { margin-bottom: 12px; }

/* ---- the weight column on MU-8's factor table (plan §9.3) ---- */

/* Folded away on a phone, where the factor and its reading are what 360px has room for, and back from
   600px. It is a share of a hundred, so it reads as a number and aligns as one. */
.ff-ml-wt {
    display: none;
    text-align: right;
    white-space: nowrap;
    font-variant-numeric: tabular-nums;
}

@media (min-width: 600px) {
    .ff-ml-wt { display: table-cell; }
}

/* ---- the lenses ---- */

.ff-ml-lens { margin-bottom: 16px; }

/* One card per direction, stacked on a phone and paired once there is room for two readable grids.
   960px is where the plan asks for side by side, and it is where two of these stop crowding. */
.ff-ml-dvp {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    gap: 10px;
}

@media (min-width: 960px) {
    .ff-ml-dvp { grid-template-columns: minmax(0, 1fr) minmax(0, 1fr); }
}

.ff-ml-side { min-width: 0; margin-bottom: 12px; }

.ff-ml-dvp .ff-ml-side { margin-bottom: 0; }

/* Whose defense this card is about, and who has to play against it. The second half is what makes two
   stacked cards unambiguous on a phone, where they are not side by side to compare. */
.ff-ml-sidehead {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 2px 8px;
    min-width: 0;
    margin-top: 12px;
}

.ff-ml-sidehead .who {
    min-width: 0;
    font-size: .9rem;
    font-weight: 700;
    overflow-wrap: anywhere;
}

.ff-ml-sidehead .sub {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* The signal grammar row, wherever a lens attaches one. It is the shipped pill row; this only places it. */
.ff-ml-grammar { margin-top: 4px; }

/* ---- the players lens: the ratified Q16 defense row ---- */

/* The league drafts a defense every week, so this row leads the side rather than trailing it, and the
   two stored opponent terms ride beside the opponent they are actually about. */
.ff-ml-defproj {
    box-sizing: border-box;
    min-width: 0;
    margin-bottom: 14px;
    padding: 10px 12px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 12px;
    background: var(--mud-palette-background);
}

.ff-ml-defhead {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 10px;
    min-width: 0;
}

.ff-ml-defhead .nm { font-size: .8rem; font-weight: 700; }

.ff-ml-defhead .pj {
    font-size: 1.02rem;
    font-weight: 700;
    font-variant-numeric: tabular-nums;
}

.ff-ml-defhead .rg {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
}

.ff-ml-terms {
    display: flex;
    flex-wrap: wrap;
    gap: 4px;
    min-width: 0;
    margin-top: 6px;
}

.ff-ml-term { font-variant-numeric: tabular-nums; }

/* ---- the players lens: one position group ---- */

.ff-ml-group { min-width: 0; margin-bottom: 14px; }

.ff-ml-grouphead {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 6px;
    min-width: 0;
    margin-bottom: 6px;
}

/* The shipped position token, given the horizontal padding it needs as an inline chip rather than as a
   full width cell of a roster grid. Nothing else about it is touched. */
.ff-ml-pos { padding-left: 7px; padding-right: 7px; }

/* "#3 stingiest vs WR", composed by DvpCopy so this page and the hubs read one phrase. */
.ff-ml-grouphead .rk {
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* One card per player at 360px, two once there is room. The card is the same DOM at every width. */
.ff-ml-rows {
    list-style: none;
    margin: 0;
    padding: 0;
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    gap: 8px;
}

@media (min-width: 700px) {
    .ff-ml-rows { grid-template-columns: minmax(0, 1fr) minmax(0, 1fr); }
}

.ff-ml-row {
    box-sizing: border-box;
    min-width: 0;
    padding: 8px 10px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 12px;
    background: var(--mud-palette-surface);
}

.ff-ml-rowhead {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 8px;
    min-width: 0;
}

.ff-ml-rowhead .nm {
    min-width: 0;
    font-size: .86rem;
    font-weight: 600;
    overflow-wrap: anywhere;
}

/* What the projection row actually reported, when it is not simply the bucket. */
.ff-ml-rowhead .ps {
    font-size: .62rem;
    font-weight: 600;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-ml-rowhead .pj {
    margin-left: auto;
    font-size: 1rem;
    font-weight: 700;
    font-variant-numeric: tabular-nums;
}

.ff-ml-row .rg {
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
}

.ff-ml-row .up {
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* The fold. A real thumb target, and it says how many rows it is about to reveal. */
.ff-ml-more {
    display: inline-flex;
    align-items: center;
    min-height: 44px;
    margin-top: 6px;
    padding: 0 10px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 999px;
    background: transparent;
    color: var(--mud-palette-primary);
    font: inherit;
    font-size: .74rem;
    font-weight: 600;
    cursor: pointer;
}

.ff-ml-more:hover { background: var(--mud-palette-action-default-hover); }

/* ---- the players lens: one player's opponent history ---- */

/* The other lens in the row. It is separated by a rule rather than by a colour, because the thing that
   makes it different is whose scoring it is, and the SignalChip row inside it is what says so. */
.ff-ml-hist {
    min-width: 0;
    margin-top: 6px;
    padding-top: 6px;
    border-top: 1px solid var(--mud-palette-lines-default);
}

.ff-ml-hist .ln {
    font-size: .72rem;
    line-height: 1.45;
    overflow-wrap: anywhere;
}

.ff-ml-hist .ln.sub { font-size: .66rem; color: var(--mud-palette-text-secondary); }

/* The fold's own honesty line, and the dark flag's, and a read that failed: one treatment, so all three
   read as the same kind of statement rather than as three different problems. */
.ff-ml-hist.note {
    font-size: .7rem;
    font-style: italic;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-ml-meets {
    display: flex;
    flex-wrap: wrap;
    gap: 4px 8px;
    min-width: 0;
    margin-top: 4px;
}

.ff-ml-meet {
    font-size: .66rem;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
    white-space: nowrap;
}

.ff-ml-buckets {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px;
    min-width: 0;
    margin-top: 5px;
}

.ff-ml-buckets .cap {
    font-size: .6rem;
    font-weight: 600;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-ml-bucket { font-variant-numeric: tabular-nums; }

/* The bucket this week's opponent falls into. A border weight, not a band tint: which bucket is
   UPCOMING is a fact about the schedule, and painting it in the band palette would read as a verdict
   about how hard it is. */
.ff-ml-bucket.up { border-color: var(--mud-palette-primary); }
/* ---- end Phase 42 MU-9 ---- */

/* =================================================================================================
   AF-1: the two chat tap targets the ratified reply matrix asked for (Phase 43 adversarial audit,
   2026-08-31).

   Appended as its own commented tail block after Phase 42 MU-9's, per the parallel-slice merge
   convention. Every selector below is one of the three this slice is about (.ff-chat-row__head,
   .ff-chat-row__reply-btn, .ff-chat-quote--live); nothing MU-6, MU-8 or MU-9 owns is touched, and
   nothing the owner's chat density pass tuned is re-declared.

   THE WHOLE PROBLEM IS "44px TARGET, NO NEW ROW HEIGHT" AT ONCE. §9's matrix words the reply
   affordance as "Icon only, on the row's existing action line, 44px target, no new row height", and
   the shipped button honours the first three clauses and not the third: a Size.Small icon under the
   density pass's 3px padding is about 26px square, sitting 8px from a Delete button of exactly the
   same size. That is the classic mis-tap pair, and it is the one members meet on a phone.

   So the growth goes into the BORDER box and comes straight back out of the MARGIN box. A flex line's
   height is set by its items' margin boxes, so a button whose border box is 44px and whose margins are
   -9px lays out in the same 26px it always did: the head does not move, the row does not grow, and the
   thumb gets the whole 44px. The one visible consequence is that the button's hover tint is now the
   size of its real target, which is the target made honest rather than a regression.

   THE HEAD IS RAISED SO THE EXPANSION CANNOT BE STOLEN. An expanded target overhangs its neighbours by
   construction, and the neighbour below the head is the quotation, which is itself a button. Giving the
   head its own stacking context settles the overlap once, in the direction that is always right: the
   row's own action buttons win every pixel they cover, and anything reaching up into them loses.

   THE QUOTATION USES AN OVERLAY RATHER THAN PADDING, and that is the one place the two surfaces differ.
   The quotation paints its own hover tint across its whole box, so growing its padding would paint a
   40px tint over the author line above it, which the CHAT-10 guard rightly forbids ("a hover that
   resized the block would nudge the whole row under the finger"). An inert absolutely positioned
   overlay adds no box, no paint and no layout at all: it is hit area and nothing else.

   360px: nothing here can produce a horizontal scroll. Neither rule adds a single pixel to any margin
   box, so the head lays out exactly as it did at every width, and the overlay is inset horizontally to
   its own element's edges and therefore cannot be wider than the column.
   ================================================================================================= */

/* Its own stacking context, so the row's action buttons are never overlapped by the expanded targets
   below them. Two properties added; the density pass's own declarations are left where they are. */
.ff-chat-row__head {
    position: relative;
    z-index: 1;
}

/* The 44px target. Specificity deliberately matches the density rule it has to outrank
   (.ff-chat-row__head .mud-icon-button { padding: 3px }), and this block is later in the cascade,
   which is what lets an equal-specificity rule win. */
.ff-chat-row__head .ff-chat-row__reply-btn {
    /* A Size.Small icon is 20px, so 12px a side is 44px square. */
    padding: 12px;
    /* And every added pixel given straight back: 12px asked for, 3px the density pass already spent. */
    margin: -9px;
}

/* The live quotation's own target. The block is about 22px tall (a .75rem line inside 2px of padding),
   which is a thin thing to hit on a phone even though it is full width. */
.ff-chat-quote--live {
    position: relative;
}

/* 9px above and below a 22px box is 40px, the house instinct for a secondary control, and it costs the
   layout nothing because an absolutely positioned overlay is out of flow. It is inset to zero
   horizontally because the block is already the full width of the row. */
.ff-chat-quote--live::after {
    content: "";
    position: absolute;
    inset: -9px 0;
}
/* ---- end AF-1 ---- */

/* =================================================================================================
   AF-4 (2026-08-31): the matchups slate's "Filters" toggle, retired over the range where it is inert.

   THE TOGGLE WAS A NO-OP AT TABLET WIDTH WITH THE BANDS DARK. The slate's control fold is positional,
   which is the shipped /leaders mechanism and the right one (a MudSelect puts its Class one level in,
   so hiding by marker would blank the field and leave an empty cell holding its place). The tablet
   rule folds from the THIRD control and the phone rule from the SECOND. With the research surfaces
   dark the band picker does not render at all, so the toolbar is down to two children: between 600px
   and 959px the toggle rendered, flipped its label between "Filters" and "Fewer filters", and moved
   not one pixel. A control that visibly does nothing teaches a member that the page is broken.

   WHY IT IS A STYLESHEET RULE AND NOT A RENDER CONDITION. Whether the toggle has anything to fold is
   a VIEWPORT question, and the page deliberately cannot see the viewport: below 600px the same two
   child toolbar folds its conference picker, so there the toggle still works and must stay. The razor
   states what it knows (the toolbar is down to two children, via .ff-mu-foldsphoneonly) and the
   breakpoint that owns the fold decides what that means, which is the same division of labour the
   fold itself already uses.

   Specificity: two classes, against the one class rule above that turns the row on below 960px, so it
   wins on specificity as well as on order. 360px: nothing here adds a box, a width or an overflow.
   Both themes: no colour is declared at all.
   ================================================================================================= */

@media (min-width: 600px) and (max-width: 959.98px) {
    .ff-mu-filters-row.ff-mu-foldsphoneonly { display: none; }
}
/* ---- end AF-4 ---- */

/* =================================================================================================
   AF-19 (2026-09-01): the Draft Order rows name the TEAM, with the account handle under it.

   THE ROW USED TO BE ONE LINE OF LOGIN HANDLE. The commissioner's reorder list printed the account
   username while the scoreboard, the standings and the chat beside it all say the league's team name,
   so the one page where a commissioner arranges their league was the one page that did not speak the
   league's vocabulary. The name is now resolved through the shared ladder and the username survives as
   the deliberate "@handle" metadata line beneath it, because matching a seat to an account is a real
   task on this page (and the row suppresses the handle whenever it would just repeat the name).

   WHY A COLUMN AND NOT A SECOND FLEX CHILD. .ff-do-row is a four-column grid and .ff-do-main is the
   third cell: avatar, then identity. Putting the handle beside the name would compete with the name
   for the one flexible column and push the row actions at 360px. Stacking them inside the existing
   cell adds no column and no width; min-width:0 on the stack is what keeps .ff-do-name's ellipsis
   working now that it is no longer a direct flex child.

   360px: the row's phone grid (20px 26px 1fr auto) is untouched, and both lines ellipsis rather than
   wrap, so a long team name cannot grow the row past one line each. Both themes: the handle takes the
   theme's own secondary text token, and no background or border is introduced.
   ================================================================================================= */

.ff-do-ident { display: flex; flex-direction: column; justify-content: center; min-width: 0; }
.ff-do-handle {
    font-size: .72rem; line-height: 1.3; color: var(--mud-palette-text-secondary);
    overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}
/* ---- end AF-19 ---- */

/* =================================================================================================
   PL-2 (2026-09-01): the survivor picker is the week's matchup list.

   THE PICKER USED TO BE A FLAT DROPDOWN OF SCHOOL NAMES. It was built by flattening the week's games
   into a sorted, distinct list, which threw away the one fact a survivor pick turns on ("who are they
   playing?") and, because the slate deliberately keeps FBS-hosts-FCS games, offered the FCS visitor as
   a pickable team. The row is now the GAME: a heading that names both sides with the kickoff and the
   line under it, and two buttons, one per side, with the unavailable ones disabled and labelled rather
   than hidden.

   WHY THE SIDES ARE THEIR OWN BLOCK. The heading and the two buttons on one flex row is the shape that
   overflows a phone, which is the same lesson POOLS-3 learned with the per-row lock line. The sides sit
   under the heading as a sibling block, so the two halves wrap independently.

   360px: the buttons go full width and stack, one side per line, so a long school name never has to
   share 328px with another one; the heading wraps its meta line under the matchup name; nothing here
   sets a fixed width, so the card cannot push the page sideways. Both themes: the only colour named is
   the theme's own secondary text token for the quiet meta and note text; the buttons take MudBlazor's
   own palette, and a disabled one takes MudBlazor's own disabled treatment.
   ================================================================================================= */

.pool-matchup__head {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: .1rem .5rem;
}

.pool-matchup__teams {
    font-weight: 600;
    line-height: 1.35;
}

/* Kickoff and line: informative, not competing with the matchup name above it. */
.pool-matchup__meta {
    font-size: .75rem;
    line-height: 1.35;
    color: var(--mud-palette-text-secondary);
}

.pool-matchup__sides {
    display: flex;
    flex-wrap: wrap;
    gap: .4rem;
    margin-top: .4rem;
}

/* flex-basis 0 so the two sides split the row evenly on a desktop column regardless of name length. */
.pool-matchup__sides > * {
    flex: 1 1 0;
    min-width: 0;
}

/* A school name is the button's payload and must never widen the card: it ellipsises instead. */
.pool-side__team {
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

/* "(used)" / "(kicked off)" / "(not FBS)": the reason the side is disabled, said quietly beside it. */
.pool-side__note {
    margin-left: .3rem;
    font-size: .7rem;
    text-transform: none;
    letter-spacing: normal;
    opacity: .85;
    white-space: nowrap;
}

@media (max-width: 599.98px) {
    /* One side per line. Two buttons plus a gap inside 328px is where a real school name starts
       truncating to nothing useful, so the phone gets the full width for each. */
    .pool-matchup__sides > * { flex: 1 1 100%; }
}
/* ---- end PL-2 ---- */

/* =================================================================================================
   PL-4 (2026-09-01): the pools surfaces on a phone.

   FROM THE OWNER'S PROD SCREENSHOTS AT 360 to 390px: the auto-pick toggle painted on top of the next
   panel's "Leaderboard" heading, every panel carried a collapse caret nobody asked for, and the cards
   were mostly padding.

   THE OVERLAP WAS ONE MECHANISM, NOT A Z-INDEX. AnalyticsPanel's MudCard is height:100%, a MudGrid
   item is stretched to its own flex line's height, and the auto-pick paper is a SIBLING of that card
   inside the same item. The item measured itself from card PLUS paper, the card then filled the item,
   and the paper had nowhere left to go but out the bottom, over whatever was stacked below it. Two
   changes retire it, both structural: a pools panel is PLAIN and sets no height at all (see
   AnalyticsPanel.Plain), and each column's children live in an .ff-pool-col of their own, so a
   percentage height resolves against auto and nothing is a loose sibling of a stretched item.

   THE CARETS ARE GONE RATHER THAN HIDDEN: the same Plain cascade drops the toggle from the header.
   On a page whose panels ARE the page, an affordance whose only job is to hide them is a way to lose
   them, and it sat one tap width from the title.

   360px: nothing here declares a width, the survivor slate stops being a nested scroller (the page is
   the scroller a thumb expects), and the leaderboard's second line WRAPS instead of ellipsising away
   the half of the row that says how someone is doing. Both themes: every value is a length or a
   MudBlazor palette token, and this block names no colour of its own.
   ================================================================================================= */

/* The column's own flow container: the panel card, the auto-pick card and the pick distribution in
   one stack with one gap. This is what makes the overlap structurally impossible at any width. */
.ff-pool-col {
    display: flex;
    flex-direction: column;
    gap: 12px;
}

/* The pick panel's body gutter. A class rather than pa-4 so the phone can spend 12px here without an
   !important fight with MudBlazor's own spacing utilities. */
.ff-pool-pad { padding: 16px; }

/* The cards that sit under a panel (auto-pick, pick distribution). No margin of their own: the
   column's gap above is what spaces them, and a margin would have stacked on top of it. */
.ff-pool-subcard { padding: 12px; }

/* Line the back arrow up with the left edge of the hero under it. MudButton's own text padding is
   what indents it, and 8px is exactly that padding. */
.ff-pool-back { margin-left: -8px; }

/* The survivor slate's scroll region is a DESKTOP device: with two columns, an uncapped twelve game
   slate makes the pick column twice the height of the board beside it. A phone has one column and
   the page itself already scrolls, so there is nothing to cap and a second scroller only traps the
   thumb. Mobile first: the phone gets no rule at all. */
@media (min-width: 600px) {
    .ff-pool-scroll { max-height: 420px; overflow-y: auto; }
}

/* Panel chrome at the density the Home page's own panels use (.ff-panel-head is 13px 16px), rather
   than MudCardHeader's 16px box. */
.ff-pool-detail .mud-card-header { padding: 13px 16px; }

@media (max-width: 599.98px) {
    .ff-pool-detail .mud-card-header { padding: 11px 12px; }
    .ff-pool-detail .mud-card-header .mud-typography-h6 { font-size: 1.05rem; line-height: 1.3; }
    .ff-pool-pad { padding: 12px; }
    .ff-pool-col { gap: 10px; }

    /* The pick'em slate's body gutter. Its panel is declared inside PickemPickPanel, a sibling
       slice's file, so the phone budget reaches it as a container rule here rather than as a class
       swap there. The !important is MudBlazor's own: every one of its spacing utilities carries one.
       Inert by design if that markup ever stops using pa-4. */
    .ff-pool-detail .mud-card-content .pa-4 { padding: 12px !important; }

    /* Join and empty states. Off season, no active week and not joined yet are the NORMAL states most
       of the year, so this is the panel body a member sees most often, not an edge case. */
    .ff-pool-detail .pool-join { padding: 24px 16px; }

    /* The stacked panels' vertical rhythm. MudGrid's spacing puts a desktop gutter between them,
       which a phone reads as 24px of nothing; the grid's matching negative margin moves with it. */
    .ff-pool-grid { margin-top: -16px; }
    .ff-pool-grid > .mud-grid-item { padding-top: 16px; }

    .ff-pool-detail .pool-hero { margin-bottom: 14px; }

    /* Leaderboard rows. minmax(0, 1fr) so the name column can genuinely shrink, and the second line
       wraps instead of ellipsising: "3 correct, this week: Boise State" is the row's whole point, and
       at 360px the nowrap version showed about four words of it. */
    .ff-pool-detail .pool-lb { padding: 4px; }
    .ff-pool-detail .pool-lb-row {
        grid-template-columns: 24px 32px minmax(0, 1fr) auto;
        gap: 8px;
        padding: 8px;
    }
    .ff-pool-detail .pool-lb-row .who .sub {
        white-space: normal;
        line-height: 1.35;
    }

    /* The hub's cards: same proportions, phone gutters. 18px of padding either side is a tenth of a
       360px card. */
    .ff-pool-hub .pool-grid { gap: 12px; }
    .ff-pool-hub .pool-card { padding: 14px 14px 13px; gap: 11px; }
    .ff-pool-hub .pool-card__stats { padding: 8px 6px; }
    .ff-pool-hub .pool-empty { padding: 28px 16px; }
}
/* ---- end PL-4 ---- */

/* ---- PL-6: the confidence pick'em row on a phone ----
   Appended block (parallel-slice merge convention). Owner screenshots at 360 to 390px showed the
   confidence rows cramped: the matchup rode the selector's floating LABEL, so it was clipped to that
   control's width ("West Georgia at Kennesaw St..."), and a narrow weight select sat beside it on the
   same line. The fix is structural rather than cosmetic. The matchup is its own line above the controls
   and wraps, so no school name is ever truncated; the two controls are proportional rather than pinned
   to pixel widths, so they divide whatever width there is; and below 600px each takes a full line of
   its own. Nothing here states a width in pixels, which is the point: the row has to work at 320px and
   at 1400px off the same rules. */

/* The scroll box the rows live in. A viewport fraction rather than a fixed height, so a phone is not
   scrolling a short window inside a short page. */
.ff-pickem-list {
    max-height: 65vh;
    overflow-y: auto;
}

/* The matchup, as a line the member reads before choosing. overflow-wrap so a long pair of school names
   wraps inside the card instead of widening it. */
.ff-pickem-row__matchup {
    font-size: .82rem;
    font-weight: 600;
    line-height: 1.35;
    margin-bottom: .35rem;
    overflow-wrap: anywhere;
}

.ff-pickem-row__controls {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: .5rem;
}

/* min-width 0 is what actually lets a flex child shrink: without it the select's own content sets a
   floor and the row overflows the card rather than reflowing. */
.ff-pickem-row__controls > * {
    min-width: 0;
}

/* sm and up: side by side, the winner taking three times the weight picker's share. flex-basis 0 so the
   split is the ratio and not the controls' natural widths. */
.ff-pickem-row__winner {
    flex: 3 1 0;
}

.ff-pickem-row__weight {
    flex: 1 1 0;
}

/* A comfortable tap target on every control in the row, at every width. A height, deliberately: the
   widths in this block are all relative and stay that way. */
.ff-pickem-row__controls .mud-input-control {
    min-height: 40px;
}

/* The action row under the list wraps as a group, so the submit button, the two weighting buttons and
   the progress line stack instead of running off the side of a phone. */
.ff-pickem-actions {
    row-gap: .5rem;
}

@media (max-width: 599.98px) {
    /* xs: one control per line. A winner select and a weight select plus a gap inside 328px of usable
       width is where the selector starts clipping the team it is showing. */
    .ff-pickem-row__winner,
    .ff-pickem-row__weight {
        flex: 1 1 100%;
    }
}
/* ---- end PL-6 ---- */

/* ---- PL-7: the confidence pick'em slate on a desktop, and a leaderboard that cannot be widened ----
   Appended block (parallel-slice merge convention).

   WHY THIS SUPERSEDES PL-6'S TWO FLEX RULES RATHER THAN EDITING THEM. From the owner's 1526px
   screenshot: every row's winner select was a different width, the weight label landed at a different x
   on each consecutive row, and a two digit number was given roughly a third of the page. PL-6 asked for
   `flex: 3 1 0` / `flex: 1 1 0`, and neither ever applied, because a Class on a MudSelect is written
   onto the `.mud-input-control` element two levels down while the box that actually participates in the
   row's layout is MudBlazor's own `.mud-select` wrapper (`display:flex; flex-grow:1`, auto basis). A
   grow of 1 with a content basis is exactly what was on screen: each winner sized to its own team names
   and the remainder split evenly. MudStack made it unfixable from here as well, since it renders the
   d-flex utility and that is `display:flex !important`. So the markup now wraps each control in a div
   this file's slice owns, and those wrappers carry the classes below; PL-6's two flex declarations
   survive on the same class names but are inert, because a grid item is not a flex item.

   THE ROW IS A GRID, WHICH IS WHAT MAKES COLUMNS LINE UP. Every row's container is the same width, so a
   named track is the same width on every row, which flex ratios over content-sized bases can never
   promise. xs keeps PL-6's one-control-per-line. sm and up puts the two controls side by side with the
   weight on a narrow fixed track, the matchup still on its own line above. 1280px and up folds the
   matchup into the same grid: one line per game, so a 91 game slate reads as a table rather than as 91
   stacked cards, and the card chrome steps down to a hairline rule for the same reason. That last
   breakpoint is deliberately NOT MudBlazor's md, for the reason stated above the rule itself.

   Both themes: every colour here is a MudBlazor palette token and this block names none of its own. */

/* The row card. Padding and rhythm live here rather than on MudBlazor's pa-2 / mb-1 utilities, so the
   widest breakpoint can take the row down to a table line without an !important fight with them. */
.ff-pickem-row {
    padding: 8px;
    margin-bottom: 4px;
}

/* xs: one control per line, which is PL-6's phone contract restated as a single-column grid. */
.ff-pickem-row__controls {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    align-items: center;
    gap: .5rem;
}

/* A grid item's automatic minimum size is its content, so without this a long team name would push its
   own column wider than the track it was given and the row would overflow the card. */
.ff-pickem-row__controls > * {
    min-width: 0;
}

@media (min-width: 600px) {
    /* sm and up: winner takes the remainder, the weight takes a narrow fixed column. A two digit number
       needs a two digit box, and a fixed track is the only thing that makes the SAME box appear on every
       row. Straight and ATS slates carry no weight control, so they keep the single column. */
    .ff-pickem-row--weighted .ff-pickem-row__controls {
        grid-template-columns: minmax(0, 1fr) 7.5rem;
    }
}

/* 1280px, NOT MudBlazor's md, and the number is measured rather than chosen. The one-line row is a
   claim about the pick COLUMN's width, and that column is five twelfths of the page: at md it is only
   about 414px, and three columns inside 414px leave the winner select 133px, which clips a school name
   on every row that has a real one.

   1280px is the first width at which the one-line winner slot clears the LONGEST names the pool can put
   in it with room to spare. Measured, the slot is 160px there and the widest name the slate can hold is
   "Southern Mississippi" at 144px, with "North Carolina State" 141px and "Florida International" 140px
   behind it: 16px of headroom on the worst case. The obvious cheaper number, 1220px, is NOT this. It is
   the bare threshold, 145px of slot against that same 144px name, and a one pixel margin is not a
   margin once a different font stack, a browser's own metrics or a page zoom shifts the text by half a
   percent. 16px survives that; 1px is a coin toss dressed up as a fix.

   The consequence, stated once so nobody has to rediscover it: this number is a function of the slot,
   and the slot is what the row's other tracks leave over. A wider weight track, a larger control font,
   a third control in the row, or a longer name in the data all eat the headroom and move this
   breakpoint with them. It is one number in one place for exactly that reason, and nothing else in this
   block encodes it.

   Below 1280px the sm two-line layout applies unchanged, matchup above with winner and weight side by
   side, and there the winner has the whole column rather than a share of it. Measured at 1024px that is
   a 238px cell with a 191px text slot, which clears every FBS name with room to spare. So the band this
   breakpoint hands back is not a compromise; it is the wider box.

   The density rules travel WITH the one-line layout rather than staying at md, because the argument for
   them is the same argument: a hairline instead of a card is what makes a list of ROWS readable, and a
   row is what this breakpoint creates. Below it a game is two lines, which is a card, and it keeps the
   card's chrome. One breakpoint, one story. */
@media (min-width: 1280px) {
    /* The whole row on one line. The matchup is the grid's first track, so the controls box hands its
       children up (display: contents) instead of being a single cell holding both.

       The winner gets the LARGER of the two flexible tracks (1 : 1.5), which looks backwards until you
       remember what each one holds. The matchup is a wrapping line of prose and loses nothing by taking
       two lines; the winner is a MudSelect, and a select that runs out of room ellipsises the school
       name it is showing. So the track that cannot wrap gets the room. */
    .ff-pickem-row__main {
        display: grid;
        grid-template-columns: minmax(0, 1fr) minmax(0, 1.5fr);
        align-items: center;
        column-gap: .5rem;
    }

    .ff-pickem-row--weighted .ff-pickem-row__main {
        grid-template-columns: minmax(0, 1fr) minmax(0, 1.5fr) 7rem;
    }

    .ff-pickem-row__controls {
        display: contents;
    }

    /* The matchup is beside the controls now, not above them. */
    .ff-pickem-row__matchup {
        margin-bottom: 0;
    }

    /* Rows, not tiles. A shadow per game is 91 shadows, and the list reads as a stack of cards the eye
       has to re-enter for each one; a hairline rule is what a table gives you instead. Two classes deep
       so it outranks MudPaper's own elevation and radius without an !important. */
    .ff-pickem-list .ff-pickem-row {
        box-shadow: none;
        border-radius: 0;
        border-bottom: 1px solid var(--mud-palette-lines-default);
        padding: 6px 8px;
        margin-bottom: 0;
    }

    .ff-pickem-list .ff-pickem-row:last-child {
        border-bottom: 0;
    }
}

/* The pool detail page's panel headers. The tiebreak sentence is commissioner-written free text, and it
   is rendered inside MudBlazor's .mud-card-header-content, which is `flex: 1 1 auto` with no min-width
   of its own: one long unbroken token (a URL, a run-on word) therefore sets a minimum the header cannot
   shrink below, and the card, the column and the page scroll sideways behind it. min-width 0 lets the
   box shrink and the wrap rule lets the token itself break, so no sentence anyone can type widens the
   leaderboard column. A reach-in container rule because the header is AnalyticsPanel's markup, shared
   with dozens of surfaces this slice has no business restyling. */
.ff-pool-detail .mud-card-header .mud-card-header-content {
    min-width: 0;
}

.ff-pool-detail .mud-card-header .mud-card-header-content .mud-typography-caption {
    overflow-wrap: anywhere;
}
/* ---- end PL-7 ---- */

/* ---- DO-1: the pre-draft draft-order strip ------------------------------------------------------
   A compact row of numbered seats, shown inside the dashboard's scheduled-start card and under the
   draft room's scheduled-start panel while the draft has not started.

   The one rule that matters here is that the chips WRAP. A nine-member league at 360px cannot fit nine
   names on a line, and the strip lives inside a MudAlert whose content box will happily be widened by
   an unbreakable row, taking the whole panel (and the page behind it) into a sideways scroll. So the
   container is a wrapping flex, and every chip is allowed to shrink and to break its own name, which is
   commissioner- and member-supplied text and can be arbitrarily long. On a desktop the same rules leave
   the row on one line whenever it fits, because wrap only engages when it does not. */
.ff-order-strip {
    margin-top: 8px;
}

.ff-order-summary {
    margin-bottom: 4px;
}

.ff-order-chips {
    display: flex;
    flex-wrap: wrap;
    gap: 4px 6px;
    align-items: center;
    /* A flex ITEM defaults to min-width:auto, so a long name would set a floor the strip cannot shrink
       below even with wrap on. This is the other half of the 360px promise. */
    min-width: 0;
}

.ff-order-chip {
    display: inline-flex;
    align-items: baseline;
    gap: 4px;
    min-width: 0;
    max-width: 100%;
    padding: 2px 8px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 999px;
    font-size: 0.78rem;
    line-height: 1.5;
    background-color: var(--mud-palette-background-gray);
}

.ff-order-chip.me {
    border-color: var(--mud-palette-primary);
    background-color: var(--mud-palette-primary-hover);
    font-weight: 600;
}

.ff-order-chip-pos {
    flex: 0 0 auto;
    font-variant-numeric: tabular-nums;
    font-weight: 600;
    opacity: 0.7;
}

.ff-order-chip-name {
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-order-chip-you {
    flex: 0 0 auto;
    font-size: 0.68rem;
    text-transform: uppercase;
    letter-spacing: 0.04em;
    color: var(--mud-palette-primary);
}

.ff-order-note {
    display: block;
    margin-top: 4px;
}

.ff-order-chip-skeleton {
    border-radius: 999px;
}
/* ---- end DO-1 ---- */

/* ---- DO-1 addendum: the draft room's read-only queue list --------------------------------------
   Sits inside the pool card, under the search box: the narrow right-hand column on a wide screen, and
   directly below the add box on a phone. Rows must WRAP rather than truncate. An athlete's name plus a
   position plus a school does not fit one 360px line in a column that is already the narrow half of the
   grid, and the alternative to wrapping is an ellipsis that hides the school, which is the one thing
   distinguishing two athletes who share a name. So the row is a wrapping flex whose rank column stays
   fixed and whose name and meta are each allowed to shrink and break. */
.ff-room-queue {
    margin-top: 12px;
    padding-top: 10px;
    border-top: 1px solid var(--mud-palette-lines-default);
}

.ff-room-queue-head {
    display: flex;
    align-items: baseline;
    justify-content: space-between;
    gap: 8px;
    flex-wrap: wrap;
    margin-bottom: 4px;
}

.ff-room-queue-list {
    list-style: none;
    margin: 0;
    padding: 0;
}

.ff-room-queue-row {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 2px 6px;
    min-width: 0;
    padding: 3px 0;
    font-size: 0.8rem;
    line-height: 1.4;
}

.ff-room-queue-rank {
    flex: 0 0 auto;
    min-width: 1.4em;
    font-variant-numeric: tabular-nums;
    opacity: 0.65;
}

.ff-room-queue-name {
    min-width: 0;
    overflow-wrap: anywhere;
    font-weight: 500;
}

.ff-room-queue-meta {
    min-width: 0;
    overflow-wrap: anywhere;
    color: var(--mud-palette-text-secondary);
}
/* ---- end DO-1 addendum ---- */

/* ============================================================================================
   BO-1 (2026-09-02) - the breakout board's team-level row marker.

   A preseason "production vacuum" row is a TEAM, not a player: the school sits in the name slot,
   which reads as a player name unless something says otherwise. This is that something. Tiny,
   uppercase and muted, so it labels the row without competing with the name it follows; the
   geometry matches the .ff-eff-tag idiom, kept as its own class because the two live on unrelated
   surfaces and should be free to diverge.

   Inline-block after the name so it wraps with the title rather than widening the 360px card, and
   nowrap so the word itself never breaks.
   ============================================================================================ */
.ff-row-kind {
    display: inline-block;
    margin-left: 6px;
    padding: 1px 5px;
    border-radius: 6px;
    background: var(--mud-palette-background);
    border: 1px solid var(--mud-palette-lines-default);
    color: var(--mud-palette-text-secondary);
    font-size: .6rem;
    font-weight: 700;
    letter-spacing: .04em;
    line-height: 1.7;
    text-transform: uppercase;
    vertical-align: middle;
    white-space: nowrap;
}
/* ---- end BO-1 addendum ---- */

/* ============================================================================================
   SS-2 (2026-09-02) - the stat search render extras: the defense vs position mini board and the
   two column panel.

   WHY THIS BOARD IS MARKUP AND NOT A CHART SPEC. Every other ranking on this page goes through
   <Chart> and ECharts, and this one deliberately does not, for two reasons the acceptance shape
   names. A DvP bar has to be tinted by its OWN band, and ChartSeriesData carries one colour per
   SERIES rather than per point, so a band coloured board is not expressible through that spec at
   all. And the board has to be keyboard reachable, which a canvas is not: here each row is a
   focusable list item whose aria-label says in words what the colour and the length say visually.
   The geometry is still the leaderboards' horizontal ranking (name on the left, bar, value on the
   right, best row on top), so the two read as one system.

   COLOUR COMES FROM THE BAND WORD AND FROM NOTHING ELSE. Every tinted rule below is anchored on a
   .ff-ss-band-* token, and that set is exactly SignalCopy.BandClasses plus the four matchup band
   words the tag panel carries. There is NO rule here whose selector is driven by a magnitude, a
   percentage or a threshold: the only number that reaches the stylesheet is the inline bar width,
   which is a length and never a colour. That is the same rule the 40A grammar block keeps, and it
   is what stops a thin sample being tinted into confidence: an insufficient defense carries an
   empty band, lands on .ff-ss-band-none, and renders in the neutral secondary text colour.

   THE TINTS ARE THE SHIPPED PALETTE. The five DvP bands reuse the .ff-dvp-chip values and the four
   matchup bands reuse MatchupChip's, so a band means the same colour whether it arrives here, on a
   draft board chip or on a game page.

   THE 360px SHAPE. The board scrolls INSIDE .ff-ss-dvp-scroll and never widens the page; the cap
   is applied only from 600px up, because on a phone the page itself is the scroll and a nested one
   would trap the touch. The panel is one stacked column at 360px (left, the read, right, in that
   order, so a versus panel still reads with its sentence between the two halves) and becomes a
   three column grid at 600px.
   ============================================================================================ */

/* ---- the defense vs position board ---- */
.ff-ss-dvp { margin-top: 12px; }

.ff-ss-dvp-scroll { overflow-x: auto; }

@media (min-width: 600px) {
    /* Above the phone the board gets a height cap and scrolls itself; below it, the page scrolls. */
    .ff-ss-dvp-scroll { max-height: 420px; overflow-y: auto; }
}

.ff-ss-dvp-list { list-style: none; margin: 0; padding: 0; min-width: 0; }

.ff-ss-dvp-row {
    display: grid;
    grid-template-columns: minmax(72px, 1fr) minmax(60px, 3fr) auto auto;
    align-items: center;
    gap: 8px;
    padding: 4px 6px;
    border-radius: 6px;
    min-width: 0;
}

.ff-ss-dvp-row:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 1px;
}

/* The school the question named. A ring plus a weight change, so it is findable without a second
   colour competing with the band tints that carry the actual meaning. */
.ff-ss-dvp-row.is-asked {
    background: var(--mud-palette-background-gray);
    box-shadow: inset 0 0 0 1px var(--mud-palette-lines-default);
}

.ff-ss-dvp-row.is-asked .nm { font-weight: 700; }

.ff-ss-dvp-row .nm {
    min-width: 0;
    overflow-wrap: anywhere;
    font-size: .78rem;
    font-weight: 600;
}

.ff-ss-dvp-row .bar {
    display: block;
    min-width: 0;
    height: 10px;
    border-radius: 5px;
    background: var(--mud-palette-background-gray);
    overflow: hidden;
}

.ff-ss-dvp-row .fill { display: block; height: 100%; border-radius: 5px; }

.ff-ss-dvp-row .val {
    font-size: .74rem;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
    white-space: nowrap;
}

.ff-ss-dvp-row .bnd {
    font-size: .6rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
    white-space: nowrap;
    padding: 1px 5px;
    border-radius: 6px;
}

.ff-ss-dvp-legend {
    margin-top: 8px;
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

/* ---- the two column panel ---- */
.ff-ss-panel { margin-top: 12px; }

.ff-ss-panel-cols {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    gap: 10px;
    min-width: 0;
}

@media (min-width: 600px) {
    /* The read sits in the middle cell, which is what makes a versus panel read left to right. The
       boards have no middle cell, so their two columns simply span it. */
    .ff-ss-panel[data-kind="versus"] .ff-ss-panel-cols {
        grid-template-columns: minmax(0, 1fr) minmax(0, 180px) minmax(0, 1fr);
        align-items: center;
    }

    .ff-ss-panel:not([data-kind="versus"]) .ff-ss-panel-cols {
        grid-template-columns: repeat(2, minmax(0, 1fr));
    }
}

.ff-ss-panel-col {
    min-width: 0;
    padding: 10px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 8px;
    background: var(--mud-palette-surface);
}

.ff-ss-panel-col .hd {
    font-size: .68rem;
    font-weight: 700;
    letter-spacing: .05em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
    margin-bottom: 6px;
}

.ff-ss-panel-col .mt { font-size: .76rem; color: var(--mud-palette-text-secondary); }

.ff-ss-panel-col ul { list-style: none; margin: 0; padding: 0; }

.ff-ss-panel-col li {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 6px;
    min-width: 0;
    padding: 4px 0;
}

.ff-ss-panel-col li + li { border-top: 1px solid var(--mud-palette-lines-default); }

.ff-ss-panel-col .nm { font-size: .8rem; font-weight: 600; min-width: 0; overflow-wrap: anywhere; }

.ff-ss-panel-col .val {
    font-size: .74rem;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
}

/* The why wraps onto its own full line, so a long reason never squeezes the name beside it. */
.ff-ss-panel-col .why {
    flex: 1 0 100%;
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-ss-panel-col .lens {
    flex: 1 0 100%;
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
    opacity: .85;
}

/* The model's one sentence, between the two halves of a versus panel. */
.ff-ss-panel-read {
    min-width: 0;
    font-size: .76rem;
    line-height: 1.45;
    color: var(--mud-palette-text-secondary);
    text-align: center;
    padding: 4px 6px;
    overflow-wrap: anywhere;
}

/* The boards' server authored caveat, under the whole panel. */
.ff-ss-panel-note {
    margin-top: 8px;
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* ---- the band tints, from the band WORD only ---- */
.ff-ss-band {
    font-size: .6rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
    white-space: nowrap;
    padding: 1px 5px;
    border-radius: 6px;
}

/* The five DvP bands (SignalCopy.BandClass), on the shipped .ff-dvp-chip palette. */
.ff-ss-band-top10 { color: var(--mud-palette-error); background: rgba(244, 67, 54, .16); }
.ff-ss-band-tough { color: var(--mud-palette-warning); background: rgba(255, 152, 0, .16); }
.ff-ss-band-average { color: var(--mud-palette-text-secondary); background: rgba(158, 158, 158, .16); }
.ff-ss-band-soft { color: var(--mud-palette-info); background: rgba(3, 169, 244, .16); }
.ff-ss-band-bottom10 { color: var(--mud-palette-success); background: rgba(76, 175, 80, .16); }

/* The four matchup bands (MatchupBands), on MatchupChip's palette. */
.ff-ss-band-trap { color: var(--mud-palette-error); background: rgba(244, 67, 54, .16); }
.ff-ss-band-boom { color: var(--mud-palette-info); background: rgba(3, 169, 244, .16); }
.ff-ss-band-smash { color: var(--mud-palette-success); background: rgba(76, 175, 80, .16); }
.ff-ss-band-neutral { color: var(--mud-palette-text-secondary); background: rgba(158, 158, 158, .16); }

/* No band at all: an insufficient sample, or a word no scale here knows. Neutral by construction,
   because a suppressed verdict is an absent one and must never be coloured like a present one. */
.ff-ss-band-none { color: var(--mud-palette-text-secondary); background: transparent; }

.ff-ss-dvp-row .fill.ff-ss-band-none { background: var(--mud-palette-text-secondary); opacity: .35; }
/* ---- end SS-2 addendum ---- */

/* =================================================================================================
   Phase 42 follow-up MR-1 (2026-09-05): a finished game on the matchup surfaces

   Game Day owns LIVE (ratified D0-7) and still does. This block styles the one retrospective state the
   two matchup surfaces now report: the final score on the slate card and the game page, the verdict
   chips beside the market cell, the result table on the game page, and the actual-beside-projected
   chip in the players lens. Everything this slice authors is .ff-mr-* ("matchup result"), so a block
   appended after it cannot silently win a cascade against MU-6's .ff-mu-*, MU-8's .ff-mg-* or MU-9's
   .ff-ml-* rules, and none of those are redefined here: the result table reuses .ff-mg-table BY ITS
   OWN CLASS and only adds to it under .ff-mr-table.

   Colour is never the only carrier. Every chip and every row that is tinted says the same thing in
   words (the school that covered, "Upset", "Push", the signed delta), and no selector here is reachable
   from a band word or a magnitude.
   ================================================================================================= */

/* ---- the final score, on the slate card's "when" line and the game page's result panel ---- */

.ff-mr-final .val { letter-spacing: .04em; text-transform: uppercase; font-size: .62rem; }

/* The live score beside the live marker (owner request, 2026-09-07). */
.ff-mr-livescore .val { font-weight: 600; font-variant-numeric: tabular-nums; }

/* THE FINAL SCORE IS THE LOUDEST THING ON A FINISHED CARD (owner walk, 2026-09-22: "for games that
   are final on matchups can we highlight the score or something to make it easier to see at a
   glance?"). It sat inline among the chips at .8rem, where "Syracuse 13 Pittsburgh 27" read as one
   more piece of body text. Now it takes a line of its own under the chips (a full basis in the when
   line's wrapping row, which is the middle column at 960px and a line of the stack at 360px), the
   points are set large and heavy, the winner's points take the primary colour while the loser's step
   back, and the card itself carries a left accent, so a scan down the slate separates the finals
   from the games still to come before a single number is read. Colour is never the only carrier:
   the winner's side keeps its own class and weight, and the score keeps its spoken sentence. */
.ff-mr-score {
    display: inline-flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 2px 14px;
    min-width: 0;
    flex: 1 0 100%;
    padding-top: 2px;
    font-size: .8rem;
    font-variant-numeric: tabular-nums;
}

/* The finished card's accent: a bar on its leading edge, drawn inside the border so nothing moves. */
.ff-mu-card.ff-mr-card { box-shadow: inset .1875rem 0 0 var(--mud-palette-primary); }

.ff-mr-score .side { display: inline-flex; align-items: baseline; gap: 4px; min-width: 0; }

/* The school name gives before the card does, and the points never wrap away from their school. */
.ff-mr-score .tm {
    max-width: 14ch;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
    color: var(--mud-palette-text-secondary);
}

.ff-mr-score .pts { font-size: 1.15rem; font-weight: 800; line-height: 1.2; }

/* The winner is the side that reads as the headline, its points in the primary colour; the loser
   stays in the secondary tone, points included, once there is a winner to defer to. A tie marks
   nobody, so it mutes nobody either. */
.ff-mr-score .side.win .tm { color: var(--mud-palette-text-primary); font-weight: 600; }
.ff-mr-score .side.win .pts { color: var(--mud-palette-primary); }
.ff-mr-score:has(.side.win) .side:not(.win) .pts { color: var(--mud-palette-text-secondary); }

@media (min-width: 600px) {
    .ff-mr-score .tm { max-width: 22ch; }
}

/* ---- the verdict chips in the slate card's market cell ---- */

.ff-mr-verdicts {
    display: inline-flex;
    flex-wrap: wrap;
    gap: 6px;
    min-width: 0;
    width: 100%;
}

/* The upset is the one thing on a finished card a member scans for, so it is the one chip tinted. A
   push is muted because it is the market being exactly right, which is an absence of a verdict. */
.ff-mr-chip.upset { border-color: var(--mud-palette-warning); }
.ff-mr-chip.upset .val { color: var(--mud-palette-warning); }
.ff-mr-chip.push .val { color: var(--mud-palette-text-secondary); font-weight: 500; }

/* ---- the game page's result panel ---- */

.ff-mr-panel { margin-bottom: 16px; }

.ff-mr-scoreline {
    display: grid;
    grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
    gap: 8px 16px;
    margin-bottom: 12px;
    min-width: 0;
}

.ff-mr-scoreline .side {
    display: flex;
    flex-direction: column;
    gap: 2px;
    min-width: 0;
}

.ff-mr-scoreline .tm {
    font-size: .8rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-mr-scoreline .pts {
    font-size: 1.6rem;
    font-weight: 700;
    line-height: 1.1;
    font-variant-numeric: tabular-nums;
}

.ff-mr-scoreline .side.win .tm { color: var(--mud-palette-text-primary); font-weight: 600; }
.ff-mr-scoreline .side.win .pts { color: var(--mud-palette-primary); }

/* The result table: MU-8's table by its own class, plus the "what happened" cell's two lines. */
.ff-mr-table .vd { display: block; font-size: .72rem; font-weight: 600; }
.ff-mr-table .vd.sub { font-weight: 500; color: var(--mud-palette-text-secondary); }

.ff-mr-row.upset .vd { color: var(--mud-palette-warning); }
.ff-mr-row.push .vd { color: var(--mud-palette-text-secondary); font-weight: 500; }

/* ---- the players lens: actual beside projected ---- */

/* The lens's own research note, placed; it is the shipped note by its own class. */
.ff-mr-actualsnote { margin-bottom: 8px; }

.ff-mr-actual {
    display: inline-flex;
    align-items: baseline;
    flex-wrap: wrap;
    gap: 4px;
    min-width: 0;
    padding: 1px 7px;
    border-radius: 999px;
    border: 1px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-background);
    font-size: .68rem;
    line-height: 1.7;
    font-variant-numeric: tabular-nums;
}

.ff-mr-actual .lbl {
    font-size: .62rem;
    text-transform: uppercase;
    letter-spacing: .04em;
    color: var(--mud-palette-text-secondary);
}

.ff-mr-actual .val { font-weight: 700; }

/* The delta: over the projection, under it, or on it. The sign in the text carries the same fact. */
.ff-mr-actual .dl { font-weight: 600; }
.ff-mr-actual .dl.up { color: var(--mud-palette-success); }
.ff-mr-actual .dl.down { color: var(--mud-palette-error); }
.ff-mr-actual .dl.even { color: var(--mud-palette-text-secondary); }

/* In or out of the projected range, muted either way: the delta is the number, this is its context. */
.ff-mr-actual .bd { font-size: .62rem; color: var(--mud-palette-text-secondary); }
.ff-mr-actual .bd.out { color: var(--mud-palette-warning); }

/* ---- end Phase 42 MR-1 ---- */

/* =================================================================================================
   Phase 44 LG-2 (2026-09-06): the live game sheet

   Tapping a live chip on Game Day opens this. Everything this slice authors is .ff-lg-* ("live
   game"), so a block appended after it cannot silently win a cascade against Game Day's own
   .ff-gd-* rules, and none of those are redefined here: the tappable chip is styled BY ITS OWN
   ADDED CLASS (.ff-gd-chip.ff-lg-tap) and the label it was before this slice is untouched.

   360px FIRST, which is why nothing here declares a pixel width. The sheet is one column that may
   shrink to nothing and wrap as often as it needs; the dialog is capped at 45rem (720px at the
   default root size) on a desktop and goes edge to edge below 600px, where a phone has no room for
   a dialog's margins. The one scroll container is the line score table's, and it scrolls in BOTH
   axes rather than declaring a horizontal one, because a second horizontal scroller on the page is
   what the 360px rule exists to prevent.

   Colour is never the only carrier and never a literal. Every value is a palette token, so both
   themes are correct by construction; the live state says "live" with a clock beside its dot, the
   leader is marked with weight as well as tone, and a player with no stored line carries the
   sanctioned placeholder glyph AND the sentence that explains it.
   ================================================================================================= */

/* ---- the dialog itself ---- */

/* Medium (960px) is the MudBlazor option the component asks for; this narrows it to the plan's
   720px on a desktop without a pixel of its own. */
.ff-lg-dialog { max-width: 45rem; }

.ff-lg-sheet {
    display: flex;
    flex-direction: column;
    gap: 14px;
    min-width: 0;
}

/* ---- block 1: the head, which is the dialog's title ---- */

.ff-lg-head {
    display: flex;
    flex-direction: column;
    gap: 4px;
    min-width: 0;
    width: 100%;
}

.ff-lg-score {
    display: flex;
    flex-wrap: wrap;
    gap: 4px 18px;
    min-width: 0;
    font-variant-numeric: tabular-nums;
}

.ff-lg-score .side {
    display: inline-flex;
    align-items: baseline;
    gap: 8px;
    min-width: 0;
}

.ff-lg-score .tm {
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lg-score .pts { font-size: 1.5rem; font-weight: 700; line-height: 1.1; }

/* The side in front while the game is being played. Weight and tone together, never tone alone. */
.ff-lg-score .side.lead .tm { color: var(--mud-palette-text-primary); font-weight: 600; }
.ff-lg-score .side.lead .pts { color: var(--mud-palette-primary); }

.ff-lg-state {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 6px 12px;
    min-width: 0;
    font-size: .8rem;
}

.ff-lg-live {
    display: inline-flex;
    align-items: center;
    gap: 6px;
    font-weight: 600;
    color: var(--mud-palette-error);
}

.ff-lg-live .dot {
    display: inline-block;
    width: .5rem;
    height: .5rem;
    border-radius: 999px;
    background: var(--mud-palette-error);
}

.ff-lg-final { font-weight: 600; letter-spacing: .04em; text-transform: uppercase; font-size: .72rem; }
.ff-lg-upcoming { color: var(--mud-palette-text-secondary); }

.ff-lg-poss {
    display: inline-flex;
    align-items: center;
    gap: 4px;
    min-width: 0;
    color: var(--mud-palette-text-secondary);
}

.ff-lg-observed { font-size: .72rem; color: var(--mud-palette-text-secondary); }

/* "Still watching?", in the freshness row's place once the refresh has stopped itself at its bound
   (plan §3.3: every composed read registers this game with the capture loop's watch registry, so a
   sheet open in a forgotten tab keeps buying a metered feed). It is a control, so it reads as one and
   takes a focus ring of its own. */
.ff-lg-keep {
    cursor: pointer;
    text-decoration: underline;
    color: var(--mud-palette-primary);
}

.ff-lg-keep:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
}

/* ---- the shared block frame, and the sentence a degraded block renders instead ---- */

.ff-lg-block {
    display: flex;
    flex-direction: column;
    gap: 6px;
    min-width: 0;
}

.ff-lg-h {
    margin: 0;
    font-size: .68rem;
    font-weight: 600;
    letter-spacing: .06em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-lg-note {
    font-size: .8rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lg-skeleton { display: flex; flex-direction: column; gap: 8px; }

/* ---- block 2: the situation and the last play ---- */

.ff-lg-situation { font-weight: 600; overflow-wrap: anywhere; }

.ff-lg-lastplay { font-size: .82rem; overflow-wrap: anywhere; }

.ff-lg-lastplay .lbl {
    margin-right: 6px;
    font-size: .62rem;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

/* ---- block 3: the two sided probability bar, and the history line ---- */

.ff-lg-wp-bar {
    display: flex;
    width: 100%;
    height: .6rem;
    border-radius: 999px;
    overflow: hidden;
    background: var(--mud-palette-lines-default);
}

.ff-lg-wp-bar .away { background: var(--mud-palette-secondary); }
.ff-lg-wp-bar .home { background: var(--mud-palette-primary); }

.ff-lg-wp-legend {
    display: flex;
    justify-content: space-between;
    gap: 8px;
    min-width: 0;
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

.ff-lg-wp-legend .away { overflow-wrap: anywhere; }
.ff-lg-wp-legend .home { overflow-wrap: anywhere; text-align: right; }

.ff-lg-spark { display: block; width: 100%; height: 48px; }

.ff-lg-spark polyline { stroke: var(--mud-palette-primary); stroke-width: 2; }

.ff-lg-spark-axis {
    display: flex;
    justify-content: space-between;
    font-size: .62rem;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

/* ---- block 4: the line scores ---- */

/* Both axes, deliberately: an overtime game grows columns, and a container that scrolls itself is
   what keeps the PAGE from scrolling sideways at 360px. */
.ff-lg-lines-wrap { overflow: auto; }

.ff-lg-lines {
    width: 100%;
    border-collapse: collapse;
    font-size: .78rem;
    font-variant-numeric: tabular-nums;
}

.ff-lg-lines th, .ff-lg-lines td {
    padding: 4px 6px;
    text-align: center;
    border-bottom: 1px solid var(--mud-palette-lines-default);
}

.ff-lg-lines th[scope="row"] {
    text-align: left;
    font-weight: 500;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lg-lines thead th {
    font-size: .62rem;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-lg-lines .tot { font-weight: 700; }

/* ---- block 5: the market held against the score ---- */

.ff-lg-market { font-size: .82rem; overflow-wrap: anywhere; }

/* ---- block 6: the context chips ---- */

.ff-lg-chips {
    display: flex;
    flex-wrap: wrap;
    gap: 6px;
    min-width: 0;
    width: 100%;
}

.ff-lg-chip {
    display: inline-flex;
    align-items: baseline;
    min-width: 0;
    padding: 1px 8px;
    border-radius: 999px;
    border: 1px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-background);
    font-size: .68rem;
    line-height: 1.7;
}

.ff-lg-chip .val { overflow-wrap: anywhere; }

/* ---- block 7: who is in this game ---- */

.ff-lg-lens { margin-bottom: 2px; }

.ff-lg-basis { font-size: .72rem; color: var(--mud-palette-text-secondary); }

.ff-lg-members { display: grid; grid-template-columns: minmax(0, 1fr); gap: 10px; }

.ff-lg-member {
    display: flex;
    flex-direction: column;
    gap: 4px;
    min-width: 0;
    padding: 8px 10px;
    border-radius: 8px;
    border: 1px solid var(--mud-palette-lines-default);
}

.ff-lg-member.mine { border-color: var(--mud-palette-primary); }

.ff-lg-member .who {
    display: flex;
    align-items: center;
    gap: 6px;
    min-width: 0;
    font-weight: 600;
}

.ff-lg-member .who .nm { overflow-wrap: anywhere; }

.ff-lg-member .metag {
    padding: 0 6px;
    border-radius: 999px;
    background: var(--mud-palette-primary);
    color: var(--mud-palette-primary-text);
    font-size: .58rem;
    letter-spacing: .06em;
}

.ff-lg-player {
    display: flex;
    align-items: baseline;
    gap: 8px;
    min-width: 0;
    font-size: .8rem;
}

.ff-lg-player .pos {
    flex: 0 0 auto;
    font-size: .62rem;
    letter-spacing: .04em;
    color: var(--mud-palette-text-secondary);
}

.ff-lg-player .main { display: flex; flex-direction: column; min-width: 0; flex: 1 1 auto; }

.ff-lg-player .main .nm { overflow-wrap: anywhere; }

/* The name line: the name, then the school beside it, wrapping under it when the row is narrow. */
.ff-lg-who { display: flex; flex-wrap: wrap; align-items: baseline; column-gap: 6px; min-width: 0; }

.ff-lg-who .school {
    font-size: .7rem;
    letter-spacing: .02em;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lg-player .line, .ff-lg-player .note {
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lg-player .pts {
    flex: 0 0 auto;
    font-weight: 700;
    font-variant-numeric: tabular-nums;
}

/* No stored line yet: the sanctioned glyph, muted, with its own sentence beside it. */
.ff-lg-player .pts.none { font-weight: 500; color: var(--mud-palette-text-secondary); }

/* ---- owner request, 2026-09-07: where the ball is, who is on the field, the scoring as captured ---- */

.ff-lg-field { display: flex; flex-direction: column; gap: 6px; margin-top: 8px; }

.ff-lg-field-bar {
    position: relative;
    height: .5rem;
    border-radius: 999px;
    background: var(--mud-palette-lines-default);
}

.ff-lg-field-marker {
    position: absolute;
    top: -.2rem;
    width: .25rem;
    height: .9rem;
    margin-left: -.125rem;
    border-radius: .125rem;
    background: var(--mud-palette-primary);
}

.ff-lg-field-text {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 8px;
    font-size: .78rem;
    color: var(--mud-palette-text-secondary);
}

.ff-lg-zone {
    padding: 0 8px;
    border-radius: 999px;
    border: 1px solid var(--mud-palette-error);
    color: var(--mud-palette-error);
    font-size: .62rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
}

.ff-lg-ball {
    display: inline-flex;
    align-items: center;
    width: fit-content;
    padding: 0 6px;
    border-radius: 999px;
    border: 1px solid var(--mud-palette-primary);
    color: var(--mud-palette-primary);
    font-size: .62rem;
    font-weight: 600;
    letter-spacing: .04em;
    text-transform: uppercase;
}

.ff-lg-scoring { margin-top: 10px; }

.ff-lg-scoring-cap {
    margin-bottom: 4px;
    font-size: .62rem;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-lg-scoring-list { list-style: none; margin: 0; padding: 0; display: flex; flex-direction: column; gap: 6px; }

.ff-lg-scoring-row {
    display: grid;
    grid-template-columns: auto 1fr auto;
    column-gap: 8px;
    align-items: baseline;
    font-size: .8rem;
}

.ff-lg-scoring-row .when { font-variant-numeric: tabular-nums; color: var(--mud-palette-text-secondary); }

.ff-lg-scoring-row .what { font-weight: 600; }

.ff-lg-scoring-row .score { font-variant-numeric: tabular-nums; }

.ff-lg-scoring-row .play {
    grid-column: 2 / span 2;
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lg-scoring-basis { margin-top: 6px; font-size: .68rem; color: var(--mud-palette-text-secondary); }

/* ---- block 9: talk about it, ask about it ---- */

.ff-lg-actions { display: flex; flex-direction: column; gap: 8px; }

.ff-lg-action { text-transform: none; }

/* ---- the chip that opens all of this ---- */

/* The live chip becomes a control only where the host offers the sheet, so this rule is keyed to a
   class the chip adds ONLY in that state: an untapped chip keeps the label's cursor and its exact
   markup. */
.ff-gd-chip.ff-lg-tap { cursor: pointer; }

.ff-gd-chip.ff-lg-tap:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
}

/* ---- 360px: the sheet is the screen ---- */

@media (max-width: 599.98px) {
    .ff-lg-dialog {
        width: 100%;
        max-width: 100%;
        height: 100%;
        max-height: 100%;
        margin: 0;
        border-radius: 0;
    }

    .ff-lg-score .pts { font-size: 1.3rem; }
}

/* ---- 960px: the member cards pair up, and nothing else moves ---- */

@media (min-width: 960px) {
    .ff-lg-members { grid-template-columns: minmax(0, 1fr) minmax(0, 1fr); }

    .ff-lg-actions { flex-direction: row; }
}

/* ---- end Phase 44 LG-2 ---- */

/* =================================================================================================
   Phase 44 LG-5 (2026-09-06): the drives block of the live game sheet

   The metered half of the live game view: the drive under way play by play, the whole drive log with
   the scoring drives marked, and the two sides' live advanced numbers side by side. Everything this
   slice authors is .ff-lgd-* ("live game drives"), which is deliberately a different prefix from
   LG-2's .ff-lg-*: the two blocks are appended separately and neither may win a cascade against the
   other by accident. The block reuses LG-2's .ff-lg-h heading and .ff-lg-note sentence classes rather
   than redefining them, so a degraded drives block reads exactly like every other degraded block of
   the sheet.

   360px FIRST, which is why nothing here declares a pixel width. The block is one column that stacks
   the play list, then the log, then the comparison; at 960 the grid becomes two columns with the play
   list on the left and the log and comparison on the right (plan §9.3), which is the only thing that
   moves. The comparison table scrolls inside its OWN container, in both axes rather than declaring a
   horizontal one, because a second horizontal scroller on the page is what the 360px rule exists to
   prevent.

   Colour is never the only carrier and never a literal. Every value is a palette token, so both
   themes are correct by construction; a scoring drive and a scoring play say "scored" in a word beside
   their tint, the leader on a paired metric says "leads", and a garbage time play is muted AND carries
   CFBD's own explanation on hover.
   ================================================================================================= */

.ff-lgd-block {
    display: flex;
    flex-direction: column;
    gap: 8px;
    min-width: 0;
}

/* One column at 360, two at 960. minmax(0, 1fr) rather than 1fr so a long play description shrinks the
   column instead of widening the grid, which is the whole reason the sheet does not scroll sideways. */
.ff-lgd-grid {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    gap: 12px;
    min-width: 0;
}

.ff-lgd-col {
    display: flex;
    flex-direction: column;
    gap: 6px;
    min-width: 0;
}

.ff-lgd-sub {
    margin: 0;
    font-size: .62rem;
    font-weight: 600;
    letter-spacing: .06em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-lgd-driveline {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* ---- the current drive, newest snap first ---- */

.ff-lgd-play {
    display: flex;
    flex-direction: column;
    gap: 2px;
    min-width: 0;
    padding: 6px 8px;
    border-radius: 8px;
    border: 1px solid var(--mud-palette-lines-default);
}

/* CFBD's judgement, not ours: the play still renders in full, and the title says whose call it is. */
.ff-lgd-play.garbage { opacity: .62; }

.ff-lgd-play .hd {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 4px 10px;
    min-width: 0;
}

.ff-lgd-play .dd {
    font-size: .72rem;
    font-weight: 600;
    overflow-wrap: anywhere;
}

.ff-lgd-play .ck {
    font-size: .62rem;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
}

.ff-lgd-play .tx { font-size: .78rem; overflow-wrap: anywhere; }

.ff-lgd-play .mk {
    display: flex;
    flex-wrap: wrap;
    gap: 4px 8px;
    min-width: 0;
    font-size: .62rem;
    font-variant-numeric: tabular-nums;
}

.ff-lgd-play .gn { color: var(--mud-palette-text-secondary); }

/* Garbage time in WORDS beside the numbers. The muted row and the hover title carried this alone,
   which is colour plus an attribute a phone never shows; the chip is the fact itself, and it is muted
   because it is a caveat about the play rather than a mark against it. */
.ff-lgd-play .gt {
    color: var(--mud-palette-text-secondary);
    font-style: italic;
    overflow-wrap: anywhere;
}

.ff-lgd-play .epa {
    padding: 0 6px;
    border-radius: 999px;
    border: 1px solid var(--mud-palette-lines-default);
    color: var(--mud-palette-text-secondary);
}

.ff-lgd-play .epa.up { color: var(--mud-palette-success); }
.ff-lgd-play .epa.down { color: var(--mud-palette-error); }

.ff-lgd-play .sc, .ff-lgd-drive .sc {
    padding: 0 6px;
    border-radius: 999px;
    background: var(--mud-palette-primary);
    color: var(--mud-palette-primary-text);
    font-size: .58rem;
    letter-spacing: .06em;
    text-transform: uppercase;
}

/* ---- the drive log, oldest first ---- */

.ff-lgd-log {
    display: flex;
    flex-direction: column;
    gap: 4px;
    min-width: 0;
}

.ff-lgd-drive {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 2px 8px;
    min-width: 0;
    padding: 4px 8px;
    border-radius: 6px;
    border-left: 2px solid var(--mud-palette-lines-default);
    font-size: .74rem;
}

/* Weight and tone together, with the word beside them: colour is never the only carrier. */
.ff-lgd-drive.scored { border-left-color: var(--mud-palette-primary); }

.ff-lgd-drive .off { font-weight: 600; overflow-wrap: anywhere; }

.ff-lgd-drive .res {
    letter-spacing: .04em;
    text-transform: uppercase;
    font-size: .62rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lgd-drive .ct {
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
}

/* ---- the two sides' live advanced numbers ---- */

.ff-lgd-teams {
    display: flex;
    flex-direction: column;
    gap: 4px;
    min-width: 0;
}

.ff-lgd-lens { margin-bottom: 2px; }

.ff-lgd-source { font-size: .62rem; color: var(--mud-palette-text-secondary); }

/* Both axes, deliberately: two long school names in the header can outgrow a phone, and a container
   that scrolls itself is what keeps the PAGE from scrolling sideways at 360px. */
.ff-lgd-scroll { overflow: auto; }

.ff-lgd-table {
    width: 100%;
    border-collapse: collapse;
    font-size: .72rem;
    font-variant-numeric: tabular-nums;
}

.ff-lgd-table th, .ff-lgd-table td {
    padding: 3px 6px;
    text-align: left;
    border-bottom: 1px solid var(--mud-palette-lines-default);
    vertical-align: baseline;
}

.ff-lgd-table thead th {
    font-size: .62rem;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lgd-table .num { text-align: right; }

.ff-lgd-table th[scope="row"] { font-weight: 500; }

.ff-lgd-table .nm { display: block; overflow-wrap: anywhere; }

.ff-lgd-table .bs { display: block; font-size: .58rem; color: var(--mud-palette-text-secondary); }

.ff-lgd-table .lead .vl { font-weight: 700; color: var(--mud-palette-text-primary); }

.ff-lgd-table .ld {
    display: block;
    font-size: .55rem;
    letter-spacing: .06em;
    text-transform: uppercase;
    color: var(--mud-palette-primary);
}

/* ---- how fresh the log is ---- */

.ff-lgd-captured { font-size: .62rem; color: var(--mud-palette-text-secondary); }

/* ---- 960px: the play list left, the log and the comparison right (plan §9.3) ---- */

@media (min-width: 960px) {
    .ff-lgd-grid { grid-template-columns: minmax(0, 1fr) minmax(0, 1fr); }

    /* A game that is not being played has no current drive, so the log is the only column: it takes
       the whole row rather than leaving half the sheet empty beside it. */
    .ff-lgd-grid > .ff-lgd-col:only-child { grid-column: 1 / -1; }
}

/* ---- end Phase 44 LG-5 ---- */

/* =================================================================================================
   Phase 44 LG-6 (2026-09-06): the entry points and the finished game's story

   Three small surfaces and one prefix. The Matchups slate's live marker, the graded market the live
   game sheet shows once a game is over, and the "how it unfolded" block on the finished game's result
   panel. Everything here is .ff-lg6-*, which is deliberately a third prefix beside LG-2's .ff-lg- and
   LG-5's .ff-lgd-: the three blocks are appended separately and none of them may win a cascade against
   another by accident. (It also does not CONTAIN either of the other two as a substring, which is what
   keeps their own prefix guards honest, and the reason it is "lg6" rather than "lg-6".)

   IT REUSES RATHER THAN REDEFINES. The verdict chips are MR-1's .ff-mr-chip on the shipped
   .ff-ctx-chip geometry, the tables are the game page's own .ff-mg-table inside its own .ff-mg-scroll
   container, and the lens is the shipped SignalChip. Nothing below restyles any of them; it only
   places them.

   360px FIRST, which is why nothing here declares a pixel width. The unfolded block is one column at
   every size: a caption, a full width chart, then two tables that each scroll inside their own
   container so a long drive result can never push the PAGE sideways. The two tables are the only thing
   here that can overflow and neither declares a horizontal scroller of its own, because the shared
   .ff-mg-scroll container already owns that behaviour.

   BOTH THEMES BY CONSTRUCTION: every colour below is a MudBlazor palette token, so light and dark are
   correct without a second rule anywhere in this block.
   ================================================================================================= */

/* ---- the Matchups slate's live marker (LG-6 entry point) ----
   The dot is the same error token the sheet's own live marker uses, so "this game is being played"
   looks the same wherever the product says it. It does not pulse: this row can carry sixty of them on
   a Saturday board, and sixty pulsing dots is a page nobody can read. */

.ff-lg6-live { color: var(--mud-palette-error); font-weight: 600; }

.ff-lg6-live .dot {
    display: inline-block;
    width: .45rem;
    height: .45rem;
    border-radius: 999px;
    background: var(--mud-palette-error);
    margin-right: 5px;
    flex: none;
}

/* ---- the sheet's graded market, once the game is over (block 5b) ---- */

.ff-lg6-outcome { font-weight: 600; margin-bottom: 6px; }

/* Wrapping rather than scrolling: three short chips fit one line on a phone and two lines at worst,
   and a chip row that scrolled would hide a verdict behind an edge. */
.ff-lg6-verdicts { display: flex; flex-wrap: wrap; gap: 6px; }

/* ---- "how it unfolded", inside MR-1's result panel ---- */

/* It stands in a panel of its own since the Phase 44 audit (B3): the block used to be a footer inside
   MR-1's result panel, and the rule that separated it from the table above it drew a stray line across
   the top of its own panel once it moved. There is nothing above it to separate it from any more. */
.ff-lg6-unfolded { min-width: 0; }

/* The panel's own gap to whatever follows it (owner, 2026-09-07): MR-1's result panel carries the
   same 16px through .ff-mr-panel, and this one, standing on its own since B3, carried none, so the
   scouting block below it sat flush against its border. */
.ff-lg6-panel { margin-bottom: 16px; }

.ff-lg6-h {
    margin: 0 0 8px;
    font-size: .78rem;
    letter-spacing: .05em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-lg6-cap {
    margin: 10px 0 4px;
    font-size: .68rem;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-lg6-chart { margin-bottom: 4px; }

/* The shipped ECharts host, full width of whatever holds it (owner, 2026-09-07: the sparkline named no
   number). The host sizes its own canvas from its Height parameter, so nothing here declares one. */
.ff-lg6-wpchart { margin: 4px 0 2px; min-width: 0; }

.ff-lg6-basis {
    margin-top: 6px;
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
}

.ff-lg6-drives { margin-top: 10px; }

.ff-lg6-lens { margin-bottom: 4px; }

/* Figures line up column to column, and a drive result stays on one line inside the scroll container
   rather than wrapping a four column table into a wall. */
.ff-lg6-table th, .ff-lg6-table td { font-variant-numeric: tabular-nums; white-space: nowrap; }

/* The scoring as captured, on the finished game panel (owner request, 2026-09-07). */
.ff-lg6-scoring { margin-top: 10px; }

.ff-lg6-scoring-list { list-style: none; margin: 0; padding: 0; display: flex; flex-direction: column; gap: 6px; }

.ff-lg6-scoring-row {
    display: grid;
    grid-template-columns: auto 1fr auto;
    column-gap: 8px;
    align-items: baseline;
    font-size: .85rem;
}

.ff-lg6-scoring-row .when { font-variant-numeric: tabular-nums; color: var(--mud-palette-text-secondary); }

.ff-lg6-scoring-row .what { font-weight: 600; }

.ff-lg6-scoring-row .score { font-variant-numeric: tabular-nums; }

.ff-lg6-scoring-row .play {
    grid-column: 2 / span 2;
    font-size: .74rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* ---- end Phase 44 LG-6 ---- */


/* ---------------------------------------------------------------------------------------------
   LIVE FIRST (owner request, 2026-09-12)

   Two strips, one idea: while a game is being played it should be the easiest thing on the page to
   find and the easiest thing to tap.

   On the Matchups slate the live rows are pinned to the top of whatever sort the member chose, and
   .ff-mu-livenow is the one line that explains why the order looks the way it does. On Game Day the
   ticker's "3 in play" finally names its three, and .ff-gd-livenow is that list.

   Both reuse what is already here rather than inventing a look: the live dot is .ff-lg6-live's, the
   surfaces and lines are the same tokens the ticker beside them uses, and neither strip introduces a
   colour of its own. Both wrap at 360px, and the Game Day chips are sized as tap targets because on
   a Saturday afternoon that is exactly what they are.
   --------------------------------------------------------------------------------------------- */

/* ---- the slate's "these are listed first" line ---- */

.ff-mu-livenow {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 4px 10px;
    margin: 0 0 10px;
    font-size: .82rem;
    color: var(--mud-palette-text-secondary);
}

/* The sentence may shrink and wrap; the chip beside it keeps its size. */
.ff-mu-livenow .txt { min-width: 0; overflow-wrap: anywhere; }

.ff-mu-livenow .ff-lg6-live {
    display: inline-flex;
    align-items: center;
    flex: none;
    font-size: .74rem;
    text-transform: uppercase;
    letter-spacing: .04em;
}

/* ---- Game Day: the games behind the live count ---- */

.ff-gd-livenow {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: 8px 10px;
    /* It sits directly under the ticker, so it pulls up into the ticker's own bottom margin: the two
       read as one block rather than as two bars with a gap between them. */
    margin: -10px 0 18px;
    padding: 0 2px;
}

.ff-gd-livenow .lbl {
    display: inline-flex;
    align-items: center;
    flex: none;
    gap: 6px;
    font-size: .72rem;
    font-weight: 700;
    text-transform: uppercase;
    letter-spacing: .06em;
    color: var(--mud-palette-error);
}

/* The same pulse the ticker's own live dot carries, so one page has one live mark. */
.ff-gd-livenow .lbl .dot {
    /* rem rather than px, so the mark scales with the reader's own type size and the block carries
       no fixed pixel size at all. */
    width: .5rem;
    height: .5rem;
    border-radius: 999px;
    background: var(--mud-palette-error);
    animation: ff-pulse 1.4s ease-in-out infinite;
}

.ff-gd-livenow .gm {
    display: inline-flex;
    align-items: baseline;
    gap: 8px;
    min-width: 0;
    /* A thumb sized target: this is read and tapped on a phone, mid game. */
    padding: 7px 11px;
    border-radius: 999px;
    background: var(--mud-palette-surface);
    border: 1px solid rgba(var(--mud-palette-error-rgb), .35);
    font-size: .82rem;
    line-height: 1.3;
    color: var(--mud-palette-text-primary);
    text-decoration: none;
    overflow-wrap: anywhere;
}

.ff-gd-livenow a.gm:hover,
.ff-gd-livenow a.gm:focus-visible {
    background: rgba(var(--mud-palette-error-rgb), .10);
    border-color: var(--mud-palette-error);
}

.ff-gd-livenow .gm .tms { font-weight: 700; font-variant-numeric: tabular-nums; min-width: 0; }

.ff-gd-livenow .gm .cl {
    flex: none;
    font-size: .72rem;
    font-weight: 600;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
}

@media (max-width: 599.98px) {
    /* At 360px the label takes its own line and the games stack under it, each one full width, which
       keeps every chip a whole row target instead of two half rows a thumb has to aim between. */
    .ff-gd-livenow { gap: 6px; }
    .ff-gd-livenow .lbl { flex-basis: 100%; }
    .ff-gd-livenow .gm { flex: 1 1 100%; justify-content: space-between; }
}

/* ---- end LIVE FIRST ---- */

/* =============================================================================================
   Phase 45 45E (2026-09-12): the live game stage

   The field, the drive chart, the deserve to win gauge and the More live numbers block, all of them
   inside the live game sheet and all of them .ff-lgf-* ("live game field"), which is deliberately a
   different prefix from LG-2's .ff-lg-* and LG-5's .ff-lgd-*: the blocks are appended separately and
   none of them may win a cascade against another by accident. It reuses LG-2's .ff-lg-h heading and
   .ff-lg-note sentence classes rather than redefining them, so a degraded stage block reads exactly
   like every other degraded block of the sheet.

   NO PIXEL WIDTH ANYWHERE, and that is load bearing rather than stylistic here. The field, the chart
   and the gauge are inline SVGs with a viewBox and width: 100%; height: auto, so each one is exactly
   as wide as whatever holds it and as tall as its own proportions say, at 360px and at 1920, with no
   measurement in this file at all. The one table scrolls inside its OWN container, in both axes rather
   than declaring a horizontal one, because a second horizontal scroller on the page is what the 360px
   rule exists to prevent.

   TWO BREAKPOINTS, AND NEITHER IS ABOVE 960 (plan §3.4, D0-13). Below 600px the field's yard numbers
   are hidden, because eight numbers in a 360px wide picture are ink rather than information. At 960px
   and wider the More live numbers panel is always open and its button is hidden, which is how "always
   open at the sheet's own breakpoint" is true with no JavaScript, no resize listener and no viewport
   measurement. The sheet never acquires a breakpoint above 960 (LiveGameSheetStylesheetTests asserts
   exactly that), so a desktop member who reaches the sheet reads the phone layout, which is a complete
   layout rather than a degraded one.

   COLOUR IS NEVER THE ONLY CARRIER AND NEVER A LITERAL. Every value here is a palette token, so both
   themes are correct by construction. The two places a school's own colour appears are INLINE fills
   composed from the stored /teams payload, which is data rather than stylesheet, and every one of those
   elements carries a palette token stroke as well, so the shape reads on any background, in any theme
   and against any colour vision, with the school named in the element's aria label either way.
   ============================================================================================= */

/* ---- the field ---- */

.ff-lgf-block {
    display: flex;
    flex-direction: column;
    gap: 6px;
    min-width: 0;
}

/* The whole picture, sized by its viewBox and by nothing else. */
.ff-lgf-svg {
    width: 100%;
    height: auto;
    display: block;
    border-radius: 6px;
    border: 1px solid var(--mud-palette-lines-default);
}

.ff-lgf-turf { fill: var(--mud-palette-background-gray); }

.ff-lgf-zone {
    fill: var(--mud-palette-error);
    opacity: .12;
}

/* The zone the offense is attacking, emphasised. The tint is the emphasis and the aria label carries
   the fact, so the emphasis is never the only thing saying it. */
.ff-lgf-zone.on { opacity: .3; }

.ff-lgf-line {
    stroke: var(--mud-palette-lines-default);
    stroke-width: .2;
}

/* The two font sizes in this block are inside an SVG viewBox, where a px IS a user unit: they scale
   with the picture exactly as the yard lines do, and they are not device pixels. Everywhere outside an
   SVG this block measures in rem or in nothing at all. */
.ff-lgf-num {
    fill: var(--mud-palette-text-secondary);
    font-size: 3.4px;
    font-weight: 600;
}

/* An end zone's own tint is an INLINE fill from the stored payload, so this rule supplies only the
   palette token stroke that keeps the shape readable when the payload published no colour at all. */
.ff-lgf-end {
    fill: var(--mud-palette-background-gray);
    stroke: var(--mud-palette-lines-default);
    stroke-width: .3;
}

.ff-lgf-mono {
    fill: var(--mud-palette-text-primary);
    font-size: 4px;
    font-weight: 700;
}

.ff-lgf-mark { opacity: .95; }

/* One snap of the drive under way. The WIDTH steps off the yards the feed published and the TOKEN
   follows the sign of its EPA, which is the one place a magnitude reaches a class in this block. */
.ff-lgf-seg {
    stroke: var(--mud-palette-text-secondary);
    stroke-linecap: round;
    opacity: .85;
}

.ff-lgf-seg.up { stroke: var(--mud-palette-success); }

.ff-lgf-seg.down { stroke: var(--mud-palette-warning); }

.ff-lgf-score {
    fill: var(--mud-palette-warning);
    stroke: var(--mud-palette-text-primary);
    stroke-width: .2;
}

.ff-lgf-first {
    stroke: var(--mud-palette-warning);
    stroke-width: .4;
}

.ff-lgf-los {
    stroke: var(--mud-palette-info);
    stroke-width: .4;
}

.ff-lgf-ball {
    fill: var(--mud-palette-text-primary);
    stroke: var(--mud-palette-surface);
    stroke-width: .3;
}

/* ---- the drive chart ---- */

.ff-lgf-chart {
    display: flex;
    flex-direction: column;
    gap: 6px;
    min-width: 0;
}

.ff-lgf-sub {
    margin: 0;
    font-size: .82rem;
    font-weight: 700;
    letter-spacing: .02em;
    color: var(--mud-palette-text-secondary);
    text-transform: uppercase;
}

.ff-lgf-chartsvg {
    width: 100%;
    height: auto;
    display: block;
}

.ff-lgf-chartbg { fill: var(--mud-palette-background-gray); }

.ff-lgf-chartline {
    stroke: var(--mud-palette-lines-default);
    stroke-width: .2;
}

/* A bar's tint is an inline fill from the stored payload; this supplies the token stroke under it. */
.ff-lgf-bar {
    fill: var(--mud-palette-action-default);
    stroke: var(--mud-palette-lines-default);
    stroke-width: .2;
    opacity: .85;
}

.ff-lgf-bar.scored {
    stroke: var(--mud-palette-success);
    stroke-width: .5;
    opacity: 1;
}

/* ---- the deserve to win gauge ---- */

.ff-lgf-gauge {
    display: flex;
    flex-direction: column;
    gap: 4px;
    min-width: 0;
}

.ff-lgf-gaugesvg {
    width: 100%;
    height: .5rem;
    display: block;
    border-radius: 4px;
    overflow: hidden;
}

.ff-lgf-gauge-away { fill: var(--mud-palette-info); }

.ff-lgf-gauge-home { fill: var(--mud-palette-primary); }

.ff-lgf-gauge-legend {
    display: flex;
    justify-content: space-between;
    gap: 8px;
    font-size: .74rem;
    color: var(--mud-palette-text-secondary);
    min-width: 0;
}

.ff-lgf-basis {
    font-size: .72rem;
    line-height: 1.35;
    color: var(--mud-palette-text-secondary);
    min-width: 0;
}

/* ---- More live numbers ---- */

.ff-lgf-more {
    display: flex;
    flex-direction: column;
    gap: 8px;
    min-width: 0;
}

.ff-lgf-toggle {
    appearance: none;
    background: transparent;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 999px;
    color: var(--mud-palette-text-primary);
    cursor: pointer;
    font: inherit;
    font-size: .8rem;
    font-weight: 600;
    padding: 6px 14px;
    align-self: flex-start;
}

/* The panel is in the markup at every width. Below 960 it is hidden until a member opens it; at 960
   and wider the rule below shows it regardless and hides the button instead. */
.ff-lgf-panel {
    display: none;
    flex-direction: column;
    gap: 12px;
    min-width: 0;
}

.ff-lgf-panel.is-open { display: flex; }

/* ---- the tempo block ---- */

.ff-lgf-tempo {
    display: flex;
    flex-direction: column;
    gap: 6px;
    min-width: 0;
}

.ff-lgf-lens { margin: 0; }

.ff-lgf-scroll {
    overflow: auto;
    min-width: 0;
}

.ff-lgf-table {
    width: 100%;
    border-collapse: collapse;
    font-size: .78rem;
}

.ff-lgf-table th,
.ff-lgf-table td {
    padding: 4px 6px;
    text-align: left;
    vertical-align: top;
    border-bottom: 1px solid var(--mud-palette-lines-default);
}

.ff-lgf-table .num {
    text-align: right;
    font-variant-numeric: tabular-nums;
    white-space: nowrap;
}

.ff-lgf-table .nm {
    display: block;
    font-weight: 600;
}

.ff-lgf-table .bs {
    display: block;
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
}

.ff-lgf-longest {
    display: flex;
    flex-direction: column;
    gap: 6px;
    min-width: 0;
}

.ff-lgf-long {
    border-left: 2px solid var(--mud-palette-lines-default);
    padding-left: 8px;
    min-width: 0;
}

.ff-lgf-long .hd {
    display: flex;
    flex-wrap: wrap;
    gap: 4px 10px;
    font-size: .75rem;
    color: var(--mud-palette-text-secondary);
    min-width: 0;
}

.ff-lgf-long .gn {
    font-weight: 700;
    color: var(--mud-palette-text-primary);
    font-variant-numeric: tabular-nums;
}

.ff-lgf-long .tx {
    font-size: .78rem;
    overflow-wrap: anywhere;
    min-width: 0;
}

@media (max-width: 599.98px) {
    /* Eight numbers painted across a 360px wide picture are ink rather than information (plan §9.3). */
    .ff-lgf-num { display: none; }
}

@media (min-width: 960px) {
    /* D0-13 reads 1280, and this is 960 on purpose: the sheet has no breakpoint above 960 and must not
       gain one (plan §3.4), so "always open" begins at the breakpoint the sheet already has. Above it a
       live tap lands on 45F's full page instead, which is where the 1280 stage actually lives. */
    .ff-lgf-panel { display: flex; }
    .ff-lgf-toggle { display: none; }
}

/* ---- end Phase 45 45E ---- */


/* =================================================================================================
   Phase 47F: the passing profile panel, the passing strip and the situational usage splits

   GEOMETRY ONLY, AND BORROWED GEOMETRY AT THAT. Every colour below is a palette token and every
   figure sits in the same .ff-kv shaped line the shipped context panels use, so a charted passing
   figure reads as one more fact about a player rather than as a new kind of block. Nothing here
   introduces a chip shape, a band or a tint: a depth of target is not good or bad, it is deep or
   shallow, and colouring it would be this slice inventing a verdict the data does not carry.

   THE 360px RULE IS THE DEFAULT. .ff-passing-figures is one column at a phone width, becomes two at
   40rem and three at 120rem, which is the §9.3 matrix read exactly: two columns at 960 AND at 1280,
   three only at 1920. (Audit P47P-11: the third step shipped at 64rem, so a 1280px laptop rendered
   three columns where the ratified matrix says two.) No pixel value appears in any sizing declaration,
   every cap is in rem, nothing carries a min-width, and the game log scrolls inside the shipped
   .ff-table-scroll container rather than widening the page.
   ================================================================================================= */

.ff-passing-panel {
    min-width: 0;
}

.ff-passing-figures {
    display: grid;
    grid-template-columns: 1fr;
    gap: .5rem;
    min-width: 0;
}

@media (min-width: 40rem) {
    .ff-passing-figures {
        grid-template-columns: repeat(2, minmax(0, 1fr));
    }
}

@media (min-width: 120rem) {
    .ff-passing-figures {
        grid-template-columns: repeat(3, minmax(0, 1fr));
    }
}

.ff-passing-figure {
    display: flex;
    flex-direction: column;
    gap: .1rem;
    min-width: 0;
    padding: .4rem .5rem;
    border-radius: .35rem;
    background: var(--mud-palette-background-gray);
}

.ff-passing-figure .k {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

.ff-passing-figure .v {
    font-size: 1.05rem;
    font-weight: 600;
    color: var(--mud-palette-text-primary);
}

.ff-passing-figure .n {
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
}

.ff-passing-empty,
.ff-passing-note,
.ff-passing-explainer {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

.ff-passing-note {
    margin-top: .5rem;
}

/* The weekly detail page's one line. It stacks under itself on a phone and sits on one line once
   there is room, like the week-vs-average strip it lives beside. */
.ff-passing-strip {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: .35rem;
    min-width: 0;
    margin: .5rem 0;
}

.ff-passing-strip .k {
    font-size: .72rem;
    font-weight: 600;
    letter-spacing: .02em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-passing-strip .v {
    font-size: .85rem;
    color: var(--mud-palette-text-primary);
}

.ff-passing-strip .n {
    flex: 1 1 100%;
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
}

/* Phase 47A carry: the Splits tab's situational usage block. Same grid as the figures above, one
   column narrow and three wide, because these are the same kind of reading. */
.ff-usage-splits {
    min-width: 0;
}

.ff-usage-splits-row {
    display: grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
    gap: .4rem;
    min-width: 0;
}

@media (min-width: 40rem) {
    .ff-usage-splits-row {
        grid-template-columns: repeat(3, minmax(0, 1fr));
    }
}

.ff-usage-share {
    display: flex;
    flex-direction: column;
    gap: .1rem;
    min-width: 0;
}

.ff-usage-share .k {
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
}

.ff-usage-share .v {
    font-size: .95rem;
    font-weight: 600;
    color: var(--mud-palette-text-primary);
}

.ff-usage-splits-note {
    margin-top: .5rem;
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
}

/* ---- end Phase 47F ---- */
/* =================================================================================================
   Phase 47C: the per quarter usage and PPA strip on Player Detail (plan §5.3, §9.3).

   Appended as its own commented tail block, because app.css is passed between parallel slices and an
   edit into an earlier block is a merge conflict by construction.

   The block is a plain table because it IS a table (two measures over four quarters plus the game), and
   the only thing it needs from the stylesheet is that a five or six column table can never widen the
   page at phone widths: the scroll lives on the strip's own container, the page itself is never given
   an overflow rule of its own, and every cap here is in rem. Colours and type come from the palette
   tokens the rest of the page already uses.
   ================================================================================================= */
.ff-qstrip-scroll {
    overflow-x: auto;
    max-width: 100%;
}

.ff-qstrip-table {
    border-collapse: collapse;
    min-width: 18rem;
}

.ff-qstrip-table th,
.ff-qstrip-table td {
    padding: .35rem .6rem;
    text-align: right;
    white-space: nowrap;
}

.ff-qstrip-table th[scope="row"],
.ff-qstrip-table thead th:first-child {
    text-align: left;
}

.ff-qstrip-basis {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    margin-top: .35rem;
}
/* ---- end Phase 47C ---- */

/* =================================================================================================
   Phase 47D: the play by play attribution strip on Player Detail (plan §5.4, §9.3).

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner block below, which is where
   every slice's block goes: app.css is passed between parallel slices, an edit into an earlier block is
   a merge conflict by construction, and the UX-1 end marker has to stay the last block marker in the
   file (PickInFlightRoomTests pins exactly that, and six Phase 45 stylesheet tests pin the banner's
   byte offset).

   It is a plain table because it IS a table (one row per snap, four columns), and the only thing it
   needs from the stylesheet is that it can never widen the page at phone widths: the scroll lives on
   the strip's own container, the page itself is never given an overflow rule, and every cap is in rem.
   The play text column is the one that can run long, so it wraps inside its own width cap rather than
   pushing the numeric columns off the screen. Colours and type come from the palette tokens the rest of
   the page already uses.
   ================================================================================================= */
.ff-tstrip-scroll {
    overflow-x: auto;
    max-width: 100%;
}

.ff-tstrip-table {
    border-collapse: collapse;
    min-width: 20rem;
}

.ff-tstrip-table th,
.ff-tstrip-table td {
    padding: .35rem .6rem;
    text-align: right;
    white-space: nowrap;
    vertical-align: top;
}

.ff-tstrip-table th[scope="col"]:first-child,
.ff-tstrip-table td:first-child,
.ff-tstrip-table th[scope="col"]:last-child,
.ff-tstrip-table td:last-child {
    text-align: left;
}

/* The play's own description: the one value that runs long, capped and wrapped inside its own cell so
   a verbose snap cannot push the numbers out of view. */
.ff-tstrip-table td:last-child {
    white-space: normal;
    max-width: 22rem;
}

.ff-tstrip-join,
.ff-tstrip-basis {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    margin-top: .35rem;
}
/* ---- end Phase 47D ---- */

/* =============================================================================================
   Phase 45 45F (2026-09-13): the full page live mode

   The three column stage the matchup game page renders while its game is being played, and nothing
   else: every block INSIDE the columns is the sheet's own, drawn by the same components and styled by
   LG-2's .ff-lg-*, LG-5's .ff-lgd-* and 45E's .ff-lgf-* rules, which is what makes "one implementation
   of every block" true of the stylesheet as well as of the markup. This block owns the columns, their
   two headings, the room, and one override inside its own third column.

   ONE BREAKPOINT, AND IT IS THE TAP RULE'S OWN NUMBER. 1280px is where a live tap starts landing on
   this page (LiveTapDestination.PageWidthPx, D0-10), so it is also where this page becomes three
   columns: a tap that opened the page at a width where the page had not yet become a stage would be two
   answers to one question. Below it the grid is one column and the stage stacks in the phone order the
   sheet uses, which is why there is no second breakpoint here and none is wanted.

   THE ROOM IS THE ONE DESKTOP ONLY BLOCK (plan §6 45F). Below 1280 the week's game day room is hidden
   rather than stacked: a phone reading a live game has the room one tap away in the nav already, and a
   second route to it under the drives would be a column of chrome on the surface with the least room
   for it. With chat dark for the league the markup is not rendered at all, and the grid drops to two
   columns that fill the width.

   NO PIXEL MEASUREMENT ANYWHERE EXCEPT THE BREAKPOINT ITSELF. Every length here is rem, so the stage
   scales with a member who has made their text bigger, and the columns are fractions of whatever holds
   them rather than widths of their own. No rule declares a horizontal scroller: the one table inside
   the stage is the line score table, which scrolls inside LG-2's own container.

   COLOUR IS A PALETTE TOKEN. The only colour in this block is the column heading's secondary text, so
   both themes are correct by construction.
   ============================================================================================= */

.ff-lgs-stage {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    gap: 1rem;
    margin-bottom: 1rem;
}

.ff-lgs-col {
    display: flex;
    flex-direction: column;
    gap: .75rem;
    min-width: 0;
}

.ff-lgs-colhead {
    margin: 0;
    font-size: .72rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-lgs-room {
    display: none;
    flex-direction: column;
    gap: .5rem;
}

@media (min-width: 1280px) {
    /* Two columns with no room to show, three with one. In the two column case the people block flows
       under the game column, which is what "the column is absent and the other two fill the width"
       means in a grid: nothing is stretched to cover a hole. */
    .ff-lgs-stage { grid-template-columns: minmax(0, 1.15fr) minmax(0, 1fr); }

    .ff-lgs-stage.has-room {
        grid-template-columns: minmax(0, 1.15fr) minmax(0, 1fr) minmax(0, .95fr);
    }

    .ff-lgs-room { display: flex; }

    /* One member card per row inside the people column. LG-2's own grid pairs them at 960px, which is
       right for a 45rem dialog and wrong for a third of a page. */
    .ff-lgs-talk .ff-lg-members { grid-template-columns: minmax(0, 1fr); }
}

/* ---- end Phase 45 45F ---- */

/* =================================================================================================
   Phase 45 45G (2026-09-13): the board's live detail, the slate's live chips and the live game dock

   Three surfaces, one prefix. Everything this slice draws is .ff-lgk-* ("live game dock and kit"),
   which is deliberately NOT LG-2's .ff-lg-, LG-5's .ff-lgd-, 45E's .ff-lgf- or 45F's .ff-lgs-: the
   blocks are appended separately, so none may win a cascade against another by accident.

   360px FIRST. Nothing here declares a pixel width, a min-width or a second horizontal scroller. The
   ticker and the dock are flex rows that wrap at their gaps, every cap is in rem so it scales with a
   member who has made their text bigger, and every colour is a palette token so both themes are right
   by construction. A school's own colour never appears here: that is data, and it is an inline fill
   where it is drawn.

   THE DOCK SITS ABOVE THE DRAFT DOCK RATHER THAN UNDER IT. Both are fixed to the bottom of the app
   frame and both can legitimately be showing at once (a member can be mid draft on a Saturday), so the
   live game dock lifts by TURN-3's own --ff-dock-clearance whenever a draft dock is on the page. The
   variable is reused rather than re-measured, so the two bars cannot drift apart if either grows.

   Appended as its own bannered tail block, immediately before UX-1's banner, which has to remain the
   LAST end marker in this file (PickInFlightRoomTests pins that).
   ================================================================================================= */

/* ---- the board: the stored line under a roster row, and the pace strip's fourth cell ---- */

.ff-lgk-statline {
    display: block;
    width: 100%;
    font-size: .72rem;
    line-height: 1.25;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lgk-pacecell .v {
    color: var(--mud-palette-success);
}

/* ---- the board: the on the field ticker ---- */

.ff-lgk-ticker {
    display: flex;
    flex-direction: column;
    gap: .25rem;
    margin-top: .5rem;
}

.ff-lgk-ticker-hd {
    font-size: .68rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-lgk-ticker-row {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: .2rem .45rem;
    min-width: 0;
}

.ff-lgk-ticker-pos {
    flex: 0 0 2.2rem;
    font-size: .68rem;
    font-weight: 700;
    color: var(--mud-palette-text-secondary);
}

.ff-lgk-ticker-who {
    font-size: .8rem;
    font-weight: 600;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-lgk-ticker-line {
    flex: 1 1 100%;
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* ---- the slate: the live chips, and the last score on its own line ---- */

.ff-lgk-redzone {
    border-color: var(--mud-palette-error);
    color: var(--mud-palette-error);
}

.ff-lgk-pulse .dot {
    display: inline-block;
    width: .4rem;
    height: .4rem;
    margin-right: .3rem;
    border-radius: 50%;
    background: var(--mud-palette-success);
}

.ff-lgk-lastscore {
    flex: 1 1 100%;
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* ---- the live game dock ---- */

/* The fixed slot. It spans the viewport so the bar inside can centre itself, and it is click through
   everywhere but on the bar, so it never steals a press meant for the page behind it. */
.ff-lgk-dock {
    position: fixed;
    left: 0;
    right: 0;
    bottom: 0;
    z-index: 1150;
    box-sizing: border-box;
    display: flex;
    justify-content: center;
    padding: .5rem .75rem calc(.5rem + var(--ff-dock-safe-bottom));
    pointer-events: none;
}

/* Both docks can be showing at once, and this one is the newer signal, so it lifts above the draft
   dock rather than landing on top of it. */
body:has(.ff-draft-dock) .ff-lgk-dock {
    bottom: var(--ff-dock-clearance);
}

.ff-lgk-dock-bar {
    pointer-events: auto;
    box-sizing: border-box;
    display: inline-flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: center;
    gap: .15rem .5rem;
    max-width: 100%;
    min-height: 2.75rem;
    padding: .5rem 1.1rem;
    border-radius: 999px;
    border: 1px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-surface);
    color: var(--mud-palette-text-primary);
    cursor: pointer;
    text-align: center;
}

.ff-lgk-dock-bar:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
}

.ff-lgk-dock-dot {
    display: inline-block;
    width: .45rem;
    height: .45rem;
    border-radius: 50%;
    background: var(--mud-palette-success);
}

.ff-lgk-dock-lead {
    font-size: .78rem;
    font-weight: 700;
    letter-spacing: .02em;
}

.ff-lgk-dock-sep {
    color: var(--mud-palette-text-secondary);
}

.ff-lgk-dock-score {
    font-size: .8rem;
    font-weight: 600;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-lgk-dock-clock {
    font-size: .78rem;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
}

.ff-lgk-dock-mine {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

/* ---- end Phase 45 45G ---- */

/* =================================================================================================
   Phase 47G (2026-09-13): the rushing profile panel, its board explainer and the weekly rushing strip

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which every slice in this campaign does and which
   PickInFlightRoomTests pins by asserting that UX-1's end marker is the LAST block marker in the file.

   GEOMETRY ONLY, AND MOSTLY BORROWED GEOMETRY. The rushing panel renders through the same component and
   the same figure grid the passing panel does, so it reuses 47F's .ff-passing-figures rules rather than
   declaring a second identical grid: one implementation of the layout is the same argument as one
   implementation of the read. What is here is what is genuinely this family's own, which is the panel's
   own root class, the board's explainer line and the weekly strip.

   THE 360px RULE IS THE DEFAULT. The strip is a flex line that wraps as many times as it needs, its note
   takes a row of its own, and nothing here declares a width at all. No pixel value appears in any sizing
   declaration, every cap is in rem, and the panel's game log scrolls inside the shipped .ff-table-scroll
   container rather than widening the page.

   COLOUR IS A PALETTE TOKEN, so both themes are correct by construction. Nothing here tints a figure:
   a yards per carry is not good or bad, it is long or short, and colouring it would be this slice
   inventing a verdict the data does not carry.
   ================================================================================================= */

.ff-rushing-panel {
    min-width: 0;
}

.ff-rushing-explainer {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

/* The weekly detail page's one line, the passing strip's twin. Its note row carries the attribution
   sentence, which is why the note is a full-width row rather than a trailing clause: on a phone it is a
   sentence a member has to be able to read, not a tail that gets cut. */
.ff-rushing-strip {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: .35rem;
    min-width: 0;
    margin: .5rem 0;
}

.ff-rushing-strip .k {
    font-size: .72rem;
    font-weight: 600;
    letter-spacing: .02em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-rushing-strip .v {
    font-size: .85rem;
    color: var(--mud-palette-text-primary);
}

.ff-rushing-strip .n {
    flex: 1 1 100%;
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
}

/* ---- end Phase 47G ---- */

/* =================================================================================================
   Phase 48B (2026-09-13): pools, live

   The block above the settled standings on a pick'em pool page, and the one chip it adds to a live
   row on the research matchups slate.

   GEOMETRY ONLY, BORROWED. Every colour is a palette token and the matchups chip is the shipped
   .ff-ctx-chip pill untouched; what is here decides where a line sits and, at 360px, whether it sits
   at all. Borrowing the shipped chip is deliberate: a member should read the cover note as the same
   kind of fact they already read on that card, and a new pill shape would be a second answer to
   "what does a fact about this game look like".

   THE BREAKPOINTS ARE THE PLAN'S (§9.3) AND THEY WORK MOBILE FIRST. Under 600px the projected board
   is not rendered at all and the headline sentence carries the whole block, which is the plan's
   "collapsed, headline row only": a nine row leaderboard above the real one is the fastest way to
   make a 360px phone unreadable on the one afternoon this block exists for. At 600px the top three
   rows appear, and at 960px the rest of them do. Nothing is removed from the markup, so a screen
   reader and a test both still see the whole board.
   ================================================================================================= */

.ff-plv-card {
    display: flex;
    flex-direction: column;
    gap: .5rem;
    padding: .75rem;
    min-width: 0;
}

.ff-plv-title {
    font-size: .8rem;
    font-weight: 700;
    letter-spacing: .02em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-plv-headline {
    font-size: .9rem;
    font-weight: 600;
    overflow-wrap: anywhere;
}

.ff-plv-weights {
    font-size: .78rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-plv-basis {
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-plv-board {
    display: none;
    flex-direction: column;
    gap: .15rem;
}

.ff-plv-row {
    display: flex;
    align-items: baseline;
    gap: .4rem;
    font-size: .8rem;
    min-width: 0;
}

.ff-plv-row.me {
    font-weight: 700;
}

.ff-plv-rank {
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
    flex: 0 0 1.5rem;
}

.ff-plv-name {
    flex: 1 1 auto;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-plv-pts {
    font-variant-numeric: tabular-nums;
    flex: 0 0 auto;
}

.ff-plv-picks {
    display: flex;
    flex-direction: column;
    gap: .4rem;
}

.ff-plv-pick {
    display: flex;
    flex-direction: column;
    gap: .1rem;
    min-width: 0;
    border-left: .15rem solid var(--mud-palette-lines-default);
    padding-left: .5rem;
}

.ff-plv-pick-score {
    font-size: .76rem;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
    overflow-wrap: anywhere;
}

.ff-plv-pick-line {
    font-size: .82rem;
    overflow-wrap: anywhere;
}

.ff-plv-weight {
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
}

.ff-plv-empty {
    font-size: .78rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* The matchups slate's own chip. It is the shipped .ff-ctx-chip pill and this adds nothing but the
   figure alignment every other numeric chip on that card already has. */
.ff-plv-cover {
    font-variant-numeric: tabular-nums;
}

@media (min-width: 600px) {
    .ff-plv-board {
        display: flex;
    }

    .ff-plv-row:nth-child(n+4) {
        display: none;
    }
}

@media (min-width: 960px) {
    .ff-plv-row:nth-child(n+4) {
        display: flex;
    }
}

/* ---- end Phase 48B ---- */

/* =================================================================================================
   Phase 47H (2026-09-13): the target profile card and the matchup comparison's last three games line

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which every slice in this campaign does and which
   PickInFlightRoomTests pins by asserting that UX-1's end marker is the LAST block marker in the file.

   ALMOST NOTHING, AND THAT IS THE POINT. The target card renders through the SAME component, the same
   panel chrome and the same figure grid the passing and rushing cards do, so it reuses 47F's
   .ff-passing-figures rules rather than declaring a third identical grid. What is here is what is
   genuinely this slice's own: the card's root class, and the one small line that carries a school's
   last three charted games under its season value on the matchup comparison.

   THE 360px RULE IS THE DEFAULT. The trend line is a block of its own under the value it belongs to
   rather than a fourth and fifth table column, because a two team comparison with a trend column on
   each side is six columns wide and unreadable on a phone even inside a scroller. Nothing here declares
   a width at all, no pixel value appears in any sizing declaration, and the comparison keeps scrolling
   inside its shipped .ff-mg-scroll container rather than widening the page.

   COLOUR IS A PALETTE TOKEN, so both themes are correct by construction. Nothing here tints a figure: a
   target share is not good or bad, it is large or small, and a colour would be this slice inventing a
   verdict the data does not carry. The trend line is deliberately the secondary text colour, because it
   is a second reading of a row rather than the row's answer.
   ================================================================================================= */

.ff-pg-panel {
    min-width: 0;
}

/* The last three games line, under a season value on the matchup comparison and under the metric name
   in its header cell. A block of its own so it wraps as its own row at any width, and lighter than the
   value above it so the season figure stays the row's answer. */
.ff-pg-trend {
    display: block;
    margin-top: .1rem;
    font-size: .68rem;
    font-weight: 400;
    line-height: 1.25;
    color: var(--mud-palette-text-secondary);
}

/* ---- end Phase 47H ---- */

/* =================================================================================================
   Phase 48D (2026-09-13): the labelled reference facts, as chips

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which every slice in this campaign does and which
   PickInFlightRoomTests pins by asserting that UX-1's end marker is the LAST block marker in the file.

   ONE ROW, FIVE FACTS, NO WIDTH. Everything here is a wrapping flex row whose children may shrink to
   nothing, because the chips carry SENTENCES rather than labels: "12 of Alabama's 41 carries inside the
   20 were his" is a line of prose and a fixed width would either truncate it or push the page sideways.
   Nothing in this block declares a pixel value, a min-width or an overflow, so at 360px the chips fall
   onto as many lines as they need and the page body never scrolls horizontally.

   COLOUR IS A PALETTE TOKEN AND NEVER A VERDICT. Not one rule here tints a figure. A red zone share is
   not good or bad, it is large or small, and a colour would be this slice inventing a judgement the
   data does not carry, which is exactly what the phase's honesty contract forbids. The basis line under
   each chip is the secondary text colour because it is a second reading of the chip above it rather
   than the chip's answer.

   THE BASIS IS A BLOCK, NOT A SUFFIX. Every share here prints what it is a share of, and a denominator
   appended to the end of a sentence is a denominator a member's eye skips. It gets its own line inside
   the chip, at the same smaller size the rest of the product's basis captions use.
   ================================================================================================= */

.ff-rc-row {
    display: flex;
    flex-wrap: wrap;
    align-items: flex-start;
    gap: .4rem;
    min-width: 0;
    margin-top: .4rem;
}

/* One fact. Column, so the sentence and the population it is over stack rather than competing for a
   line, and it may shrink to nothing so a long sentence wraps inside the chip instead of widening it. */
.ff-rc-chip {
    display: flex;
    flex-direction: column;
    gap: .1rem;
    min-width: 0;
    max-width: 100%;
    padding: .3rem .55rem;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: .6rem;
    background: var(--mud-palette-surface);
}

.ff-rc-text {
    font-size: .78rem;
    line-height: 1.3;
    overflow-wrap: anywhere;
    color: var(--mud-palette-text-primary);
}

.ff-rc-basis {
    font-size: .68rem;
    line-height: 1.25;
    overflow-wrap: anywhere;
    color: var(--mud-palette-text-secondary);
}

/* The lens and the cold sentence are their own full width lines under the chips, so neither can read
   as a sixth fact. */
.ff-rc-lens,
.ff-rc-cold {
    flex: 1 1 100%;
    min-width: 0;
    font-size: .68rem;
    line-height: 1.3;
    overflow-wrap: anywhere;
    color: var(--mud-palette-text-secondary);
}

/* The board's adjusted rank cell. A second, quieter line under the raw rank it disagrees with, never a
   colour and never a bold: the disagreement is the information, and emphasising one half of it would be
   this column claiming to be the right one. */
.ff-rc-adj {
    display: block;
    font-size: .68rem;
    line-height: 1.25;
    color: var(--mud-palette-text-secondary);
}

/* ---- end Phase 48D ---- */

/* =============================================================================================
   Phase 48 (48A): the pace clock's sentence

   TWO PLACES, ONE VOICE. The Game Day pace strip gets one line under it saying what its "On the
   field" figure did, and the live game sheet's players block gets the reader's own sentences for
   that game. Both are composed on the SERVER by PaceClockService and rendered verbatim here, so the
   board and the sheet cannot word one game two ways.

   360px FIRST, and the geometry is the whole point of the block. The sentence sits OUTSIDE
   .ff-gd-pace rather than inside it, because a fourth item in that flex row would wrap the three
   cells onto four lines on a phone; on its own line it cannot. It then TRUNCATES rather than
   overflows: two lines at this line height and an ellipsis after them, so a long school name plus a
   damping clause can never push the panel sideways. No width, no flex basis and no overflow-x
   anywhere in this block, every measurement is in rem so it scales with a member who has enlarged
   their text, and every colour is a palette token so both themes are right by construction.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, which is where
   every tail block in this file goes: UX-1's end marker has to remain the LAST block marker in the
   sheet (PickInFlightRoomTests pins that), and a parallel slice appending its own region here is a
   merge conflict by construction rather than by accident.
   ============================================================================================= */

/* ---- the board: the one sentence under the pace strip ---- */

.ff-gdp-reason {
    display: -webkit-box;
    -webkit-line-clamp: 2;
    -webkit-box-orient: vertical;
    overflow: hidden;
    text-overflow: ellipsis;
    overflow-wrap: anywhere;
    margin: 0 0.875rem 0.625rem;
    min-width: 0;
    max-height: 2.6rem;
    font-size: 0.72rem;
    line-height: 1.3;
    color: var(--mud-palette-text-secondary);
}

/* ---- the live game sheet: my own sentences for the game on screen ---- */

.ff-gdp-sheetnotes {
    display: flex;
    flex-direction: column;
    gap: 0.25rem;
    margin: 0.25rem 0 0.5rem;
    min-width: 0;
}

.ff-gdp-sheetnote {
    display: -webkit-box;
    -webkit-line-clamp: 2;
    -webkit-box-orient: vertical;
    overflow: hidden;
    text-overflow: ellipsis;
    overflow-wrap: anywhere;
    min-width: 0;
    max-height: 2.6rem;
    font-size: 0.72rem;
    line-height: 1.3;
    color: var(--mud-palette-text-secondary);
}

/* ---- end Phase 48 48A ---- */

/* =============================================================================================
   Phase 45 45I (2026-09-13): the red zone mode on Game Day

   ONE PREFIX, AND DELIBERATELY NOT ONE OF THE FOUR ABOVE IT. Everything this slice draws is
   .ff-lgr-* ("live game red zone"), never LG-2's .ff-lg-, LG-5's .ff-lgd-, 45E's .ff-lgf-, 45F's
   .ff-lgs- or 45G's .ff-lgk-: the blocks are appended separately, so none may win a cascade against
   another by accident.

   THE TOGGLE IS A BUTTON WEARING A CELL. It sits in the pace strip beside the three cells that are
   divs, so it takes the strip's own .cell layout and this block only strips the user agent's button
   chrome off it. That is what keeps it in the keyboard order and gives it a real pressed state
   without the strip having to know a control is in it.

   360px FIRST. Nothing here declares a pixel width, a min-width or a second horizontal scroller, and
   there is no breakpoint at all: a row is a column, its head is a flex line that wraps at its gaps,
   and every long string (a school name, a situation line) is allowed to break inside a word. One rule
   is therefore right from 320px to 1920, which is also why the rows stack rather than tabulate.

   Every cap is in rem so it scales with a member who has made their text bigger, and every colour is
   a palette token so both themes are correct by construction.

   Appended as its own bannered tail block, immediately before UX-1's banner, which has to remain the
   LAST end marker in this file (PickInFlightRoomTests pins that).
   ================================================================================================= */

/* ---- the toggle in the pace strip ---- */

.ff-lgr-chip {
    appearance: none;
    box-sizing: border-box;
    border: 1px solid var(--mud-palette-lines-default);
    background: transparent;
    color: inherit;
    font: inherit;
    text-align: center;
    cursor: pointer;
    max-width: 100%;
    min-height: 2.25rem;
    border-radius: .5rem;
}

.ff-lgr-chip:hover {
    border-color: var(--mud-palette-error);
}

.ff-lgr-chip:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
}

/* Pressed. The word in the cell says which mode the board is in as well, so the tint is never the
   only carrier of the state. */
.ff-lgr-chip.on {
    border-color: var(--mud-palette-error);
    background: rgba(var(--mud-palette-error-rgb), .12);
}

.ff-lgr-chip.on .v {
    color: var(--mud-palette-error);
}

/* ---- the mode itself ---- */

.ff-lgr-mode {
    display: block;
    max-width: 100%;
}

/* The normal state for all but a few minutes of a Saturday, so it reads as a sentence rather than as
   an absence. */
.ff-lgr-empty {
    display: flex;
    align-items: center;
    gap: .5rem;
    padding: .75rem .25rem;
    font-size: .82rem;
    color: var(--mud-palette-text-secondary);
}

.ff-lgr-list {
    display: flex;
    flex-direction: column;
    gap: .5rem;
    max-width: 100%;
}

/* A row is a COLUMN, which is what makes it stack at 360px without a breakpoint and without ever
   needing a sideways scroller. */
.ff-lgr-row {
    box-sizing: border-box;
    display: flex;
    flex-direction: column;
    gap: .2rem;
    max-width: 100%;
    padding: .5rem .6rem;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: .5rem;
    background: var(--mud-palette-background-gray);
}

/* The one game this mode has registered a watch for. */
.ff-lgr-row.focus {
    border-color: var(--mud-palette-error);
}

.ff-lgr-head {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: .15rem .5rem;
    max-width: 100%;
}

.ff-lgr-zone {
    flex: 0 0 auto;
    padding: .05rem .4rem;
    border-radius: .35rem;
    font-size: .68rem;
    font-weight: 700;
    letter-spacing: .02em;
    text-transform: uppercase;
    color: var(--mud-palette-error);
    background: rgba(var(--mud-palette-error-rgb), .12);
}

.ff-lgr-score {
    font-size: .86rem;
    font-weight: 600;
    color: var(--mud-palette-text-primary);
    overflow-wrap: anywhere;
}

.ff-lgr-clock {
    font-size: .76rem;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
}

.ff-lgr-ball {
    font-size: .78rem;
    color: var(--mud-palette-text-primary);
    overflow-wrap: anywhere;
}

.ff-lgr-sit {
    font-size: .74rem;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lgr-mine {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* ---- end Phase 45 45I ---- */

/* =================================================================================================
   Phase 48C (2026-09-13): the week verdict strip and the luck ledger panel

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which is where every appended block in this campaign
   goes. UX-1's end marker has to remain the LAST block marker in the sheet
   (PickInFlightRoomTests.TheUx1Block_IsAppendedAtTheTailOfAppCss is the guard), so a block appended
   after it turns that guard red; a block inserted here cannot, and two parallel slices inserting at the
   same point conflict textually rather than silently.

   GEOMETRY ONLY, BORROWED. Both surfaces are .ff-panel with the shipped head and body, so a member
   reads them as the same kind of card they already read on these pages. Every rule below decides where
   a line sits and how it folds; every colour is a palette token, and there is not one pixel width
   anywhere, which is what makes 360px and both themes correct by construction rather than by luck of
   the draw.

   .ff-wv- IS THE VERDICT STRIP AND .ff-ll- IS THE LEDGER, and no selector in this block names anything
   else. Two prefixes rather than one because they are two surfaces on two pages; the guard trio in
   WeekVerdictStylesheetTests asserts that every selector part names one of them, so this block cannot
   reach into Matchups' .ff-mg- rules or the Regret engine's .ff-eff- rules from the tail of the sheet.

   THE CARDS WRAP RATHER THAN COLUMN COUNT. §9.3 wants one card a row at 360 and up to four at 1280,
   and a flex row whose items have a rem basis and may grow does that at every width in between without
   a single breakpoint or a single fixed column, which is also what keeps a long school name from
   pushing the page sideways.
   ================================================================================================= */

.ff-wv-panel {
    margin-bottom: 1rem;
}

.ff-wv-cards {
    display: flex;
    flex-wrap: wrap;
    gap: .6rem;
}

.ff-wv-card {
    flex: 1 1 16rem;
    min-width: 0;
    display: flex;
    flex-direction: column;
    gap: .15rem;
    padding: .55rem .7rem;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: .6rem;
    background: var(--mud-palette-background-gray);
}

/* The game the host page is showing leads the strip, and reads as the one it is about. */
.ff-wv-here {
    border-color: var(--mud-palette-primary);
}

.ff-wv-match {
    font-weight: 700;
    font-size: .82rem;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-wv-read {
    font-size: .78rem;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-wv-note {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-wv-gap {
    display: flex;
    flex-wrap: wrap;
    gap: .25rem .5rem;
    margin-top: .2rem;
}

.ff-wv-said {
    font-size: .78rem;
    font-weight: 600;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-wv-num {
    font-size: .74rem;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
}

.ff-wv-basis {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    margin-top: .45rem;
    min-width: 0;
    overflow-wrap: anywhere;
}

/* ---- the luck ledger ---- */

.ff-ll-panel {
    margin-bottom: 1rem;
}

.ff-ll-note {
    font-size: .88rem;
    min-width: 0;
    overflow-wrap: anywhere;
}

/* §9.3: the range is its own line at 360 and folds inline from 600 up. A wrapping flex row does both
   with no breakpoint: at 360 the two figures cannot both fit their rem basis and wrap. */
.ff-ll-figures {
    display: flex;
    flex-wrap: wrap;
    gap: .4rem .9rem;
    margin-top: .5rem;
}

.ff-ll-fig {
    flex: 1 1 9rem;
    min-width: 0;
    display: flex;
    flex-direction: column;
}

.ff-ll-fig .k {
    font-size: .7rem;
    letter-spacing: .02em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-ll-fig .v {
    font-size: 1.05rem;
    font-weight: 700;
    font-variant-numeric: tabular-nums;
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-ll-basis {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    margin-top: .4rem;
    min-width: 0;
    overflow-wrap: anywhere;
}

/* ---- end Phase 48C ---- */

/* =============================================================================================
   Phase 48 (48F): the clutch split's four rules

   GEOMETRY ONLY, AND BORROWED WHEREVER THERE WAS SOMETHING TO BORROW. The matchup row's caption, its
   basis lines, its scroll container and its table are the LG-6 block's own shipped classes, untouched,
   and the Scouting board is a RankedStatCard with no styling of its own at all. What is left is four
   rules that decide where a line sits, and nothing that decides what it looks like: a member should
   read the clutch row as the same kind of line they already read in that panel, and a new palette or a
   new table shape here would be a second answer to "what does a fact about this game look like".

   360px FIRST, which is why nothing below declares a width. Every rule is a min-width:0 so a long
   school name may shrink and wrap rather than push the panel sideways, and the one numeric cell is
   tabular so a column of figures lines up without being given a width to do it with. No pixel value,
   no breakpoint, no overflow-x: the wide table inside this block scrolls in the shipped .ff-mg-scroll
   container exactly as the two tables above it do.
   ============================================================================================= */

.ff-clu-block {
    margin-top: .75rem;
    min-width: 0;
}

.ff-clu-explainer {
    min-width: 0;
    overflow-wrap: anywhere;
    color: var(--mud-palette-text-secondary);
}

.ff-clu-caption {
    min-width: 0;
    overflow-wrap: anywhere;
    margin-bottom: .5rem;
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

.ff-clu-cell {
    font-variant-numeric: tabular-nums;
    white-space: nowrap;
}

/* ---- end Phase 48 48F ---- */

/* =================================================================================================
   Phase 47A: the game context and the market movement line on the Matchups slate

   Two rules, both about WHERE a line sits rather than what it looks like. Everything visual is
   inherited: the chips are .ff-ctx-chip inside .ff-mu-pills, exactly as the market pills above them
   are, and the movement sentence is the same muted note geometry .ff-mu-nomarket already defines.
   Borrowing the shipped geometry is deliberate. A member should read both as the same kind of line
   they already read on this card, and a new palette or a new chip shape here would be a second
   answer to "what does a fact about this game look like".

   .ff-mu-market is a wrapping flex row, so a block that belongs on its own line has to say so. Both
   take the full row width and nothing else, which is what makes them wrap below the pills at every
   width instead of competing with them for the same line at 360px.
   ================================================================================================= */

.ff-mu-ctx {
    width: 100%;
    min-width: 0;
}

.ff-mu-move {
    width: 100%;
    min-width: 0;
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

/* ---- end Phase 47A ---- */

/* =================================================================================================
   Phase 47B: the ratings shelf and the Teams hub season shape block

   GEOMETRY ONLY, BORROWED. Every colour here is a palette token and every chip inside the shelf is
   SignalChip's shipped .ff-ctx-chip .ff-signal-attr pill, untouched. The rules below decide where a
   line sits and how it folds, nothing else: a member should read a rating row as the same kind of
   line they already read on the Teams hub, and a new chip shape or a new palette would be a second
   answer to "what does a fact about this school look like".

   THE 360px RULE IS THE DEFAULT, NOT THE EXCEPTION. .ff-ratings-row is a column at narrow widths and
   becomes a row at 40rem, which is the ResponsiveList shape §9.3 asks for: a stacked card line on a
   phone, a wide row on a desktop. No pixel value appears in any sizing declaration, every cap is in
   rem, and nothing here can widen the page, because nothing here has a min-width.

   COLOUR CARRIES NOTHING. A rating's sign is not a band and is never tinted: the shelf prints six
   published models and deliberately makes none of them look more right than another (plan §4.2).
   ================================================================================================= */

.ff-ratings-shelf {
    display: block;
    min-width: 0;
}

.ff-ratings-head {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: .5rem;
    min-width: 0;
}

.ff-ratings-head .ttl {
    font-size: .78rem;
    font-weight: 600;
    letter-spacing: .02em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-ratings-head .hl {
    display: inline-flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: .35rem;
    min-width: 0;
}

.ff-ratings-head .hl .nm {
    font-size: .8rem;
    color: var(--mud-palette-text-secondary);
}

.ff-ratings-head .hl .vl {
    font-size: 1.05rem;
    font-weight: 600;
    color: var(--mud-palette-text-primary);
}

.ff-ratings-head .hl .rk {
    font-size: .8rem;
    color: var(--mud-palette-text-secondary);
}

.ff-ratings-panels {
    background: transparent;
}

.ff-ratings-rows {
    display: flex;
    flex-direction: column;
    gap: .4rem;
    min-width: 0;
}

/* Stacked at 360px, one wide row from 40rem up. The name and the two numbers keep their own columns
   on the wide form so six rows read as a table without being one. */
.ff-ratings-row {
    display: flex;
    flex-direction: column;
    gap: .15rem;
    min-width: 0;
    padding-block: .25rem;
    border-bottom: 1px solid var(--mud-palette-lines-default);
}

.ff-ratings-row:last-child {
    border-bottom: 0;
}

.ff-ratings-row .nm {
    font-size: .8rem;
    font-weight: 600;
    color: var(--mud-palette-text-primary);
}

.ff-ratings-row .vl {
    font-size: .85rem;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-primary);
}

.ff-ratings-row .rk {
    font-size: .75rem;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
}

.ff-ratings-row .cold {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

.ff-ratings-basis {
    min-width: 0;
}

.ff-ratings-note,
.ff-ratings-empty {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

.ff-ratings-note {
    margin-top: .4rem;
}

@media (min-width: 40rem) {
    .ff-ratings-row {
        flex-direction: row;
        flex-wrap: wrap;
        align-items: baseline;
        gap: .5rem;
    }

    .ff-ratings-row .nm {
        flex: 0 0 8rem;
        max-width: 100%;
    }

    .ff-ratings-row .vl {
        flex: 0 0 4.5rem;
        text-align: right;
    }

    .ff-ratings-row .rk {
        flex: 0 0 3.5rem;
        text-align: right;
    }

    .ff-ratings-row .cold {
        flex: 1 1 12rem;
    }
}

/* The Teams hub "season shape" and "last game" lines. Same .ff-kv geometry the three shipped context
   panels use, so the fourth column reads as one of them rather than as a new kind of block. */
.ff-season-shape-note {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    margin-top: .35rem;
}

.ff-lastgame-line {
    display: flex;
    flex-wrap: wrap;
    gap: .4rem;
    min-width: 0;
    margin-top: .5rem;
}

/* ---- end Phase 47B ---- */

/* =============================================================================================
   POST GAME PARITY (owner, 2026-09-13; Phase 45 plan D0-25) - the widened "How it unfolded"

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which is where every appended block goes: UX-1's
   end marker has to remain the last block marker in this file (PickInFlightRoomTests asserts it).

   THE BLOCK ADDS ALMOST NO LOOK. The finished panel now hosts the same three components the live
   stage hosts (the drive chart, the drive log with its twenty paired metrics, and the tempo
   counters), and every one of them brings its own .ff-lgf-* and .ff-lgd-* rules from earlier in
   this file. What is new here is only the three WRAPPERS that place them in the panel's one
   column, plus the line score table's total cell. Re-styling the hosted components for this
   placement would be a second look for one set of blocks, which is the drift the shared
   components exist to prevent.

   360px FIRST. Nothing here declares a width, and each wrapper carries min-width: 0 so a long
   drive result or a wide paired table shrinks its own column rather than widening the panel. The
   tables that can genuinely outgrow a phone (the reconstructed line score, an overtime game's
   extra columns) scroll inside .ff-mg-scroll, which is the MU-8 rule this page already follows;
   the hosted blocks scroll inside their own .ff-lgd-scroll and .ff-lgf-scroll containers.
   ============================================================================================= */

/* The three new wrappers, spaced exactly as .ff-lg6-drives is, so the panel reads as one stack
   rather than as an old half and a new one. */
.ff-lg6-lines,
.ff-lg6-full,
.ff-lg6-players {
    margin-top: 10px;
    min-width: 0;
}

/* The hosted blocks stack with the panel's own rhythm. gap rather than margins on the children,
   because the children are shared components and must not be reached into. */
.ff-lg6-full {
    display: flex;
    flex-direction: column;
    gap: 12px;
}

/* The line score's total column: the same emphasis the live stage's own table gives it, so the two
   tables read the same way. */
.ff-lg6-table .tot { font-weight: 700; }

/* ---- end post game parity ---- */

/* =============================================================================================
   PHONE METRIC COLUMNS (owner walk, 2026-09-13) - the tempo table and the paired live metrics
   at 360px

   WHAT THE OWNER SAW. On a 390px phone, the "Tempo and tendencies" table's Metric column had
   collapsed to about ninety pixels while the two value columns sat wide, so "Seconds between
   snaps" and the basis under it wrapped into an eight line sliver beside a number. The paired
   "Live team numbers" table was tight for the same reason and one school name away from the same
   shape.

   WHY IT HAPPENED. Both tables are width: 100% inside a scroll container with automatic layout,
   so the browser is free to squeeze any column whose content CAN wrap in order to honour the
   columns that cannot. The tempo table's value columns declare white-space: nowrap, which is
   right for a number and wrong for the SCHOOL NAME sitting in the same class in the header: two
   unbreakable team names took the width and the only wrappable column paid for it.

   THE RULE, AND IT IS THE COMPONENTS' OWN. Four small rules, all on .ff-lgf-* and .ff-lgd-*,
   which are the classes LiveGameTempo and LiveGameDrives carry everywhere. Fixing it here rather
   than on a host wrapper is what makes BOTH placements right at once: the live stage's "More live
   numbers" panel and the finished game's "Everything the drive log holds" block host the same two
   components, and a host scoped fix would have left the other one broken.

   NO BREAKPOINT, DELIBERATELY. A minimum width only binds where the width is actually short, so
   the rule is inert at desktop widths and needs no media query to be inert there; it then also
   holds for a narrow COLUMN on a wide screen, which a viewport query would have missed.

   NO SECOND SCROLLER. Nothing here declares overflow: the two tables already sit in
   .ff-lgf-scroll and .ff-lgd-scroll, which scroll in both axes, so a table that outgrows a phone
   scrolls inside its own container exactly as it did before and the page body never moves.

   THE SWEEP THAT FOUND NOTHING ELSE (same walk, the other new finished page blocks). The line
   score, the scoring drives table and the clutch board are .ff-lg6-table, whose cells are
   white-space: nowrap: they overflow into .ff-mg-scroll rather than collapsing a column, which is
   the shipped MU-8 behaviour. The players block, the drive log rows and the pace clock strip are
   flex lines with min-width: 0 and overflow-wrap: anywhere, so they reflow instead of squeezing.
   None of them needs this rule and none of them is touched by it.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, which is where
   every tail block in this file goes: UX-1's end marker has to remain the LAST block marker in
   the sheet (PickInFlightRoomTests pins that).
   ============================================================================================= */

/* Both tables grow to their own content instead of being squeezed into the container, and the
   scroll container each already sits in takes whatever will not fit. min-width keeps the ordinary
   case identical: a table whose columns fit still fills its container edge to edge. */
.ff-lgf-table,
.ff-lgd-table {
    width: auto;
    min-width: 100%;
}

/* The metric column cannot collapse below a readable line. It is the row's HEADER cell in both
   tables, carrying the metric name and the basis or direction under it, and it is the only column
   in either table whose content can wrap, which is exactly why it was the column that paid. */
.ff-lgf-table th[scope="row"],
.ff-lgd-table th[scope="row"] {
    min-width: 9rem;
}

/* A number stays on one line; a school name is not a number. The nowrap on .num is what the value
   COLUMNS want and what the header cells in the same class must not have, so the header is handed
   back its ability to wrap. The paired table already reads this way (its own thead rule wraps),
   which is why the owner found that one tight but readable and this one unreadable. */
.ff-lgf-table thead th.num {
    white-space: normal;
    overflow-wrap: anywhere;
}

/* And a value cell may break at a SPACE, which is a rule only a phrase can ever use: a figure like
   24.1 or 58% carries no space to break at, so it stays on one line by construction, while "18
   rush, 24 pass" stops holding a whole column open at its full width. Measured at 360px against
   the widest pair of school names in the FBS, it is the difference between a three line row and a
   two line one, and between a table that scrolls inside its container and one that fits. No
   overflow-wrap here, deliberately: that would let a long single token break mid figure. */
.ff-lgf-table tbody td.num {
    white-space: normal;
}

/* ---- end phone metric columns ---- */
/* =============================================================================================
   GAME PAGE LAYOUT (owner walk, 2026-09-13) - the drive chart, the collapsible sections and the
   two column finished game page

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which is where every appended block in this
   campaign goes: UX-1's end marker has to remain the last block marker in this file
   (PickInFlightRoomTests asserts it from the other side).

   THE OWNER'S THREE SENTENCES, IN ORDER. "The drive graphic needs some scaling for sure and no
   labels at all" is the .ff-dch block: a bar per drive at a FIXED row height in pixels, so
   twenty seven drives is about four hundred pixels rather than the two thousand an SVG whose box
   grew six units per drive was drawing, and real text at a real size on every row because an
   HTML row does not scale its type with its container. "Some of this stuff might need
   collapsible panels" is .ff-gsec. "Maybe on larger screens we can have some panels side by
   side" is the one media query at the end.

   ONE BREAKPOINT, AND IT IS THE PRODUCT'S OWN. The sections pair into two columns at exactly
   LiveTapDestination.PageWidthPx (1280), which is the same number the live stage's own layout
   uses and the same number GameSections chooses its default open set at. A page that paired its
   blocks at one width and opened them at another would be two answers to one question.

   360px FIRST. The chart's track is a percentage of whatever holds it and carries no width of
   its own; every row hides its own overflow so a badge at a goal line can never push the page
   sideways; the wide tables keep scrolling inside the .ff-mg-scroll, .ff-lgd-scroll and
   .ff-lgf-scroll containers they already had. The only pixel measurements here are HEIGHTS (the
   row, the chart's scroll cap, the chevron), which is what "a fixed row height" means.

   BOTH THEMES BY CONSTRUCTION. Every colour is a palette token or a translucent layer over one,
   with the single exception of a bar's tint, which is the school's own stored colour and arrives
   as an inline style from the payload rather than from this sheet.
   ============================================================================================= */

/* ---- the drive chart ------------------------------------------------------------------------ */

.ff-dch {
    display: flex;
    flex-direction: column;
    min-width: 0;
    border-radius: 8px;
    border: 1px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-background-gray);
}

/* The row's own two columns: the side's short name, then the hundred yards. The axis rows carry
   the same two, which is what keeps a tick over the yard line it names. */
.ff-dch-row,
.ff-dch-axis {
    display: grid;
    grid-template-columns: 3.4rem 1fr;
    align-items: center;
    column-gap: 6px;
    min-width: 0;
    padding: 0 8px;
}

/* A FIXED row height, which is the whole point of the rebuild: the list is as tall as the game
   was long and never as tall as the container is wide. */
.ff-dch-row {
    height: 14px;
    overflow: hidden;
    cursor: pointer;
}

.ff-dch-row:hover { background: rgba(var(--mud-palette-primary-rgb), .08); }

.ff-dch-row:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: -2px;
}

.ff-dch-row .tm {
    font-size: .58rem;
    line-height: 1;
    letter-spacing: .02em;
    color: var(--mud-palette-text-secondary);
    white-space: nowrap;
    overflow: hidden;
    text-overflow: ellipsis;
}

/* The hundred yards. Everything on it is placed as a percentage, so it is exactly as wide as the
   panel holding it at every viewport. */
.ff-dch-row .trk,
.ff-dch-axis .trk {
    position: relative;
    min-width: 0;
    height: 100%;
}

.ff-dch-bar {
    position: absolute;
    top: 50%;
    height: 8px;
    transform: translateY(-50%);
    border-radius: 2px;
    background: var(--mud-palette-action-default);
}

/* The honest neutral PAIR: a game where neither school published a colour still reads as two
   sides, because the two sides draw different neutrals. A school that did publish one overrides
   this with an inline background from the payload. */
.ff-dch-bar.home { background: var(--mud-palette-action-default); }

.ff-dch-bar.away { background: var(--mud-palette-text-disabled); }

/* A scoring drive is outlined rather than recoloured, so the school's own tint survives it and
   the mark is never carried by colour alone (the row also names the drive and its result). */
.ff-dch-bar.scored {
    outline: 1.5px solid var(--mud-palette-success);
    outline-offset: 0;
}

/* THE DIRECTION OF PLAY, on the bar's LEADING edge. The home side attacks the away end zone,
   which is the left of this axis, and the away side attacks the right. It is a second carrier of
   a fact the badge's own side already states and the tooltip spells out in words. */
.ff-dch-row.dir-left .ff-dch-bar { border-left: 3px solid var(--mud-palette-text-primary); }

.ff-dch-row.dir-right .ff-dch-bar { border-right: 3px solid var(--mud-palette-text-primary); }

/* The result, at the end the drive stopped at, hanging into the field rather than off it. */
.ff-dch-row .bdg {
    position: absolute;
    top: 50%;
    transform: translateY(-50%);
    padding: 0 3px;
    border-radius: 3px;
    background: var(--mud-palette-surface);
    color: var(--mud-palette-text-primary);
    font-size: .52rem;
    line-height: 1.4;
    letter-spacing: .04em;
    white-space: nowrap;
}

/* A labelled rule wherever the quarter changes: a line on its own says something changed and
   never what. */
.ff-dch-qtr {
    display: flex;
    align-items: center;
    gap: 6px;
    padding: 2px 8px;
}

.ff-dch-qtr::after {
    content: "";
    flex: 1 1 auto;
    border-top: 1px dashed var(--mud-palette-lines-default);
}

.ff-dch-qtr .lb {
    font-size: .56rem;
    letter-spacing: .08em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

/* The list scrolls inside ITSELF past the height a phone can hold, so a long game never turns
   the page into a scroll of one picture. Vertical only: nothing here can grow sideways. */
.ff-dch-rows {
    min-width: 0;
    max-height: 22rem;
    overflow-y: auto;
    overflow-x: hidden;
    padding: 4px 0;
}

/* The axis, top and bottom, so a member who has scrolled past one can still read the other. */
.ff-dch-axis {
    height: 16px;
    background: rgba(var(--mud-palette-primary-rgb), .06);
}

.ff-dch-axis:first-child { border-bottom: 1px solid var(--mud-palette-lines-default); }

.ff-dch-axis:last-child { border-top: 1px solid var(--mud-palette-lines-default); }

.ff-dch-axis .tk {
    position: absolute;
    top: 50%;
    transform: translate(-50%, -50%);
    font-size: .54rem;
    line-height: 1;
    color: var(--mud-palette-text-secondary);
    font-variant-numeric: tabular-nums;
}

/* Each end zone is named for the school that defends it, which is the field's own rule. */
.ff-dch-axis .ez {
    position: absolute;
    top: 50%;
    transform: translateY(-50%);
    max-width: 18%;
    font-size: .54rem;
    line-height: 1;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
    white-space: nowrap;
    overflow: hidden;
    text-overflow: ellipsis;
}

.ff-dch-axis .ez.l { left: 0; }

.ff-dch-axis .ez.r { right: 0; }

/* The tooltip a phone can reach, under the row a member tapped. */
.ff-dch-tip {
    margin: 2px 8px 4px;
    padding: 4px 6px;
    border-radius: 4px;
    background: var(--mud-palette-surface);
    color: var(--mud-palette-text-primary);
    font-size: .66rem;
    line-height: 1.35;
    overflow-wrap: anywhere;
}

/* ---- the drive log's card ------------------------------------------------------------------- */

/* One drive and whatever it opens, as one object. */
.ff-lgd-card {
    min-width: 0;
    border-radius: 6px;
}

.ff-lgd-card.is-open {
    background: rgba(var(--mud-palette-primary-rgb), .06);
    padding-bottom: 4px;
}

/* A scoring drive reads heavier, because a log of twenty seven identical rows is a wall. The
   word beside it is what carries the fact where weight cannot. */
.ff-lgd-drive.scored { font-weight: 600; }

.ff-lgd-drive.scored .res { color: var(--mud-palette-text-primary); }

/* The summed EPA in the card's HEADER, which is where a member looks for the number that
   describes the thing they just opened. By the SIGN and never by the magnitude. */
.ff-lgd-drive .ep {
    margin-left: auto;
    font-size: .66rem;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
}

.ff-lgd-drive .ep.up { color: var(--mud-palette-success); }

.ff-lgd-drive .ep.down { color: var(--mud-palette-error); }

.ff-lgd-detail {
    display: flex;
    flex-direction: column;
    gap: 4px;
    min-width: 0;
    padding: 4px 8px 0 14px;
}

/* D0-14's other half: the caption that says whose numbers the header's figure is made of. */
.ff-lgd-epabasis {
    font-size: .6rem;
    color: var(--mud-palette-text-secondary);
}

/* ---- the collapsible sections ---------------------------------------------------------------- */

.ff-gsec {
    min-width: 0;
    border-top: 1px solid var(--mud-palette-lines-default);
}

.ff-gsec-head {
    display: flex;
    align-items: baseline;
    gap: 8px;
    width: 100%;
    min-width: 0;
    padding: 8px 2px;
    appearance: none;
    background: transparent;
    border: 0;
    color: inherit;
    font: inherit;
    text-align: left;
    cursor: pointer;
}

.ff-gsec-head:hover .ff-gsec-ttl { color: var(--mud-palette-primary); }

.ff-gsec-head:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
    border-radius: 4px;
}

.ff-gsec-ttl {
    flex: 0 0 auto;
    font-size: .74rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

/* The summary is the point of the header: it has to be true while the section is shut, so it
   gets the room and shrinks before the heading does. */
.ff-gsec-sum {
    flex: 1 1 auto;
    min-width: 0;
    font-size: .74rem;
    color: var(--mud-palette-text-primary);
    overflow-wrap: anywhere;
}

/* A border triangle rather than an icon component, so the component carries no dependency. */
.ff-gsec-chv {
    flex: 0 0 auto;
    align-self: center;
    width: 0;
    height: 0;
    border-left: 4px solid transparent;
    border-right: 4px solid transparent;
    border-top: 5px solid var(--mud-palette-text-secondary);
}

.ff-gsec.is-open .ff-gsec-chv {
    border-top: 0;
    border-bottom: 5px solid var(--mud-palette-primary);
}

.ff-gsec-body {
    min-width: 0;
    padding-bottom: 10px;
}

/* ---- the scoring list's play by play ---------------------------------------------------------- */

/* Two lines, and the rest on a tap. The whole text is in the markup either way. */
.ff-lg6-scoring-row .play {
    cursor: pointer;
}

.ff-lg6-scoring-row .play.clamp {
    display: -webkit-box;
    -webkit-line-clamp: 2;
    line-clamp: 2;
    -webkit-box-orient: vertical;
    overflow: hidden;
}

.ff-lg6-scoring-row .play:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
    border-radius: 4px;
}

/* ---- the phone's own measurements -------------------------------------------------------------- */

@media (max-width: 600px) {
    /* A shorter row, so twenty seven drives is about three hundred and twenty pixels, and a
       shorter scroll cap because a phone holds fewer rows before the picture owns the screen. */
    .ff-dch-row { height: 12px; }

    .ff-dch-rows { max-height: 18rem; }

    .ff-dch-row,
    .ff-dch-axis { grid-template-columns: 2.8rem 1fr; }

    .ff-dch-bar { height: 7px; }
}

/* ---- side by side on a large screen ------------------------------------------------------------ */

/* THE ONE BREAKPOINT, and it is LiveTapDestination.PageWidthPx. Below it the page is the single
   column it has always been at every width. */
@media (min-width: 1280px) {
    .ff-lg6-unfolded {
        display: grid;
        grid-template-columns: 1fr 1fr;
        align-items: start;
        column-gap: 24px;
    }

    /* The two wrappers are made transparent to the grid so their children pair with the sections
       around them rather than stacking inside a column of their own. Neither carries a border, a
       background or a scroller of its own, which is what makes that safe. */
    .ff-lg6-drives,
    .ff-lg6-full { display: contents; }

    /* Everything that is a statement about the whole panel spans it. */
    .ff-lg6-unfolded > .ff-lg6-h,
    .ff-lg6-unfolded .ff-lg6-lens,
    .ff-lg6-unfolded .ff-lg6-basis,
    .ff-lg6-unfolded .ff-lg6-full > .ff-lg6-cap { grid-column: 1 / -1; }

    /* The chart has room for a taller list here than a phone can hold. */
    .ff-dch-rows { max-height: 28rem; }
}

/* ---- end game page layout ---- */


/* =============================================================================================
   GAME PAGE CORRECTNESS (owner walk, 2026-09-14) - the labels and the paired panels

   Three presentation halves of one walk over a finished game page. The correctness half of that
   walk is all server side; these are the rules the markup it changed needs.

   1. THE RETURN KIND ON A LONGEST PLAY. A 95 yard interception return now names the team that ran
      it back and says what kind of gain it was, so the row carries one more chip than it did.

   2. THE PROJECTION LABEL. A player card printed a big number, a range and "ACTUAL 24.7", and only
      the middle one of the three said what it was. The number is now labelled the way the actual
      chip beside it already labels itself, which means the label has to be the SMALL half of the
      pair and the number the large one, inside an element that used to hold only the number.

   3. THE TWO DEFENCE VS POSITION PANELS, EQUAL HEIGHT. Side by side from 960px, one of them a card
      taller than the other whenever its cells carried the "fewer than 3 games sampled" sentence,
      so the pair read as two unrelated blocks instead of one row. The grid items stretch and the
      panel inside each one grows to fill its item, which is the whole fix; the three cards inside
      a panel are told to stretch for the same reason one row down.

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which is where every appended block in this file
   goes: UX-1's end marker has to remain the LAST block marker in the sheet, and PickInFlightRoomTests
   asserts that from the other side.

   360px FIRST, and by construction rather than by a query: every rule here is either a chip's
   typography or a stretch inside a container that is already ONE column at phone width, so the
   stacked render is byte for byte what it was. No breakpoint of its own, no pixel size, and the
   only colour is a palette token on the new chip.
   ============================================================================================= */

/* ---- 1: what kind of gain the yards on a longest play were ---- */

/* The chip sits in the same header row as the gain, the team and the clock, and inherits that row's
   secondary colour; it is only told to hold together as one phrase. */
.ff-lgf-long .kd {
    font-style: italic;
    white-space: nowrap;
}

/* ---- 2: the projection is labelled, on both cards of the players lens ---- */

/* The projection cell now holds a label and a value rather than a bare number, so it becomes a row
   of its own. It keeps the margin-left:auto and the type scale it already had, from the base rules
   earlier in this file; only the arrangement of its two children is new. */
.ff-ml-rowhead .pj,
.ff-ml-defhead .pj {
    display: inline-flex;
    align-items: baseline;
    gap: 5px;
    min-width: 0;
}

/* The label is the quiet half, matching the actual chip's own label beside it so the two read as a
   pair rather than as two different kinds of thing. */
.ff-ml-rowhead .pj .lbl,
.ff-ml-defhead .pj .lbl {
    font-size: .62rem;
    font-weight: 600;
    text-transform: uppercase;
    letter-spacing: .04em;
    color: var(--mud-palette-text-secondary);
}

/* The number keeps the weight and the tabular figures the cell used to carry on its own. */
.ff-ml-rowhead .pj .val,
.ff-ml-defhead .pj .val {
    font-weight: 700;
    font-variant-numeric: tabular-nums;
}

/* ---- 3: the two defence vs position panels read as one row ---- */

/* Stated rather than left to the default: it is the declaration the rest of this section depends
   on, and a later edit that changed it would silently undo the fix. */
.ff-ml-dvp {
    align-items: stretch;
}

/* Each side becomes a column so its panel can be told to take the room the head does not. At phone
   and tablet width the grid is one column, so each item is its own row and this is inert. */
.ff-ml-dvp .ff-ml-side {
    display: flex;
    flex-direction: column;
}

.ff-ml-dvp .ff-ml-side > .ff-panel {
    flex: 1 1 auto;
    display: flex;
    flex-direction: column;
    min-width: 0;
}

.ff-ml-dvp .ff-ml-side > .ff-panel > .ff-panel-body {
    flex: 1 1 auto;
}

/* And the three cards inside one panel line up with each other, so the taller sentence lengthens
   the row rather than one card in it. Below 600px the card grid is a single column and each card is
   its own row, so this is inert there too. */
.ff-ml-dvp .ff-dvp-cards {
    align-items: stretch;
}

.ff-ml-dvp .ff-dvp-card {
    display: flex;
    flex-direction: column;
}

/* ---- end game page correctness ---- */

/* =============================================================================================
   Player hub findings (owner review, 2026-09-14)

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which is where every appended block in this file
   goes: UX-1's end marker has to remain the last block marker in this file.
   ============================================================================================= */

/* The board's trend tag now names the season it was measured against ("COLD VS 2025"), because the
   board's basis can be the season before this one (#924) while a profile's own form line is about
   the current one, and one word was standing for both. The tag needs more than the 46px the fixed
   grid gave "COLD", so the track widens and the flexible school column absorbs it.

   DESKTOP ONLY, and behind a min-width so it can never reach the phone grid declared earlier in this
   file: at 640px and below the cell prints a single letter and the basis lives in the title. The row
   still lays out on one line at every width, which is the rule the fixed tracks exist to keep. */
@media (min-width: 641px) {
    .ff-draft-row {
        grid-template-columns: 30px minmax(0, 1.4fr) 46px minmax(0, 1fr) 84px 50px 84px;
    }
}

/* The trend tag's own text: one line, never wrapped into a second row of the board. */
.ff-draft-trend .ff-trend-full { white-space: nowrap; }

/* ---- end player hub findings ---- */


/* ---------------------------------------------------------------------------------------------
   The Teams hub Games tab (owner walk 2026-09-14, finding 5)

   One school's season of real games. Three zones per row: WHEN (the week the league calls it, and
   the date in the viewer's own timezone), WHO (the opponent, a link into that game's page), and the
   chips (the final or the upcoming marker, the band when the page holds one for that game, and the
   neutral site marker).

   Desktop is a three column grid so the weeks line up down the left and the chips down the right,
   which is what makes a season scannable. Under 600px the grid collapses to ONE column, the week and
   the date share a line, and the chips wrap to the left rather than hanging off the right edge: at
   360px a three column row either overflows or squeezes the opponent name to nothing, and members
   read this page from their phones.
   --------------------------------------------------------------------------------------------- */

.ff-team-games {
    display: flex;
    flex-direction: column;
}

.ff-team-game {
    display: grid;
    grid-template-columns: minmax(110px, 150px) minmax(0, 1fr) auto;
    align-items: center;
    gap: 4px 12px;
    padding: 7px 2px;
    border-bottom: 1px solid var(--mud-palette-divider);
}

.ff-team-game:last-child {
    border-bottom: 0;
}

.ff-team-game-when {
    display: flex;
    flex-direction: column;
    line-height: 1.3;
}

.ff-team-game-when .wk {
    font-weight: 600;
    font-size: .8rem;
}

.ff-team-game-when .dt {
    color: var(--mud-palette-text-secondary);
    font-size: .75rem;
}

/* min-width:0 is what lets a long school name wrap inside its grid track instead of widening it. */
.ff-team-game-who {
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-team-game-chips {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: flex-end;
    gap: 4px;
}

@media (max-width: 599.98px) {
    .ff-team-game {
        grid-template-columns: 1fr;
        gap: 2px;
        padding: 9px 2px;
    }

    .ff-team-game-when {
        flex-direction: row;
        align-items: baseline;
        gap: 8px;
    }

    .ff-team-game-chips {
        justify-content: flex-start;
    }
}

/* ---- end Teams hub games tab ---- */


/* =============================================================================================
   Matchups school filter and All weeks (owner intake, 2026-09-14)

   TWO ELEMENTS, ONE PREFIX. Everything this slice draws is .ff-mu-, which is the Matchups slate's
   own prefix, because both elements live inside that slate and nowhere else: the week heading that
   groups the season view, and the autocomplete's no-match line. Nothing here reaches outside the
   page, and nothing redefines a rule the slate's own block already sets.

   THE FIFTH CONTROL NEEDED NO NEW RULE, which is the point worth recording. The toolbar's fold is
   POSITIONAL (.ff-mu-toolbar.ff-mu-collapsed hides from the third child at tablet width and from the
   SECOND at 360px), so a fifth picker folds under the Filters toggle by the rule that is already
   there: at 360px the sort is the only control on screen and the school, the conference, the band and
   the week all wrap away behind the toggle. A rule counting controls would have had to be edited
   every time one arrived, which is exactly the trap the positional form avoids.

   360px FIRST. Nothing in this block declares a pixel width, a min-width or a second horizontal
   scroller. The heading is a plain block that wraps, and its one size is in rem so it scales with a
   member who has made their text bigger.

   BOTH THEMES BY CONSTRUCTION: every colour is a palette token, and the heading's rule under it is a
   palette line rather than a hairline of its own.

   Appended as its own bannered tail block, immediately before UX-1's banner, which has to remain the
   LAST end marker in this file (PickInFlightRoomTests pins that).
   ============================================================================================= */

/* The season view's week heading. It is a heading rather than a chip because it names a GROUP of
   cards below it, and the rule under it is what makes the group visible without a box around it. */
.ff-mu-weekhead {
    margin: 14px 0 2px;
    padding-bottom: 6px;
    border-bottom: 1px solid var(--mud-palette-lines-default);
    color: var(--mud-palette-text-primary);
    font-size: .95rem;
    font-weight: 600;
    letter-spacing: .01em;
    overflow-wrap: anywhere;
}

/* The first group sits directly under the controls, which already carry their own spacing. */
.ff-mu-weekhead:first-child {
    margin-top: 0;
}

/* The school picker's empty result. It says why rather than only that, because the commonest cause
   is the conference filter above it. */
.ff-mu-noschool {
    padding: 8px 12px;
    color: var(--mud-palette-text-secondary);
    font-size: .85rem;
}

/* ---- end Matchups school filter ---- */


/* ================================================================================================
   Owner walk 2026-09-14: the Home edge pointer's shimmer, and the My Team panel's week line.

   TWO PROBLEMS, ONE PAGE. The edge pointer card's aggregate took fifteen to twenty seconds to answer
   and the card rendered nothing at all until it did, so the dashboard reflowed under the reader when
   it finally arrived. And the My Team panel listed a finished week's roster under a bare "My Team",
   which reads as the current lineup on a page whose next draft is two days away.

   Both fixes are additive: nothing here restyles an element that already had a rule, so the panels,
   the tile row and the pointer card keep their existing geometry to the pixel.

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which every recent slice does and which the stylesheet
   guards pin by asserting that UX-1's end marker is the LAST block marker in the file. It is still a
   tail block for merge purposes (nothing above it moves), and it is still one contiguous commented
   region, so two parallel slices land beside each other rather than on top of each other.
   ------------------------------------------------------------------------------------------------ */

/* The shimmer stands in the link's place so the row does not grow when the real link lands. It is a
   span rather than an anchor (there is nowhere to go yet), so it needs the layout half of the link
   rule and none of the colour half. */
.ff-edge-pointer-card .ff-edge-pointer-link-pending {
    display: inline-flex;
    align-items: center;
    min-height: 44px;
    margin-top: -8px;
}

/* The week and state note in the My Team panel head. It shares a wrapper with the title so the head
   keeps its two children and its space-between geometry, and the wrapper WRAPS: on a wide panel the
   note sits beside "My Team", and at 360px it drops to its own line under it rather than truncating
   the one fact the line exists to carry or squeezing the Details button's tap target. */
.ff-myteam-title {
    display: flex;
    align-items: baseline;
    flex-wrap: wrap;
    gap: 2px 10px;
    min-width: 0;
}

.ff-panel-head .ff-myteam-week {
    min-width: 0;
    overflow-wrap: anywhere;
}

/* The one-line pointer at a draft that has not happened yet, under the roster rows. Separated by a
   hairline rather than a gap, because it is a different KIND of fact from the slots above it. */
.ff-myteam-next {
    display: flex;
    align-items: center;
    gap: 8px;
    padding: 10px 10px 6px;
    margin-top: 4px;
    border-top: 1px solid var(--mud-palette-lines-default);
    font-size: .82rem;
}

.ff-myteam-next .mud-icon-root { color: var(--mud-palette-text-secondary); }

/* ---- end owner walk 2026-09-14 ---- */

/* =================================================================================================
   FOOT-1 (owner report, 2026-09-16): a fixed bottom bar reserves its room, and the second bar joins
   every lift the first one already had

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which is where every appended block in this file goes:
   UX-1's end marker has to remain the LAST block marker in the sheet and PickInFlightRoomTests pins
   that.

   THE REPORT. The authenticated site footer was not sitting at the bottom of the page. The producer was
   TURN-3's own coordination rule: it reserved the dock's room with padding-bottom on
   .ff-appshell .mud-main-content, and the footer is the LAST item inside that content area, so the
   reservation landed below the footer as a 76px strip of page background. The strip is per league in
   practice because the draft dock is current league scoped, so a league with a live draft carried it and
   a league without one did not. The owner had already ruled on this exact trade once, on the
   scroll-to-top FAB on 2026-08-03: a slight overlap beats an empty band (see SiteFooter.razor.css).

   THE MECHANISM. The room is now reserved inside the footer's own padding-bottom rather than under it.
   The footer therefore still reaches the bottom of the page, which is what an actual footer means, and
   its last text row still sits above the bar. Nothing else moves: the FAB, the snackbars, the point-type
   save bar and the framework error strip keep TURN-3's own lifts, and the page's own last row is above
   the footer's margin-top, its height and its padding, so it clears the bar by more than it used to.

   WHY GLOBAL AND NOT SiteFooter.razor.css. .ff-sitefooter--appshell is authored in SiteFooter.razor, so
   a scoped rule COULD reach it, but the condition cannot: the docks are rendered by MainLayout, outside
   that component, so only a rule anchored on body can see them. Specificity is deliberate too: the
   scoped .ff-sitefooter--appshell[b-xxxxx] rule is (0,2,0) and body:has(.ff-draft-dock)
   .ff-sitefooter--appshell is (0,2,1), so these win without !important.

   THE SUM. Both bars can be up at once (a member mid draft on a Saturday). 45G lifts the game dock above
   the draft dock by the draft dock's own clearance, so when both are present everything below has to
   clear the two stacked, which is what every :has(.ff-draft-dock):has(.ff-lgk-dock) rule here does. Each
   clearance is named once and reused rather than re-measured, so the bars and the things above them
   cannot drift apart if either grows a line.

   THE SECOND HALF, ADDED IN THE SAME ROUND. TURN-3 §9.4 enumerated four FLOATING affordances that lift
   clear of a bar (the scroll-to-top FAB at each of its own two offsets, bottom snackbars, the point-type
   save bar and the framework error strip), and every one of those rules is gated on the draft dock alone.
   45G then shipped a second bar and joined none of them, so with a live game dock up and no draft dock
   the FAB sat 44px inside the bar and the other three sat under it. The game dock now has the same four
   lifts and the same stacked pair, which is the whole of TURN-3's contract rather than the half of it
   that happened to be written first. TURN-3's own rules are untouched: a page with only a draft dock on
   it behaves exactly as it did.

   THE BASE STAYS. The 2rem / 1.75rem already in the footer is the FAB's clearance and is still wanted:
   with a dock up, TURN-3 lifts the FAB ABOVE the dock, so the footer has to clear the dock and then the
   FAB on top of it.

   360px FIRST. Nothing here declares a width, every value is a rem or an existing clearance variable, and
   the phone breakpoint is the footer's own 599.98px so the two cannot drift.
   ================================================================================================= */

:root {
    /* The live game dock's rendered height, which is its 2.75rem bar plus its own .5rem of padding above
       and below, plus the same 12px breathing gap TURN-3 gave the draft dock. 45G never named this, so it
       is named here and the dock's own padding line is the thing to keep it honest against. The safe-area
       inset is the same one --ff-dock-clearance reserves, for the same reason: an iPhone's home indicator
       is not free space. One value covers both breakpoints because the dock is sized entirely in rem. */
    --ff-lgk-dock-clearance: calc(3.75rem + 12px + var(--ff-dock-safe-bottom));
}

body:has(.ff-draft-dock) .ff-sitefooter--appshell {
    padding-bottom: calc(2rem + var(--ff-dock-clearance));
}

body:has(.ff-lgk-dock) .ff-sitefooter--appshell {
    padding-bottom: calc(2rem + var(--ff-lgk-dock-clearance));
}

/* Both bars up: the game dock is sitting on top of the draft dock, so the footer clears the pair. */
body:has(.ff-draft-dock):has(.ff-lgk-dock) .ff-sitefooter--appshell {
    padding-bottom: calc(2rem + var(--ff-dock-clearance) + var(--ff-lgk-dock-clearance));
}

/* ---- the game dock joins TURN-3's four floating lifts (§9.4, mirrored) ---- */

/* The floating scroll-to-top FAB, lifted at each of its own two offsets so it keeps the spacing it was
   tuned to, exactly as TURN-3 does for the draft dock. The phone offset is in the breakpoint below. */
body:has(.ff-lgk-dock) .ff-scroll-top {
    bottom: calc(1.5rem + var(--ff-lgk-dock-clearance));
}

body:has(.ff-draft-dock):has(.ff-lgk-dock) .ff-scroll-top {
    bottom: calc(1.5rem + var(--ff-dock-clearance) + var(--ff-lgk-dock-clearance));
}

/* Snackbars. The container is portalled to the document body, which is why this whole family is written
   with :has() rather than a sibling selector: nothing inside the layout can reach it. */
body:has(.ff-lgk-dock) [class*="mud-snackbar-location-bottom"] {
    padding-bottom: var(--ff-lgk-dock-clearance);
}

body:has(.ff-draft-dock):has(.ff-lgk-dock) [class*="mud-snackbar-location-bottom"] {
    padding-bottom: calc(var(--ff-dock-clearance) + var(--ff-lgk-dock-clearance));
}

/* The point-type editor's save bar, the product's other bottom-anchored action. It is sticky on a
   desktop and fixed on a phone, and both forms resolve their offset against the same bottom edge. */
body:has(.ff-lgk-dock) .ff-pt-savebar {
    bottom: var(--ff-lgk-dock-clearance);
}

body:has(.ff-draft-dock):has(.ff-lgk-dock) .ff-pt-savebar {
    bottom: calc(var(--ff-dock-clearance) + var(--ff-lgk-dock-clearance));
}

/* The framework's own unhandled-error strip. It is hidden until something has gone badly wrong, and when
   it appears it must not be the thing hiding behind a bar. */
body:has(.ff-lgk-dock) #blazor-error-ui {
    bottom: var(--ff-lgk-dock-clearance);
}

body:has(.ff-draft-dock):has(.ff-lgk-dock) #blazor-error-ui {
    bottom: calc(var(--ff-dock-clearance) + var(--ff-lgk-dock-clearance));
}

/* The phone breakpoint, matching the footer's own (SiteFooter.razor.css drops the base to 1.75rem here
   because the FAB sits at 1rem rather than 1.5rem on a phone). Same specificity as the rules above and
   later in the sheet, so these win inside the breakpoint. Only the two surfaces with a breakpoint of
   their own are repeated here: the footer and the FAB. The snackbar, the save bar and the error strip
   resolve against the bottom edge itself at every width, so one rule each covers them. */
@media (max-width: 599.98px) {
    body:has(.ff-draft-dock) .ff-sitefooter--appshell {
        padding-bottom: calc(1.75rem + var(--ff-dock-clearance));
    }

    body:has(.ff-lgk-dock) .ff-sitefooter--appshell {
        padding-bottom: calc(1.75rem + var(--ff-lgk-dock-clearance));
    }

    body:has(.ff-draft-dock):has(.ff-lgk-dock) .ff-sitefooter--appshell {
        padding-bottom: calc(1.75rem + var(--ff-dock-clearance) + var(--ff-lgk-dock-clearance));
    }

    body:has(.ff-lgk-dock) .ff-scroll-top {
        bottom: calc(1rem + var(--ff-lgk-dock-clearance));
    }

    body:has(.ff-draft-dock):has(.ff-lgk-dock) .ff-scroll-top {
        bottom: calc(1rem + var(--ff-dock-clearance) + var(--ff-lgk-dock-clearance));
    }
}
/* ---- end FOOT-1 ---- */

/* =============================================================================================
   52J - the dock clearance contract, published as one opt-in class (Phase 52 plan section 5.10)

   WHAT THIS IS. A scrolling region whose visible area reaches the bottom of the viewport has the
   footer's problem: a fixed bottom bar sits on top of its last row. FOOT-1 (owner, 2026-09-16)
   settled how that room gets reserved. A fixed bottom bar reserves its room INSIDE the box that
   would otherwise be covered, never as padding on the content area, because padding on the content
   area lands BELOW the site footer and reads as the footer not reaching the bottom of the page.
   This block is that same reservation made available to an inner scroll region, in one class, so
   the next surface applies a class instead of re-deriving the arithmetic.

   WHAT IT IS NOT. It adds nothing to the content area, nothing to the footer, and nothing to either
   dock. Every rule here is gated on a dock actually being on the page, and the class is applied to
   no surface in the slice that ships it, so nothing that renders today moves by a pixel. Phase 51
   is the first consumer (the assistant transcript's inner scroll region, finding A3-4).

   WHY A CLASS AND NOT THE VARIABLES. The two clearances are each named exactly once in this sheet
   (--ff-dock-clearance in the TURN-3 block, --ff-lgk-dock-clearance in the FOOT-1 block) and the
   stacked case is their sum, because 45G lifts the live game dock above the draft dock by the draft
   dock's own clearance. A consumer reasoning about the variables directly has to know that third
   fact, and the first surface to forget it overlaps a bar. Three rules here, matching the FOOT-1
   block's three cases exactly, state the sum once for every consumer that follows.

   PADDING, NOT MARGIN, AND NOT A LIFT. The room has to be inside the region's own scrollable box:
   that is what carries the last row up clear of the bar when the member is scrolled to the bottom.
   A margin would move the whole region up the page instead, and a bottom offset would only work on
   something taken out of flow, which a transcript is not.

   360px FIRST, and why there is no breakpoint. Both clearances are authored entirely in rem plus
   the iOS home-indicator inset, so neither changes with the viewport. The FOOT-1 block repeats its
   footer rules inside the 599.98px breakpoint only because the footer's own BASE padding drops
   there, and this class has no base of its own to drop. One rule per case therefore covers every
   width, and a second declaration would be a re-measurement of a value that is already named.
   ============================================================================================= */

/* The region pays for whichever bar is up. */
body:has(.ff-draft-dock) .ff-dock-scroll-clear {
    padding-bottom: var(--ff-dock-clearance);
}

body:has(.ff-lgk-dock) .ff-dock-scroll-clear {
    padding-bottom: var(--ff-lgk-dock-clearance);
}

/* Both bars up (a member mid draft on a Saturday): the game dock is sitting on top of the draft
   dock, so the region clears the pair. Specificity carries it, exactly as it does in FOOT-1: this
   selector is (0,3,1) against the two above at (0,2,1), so no !important is needed. */
body:has(.ff-draft-dock):has(.ff-lgk-dock) .ff-dock-scroll-clear {
    padding-bottom: calc(var(--ff-dock-clearance) + var(--ff-lgk-dock-clearance));
}
/* ---- end 52J dock scroll clearance ---- */

/* =============================================================================================
   PHASE 52 (52B): THE PANEL SKELETON, the loading silhouette primitive (plan 5.2, 9.1)

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, which is where every appended block in this sheet
   goes: UX-1's end marker has to stay the LAST block marker in app.css (PickInFlightRoomTests pins
   that, and PanelSkeletonTests pins this block's own position ahead of it).

   WHAT IT IS. Four silhouettes for PanelSkeleton.razor, which is DataLoader's optional LoadingContent
   made composable: a page band, a tile row, a stack of text rows and a chart box. It is the live game
   sheet's .ff-lg-skeleton (this sheet, block above) generalised rather than a second animation: the
   same MudSkeleton wave, the same .5rem column gap, the same 1.5rem text row.

   THE FILL IS NEVER DECLARED HERE. Every bar, tile and box takes var(--mud-palette-skeleton) from
   MudBlazor's own .mud-skeleton rule, so the shimmer is the framework's in both themes and this block
   only ever says how big each piece is and where it sits. The one painted surface is the hero band,
   and it borrows the shared page band's language exactly (PageHero.razor.css: a primary-tinted
   gradient with a primary hairline, both alpha over whatever surface the band sits on), so the
   skeleton reads as the band that is arriving and needs no light-mode override.

   360px FIRST, and pinned by test. Nothing here declares a width in pixels, no rule declares a
   max-width, no rule declares overflow-x and no rule sets white-space: nowrap, so none of the four
   pieces can hand a phone a horizontal scrollbar. Every size is a rem, so a piece scales with the
   root font rather than against it, and the tile row is an auto-fitting grid: it drops to fewer
   columns as the viewport narrows instead of overflowing.

   HEIGHTS ARE THE POINT, not decoration. A skeleton exists so the arriving content moves nothing on
   the page and so the footer stays below the fold while a full page loads (plan §9.1 rules 1 and 3),
   and a surface reaches that height by stacking pieces. The chart box is 12.5rem because 200px is
   what the game page's own chart host is given, and the tile and row heights are the shipped tile and
   text-line heights for the same reason.
   ============================================================================================= */

/* Every piece is a flex/grid child somewhere, so it must be allowed to shrink below its content: the
   default min-width:auto of a flex item is how a silhouette widens the page it is standing in for. */
.ff-skel {
    min-width: 0;
    margin-bottom: .75rem;
}

/* ---- the page band: PageHero's badge beside its text column ---- */

.ff-skel-hero {
    display: flex;
    align-items: flex-start;
    gap: .75rem;
    min-width: 0;
    /* The shared page band's own 18px, so the band and its skeleton leave the same gap under them. */
    margin-bottom: 1.125rem;
    padding: .875rem .9375rem;
    border-radius: .875rem;
    background: linear-gradient(135deg,
        rgba(var(--mud-palette-primary-rgb), .13),
        rgba(var(--mud-palette-primary-rgb), .03));
    border: 1px solid rgba(var(--mud-palette-primary-rgb), .22);
}

/* The badge keeps its own size at every width, as the shared page band's does, so a wrap can never
   squeeze it into an ellipse and the bars beside it are the only elastic part of the band. */
.ff-skel-hero .ff-skel-hero-badge {
    flex: none;
    width: 2.5rem;
    height: 2.5rem;
    border-radius: .6875rem;
}

.ff-skel-hero-text {
    flex: 1 1 auto;
    min-width: 0;
    display: flex;
    flex-direction: column;
    gap: .5rem;
}

/* Two title-weight bars by default, because the first surface to compose this one is a game page
   whose head is two school names. The widths are percentages of the band, not fixed measures, so the
   pair reads as two names at 360px and at 1440px. A third bar and beyond is a sub-line. */
.ff-skel-hero-text .ff-skel-bar {
    height: 2rem;
}

.ff-skel-hero-text .ff-skel-bar:nth-child(1) { width: 62%; }

.ff-skel-hero-text .ff-skel-bar:nth-child(2) { width: 46%; }

.ff-skel-hero-text .ff-skel-bar:nth-child(n+3) {
    width: 38%;
    height: 1.25rem;
}

/* ---- the tile row: a KPI or stat strip ---- */

/* auto-fit rather than a column count, so the row reflows to what fits instead of scrolling: five
   tiles land three and two on a phone and in one row on a tablet, with no breakpoint to maintain. */
.ff-skel-tilerow {
    display: grid;
    grid-template-columns: repeat(auto-fit, minmax(5.5rem, 1fr));
    gap: .5rem;
}

.ff-skel-tilerow .ff-skel-tile {
    height: 4.5rem;
    border-radius: .625rem;
}

/* ---- the row stack: a list, a table body, a column of lens rows ---- */

/* The live game sheet's .ff-lg-skeleton, generalised: a flex column with the same .5rem gap and the
   same 1.5rem text row, which is the combination already shipped and already reviewed. */
.ff-skel-rows {
    display: flex;
    flex-direction: column;
    gap: .5rem;
}

.ff-skel-rows .ff-skel-row {
    height: 1.5rem;
}

/* ---- the chart box ---- */

/* 12.5rem is the 200px the game page hands its own chart host, so the chart arriving into this box
   moves nothing under it. A surface with a taller chart passes its own class on the root. */
.ff-skel-chartbox .ff-skel-chart {
    height: 12.5rem;
    border-radius: .5rem;
}

/* ---- the one modifier: pieces that stand in for CARDS rather than for lines and chips ----

   It is declared HERE rather than on the consuming surfaces because they own no block in this sheet:
   the dashboard's tile row and the Matchups slate carry the choice in their markup (PanelSkeleton's
   Cards parameter) and this is where the choice means something.

   8rem is the width that makes four cards behave the way the dashboard's own grid does at every width
   the matrix names, measured rather than guessed: at 360px the content box is about 328px, two columns
   fit and four cards land two and two; at 600px the box is about 568px, four fit and they are one row,
   which is where the shipped grid puts them. It is deliberately NOT the widest value that fits at
   568px (8.5rem fits to the pixel and then loses the fourth column to a subpixel gutter), because a
   silhouette that is one device-pixel away from reflowing is a silhouette that reflows on some phone.
   No breakpoint of its own either, because auto-fit already IS the breakpoint. */

.ff-skel-tilerow.ff-skel-cards {
    grid-template-columns: repeat(auto-fit, minmax(8rem, 1fr));
}

/* A slate row is a bordered card with a team line, a kickoff line and a band line in it, not a line of
   text, so its silhouette is a block of that card's height with the card's own corner radius. */
.ff-skel-rows.ff-skel-cards .ff-skel-row {
    height: 4.5rem;
    border-radius: .875rem;
}

/* ---- end panel skeleton ---- */

/* =============================================================================================
   PHASE 52 (52F): THE WATCHLIST ROW AT 360px, AND THE SKELETON'S THREE BREAKPOINT ANSWERS

   INSERTED IMMEDIATELY BEFORE THE UX-1 BANNER, after 52B's panel skeleton block, which is where
   every appended block in this sheet goes: UX-1's end marker has to stay the LAST block marker in
   app.css (PickInFlightRoomTests pins that from the other side, and PanelSkeletonTests pins 52B's
   position ahead of it).

   IT IS A SEPARATE BLOCK FROM 52B'S ON PURPOSE. Every rule here is a media query, and 52B's block
   is asserted to contain none: its four silhouettes are authored so that auto-fit, percentages and
   rem carry them at every width with no breakpoint to maintain, and PanelSkeletonTests states that
   as "no @media in this block". The three answers below are not re-measurements of those pieces;
   they are the two surfaces that compose them saying what their own layout does at a width, plus
   one row-height variant. So they live with the surfaces' own slice rather than inside the
   primitive's block.

   FOUR RULES, THREE SUBJECTS.

   1. GD-6, the watchlist row (backlog GD-6, plan section 5.6). The owner's Week 3 phone screenshot
      has "From your watchlist today" and then the first two names on line one, and the third name
      alone on line two, wrapping AROUND the label rather than as a list. It is a shape problem and
      not a length problem: the row is a wrapping flex line whose first item is a label, so however
      short the label gets, the names start beside it and break wherever they run out of room. Below
      420px the label takes the whole first line and the names become a list of their own. 52F also
      shortens the label itself ("Watching today", eleven characters against twenty five), because
      fixing only the shape would leave a label eating a third of a 360px line.

      420px rather than the sheet's usual 599.98px: this row sits inside the My Team panel, which is
      half the grid from 600px up, so the room it has is not the viewport. 420px is where the label
      and two names stop fitting on one line at the panel's narrow width, and above it the inline
      label is the right shape and is what every wider screen already shows.

   2 and 3. The game page's silhouette at 600px and at 960px (plan section 9.2's matrix, rows "Game
      page skeleton"). A skeleton is the shape of the page that is COMING (section 9.1 rule 1), so
      where the real page reflows, its silhouette has to reflow with it or the content moves when it
      lands, which is the shift a skeleton exists to prevent.

        - 600px: the band's two bars sit INLINE. The band they stand in for is a game's two school
          names with the word between them, and that head is one line from 600px up. A third bar and
          beyond is a sub-line rather than half of a pair, so it takes the whole next row instead of
          joining them.
        - 960px: the lens blocks run in TWO COLUMNS, which is the shipped lens layout's own
          breakpoint (.ff-ml-dvp in this sheet, "960px is where the plan asks for side by side").

      SCOPED BY THE COMPOSITION, not by a page class. The game page's fragment is the one that
      composes a chart box with a card-height row stack directly after it; the Matchups slate is a
      card-height stack with nothing before it (its slate is a flex column at every width, so two
      columns there would be wrong), and the dashboard's stacks are line rows rather than cards. The
      adjacency IS the distinguishing fact, and GameDayPreKickoffCopyTests pins the composition it
      depends on so this rule cannot go quietly dead if that fragment is reordered.

   4. The panel line row, .ff-skel-rows-panel. A row stack standing in for the rows of a bordered
      panel (a roster row, a standings row) is neither a 1.5rem line of text nor a 4.5rem card: the
      real rows are about 44px of content and padding plus their rule. 2.875rem is 46px, rounded UP
      past both, because a silhouette that reserves LESS room than the rows replacing it lets the
      panel grow when the data lands. It is a modifier a caller passes through PanelSkeleton's Class
      parameter, so it needs no change to the primitive, and it is declared here for the same reason
      52B declared .ff-skel-cards there: the consuming surfaces own no block in this sheet.
   ============================================================================================= */

/* ---- 1. GD-6: the watchlist label takes its own line on a phone ---- */

@media (max-width: 420px) {
    /* flex-basis and not width: this is a flex item on a wrapping line, and a full basis is what
       makes the line break AFTER the label rather than inside the names beside it. */
    .ff-gd-watch .lbl {
        flex-basis: 100%;
    }
}

/* ---- 2. the page band's bars pair up once there is room for the pair ---- */

@media (min-width: 600px) {
    .ff-skel-hero-text {
        flex-direction: row;
        flex-wrap: wrap;
        align-items: center;
        /* The row gap stays 52B's .5rem (its gap shorthand), which is what a wrapped sub-line uses. */
        column-gap: .75rem;
    }

    /* Two names, the first the wider, as two school names read. Percentages of the band and not
       measures, so the pair is the same shape at 600px and at 1440px, and their sum plus the gap
       leaves room to spare at the narrow end of this range. */
    .ff-skel-hero-text .ff-skel-bar:nth-child(1) { width: 46%; }

    .ff-skel-hero-text .ff-skel-bar:nth-child(2) { width: 34%; }

    /* A sub-line is not half of the pair: it wraps to its own row under them, at the shorter height
       52B already gives it. */
    .ff-skel-hero-text .ff-skel-bar:nth-child(n+3) { width: 100%; }
}

/* ---- 3. the lens blocks pair up where the shipped lens layout does ---- */

@media (min-width: 960px) {
    /* A card stack that follows a chart box is the game page's lens silhouette. minmax(0, 1fr)
       twice, the same idiom the shipped .ff-ml-dvp grid uses, so a wide card can never push the
       column past its track. The .5rem gap carries over from 52B's base rule. */
    .ff-skel-chartbox + .ff-skel-rows.ff-skel-cards {
        display: grid;
        grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
    }
}

/* ---- 4. the panel line row: taller than a text line, shorter than a card ---- */

.ff-skel-rows.ff-skel-rows-panel .ff-skel-row {
    height: 2.875rem;
}

/* ---- end 52F watchlist row and skeleton breakpoints ---- */

/* =================================================================================================
   52K: the play by play attribution block on Player Detail, and the quarter strip above it

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, which is where every
   slice's block goes: app.css is passed between parallel slices, an edit into an earlier block is a
   merge conflict by construction, and the UX-1 end marker has to stay the last block marker in the
   file (PickInFlightRoomTests pins exactly that).

   Owner, 2026-09-17: "since we have the play by play stuff now, we need to make it look nicer." What
   he was reading was a four column table of raw feed text with the same touchdown run listed twice and
   a situation phrase long enough to wrap three times on a phone. The markup that replaced it is one
   table per quarter with that quarter's total in its caption, one row per play, a gain chip and a
   details element for the full play text; this block is what makes those read as one designed section
   rather than as a denser table.

   THREE RULES THIS BLOCK KEEPS.
   1. It never widens the page. The horizontal scroll stays on the strip's own container (47D's rule,
      untouched here), and at phone widths the table stops being a table at all: each row becomes a
      card whose cells carry their own labels, so there is nothing left to scroll sideways.
   2. Colour is never the only carrier. A gain chip carries its plus sign, a loss carries its minus and
      a scoring play carries the TD badge in the cell beside it, so the three read apart in monochrome
      and to a screen reader.
   3. Every size is in rem and every colour is a palette token, so the block follows the type scale and
      both themes without a second definition of either.
   ================================================================================================= */

/* The card both post game blocks share, which is the "same visual language" half of the ask: the
   quarter strip and the play by play read as two sections of one panel rather than as two tables that
   happen to sit near each other. */
.ff-pbp {
    display: block;
    margin-top: .75rem;
    padding: .6rem .7rem .7rem;
    border: .0625rem solid var(--mud-palette-lines-default);
    border-radius: .5rem;
    background: var(--mud-palette-surface);
}

.ff-pbp > .ff-attr-head {
    margin-bottom: .4rem;
}

/* One quarter's table. The gap is what separates the quarters, with no rule between them. */
.ff-pbp-q + .ff-pbp-q {
    margin-top: .6rem;
}

.ff-pbp-table {
    width: 100%;
}

/* The quarter's heading and its own totals, on one line: the quarter left, what it added right. A
   caption rather than a header row, so the row count under a quarter stays exactly the number of plays
   in it. */
.ff-pbp-cap {
    display: flex;
    align-items: baseline;
    justify-content: space-between;
    gap: .5rem;
    padding: .2rem .1rem .3rem;
    text-align: left;
    caption-side: top;
}

.ff-pbp-cap .q {
    font-weight: 600;
    font-size: .8rem;
    letter-spacing: .02em;
}

.ff-pbp-cap .tot {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
}

.ff-pbp-table thead th {
    font-size: .68rem;
    font-weight: 600;
    letter-spacing: .03em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
    border-bottom: .0625rem solid var(--mud-palette-lines-default);
}

.ff-pbp-table tbody tr + tr td {
    border-top: .0625rem solid var(--mud-palette-lines-default);
}

/* The gain column is the one the eye goes to, so it is centred on its own chip rather than ragged.
   THE HEADING IS CENTRED WITH IT (owner walk, 2026-09-22: "the numbers in the gain column are aligned
   left and don't line up with the column"). 47D's strip rule right aligns every heading and every cell
   between the first column and the last, and centring the cells alone left the chips sitting to the
   left of a right aligned "Gain" above them. A column's heading and its values share one alignment, so
   both are named here. This selector outranks the strip rule (two classes and an element against one
   class and an element), and at phone widths the heading row is removed and every cell carries its own
   label, so this only ever decides the table layout. */
.ff-pbp-table th.gn,
.ff-pbp-table td.gn {
    text-align: center;
}

/* The situation reads as a coordinate rather than as prose, so it is the quieter of the two text
   columns and never the one that wraps first. */
.ff-pbp-table td.st {
    color: var(--mud-palette-text-secondary);
    font-size: .76rem;
}

.ff-pbp-stat {
    font-size: .78rem;
}

/* The touchdown, merged onto the play's own row. It is a word and not only a colour. */
.ff-pbp-td {
    display: inline-block;
    margin-left: .3rem;
    padding: 0 .3rem;
    border-radius: .25rem;
    font-size: .62rem;
    font-weight: 700;
    letter-spacing: .04em;
    color: var(--mud-palette-warning);
    background: rgba(var(--mud-palette-warning-rgb), .16);
}

/* The yards, as a chip. The sign is inside the text, which is what keeps the reading correct with no
   colour at all. */
.ff-pbp-chip {
    display: inline-block;
    min-width: 2.6rem;
    padding: .05rem .35rem;
    border-radius: .75rem;
    font-size: .76rem;
    font-weight: 600;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-primary);
    background: rgba(var(--mud-palette-primary-rgb), .08);
}

.ff-pbp-chip.up {
    color: var(--mud-palette-success);
    background: rgba(var(--mud-palette-success-rgb), .14);
}

.ff-pbp-chip.down {
    color: var(--mud-palette-error);
    background: rgba(var(--mud-palette-error-rgb), .14);
}

.ff-pbp-chip.score {
    color: var(--mud-palette-warning);
    background: rgba(var(--mud-palette-warning-rgb), .18);
}

/* A scoring play, marked on the row as well as in the cell, so the eye finds it while scrolling. */
.ff-pbp-table tbody tr.is-score td.st {
    box-shadow: inset .1875rem 0 0 0 var(--mud-palette-warning);
}

/* The play text: its clause, with the full sentence one tap away. A native details element, because a
   phone has no hover and this page is read on one. */
.ff-pbp-more > summary {
    cursor: pointer;
    list-style: none;
}

.ff-pbp-more > summary::-webkit-details-marker {
    display: none;
}

.ff-pbp-more > summary::after {
    content: " more";
    font-size: .68rem;
    color: var(--mud-palette-primary);
}

.ff-pbp-more[open] > summary::after {
    content: " less";
}

.ff-pbp-full {
    display: block;
    margin-top: .2rem;
    font-size: .74rem;
    color: var(--mud-palette-text-secondary);
}

/* The link to this week's game (L-1) where it stands on a line of its own rather than inline in the
   hero. Quiet until it is wanted, exactly like the Player hub's game log icon. */
.ff-pd-gamelink-row {
    margin: .25rem 0 .5rem;
    font-size: .8rem;
}

.ff-pd-gamelink {
    font-weight: 600;
}

/* -------------------------------------------------------------------------------------------------
   Phone widths: the play by play stops being a table and becomes a stack of cards.

   Four columns of feed data on a 360 pixel screen is either a sideways scroll or four unreadable ones,
   and the owner drafts and reads from a phone. Each row becomes its own card, each cell carries its
   own label, and the header row is removed rather than merely hidden: the labels ARE the header once
   the table is a stack. The quarter caption stays, because it is what says which part of the game the
   cards below it belong to.
   ------------------------------------------------------------------------------------------------- */
@media (max-width: 30rem) {
    .ff-pbp-table,
    .ff-pbp-table thead,
    .ff-pbp-table tbody,
    .ff-pbp-table tr,
    .ff-pbp-table td {
        display: block;
        width: 100%;
    }

    .ff-pbp-table thead {
        display: none;
    }

    .ff-pbp-table caption {
        display: flex;
    }

    .ff-pbp-table tbody tr {
        margin-bottom: .5rem;
        padding: .4rem .5rem;
        border: .0625rem solid var(--mud-palette-lines-default);
        border-radius: .4rem;
    }

    .ff-pbp-table tbody tr + tr td {
        border-top: 0;
    }

    .ff-pbp-table td {
        display: flex;
        align-items: baseline;
        justify-content: space-between;
        gap: .5rem;
        padding: .15rem 0;
        text-align: right;
        white-space: normal;
    }

    .ff-pbp-table td::before {
        content: attr(data-label);
        flex: 0 0 auto;
        font-size: .64rem;
        font-weight: 600;
        letter-spacing: .03em;
        text-transform: uppercase;
        color: var(--mud-palette-text-secondary);
    }

    /* The situation is the card's own heading, so it keeps the full width and drops its label. */
    .ff-pbp-table td.st {
        display: block;
        text-align: left;
        font-weight: 600;
    }

    .ff-pbp-table td.st::before {
        content: none;
    }

    /* And the play text gets the whole card width under its label rather than a narrow right column. */
    .ff-pbp-table td.dt {
        display: block;
        text-align: left;
        max-width: 100%;
    }

    .ff-pbp-table td.dt::before {
        display: block;
        margin-bottom: .1rem;
    }

    .ff-pbp-table tbody tr.is-score td.st {
        box-shadow: none;
    }

    .ff-pbp-table tbody tr.is-score {
        border-left: .1875rem solid var(--mud-palette-warning);
    }
}

/* ---- end 52K ---- */

/* =================================================================================================
   Phase 52 52M (2026-09-18): the live game sheet's scrolling content, and the head it scrolls under

   OWNER WALK, from his own phone screenshots of Syracuse at Pittsburgh, the first live game this
   product ever showed in production. The sheet's head (the score, the state line and the "observed N
   seconds ago" line) IS the dialog's title, so it stays put while the content region scrolls beneath
   it, and MudBlazor clips that scroll at the content box: flat, hard, and straight through whatever
   text happens to be crossing the edge. He read a guillotined "Pittsburgh 24" scoring row, and
   earlier a slice of the win probability sparkline hanging under the freshness line, as a rendering
   fault. Both of them were that clip.

   A SHORT TOP FADE, AND NOTHING ELSE. The scroll container gets a mask that ramps from transparent at
   its top edge to opaque one rem in, so a row passing under the head dissolves into it instead of
   being cut in half. Nothing about the head moves: no markup, no test id, and no MudDialog default.
   One property on one container, plus the padding that makes it safe.

   IT CANNOT DIM ANYTHING A MEMBER IS READING AT REST, which is what the padding rule is for. The ramp
   is exactly as deep as the container's own top padding, so at scroll position zero the faded band
   holds padding and nothing else. MudBlazor's own 8px top padding would have left the first row
   sitting half inside the ramp, which is the same defect in the other direction, so the two lengths
   are deliberately ONE length and the contract test says so.

   SCOPED TO THIS DIALOG. Every selector names .ff-lg-dialog, the class the sheet puts on its own
   MudDialog, so nothing here can reach another dialog in the product. The prefixed property rides
   beside the standard one because the screenshots came from a phone browser and this is the one
   property in the block that does any work.

   NO PIXEL MEASUREMENT ANYWHERE. Both lengths are rem, so the fade scales with a member who has made
   their text bigger, and the mask's own black is an alpha ramp rather than ink: no colour in this
   block reaches a member's eye, in either theme.
   ================================================================================================= */

.ff-lg-dialog .mud-dialog-content {
    padding-top: 1rem;
    -webkit-mask-image: linear-gradient(to bottom, transparent 0, #000 1rem);
    mask-image: linear-gradient(to bottom, transparent 0, #000 1rem);
}

/* ---- end Phase 52 52M ---- */

/* ============================================================================================
   PLAYER HUB GAME LOG: THE LINK TO THE GAME (owner walk, 2026-09-14)

   Inserted BEFORE the UX-1 banner below, which stays the last block marker in this sheet.

   MOVED HERE 2026-09-18 (audit finding 8), because for four days it was not. It landed between
   UX-1's own banner and UX-1's end marker, so the sentence above it was false and UX-1's block had
   another block nested inside it. The guard every appender was reading only ever asserted that the
   end marker is LAST, which it still was, so nothing failed. AppCssIntegrityTests now asserts the
   other half, that no block opener appears after UX-1's, so the next appender cannot land inside it
   either.

   The game log's week cell already carries the link to that week's stat detail, and this is the
   second destination the row now has: the game itself. It is an ICON rather than a word because
   the table is fourteen columns wide at its widest and a second label in the first cell would
   push the whole row; the anchor carries its own title and aria-label, so the affordance is named
   for a pointer and for a screen reader without spending a column on it.

   Muted until it is wanted, which keeps a column of them from reading as decoration on a dense
   table, and fully opaque on hover AND on keyboard focus, so the keyboard gets the same
   confirmation the pointer does.

   There is no disabled state to style: a row the games store could not place renders no element
   at all, which is what keeps a dead link off the page.
   ============================================================================================ */

.ff-gamelog-game {
    margin-left: 6px;
    vertical-align: text-bottom;
    opacity: .72;
}

.ff-gamelog-game:hover,
.ff-gamelog-game:focus-visible {
    opacity: 1;
}

.ff-gamelog-game .mud-icon-root {
    font-size: 1rem;
}

/* ---- end player hub game log link ---- */

/* ================================================================================================
   PLAY BY PLAY: THE SNAP'S OTHER STATS (audit round, 2026-09-18)

   Inserted immediately BEFORE the UX-1 banner below, which stays the last block marker in this
   sheet.

   52K merged every row of a snap into one row. That merge was written for the touchdown case and
   applied to every case, so a carry that ended in a fumble rendered as the carry alone and the
   fumble was emitted nowhere at all. The server now hands each row everything else the feed
   attributed to that athlete on that snap, in CFBD's own words, and this is what those strings look
   like.

   QUIETER THAN THE PLAY AND QUIETER THAN THE TOUCHDOWN, deliberately. The stat name is the cell's
   subject and the TD badge is the one thing in the cell that changes how a member reads the score;
   these are additional published facts, so they take the secondary text colour and a hairline
   outline rather than a fill. Colour is never their carrier in any case, because every chip states
   its own word.

   IT WRAPS RATHER THAN WIDENING THE COLUMN. The play cell is one of four in a table that already
   scrolls inside its own container at 360px, so a snap carrying two extra stats has to reflow inside
   the cell it is in: inline-block chips with a little leading, and no width, no min-width and no
   overflow of any kind declared anywhere in this block.

   NO COLOUR OF ITS OWN. Both values are palette tokens, so the chip is correct in dark mode (the
   default) and in light mode by construction rather than by a second rule.
   ================================================================================================ */

.ff-pbp-also {
    display: inline-block;
    margin-left: .3rem;
    margin-top: .15rem;
    padding: 0 .3rem;
    border-radius: .25rem;
    font-size: .66rem;
    font-weight: 600;
    color: var(--mud-palette-text-secondary);
    border: .0625rem solid var(--mud-palette-lines-default);
}

/* ---- end play by play other stats ---- */

/* =================================================================================================
   PLAY BY PLAY: THE CARD'S OWN WIDTH, AND THE CELLS THAT COULD NOT WRAP
   (promotion readiness review, 2026-09-18, findings P9 and P19)

   Inserted immediately BEFORE the UX-1 banner below, which stays the last block marker in this sheet.

   Every rule here is a correction to 52K's phone block above, which is why they are separate rules
   rather than edits: 52K's block is what a reader goes to for "how does this table become cards", and
   these are the four places that description was not true at a real width. All four ride
   Features:GameStoryEnabled, so this is a flip day repair rather than a deploy day one.

   1. THE CARD WAS 34 PIXELS WIDER THAN THE SCREEN (P9, the repo's 360px hard rule). The table carries
   .ff-tstrip-table as well, whose min-width is 20rem, and 52K's block turns the table, the rows and the
   cells into blocks at 100% width without ever putting that floor down. This sheet declares no global
   box-sizing, so the row's own padding and hairline are added OUTSIDE its 100%: a 20rem floor plus
   1rem of padding plus a hairline each side is 338 pixels inside a 303.6 pixel container, and the
   roughly 34 pixels that fall off the right edge take about 40% of the Gain chip with them, which is
   the number the whole card exists to show. The floor is a floor for a TABLE, and there is no table at
   this width, so it is released; the card is measured border box, so its padding is inside the width it
   was given rather than added to it.

   2. THE PLAY CELL WAS FOUR ITEMS ON ONE UNWRAPPED LINE (P19a). 52K makes every cell a
   space-between flex line with its label on the left, and resets the two cells that are prose (the
   situation and the detail) back to blocks. The PLAY cell is prose too: since this round it can carry
   the stat, a touchdown badge and one or two "also" chips, and as a flex line those are four items that
   do not wrap, so the badge is flung to the card's right edge and the chips are squeezed between. It
   reads as a block, with its label above it, exactly as the detail cell does.

   3. THE PLAY CELL COULD NOT WRAP AT ALL BETWEEN 481 AND 700 PIXELS (P19b). The "also" chips block
   below says in prose that they wrap inside the cell, and they cannot: .ff-tstrip-table td sets
   white-space: nowrap for every cell but the last, so between the phone block's ceiling and the width
   at which the table is comfortable, the play cell is one unbreakable line that pushes Gain and Detail
   off the right of the strip's scroller. Prose wraps; that is what makes it prose.

   4. TWENTY EIGHT PIXELS OF AIR ABOVE BOTH STRIP HEADINGS (P19c). .ff-attr-head carries
   margin: 18px 2px 2px, and the strip's own rule overrides margin-bottom alone, so the top margin
   survives inside a panel that already has its own padding. Stating the whole shorthand is what
   actually replaces it.

   NO COLOUR, NO NEW LENGTH THAT IS NOT A REM, and nothing here selects the document: the strip keeps
   its own scroller, exactly as 47D requires.
   ================================================================================================= */

/* (3) The play cell is prose, at every width. */
.ff-pbp-table td.pl {
    white-space: normal;
}

/* (4) The whole shorthand, so the 18px top margin from .ff-attr-head is replaced rather than joined. */
.ff-pbp > .ff-attr-head {
    margin: 0 0 .4rem;
}

@media (max-width: 30rem) {
    /* (1) The table's floor is a floor for a table, and there is no table here. */
    .ff-pbp-table,
    .ff-pbp-table thead,
    .ff-pbp-table tbody,
    .ff-pbp-table tr,
    .ff-pbp-table td {
        min-width: 0;
    }

    /* And the card's padding and hairline are inside the width it was given. */
    .ff-pbp-table tbody tr,
    .ff-pbp-table td {
        box-sizing: border-box;
    }

    /* (2) The play cell reads as a block under its own label, like the detail cell beside it. */
    .ff-pbp-table td.pl {
        display: block;
        text-align: left;
    }

    .ff-pbp-table td.pl::before {
        display: block;
        margin-bottom: .1rem;
    }
}

/* ---- end play by play card width ---- */

/* =============================================================================================
   Phase 57 57A (2026-09-21) - the forecast pair's narrow variant

   ForecastPair is the chip Phase 42 MR-1 shipped on the matchup Players tab, published once so the
   seven surfaces that keep a projection on screen after a row goes final all state it the same way.
   Its wide form is .ff-mr-actual above, unchanged and not redefined here: every token below is that
   block's own, only tightened.

   THE NARROW FORM IS FOR A POINT COLUMN, NOT A CARD. On Game Day the chip sits in a 96px cell beside
   a name, a game chip and a stat line, under a banked total that has already said what the big number
   is. So .compact drops the label word (the component does that) and this block gives back the height
   and the horizontal padding a pill needs on a card and does not need in a column: no border, no
   background, a smaller gap, and the tabular figures inherited from the base rule so the digits line
   up under the total above them.

   BELOW 600px THE VERDICT WORD GOES TO THE TOOLTIP (plan Q7, decision 7). "in range" is eight to
   twelve characters beside a value and a signed delta, and a fourth thing in that cell is how a Game
   Day row grows a third line on a phone. The band and the verdict both ride the chip's title in this
   variant, and both are on the game page in full, so nothing is lost: the row is two lines on a phone
   and one line from 600px up. Colour is never the only carrier here either, because the delta's sign
   says what the delta's colour says.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, which is where every
   slice in this round appends and which AppCssIntegrityTests and PickInFlightRoomTests both pin: the
   UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

.ff-mr-actual.compact {
    gap: 3px;
    padding: 0;
    border: 0;
    background: none;
    font-size: .64rem;
    line-height: 1.45;
}

.ff-mr-actual.compact .val { font-weight: 600; }

/* The muted spans declare their own weight (57I). Every other span in this chip already did, and
   this one inherited the HOST's: normal inside Game Day's point column, 600 inside the home card's
   points cell and 700 inside its Total row, which is one fact styled three ways on three surfaces
   that exist to be read against each other. */
.ff-mr-actual.compact .bd { font-size: .58rem; font-weight: 400; }

@media (max-width: 599.98px) {
    .ff-mr-actual.compact { flex-wrap: nowrap; }

    /* The band's verdict lives in the chip's title at this width, with the band itself.

       EXCEPT the no line reason (Phase 57 audit, 2026-09-22, finding D4). "no box score" is the one
       muted span the component prints BECAUSE a phone has no hover, so hiding it here removed the
       sentence at exactly the width it exists for and left a bare placeholder glyph with nothing to
       explain it. .ff-mr-noline marks that span and nothing else, and it is exempted rather than
       restyled: every token on it stays the rule above's. */
    .ff-mr-actual.compact .bd:not(.ff-mr-noline) { display: none; }
}

/* ---- end 57A ---- */

/* =============================================================================================
   Phase 54 54C (2026-09-21) - the live bar catches the eye when somebody scores

   THE OWNER'S N-10, AND THE WHOLE OF IT IS EIGHT SECONDS AND ONE SENTENCE. A member reading their
   profile, a pool page or the assistant on a Saturday learns nothing when their quarterback throws a
   touchdown: the bar at the bottom rewrites one number on its next poll and not one pixel moves. This
   block is the motion, modelled line for line on the draft dock's own pulse above (ff-draft-dock-pulse,
   the same 1.6s ease-in-out and the same reduced motion arm), because the two bars sit on top of each
   other and must not celebrate in two different languages.

   IT CANNOT CHANGE THE BAR'S SIZE, AND THAT IS THE ACCEPTANCE. The bar is fixed at the bottom of the
   app and the page reserves room for exactly one line of it (--ff-lgk-dock-clearance, FOOT-1), so a
   pulse that grew the bar would push the footer and every fixed bottom control out of place on a phone.
   So there is no padding, no margin, no width, no height and no font size change in here at all: the
   animation is opacity and a 2% SCALE, which is a paint transform and takes no layout, and the sentence
   itself REPLACES the "1 of your players in this game" cell in the markup rather than being added
   beside it. That replacement is why this block needs no media query: there is no width at which the
   bar has one cell more than it had before.

   EVERY SELECTOR IS .ff-lgm- ("live moments"), this slice's own prefix, and deliberately not 45G's
   .ff-lgk- which paints the bar itself, nor LG-2's .ff-lg-, LG-5's .ff-lgd-, 45E's .ff-lgf-, 45F's
   .ff-lgs- or 45I's .ff-lgr-. The blocks are appended separately and none may win a cascade against
   another by accident, so the component adds this block's classes alongside 45G's rather than this
   block reaching into 45G's.

   COLOUR IS NEVER THE ONLY CARRIER (the rule this family states for itself at LiveGameField.razor:40).
   Nothing here paints anything: the motion is opacity and scale, the sentence is what actually says a
   score happened, and under prefers-reduced-motion the sentence is still there with the motion gone.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after 57A's, which is
   where every slice in this round appends and which AppCssIntegrityTests and PickInFlightRoomTests both
   pin: the UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

/* The bar, while a score is being marked. Five cycles of 1.6s is exactly the eight seconds the
   component holds the mark for (LiveMomentCopy.DockPulseSeconds), so the motion ends when the state
   does instead of being cut off part way through a cycle. */
.ff-lgm-dock-bar {
    animation: ff-lgm-dock-pulse 1.6s ease-in-out 5;
}

@keyframes ff-lgm-dock-pulse {
    0%, 100% { opacity: 1; transform: scale(1); }
    50% { opacity: .72; transform: scale(1.02); }
}

/* The sentence, in the cell the players count was in. It takes that cell's own type scale and secondary
   colour so the bar reads as one line rather than as a line with something stuck on it, and it may
   break inside a word, because a school name plus a count is the longest thing this bar ever says. */
.ff-lgm-dock-said {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    min-width: 0;
    overflow-wrap: anywhere;
}

/* BELOW 600px THE COUNT CLAUSE GOES, AND WITH IT THE ONLY WAY THIS BAR COULD GAIN A LINE. The sentence
   is one string in two elements: the lead, this clause, and then the full stop outside it. Hidden, a
   phone reads "Vanderbilt scored." (29 characters at the longest school in the catalog's own fixtures)
   in place of "1 of your players in this game" (30), so the replacement is strictly shorter than what it
   replaced and the wrapping bar cannot grow while it is marking a score. display:none rather than a
   visual hide is deliberate: it takes the clause out of the accessibility tree as well, so the sentence
   is announced once and whole rather than twice or half. From 600px up the bar has the room for all of
   it. This is the one breakpoint in this block, and the only declaration inside it. */
@media (max-width: 599.98px) {
    .ff-lgm-dock-said-mine { display: none; }
}

/* Reduced motion: the state, the class and the sentence all stay, and only the movement goes. A member
   who has asked their device for less motion is asking for less motion, not for less information. */
@media (prefers-reduced-motion: reduce) {
    .ff-lgm-dock-bar {
        animation: none;
        transition: none;
    }
}

/* ---- end 54C ---- */

/* =============================================================================================
   Phase 54 54D (2026-09-21) - the celebration over the live field

   THE OWNER'S N-1. "when a score happens, like a TD or a FG when that play gets updated we have an
   animation for that event. Like a celebration or something when a user is viewing that." A member
   holding the live sheet when their quarterback scores currently sees a row appear in a list on the
   next poll and nothing moves. This block is the six seconds that move.

   IT OVERLAYS AND IT NEVER REFLOWS, WHICH IS THE ACCEPTANCE. The panel is absolutely positioned
   against a host element that is ZERO HEIGHT and relatively positioned, so nothing here takes one
   pixel of layout from the situation block it sits in: the heading, the situation line, the field and
   the scoring list under them keep their positions at 360, 600 and 960px. That is also why the block
   declares no width media query at all and why the tests below assert the host's height rather than
   trusting a comment. A dialog that grows under a reading member is worse than no celebration.

   AND IT IS POINTER TRANSPARENT. It stands over the field for six seconds, and a member tapping the
   field, the last play or the drive log in that window must reach what they tapped.

   EVERY SELECTOR IS .ff-lgc- ("live game celebration"), this slice's own prefix, and deliberately not
   54C's .ff-lgm-, LG-2's .ff-lg-, LG-5's .ff-lgd-, 45E's .ff-lgf-, 45F's .ff-lgs-, 45G's .ff-lgk- or
   45I's .ff-lgr-. No name here is a substring of another name here either, so a guard that asks
   whether a rule mentions a class cannot be satisfied by the wrong rule (which is a real hazard: 54C's
   own .ff-lgm-dock-said-mine contains .ff-lgm-dock-said, and its tests compare selectors exactly for
   that reason).

   .ff-lgc-flash IS DELIBERATELY STANDALONE AND ENDS WHERE IT STARTED. It is the phase's one emphasis
   vocabulary, 1.6s per cycle exactly like the live bar's pulse beside it and the draft dock's above
   it, so the surfaces that mark a score do not each celebrate in a language of their own. 54G puts it
   on a red zone card that resolves with a score, which is what makes that the SAME feature as this one
   rather than a second animation; a card has to still be there afterwards, so the frames return to
   neutral and nothing about this class assumes the element it is on is going away.

   COLOUR IS NEVER THE ONLY CARRIER (the rule this family states at LiveGameField.razor:40). The
   sentence is what says a score happened; the tint on a score by the reader's OWN player is emphasis
   on top of a line that already names the player and whose roster he is on.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after 54C's, which is
   the round wide append order resolution R14 fixes and which AppCssIntegrityTests and
   PickInFlightRoomTests both pin: the UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

/* The anchor, and the whole of why nothing reflows: zero height, so it takes no layout, and relatively
   positioned, so the panel has something of its own to be positioned against rather than reaching out
   to whatever ancestor happens to be positioned. It is a block element, so it is already the width of
   the situation block's content box and the panel needs no width of its own. */
.ff-lgc-host {
    position: relative;
    height: 0;
}

/* The panel. Out of flow, pinned across the block's content width, and above the field it covers. */
.ff-lgc-over {
    position: absolute;
    top: 0;
    left: 0;
    right: 0;
    z-index: 2;
    display: flex;
    flex-direction: column;
    gap: .1rem;
    padding: .45rem .6rem;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 6px;
    background: var(--mud-palette-surface);
    /* It stands over the field, the last play and the drive rows for six seconds, and a tap in that
       window belongs to them. */
    pointer-events: none;
    /* A school name plus a player plus a possessive is the longest thing this panel ever says, and it
       has one column to say it in on a 360px phone. */
    overflow-wrap: anywhere;
    opacity: 1;
    /* Six seconds, which is LiveMomentCopy.CelebrationSeconds, so the motion ends exactly when the
       component takes the panel down instead of stopping short or popping back. "forwards" holds the
       last frame for the few milliseconds between the two. */
    animation: ff-lgc-say 6s ease-in-out forwards;
}

/* A score by one of the READER'S OWN players. The line under it already names the player and whose row
   he is, so this is emphasis on a fact that is written out, never the carrier of it. */
.ff-lgc-mine {
    border-color: var(--mud-palette-primary);
}

/* The headline: "Touchdown, Vanderbilt." */
.ff-lgc-kind {
    font-weight: 600;
    line-height: 1.25;
}

/* The scorer line: "The play named Sedrick Alexander, Josh's FLEX." Secondary, because the headline is
   the event and this is who it happened to.

   TWO LINES MAXIMUM, which is plan 9.3 stated where a stylesheet can carry it (audit fix A10,
   2026-09-22). The panel wraps rather than truncating (overflow-wrap: anywhere on .ff-lgc-over), so a
   long school plus two bundled scorers ran to three or four lines at 360px and covered more of the field
   than the spec allows. The clamp is this sheet's own shipped idiom, the same five declarations the
   scoring list's play line uses. It takes no layout from anything: this element is an absolutely
   positioned panel's child and the panel's host is zero height, so what the clamp bounds is how much of
   the FIELD the overlay covers, never where anything under it sits. */
.ff-lgc-who {
    font-size: .78rem;
    line-height: 1.25;
    color: var(--mud-palette-text-secondary);
    display: -webkit-box;
    -webkit-line-clamp: 2;
    line-clamp: 2;
    -webkit-box-orient: vertical;
    overflow: hidden;
}

/* The phase's one emphasis, usable on ANY element (54G's red zone card takes it). Two cycles of 1.6s,
   the same 1.6s the live bar's pulse and the draft dock's use, and the frames return to neutral so an
   element that has to survive the animation does. */
.ff-lgc-flash {
    animation: ff-lgc-flash 1.6s ease-in-out 2;
}

/* In, hold, out. Opacity and a transform only: both are paint, so neither can reflow the panel, the
   block it covers or the page around them. The first stop is 200ms of the six seconds. */
@keyframes ff-lgc-say {
    0% { opacity: 0; transform: translateY(-4px); }
    3.33% { opacity: 1; transform: translateY(0); }
    92% { opacity: 1; transform: translateY(0); }
    100% { opacity: 0; transform: translateY(-4px); }
}

@keyframes ff-lgc-flash {
    0%, 100% { opacity: 1; transform: scale(1); }
    50% { opacity: .78; transform: scale(1.02); }
}

/* Reduced motion: the panel, the headline and the scorer line all stay, and only the movement goes. The
   component's own six second timer still takes the panel down, so what a member who asked their device
   for less motion gets is the same sentence for the same six seconds without anything moving. Less
   motion is not less information. */
@media (prefers-reduced-motion: reduce) {
    .ff-lgc-over,
    .ff-lgc-flash {
        animation: none;
        transition: none;
    }
}

/* ---- end 54D ---- */

/* =============================================================================================
   Phase 55 55H (2026-09-21) - the dock a desktop can see

   THE OWNER'S N-9, AND IT IS THREE DECLARATIONS. "it's really hard to notice that live dock on bigger
   screens since it is the same color, maybe we either make the color a little different or add a
   border." He is exactly right about the cause: 45G paints the bar in --mud-palette-surface, which is
   the same token every card on the page behind it is painted in, so at 1920px over the AI insights row
   a pill in the page's own colour with a 12% line around it is a pill nobody can find. He also praised
   the dock itself ("working and I absolutely love that"), so the whole of this block is background,
   border and shadow: not one thing about the bar's behaviour, its geometry or its words moves.

   THE BORDER IS WHAT CARRIES IT, IN BOTH THEMES, AND THAT IS MEASURED RATHER THAN ASSUMED. MudBlazor
   has no raised-surface token that clears 3:1 against a surface: the only surface variation in the
   palette is --mud-palette-background-gray, which measures 1.09:1 against the light surface (#f5f5f5
   against #ffffff) and 1.07:1 against the dark one (#27272f against this app's #16213e). It is worth
   having anyway, because in dark it is a HUE change rather than a lightness one (charcoal against
   navy) and that is the "different color" half of what was asked for, but it is a supporting cue and
   the acceptance does not rest on it. The line does: --mud-palette-text-secondary measures 4.85:1 in
   light (rgba(0,0,0,.537) composited over the bar's own #f5f5f5) and 7.33:1 in dark (#b0b0b0 against
   #16213e), against 1.31:1 and 1.43:1 for the --mud-palette-lines-default line it replaces.
   LiveDockVisibilityTests computes all four from the live palette rather than from these numbers, so a
   palette change that broke the rule would name itself instead of quietly shipping.

   IT CANNOT CHANGE THE BAR'S SIZE, WHICH IS THE SAME CONSTRAINT 54C's BLOCK ABOVE CARRIES. The bar is
   fixed at the bottom of the app and the page reserves room for exactly one line of it
   (--ff-lgk-dock-clearance, FOOT-1, and 58 §15.1 requires any height change to move it in the same
   PR), so the border here REPLACES 45G's rather than adding to it: same 1px, same box-sizing:border-box
   box, so the used height is byte for byte what it was. The shadow is a box-shadow, which is paint and
   takes no layout at all. There is no padding, no margin, no width, no height and no min-height in
   here, and the clearance variable is neither read nor written.

   IT DOES NOT FIGHT 54C's PULSE. That block declares no background, no border, no outline and no
   shadow: it is an animation of opacity and a 2% scale, and a scale is a paint transform that carries
   this border and this shadow with it rather than against them. The two blocks share the bar and do
   not share a property. (At the pulse's 50% trough the whole bar sits at .72 opacity, which takes the
   light border to 2.85:1 for a fraction of a second; the resting state the acceptance measures is
   4.85:1, and the motion is 54C's.)

   COLOUR IS NEVER THE ONLY CARRIER (plan §9.4). The bar still says "Live now" in words and still
   carries its own dot, and that is what says a game is being played. This edge carries findability and
   nothing else, so a member who cannot tell these two greys apart loses no fact. And the focus ring is
   untouched: .ff-lgk-dock-bar:focus-visible is an outline, which is painted outside the border box and
   wins on specificity besides, so a keyboard member still gets the 2px primary ring at 2px offset.

   A PHONE SEES ALMOST NOTHING CHANGE, WHICH IS THE POINT (plan §9.1: "visibly unchanged"). There is no
   media query here because there is nothing to vary: at 360px the bar keeps its size to the pixel, and
   what a phone gets is a crisper line and a soft halo around the same pill in the same place.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after 54C's, which is
   where every slice in this round appends and which AppCssIntegrityTests and PickInFlightRoomTests both
   pin: the UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

/* The bar 45G declares four thousand lines above, and only the three properties that decide whether a
   member can find it. Every colour is a palette token, so both themes are correct by construction; the
   shadow is a literal black at low alpha, which is what every other shadow in this sheet is, because
   the palette has no shadow token to spend. */
.ff-lgk-dock-bar {
    background: var(--mud-palette-background-gray);
    border: 1px solid var(--mud-palette-text-secondary);
    box-shadow: 0 0 12px rgba(0, 0, 0, .28);
}

/* ---- end 55H ---- */

/* =============================================================================================
   Phase 54 54G (2026-09-21) - the red zone card carries its drive, and says how it ended

   THE OWNER'S N-7, AND SUGGESTIONS S-3 AND S-7. A red zone card is a still photograph of a drive
   that is in motion, and then it disappears mid drive. This block draws the drive under way on the
   focused card (its newest four plays, and who in the league is on that offense) and styles the card
   that is HELD for twenty seconds after the drive leaves the list so it can say how it ended.

   EVERY SELECTOR IS .ff-rzd- ("red zone drive"), a prefix no other block in this sheet uses and
   which contains none of theirs: deliberately not 45I's .ff-lgr- which paints the panel around it,
   nor LG-2's .ff-lg-, LG-5's .ff-lgd-, 45E's .ff-lgf-, 45F's .ff-lgs-, 45G's .ff-lgk- or 54C's
   .ff-lgm-. The blocks are appended separately, so none may win a cascade against another by
   accident, and a prefix that is a substring of a neighbour's is how that happens without anybody
   editing a rule.

   360px FIRST, AND NO BREAKPOINT AT ALL. A card with a drive on it is a COLUMN of columns: the block
   stacks under the row's own lines, each play is its own stacked pair of a situation and its text,
   and every long string may break inside a word, because a play description is the longest thing
   this panel ever renders and a phone is 360px wide. Nothing here declares a pixel width, a
   min-width or a second horizontal scroller, so one rule is right from 320px to 1920.

   COLOUR IS NEVER THE ONLY CARRIER, and nothing here is carried by colour at all: the outcome is a
   SENTENCE ("Touchdown, 7 points."), the state is an attribute, and the tint on a scored resolve is
   decoration over a card that already reads correctly in grey. The one animation is a 220ms fade on
   the outcome line, and it has its own prefers-reduced-motion arm.

   THE DELTA SLOT TAKES NO ROOM UNTIL SOMETHING IS IN IT (round resolution R16). 55D fills
   .ff-rzd-delta with the member's fantasy delta for this drive under its own key; while that key is
   dark the element is empty, and an empty one is display:none, so a member reads the drive and no
   gap where a number would be.

   THE SCORED CARD BORROWS 54D'S .ff-lgc-flash, AND THIS BLOCK DECLARES NO ANIMATION, OPACITY OR
   TRANSFORM ON THE CARD ITSELF, so the two can never reach the same property on the same element.
   That is the whole reason N-7 is the same feature as N-1 rather than a second celebration: the class
   is the contract, none of its keyframes are copied down here, and the one animation this block does
   declare is on the outcome LINE, a child of the card, which plays under the flash rather than
   against it. 54D's class carries its own reduced motion arm, so a member who asked for less motion
   reads the same sentence with nothing moving.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after 54D's, which
   is where every slice in this round appends and which AppCssIntegrityTests and PickInFlightRoomTests
   both pin: the UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

/* The drive, under the row's own lines. A column, so it stacks at every width. */
.ff-rzd-drive {
    box-sizing: border-box;
    display: flex;
    flex-direction: column;
    gap: .25rem;
    max-width: 100%;
    margin-top: .35rem;
    padding-top: .35rem;
    border-top: 1px solid var(--mud-palette-lines-default);
}

.ff-rzd-plays {
    display: flex;
    flex-direction: column;
    gap: .25rem;
    max-width: 100%;
}

/* One snap. The situation and the text are stacked rather than inline, because a down and distance
   phrase plus a full play description is two lines on a phone whatever is done to it, and a wrapped
   inline pair reads as one run-on sentence. */
.ff-rzd-play {
    display: flex;
    flex-direction: column;
    max-width: 100%;
    overflow-wrap: anywhere;
}

.ff-rzd-play-sit {
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
}

.ff-rzd-play-text {
    font-size: .76rem;
}

/* The payload's own sentence, IN PLACE OF the strip: this game's play by play is not being captured,
   in the words the server composed rather than in words of this panel's. */
.ff-rzd-note {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    max-width: 100%;
    overflow-wrap: anywhere;
}

/* Who in the league is on the offense with the ball. */
.ff-rzd-offense {
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    max-width: 100%;
    overflow-wrap: anywhere;
}

/* 55D'S SLOT. Empty is zero sized, so nothing on this card moves while the stat line's key is dark;
   filled, it is an ordinary block in the column above it. */
.ff-rzd-delta {
    max-width: 100%;
    overflow-wrap: anywhere;
}

.ff-rzd-delta:empty {
    display: none;
}

/* The card that is being held after its drive left the list. It is visibly a different thing from a
   live red zone row: dimmer, and with a dashed edge rather than the panel's solid one, because it is
   a game that is no longer in anybody's twenty. */
.ff-rzd-resolved {
    box-sizing: border-box;
    display: flex;
    flex-direction: column;
    gap: .25rem;
    max-width: 100%;
    margin-top: .5rem;
    padding: .5rem;
    border: 1px dashed var(--mud-palette-lines-default);
    border-radius: .5rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-rzd-resolved-head {
    font-size: .8rem;
}

/* How it ended, when this platform can prove how it ended. A card that cannot prove it simply has no
   such line, which is why the state attribute rather than this element is what a rule hangs off. */
.ff-rzd-outcome {
    font-size: .82rem;
    color: var(--mud-palette-text-primary);
    animation: ff-rzd-resolve-in .22s ease-out 1;
}

/* A resolve that SCORED. The tint is decoration: the sentence above it already says what happened,
   and the state attribute already says which state this is. */
.ff-rzd-resolved[data-rz-resolve="scored"] {
    border-style: solid;
    border-color: var(--mud-palette-error);
    background: rgba(var(--mud-palette-error-rgb), .08);
}

@keyframes ff-rzd-resolve-in {
    from { opacity: 0; }
    to { opacity: 1; }
}

/* Reduced motion: the card, the tint and every word stay, and only the fade goes. A member who has
   asked their device for less motion is asking for less motion, not for less information. */
@media (prefers-reduced-motion: reduce) {
    .ff-rzd-outcome {
        animation: none;
        transition: none;
    }
}

/* ---- end 54G ---- */

/* =============================================================================================
   Phase 57 57L (2026-09-21) - the Scoreboard row's column strip, and one empty card that cost 200px

   THE OWNER'S N-20, AND IT IS A MEASUREMENT RATHER THAN A TASTE. On a 1750px desktop the This Week
   row carried a rank, an avatar, a name, a caption and a total, and every pixel between the name
   (ending about x=480) and the total (x=1900) was empty. This block is the strip that fills it, and
   the whole of the block's job is WHEN it is allowed to exist.

   960px, AND BELOW IT THE STRIP IS NOT THERE. display:none rather than a visual hide, so the strip
   takes no part in the row's layout at all and a phone row is the row that shipped, box for box: same
   flex children, same gaps, same height. That is the acceptance this slice is held to, and it is why
   the breakpoint is 960 rather than the sheet's usual 600: six stacked label-and-value cells beside a
   name need real horizontal room to read as denser rather than as more cramped, and a tablet is where
   they would start truncating. Between 600 and 960 the row stays today's, which is the honest degrade,
   because every fact the strip carries is also one tap away in the expanded panel.

   NO FACT TWICE ON ONE ROW. The gap to the leader was already in the row's caption, and the This Week
   strip now carries it as a column, so from 960px up the caption's copy of it stands down
   (.ff-denserow-echo). The parent decides which rows get that class: the Season strip measures weeks
   and carries no gap, so its caption keeps the fact at every width. Below 960 the class is inert and
   the caption reads exactly as it always has.

   TABULAR FIGURES AND THE EXPANDED PANEL'S OWN TYPE. The cells are the .ff-sb-season-stat idiom
   (uppercase quiet label over a tabular value) at a smaller size, because the expanded row is where a
   member already meets these numbers and one vocabulary is the point. Colour is never the only
   carrier: .ff-denserow-lead only lifts a value from the secondary text colour to the primary one, and
   every value it marks is a signed comparison whose sign or arrow says the same thing in monochrome.

   THE ONE LINE EMPTY CARD (.ff-denserow-oneline) is the same slice's second half. The Pool spotlight's
   waiting state spent about 200px of height on one sentence directly above the tabs the owner called
   empty, because it borrowed the shared full height .ff-empty-state shape. It keeps that class, keeps
   its icon, its sentence, its caption and its way out, and only lays them on one line at the card's
   normal row height. The populated card is untouched, and so is every other use of .ff-empty-state.

   EVERY SELECTOR IS .ff-denserow-, this slice's own prefix: deliberately not .ff-sb-, which is the
   board's own block above, so this block can never win a cascade against it by accident, and the
   component carries both sets of classes rather than this block reaching into that one.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after 54C's, which is
   where every slice in this round appends and which AppCssIntegrityTests and PickInFlightRoomTests both
   pin: the UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

/* Not rendered below the breakpoint. The element is in the markup at every width (a Blazor component
   cannot measure a viewport, and the sheet is where this platform has always made that decision: see
   .ff-sb-spark and .ff-sb-chipdetail above), and display:none takes it out of the layout entirely, so
   the row's box at 360px is the box it had before this slice. */
.ff-denserow-strip { display: none; }

@media (min-width: 960px) {
    .ff-denserow-strip {
        display: flex;
        flex: 0 1 auto;
        align-items: center;
        gap: 14px;
        min-width: 0;
    }

    /* One fact: a quiet uppercase label over its value. min-width keeps the columns in line down the
       board when one member's cell holds a placeholder glyph and their neighbour's holds a number. */
    .ff-denserow-cell {
        display: flex;
        flex-direction: column;
        gap: 1px;
        min-width: 48px;
    }

    .ff-denserow-k {
        font-size: .58rem;
        font-weight: 700;
        letter-spacing: .04em;
        text-transform: uppercase;
        white-space: nowrap;
        color: var(--mud-palette-text-secondary);
    }

    .ff-denserow-v {
        font-size: .8rem;
        font-weight: 600;
        font-variant-numeric: tabular-nums;
        white-space: nowrap;
        color: var(--mud-palette-text-secondary);
    }

    /* A signed comparison reads at the row's own text colour, which is the only difference. */
    .ff-denserow-lead .ff-denserow-v { color: var(--mud-palette-text-primary); }

    /* The caption's copy of a fact the strip beside it is now carrying. */
    .ff-denserow-echo { display: none; }
}

/* The waiting state, on one line at the card's normal row height. It overrides the shared shape's
   stacking, its centring and its 34px of padding, and nothing else: the modifier is later in the sheet
   at the same specificity, so everything else that shape says (the muted colour, the icon's opacity)
   still applies here and on every other surface that uses it. */
.ff-denserow-oneline {
    flex-direction: row;
    flex-wrap: wrap;
    justify-content: flex-start;
    align-items: center;
    text-align: left;
    gap: 4px 8px;
    padding: 4px 0;
}

/* ---- end 57L ---- */

/* =============================================================================================
   Phase 54 54F (2026-09-21) - the red zone reads as a state on the live page

   THE OWNER'S N-18. "Do we have anything on the actual live page for when teams are in the red zone?
   ... an actual red zone look would be cool since we have a lot more room to do something." The answer
   was no, and worse than it looked: the word lived only in the pre stage fallback branch, so with the
   stage flag on, which is production, nothing on the live page said red zone at all. This block is what
   the state looks like once it says it.

   NO MOTION AT ALL, DELIBERATELY (plan §9.1). Every other block this phase appends animates something;
   this one animates nothing, because a state that pulses for a whole drive is a state members turn off.
   It is a frame, a background and a stronger tint on one end zone, and there is therefore no
   prefers-reduced-motion arm here: there is no motion to reduce, which the guard below asserts rather
   than assumes.

   COLOUR IS NEVER THE ONLY CARRIER (the rule this family states at LiveGameField.razor:40). The WORD is
   on the page: the chip says RED ZONE or GOAL TO GO beside the situation line, in the shipped
   LiveGameFormat labels, and the stage adds a sentence naming the members with a player on that offense.
   The frame and the end zone's tint are emphasis on a fact that is written out.

   360px FIRST, and the whole reason this block declares no breakpoint and no pixel width. The chip sits
   ON the situation line as a flex line that WRAPS, so a long down and distance pushes the chip to its
   own row rather than pushing a horizontal scroller; the situation text may shrink below its content and
   break inside a word, which is what keeps a school name from widening the dialog on a phone.

   EVERY SELECTOR IS .ff-lgz- ("live game zone"), this slice's own prefix, and deliberately not LG-2's
   .ff-lg-, LG-5's .ff-lgd-, 45E's .ff-lgf-, 45F's .ff-lgs-, 45G's .ff-lgk-, 45I's .ff-lgr-, 54C's
   .ff-lgm- or 54D's .ff-lgc-. No name here is a substring of another name here either, so a guard that
   asks whether a rule mentions a class cannot be satisfied by the wrong rule.

   THE ONE COMPOUND SELECTOR IS THE POINT OF THE SLICE, not a reach into another block. 45E paints both
   red zones and emphasises the attacked one at .ff-lgf-zone.on; this state's token is a SECOND class the
   component adds beside that one, so the rule has to name both to be the stronger of the two rather than
   a second opinion about the same element. Naming both also makes it strictly narrower than a bare
   .ff-lgz-threat would be: it can only ever match an element that already carries this slice's class.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after 54D's, which is
   the round wide append order resolution R14 fixes and which AppCssIntegrityTests and PickInFlightRoomTests
   both pin: the UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

/* The situation block while the offense is inside the twenty. A frame and a ground, so the block reads
   as a state rather than as the same block with an extra word in it. The radius and the padding are the
   only layout this block takes, and they are taken by the SECTION, which is already a flex column that
   may shrink (.ff-lg-block declares min-width: 0). */
.ff-lgz-state {
    padding: .5rem;
    border: 1px solid var(--mud-palette-error);
    border-radius: 6px;
    background: var(--mud-palette-background-gray);
}

/* The situation line and the chip on one line, wrapping rather than scrolling. */
.ff-lgz-line {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: .5rem;
    min-width: 0;
}

/* The situation text as a flex item. A flex item's min-width is auto, which would hold the line open at
   the width of the longest unbroken run in "2nd and 7 at OSU 31"; zero plus a break anywhere is what
   lets it wrap inside a word on a 360px phone instead. */
.ff-lgz-sit {
    min-width: 0;
    overflow-wrap: anywhere;
}

/* The word itself. Short, upper case and framed, which is the shipped .ff-lg-zone chip's vocabulary
   rather than a second one, in this block's own class so the two cannot fight over a cascade. */
.ff-lgz-chip {
    padding: 0 8px;
    border-radius: 999px;
    border: 1px solid var(--mud-palette-error);
    color: var(--mud-palette-error);
    font-size: .62rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
    white-space: nowrap;
}

/* The stage only: which members have a player on the offense that is in the red zone. Secondary, because
   the state above it is the event and this is who it is happening to. */
.ff-lgz-offense {
    font-size: .78rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

/* The threatened end zone, on top of the emphasis 45E already gives the attacked one. Both zones are
   still always drawn and 45E's rule still decides which one is attacked; this only makes that one read
   as threatened. */
.ff-lgf-zone.on.ff-lgz-threat {
    opacity: .45;
}

/* ---- end 54F ---- */

/* =============================================================================================
   Phase 55 55E (2026-09-21) - the live stage says it is coming

   THE SHAPE OF THE PAGE THAT IS COMING, and nothing else. Every piece inside this grid is Phase 52's
   PanelSkeleton, styled by 52B's own .ff-skel-* rules; this block owns the COLUMNS the pieces are laid
   out in and one spacing override inside its own container. There is no second skeleton here, no
   animation of its own (the primitive's wave is the only motion) and no colour at all, which is why
   there is no palette token in the whole block: every surface that has one is the primitive's.

   ONE BREAKPOINT, AND IT IS THE STAGE'S OWN 1280px. 45F's block turns the stage into columns at exactly
   the width the live tap rule sends a desktop to this page (LiveTapDestination.PageWidthPx), so the
   silhouette has to change at the same width or the picture would arrive in a different number of tracks
   than the shape that was standing for it, and the page would reflow on the one frame the silhouette
   exists to make still. Below it the grid is one column and the three groups stack in the stage's own
   phone order, which is why there is no second breakpoint here and none is wanted.

   360px FIRST, and it is a fold claim rather than a width claim. No rule here declares a pixel width, a
   min-width or a horizontal scroller: the tracks are fractions of whatever holds them and every gap is
   in rem, so the silhouette is exactly as wide as the page column at every viewport. Its stacked height
   at 360px is about 540px, comfortably inside one phone fold and a small fraction of the stage that
   replaces it, so the silhouette reserves room for what is arriving without pushing the matchup page's
   own blocks further down than the stage itself will. LiveGameStageSkeletonTests recomputes that from
   52B's declared heights rather than trusting this paragraph.

   EVERY SELECTOR IS .ff-lgl- ("live game loading"), this slice's own prefix, and deliberately not LG-2's
   .ff-lg-, LG-5's .ff-lgd-, 45E's .ff-lgf-, 45F's .ff-lgs-, 45G's .ff-lgk-, 45I's .ff-lgr-, 54C's
   .ff-lgm-, 54D's .ff-lgc- or 54F's .ff-lgz-. No name here is a substring of another of them in either
   direction, so a guard that asks whether a rule mentions a class cannot be satisfied by the wrong rule,
   and the one rule that reaches a 52B class does so only from inside a .ff-lgl- container.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after 54F's, which is
   the round wide append order resolution R14 fixes and which AppCssIntegrityTests and PickInFlightRoomTests
   both pin: the UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

/* The silhouette's own grid, which is 45F's stage grid with 45F's own gap: one column everywhere the
   stage is one column. */
.ff-lgl-skeleton {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    gap: 1rem;
    margin-bottom: 1rem;
}

/* One group of pieces, standing in for one column of the stage. It may shrink below its content for the
   reason every column in this family may: a grid child's default min-width would hold the track open at
   the width of the widest piece inside it. */
.ff-lgl-col {
    display: flex;
    flex-direction: column;
    gap: .75rem;
    min-width: 0;
}

/* The primitive spaces itself for a surface that stacks its pieces directly on a page. Inside a column
   the column's own gap is the spacing, so the piece's margin would be a second one added to it. */
.ff-lgl-col .ff-skel {
    margin-bottom: 0;
}

@media (min-width: 1280px) {
    /* Two tracks with no room to show and three with one, which is exactly what the stage does with the
       same parameter: with chat dark the people column flows under the game column rather than being
       stretched to cover a hole, and the silhouette says the same thing. */
    .ff-lgl-skeleton { grid-template-columns: minmax(0, 1.15fr) minmax(0, 1fr); }

    .ff-lgl-skeleton.ff-lgl-room {
        grid-template-columns: minmax(0, 1.15fr) minmax(0, 1fr) minmax(0, .95fr);
    }
}

/* ---- end 55E ---- */

/* =============================================================================================
   Phase 55 55C (2026-09-21) - what the dots say on a phone

   THE OWNER'S N-3, and the whole of it. "What are the dots on the field?" was answered three times on
   2026-09-18 and every answer was a POINTER's: a title needs a hover, and the legend says what the dots
   are without saying what any one of them says. The owner was on a phone. So the mark became a button,
   and these are the two things a button needs that the picture did not already have: somewhere for the
   touch to land, and a way to see which dot is the one being read.

   NO NEW SENTENCE AND NO NEW COLOUR. The readout prints ScoreLabel's own string, which is the same
   string the title and the accessible name carry, so this block styles TYPE and never words. The
   selected mark is ringed rather than re-tinted, because the dot's tint is the school that scored and a
   selection painted in colour would take that carrier away from it.

   THE TAP TARGET IS 44px AT 360px, and it is stated in the MARKUP rather than here, which is the one
   thing worth knowing about this block. The picture is a 120 unit viewBox at 100% width, so on a 360px
   phone a unit is three CSS pixels and the radius that makes 44px is 7.4 units: a number in the field's
   own coordinate space, which no stylesheet declaration can carry. What this block does is make that
   circle invisible and leave it clickable, which is exactly one declaration.

   EVERY SELECTOR IS .ff-lgt- ("live game tap"), this slice's own prefix, and deliberately not LG-2's
   .ff-lg-, LG-5's .ff-lgd-, 45E's .ff-lgf-, 45F's .ff-lgs-, 45G's .ff-lgk-, 45I's .ff-lgr-, 54C's
   .ff-lgm-, 54D's .ff-lgc- or 54F's .ff-lgz-. No name here is a substring of another name here either,
   so a guard that asks whether a rule mentions a class cannot be satisfied by the wrong rule.

   EXACTLY ONE RULE BELOW NAMES 45E's CLASSES, the last one, and it is the tap's own consequence rather
   than a reach into somebody else's block: two full height lines are painted after the dots and would
   take the tap off them. It declares nothing but pointer-events, and the guard pins the count at one, the
   two names exactly and the single declaration, so it cannot grow. The MARK is still untouched, which is
   what "the target grows and the dot does not" means in a stylesheet.

   NO MOTION, NO BREAKPOINT AND NOTHING SIZED IN PIXELS. The readout appears and disappears with the
   selection, and a fade on a line that answers a tap would be a delay between the tap and its answer.
   Nothing here declares a width, a height or a breakpoint: every measurement the picture takes is in the
   SVG's own units and lives in the markup, so it scales with the picture at every viewport. The one px
   in this block is the focus ring's outline, which is a device affordance rather than a layout size and
   is deliberately NOT scaled: a focus ring that shrank with the container would vanish on a phone.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after the blocks already
   there, which is the round wide append order resolution R14 fixes and which AppCssIntegrityTests and
   PickInFlightRoomTests both pin: the UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

/* Every scoring mark is a button now, so it says so to a pointer. */
.ff-lgt-dot { cursor: pointer; }

/* And it says so to a keyboard. A role="button" that cannot be seen to have focus is a control only a
   mouse can find, which is the defect this slice exists to fix from the other side. The ring is the
   theme's own ink, so it reads in both themes and on either school's colour. */
.ff-lgt-dot:focus-visible {
    outline: 2px solid var(--mud-palette-text-primary);
    outline-offset: 2px;
}

/* The touch target. Transparent rather than absent: a shape with no fill at all receives no pointer
   events over its interior, which would leave a 44px circle that only works on its edge. */
.ff-lgt-hit { fill: transparent; }

/* The selected mark's ring. Stroke only, so the dot's own tint (the school that SCORED) still shows
   through it and the selection is a second carrier rather than a replacement for the first. The rule is
   keyed on the selected group as well as on the ring, which is strictly narrower than naming the ring
   alone: it can only ever match a ring inside the one dot that is selected. */
.ff-lgt-on .ff-lgt-ring {
    fill: none;
    stroke: var(--mud-palette-text-primary);
    stroke-width: .5;
}

/* The readout line. It sits under the legend and borrows LG-2's .ff-lg-note sentence class for its size
   and its wrapping, so this rule is the one thing that separates the two: the legend says what the dots
   ARE and is secondary, this says what the tapped one SAYS and is the answer, so it takes the primary
   ink and the heavier weight. */
.ff-lgt-read {
    font-weight: 600;
    color: var(--mud-palette-text-primary);
}

/* THE ONE RULE IN THIS BLOCK THAT NAMES 45E's OWN CLASSES, and the reason it has to.

   An SVG has no z-index: the topmost painted shape takes the tap. 45E draws the line of scrimmage and
   the first down line AFTER the scoring dots and both run the full height of the picture, so before this
   slice they crossed every dot harmlessly and now they cross its tap target and win it. That is a defect
   this slice introduces, so it is this slice that closes it, and nothing is lost by refusing them the
   tap: both are decoration with no title, no accessible name and no handler of their own, so a tap that
   reached them did nothing at all.

   IT IS THOSE TWO AND NOTHING ELSE, which was checked rather than assumed. The turf, both zone rects,
   the yard lines, their numbers, the two end zones and the drive's trail are all painted BEFORE the dots,
   so paint order already puts a dot on top of them. The ball marker and the direction arrow are painted
   after, but both sit on the trail across the middle of the field while the dots sit low, so neither can
   reach a dot's target at any yard line. Turning pointer events off on those would cost the picture a
   hit region a later slice may want and buy nothing today. */
.ff-lgf-los,
.ff-lgf-first {
    pointer-events: none;
}

/* ---- end 55C ---- */

/* =============================================================================================
   Phase 54 54H (2026-09-21) - a red zone card that opens a game says so to a mouse

   ONE DECLARATION, AND IT IS THE TAP DEFECT SEEN FROM A MOUSE. 54H made a red zone card open its
   game (the owner's N-17), and the card announced that to everything except a pointer: it carries
   role="button", a tabindex, Enter and Space and its own focus ring, so a keyboard and a screen
   reader are told, while a mouse hovering a card that opens a game got the arrow cursor and no hint
   at all. That is the same "clicking it just lights up the button" report N-6 came from, one input
   device along. On a phone, which is where the owner asked for this, a thumb needs no cursor and
   gets none, so the feature was already complete there and this block changes nothing about it.

   IT DECORATES 45I'S CLASS ON PURPOSE, AND THE ROLE IS THE GATE. Every other block in this family
   owns a prefix of its own because it owns elements of its own; this one owns no element, so a
   prefix of its own would be a second way of saying "this card is a control" and the two could
   disagree. The attribute selector is the gate instead, and it is the same one the markup already
   answers: with Features:LiveGameSheetEnabled dark the page hands the panel a callback whose
   HasDelegate is false and no card carries a role at all, so this rule matches nothing whatsoever
   there and the dark board keeps the cursor it has always had.

   NOTHING ELSE IS IN HERE. No colour, no size, no motion, no breakpoint, no hover or focus state:
   the card's emphasis, its focus ring and its whole layout are 45I's and stay 45I's. This block
   cannot change what a card looks like, only what the pointer over one looks like, which is why it
   declares a single property and why its guard asserts that it declares exactly one.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after every block
   that had landed when it was written, which is where every slice in this round appends and which
   AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker has to stay the last
   block marker in the sheet. Its own ordering guard deliberately asserts that this block sits after
   54G's end marker and before UX-1's rather than naming an immediate neighbour, because the round's
   remaining client slices append between those two.
   ============================================================================================= */

.ff-lgr-row[role="button"] { cursor: pointer; }

/* ---- end 54H ---- */

/* =============================================================================================
   Phase 55 55I (2026-09-21) - Live Now opens in place, and the week's race reads on the board

   THREE THINGS, ALL OF THEM GAME DAY'S, and one prefix for them: .ff-gdw- ("game day week"). The
   owner's N-5 ("when it goes to a game tho, I think when you close it should go back to gameday
   instead of the matchups"), O-3's invisible scope ("Live now lists 2 games while Matchups lists 13",
   which is by design and was nowhere stated), and S-5's week race.

   THE ROW BECAME A CONTROL, SO IT NEEDS A CONTROL'S TWO STATES. The Live Now entry was an anchor to
   the slate and is now a role="button" span that opens the sheet on THIS page, which is the whole of
   N-5: an anchor navigated away, so closing the sheet stranded a member on Matchups. The LIVE FIRST
   block earlier in this sheet styles .ff-gd-livenow .gm for every state the chip has, and one of its
   rules is keyed on the element being an anchor (a.gm:hover, a.gm:focus-visible), which a span cannot
   satisfy. So .ff-gdw-tap carries the pointer and the two states across, on the same two error tinted
   tokens that rule already used, and it is added to the row ONLY while Features:MatchupsEnabled is
   lit. With that dark the row carries neither this class nor a role, so the strip is character for
   character the strip that shipped, which is what GameDayLiveNowInPlaceTests asserts.

   THE SCOPE AND THE WAY OUT SIT IN THE STRIP'S OWN FLEX LINE, so they wrap with it rather than
   needing a row of their own. At 360px each takes the whole line, under the games, which is the same
   rule LIVE FIRST's own phone breakpoint applies to the chips: the label reads, then the games, then
   what they are and where the rest of them live.

   THE RACE IS A GRID, ONE COLUMN THEN TWO, and the two numbers never wrap. One row per member at
   360px with the name truncating, and two columns from 960px, which is the plan's own breakpoint
   matrix. The name is the only cell allowed to shrink (minmax(0, 1fr)) and the two numbers are
   nowrap with tabular figures, so a ten member league reads as a column of aligned digits rather
   than as a ragged list. There is no rank tint and no medal: the board in the panel below owns the
   placing vocabulary, and a second gold row on one screen would be two surfaces claiming one fact.

   NO FIXED SIZE AND NO SECOND SCROLLER ANYWHERE. Every sizing declaration is fr, %, auto or minmax,
   which is what keeps a 360px phone holding a ten member race off a horizontal scrollbar, and every
   colour is a palette token so the dark default and the light toggle are both correct by
   construction rather than by a second set of rules.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after 54H's end
   marker, which is where every slice in this round appends and which AppCssIntegrityTests and
   PickInFlightRoomTests both pin: the UX-1 end marker has to stay the last block marker in the
   sheet. Its own ordering guard names 54H's marker and UX-1's rather than an immediate neighbour,
   because this round's remaining client slices append between those two.
   ============================================================================================= */

/* ---- the Live Now row, now that a tap opens the game here ---- */

/* The pointer, and the one thing a span that behaves like a button owes a mouse. The row's size, its
   pill and its border are LIVE FIRST's and stay LIVE FIRST's: nothing here changes what the chip
   looks like at rest. */
.ff-gdw-tap {
    cursor: pointer;
}

/* The two states the anchor rule carried, on the same two tokens, so a row that opens a game looks
   under a pointer and under a keyboard exactly as it did when it was a link. */
.ff-gdw-tap:hover,
.ff-gdw-tap:focus-visible {
    background: rgba(var(--mud-palette-error-rgb), .10);
    border-color: var(--mud-palette-error);
}

/* ---- what the strip is showing, and the way to everything it is not ---- */

/* Plain copy rather than a chip: it explains the list beside it and must not read as another tap
   target in a row of tap targets. */
.ff-gdw-scope {
    min-width: 0;
    font-size: .72rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-gdw-all {
    min-width: 0;
    font-size: .72rem;
    font-weight: 600;
    color: var(--mud-palette-primary);
    text-decoration: none;
    overflow-wrap: anywhere;
}

.ff-gdw-all:hover,
.ff-gdw-all:focus-visible {
    text-decoration: underline;
}

/* ---- the week's race ---- */

.ff-gdw-race {
    margin: 0 0 16px;
    padding: 10px 12px;
    border-radius: 10px;
    border: 1px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-surface);
}

.ff-gdw-race-hd {
    margin-bottom: 8px;
    font-size: .72rem;
    font-weight: 700;
    text-transform: uppercase;
    letter-spacing: .06em;
    color: var(--mud-palette-text-secondary);
}

.ff-gdw-race-rows {
    display: grid;
    grid-template-columns: 1fr;
    gap: 2px 18px;
}

/* A flex line rather than a grid, so the live cell can be ABSENT without leaving a track and a gap
   behind it: a league with the board's live detail dark reads a three cell row and not a four cell
   row with an empty one at the end. */
.ff-gdw-race-row {
    display: flex;
    align-items: baseline;
    gap: 8px;
    padding: 4px 0;
    font-size: .82rem;
    line-height: 1.3;
}

.ff-gdw-race-row.me .ff-gdw-race-who { font-weight: 700; }

.ff-gdw-race-rk {
    flex: none;
    font-size: .72rem;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
    white-space: nowrap;
}

/* THE ONLY CELL ALLOWED TO SHRINK, which is what makes the truncation land on the name and the digits
   stay whole at 360px. */
.ff-gdw-race-who {
    flex: 1 1 auto;
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
    color: var(--mud-palette-text-primary);
}

.ff-gdw-race-pts {
    flex: none;
    font-weight: 700;
    font-variant-numeric: tabular-nums;
    white-space: nowrap;
    color: var(--mud-palette-text-primary);
}

/* The live figure rides the SAME line as the total and is absent whenever the board published none,
   so a league with the live detail dark reads a three cell row rather than a blank fourth cell. */
.ff-gdw-race-live {
    display: inline-flex;
    align-items: baseline;
    flex: none;
    gap: 4px;
    font-size: .72rem;
    font-variant-numeric: tabular-nums;
    white-space: nowrap;
    color: var(--mud-palette-error);
}

.ff-gdw-race-live .k {
    text-transform: uppercase;
    letter-spacing: .04em;
}

.ff-gdw-race-live .v { font-weight: 700; }

@media (min-width: 960px) {
    /* Two columns above the fold, which is the plan's breakpoint matrix: a ten member league reads
       as five rows rather than ten on the screen the owner keeps Game Day open on. */
    .ff-gdw-race-rows { grid-template-columns: 1fr 1fr; }
}

@media (max-width: 599.98px) {
    /* The strip's own phone rule stacks the games full width; these two take a line each under them
       rather than squeezing onto the end of the last game's row. */
    .ff-gdw-scope { flex-basis: 100%; }
    .ff-gdw-all { flex-basis: 100%; }
    /* A phone reads the race as one row per member, which is the grid's own default, and the row
       keeps its three cells so the live figure stays beside the total rather than under it. */
    .ff-gdw-race { padding: 8px 10px; }
}

/* ---- end 55I ---- */

/* =============================================================================================
   Phase 55 55F (2026-09-22) - the since kickoff line answers a tap, and names its swings

   THE OWNER'S N-4 AND S-6. The finished game's chart answers a hover with the clock and the
   probability; the live sheet's line answered nothing at all, and the shape under it said nothing
   about what had happened in the game. This block is what those two additions need and nothing else:
   a focus ring, a transparent target, a dashed marker, one line of type and a three row list.

   NOTHING HERE SIZES THE PICTURE. The sparkline keeps LG-2's own 48px height and 100% width exactly;
   every coordinate the marker and the targets use is in the SVG's own 100 unit space and lives in the
   MARKUP, because no stylesheet declaration can carry a number in a viewBox's coordinate system. That
   is why there is no width, no height and no breakpoint in this block at all, and why the whole thing
   is correct at 360px and at 1920px without a media query: the type is in rem, the list is a grid of
   fractions, and the one pixel value is the focus ring's outline, which is a device affordance rather
   than a layout size and is deliberately not scaled.

   TOUCH ACTION IS DELIBERATELY NOT DECLARED. A sheet on a phone scrolls, and taking the vertical
   gesture away over a 48px band to make a scrub smoother would trade a thing every member does for a
   thing some members do. A tap still lands: it is not a scroll, so the pointer event fires either way.

   THE ROWS ARE THE SCORING LIST'S SHAPE ON PURPOSE (LG-2's .ff-lg-scoring-row, and the owner
   walk's addition beside it). The two lists sit one under the other and answer the same question about
   the same series from two sides, so they are read as one thing rather than as two designs; the play
   text is clamped to two lines by the idiom the Game Day pace sentence already uses, which is what
   keeps three rows three rows on a phone.

   Colour is never the only carrier. The marker is a DASHED line rather than a tinted one, the readout
   states the school and the figure in words, and the swing rows name the side that gained; nothing in
   the block depends on a hue to be read, and every value is a palette token, so both themes are
   correct by construction.

   EVERY SELECTOR IS .ff-lgw- ("live game win probability"), this slice's own prefix, and deliberately
   not LG-2's .ff-lg-, LG-5's .ff-lgd-, 45E's .ff-lgf-, 45F's .ff-lgs-, 45G's .ff-lgk-, 45I's
   .ff-lgr-, 54C's .ff-lgm-, 54D's .ff-lgc-, 54F's .ff-lgz-, 55E's .ff-lgl- or 55C's .ff-lgt-. No name
   here is a substring of another of them in either direction, so a guard that asks whether a rule
   mentions a class cannot be satisfied by the wrong rule. No rule here names a class from any other
   block, so this block can win no cascade it was not given.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after the blocks
   already there, which is the round wide append order resolution R14 fixes and which
   AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker has to stay the last
   block marker in the sheet.
   ============================================================================================= */

/* The interactive group inside the sparkline, which is the whole picture and is reachable with a
   keyboard. The ring is the theme's own ink, so it reads in both themes and over either school's
   colour, and it is the same ring 55C's scoring dots take. */
.ff-lgw-pin:focus-visible {
    outline: 2px solid var(--mud-palette-text-primary);
    outline-offset: 2px;
}

/* One reading's share of the x axis. Transparent rather than absent: a shape with no fill at all
   receives no pointer events over its interior, which would leave a target that only worked on its
   edge. The cursor says the picture answers a pointer, which is the only thing a mouse has to go on. */
.ff-lgw-hit {
    fill: transparent;
    cursor: pointer;
}

/* The pinned reading's marker. Dashed so it cannot be mistaken for a second series, and refused the
   pointer so it can never take a hit from the target it stands on: an SVG has no z-index and paint
   order alone decides that. */
.ff-lgw-mark {
    stroke: var(--mud-palette-text-primary);
    stroke-width: 1;
    stroke-dasharray: 2 2;
    pointer-events: none;
}

/* The readout, under the axis. ONE LINE, which is the breakpoint matrix's claim for this element at
   360px stated in the stylesheet rather than in prose: the string is short and bounded (a quarter, a
   clock, a school and a figure), and a school long enough to run out of room ends in an ellipsis
   rather than pushing the axis above it around. Tabular figures so stepping along the line with the
   arrow keys does not make the number jitter. */
.ff-lgw-read {
    font-size: .8rem;
    font-weight: 600;
    color: var(--mud-palette-text-primary);
    font-variant-numeric: tabular-nums;
    white-space: nowrap;
    overflow: hidden;
    text-overflow: ellipsis;
}

/* ---- the swings ---- */

.ff-lgw-swings { margin-top: 10px; }

/* The caption, in the scoring list's own voice: secondary, upper case and small, because it says what
   the list IS and the rows are what a member reads. */
.ff-lgw-swingcap {
    margin-bottom: 4px;
    font-size: .62rem;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-lgw-swinglist {
    list-style: none;
    margin: 0;
    padding: 0;
    display: flex;
    flex-direction: column;
    gap: 6px;
}

/* Two columns rather than the scoring list's three: a swing has a clock and a size and no score. */
.ff-lgw-swingrow {
    display: grid;
    grid-template-columns: auto 1fr;
    column-gap: 8px;
    align-items: baseline;
    font-size: .8rem;
}

.ff-lgw-swingrow .when {
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
}

.ff-lgw-swingrow .what { font-weight: 600; }

/* The play under the row it belongs to, clamped to two lines so three swings stay three rows on a
   phone. A row with no play simply has no such span, which is the payload's own honest absence. */
.ff-lgw-swingrow .play {
    grid-column: 1 / span 2;
    display: -webkit-box;
    -webkit-line-clamp: 2;
    line-clamp: 2;
    -webkit-box-orient: vertical;
    overflow: hidden;
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

.ff-lgw-swingbasis {
    margin-top: 6px;
    font-size: .68rem;
    color: var(--mud-palette-text-secondary);
}

/* ---- end 55F ---- */

/* =============================================================================================
   Phase 55 55G (2026-09-22) - the two plays a late arrival missed

   THE OWNER'S N-2. Opening a live game somebody else has been watching handed a member a trail that
   was simply already there, with nothing to say which part of it happened while the sheet was
   opening. The last two snaps now draw themselves onto that trail, one at a time, and the picture
   settles into the still field. This block is what that needs and nothing else: an ink token for the
   replayed snaps, two hiding tokens, and the small list a member who asked for less motion reads
   instead.

   NOTHING HERE SIZES OR MOVES THE PICTURE. Every coordinate the replayed snaps use is in the SVG's
   own 120 by 44 unit space and lives in the MARKUP, because no stylesheet declaration can carry a
   number in a viewBox's coordinate system, and the field's box is fixed by that viewBox. So the
   replay cannot change the field's height at 360px or at 1920px, which is the acceptance's "no layout
   shift between the replay and the settled field", and there is no width, no height and no breakpoint
   in this block at all.

   THE HIDING IS OPACITY AND NEVER DISPLAY, on the two tokens that hide a line. A shape removed from
   the tree would leave the group's own bounding box to be recomputed twice a second; a shape at zero
   opacity is laid out exactly where it will be drawn, so the reveal is the only thing that changes.

   THE ONE MEDIA QUERY DOES THE WHOLE OF THE REDUCED MOTION ACCEPTANCE, in three declarations that
   belong together. The group carrying the animation is not drawn at all, which is what "the animation
   is skipped" means for a member who asked for it to be; the composed path's held tail is released,
   so the field is its settled self from the first frame rather than a trail with two snaps missing;
   and the list of those two snaps is shown, which is what they read instead. The transition is named
   in it as well, so a future edit that moved the hiding cannot leave a motion behind.

   EVERY SELECTOR IS .ff-lgy- ("live game, the plays you missed"), this slice's own prefix, and
   deliberately not LG-2's .ff-lg-, LG-5's .ff-lgd-, 45E's .ff-lgf-, 45F's .ff-lgs-, 45G's .ff-lgk-,
   45I's .ff-lgr-, 54C's .ff-lgm-, 54D's .ff-lgc-, 54F's .ff-lgz-, 55E's .ff-lgl-, 55C's .ff-lgt- or
   55F's .ff-lgw-. No name here is a substring of another of them in either direction, so a guard that
   asks whether a rule mentions a class cannot be satisfied by the wrong rule. No rule here names a
   class from any other block, so this block can win no cascade it was not given: the hold token is a
   SECOND class on 45E's own segment line rather than a rule about it.

   Colour is never the only carrier. The replayed snaps are the theme's own ink rather than either
   school's colour, because which snaps a member missed is a fact about their arrival and not about a
   school, and every one of them is also named in words in the list below the picture.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after the blocks
   already there, which is the round wide append order resolution R14 fixes and which
   AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker has to stay the last
   block marker in the sheet.
   ============================================================================================= */

/* One replayed snap, drawn over the composed segment it stands in for. The theme's own ink, so it
   reads over either half of the field and in both themes, and the same round cap 45E's segments take
   so a replayed snap and a settled one are the same shape. */
.ff-lgy-seg {
    stroke: var(--mud-palette-text-primary);
    stroke-linecap: round;
    opacity: .95;
    transition: opacity 260ms ease-out;
}

/* A snap the run has not reached yet. */
.ff-lgy-wait { opacity: 0; }

/* The tail of the composed path the run is standing in for, which is a SECOND class on 45E's own
   segment rather than a rule about it: the picture opens on the trail as it was two snaps ago. */
.ff-lgy-hold { opacity: 0; }

/* The two snaps in words, which only a member who has asked for less motion reads. Hidden rather than
   absent, because the markup has to carry both halves: no interop call asks the browser what
   prefers-reduced-motion says, so the stylesheet is what picks. */
.ff-lgy-list { display: none; }

.ff-lgy-cap {
    margin-top: 6px;
    font-size: .62rem;
    letter-spacing: .04em;
    text-transform: uppercase;
    color: var(--mud-palette-text-secondary);
}

.ff-lgy-plays {
    list-style: none;
    margin: 0;
    padding: 0;
    display: flex;
    flex-direction: column;
    gap: 2px;
}

/* One snap's line. It wraps rather than truncating: a play description is a sentence, and a member
   reading these instead of watching them is reading for the words. */
.ff-lgy-play {
    font-size: .7rem;
    color: var(--mud-palette-text-secondary);
    overflow-wrap: anywhere;
}

@media (prefers-reduced-motion: reduce) {
    .ff-lgy-replay { display: none; }

    .ff-lgy-seg { transition: none; }

    .ff-lgy-hold { opacity: 1; }

    .ff-lgy-list { display: block; }
}

/* ---- end 55G ---- */

/* =============================================================================================
   PG-1 (owner walk, 2026-09-24) - "not played yet" survives a phone

   Before a game is played a drafted row's points are the 0.0 it carries from the pick, and the home
   card handed that zero to the forecast pair as an actual: "-23.0 below range" on every row, days
   before a kickoff. ForecastPair now takes the host's word that the game has not been played and
   prints the projection with a three word note, "not played yet", in place of a delta and a verdict.

   THE NOTE IS THE ONE .bd THE PHONE RULE MUST NOT HIDE, for the reason the no line reason is not
   hidden (57A, finding D4): below 600px 57A sends the narrow chip's muted spans to the title, and a
   phone has no hover, so a hidden note would leave a projection beside a placeholder glyph with
   nothing saying why there is no result. 57A's own rule exempts .ff-mr-noline by name and its guard
   pins that selector exactly, so this block re-shows the new note rather than editing that rule. The
   selector below carries the same four classes of weight as 57A's and sits later in the sheet, which
   is what makes it win; every token on the note stays 57A's own.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, which is where every
   slice appends and which AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker
   has to stay the last block marker in the sheet.
   ============================================================================================= */

@media (max-width: 599.98px) {
    .ff-mr-actual.compact .bd.ff-mr-notplayed { display: inline; }
}

/* ---- end PG-1 ---- */

/* =============================================================================================
   FR-1 (owner walk, 2026-09-24) - the Forecast report, less empty on a large screen

   Three asks from one walk of /forecast on a wide monitor: the Week view's two panels side by side,
   more to read on the Members view, and something on the Players view before anybody searches. The
   side by side layout itself is MudGrid's (xs 12, md 7 and 5 or 6 and 6), so nothing here sizes a
   panel or declares a breakpoint for one; below md the grid stacks the panels in the order they
   always had and a 360px phone reads the page it read before.

   What this block adds is two row shapes and their small parts:

   A MEMBER'S WEEK THAT OPENS. The week line is a real button (keyboard and screen reader for free),
   laid out on the ff-roster-row grid it already used, so the only rules here undo a button's own
   chrome and give the rows it opens a tint that says they belong to the line above them.

   A TWO LINE LIST ROW (.ff-fcr-pick), for the Players view's default list, its biggest beats and
   misses, and the "your league did hold" offer. The name and one figure share the first line; the
   second line is a wrapping flex row, so at 360px a season's figures wrap onto a third line rather
   than truncating a number, and on a wide column they sit on one line. The name ellipsises and the
   figure beside it never shrinks, which is the ff-roster-row rule for the same two cells.

   Colour is never the only carrier: the Beat and Miss tags are words, and the tint on opened rows is
   decoration over rows that are already indented under their own line.

   A NARROWER LEAGUE TABLE. The Members view's six column table sits in half the row from md up, so its
   cell padding is narrowed under its own wrapper; that is the one rule here that reaches into
   MudBlazor's markup, and the wrapper scopes it to this table alone.

   EVERY SELECTOR STARTS .ff-fcr- ("forecast report"), a prefix no other block uses; .ff-fc-top is the
   one neighbour and neither name contains the other. No rule here names a class from another block of
   this sheet.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after the blocks
   already there, which AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker
   has to stay the last block marker in the sheet.
   ============================================================================================= */

/* A member's week line, which is a button laid out on the ff-roster-row grid. Only the button's own
   chrome is undone here; the grid, the padding and the cells are ff-roster-row's. */
.ff-fcr-week {
    width: 100%;
    margin: 0;
    border: 0;
    border-bottom: 1px solid var(--mud-palette-lines-default);
    background: none;
    color: inherit;
    font: inherit;
    text-align: left;
    cursor: pointer;
}

.ff-fcr-week:hover:not(:disabled) { background: rgba(var(--mud-palette-primary-rgb), .06); }

.ff-fcr-week:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: -2px;
}

.ff-fcr-week:disabled { cursor: default; }

/* The chevron sits in the slot column, centred, so the week's name lines up with every other name. */
.ff-fcr-chev {
    display: inline-flex;
    justify-content: center;
    color: var(--mud-palette-text-secondary);
}

/* The rows a week opens: tinted so they read as that week's own, and ruled off from the next week. */
.ff-fcr-weekrows {
    background: rgba(var(--mud-palette-primary-rgb), .04);
    border-bottom: 1px solid var(--mud-palette-lines-default);
}

/* A school under a player's name, and a week under a beat's or miss's player: muted, on its own line
   inside the name cell, so a 360px name column that ellipsises the name never cuts the one word that
   tells two athletes of one name apart. The line inherits the cell's nowrap and ellipsis. */
.ff-fcr-note {
    display: block;
    overflow: hidden;
    text-overflow: ellipsis;
    color: var(--mud-palette-text-secondary);
    font-size: .74rem;
}

/* The Beat and Miss words, in the slot column where a position badge would sit. */
.ff-fcr-tag {
    font-size: .62rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-align: center;
    text-transform: uppercase;
    padding: 2px 0;
    border: 1px solid currentColor;
    border-radius: 6px;
}

.ff-fcr-tag.beat { color: var(--mud-palette-success); }
.ff-fcr-tag.miss { color: var(--mud-palette-error); }

/* The two line list row, which is the whole button. */
.ff-fcr-pick {
    display: grid;
    grid-template-columns: minmax(0, 1fr) auto;
    align-items: center;
    column-gap: 12px;
    row-gap: 2px;
    width: 100%;
    margin: 0;
    padding: 10px 14px;
    border: 0;
    border-bottom: 1px solid var(--mud-palette-lines-default);
    background: none;
    color: inherit;
    font: inherit;
    text-align: left;
    cursor: pointer;
}

.ff-fcr-pick:last-child { border-bottom: 0; }
.ff-fcr-pick:hover:not(:disabled) { background: rgba(var(--mud-palette-primary-rgb), .06); }

.ff-fcr-pick:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: -2px;
}

.ff-fcr-pick:disabled { cursor: default; }

.ff-fcr-pick .nm {
    min-width: 0;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
    font-size: .89rem;
    font-weight: 600;
}

.ff-fcr-pick .n {
    justify-self: end;
    white-space: nowrap;
    font-size: .8rem;
    font-variant-numeric: tabular-nums;
    color: var(--mud-palette-text-secondary);
}

/* The second line spans both columns and wraps, so no figure on it is ever cut. */
.ff-fcr-pick .sub {
    grid-column: 1 / -1;
    display: flex;
    flex-wrap: wrap;
    column-gap: 12px;
    row-gap: 2px;
    min-width: 0;
    font-size: .76rem;
    color: var(--mud-palette-text-secondary);
}

.ff-fcr-pick .sub .meta { overflow-wrap: anywhere; }
.ff-fcr-pick .sub .fig { font-variant-numeric: tabular-nums; white-space: nowrap; }

/* A season line: the word "Season" and a sentence of figures. On the roster grid the figures are the
   auto column and the name the 1fr one, so a sentence that long took the whole row and left "Season"
   zero pixels wide, at 360px and in half a laptop row alike. Here the label keeps its own width and the
   sentence takes the rest and wraps, right aligned like every other figure column. */
.ff-roster-row.ff-fcr-season { grid-template-columns: 52px auto minmax(0, 1fr); }
.ff-roster-row.ff-fcr-season .pt { text-align: right; }

/* The league table beside a member's weeks. Half of a laptop's content width (a 1280 screen with the
   drawer open leaves about 500px) cannot hold six dense columns at MudBlazor's 16 and 24px cell padding,
   so the table grew a scrollbar of its own. Eight a side is enough for every column to fit and still
   separates them. Scoped to this one wrapper, so no other table in the app is touched, and the phone's
   card list (ResponsiveList below sm) carries no .mud-table-cell at all. */
.ff-fcr-table .mud-table-dense .mud-table-row .mud-table-cell {
    padding: 6px 8px;
    padding-inline: 8px;
}

/* A search hit: the name, then the school that tells two athletes of one name apart. */
.ff-fcr-hit {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    column-gap: 8px;
    min-width: 0;
}

.ff-fcr-hit .nm { font-weight: 600; }

.ff-fcr-hit .sch {
    font-size: .8rem;
    color: var(--mud-palette-text-secondary);
}

/* ---- end FR-1 ---- */

/* =============================================================================================
   PS-1 (owner-approved, 2026-09-24) - the week-versus-average strip on a week not played yet

   The player page's strip printed "This week 0.00" and a "vs avg" delta against that zero while the
   row's game had not been played. The cell now prints the placeholder glyph with the pair's own "not
   played yet" under it, so the glyph says why it is there on a phone that has no hover. This is that
   one line of small print: muted, on its own line under the value, and wrapping inside the cell's own
   92px minimum at 360px rather than widening it. Nothing else in PS-1 needs a rule (the Scoreboard's
   notes ride the board's existing caption line and notice).

   EVERY SELECTOR STARTS .ff-unplayed-, a prefix no other block uses.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, which AppCssIntegrityTests
   pins: the UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

.ff-unplayed-note {
    display: block;
    margin-top: 2px;
    color: var(--mud-palette-text-secondary);
    font-size: .72rem;
    line-height: 1.3;
}

/* ---- end PS-1 ---- */

/* =============================================================================================
   DM-0 (Phase 60 60C, 2026-10-22) - the draft motion tokens and the reduced-motion gaps

   Two small things, both live, neither behind a key.

   THE TOKENS. The round's motion vocabulary, declared once on :root so the draft room (Phase 60's
   later DM blocks), the bell (Phase 61) and the live game surfaces (Phase 63) speak one motion
   language instead of each copying a number from a neighbouring block. They are INERT until a
   later block reads them with var(): a custom property does nothing on its own, so this block makes
   no visible change for anybody. Two of them are not new, they name idioms this sheet already ships:

     --ff-ease-enter  the house reveal curve (.ff-js-motion .ff-reveal, the Wave 2 motion block)
     --ff-dur-emph    the 1.6s emphasis cycle (ff-draft-dock-pulse, ff-lgc-flash)

   The rest are the phase's own (plan 60C and section 9.2): a 320ms row entrance, a 200ms row open
   inside the fixed-height list, a 240ms banner handoff, a 1.1s fresh tint (shorter than the 1.2s
   pick cadence, so one pick's tint has finished before the next pick lands), a 160ms exit, a 300ms
   pop and an 80ms stagger between rows that arrive in the same render.

   EACH TOKEN IS DECLARED HERE AND NOWHERE ELSE. A later block consumes them and redeclares none,
   because a redeclaration further down the sheet silently wins the cascade for every surface at
   once. DraftMotionTokensStylesheetTests fails a second declaration anywhere in the client's
   stylesheets. Renaming one is a cross-phase change: Phase 61 and Phase 63 both name them.

   THE REDUCED-MOTION GAPS. Three infinite pulses in the draft family had no prefers-reduced-motion
   arm: the room tab's turn dot (.ff-segtab-dot), the app bar pill's and the nav drawer's your-turn
   dot (.ff-livedraft.mine .ff-livedraft-dot), and the LIVE badge's dot that My Team renders in the
   room (.ff-live-badge .dot, the Game Day layer's badge). The arm stops the motion and nothing else.
   Each base rule paints its state colour as a background and declares no opacity, so with the
   animation gone the dot sits still at full opacity in its own colour and the meaning (it is your
   turn, it is live) survives. Each override repeats its base rule's selector exactly, so the two tie
   on specificity and this later rule wins on source order, with no !important. Ungated: it is an
   accessibility fix.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, which
   AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker has to stay the last
   block marker in the sheet.
   ============================================================================================= */

:root {
    --ff-ease-enter: cubic-bezier(.22, .61, .36, 1);
    --ff-ease-exit: cubic-bezier(.4, 0, 1, 1);
    --ff-ease-pop: cubic-bezier(.34, 1.56, .64, 1);
    --ff-dur-row: 320ms;
    --ff-dur-open: 200ms;
    --ff-dur-handoff: 240ms;
    --ff-dur-fresh: 1100ms;
    --ff-dur-exit: 160ms;
    --ff-dur-pop: 300ms;
    --ff-dur-emph: 1.6s;
    --ff-dm-stagger: 80ms;
}

@media (prefers-reduced-motion: reduce) {
    .ff-segtab-dot,
    .ff-livedraft.mine .ff-livedraft-dot,
    .ff-live-badge .dot {
        animation: none;
    }
}

/* ---- end DM-0 ---- */

/* =============================================================================================
   NB-1 (Phase 61, 61C) - the notification bell menu's width clamp

   The bell's dropdown carried an inline min-width:280px; max-width:360px, inside a menu anchored
   bottom-right of a bell that sits left of the user button. On a 360px phone a 360px maximum is the
   whole viewport, so nothing kept the popover from pushing the page sideways. The clamp keeps the
   menu 16px inside each edge on a narrow phone (at most 328px at 360px, at least 280px down to a
   312px viewport) and is IDENTICAL to the old inline pair above a 392px viewport, where
   100vw - 32px first reaches 360px.

   One class and nothing else: the bell's motion (NB-2, 61G) is a separate block under its own key.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, which
   AppCssIntegrityTests pins: the UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

.ff-bell-menu {
    min-width: min(280px, calc(100vw - 32px));
    max-width: min(360px, calc(100vw - 32px));
}

/* ---- end NB-1 ---- */

/* =============================================================================================
   DM-1 (Phase 60 60E, 2026-10-22) - the draft room draws picks one at a time

   Behind Features:DraftMotionEnabled, and inert without it: every selector below names a class that
   only the room's pick presenter puts on the page (ff-dm-enter, ff-dm-group, ff-dm-handoff,
   ff-dm-held, ff-dm-sr), and with the key dark the room constructs no presenter, so none of them is
   ever emitted and nothing here can match. Every duration and curve is a DM-0 token read with var();
   this block declares none of them (DraftMotionTokensStylesheetTests fails a second declaration).

   A PACED ARRIVAL (.ff-dm-enter on a Recent picks row, plan 9.2 and D11). Three animations on one row,
   in this order: the row OPENS its own height over --ff-dur-open, inside the list's fixed BH-2 height,
   so the rows under it ease down instead of snapping a whole row at once; then it fades and rises over
   --ff-dur-row, starting one --ff-dm-stagger after the open begins; and it carries the fresh tint for
   --ff-dur-fresh (1.1s), which ends before the next pick's 1.2s beat, so no two tints are ever on
   screen together. The open animates max-height up to the list's own row constant (--ff-recent-row,
   BH-2) and the row clips while it opens; every fill mode is backwards, so once the animations end the
   row holds no max-height of its own and is exactly the row BH-2 measured. Only opacity, transform and
   background-color move otherwise (plan 9.1).

   A FAST-FORWARD (the member's turn, or the member touching a decision control) lands every held row
   in one render: each row's --ff-dm-i (set by the strip) delays its three animations by that many
   --ff-dm-stagger steps, so six rows finish inside half a second. A GROUP (.ff-dm-group: picks older
   than the newest six, or older than the newest three after a hidden tab) gets the tint and no
   movement at all.

   THE BANNER (plan 3.5, D6, D7). .ff-dm-handoff is on the headline element the room keys per beat, so
   each "DJ picked John Smith." and the hand back to "Bob is on the clock!" is a new element that fades
   and rises once over --ff-dur-handoff. .ff-dm-held keeps an element's box and hides its ink: the
   up-next line during a narration, so the cell's height never changes and the board under it never
   moves at either end of a burst. The pick clock and the lock countdown are never held.

   .ff-dm-sr is the list's polite status line, one sentence per arrival, visually hidden and still
   read by a screen reader. Its 1px box is the standard visually hidden pattern, not a layout width.

   REDUCED MOTION (plan 9.2, Q6): movement goes, information stays. The rows still arrive one at a
   time on their beats (the cadence is order, and order is information), with no open, no rise and no
   stagger, and the tint is kept, because a colour change is not movement. The banner swaps instantly.

   360px: the list keeps its three-row phone height (BH-2) and an arriving row opens inside it, so the
   list never grows; the held up-next line keeps the on-clock cell's height. Nothing here declares a
   width or a media query of its own beyond the reduced-motion arm.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after DM-0 and NB-1,
   which AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker has to stay the
   last block marker in the sheet.
   ============================================================================================= */

.ff-room-recent-row.ff-dm-enter {
    overflow: hidden;
    animation:
        ff-dm-row-open var(--ff-dur-open) var(--ff-ease-enter) calc(var(--ff-dm-i, 0) * var(--ff-dm-stagger)) backwards,
        ff-dm-row-rise var(--ff-dur-row) var(--ff-ease-enter) calc((var(--ff-dm-i, 0) + 1) * var(--ff-dm-stagger)) backwards,
        ff-dm-row-fresh var(--ff-dur-fresh) var(--ff-ease-enter) calc(var(--ff-dm-i, 0) * var(--ff-dm-stagger)) backwards;
}

.ff-room-recent-row.ff-dm-group {
    animation: ff-dm-row-fresh var(--ff-dur-fresh) var(--ff-ease-enter) backwards;
}

.ff-dm-handoff {
    animation: ff-dm-handoff var(--ff-dur-handoff) var(--ff-ease-enter) backwards;
}

.ff-dm-held {
    visibility: hidden;
}

.ff-dm-sr {
    position: absolute;
    width: 1px;
    height: 1px;
    margin: -1px;
    padding: 0;
    border: 0;
    overflow: hidden;
    clip-path: inset(50%);
    white-space: nowrap;
}

@keyframes ff-dm-row-open {
    from {
        max-height: 0;
        padding-top: 0;
        padding-bottom: 0;
    }
    to {
        max-height: var(--ff-recent-row, 2rem);
    }
}

@keyframes ff-dm-row-rise {
    from {
        opacity: 0;
        transform: translateY(6px);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-dm-row-fresh {
    from {
        background-color: rgba(var(--mud-palette-primary-rgb), .18);
    }
    to {
        background-color: transparent;
    }
}

@keyframes ff-dm-handoff {
    from {
        opacity: 0;
        transform: translateY(4px);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-room-recent-row.ff-dm-enter {
        animation: ff-dm-row-fresh var(--ff-dur-fresh) var(--ff-ease-enter) backwards;
    }

    .ff-dm-handoff {
        animation: none;
    }
}

/* ---- end DM-1 ---- */

/* =============================================================================================
   DM-2 (Phase 60 60F, 2026-10-22) - the your-turn moment

   Behind Features:DraftMotionEnabled, and inert without it: every class below (ff-dm-turn, ff-dm-sel,
   ff-dm-dock) is emitted only by the room and the dock when the key is on, so with the key dark
   nothing here can match. Every duration and curve is a DM-0 token read with var(); this block
   declares none of them (DraftMotionTokensStylesheetTests fails a second declaration).

   THE RING (.ff-room-onclock.ff-dm-turn). The on-clock cell takes the class on the render that first
   shows this member a turn instance (keyed by the snapshot's PickStartedUtc in a per-tab memory, so a
   re-render or a remount inside the same turn never replays it). Two cycles of --ff-dur-emph (1.6s),
   3.2s in all, of a success-coloured ring that grows out from the cell and fades. It is a box-shadow,
   so the cell takes no room it did not already take at any width, 360px included; the radius only
   rounds the shadow's corners. The animation keeps no fill, so once it ends the cell is exactly the
   cell it was.

   THE SELECT CONTROLS (.ff-dm-sel). The per-row "select this as your pick" controls are new elements
   on the turn's render. The first eight (plan 9.4) pop in one after another, 20ms apart: a quarter of
   DM-0's 80ms stagger token, times the row's own --ff-dm-i, which the room sets and this block only
   reads. Opacity and transform only.

   THE DOCK (.ff-draft-dock.ff-dm-dock). Off /draft, the TURN-3 dock's link grows from the waiting pill
   into the "Your pick" bar over --ff-dur-handoff (240ms): its minimum height, its corner radius and its
   colours transition instead of snapping. The bottom clearance (--ff-dock-clearance) is already sized
   for the taller state, so nothing else on the page moves. The dock renders nothing on a /draft route,
   so this exists only where the dock does.

   REDUCED MOTION (plan 9.2): movement goes, information stays. The ring becomes a STATIC 2px success
   ring held for the same 3.2s (a constant keyframe, so nothing moves, and it still goes away on its
   own), the select controls simply appear, and the dock swaps state instantly. The haptic follows its
   own device switch and never this query.

   PLACEMENT (round order, orchestrator 2026-10-22): after DM-1 (and after Phase 61's NB-2 when that
   block is present), and BEFORE the first Phase 63 block, because the round keeps every Phase 60 and
   61 block ahead of Phase 63's and only Phase 63 blocks between 63H and UX-1. UX-1's end marker stays
   the last block marker in the sheet (AppCssIntegrityTests, PickInFlightRoomTests).
   ============================================================================================= */

.ff-room-onclock.ff-dm-turn {
    border-radius: var(--mud-default-borderradius, 4px);
    animation: ff-dm-turn-ring var(--ff-dur-emph) var(--ff-ease-enter) 2;
}

.ff-dm-sel {
    animation: ff-dm-sel-pop var(--ff-dur-pop) var(--ff-ease-pop) calc(var(--ff-dm-i, 0) * var(--ff-dm-stagger) / 4) backwards;
}

.ff-draft-dock.ff-dm-dock .ff-draft-dock-link {
    transition:
        min-height var(--ff-dur-handoff) var(--ff-ease-enter),
        border-radius var(--ff-dur-handoff) var(--ff-ease-enter),
        background-color var(--ff-dur-handoff) var(--ff-ease-enter),
        border-color var(--ff-dur-handoff) var(--ff-ease-enter),
        color var(--ff-dur-handoff) var(--ff-ease-enter);
}

@keyframes ff-dm-turn-ring {
    0% {
        box-shadow: 0 0 0 0 rgba(var(--mud-palette-success-rgb), .55);
    }
    70% {
        box-shadow: 0 0 0 10px rgba(var(--mud-palette-success-rgb), 0);
    }
    100% {
        box-shadow: 0 0 0 0 rgba(var(--mud-palette-success-rgb), 0);
    }
}

@keyframes ff-dm-sel-pop {
    from {
        opacity: 0;
        transform: scale(.6);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-dm-turn-still {
    from {
        box-shadow: 0 0 0 2px var(--mud-palette-success);
    }
    to {
        box-shadow: 0 0 0 2px var(--mud-palette-success);
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-room-onclock.ff-dm-turn {
        animation: ff-dm-turn-still calc(var(--ff-dur-emph) * 2) var(--ff-ease-enter);
    }

    .ff-dm-sel {
        animation: none;
    }

    .ff-draft-dock.ff-dm-dock .ff-draft-dock-link {
        transition: none;
    }
}

/* ---- end DM-2 ---- */

/* =============================================================================================
   DM-3 (Phase 60 60G, 2026-10-22) - one confirmation for your own pick, and the roster slot that fills

   Behind Features:DraftMotionEnabled, and inert without it: every rule below is qualified by a class
   that only the room and its roster strip emit with the key on (ff-dm-done on the pick banner,
   ff-dm-press on the green Draft button, ff-dm-fill on a roster chip, ff-dm-sweep on the strip), so
   with the key dark nothing here can match. Every duration and curve is a DM-0 token read with var();
   this block declares none of them (DraftMotionTokensStylesheetTests fails a second declaration).

   "DRAFTED." (.ff-pick-inflight.ff-dm-done, plan 11 Q11). The UX-1 banner that acknowledged the tap
   becomes the confirmation: "Drafted. John Smith is on your team." with a check icon, in the success
   tone, for 1.6s on the room's clock, then it collapses. The room raises neither the top alert nor the
   success snackbar for it; a refusal and a lost response keep both, untouched. The state is the same
   element the waiting banner was, so the success tint settles in over --ff-dur-handoff and the check
   pops once over --ff-dur-pop on the pop curve. Two classes qualify each rule, which outranks UX-1's
   single-class state rules below without !important and without depending on source order.

   THE PRESS (.ff-dm-press:active). The Draft button answers the finger in 100ms (half DM-0's 200ms
   --ff-dur-open): it eases down to .96 while pressed. The transition is declared on the pressed state
   only, so MudBlazor's own colour transitions on the button are left alone the rest of the time.

   THE FILL (.ff-teamstrip-slot.ff-dm-fill). The roster chip a pick filled is the same element it was
   while empty (the strip's slots are positional), so the class starts one --ff-dur-row fill: a
   success wash and a small grow from .92 that settle into the chip's own colours. THE SWEEP
   (.ff-teamstrip.ff-dm-sweep): when that pick was the member's last slot, one highlight passes across
   the five chips, each one --ff-dm-stagger after the last (the strip sets --ff-dm-i, this block only
   reads it), starting once the fill has played. Both classes stay on until the roster next changes, so
   neither is cut short by an unrelated render and neither replays.

   REDUCED MOTION (plan 9.2): movement goes, information stays. No press scale, no check pop, no fill
   and no sweep: the chip is simply filled. The "Drafted." state still shows and still expires, because
   that is the room's clock and not an animation, and its success tint still settles, because a colour
   change is not movement (DM-1 keeps its fresh tint for the same reason).

   360px (plan 9.4): the confirmation is the UX-1 banner's own sentence element, so it wraps exactly as
   UX-1's sentences do and takes no width of its own; the fill and the sweep stay inside each chip
   (transform, background and box-shadow only). Nothing here declares a width or a media query beyond
   the reduced-motion arm.

   PLACEMENT (round order, orchestrator 2026-10-22): after DM-2, before Phase 61's NB-2 and before the
   first Phase 63 block, because the round keeps the Phase 60 chain together ahead of Phase 61's and
   Phase 63's blocks. UX-1's end marker stays the last block marker in the sheet (AppCssIntegrityTests,
   PickInFlightRoomTests).
   ============================================================================================= */

.ff-pick-inflight.ff-dm-done {
    border-left-color: var(--mud-palette-success);
    background: rgba(var(--mud-palette-success-rgb), .12);
    animation: ff-dm-done-in var(--ff-dur-handoff) var(--ff-ease-enter);
}

.ff-pick-inflight.ff-dm-done .mud-icon-root {
    color: var(--mud-palette-success);
    animation: ff-dm-done-check var(--ff-dur-pop) var(--ff-ease-pop) backwards;
}

.ff-dm-press:active {
    transform: scale(.96);
    transition: transform calc(var(--ff-dur-open) / 2) var(--ff-ease-enter);
}

.ff-teamstrip-slot.ff-dm-fill {
    animation: ff-dm-fill var(--ff-dur-row) var(--ff-ease-enter) backwards;
}

.ff-teamstrip.ff-dm-sweep .ff-teamstrip-slot {
    animation: ff-dm-sweep var(--ff-dur-row) var(--ff-ease-enter) calc(var(--ff-dur-row) + var(--ff-dm-i, 0) * var(--ff-dm-stagger));
}

.ff-teamstrip.ff-dm-sweep .ff-teamstrip-slot.ff-dm-fill {
    animation:
        ff-dm-fill var(--ff-dur-row) var(--ff-ease-enter) backwards,
        ff-dm-sweep var(--ff-dur-row) var(--ff-ease-enter) calc(var(--ff-dur-row) + var(--ff-dm-i, 0) * var(--ff-dm-stagger));
}

@keyframes ff-dm-done-in {
    from {
        background-color: rgba(var(--mud-palette-success-rgb), .28);
    }
}

@keyframes ff-dm-done-check {
    from {
        opacity: 0;
        transform: scale(.6);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-dm-fill {
    from {
        transform: scale(.92);
        background-color: rgba(var(--mud-palette-success-rgb), .28);
        box-shadow: 0 0 0 2px rgba(var(--mud-palette-success-rgb), .45);
    }
}

@keyframes ff-dm-sweep {
    50% {
        background-color: rgba(var(--mud-palette-success-rgb), .22);
        box-shadow: 0 0 0 2px rgba(var(--mud-palette-success-rgb), .35);
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-pick-inflight.ff-dm-done .mud-icon-root {
        animation: none;
    }

    .ff-dm-press:active {
        transform: none;
        transition: none;
    }

    .ff-teamstrip-slot.ff-dm-fill {
        animation: none;
    }

    .ff-teamstrip.ff-dm-sweep .ff-teamstrip-slot {
        animation: none;
    }

    .ff-teamstrip.ff-dm-sweep .ff-teamstrip-slot.ff-dm-fill {
        animation: none;
    }
}

/* ---- end DM-3 ---- */

/* =============================================================================================
   DM-4 (Phase 60 60H, 2026-10-22) - the draft ends on the pick that ended it

   Behind Features:DraftMotionEnabled, and inert without it: every rule below is qualified by a class
   that only the room emits with the key on, and only after a finish THIS mount watched (ff-dm-finishing
   on the on-clock cell while the last picks are drawn, ff-dm-finish on the Complete alert, the
   ff-dm-recap-host wrapper with is-observed around the recap panel, ff-dm-grade-in on the grade letter
   once the card lands). With the key dark, or on a mount into a finished draft, nothing here can match.
   Every duration and curve is a DM-0 token read with var(); this block declares none of them
   (DraftMotionTokensStylesheetTests fails a second declaration).

   THE FINISHING CELL (.ff-room-onclock.ff-dm-finishing). While the presenter drains and through the last
   pick's two-beat hold, the room keeps the on-clock cell on screen in its narrating arm over the
   finished snapshot. Nobody is on the clock, so the banner's avatar has nobody to picture: its box is
   kept (the cell does not change shape) and its ink is hidden, DM-1's .ff-dm-held idiom. Not motion.

   THE CELEBRATION (.mud-alert.ff-dm-finish). The Complete alert takes the class on the render it first
   appears in, after the hold: the trophy pops once (500ms, DM-0's --ff-dur-pop plus --ff-dur-open, on
   the pop curve, a transform from small to its own size) and the headline rises once over
   --ff-dur-handoff. The copy is unchanged. Closed (locked with slots unfilled) gets the hand-off and
   none of this.

   THE RECAP CARD (.ff-dm-recap-host.is-observed). After a celebrated finish the room wraps the recap
   panel, which is Phase 62's and is not edited here. The landed card (.ff-recap-panel without .pending)
   fades and rises once over 360ms (one and a half --ff-dur-handoff) when it replaces the pending line;
   the pending line itself never moves. Through Phase 62's 62C hook the room hands the letter
   ff-dm-grade-in once the card has landed, and the letter settles in on the pop curve as the card
   finishes arriving.

   REDUCED MOTION (plan 9.2): no pop, no rise, no card entrance and no letter settle. The alert, the
   headline, the card and the letter all appear, and the finishing cell's hold still runs, because the
   order of the story is information and the room's clock is not an animation.

   360px (plan 9.4): the pop, the rise and the entrances are transforms and opacity only, so nothing
   changes layout; the alert's buttons wrap exactly as they always did. Nothing here declares a width or
   a media query beyond the reduced-motion arm.

   PLACEMENT (round order, orchestrator 2026-10-22): after DM-3, before Phase 61's NB-2 and before the
   first Phase 63 block, because the round keeps the Phase 60 chain together ahead of Phase 61's and
   Phase 63's blocks. UX-1's end marker stays the last block marker in the sheet (AppCssIntegrityTests,
   PickInFlightRoomTests).
   ============================================================================================= */

.ff-room-onclock.ff-dm-finishing .mud-avatar {
    visibility: hidden;
}

.mud-alert.ff-dm-finish .mud-alert-icon {
    animation: ff-dm-finish-pop calc(var(--ff-dur-pop) + var(--ff-dur-open)) var(--ff-ease-pop) backwards;
}

.mud-alert.ff-dm-finish .mud-typography-h6 {
    animation: ff-dm-finish-rise var(--ff-dur-handoff) var(--ff-ease-enter) backwards;
}

.ff-dm-recap-host.is-observed .ff-recap-panel:not(.pending) {
    animation: ff-dm-recap-in calc(var(--ff-dur-handoff) * 1.5) var(--ff-ease-enter) backwards;
}

.ff-dm-recap-host.is-observed .ff-recap-letter.ff-dm-grade-in {
    animation: ff-dm-grade-in var(--ff-dur-pop) var(--ff-ease-pop) var(--ff-dur-handoff) backwards;
}

@keyframes ff-dm-finish-pop {
    from {
        opacity: 0;
        transform: scale(.4);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-dm-finish-rise {
    from {
        opacity: 0;
        transform: translateY(6px);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-dm-recap-in {
    from {
        opacity: 0;
        transform: translateY(8px);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-dm-grade-in {
    from {
        transform: scale(.7);
    }
    to {
        transform: none;
    }
}

@media (prefers-reduced-motion: reduce) {
    .mud-alert.ff-dm-finish .mud-alert-icon {
        animation: none;
    }

    .mud-alert.ff-dm-finish .mud-typography-h6 {
        animation: none;
    }

    .ff-dm-recap-host.is-observed .ff-recap-panel:not(.pending) {
        animation: none;
    }

    .ff-dm-recap-host.is-observed .ff-recap-letter.ff-dm-grade-in {
        animation: none;
    }
}

/* ---- end DM-4 ---- */

/* =============================================================================================
   DM-7 (Phase 60 60J, 2026-10-22) - the small things

   Behind Features:DraftMotionEnabled, and inert without it: every rule below is qualified by a class
   that only a 60J surface emits with the key on (the freshness leaf's ff-dm-fresh family and its
   ff-dm-blink, the ff-dm-backup chip, ff-dm-open on the stale strip, ff-dm-roll on a rolled distance).
   With the key dark the room, the Board, the turn companion and the dock render their shipped markup and
   nothing here can match. Every duration and curve is a DM-0 token read with var(); this block declares
   none of them (DraftMotionTokensStylesheetTests fails a second declaration).

   THE FRESHNESS LEAF (.ff-dm-fresh). The status head's word: "Live" with a small success-coloured dot,
   "Updated 40s ago" past two poll intervals, "Back up to date." once after a stale stretch. Unlike the
   shipped caption (.ff-draft-updated, hidden below 400px) it stays visible on a phone: it never wraps,
   its longest copy is sixteen characters at the caption's size, and it fits beside the refresh button in
   the status head's one row at 360px. Every size is in em or rem, never a pixel width.

   ONE BLINK PER UPDATE (.ff-dm-fresh-live.ff-dm-blink). The leaf keys the word by the update's stamp, so
   each update is a new element carrying the class from its creation: the dot dips and comes back once
   over --ff-dur-row. Opacity only. The stamp the leaf first saw carries no class, so a mount never blinks.

   BACK UP (.ff-dm-backup). A tinted chip that settles in over --ff-dur-open (opacity and a slight scale)
   for the 1.5 s it is on screen. It is a role="status" line, so a screen reader hears it once.

   THE STALE STRIP OPENS (.ff-draft-stale.ff-dm-open). DR-0's strip, which the room and the Board show
   after three failed reads, unfolds from its top edge over --ff-dur-open (opacity and a vertical scale)
   when it appears in front of a member who was watching the board live. Its box is the shipped one.

   A ROLLED DISTANCE (.ff-dm-roll). "You pick in N picks" and the dock's "N picks away" key their number by
   its value, so a new distance is a new element that drops into place over --ff-dur-open (opacity and a
   short translate). The first distance a surface draws carries no class. inline-block is what lets an
   inline number take a transform; it changes no line box.

   REDUCED MOTION (plan 9.2): no blink, no roll, no open, no settle. The words carry every state ("Live",
   "Updated 40s ago", "Back up to date.", the stale sentence), and the chip and the strip simply appear.

   Only opacity and transform move; nothing here transitions. No media query beyond the reduced-motion arm.

   PLACEMENT (round order, orchestrator 2026-10-22): after DM-4, before Phase 61's NB-2 and before the
   first Phase 63 block, so the Phase 60 chain stays together. UX-1's end marker stays the last block
   marker in the sheet (AppCssIntegrityTests, PickInFlightRoomTests).
   ============================================================================================= */

.ff-dm-fresh {
    display: inline-flex;
    align-items: center;
    margin-right: .25rem;
    font-size: .72rem;
    line-height: 1.2;
    white-space: nowrap;
    color: var(--mud-palette-text-secondary);
}

.ff-dm-fresh .ff-dm-fresh-live {
    display: inline-flex;
    align-items: center;
    gap: .3em;
}

.ff-dm-fresh .ff-dm-fresh-dot {
    display: inline-block;
    width: .55em;
    height: .55em;
    border-radius: 50%;
    background-color: var(--mud-palette-success);
}

.ff-dm-fresh-live.ff-dm-blink .ff-dm-fresh-dot {
    animation: ff-dm-fresh-blink var(--ff-dur-row) var(--ff-ease-enter);
}

.ff-dm-fresh .ff-dm-backup {
    padding: .1em .5em;
    border-radius: 1em;
    background-color: rgba(var(--mud-palette-success-rgb), .16);
    color: var(--mud-palette-success);
    animation: ff-dm-backup-in var(--ff-dur-open) var(--ff-ease-enter) backwards;
}

.ff-draft-stale.ff-dm-open {
    transform-origin: top center;
    animation: ff-dm-stale-open var(--ff-dur-open) var(--ff-ease-enter) backwards;
}

.ff-dm-roll {
    display: inline-block;
    animation: ff-dm-roll var(--ff-dur-open) var(--ff-ease-enter) backwards;
}

@keyframes ff-dm-fresh-blink {
    0% {
        opacity: 1;
    }
    50% {
        opacity: .2;
    }
    100% {
        opacity: 1;
    }
}

@keyframes ff-dm-backup-in {
    from {
        opacity: 0;
        transform: scale(.9);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-dm-stale-open {
    from {
        opacity: 0;
        transform: scaleY(.6);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-dm-roll {
    from {
        opacity: 0;
        transform: translateY(-.6em);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-dm-fresh-live.ff-dm-blink .ff-dm-fresh-dot {
        animation: none;
    }

    .ff-dm-fresh .ff-dm-backup {
        animation: none;
    }

    .ff-draft-stale.ff-dm-open {
        animation: none;
    }

    .ff-dm-roll {
        animation: none;
    }
}

/* ---- end DM-7 ---- */

/* =============================================================================================
   NB-2 (Phase 61, 61G) - the bell feels an arrival

   Behind Features:BellMotionEnabled, and inert without it: every selector below names a class that
   only the bell puts on the page under that key (ff-bell-bump-a/-b on the badge, ff-bell-swing-a/-b
   on the icon button, ff-bell-unread and ff-bell-row-in on menu rows, ff-bell-pill for the note), so
   with the key dark nothing here can match. The menu's own width clamp is NB-1's and is not touched.

   Plan 9.1, one rule per moment. Only opacity, transform, background-color and box-shadow move;
   nothing runs longer than 2 x 1.6s and nothing repeats.

     Badge pop       300ms, the pop curve, scale 1 to 1.25 to 1, on an increase only. Two names (a,
                     b) with identical frames, because the bell alternates them: a class that stays
                     on an element never replays, and a changed animation name always restarts.
     Bell swing      700ms ease-in-out, two damped swings of up to 12 degrees about the glyph's top
                     centre. Only the glyph turns, inside the 48px button, so the badge and the
                     button's box never move. Alternates a and b for the same reason.
     Row entrance    320ms, the house enter curve, a 6px drop and a fade, plus the 1.1s fresh tint,
                     on a row new since the list last rendered. The row is keyed, so a re-render never
                     re-creates it and never replays this.
     The note        240ms, the enter curve, a 4px rise and a fade.
     Unread fade     1.1s ease-out, the unread tint fading in as the menu opens. Only a from frame,
                     so it lands on the row's own inline tint whatever the theme makes it.

   Every duration and curve is a DM-0 token read with var() and a literal fallback equal to the
   token's own value, so a token rename leaves the bell timed exactly as it is now. This block
   declares no token (DraftMotionTokensStylesheetTests fails a second declaration) and no ff-dm-
   selector (Phase 60's prefix).

   REDUCED MOTION (plan 9.1): movement goes, information stays. The badge does not scale; it wears a
   static 2px ring for 1.6s instead, so the rise is still marked. The swing goes entirely (the count
   changing carries it). A new row appears in place and keeps its fresh tint, because a colour fade is
   not movement. The note appears with no movement. The unread fade is kept, restated in the arm so
   the contract is visible here rather than implied.

   360px (plan 9.3): the pop and the swing stay inside the 48px button box; the note is one line and
   the menu's full width, inside NB-1's clamp. Nothing here declares a media query beyond the arm.

   Placement: in the tail before the UX-1 banner, after DM-0, NB-1, DM-1 and DM-2, and BEFORE Phase
   63's blocks. The round's tail is ordered earlier chain first (Orchestration Playbook stage 4: 60,
   61, 62, 63), and Phase 63's own guard (LiveMotionFieldStylesheetTests) pins 63H as the first block
   after every Phase 60 and 61 block. AppCssIntegrityTests pins the rest: the UX-1 end marker stays
   the last block marker in the sheet. BellMotionStylesheetTests holds the rest of this contract.
   ============================================================================================= */

.ff-bell-bump-a {
    animation: ff-bell-bump-a var(--ff-dur-pop, 300ms) var(--ff-ease-pop, cubic-bezier(.34, 1.56, .64, 1));
}

.ff-bell-bump-b {
    animation: ff-bell-bump-b var(--ff-dur-pop, 300ms) var(--ff-ease-pop, cubic-bezier(.34, 1.56, .64, 1));
}

.ff-bell-swing-a .mud-icon-root {
    transform-origin: 50% 0;
    animation: ff-bell-swing-a 700ms ease-in-out;
}

.ff-bell-swing-b .mud-icon-root {
    transform-origin: 50% 0;
    animation: ff-bell-swing-b 700ms ease-in-out;
}

.ff-bell-unread {
    animation: ff-bell-unread-in var(--ff-dur-fresh, 1100ms) ease-out;
}

/* After .ff-bell-unread on purpose: a new unread row carries both classes, the two tie on specificity,
   and this one wins on source order. Its tint fades down to the row's own background, unread or not. */
.ff-bell-row-in {
    animation:
        ff-bell-row-in var(--ff-dur-row, 320ms) var(--ff-ease-enter, cubic-bezier(.22, .61, .36, 1)) backwards,
        ff-bell-row-fresh var(--ff-dur-fresh, 1100ms) ease-out;
}

.ff-bell-pill {
    display: block;
    box-sizing: border-box;
    width: calc(100% - 16px);
    min-height: 36px;
    margin: 8px 8px 4px;
    padding: 6px 12px;
    border: 0;
    border-radius: 999px;
    background-color: var(--mud-palette-primary);
    color: var(--mud-palette-primary-text);
    font: inherit;
    font-size: .8125rem;
    font-weight: 600;
    line-height: 1.4;
    white-space: nowrap;
    overflow: hidden;
    text-overflow: ellipsis;
    cursor: pointer;
    animation: ff-bell-pill-in var(--ff-dur-handoff, 240ms) var(--ff-ease-enter, cubic-bezier(.22, .61, .36, 1)) backwards;
}

.ff-bell-pill:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
}

@keyframes ff-bell-bump-a {
    0% {
        transform: scale(1);
    }
    50% {
        transform: scale(1.25);
    }
    100% {
        transform: scale(1);
    }
}

@keyframes ff-bell-bump-b {
    0% {
        transform: scale(1);
    }
    50% {
        transform: scale(1.25);
    }
    100% {
        transform: scale(1);
    }
}

@keyframes ff-bell-swing-a {
    0% {
        transform: rotate(0deg);
    }
    20% {
        transform: rotate(12deg);
    }
    40% {
        transform: rotate(-10deg);
    }
    60% {
        transform: rotate(6deg);
    }
    80% {
        transform: rotate(-3deg);
    }
    100% {
        transform: rotate(0deg);
    }
}

@keyframes ff-bell-swing-b {
    0% {
        transform: rotate(0deg);
    }
    20% {
        transform: rotate(12deg);
    }
    40% {
        transform: rotate(-10deg);
    }
    60% {
        transform: rotate(6deg);
    }
    80% {
        transform: rotate(-3deg);
    }
    100% {
        transform: rotate(0deg);
    }
}

@keyframes ff-bell-row-in {
    from {
        opacity: 0;
        transform: translateY(-6px);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-bell-row-fresh {
    from {
        background-color: rgba(var(--mud-palette-primary-rgb), .18);
    }
}

@keyframes ff-bell-unread-in {
    from {
        background-color: transparent;
    }
}

@keyframes ff-bell-pill-in {
    from {
        opacity: 0;
        transform: translateY(4px);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

/* The reduced-motion badge: a ring that is on for its whole run and gone after it, with no scale. Read
   only by the arm below. */
@keyframes ff-bell-ring-a {
    from,
    to {
        box-shadow: 0 0 0 2px var(--mud-palette-error);
    }
}

@keyframes ff-bell-ring-b {
    from,
    to {
        box-shadow: 0 0 0 2px var(--mud-palette-error);
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-bell-bump-a {
        animation: ff-bell-ring-a var(--ff-dur-emph, 1.6s) linear;
    }

    .ff-bell-bump-b {
        animation: ff-bell-ring-b var(--ff-dur-emph, 1.6s) linear;
    }

    .ff-bell-swing-a .mud-icon-root,
    .ff-bell-swing-b .mud-icon-root {
        animation: none;
    }

    .ff-bell-unread {
        animation: ff-bell-unread-in var(--ff-dur-fresh, 1100ms) ease-out;
    }

    .ff-bell-row-in {
        animation: ff-bell-row-fresh var(--ff-dur-fresh, 1100ms) ease-out;
    }

    .ff-bell-pill {
        animation: none;
    }
}

/* ---- end NB-2 ---- */

/* =============================================================================================
   63H (Phase 63, 2026-10-22) - the field moves

   Behind Features:LiveMotionEnabled, and inert without it: every selector below names a class that
   only LiveGameField emits when a host hands it a play presenter (ff-lgp-field, ff-lgp-ball-go,
   ff-lgp-ball-goal, ff-lgp-seg-in, ff-lgp-tail, ff-lgp-held, ff-lgp-cap, ff-lgp-capchip, ff-lgp-slot,
   ff-lgx-dot), and with the key dark the hosts construct no presenter, so none of them is ever
   emitted and nothing here can match.

   THE BALL OF A BEAT (.ff-lgp-ball-go, R6 2.11 rule 1). A new keyed SVG group per beat carries both
   ends of the snap as --ff-lgp-from and --ff-lgp-to in the field's own units (inside an SVG a CSS px
   in a transform is a user unit), and translates from one to the other from its first frame. Never a
   transition on the circle's cx: SVG geometry attributes are not reliably transitionable in WebKit.
   The group's own transform ATTRIBUTE is the ball at the end of its travel, so wherever no animation
   runs (reduced motion, or an engine that cannot animate a custom property in a keyframe) the ball
   simply sits at its end. A travel that ends on the goal line (.ff-lgp-ball-goal) takes the longer
   --ff-lgp-score-travel on the exit curve, which accelerates into the end zone.

   THE BEAT'S SEGMENT (.ff-lgp-seg-in) draws itself over its held composed segment (.ff-lgp-tail, which
   also hides every segment whose play is still waiting). The line carries pathLength="1", so a dash of
   1 is the whole line and the offset runs 1 to 0. THE DASH LIVES ONLY INSIDE THE KEYFRAME and the fill
   mode is backwards, so the resting line never carries a dash array: an engine that ignores pathLength
   on a line shows a short shimmer for the draw's 500ms and then the solid line, never a dotted one.
   The planned fallback if the phone walk shows that shimmer is an opacity fade on this one rule.

   THE LINES WHILE WALKING (.ff-lgp-held): the line of scrimmage, the first down line and the direction
   arrow describe where the walk is going, not where the ball is drawn, so they fade to .35 over the
   handoff. A fade under 400ms, so the reduced-motion arm keeps it (plan 9.2).

   THE CAPTION (.ff-lgp-cap) and THE OVERLAY SLOT (.ff-lgp-slot) are absolutely positioned over the
   picture inside .ff-lgp-field, whose one declaration is position: relative. An absolutely positioned
   child of the field's flex column is not a flex item, so neither takes the column's gap or any height:
   nothing under the field moves at 360px, 600px or 960px. The slot is the picture's own box by the
   viewBox's 120 by 44 ratio, and transparent to a tap.

   A SCORING MARK THAT ARRIVES (.ff-lgx-dot) drops in over --ff-dur-pop on the pop curve. The class lives
   here; 63J adds the score sequence's own timing to it.

   Every curve and every shared duration is a DM-0 token read with var(), and this block declares none
   of them (DraftMotionTokensStylesheetTests fails a second declaration). The three live-only durations
   and the travel curve are live-local names on :root. Only transform, opacity and a stroke dash
   animate.

   REDUCED MOTION (plan 9.2): movement goes, information stays. The ball is placed at its end at the
   beat's start, the segment is drawn whole, the caption and the new mark are simply present, and the
   held lines keep their fade. The cadence is untouched, because it is the presenter's and it is order.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after DM-0, NB-1 and
   DM-1, which AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker has to stay
   the last block marker in the sheet.
   ============================================================================================= */

:root {
    --ff-lgp-travel: 600ms;
    --ff-lgp-score-travel: 700ms;
    --ff-lgp-draw: 500ms;
    --ff-lgp-ease-travel: cubic-bezier(.45, 0, .2, 1);
}

.ff-lgp-field {
    position: relative;
}

.ff-lgp-ball-go {
    animation: ff-lgp-travel var(--ff-lgp-travel) var(--ff-lgp-ease-travel) both;
}

.ff-lgp-ball-go.ff-lgp-ball-goal {
    animation-duration: var(--ff-lgp-score-travel);
    animation-timing-function: var(--ff-ease-exit);
}

.ff-lgp-seg-in {
    animation: ff-lgp-draw var(--ff-lgp-draw) var(--ff-ease-enter) backwards;
}

.ff-lgp-tail {
    opacity: 0;
}

.ff-lgp-held {
    opacity: .35;
    transition: opacity var(--ff-dur-handoff) var(--ff-ease-enter);
}

.ff-lgp-cap {
    position: absolute;
    top: 4px;
    left: 0;
    right: 0;
    display: flex;
    justify-content: center;
    pointer-events: none;
    animation: ff-lgp-cap-in var(--ff-dur-handoff) var(--ff-ease-enter) backwards;
}

.ff-lgp-capchip {
    padding: 1px 8px;
    border-radius: 999px;
    border: 1px solid var(--mud-palette-lines-default);
    background: var(--mud-palette-surface);
    color: var(--mud-palette-text-secondary);
    font-size: .62rem;
    letter-spacing: .04em;
    text-transform: uppercase;
    white-space: nowrap;
}

.ff-lgp-slot {
    position: absolute;
    top: 0;
    left: 0;
    right: 0;
    aspect-ratio: 120 / 44;
    pointer-events: none;
}

.ff-lgx-dot {
    transform-box: fill-box;
    transform-origin: center;
    animation: ff-lgx-drop var(--ff-dur-pop) var(--ff-ease-pop) backwards;
}

@keyframes ff-lgp-travel {
    from {
        transform: translate(var(--ff-lgp-from), 0);
    }
    to {
        transform: translate(var(--ff-lgp-to), 0);
    }
}

@keyframes ff-lgp-draw {
    from {
        stroke-dasharray: 1;
        stroke-dashoffset: 1;
    }
    to {
        stroke-dasharray: 1;
        stroke-dashoffset: 0;
    }
}

@keyframes ff-lgp-cap-in {
    from {
        opacity: 0;
        transform: translateY(-4px);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-lgx-drop {
    from {
        opacity: 0;
        transform: translateY(-3px) scale(.4);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-lgp-ball-go {
        animation: none;
    }

    .ff-lgp-seg-in {
        animation: none;
    }

    .ff-lgp-cap {
        animation: none;
    }

    .ff-lgx-dot {
        animation: none;
    }
}

/* ---- end 63H ---- */

/* =============================================================================================
   63M (Phase 63, 2026-10-22) - the family echoes

   Behind Features:LiveMotionEnabled, and inert without it: every class this block styles (all of
   them .ff-lge-, "live echoes", a prefix nothing else uses) is put on the page only by the three
   surfaces' echo paths, and with the key dark none of them is ever emitted, so nothing here can
   match. The two classes it reuses rather than owns are 54D's .ff-lgc-flash (the family's one
   emphasis, which the Matchups row now carries beside the Live Now entry and the red zone card) and
   the shipped .ff-lgk-dock-bar and .ff-mu-card it qualifies.

   ONE MOMENT, ONE SURFACE (plan 5.7). The surface a member is looking at carries the whole moment;
   these three carry a short echo in their own vocabulary and nothing more. The dock: a 3px stripe
   sweeps once across the top of the shipped pulse and the school is bold. The Live Now entry: the
   clock cell reads "Scored" and the side that scored is the bold one. A Matchups row: the risen
   number rolls in and the row flashes and holds a fill. Each lasts the family's eight seconds
   (LiveMomentCopy.DockPulseSeconds); the components take the classes off, so nothing here counts.

   THE DOCK'S HEIGHT DOES NOT MOVE, and that is the acceptance (plan R15). The stripe is a pseudo
   element positioned absolutely inside the bar, so it takes no layout; the bar gains position:
   relative and nothing else, no padding, no border, no height. FOOT-1's --ff-lgk-dock-clearance is
   neither read nor written here. The Live Now word sits in the clock's own grid cell over the clock
   itself, which stays in the cell unseen, so the cell is never narrower than the clock it replaces.

   MOTION (plan 9.1). Only transform and opacity animate, every duration and curve is a DM-0 token
   read with var() (this block declares no custom property), and nothing repeats: the sweep and the
   roll each play once, on an element created with its class.

   REDUCED MOTION (plan 9.2): the word, the bold and the fill stay; the sweep and the roll go. The
   stripe is simply there for the window, the risen number simply new, and 54D's own arm already
   stills the flash. Less motion is not less information.

   360px: the dock keeps its one line of room, the Live Now word is shorter than the clock text it
   covers, and the Matchups roll is inside the score chip's own text. Nothing here declares a width or
   a media query beyond the reduced-motion arm.

   Inserted as its own commented block IMMEDIATELY BEFORE the UX-1 banner below, after every Phase 60
   and Phase 61 block and after 63H (the round's Phase 63 blocks land in merge order), which
   AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker has to stay the last
   block marker in the sheet.
   ============================================================================================= */

.ff-lgk-dock-bar.ff-lge-dock-bar {
    position: relative;
}

/* The stripe: inset by the bar's own side padding so the pill's rounded ends never clip it. */
.ff-lge-dock-bar::before {
    content: "";
    position: absolute;
    top: 0;
    left: 1.1rem;
    right: 1.1rem;
    height: 3px;
    border-radius: 0 0 3px 3px;
    background-color: var(--mud-palette-primary);
    pointer-events: none;
    transform-origin: left center;
    animation: ff-lge-sweep var(--ff-dur-row) var(--ff-ease-enter) backwards;
}

.ff-lge-dock-school {
    font-weight: 700;
}

/* The Live Now label is bold as shipped, so the echo sets the side that did not score at the regular
   weight and leaves the scorer bold: the text only ever gets narrower, never wider. */
.ff-gd-livenow .gm .tms.ff-lge-tms {
    font-weight: 400;
}

.ff-gd-livenow .gm .tms.ff-lge-tms .ff-lge-side {
    font-weight: 700;
}

.ff-gd-livenow .gm .cl.ff-lge-cl {
    display: inline-grid;
}

.ff-lge-cl > .ff-lge-was,
.ff-lge-cl > .ff-lge-word {
    grid-area: 1 / 1;
}

.ff-lge-was {
    visibility: hidden;
}

.ff-lge-word {
    justify-self: end;
    font-weight: 700;
    color: var(--mud-palette-text-primary);
}

/* The Matchups row: 54D's flash rides the class beside this one, and this is the fill it holds. */
.ff-mu-card.ff-lge-risen {
    background-color: rgba(var(--mud-palette-primary-rgb), .10);
}

.ff-lge-roll {
    display: inline-block;
    animation: ff-lge-roll var(--ff-dur-row) var(--ff-ease-pop) backwards;
}

@keyframes ff-lge-sweep {
    from {
        transform: scaleX(0);
    }
    to {
        transform: scaleX(1);
    }
}

@keyframes ff-lge-roll {
    from {
        opacity: 0;
        transform: translateY(.6em);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-lge-dock-bar::before {
        animation: none;
    }

    .ff-lge-roll {
        animation: none;
    }
}

/* ---- end 63M ---- */

/* =============================================================================================
   63I (Phase 63, 2026-10-22) - the hosts walk plays, and the catch-up narrates

   Behind Features:LiveMotionEnabled, and inert without it: every selector below names a class that
   only the live sheet, the full page stage and the drives block emit when a host owns a play presenter
   (ff-lgp-rowwrap, ff-lgp-in, ff-lgp-group, ff-lgp-say, ff-lgp-sr), and with the key dark the hosts
   construct no presenter, so none of them is ever emitted and nothing here can match.

   A PLAY ROW THAT ARRIVES (.ff-lgp-in on the "This drive" row's keyed wrapper, R6 2.11 rule 3). The
   wrapper is display: contents, so the row lays out exactly as it does without it, and the animation
   is on the row itself, the wrapper's one child. Three animations, in this order (plan 9.2): the row
   OPENS its own height over --ff-dur-open, so the rows under it ease down instead of snapping; it fades
   and rises over --ff-dur-handoff, starting one --ff-dm-stagger after the open; and it carries the
   fresh tint for --ff-dur-fresh, which ends before the next beat starts. During a fast forward each
   row's --ff-lgp-i (written by the drives block) delays all three by that many staggers. A GROUP
   (.ff-lgp-group: plays older than the paced window, or everything but the newest on a resume) gets
   the tint and no movement. Every fill mode is backwards, so a row at rest holds nothing of its own.

   THE LAST PLAY LINE'S HANDOFF (.ff-lgp-say) is on the value element the hosts key by the play it
   shows, so each beat's words are a new element that fades in once over --ff-dur-handoff, and the
   settle onto the same play re-enters nothing. The value is an inline span inside a wrapping line, so
   the handoff is opacity only: giving it a box of its own to rise in would change how the line wraps at
   360px, which the plan forbids.

   .ff-lgp-sr is the walk's one status line, visually hidden and read by a screen reader: "Catching up"
   once when a walk or a resume starts, never once per play. Its 1px box is the standard visually hidden
   pattern, not a layout width.

   Every curve and duration is a DM-0 token read with var(), and this block declares no token at all,
   neither DM-0's nor 63H's (DraftMotionTokensStylesheetTests fails a second declaration). Only
   opacity, transform and background-color animate, plus the row open.

   THE ROW OPEN IS A RECORDED EXCEPTION TO PLAN 9.1's COMPOSITOR-ONLY RULE (Phase 63 audit fix P63-A-12).
   ff-lgp-row-open animates max-height and the vertical padding, which is layout: it is the plan's own row
   arrival ("200 ms open", 9.2; "the open is a row's own height", 9.4), Phase 60's ff-dm-row-open shape, and
   the only way the rows under an arriving one ease down rather than snap, which a transform cannot do
   (a scaled row still takes its full height at once). Unlike 63K's bar it is NOT contained: for --ff-dur-open
   (200 ms) per arrival it reflows the drives column under the row, and 63K's new swing row reuses it on the
   swings list. While the class stands (the beat) the row also carries overflow: hidden, which clips its own
   open. Recorded here and owed to plan 9.1 and the runbook (the docs slice). The rise animates opacity FROM
   zero to the row's own opacity (no to-value), so a dimmed garbage time row rises to its dim and never
   flashes to full opacity and snaps back.

   REDUCED MOTION (plan 9.2): movement goes, information stays. A row is present on its beat with the
   tint kept, a group keeps its tint, and the Last play line swaps instantly. The cadence is the
   presenter's and it is order, so it is untouched.

   Inserted as its own commented block in the Phase 63 tail, after 63H and 63M in merge order and
   before the UX-1 banner below, which AppCssIntegrityTests and PickInFlightRoomTests both pin: the
   UX-1 end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

.ff-lgp-rowwrap {
    display: contents;
}

.ff-lgp-rowwrap.ff-lgp-in > * {
    overflow: hidden;
    animation:
        ff-lgp-row-open var(--ff-dur-open) var(--ff-ease-enter) calc(var(--ff-lgp-i, 0) * var(--ff-dm-stagger)) backwards,
        ff-lgp-row-rise var(--ff-dur-handoff) var(--ff-ease-enter) calc((var(--ff-lgp-i, 0) + 1) * var(--ff-dm-stagger)) backwards,
        ff-lgp-row-fresh var(--ff-dur-fresh) var(--ff-ease-enter) calc(var(--ff-lgp-i, 0) * var(--ff-dm-stagger)) backwards;
}

.ff-lgp-rowwrap.ff-lgp-group > * {
    animation: ff-lgp-row-fresh var(--ff-dur-fresh) var(--ff-ease-enter) backwards;
}

.ff-lgp-say {
    animation: ff-lgp-say var(--ff-dur-handoff) var(--ff-ease-enter) backwards;
}

.ff-lgp-sr {
    position: absolute;
    width: 1px;
    height: 1px;
    margin: -1px;
    padding: 0;
    border: 0;
    overflow: hidden;
    clip-path: inset(50%);
    white-space: nowrap;
}

@keyframes ff-lgp-row-open {
    from {
        max-height: 0;
        padding-top: 0;
        padding-bottom: 0;
    }
    to {
        max-height: 12rem;
    }
}

@keyframes ff-lgp-row-rise {
    from {
        opacity: 0;
        transform: translateY(6px);
    }
    to {
        transform: none;
    }
}

@keyframes ff-lgp-row-fresh {
    from {
        background-color: rgba(var(--mud-palette-primary-rgb), .18);
    }
    to {
        background-color: transparent;
    }
}

@keyframes ff-lgp-say {
    from {
        opacity: 0;
    }
    to {
        opacity: 1;
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-lgp-rowwrap.ff-lgp-in > * {
        animation: ff-lgp-row-fresh var(--ff-dur-fresh) var(--ff-ease-enter) backwards;
    }

    .ff-lgp-say {
        animation: none;
    }
}

/* ---- end 63I ---- */

/* =============================================================================================
   63J (Phase 63, 2026-10-22) - the scoring moment

   Behind Features:LiveMotionEnabled AND Features:LiveScoreCelebrationEnabled, and inert without both:
   every selector below names a .ff-lgx- class that only the two live hosts, the field and the
   celebration's Big branch emit while a host owns a play presenter AND the celebration key is on, so with
   either key dark none of them is ever emitted and nothing here can match. The one class it qualifies
   rather than owns is 63H's .ff-lgx-dot, whose drop it times to the banner's entrance.

   THE SEQUENCE IS ONE RENDER AND ANIMATION-DELAY (plan 3.4, 9.1). The render that starts a score creates
   every element below with its class, keyed by the sequence, and the choreography inside it is delays,
   never a C# step: at 0 the scorer's number rises out of its clip (--ff-lgx-roll on the pop curve) and the
   scoring side takes two --ff-dur-emph cycles of its colour; at 600 ms the attacked end zone fills to 85 %
   (half on a field goal) and one light band sweeps across it; at 700 ms the kind chip stands where the
   zone chip stood; at 900 ms the banner rises and scales in, which is also the haptic's instant and the
   arriving scoring mark's drop; 600 ms before the hold ends the banner, the ribbon and the light exit. The
   hold is --ff-lgx-hold, which is LiveMomentCopy.CelebrationSeconds (a touchdown's 6 s); a shorter kind's
   element carries its own --ff-lgx-len inline (4 s, or 3.2 s for a standalone conversion).

   COLOUR IS THE SCHOOL'S AND NEVER THE ONLY CARRIER. The scorer's primary and the ink that reads on it
   arrive as --ff-lgx-fill and --ff-lgx-ink inline, chosen by luminance on the WCAG crossover the field's
   marks already use, and the palette primary stands when the payload has no colour. Every one of them
   sits beside words that say the same thing.

   THE BANNER TAKES NO LAYOUT. Its host is zero height and absolutely positioned on the field's midline,
   inset by the end zone's width (10 of the 120 field units), inside 63H's absolutely positioned slot, so
   nothing under the field moves at 360px, 600px or 960px. Its type is clamp() sized and its words wrap
   anywhere, so a long school and two named scorers stay inside the field at 360px.

   Every curve and shared duration is a DM-0 token read with var(); this block declares only its own
   .ff-lgx- live-local names, and neither a DM-0 token nor a 63H one. Only transform, opacity,
   box-shadow and a stroke dash animate.

   REDUCED MOTION (plan 9.2): movement goes, information stays. The number is simply new with a static
   2px ring in the scorer's colour for 3.2 s, the emphasis is that ring, the ribbon and the banner are
   present for the hold without rising or fading, the end zone fill is applied at the start and held with
   no sweep, the kick arc is drawn whole, the kind chip and the talk action are simply there.

   Inserted as its own commented block in the Phase 63 tail, after 63I in merge order and before the
   UX-1 banner below, which AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker
   has to stay the last block marker in the sheet.
   ============================================================================================= */

:root {
    --ff-lgx-hold: 6s;
    --ff-lgx-roll: 420ms;
    --ff-lgx-fill-in: 300ms;
    --ff-lgx-sweep: 600ms;
    --ff-lgx-arc: 600ms;
    --ff-lgx-at-light: 600ms;
    --ff-lgx-at-chip: 700ms;
    --ff-lgx-at-banner: 900ms;
    --ff-lgx-out-before: 600ms;
}

/* The head: a digit rises out of its clip; the scoring side carries the emphasis. */
.ff-lgx-clip {
    display: inline-block;
    overflow: hidden;
    vertical-align: bottom;
}

.ff-lgx-num {
    display: inline-block;
}

.ff-lgx-roll {
    animation: ff-lgx-rise var(--ff-lgx-roll) var(--ff-ease-pop) backwards;
}

.ff-lgx-side {
    border-radius: 6px;
    animation: ff-lgx-emph var(--ff-dur-emph) var(--ff-ease-enter) 2;
}

/* The ribbon wraps under the state row and never over the score. */
.ff-lgx-ribbon {
    margin-top: 4px;
    padding: 2px 8px;
    border-radius: 4px;
    background-color: var(--ff-lgx-fill, var(--mud-palette-primary));
    color: var(--ff-lgx-ink, var(--mud-palette-primary-text));
    font-size: .78rem;
    font-weight: 600;
    line-height: 1.3;
    min-width: 0;
    overflow-wrap: anywhere;
    animation:
        ff-lgx-in var(--ff-dur-handoff) var(--ff-ease-enter) backwards,
        ff-lgx-out var(--ff-dur-handoff) var(--ff-ease-exit) calc(var(--ff-lgx-len, var(--ff-lgx-hold)) - var(--ff-lgx-out-before)) forwards;
}

/* The kind chip, in the zone chip's slot. */
.ff-lgx-kind {
    padding: 0 8px;
    border-radius: 999px;
    border: 1px solid var(--mud-palette-primary);
    color: var(--mud-palette-primary);
    font-size: .62rem;
    font-weight: 700;
    letter-spacing: .04em;
    text-transform: uppercase;
    white-space: nowrap;
    animation: ff-lgx-in var(--ff-dur-handoff) var(--ff-ease-enter) var(--ff-lgx-at-chip) backwards;
}

/* "Talk about this game": one emphasis cycle. */
.ff-lgx-talk {
    animation: ff-lgx-emph var(--ff-dur-emph) var(--ff-ease-enter) 1;
}

/* The banner: a zero height anchor on the field's midline, inset by the end zones. */
.ff-lgx-host {
    position: absolute;
    top: 50%;
    left: calc(100% * 10 / 120);
    right: calc(100% * 10 / 120);
    height: 0;
    display: flex;
    align-items: center;
    justify-content: center;
    pointer-events: none;
}

/* The banner's lines (Phase 63 audit fix P63-A-15, plan 9.4's "at most four lines inside the field"): the
   YOU tag, the big word and the eight point tail share the first line where it fits, and the school, the
   scorer (one line) and the score line take a line each, so the banner is four lines at most from 600px up;
   the narrow arm after the reduced-motion one drops the school line, which the score line repeats. */
.ff-lgx-banner {
    display: flex;
    flex-flow: row wrap;
    justify-content: center;
    align-items: baseline;
    column-gap: .35em;
    row-gap: 1px;
    min-width: 0;
    max-width: 100%;
    box-sizing: border-box;
    padding: 4px 10px;
    border-radius: 8px;
    background-color: var(--ff-lgx-fill, var(--mud-palette-primary));
    color: var(--ff-lgx-ink, var(--mud-palette-primary-text));
    text-align: center;
    line-height: 1.15;
    overflow-wrap: anywhere;
    box-shadow: 0 2px 10px rgba(0, 0, 0, .35);
    animation:
        ff-lgx-banner-in var(--ff-dur-pop) var(--ff-ease-pop) var(--ff-lgx-at-banner) backwards,
        ff-lgx-out var(--ff-dur-handoff) var(--ff-ease-exit) calc(var(--ff-lgx-len, var(--ff-lgx-hold)) - var(--ff-lgx-out-before)) forwards;
}

/* The reader's own score: a primary ring beside the YOU tag. */
.ff-lgx-banner.ff-lgx-mine {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
}

.ff-lgx-you {
    padding: 0 6px;
    border-radius: 999px;
    background-color: var(--mud-palette-surface);
    color: var(--mud-palette-primary);
    font-size: .58rem;
    font-weight: 800;
    letter-spacing: .08em;
    text-transform: uppercase;
}

.ff-lgx-big {
    font-size: clamp(1rem, 5.2vw, 1.6rem);
    font-weight: 800;
    letter-spacing: .06em;
    text-transform: uppercase;
}

.ff-lgx-tail {
    font-size: clamp(.62rem, 2.6vw, .8rem);
    font-weight: 600;
}

.ff-lgx-school {
    display: inline-flex;
    flex-basis: 100%;
    justify-content: center;
    align-items: center;
    gap: 4px;
    min-width: 0;
    font-size: clamp(.66rem, 2.8vw, .85rem);
    font-weight: 600;
}

.ff-lgx-mono {
    padding: 0 4px;
    border-radius: 3px;
    border: 1px solid currentColor;
    font-size: .58rem;
    font-weight: 800;
}

.ff-lgx-who {
    flex-basis: 100%;
    font-size: clamp(.6rem, 2.4vw, .75rem);
    display: -webkit-box;
    -webkit-line-clamp: 1;
    line-clamp: 1;
    -webkit-box-orient: vertical;
    overflow: hidden;
}

.ff-lgx-line {
    flex-basis: 100%;
    font-size: clamp(.62rem, 2.6vw, .8rem);
    font-variant-numeric: tabular-nums;
}

/* The field: the end zone the scorer attacks, its light band, and a field goal's kick arc. The light is
   decoration over the picture, so it never takes a tap from it. */
.ff-lgx-light {
    pointer-events: none;
}

.ff-lgx-fill {
    fill: var(--ff-lgx-fill, var(--mud-palette-primary));
    opacity: .85;
    animation:
        ff-lgx-light var(--ff-lgx-fill-in) var(--ff-ease-enter) var(--ff-lgx-at-light) backwards,
        ff-lgx-out var(--ff-dur-handoff) var(--ff-ease-exit) calc(var(--ff-lgx-len, var(--ff-lgx-hold)) - var(--ff-lgx-out-before)) forwards;
}

.ff-lgx-half .ff-lgx-fill {
    opacity: .425;
}

.ff-lgx-sweep {
    fill: var(--mud-palette-white, #fff);
    opacity: 0;
    animation: ff-lgx-band var(--ff-lgx-sweep) var(--ff-ease-enter) var(--ff-lgx-at-light);
}

.ff-lgx-arc {
    fill: none;
    stroke: var(--mud-palette-text-primary);
    stroke-width: .5;
    stroke-linecap: round;
    animation: ff-lgx-draw var(--ff-lgx-arc) var(--ff-ease-enter) backwards;
}

/* 63H's arriving scoring mark drops with the banner while a score is celebrated. */
.ff-lgx-scoring .ff-lgx-dot {
    animation-delay: var(--ff-lgx-at-banner);
}

@keyframes ff-lgx-rise {
    from {
        opacity: 0;
        transform: translateY(100%);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-lgx-emph {
    0%, 100% {
        box-shadow: 0 0 0 0 transparent;
    }
    50% {
        box-shadow: 0 0 0 2px var(--ff-lgx-fill, var(--mud-palette-primary));
    }
}

@keyframes ff-lgx-in {
    from {
        opacity: 0;
        transform: translateY(-3px);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-lgx-out {
    to {
        opacity: 0;
    }
}

@keyframes ff-lgx-banner-in {
    from {
        opacity: 0;
        transform: translateY(8px) scale(.85);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-lgx-light {
    from {
        opacity: 0;
    }
}

@keyframes ff-lgx-band {
    0% {
        opacity: 0;
        transform: translateX(0);
    }
    30% {
        opacity: .55;
    }
    100% {
        opacity: 0;
        transform: translateX(7px);
    }
}

@keyframes ff-lgx-draw {
    from {
        stroke-dasharray: 1;
        stroke-dashoffset: 1;
    }
    to {
        stroke-dasharray: 1;
        stroke-dashoffset: 0;
    }
}

@keyframes ff-lgx-still {
    from {
        box-shadow: 0 0 0 2px var(--ff-lgx-fill, var(--mud-palette-primary));
    }
    to {
        box-shadow: none;
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-lgx-roll {
        animation: none;
    }

    .ff-lgx-rolling {
        animation: ff-lgx-still calc(var(--ff-dur-emph) * 2) step-end;
    }

    .ff-lgx-side {
        animation: ff-lgx-still calc(var(--ff-dur-emph) * 2) step-end;
    }

    .ff-lgx-ribbon {
        animation: none;
    }

    .ff-lgx-kind {
        animation: none;
    }

    .ff-lgx-talk {
        animation: none;
    }

    .ff-lgx-banner {
        animation: none;
    }

    .ff-lgx-fill {
        animation: none;
    }

    .ff-lgx-sweep {
        animation: none;
    }

    .ff-lgx-arc {
        animation: none;
    }
}

/* Plan 9.4's four line cap at the phone widths (Phase 63 audit fix P63-A-15): the school line goes, because
   the score line under it already names the scoring school first, so the banner is at most the big word's
   line (with the YOU tag and the tail, wrapping to a second only for the eight point tail), the scorer and
   the score. */
@media (max-width: 599.98px) {
    .ff-lgx-school {
        display: none;
    }
}

/* ---- end 63J ---- */

/* =============================================================================================
   63K (Phase 63, 2026-10-22) - the numbers around the score

   Behind Features:LiveMotionEnabled, and inert without it: every selector below names a class that only
   the live sheet and the full page stage emit while they own a play presenter (ff-lgp-wp, ff-lgp-gx,
   ff-lgp-gx-end, ff-lgp-seg, ff-lgp-spark-in, ff-lgp-swin, ff-lgp-named, ff-lgp-scored, ff-lgp-onscore), and
   with the key dark the hosts construct no presenter, so none of them is ever emitted and nothing here can
   match. The bar, the gauge, the line, the swings list and the players block are the shipped ones.

   THE WIN PROBABILITY BAR (.ff-lgp-wp) is the plan's ONE recorded exception to the compositor-only rule
   (R6 2.10, plan 9.1): its two halves transition WIDTH over --ff-lgp-bar, and the bar itself declares
   contain: layout paint, so the reflow a width change costs ends at the bar's own box and nothing around
   it moves. THE DESERVE TO WIN GAUGE does not take the exception: each of its rects spans the gauge and
   is scaled from its own edge (.ff-lgp-gx from the left, .ff-lgp-gx-end from the right), so a new share is
   a transform transition over the same duration.

   THE SPARKLINE'S NEWEST SEGMENT (.ff-lgp-seg) is its own line, keyed by its point's instant, drawn in the
   line's own ink; a segment newer than the one the open began with also carries .ff-lgp-spark-in and fades
   in once over --ff-lgp-seg-fade. (Its own name, not 63H's .ff-lgp-seg-in: Phase 63 audit fix P63-A-3. The
   two blocks once declared that one selector at one specificity, so this later fade replaced the field
   segment's dash draw everywhere.) A NEW SWING ROW (.ff-lgp-swin) speaks 63I's row vocabulary, reusing its
   three keyframes: it opens its own height, rises one stagger later, and carries the fresh tint.

   THE NAMED ROW (.ff-lgp-named) is the "In this game" row the celebrated scoring play named, for the hold:
   a tint, and the "Scored" chip (.ff-lgp-scored) that enters with the banner. The points column is never
   touched; they are official.

   WHILE A SCORE'S BANNER IS UP (.ff-lgp-onscore on the probability and history sections) the numbers keep
   the sequence's time (plan 3.4): the bars and the gauge ease at the banner's entrance
   (--ff-lgx-at-banner, 900 ms) and the segment and a new swing row follow one --ff-dur-open later.

   Every curve and shared duration is a DM-0 token read with var(), the banner instant is 63J's; this block
   declares only its own two live-local durations (600 ms for the bar, 400 ms for the segment, plan 9.2)
   and redeclares no DM-0, 63H or 63J token. Only opacity, transform and background-color animate, plus
   the bar's recorded width transition and the row open 63I records.

   REDUCED MOTION (plan 9.2): instant widths and an instant gauge, the segment simply present, a new swing
   row present with its tint kept, the chip simply present; the named row's tint is a colour and is kept.

   360px (plan 9.4): nothing here declares a width; the bar is the shipped full-width bar under paint
   containment, a new swing row clips its own open, and the chip wraps inside the row's wrapping name line.

   Inserted as its own commented block in the Phase 63 tail, after 63J in merge order and before the
   UX-1 banner below, which AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker
   has to stay the last block marker in the sheet.
   ============================================================================================= */

:root {
    --ff-lgp-bar: 600ms;
    --ff-lgp-seg-fade: 400ms;
}

/* The win probability bar: the one recorded width transition, inside layout and paint containment. */
.ff-lgp-wp {
    contain: layout paint;
}

.ff-lgp-wp > span {
    transition: width var(--ff-lgp-bar) var(--ff-ease-enter);
}

/* The deserve to win gauge: each rect scales from its own edge. */
.ff-lgp-gx {
    transform-box: fill-box;
    transform-origin: 0 50%;
    transition: transform var(--ff-lgp-bar) var(--ff-ease-enter);
}

.ff-lgp-gx-end {
    transform-origin: 100% 50%;
}

/* The sparkline's newest segment, in the line's ink; a new one fades in once. */
.ff-lgp-seg {
    fill: none;
    stroke: var(--mud-palette-primary);
    stroke-width: 2;
    stroke-linecap: round;
}

.ff-lgp-spark-in {
    animation: ff-lgp-spark-in var(--ff-lgp-seg-fade) var(--ff-ease-enter) backwards;
}

/* A swing row this open had not seen: 63I's open, rise and fresh tint. */
.ff-lgp-swin {
    overflow: hidden;
    animation:
        ff-lgp-row-open var(--ff-dur-open) var(--ff-ease-enter) backwards,
        ff-lgp-row-rise var(--ff-dur-handoff) var(--ff-ease-enter) var(--ff-dm-stagger) backwards,
        ff-lgp-row-fresh var(--ff-dur-fresh) var(--ff-ease-enter) backwards;
}

/* The row the scoring play named, for the hold, and its word chip. */
.ff-lgp-named {
    border-radius: 4px;
    background-color: rgba(var(--mud-palette-primary-rgb), .14);
}

.ff-lgp-scored {
    padding: 0 6px;
    border-radius: 999px;
    background-color: var(--mud-palette-primary);
    color: var(--mud-palette-primary-text);
    font-size: .58rem;
    font-weight: 700;
    letter-spacing: .06em;
    text-transform: uppercase;
    white-space: nowrap;
    animation: ff-lgp-chip-in var(--ff-dur-open) var(--ff-ease-enter) var(--ff-lgx-at-banner) backwards;
}

/* While a score's banner is up, the numbers keep the sequence's time. */
.ff-lgp-onscore .ff-lgp-wp > span,
.ff-lgp-onscore .ff-lgp-gx {
    transition-delay: var(--ff-lgx-at-banner);
}

.ff-lgp-onscore .ff-lgp-spark-in {
    animation-delay: calc(var(--ff-lgx-at-banner) + var(--ff-dur-open));
}

.ff-lgp-onscore .ff-lgp-swin {
    animation-delay:
        calc(var(--ff-lgx-at-banner) + var(--ff-dur-open)),
        calc(var(--ff-lgx-at-banner) + var(--ff-dur-open) + var(--ff-dm-stagger)),
        calc(var(--ff-lgx-at-banner) + var(--ff-dur-open));
}

@keyframes ff-lgp-spark-in {
    from {
        opacity: 0;
    }
    to {
        opacity: 1;
    }
}

@keyframes ff-lgp-chip-in {
    from {
        opacity: 0;
        transform: translateY(-3px);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-lgp-wp > span {
        transition: none;
    }

    .ff-lgp-gx {
        transition: none;
    }

    .ff-lgp-spark-in {
        animation: none;
    }

    .ff-lgp-swin {
        animation: ff-lgp-row-fresh var(--ff-dur-fresh) var(--ff-ease-enter) backwards;
    }

    .ff-lgp-scored {
        animation: none;
    }
}

/* ---- end 63K ---- */

/* =============================================================================================
   63L (Phase 63, 2026-10-22) - the states between plays

   Behind Features:LiveMotionEnabled, and inert without it: every selector below names a class that only
   the live sheet, the full page stage and their freshness leaf (LiveFreshness) emit while they own a play
   presenter (ff-lgp-upd, ff-lgp-late, ff-lgp-ago, ff-lgp-again, ff-lgp-beat, ff-lgp-stamp, ff-lgp-zone,
   ff-lgp-zword, ff-lgp-closing, ff-lgp-fhost, ff-lgp-fban), and with the key dark the hosts construct no
   presenter, so none of them is ever emitted and nothing here can match.

   THE FRESHNESS LINE (.ff-lgp-upd) keeps the shipped .ff-lg-observed type and tone and wraps inside the
   head; on its stale rung (.ff-lgp-late, 180 seconds) it takes the warning tone through a colour
   transition and offers "Refresh now" (.ff-lgp-again), a control in the shipped "Still watching?" voice.
   THE LIVE DOT (.ff-lgp-beat) blinks once, on opacity, when a new observation keys a new dot: a heartbeat,
   never an infinite pulse. AN OBSERVED FINAL pops the head's word once (.ff-lgp-stamp) and stands a neutral
   banner over the playing surface (.ff-lgp-fban in its zero height anchor .ff-lgp-fhost, the scoring
   banner's geometry): the surface's own ground and ink, no school colour, because the end of a game is not
   a celebration of one side. The full page stage holds that closing frame for --ff-lgp-final and fades out
   over its last handoff (.ff-lgp-closing) as the page's result takes over.

   THE RED ZONE (.ff-lgp-zone, on the situation section while the state can apply) changes COLOUR rather
   than snapping: the section keeps the state's frame geometry at rest in transparent colours, so entering
   and leaving the twenty transition only the border and the fill. The shipped .ff-lgz-state paints the
   state; this block only times it. The chip's word (.ff-lgp-zword) is keyed by the word and hands off once.

   Every curve and shared duration is a DM-0 token read with var(); this block declares only its own three
   live-local durations (600 ms for the blink, 400 ms for the colour transitions, 4 s for the Final hold,
   plan 9.2) and redeclares no DM-0, 63H, 63J or 63K token. Only opacity and transform animate; the two
   transitions are colours.

   REDUCED MOTION (plan 9.2): no blink, no pop, no banner entrance, no chip handoff and no fade of the
   closing frame (the banner stands for its four seconds and goes); the two colour transitions are KEPT,
   because a colour change of 400 ms or less is information, not movement.

   360px (plan 9.4): nothing here declares a fixed width; the freshness line and "Refresh now" are a
   wrapping flex row whose line may break anywhere, inside the shipped head's min-width: 0 column, and the
   Final banner is inset by the end zones, clamped in type and limited to four lines.

   Inserted as its own commented block in the Phase 63 tail, after 63K in merge order and before the UX-1
   banner below, which AppCssIntegrityTests and PickInFlightRoomTests both pin: the UX-1 end marker has to
   stay the last block marker in the sheet.
   ============================================================================================= */

:root {
    --ff-lgp-blink: 600ms;
    --ff-lgp-zone: 400ms;
    --ff-lgp-final: 4s;
}

/* The freshness line, wrapping inside the head at 360px; the warning tone arrives as a colour. */
.ff-lgp-upd {
    display: flex;
    flex-wrap: wrap;
    align-items: baseline;
    gap: 2px 8px;
    min-width: 0;
    transition: color var(--ff-lgp-zone) var(--ff-ease-enter);
}

.ff-lgp-ago {
    min-width: 0;
    overflow-wrap: anywhere;
}

.ff-lgp-upd.ff-lgp-late {
    color: var(--mud-palette-warning);
}

/* "Refresh now": a control, so it reads as one and takes a focus ring of its own. */
.ff-lgp-again {
    padding: 0;
    border: 0;
    background: none;
    color: var(--mud-palette-primary);
    font: inherit;
    text-decoration: underline;
    cursor: pointer;
    white-space: nowrap;
}

.ff-lgp-again:focus-visible {
    outline: 2px solid var(--mud-palette-primary);
    outline-offset: 2px;
}

/* The live dot's heartbeat: one blink per new observation. */
.ff-lgp-beat {
    animation: ff-lgp-beat var(--ff-lgp-blink) var(--ff-ease-enter);
}

/* An observed Final: the head's word pops once. */
.ff-lgp-stamp {
    display: inline-block;
    animation: ff-lgp-stamp var(--ff-dur-pop) var(--ff-ease-pop) backwards;
}

/* The red zone changes colour rather than snapping. */
.ff-lgp-zone {
    transition:
        border-color var(--ff-lgp-zone) var(--ff-ease-enter),
        background-color var(--ff-lgp-zone) var(--ff-ease-enter);
}

.ff-lgp-zone:not(.ff-lgz-state) {
    padding: .5rem;
    border: 1px solid transparent;
    border-radius: 6px;
    background-color: transparent;
}

/* The zone chip's word hands off once, keyed by the word. */
.ff-lgp-zword {
    animation: ff-lgp-zword-in var(--ff-dur-handoff) var(--ff-ease-enter) backwards;
}

/* The Final banner's anchor: the scoring banner's geometry, zero height, inset by the end zones. */
.ff-lgp-fhost {
    position: absolute;
    top: 50%;
    left: calc(100% * 10 / 120);
    right: calc(100% * 10 / 120);
    height: 0;
    display: flex;
    align-items: center;
    justify-content: center;
    pointer-events: none;
}

/* The neutral Final banner: the surface's own ground and ink, no school colour. */
.ff-lgp-fban {
    display: -webkit-box;
    -webkit-box-orient: vertical;
    -webkit-line-clamp: 4;
    overflow: hidden;
    min-width: 0;
    max-width: 100%;
    box-sizing: border-box;
    padding: 4px 10px;
    border: 1px solid var(--mud-palette-lines-default);
    border-radius: 8px;
    background-color: var(--mud-palette-surface);
    color: var(--mud-palette-text-primary);
    font-size: clamp(.8rem, 3.6vw, 1.1rem);
    font-weight: 700;
    line-height: 1.2;
    text-align: center;
    overflow-wrap: anywhere;
    box-shadow: 0 2px 10px rgba(0, 0, 0, .35);
    animation: ff-lgp-fban-in var(--ff-dur-pop) var(--ff-ease-pop) backwards;
}

/* The full page stage's closing frame: it fades out over the hold's last handoff. */
.ff-lgp-closing {
    animation: ff-lgp-close var(--ff-dur-handoff) var(--ff-ease-exit) calc(var(--ff-lgp-final) - var(--ff-dur-handoff)) forwards;
}

@keyframes ff-lgp-beat {
    0% {
        opacity: 1;
    }
    50% {
        opacity: .25;
    }
    100% {
        opacity: 1;
    }
}

@keyframes ff-lgp-stamp {
    from {
        opacity: 0;
        transform: scale(.6);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-lgp-zword-in {
    from {
        opacity: 0;
        transform: translateY(3px);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-lgp-fban-in {
    from {
        opacity: 0;
        transform: translateY(8px) scale(.85);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-lgp-close {
    to {
        opacity: 0;
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-lgp-upd {
        transition: color var(--ff-lgp-zone) var(--ff-ease-enter);
    }

    .ff-lgp-beat {
        animation: none;
    }

    .ff-lgp-stamp {
        animation: none;
    }

    .ff-lgp-zone {
        transition:
            border-color var(--ff-lgp-zone) var(--ff-ease-enter),
            background-color var(--ff-lgp-zone) var(--ff-ease-enter);
    }

    .ff-lgp-zword {
        animation: none;
    }

    .ff-lgp-fban {
        animation: none;
    }

    .ff-lgp-closing {
        animation: none;
    }
}

/* ---- end 63L ---- */

/* =============================================================================================
   63N (Phase 63, 2026-10-22) - phone polish

   Three rules for the member watching on a phone. Two ride Features:LiveMotionEnabled and one is live.

   THE STICKY STAGE HEAD (the key, below 1280px). The full page stage puts one class on its game column
   (.ff-lgn-sticky) while it owns a play presenter, and with the key dark it constructs none, so the
   class is never emitted and nothing here can match. Below 1280 that column's head (the score, the state
   row, the ribbon and the freshness leaf) sticks under the app bar, so a member reading the drives, the
   numbers or the people below it keeps the score on screen. It is compact because the head already is:
   nothing here resizes it, and the freshness leaf's stale rung, which can take a second line at 360px
   with "Refresh now", simply makes the stuck head that much taller.

   WHY THE COLUMN AND NOT THE HEAD CARRIES THE CLASS. A sticky box can only travel inside its parent, and
   below 1280 the head's parent is the game column, which ends where the drives begin. So, where the
   browser can select a parent (:has, the same idiom as the dock's body:has gates), the stage below 1280
   becomes the flex column it already looked like and the game column becomes transparent to layout
   (display: contents), which hands the head the whole stage to travel in. Where it cannot, the head still
   sticks through its own column, which is the graceful half.

   IT TAKES NO LAYOUT HEIGHT. A sticky box keeps exactly its in-flow box; the head rule declares no size,
   no margin and no padding, only its offset, its stacking and an opaque ground in the page's own
   background (plus a 6px ground-coloured shadow that, at rest, falls inside the .75rem gap under the head
   and so is invisible). The stage keeps its shipped rhythm to the rem: the game column's .75rem between
   its own blocks becomes the stage's gap, and the .25rem top margin on the drives and talk columns makes
   up 45F's 1rem between columns.

   THE OFFSET IS THE APP BAR'S OWN HEIGHT, from MudBlazor's --mud-appbar-height on MudBlazor's own steps:
   seven eighths of it on a portrait phone, three quarters in landscape below 600px, the whole of it from
   600px, and the app bar's desktop bump from 601px (the .ff-appbar toolbar's 72px, which is the token
   plus an eighth). The head sits below the bar (z-index 3: over the stage's own overlays, under every
   fixed bar and dialog).

   THE LANDSCAPE FIELD CAP (the key; orientation: landscape and max-height: 500px). A landscape phone
   drew the field at most of the screen's height and pushed the Last play line off it. The picture's
   height is capped at 45vh, and the field (.ff-lgp-field, emitted only under the key) is capped at the
   width that height implies by the viewBox's 120 by 44 ratio, so the caption, the overlay slot and the
   banners that 63H to 63L size off the field's width stay registered over the capped picture. Portrait
   and every desktop are untouched.

   THE SHEET'S SCROLLER CONTAINS ITS OVERSCROLL (live, outside any key). A pull at the top of the live
   game sheet chained to the page and could reload the app (the native pull to refresh). One declaration
   on the dialog's content box, which changes no layout.

   No token is declared here: every length reads an existing one or is a rem, and nothing animates, so
   there is no reduced-motion arm to write.

   Inserted as its own commented block in the Phase 63 tail, after 63L in merge order and before the UX-1
   banner below, whose end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

@media (max-width: 1279.98px) {
    .ff-lgs-stage:has(> .ff-lgn-sticky) {
        display: flex;
        flex-direction: column;
        gap: .75rem;
    }

    .ff-lgs-stage:has(> .ff-lgn-sticky) > .ff-lgn-sticky {
        display: contents;
    }

    .ff-lgs-stage:has(> .ff-lgn-sticky) > .ff-lgs-drives,
    .ff-lgs-stage:has(> .ff-lgn-sticky) > .ff-lgs-talk {
        margin-top: .25rem;
    }

    .ff-lgn-sticky > .ff-lg-head {
        position: sticky;
        top: calc(var(--mud-appbar-height) - var(--mud-appbar-height) / 8);
        z-index: 3;
        background-color: var(--mud-palette-background);
        box-shadow: 0 .375rem 0 var(--mud-palette-background);
    }
}

@media (max-width: 1279.98px) and (orientation: landscape) {
    .ff-lgn-sticky > .ff-lg-head {
        top: calc(var(--mud-appbar-height) - var(--mud-appbar-height) / 4);
    }
}

@media (min-width: 600px) and (max-width: 1279.98px) {
    .ff-lgn-sticky > .ff-lg-head {
        top: var(--mud-appbar-height);
    }
}

@media (min-width: 601px) and (max-width: 1279.98px) {
    .ff-lgn-sticky > .ff-lg-head {
        top: calc(var(--mud-appbar-height) + var(--mud-appbar-height) / 8);
    }
}

@media (orientation: landscape) and (max-height: 500px) {
    .ff-lgp-field {
        max-width: calc(45vh * 120 / 44);
    }

    .ff-lgp-field > svg {
        max-height: 45vh;
    }
}

.ff-lg-dialog .mud-dialog-content {
    overscroll-behavior: contain;
}

/* ---- end 63N ---- */

/* =============================================================================================
   63P (Phase 63, 2026-10-25) - the big moments

   The owner's Saturday (2026-10-24): the field goal's box on the field looked great, the touchdown said
   "X team scored" in a small thing for a couple of seconds, and kickoffs, fumbles and interceptions drew
   nothing at all. Three field moments and a bigger touchdown, all behind Features:LiveMotionEnabled (and
   the touchdown's banner and light behind Features:LiveScoreCelebrationEnabled as well), and inert without
   them: every selector below names a .ff-lgp- or .ff-lgx- class that only LiveGameField and the
   celebration's Big branch emit while a host owns a play presenter, so with the key dark nothing here can
   match.

   A KICK LOFTS (.ff-lgp-ball-kick, a kickoff or a punt by the feed's own play type). The travel group
   reuses 63H's ff-lgp-travel by name over the longer --ff-lgp-kick, to where the next known snap starts,
   and its two circles (.ff-lgp-swap-from in the kicking side's colour, .ff-lgp-swap-to in the receiving
   side's) grow to 2.6 times and come back down, which is what a ball looks like from above, and change
   hands as it lands.

   A TURNOVER JARS AND CALLS ITSELF OUT (.ff-lgp-ball-turn, an interception or a lost fumble). The ball
   does not travel (the return path is not published): it pulses and shakes where the snap started and
   takes the recovering side's colour at 55 %. The callout (.ff-lgp-call) is a zero height anchor on the
   picture's midline, inset by the end zones' 10 of 120 units, inside its own copy of 63H's slot, so
   nothing under the field moves at 360px, 600px or 960px; its chip (.ff-lgp-callchip) wears the
   recovering school's colour and enters at --ff-lgp-call-at, then leaves --ff-lgp-call-out-before the
   end of the big play beat. Its type is clamp() sized and wraps anywhere.

   A TOUCHDOWN TAKES THE FIELD (.ff-lgx-td on the banner and on the end zone light). The playing surface
   washes in the scorer's colour (.ff-lgx-wash) for the hold, one ring leaves the goal line the scorer
   crossed (.ff-lgx-shock), the end zone breathes twice under the banner, and the banner has more room,
   a bigger word that settles in from a larger scale, and two glow pulses. One ring, a wash and a glow, no
   particles: the house restraint on a score stands. A field goal keeps 63J's look exactly.

   TOKENS. --ff-lgp-big is LivePlayPresenter.BigPlayBeat (3.2 s), the beat a kick or a turnover holds the
   field for. Every curve and shared duration is a DM-0 token, and 63J's sequence instants
   (--ff-lgx-at-light, --ff-lgx-at-banner, --ff-lgx-hold, --ff-lgx-out-before, --ff-lgx-fill-in) are read
   with var(); this block declares only its own live-local names. Only transform, opacity and box-shadow
   animate, and nothing transitions.

   REDUCED MOTION (plan 9.2): movement goes, information stays. The kick's ball rests on the receiving
   side's colour at its landing, the turnover's ball rests on the recovering side's, the callout and the
   wash are simply present for the beat and the hold, the banner and its word stand without the glow, and
   the ring is not drawn.

   Inserted as its own commented block in the Phase 63 tail, after 63N and before the UX-1 banner below,
   whose end marker has to stay the last block marker in the sheet.
   ============================================================================================= */

:root {
    --ff-lgp-kick: 1400ms;
    --ff-lgp-jar: 900ms;
    --ff-lgp-big: 3.2s;
    --ff-lgp-call-at: 300ms;
    --ff-lgp-call-out-before: 400ms;
    --ff-lgx-wash-in: 400ms;
    --ff-lgx-shock: 900ms;
    --ff-lgx-word: 520ms;
}

/* A kick: the group travels to the landing over the loft; the circles grow and shrink about themselves. */
.ff-lgp-ball-go.ff-lgp-ball-kick {
    animation: ff-lgp-travel var(--ff-lgp-kick) var(--ff-ease-enter) both;
}

.ff-lgp-swap-from,
.ff-lgp-swap-to {
    transform-box: fill-box;
    transform-origin: center;
}

/* At rest the ball is the receiving side's, which is also what reduced motion shows. */
.ff-lgp-swap-from {
    opacity: 0;
}

.ff-lgp-swap-to {
    opacity: 1;
}

.ff-lgp-ball-kick .ff-lgp-swap-from {
    animation: ff-lgp-loft-out var(--ff-lgp-kick) var(--ff-ease-enter) both;
}

.ff-lgp-ball-kick .ff-lgp-swap-to {
    animation: ff-lgp-loft-in var(--ff-lgp-kick) var(--ff-ease-enter) both;
}

/* A turnover: the ball jars in place and changes colour at 55 %. */
.ff-lgp-ball-turn .ff-lgp-swap-from {
    animation: ff-lgp-jar-out var(--ff-lgp-jar) var(--ff-ease-pop) both;
}

.ff-lgp-ball-turn .ff-lgp-swap-to {
    animation: ff-lgp-jar-in var(--ff-lgp-jar) var(--ff-ease-pop) both;
}

/* The callout: a zero height anchor on the picture's midline, inset by the end zones. */
.ff-lgp-call {
    position: absolute;
    top: 50%;
    left: calc(100% * 10 / 120);
    right: calc(100% * 10 / 120);
    height: 0;
    display: flex;
    align-items: center;
    justify-content: center;
    pointer-events: none;
}

.ff-lgp-callchip {
    display: flex;
    flex-flow: column;
    align-items: center;
    row-gap: 1px;
    min-width: 0;
    max-width: 100%;
    box-sizing: border-box;
    padding: 4px 12px;
    border-radius: 8px;
    background-color: var(--ff-lgx-fill, var(--mud-palette-primary));
    color: var(--ff-lgx-ink, var(--mud-palette-primary-text));
    text-align: center;
    line-height: 1.15;
    overflow-wrap: anywhere;
    box-shadow: 0 2px 10px rgba(0, 0, 0, .35);
    animation:
        ff-lgp-call-in var(--ff-dur-pop) var(--ff-ease-pop) var(--ff-lgp-call-at) backwards,
        ff-lgp-call-out var(--ff-dur-handoff) var(--ff-ease-exit) calc(var(--ff-lgp-big) - var(--ff-lgp-call-out-before)) forwards;
}

.ff-lgp-callword {
    font-size: clamp(1rem, 5.2vw, 1.6rem);
    font-weight: 800;
    letter-spacing: .08em;
    text-transform: uppercase;
}

.ff-lgp-callwho {
    font-size: clamp(.62rem, 2.6vw, .8rem);
    font-weight: 600;
}

/* The touchdown's banner: more room, two glow pulses, and a bigger word that settles in. */
.ff-lgx-banner.ff-lgx-td {
    padding: 8px 16px;
    border-radius: 12px;
    animation:
        ff-lgx-banner-in var(--ff-dur-pop) var(--ff-ease-pop) var(--ff-lgx-at-banner) backwards,
        ff-lgx-glow var(--ff-dur-emph) var(--ff-ease-enter) var(--ff-lgx-at-banner) 2,
        ff-lgx-out var(--ff-dur-handoff) var(--ff-ease-exit) calc(var(--ff-lgx-hold) - var(--ff-lgx-out-before)) forwards;
}

.ff-lgx-td .ff-lgx-big {
    font-size: clamp(1.45rem, 8vw, 2.6rem);
    letter-spacing: .1em;
    animation: ff-lgx-word var(--ff-lgx-word) var(--ff-ease-pop) var(--ff-lgx-at-banner) backwards;
}

/* The touchdown's end zone breathes twice under the banner. */
.ff-lgx-td .ff-lgx-fill {
    animation:
        ff-lgx-light var(--ff-lgx-fill-in) var(--ff-ease-enter) var(--ff-lgx-at-light) backwards,
        ff-lgx-pulse var(--ff-dur-emph) var(--ff-ease-enter) var(--ff-lgx-at-banner) 2,
        ff-lgx-out var(--ff-dur-handoff) var(--ff-ease-exit) calc(var(--ff-lgx-hold) - var(--ff-lgx-out-before)) forwards;
}

/* The wash over the playing surface, for the hold. */
.ff-lgx-wash {
    fill: var(--ff-lgx-fill, var(--mud-palette-primary));
    opacity: .22;
    pointer-events: none;
    animation:
        ff-lgx-wash-in var(--ff-lgx-wash-in) var(--ff-ease-enter) var(--ff-lgx-at-light) backwards,
        ff-lgx-out var(--ff-dur-handoff) var(--ff-ease-exit) calc(var(--ff-lgx-hold) - var(--ff-lgx-out-before)) forwards;
}

/* One ring off the goal line the scorer crossed. At rest it is not drawn, and it has no backwards fill: through
   its delay it stays at its resting opacity 0, so it appears with the light rather than sitting still at the goal
   line first. */
.ff-lgx-shock {
    fill: none;
    stroke: var(--ff-lgx-fill, var(--mud-palette-primary));
    stroke-width: .9;
    transform-box: fill-box;
    transform-origin: center;
    opacity: 0;
    animation: ff-lgx-shock var(--ff-lgx-shock) var(--ff-ease-exit) var(--ff-lgx-at-light);
}

@keyframes ff-lgp-loft-out {
    0% {
        transform: scale(1);
        opacity: 1;
    }
    50% {
        transform: scale(2.6);
        opacity: 1;
    }
    88% {
        transform: scale(1.05);
        opacity: 1;
    }
    100% {
        transform: scale(1);
        opacity: 0;
    }
}

@keyframes ff-lgp-loft-in {
    0% {
        transform: scale(1);
        opacity: 0;
    }
    50% {
        transform: scale(2.6);
        opacity: 0;
    }
    88% {
        transform: scale(1.05);
        opacity: 0;
    }
    100% {
        transform: scale(1);
        opacity: 1;
    }
}

@keyframes ff-lgp-jar-out {
    0% {
        transform: none;
        opacity: 1;
    }
    14% {
        transform: translateX(-1.5px) scale(1.5);
    }
    28% {
        transform: translateX(1.5px) scale(1.9);
    }
    42% {
        transform: translateX(-1.5px) scale(1.6);
    }
    54% {
        transform: translateX(0) scale(1.3);
        opacity: 1;
    }
    55% {
        opacity: 0;
    }
    100% {
        transform: none;
        opacity: 0;
    }
}

@keyframes ff-lgp-jar-in {
    0% {
        transform: none;
        opacity: 0;
    }
    14% {
        transform: translateX(-1.5px) scale(1.5);
    }
    28% {
        transform: translateX(1.5px) scale(1.9);
    }
    42% {
        transform: translateX(-1.5px) scale(1.6);
    }
    54% {
        transform: translateX(0) scale(1.3);
        opacity: 0;
    }
    55% {
        opacity: 1;
    }
    100% {
        transform: none;
        opacity: 1;
    }
}

@keyframes ff-lgp-call-in {
    from {
        opacity: 0;
        transform: scale(.6);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-lgp-call-out {
    to {
        opacity: 0;
        transform: scale(.94);
    }
}

@keyframes ff-lgx-glow {
    50% {
        box-shadow: 0 0 0 5px var(--ff-lgx-fill, var(--mud-palette-primary)), 0 6px 22px rgba(0, 0, 0, .5);
    }
}

@keyframes ff-lgx-word {
    from {
        opacity: 0;
        transform: scale(1.35);
    }
    to {
        opacity: 1;
        transform: none;
    }
}

@keyframes ff-lgx-pulse {
    0%,
    100% {
        opacity: .85;
    }
    50% {
        opacity: .5;
    }
}

@keyframes ff-lgx-wash-in {
    from {
        opacity: 0;
    }
    60% {
        opacity: .4;
    }
    to {
        opacity: .22;
    }
}

@keyframes ff-lgx-shock {
    from {
        transform: scale(1);
        opacity: .9;
    }
    to {
        transform: scale(16);
        opacity: 0;
    }
}

@media (prefers-reduced-motion: reduce) {
    .ff-lgp-ball-go.ff-lgp-ball-kick {
        animation: none;
    }

    .ff-lgp-ball-kick .ff-lgp-swap-from {
        animation: none;
    }

    .ff-lgp-ball-kick .ff-lgp-swap-to {
        animation: none;
    }

    .ff-lgp-ball-turn .ff-lgp-swap-from {
        animation: none;
    }

    .ff-lgp-ball-turn .ff-lgp-swap-to {
        animation: none;
    }

    .ff-lgp-callchip {
        animation: none;
    }

    .ff-lgx-banner.ff-lgx-td {
        animation: none;
    }

    .ff-lgx-td .ff-lgx-big {
        animation: none;
    }

    .ff-lgx-td .ff-lgx-fill {
        animation: none;
    }

    .ff-lgx-wash {
        animation: none;
    }

    .ff-lgx-shock {
        animation: none;
    }
}

/* ---- end 63P ---- */

/* =============================================================================================
   UX-1 (owner, live draft 2026-09-03 00:38 UTC) - the pick in flight banner

   A member tapped Draft while the instance sat at 99% CPU and a pick took twenty to thirty seconds
   to return. The room acknowledged nothing he could see, so he tapped the queue plus and then the
   star; the pick had landed the whole time. This is the acknowledgement, at the top of the draft
   intelligence card and above the best available list.

   360px FIRST, which is the whole reason it declares no width of its own. The sentence is long by
   design (it tells a member not to tap again, which is a sentence and not a label), so the row is a
   flex line whose text column may shrink to nothing and wrap as many times as it needs: min-width:0
   on the text, overflow-wrap on its words, and the icon frozen at its own size so a wrap can never
   squeeze it into an ellipse. There is no max-width and no fixed width anywhere in this block, so
   the banner is exactly as wide as the card holding it at every viewport, and the card is already a
   grid child that shrinks below its content (UIDN-5).

   Colour is never the only carrier. Each state ALSO changes the icon (a ballot, a cloud off, an
   error mark) and the sentence itself, so the three read apart in monochrome and to a screen reader
   (the element carries role="status" with aria-live="polite", so the resolution is announced
   without stealing focus from the board).
   ============================================================================================= */

.ff-pick-inflight {
    display: flex;
    flex-direction: column;
    gap: 6px;
    width: 100%;
    min-width: 0;
    margin-bottom: 12px;
    padding: 10px 12px;
    border-radius: 8px;
    border-left: 3px solid var(--mud-palette-primary);
    background: rgba(var(--mud-palette-primary-rgb), .10);
}

.ff-pick-inflight-line {
    display: flex;
    align-items: flex-start;
    gap: 8px;
    min-width: 0;
}

/* The one element that is allowed to grow the banner, and the one that must be allowed to shrink. */
.ff-pick-inflight-txt {
    flex: 1 1 auto;
    min-width: 0;
    font-size: .82rem;
    line-height: 1.35;
    overflow-wrap: anywhere;
}

/* The icon keeps its own size at every width; only the sentence reflows. */
.ff-pick-inflight .mud-icon-root {
    flex: 0 0 auto;
    margin-top: 1px;
}

/* The indeterminate bar spans the banner, so the motion is the width of the thing that is waiting
   rather than a spinner tucked in a corner of it. */
.ff-pick-inflight-bar {
    width: 100%;
    height: 4px;
    border-radius: 999px;
}

/* Waiting: the primary tone, because nothing has gone wrong yet. */
.ff-pick-inflight.is-live {
    border-left-color: var(--mud-palette-primary);
    background: rgba(var(--mud-palette-primary-rgb), .10);
}

/* Lost: a warning and not an error. The pick may well have landed, and painting an unknown outcome
   red is the same false certainty the old "try again" copy carried. */
.ff-pick-inflight.is-lost {
    border-left-color: var(--mud-palette-warning);
    background: rgba(var(--mud-palette-warning-rgb), .12);
}

.ff-pick-inflight.is-lost .mud-icon-root { color: var(--mud-palette-warning); }

/* Refused: the server said no, in its own words. */
.ff-pick-inflight.is-refused {
    border-left-color: var(--mud-palette-error);
    background: rgba(var(--mud-palette-error-rgb), .12);
}

.ff-pick-inflight.is-refused .mud-icon-root { color: var(--mud-palette-error); }

/* ---------------------------------------------------------------------------------------------
   The recommendation star, told apart from the buttons it sits beside

   "Then hit the star, no draft" was the third of the member's three taps and the only one that was
   never going to do anything: this element has never had a click handler. It reads as a control
   purely because of where it sits, in the row's action cell between the quick add and the select
   check, so this makes the difference visible at the pointer.

   Default cursor, and deliberately NO :hover and NO :active rule for this class anywhere in the
   sheet, because a state change under the pointer is exactly the affordance that says "press me".
   Nothing else moves: the colour and size stay on the base .ff-draft-recdot rule earlier in this
   file, and the action stays one tap to the right on the select check, untouched.

   The markup carries the other half, role="img" with aria-label="Recommended pick", so the badge
   announces itself as a picture and never as a button.
   --------------------------------------------------------------------------------------------- */

.ff-draft-recdot {
    cursor: default;
}

/* ---- end UX-1 ---- */
