/* ================= THE ALTERNATE UX — TASKS =================
   The context strip, toolbar, quick actions, view tabs, list, row, and task detail panel. The
   hierarchy is the point: a full-width summary across the top, the work itself in the middle,
   the one task being read on the left, utilities on the right. */

/* ---------- the context strip, across the whole page ----------
   A sibling of .a-main, laid out by this file alone. The three-column grid inside .a-main is
   shared with notes/calendar and its tracks are counted by altGridTracks() — a strip declared
   as a fourth child would land in an implicit track. */
.a-context{ flex:0 0 auto; min-width:0; padding:var(--a-3) var(--a-4) 0; }
/* The column is the width it is given — without min-width:0 a flex/grid child sizes by its
   content, so six stat cards once grew a 320px track to 347px and the page scrolled sideways
   for no visible reason. */
.a-left > *,.a-analytics,.a-actions-card{ min-width:0; max-width:100%; }
/* A column of sections: the header row that folds it away, then the regions, which run ACROSS —
   this card spent its first life in a 320px rail where six figures had to be drawn 3x2. */
/* Ground/edge/radius come from `.a-card` (alt-components.css, added by altRenderAnalytics()) —
   not restated here. Tightened to match team_board's card: --a-3 padding, --a-2 header-to-body
   gap (was --a-4/--a-3) — measured 195px → 162px at 1440 desktop. Only the outer padding moved;
   `.a-glance .a-stats`'s own tile gap is untouched. Pinned in alt-experience.test.js. */
.a-analytics{ display:flex; flex-direction:column; align-items:stretch; gap:var(--a-2);
  padding:var(--a-3); }
.a-analytics > .a-sec-h h2{ margin:0; font-family:inherit; }
/* Three regions across: what the list amounts to, how it splits by status, which tags are in
   play. The first region is sized to content (700px ceiling), not a fractional share — a share
   put the sixth tile on a second row at some widths and not others. 700, not 600, because at
   600 the six tiles wrap "Done this week" and grow 72px tall against the 62 every other page
   uses for this component. */
.a-glance{
  display:grid; min-width:0; align-items:start; gap:var(--a-4) var(--a-5);
  grid-template-columns:minmax(0,700px) minmax(0,1fr) minmax(0,1fr);
}
.a-glance-part{ min-width:0; display:flex; flex-direction:column; gap:var(--a-2); }
.a-glance-part > .a-sec-h{ margin:0; }
.alt-app .a-btn.a-sec-h-more{ flex:0 0 auto; }   /* the shared sm icon button (DS-21): the ••• beside a glance label is no smaller */
/* `.a-stats`/`.a-stat` moved to alt-components.css — drawn by Tasks, Notes, Calendar and Admin;
   a fourth copy here would be the drift that move was meant to stop. */
.a-glance .a-stats{ grid-template-columns:repeat(auto-fit, minmax(92px, 1fr)); gap:var(--a-2); }
/* 8px gap (not 21px) matches the OTHER two columns' own h3-to-tile rhythm, and matches
   team_board.html's `.at-part` for the same column shape (alt-team.css). The border removal is
   the same deliberate match — alt-team.css:278 already ships gap:--a-2/no top padding/no top
   border for this exact component, not a side effect of the padding change. Pinned
   value-for-value in tasks-glance-panel.test.js. */
.a-dist{
  flex:0 0 auto; min-width:0; display:flex; flex-direction:column; gap:var(--a-2);
}
.a-dist-chips{ display:flex; align-items:center; gap:7px; flex-wrap:wrap; }
/* TWO ROWS OF CHIPS, AND THEN A COUNT. A reader with nine statuses and eleven tags got five rows
   of pills above their own task list — the card stopped being a summary and became a legend. The
   overflow is a control, so nothing is hidden, only folded. */
.a-dist-chips.clipped{ max-height:60px; overflow:hidden; }
.a-dist-more{
  background:none; border:0; padding:2px 4px; cursor:pointer; border-radius:var(--a-r-sm);
  color:var(--a-blue-text); font:500 var(--a-fs-12)/var(--a-lh-tight) var(--a-body);
}
.a-dist-more:hover{ text-decoration:underline; }
.a-dist-more:focus-visible{ outline:2px solid var(--a-ring); outline-offset:1px; }
/* DISABLED WHILE A PAGE LOADS — "Loading…" on the Older foot, so a double press cannot read twice.
   The control never had a disabled state before; this one says "not pressable" without a colour. */
.a-dist-more:disabled{ opacity:.6; cursor:default; text-decoration:none; }
.a-sec-h{ margin-bottom:2px; }

/* ---------- THE STRIP WAS GROWING AS THE WINDOW SHRANK ----------

   MEASURED, AND IT IS THE WRONG WAY ROUND. #altContext came to 183px at 1920 and 273px at 1024,
   because three regions fell to two rows and then to three — and at 1024x768 that was most of the
   574px of chrome above a task list which computed to ZERO height, with the first row at y=849 in
   a 768px window. The page was a full screen of controls with no tasks on it.

   SO AT 1280 AND BELOW THE STRIP IS ONE ROW. The four figures the wireframe shows — Open, Due
   today, Overdue, This week — the heading, and "More". Starred, Done this week and both chip
   regions are behind that one control (altWireStripMore in JS/alt/alt-tasks.js), offering exactly
   the same filters the tiles and the chips do, so nothing is removed and one press still reaches
   any of them. 1280 is ALT_NARROW_MAX in that file; the two must stay the same number. */
@media (max-width:1280px){
  .a-context{ padding:var(--a-2) var(--a-4) 0; }
  .a-analytics{
    flex-direction:row; align-items:center; flex-wrap:nowrap;
    gap:var(--a-3); padding:var(--a-2) var(--a-3);
  }
  .a-analytics > .a-sec-h{ flex:0 0 auto; margin:0; }
  .a-analytics > .a-glance{ flex:1 1 auto; }
  /* The glance parts are drawn only into the shared top's breakdown now (altTasksStripDrop), which
     the reader opened on purpose, so no width hides them or their headings. */
  .a-glance .a-stats{ display:flex; gap:var(--a-2); }
  /* THE TILE LIES DOWN. A figure over a caption is 62px of a row that has to be one row; side by
     side it is 30, and the baseline they share is what keeps four of them reading as a set. */
  /* THE BASELINE IS RIGHT HERE and is not the defect it is in a fixed-height tile: this row is
     shrink-to-fit (`min-height:0`), so there is no spare box for the pair to sit at the top of,
     and it measures level. 3px rather than 5 only pays back the height the numeral's honest
     line box added above; the row is the 29px it has always been. */
  .a-stat{
    flex:1 1 0; flex-direction:row; align-items:baseline; gap:6px;
    min-height:0; padding:3px 9px;
  }
  .a-stat b{ font-size:var(--a-fs-16); }
  .a-stat span{ white-space:nowrap; overflow:hidden; text-overflow:ellipsis; }
  /* The two figures and the two chip regions the row cannot hold. `display:none` rather than
     visibility, so nothing here is left in the tab order pointing at something off screen. */
  .a-stat[data-stat="starred"],.a-stat[data-stat="donewk"]{ display:none; }
}
/* ABOVE THAT WIDTH THERE IS ROOM FOR ALL OF IT, so the one control that exists only to make room
   is not drawn — and not focusable either. */
@media (min-width:1281px){
  #altStripMore{ display:none; }
}
@media (max-width:820px){
  .a-context{ padding-left:var(--a-3); padding-right:var(--a-3); }
  /* On a phone the row is allowed to become two: there is no list beside it competing for the
     height, because below 1024 the regions stack and the page scrolls. */
  .a-analytics{ flex-wrap:wrap; }
  .a-glance .a-stats{ flex-wrap:wrap; }
  .a-glance .a-stats > .a-stat{ flex:1 1 120px; }
}

/* ---------- actions row ---------- */
.a-actions{ display:flex; align-items:center; gap:var(--a-2); flex-wrap:wrap; padding:var(--a-3);
  background:var(--a-panel); border:1px solid var(--a-line-soft); border-radius:var(--a-r-lg); }
.a-actions .a-search{ flex:1 1 240px; max-width:420px; }
/* ---------- ROW 2 — THE QUICK-FILTERS STRIP ("Refined Proposal 3", 2026-09-11 rebuild) ----------
   TASKS-TOOLBAR-CONTRACT.md's Row 2: a quiet inline label, never a button, then a fixed run of
   toggle chips — Starred / On a board / Not on a board by default. The customization feature
   (`settings.altUx.tasks.quickActions`) survives per the contract's addendum Decision 2, so
   `#altQuickActions` can still render up to 16 entries if the reader chose them; only the
   ARRANGEMENT changed, from a strip mixing filters/creates/navigation with a "Choose these…"
   button in the row itself, to a quiet secondary strip whose configuration moved into
   "Filters & more" (`#altMoreFiltersBtn`, Row 1). `#altQuickToggle`'s static markup — the
   "Hide/Show quick actions" button — is UNSTYLED here on purpose: it is contract-moved inside
   that same menu, so the button in `tasks.html` needs to come out of this row (reported to the
   integrator; nothing in this file targets it any more).

   IT WEARS THE TOOLBAR'S CLOTHES, LITERALLY THIS TIME. Row 1 and Row 2 are two sibling DOM
   nodes, not two children of one wrapper, so "one compact block, not three stacked bars" is
   built the same way `.a-actions`'s own card is — background, edge and radius — split across
   the two (soon three, with the footer) siblings: `#altControls` owns the top corners and no
   bottom edge, this row owns neither, and `.a-toolbar-hint` below owns the bottom corners.

   THIS COMMENT WAS WRONG ABOUT WHY IT WOULD READ AS ONE CARD, and the owner's screenshot proved
   it: three visible bands, full-width seams between them, the middle one reading a different
   tone from its neighbours. Measured on the rendered page (both themes, signed in): the three
   regions' `background-color` are IDENTICAL and the touching edges already carry NO border
   (`#altControls` has `border-bottom:0`, this rule has `border-top:0`) — so nothing here was
   drawing a line. What was: `#altControls`/`#altQuickStrip`/`.a-toolbar-hint` are siblings of
   `.a-centre`, and `.a-left,.a-centre,.a-right{display:flex;flex-direction:column;gap:var(--a-3)}`
   (alt-shell.css, shared, not this file's to touch) puts a flat 12px `gap` between EVERY child of
   that column — `#altTabs`→`#altControls` too, correctly, but also `#altControls`→`#altQuickStrip`
   and `#altQuickStrip`→`.a-toolbar-hint`, which this file never asked for. That 12px gap is
   `.a-centre`'s own transparent background showing through, full width, between two boxes whose
   independent left/right borders resume at each one's own top-left/top-right corner — which is
   exactly "a full-width horizontal rule" and exactly why the panel between two such gaps reads as
   sitting apart rather than differently coloured; the colour was never different.

   THE FIX IS A NEGATIVE MARGIN, NOT A NEW DIVIDER. `margin-top:calc(var(--a-3) * -1)` on this rule
   and on `.a-toolbar-hint` cancels exactly the parent's own `gap` for these two seams only — every
   OTHER gap in the column (above `#altControls`, below `.a-toolbar-hint`) is untouched, because
   only these two elements carry the override. `#altControls` needs no matching rule: it is not
   pulling itself up, its two followers are. The three regions now abut with zero space between
   them, so the "minimal separation between rows" the mock asks for comes from each row's own
   padding (`--a-2`/`--a-3` top and bottom, declared where each region sets it) rather than from a
   rule or a gap — spacing, not a seam, per the instruction this rewrite was written against. */
.a-quick-strip{
  display:flex; align-items:center; gap:var(--a-2); flex-wrap:wrap; flex:0 0 auto; min-width:0;
  background:var(--a-panel); border:1px solid var(--a-line-soft); border-top:0;
  /* CANCELS `.a-centre`'s OWN `gap:var(--a-3)` FOR THIS ONE SEAM. See the comment above this
     rule for why a gap, not a colour or a border, was what read as a horizontal rule here. */
  margin-top:calc(var(--a-3) * -1);
  padding:6px var(--a-4);   /* tightened with #altControls above, 2026-09-13 */
}
.a-quick-strip .a-actions{
  padding:0; background:none; border:0; border-radius:0; flex:1 1 auto; min-width:0;
}
/* THE LABEL IS TEXT, NOT A CONTROL — no button semantics, no focus stop, no hover. The bolt is
   decorative (the words already say "Quick filters"), so it is `aria-hidden` like every other
   glyph beside a label in this file. */
.a-qf-label{
  display:inline-flex; align-items:center; gap:5px; flex:0 0 auto; white-space:nowrap;
  font-size:var(--a-fs-11); font-weight:700; letter-spacing:.02em; color:var(--a-dim);
}
.a-qf-label > svg{ width:13px; height:13px; flex:0 0 auto; color:var(--a-gold); }
#altQuickActions{
  display:flex; align-items:center; gap:var(--a-2); flex-wrap:wrap; min-width:0;
}

/* The view row and the Focus strip are the shared page top: CSS/alt/alt-page-top.css (sys_design-system.md section 4d). This sheet keeps only what is Tasks's own. */

/* A split button: the face adds under Today, the caret beside it adds anywhere. Two ladder buttons, 2px apart (DS-21). */
.a-btn-split{ display:inline-flex; align-items:center; gap:var(--a-sp-2); }

/* Row 1: add, jump, arrange, filters. `#altControls` and the parked `#altStripTools` hold the same markup, so each rule names both.
   `.a-tb-row` is the line break; the row wraps rather than overlapping (markup contract: TASKS-TOOLBAR-CONTRACT.md). */
#altControls{
  background:var(--a-panel); border:1px solid var(--a-line-soft); border-bottom:0;
  border-radius:var(--a-r-lg) var(--a-r-lg) 0 0;
  /* The side gutter lines this card up with Work at a Glance above and the list below. */
  padding:var(--a-2) var(--a-4);
}
#altStripTools .a-tb-row,
#altControls .a-tb-row{ flex:1 1 100%; display:flex; align-items:center; gap:var(--a-2); flex-wrap:wrap; min-width:0; }

/* Hide/Show sits outside `#altToolbarBody`, the wrapper JS hides when folded (altApplyToolbarOpen());
   `flex:1 1 auto` keeps `.a-tabs-end` thrown to the right. */
#altStripTools .a-tb-fold,
#altControls .a-tb-fold{
  display:flex; align-items:center; gap:var(--a-2); flex-wrap:wrap; flex:1 1 auto; min-width:0;
}
/* THE COMPACT ROW HAS NO `.a-tb-row` CHILD to hang a rule on, so the class the render functions
   toggle on `#altControls` itself (see altRenderControlsWide()/altRenderControlsCompact()) is
   the signal instead. */
/* The compact tier wraps too: nowrap over non-shrinking children overflows onto the toggle. */
#altControls.a-tb-compact{ flex-wrap:wrap; padding:var(--a-2) var(--a-4); }
#altStripTools.a-tb-compact > *,
#altControls.a-tb-compact > *{ flex:0 0 auto; }
/* The fold wrapper is the one child that must grow, so it follows the blanket `flex:0 0 auto` above. */
/* AND THE WRAPPER TOO, or the fold is a single unbreakable line inside a container that is
   allowed to wrap — which is the overflow again, one level in. */
#altStripTools.a-tb-compact > .a-tb-fold,
#altControls.a-tb-compact > .a-tb-fold{ flex:1 1 auto; flex-wrap:wrap; gap:var(--a-1); }
#altStripTools.a-tb-compact .a-tabs-end,
#altControls.a-tb-compact .a-tabs-end{ margin-left:auto; gap:var(--a-1); }

/* Date chips: four equal filters in one group. */
.a-tb-dates{ display:inline-flex; align-items:center; gap:var(--a-1); flex:0 0 auto; min-width:0; }

/* The current chip and the open menu trigger are a surface, an edge and an elevation, so the state never rests on hue
   alone. `aria-current` marks the date chips (navigation), `aria-pressed` the toggles. */
#altControls .a-chip[aria-current="true"],
#altStripTools .a-chip[aria-current="true"]{
  background:var(--a-float); color:var(--a-blue-text); font-weight:700;
  border-color:var(--a-line-strong); box-shadow:var(--a-shadow-sm);
}

/* Every non-primary Row-1 button is a quiet ladder button (DS-22: a dropdown trigger is a button, not a pill). The
   third selector is `#altFilterChips` itself: it parks in `#altQuickStrip` when the bar folds, so rules scoped to
   `#altControls` would stop matching. `:not(.ghost)` leaves the fold toggle a plain disclosure; `:not(.on)` lets the
   lit wash win (these ids outrank `.a-btn.on`). */
#altFilterChips .a-btn:not(.primary):not(.ghost):not(.on),
#altControls .a-tb-row .a-btn:not(.primary):not(.ghost):not(.on),
#altControls.a-tb-compact .a-btn:not(.primary):not(.ghost):not(.on),
#altStripTools .a-tb-row .a-btn:not(.primary):not(.ghost):not(.on),
#altStripTools.a-tb-compact .a-btn:not(.primary):not(.ghost):not(.on){
  background:transparent; border-color:var(--a-line-soft); color:var(--a-dim);
}
#altFilterChips .a-btn:not(.primary):not(.ghost):hover,
#altControls .a-tb-row .a-btn:not(.primary):not(.ghost):hover,
#altControls.a-tb-compact .a-btn:not(.primary):not(.ghost):hover,
#altStripTools .a-tb-row .a-btn:not(.primary):not(.ghost):hover,
#altStripTools.a-tb-compact .a-btn:not(.primary):not(.ghost):hover{ background:var(--a-raised); color:var(--a-text); border-color:var(--a-line-strong); }
/* THE OPEN MENU IS THE SAME RAISED SIGNAL AS A PRESSED CHIP — the trigger IS the current
   selection while its menu is up, same reasoning as the date/quick-filter chips above. */
#altFilterChips .a-btn:not(.primary):not(.ghost)[aria-expanded="true"],
#altControls .a-tb-row .a-btn:not(.primary):not(.ghost)[aria-expanded="true"],
#altControls.a-tb-compact .a-btn:not(.primary):not(.ghost)[aria-expanded="true"],
#altStripTools .a-tb-row .a-btn:not(.primary):not(.ghost)[aria-expanded="true"],
#altStripTools.a-tb-compact .a-btn:not(.primary):not(.ghost)[aria-expanded="true"]{
  background:var(--a-float); color:var(--a-blue-text);
  border-color:var(--a-line-strong); box-shadow:var(--a-shadow-sm);
}

/* The master fold-all toggle (altFoldAllEl()) is an icon button: `.a-btn.icon` squares it on the ladder, so it states no height, width or radius, and no padding. */
#altFilterChips .a-btn.a-tasks-fold,
#altControls .a-btn.a-tasks-fold,
#altStripTools .a-btn.a-tasks-fold{ padding:0; }

@media (max-width:1499px){
  /* The value stays and the icon says which control it belongs to, so the words go first. */
  #altSortMenuBtn .a-lbl,#altMoreFiltersBtn .a-lbl{ display:none; }
}

/* At 1499 and below the row sheds words, then wraps; never overlaps. `flex:0 0 auto` pairs with the wrap: a shrinkable child
   would squash to a stub first. 1499 is ALT_TIGHT_MAX in JS/alt/alt-tasks.js. */
@media (max-width:1499px){
  #altControls .a-tb-row > .a-btn,
  #altControls .a-btn-split,
  #altControls .a-tabs-end,
  #altControls .a-tabs-end .a-btn,
  #altStripTools .a-tb-row > .a-btn,
  #altStripTools .a-btn-split,
  #altStripTools .a-tabs-end,
  #altStripTools .a-tabs-end .a-btn{ flex:0 0 auto; }
  #altControls .a-lbl,
  #altControls .a-val,
  #altStripTools .a-lbl,
  #altStripTools .a-val{ display:none; }
  #altControls .a-tabs-end,
  #altStripTools .a-tabs-end{ gap:var(--a-1); }
  /* The same, against the parked cluster: identical values, one decision restated for a second parent. */
  #altFilterChips,#altFilterChips .a-btn{ flex:0 0 auto; }
  #altFilterChips .a-lbl,#altFilterChips .a-val{ display:none; }
  #altFilterChips{ gap:var(--a-1); }
}

/* Row 2 wraps, not sheds: there are no words left to shed. */
@media (max-width:479px){
  .a-quick-strip{ row-gap:var(--a-1); }
}

/* ---------- THE FOOTER — ONE MUTED HINT LINE BELOW BOTH ROWS ----------
   New element, contract §"FOOTER": folds the old bare "Double click for full detail" line (still
   removed from `altRenderList()` by LANE JS, not duplicated) into one sentence with a leading
   icon. `tasks.html` has no host for this yet — reported to the integrator as
   `<div class="a-toolbar-hint" id="altToolbarHint">` between `#altQuickStrip` and `#altList`, the
   third and final sibling completing the one-block card Row 1/Row 2 start above — see the seam
   comment on `.a-quick-strip` for why this one also needs `margin-top` rather than relying on the
   siblings simply touching: `.a-centre{gap:var(--a-3)}` (alt-shell.css) puts the same 12px between
   THIS element and `#altQuickStrip` that it put between Row 1 and Row 2, and it reads exactly the
   same way — a full-width band of the page's own ground between two independently-bordered boxes
   — so it needs the identical cancellation, not a new one. This is meant to read as the card's
   LAST LINE, set off from Row 2 by spacing and its own smaller, quieter type — never a rule. */
.a-toolbar-hint{
  display:flex; align-items:center; gap:6px; flex:0 0 auto; min-width:0;
  background:var(--a-panel); border:1px solid var(--a-line-soft); border-top:0;
  border-radius:0 0 var(--a-r-lg) var(--a-r-lg);
  /* CANCELS `.a-centre`'s OWN `gap:var(--a-3)` FOR THIS SEAM TOO — same fix, same reason, as
     `.a-quick-strip`'s own `margin-top` above. */
  margin-top:calc(var(--a-3) * -1);
  padding:6px var(--a-4);   /* tightened with #altControls above, 2026-09-13 */
  font-size:var(--a-fs-11); color:var(--a-faint); line-height:var(--a-lh-ui);
}
.a-toolbar-hint > svg{ width:13px; height:13px; flex:0 0 auto; color:var(--a-faint); }

/* ---------- AN INLINE SVG WITH NO SIZE IS NOT AN ICON ----------
   altIcon() emits `<svg viewBox="0 0 24 24">` with no width and no height, so its rendered size
   is whatever CSS gives it — and where nothing did, it came out 0×0. Measured, not noticed: the
   plus on Add task, the group and sort icons, the magnifier in the filter box and EVERY group's
   disclosure chevron were all in the DOM, correct, and painting nothing at all. An icon set
   that is uniformly invisible looks exactly like a design that has no icons, which is why this
   survived several passes by eye.

   THE SHARED GAP WENT HOME. `.a-btn.icon.sm > svg` now lives with the primitive in
   CSS/alt/alt-components.css, so this file no longer answers for icon geometry — it had been
   answering for it, which is why the same Refresh control was 32×32 with a 15px glyph here and
   32×26 with a 12px glyph on the Calendar. What remains below is the two wrapped glyphs that
   carry their own deliberate size, plus the row rule above: a LABELLED `.a-btn.sm` raised to
   --a-ctl so the toolbar has one height and one middle. That row rule is this page's decision
   about its own row and is NOT a fact about icons — deleting it as "duplication" drops six
   labelled controls off that middle, which was measured before it was kept. */
.a-group-h .cv svg,.a-disc-h .cv svg{ width:var(--a-glyph); height:var(--a-glyph); }
.a-add-row .a-btn svg{ width:var(--a-glyph); height:var(--a-glyph); flex:0 0 auto; }

/* `.a-tabs` / `.a-tab` / `.a-tabs-end` MOVED TO alt-components.css. A tab strip has no page
   knowledge — no id in any of its selectors — and alt-okrs.css:37 already lists it among the
   primitives that "exist already and are EXTENDED here", which was only true on a page that
   happened to load THIS file. The admin console needs one too. */

/* ---------- the list ---------- */
/* THE LIST SCROLLS, NOT THE PAGE — so the tabs, the toolbar and the footer stay where the
   reader put them while the work moves under them. */
.a-list{ display:flex; flex-direction:column; flex:1 1 auto; min-height:0; overflow-y:auto; }
/* AND IT CAN NEVER BE NOTHING. `min-height:0` is what lets a flex child scroll instead of pushing
   its siblings off the page — and it is also what let this one be given zero: measured at
   1024x768, #altList computed to 0 and the first task row sat at y=849 in a 768px window. The
   regions above it are bounded now, each in its own rule above; this is the floor underneath all
   of them, so whatever is added to the chrome in future takes its space from the chrome and not
   from the reason the page exists. Roughly four rows. */
#altList{ min-height:200px; }
.a-group-h{
  display:flex; align-items:center; gap:var(--a-sp-8); height:var(--a-ctl); padding:0 var(--a-sp-6); cursor:pointer;
  background:none; border:none; border-radius:var(--a-r-sm); color:inherit; font:inherit; text-align:left; width:100%;
}
.a-group-h:hover{ background:var(--a-raised); }
.a-group-h .cv{ transition:transform var(--a-quick) var(--a-ease); color:var(--a-faint); display:flex; }
.a-group-h[aria-expanded="false"] .cv{ transform:rotate(-90deg); }
.a-group-h b, .a-group-h .lb{ font-size:var(--a-fs-13); font-weight:600; line-height:var(--a-lh-ui); }
.a-group-h .a-hint{ margin:0; font-size:var(--a-fs-11); color:var(--a-faint); }

/* THE OVERDUE HEADING IS RED, AND IT IS THE SAME RED AS EVERYTHING ELSE THAT MEANS LATE.

   Asked for by the product owner, 2026-09-25: "the overdue group should have a red header the
   same color as the overdue color within the chips at the top."

   `--a-red` IS THAT COLOUR, TAKEN FROM THE TOKEN RATHER THAN MATCHED BY EYE. The strip's
   Overdue tile is `.a-stat.warn b { color:var(--a-red) }` in alt-components.css, and a row's
   own late due date is `.a-row-due.late { color:var(--a-red) }` thirty lines below here. So the
   heading, the tile and the date now say "late" in one colour that changes in one place — and
   because it is a token it follows the theme, which a hex copied out of a screenshot would not.

   THE SELECTOR KEYS OFF `data-zone`, WHICH BOTH BUILDERS ALREADY SET. `altRenderList()`'s group
   builder and the drag-zone builder each do `wrap.dataset.zone = g.key` and each emit the label
   into `.lb`, so one rule covers both paths and neither needed a new class. `overdue` is an
   ALT_BUCKETS key, not a label, so this does not break if the wording ever changes.

   ONLY THE LABEL. The count chip beside it keeps the neutral treatment every other group's
   count has: a red pill next to a red word reads as an error badge rather than as a heading,
   and the owner asked for a red header rather than a red alarm. The chevron stays `--a-faint`
   for the same reason — it is a control affordance shared with every other group, and colouring
   it would say the CONTROL is the thing that is late. */
.a-group[data-zone="overdue"] > .a-group-h .lb{ color:var(--a-red); }
/* THE SAME CHIP AS EVERY OTHER LABEL ON THE ROW. It was a gold block with its own padding and
   its own margin, so one row in ten was taller than the rest and shouted louder than the status
   it sat beside. It is a fact about where the task came from, which is chip-sized. */
.a-note-line{
  display:inline-flex; align-items:center; gap:5px; padding:0 8px; height:20px;
  border-radius:var(--a-r-pill); border:1px solid var(--a-line-strong);
  background:none; color:var(--a-dim); font-size:var(--a-fs-11); font-weight:500;
  cursor:pointer; white-space:nowrap;
}
.a-note-line:hover{ border-color:var(--a-blue); color:var(--a-blue-text); }
.a-note-line:focus-visible{ outline:2px solid var(--a-ring); outline-offset:1px; }
/* The drawer's "Came from" notes (taskNoteBannerPaint(), surface 'drawer'). Styled here because tasks.html adopts
   CSS/task-editor-core.css only for the framed editor; the link is .a-dist-more's link-button, each name cut to one line. */
#dSource[data-surface="drawer"]{ display:flex; flex-wrap:wrap; align-items:center; gap:4px 6px; min-width:0; color:var(--a-dim); font:500 var(--a-fs-12)/var(--a-lh-ui) var(--a-body); }
#dSource[data-surface="drawer"] .source-note-ref-label{ flex:none; }
#dSource[data-surface="drawer"] .source-note-ref-item{ display:flex; align-items:center; gap:6px; min-width:9ch; max-width:100%; }
#dSource[data-surface="drawer"] .source-note-ref-item:not(:last-child)::after{ content:"\00b7"; flex:none; color:var(--a-dim); }
#dSource[data-surface="drawer"] .source-note-ref-link{ background:none; border:0; padding:0; min-width:0; max-width:100%; cursor:pointer; color:var(--a-blue-text); font:600 var(--a-fs-12)/var(--a-lh-ui) var(--a-body); text-decoration:underline; text-align:left; overflow:hidden; text-overflow:ellipsis; white-space:nowrap; }
#dSource[data-surface="drawer"] .source-note-ref-link:hover{ color:var(--a-text); }
#dSource[data-surface="drawer"] .source-note-ref-link:focus-visible{ outline:2px solid var(--a-ring); outline-offset:1px; }

/* ---------- THE ROW: THREE LINES, AND NEVER A FOURTH ----------

   WHAT A ROW HAS TO ANSWER. What is this · what is it about · where does it live and who is on
   it. A list of titles alone is a list of filenames — two tasks called "Follow up with Kate" are
   two different jobs, and the sentence underneath is what separates them.

   THREE IS THE CEILING, and it is a hard one: the title, one ellipsed line of the description,
   and the facts. A row that can become four lines is a list where no two rows are the same
   height, which is the thing that stops a list scanning — the defect the Notes list already had
   and was fixed for. Every line below is single-line by construction, not by hoping the content
   is short.

   THE CONTROLS ALIGN TO THE FIRST LINE, not to the middle of a variable-height row: the
   checkbox, the date, the avatar and the star belong to the title, and centring them meant they
   drifted down as a description appeared. */
.a-row{
  display:flex; align-items:flex-start; gap:10px; min-height:var(--a-row);
  padding:7px 10px 7px 8px;
  border:1px solid transparent; border-left:3px solid transparent; border-radius:var(--a-r);
  background:var(--a-panel); margin-bottom:var(--a-gap-row); cursor:pointer; position:relative;
}
/* 3px is the optical offset that lines a 19px control up with a 14px/1.35 first line. */
.a-row > .a-check,.a-row > .a-row-due,.a-row > .a-assign-badge,.a-row > .a-av,.a-row > .a-star,.a-row > .a-more{
  margin-top:3px;
}
.a-row:hover{ border-color:var(--a-line); background:var(--a-raised); }
/* ---------- A ROW ARRIVING BECAUSE THE READER NARROWED THE LIST ----------

   THE PRIMITIVE IS `.card.card-enter` IN CSS/components.css AND IT COULD NEVER REACH THIS PAGE.
   Nothing in the suite draws a `.card` — the rows are `.a-row` — so `altAnimateFilterOnce()` and
   `altApplyFilterEntrance()` in JS/alt/alt-tasks.js were arming a class that matched no rule.
   The feature existed, the class landed on the element, and not one pixel moved. That is the
   worst shape a defect can take, because everything about it looks finished.

   THE ANIMATION IS THE SHARED ONE, NOT A COPY OF IT. `@keyframes cardIn` is declared at the TOP
   LEVEL of CSS/components.css — verified at brace depth 0, so it is document-global rather than
   scoped to the `.card` rule it sits beside — and every suite page loads that file. So this rule
   names the existing keyframe and adds nothing: the 4px rise and the fade have one definition,
   and retuning them retunes both applications. A second `@keyframes cardIn` here would be one
   animation with two bodies to keep in step, which is the drift this file is careful about.

   `--dur-quick` AND `--ease-out`, which is what the classic rule uses and what the design system
   gives "a card arriving" (§2b). The per-item delay is NOT here: it is `motionStaggerMs(i)`,
   written inline by altApplyFilterEntrance(), because a capped stagger is arithmetic over the
   tokens and JS/core/motion.js is the only place timing is computed.

   IT RUNS ON A FILTER CHANGE AND NOWHERE ELSE. altRenderList() reads and clears the flag at the
   top before any early return, so a save, a boot, a poll or a re-render paints the rows where
   they already are. `both` fill so a row is at opacity 0 during its delay and stays where it
   lands.

   THE @media BLOCK IS NOT REDUNDANT, AND THIS IS THE ONE PLACE IN MY WORK WHERE THE TOKEN IS NOT
   ENOUGH. Zeroing `--dur-quick` would settle the DURATION, but the DELAY is an inline style
   written by script, and an inline style beats a media-query rule that is not `!important`.
   `motionStaggerMs()` already returns 0 under the preference, so today the two agree — this is
   what keeps them agreeing if that ever changes, and it is exactly why the classic rule carries
   the same pair. 1ms rather than 0s, matching `.card.card-enter`, which is also the contract
   altApplyFilterEntrance()'s own comment was written against. With `both` at 1ms the row still
   ends at opacity 1: the travel goes, the content never does. */
.a-row.card-enter{ animation:cardIn var(--dur-quick) var(--ease-out) both; }
@media (prefers-reduced-motion: reduce){
  .a-row.card-enter{ animation-duration:1ms !important; animation-delay:0ms !important; }
}
.a-row:focus-visible{ outline:2px solid var(--a-ring); outline-offset:1px; }
.a-row.sel{ border-color:var(--a-blue); background:var(--a-blue-soft); }
/* ---------- THE ROW THAT WAS JUST CREATED ----------
   A new task is placed by its DATE, so it often lands below the fold — altFlashRow() (alt-tasks.js)
   brings it to the reader with a single pulse, deliberately not a selected state (a row still
   ringed a minute later stops meaning "this is the one you just made"). Animates `box-shadow`,
   the one property `.a-row.sel` isn't already using, so it composes with selection instead of
   fighting it — a shadow rather than a border keeps the row's size so the list does not shift.
   `--dur-flash` is the shared token the team board reads too. */
@keyframes altRowNew{
  0%   { box-shadow:0 0 0 2px var(--a-blue); }
  70%  { box-shadow:0 0 0 2px var(--a-blue); }
  100% { box-shadow:0 0 0 2px transparent; }
}
.a-row.is-new{ animation:altRowNew var(--dur-flash) var(--ease-out) 1; }
/* Somebody who asked for less motion asked not to be animated at, NOT to be left hunting for
   the row they just made — so the pulse becomes a plain ring, and altApplyRowFlash()'s timer
   backstop is what takes it away again, because `animation:none` fires no animationend. */
@media (prefers-reduced-motion: reduce){
  .a-row.is-new{ animation:none; box-shadow:0 0 0 2px var(--a-blue); }
}
.a-row.done .a-row-t{ text-decoration:line-through; color:var(--a-faint); }
/* VIEW ONLY (2026-10-14, altRowEditable() in JS/alt/alt-tasks.js): the checkbox, the star and the
   due date still SHOW the task's state, as disabled buttons, and must not read as pressable.
   THE CONTROLS ARE DIMMED, NOT THE ROW (review m7). This used to be `.a-row.readonly{opacity:.85}`
   on the container, which multiplied with any dimmed control inside it (.85 x .55 = .47) and also
   greyed the title, the one thing a reader of a view-only row came for. The value is the Suite's
   one disabled look, `.a-input:disabled` in CSS/alt/alt-components.css. */
.a-row.readonly .a-check:disabled,
.a-row.readonly .a-star:disabled,
.a-row.readonly .a-row-due:disabled{ opacity:.55; cursor:default; }
/* The left edge carries the row's status colour — the wireframe's coloured rule. */
.a-row.k-active{ border-left-color:var(--a-blue); }
.a-row.k-blocked{ border-left-color:var(--red); }
.a-row.k-hold{ border-left-color:var(--yellow); }
.a-row.k-monitor{ border-left-color:var(--purple); }
.a-row.k-complete{ border-left-color:var(--green); }
.a-row.k-todo{ border-left-color:var(--a-line-strong); }
.a-check{
  width:19px; height:19px; flex:0 0 auto; border-radius:50%; cursor:pointer;
  border:2px solid var(--a-line-strong); background:transparent; padding:0;
  display:inline-flex; align-items:center; justify-content:center; color:transparent;
}
.a-check:hover:not(:disabled){ border-color:var(--a-green); }
.a-check.on{ background:var(--green); border-color:var(--green); color:var(--a-on-fill); }
.a-check:focus-visible{ outline:2px solid var(--a-ring); outline-offset:2px; }
.a-row-t{ flex:1 1 auto; min-width:0; font-size:var(--a-fs-13); font-weight:600; line-height:var(--a-lh-ui); overflow:hidden;
  text-overflow:ellipsis; white-space:nowrap; }
/* One line of what the task says. `min-width:0` is load-bearing on a flex child — without it the
   box is sized by its text and the ellipsis never happens. */
.a-row-desc{
  min-width:0; max-width:100%; font-size:var(--a-fs-12); line-height:var(--a-lh-ui); color:var(--a-dim);
  overflow:hidden; text-overflow:ellipsis; white-space:nowrap;
}
.a-row.done .a-row-desc{ color:var(--a-faint); }
/* NOWRAP, AND IT CLIPS. Wrapping would make this the fourth and fifth lines of the row. What
   does not fit is still on the task, one click away, and the order is fixed so what gets clipped
   is always the least important end. */
.a-row-meta{
  display:flex; align-items:center; gap:6px; flex-wrap:nowrap;
  min-width:0; max-width:100%; overflow:hidden;
}
.a-row-meta > *{ flex:0 0 auto; }
/* Its own box so COMPACT can keep the tags and drop the rest — see the density block in
   alt-shell.css. Compact is a density, not a smaller amount of truth about a task. */
.a-row-tags{ display:flex; align-items:center; gap:6px; min-width:0; overflow:hidden; }
.a-chip.quiet{ color:var(--a-dim); }
/* ---------- WHY THIS ROW IS IN WATCHING — THE ONE CHIP THAT IS A SENTENCE ----------
   Every other `.a-chip` on the row is a NOUN (a status, a tag, a board) — this one is a SENTENCE
   from a closed set of three (altWatchReasonLabel(), alt-tasks.js), so the usual 170px noun cap
   truncated away the word that carries its meaning. 212px clears the widest of the three labels
   across all ten application fonts (sys_design-system.md §1e). `flex:0 1 auto; min-width:0` lets
   it alone absorb row overflow (the strip is otherwise `nowrap`/`flex:0 0 auto`), turned into an
   ellipsis by `.a-chip .lb` instead of a hard cut — same shape as `.completed-row .cmeta` in
   CSS/components.css. No Compact exemption: unlike the repeat/reminder/comment chips, this one
   doesn't name an ongoing commitment. A 88px floor keeps the three labels tellable apart even
   while shrinking; below that the row's own clip takes over instead. */
.a-chip-watchreason{ max-width:212px; flex:0 1 auto; min-width:88px; }
/* The recurrence marker. `.a-chip` is inline-flex and gives a direct `<svg>` child no size
   (altIcon() emits a viewBox with no width/height) — sized here, 12px for this pill's scale. */
.a-chip-rep > svg{ width:var(--a-glyph-sm); height:var(--a-glyph-sm); flex:0 0 auto; }
/* Compact keeps this one marker (glyph only, label dropped) — a repeat says the row will come
   BACK, which a density cannot make less true, unlike a tag or a date. */
body.a-compact .a-row-meta > .a-chip-rep{ display:inline-flex; }
body.a-compact .a-chip-rep .l{ display:none; }
/* The reminder marker — same three rules as the repeat marker, for the same reason: a reminder
   says this row will email somebody, so Compact keeps the glyph and drops the word. */
.a-chip-rem > svg{ width:var(--a-glyph-sm); height:var(--a-glyph-sm); flex:0 0 auto; }
body.a-compact .a-row-meta > .a-chip-rem{ display:inline-flex; }
body.a-compact .a-chip-rem .l{ display:none; }
/* The comment count — same hook, one fewer moving part: it was always icon+bare-number
   (altIcon('comment') + the count, alt-tasks.js), so there's no label to hide in Compact. An
   unread reply is a fact about the task, not a decoration Compact may drop. */
.a-chip-cm > svg{ width:var(--a-glyph-sm); height:var(--a-glyph-sm); flex:0 0 auto; }
body.a-compact .a-row-meta > .a-chip-cm{ display:inline-flex; }
/* The envelope chip — "this task came from an email" (alt-tasks.js's altTaskRow()). Same sizing
   fix as its neighbours above. NOT exempted from Compact, unlike the other three: it states a
   fact about arrival, the same kind of fact as a tag or board name, which Compact already drops. */
.a-chip-eml > svg{ width:var(--a-glyph-sm); height:var(--a-glyph-sm); flex:0 0 auto; }
/* The ✉ Update pill: the shared purple chip (alt-components.css) for an emailed update with a suggestion waiting. Compact keeps it:
   it is a decision waiting for the reader, not a decoration. */
.a-chip-upd > svg{ width:var(--a-glyph-sm); height:var(--a-glyph-sm); flex:0 0 auto; }
body.a-compact .a-row-meta > .a-chip-upd{ display:inline-flex; }
/* Likely done: the same chip with the AI mark. The shared mark fold hides it on narrow widths; here it is the cue. A label only; the row checkbox completes. */
.a-chip-done .a-ai-mark{ display:inline-block; }
/* ---------- WHO ELSE IS ON THE TASK — THE COMFY ROW'S COLLABORATOR STACK ----------

   THE LOOK IS NOT DEFINED HERE AND MUST NOT BE. The circles, the overlap, the ring between them
   and the gray "add" variant all come from CSS/contributor-field.css — the sheet behind
   JS/components/contributor-field.js, the one field both team_board.html's "Contributors" and
   tasks.html's "Collaborators" already draw — which tasks.html loads. altRowCollabEl()
   (JS/alt/alt-tasks.js) emits `.contrib-avatars` and `.contrib-add` for exactly that reason, so
   the row and the editor cannot drift into two dialects of one picture. Everything below is the
   difference between a FORM ROW and a LIST ROW, and nothing else.

   `.a-row-collab` IS A MODIFIER, NOT A SECOND COMPONENT, which is also why it is written as a
   compound with `.contrib-avatars` on the element rather than as a standalone block.

   1. NO WRAPPING. `.contrib-avatars{flex-wrap:wrap}` is correct in a field that may grow onto a
      second line and wrong in a row where `.a-row-meta` is `nowrap` and three lines is the
      stated ceiling — a wrapped stack would silently become a fourth.
   2. NO SHRINKING, AND A CEILING ANYWAY. `.a-row-meta > *{flex:0 0 auto}` already covers the
      first; the `max-width` is the belt for a capped stack — four faces, a "+N" and the add
      circle is 6 × 18px overlapped at -6px = 78px, MEASURED in a browser at ten collaborators,
      which is why 96px is a ceiling that never actually binds rather than a clamp doing work —
      so this can never be what pushes the tags off the end of the line.
   3. A SMALL GAP TO THE CHIP BEFORE IT. `.a-row-meta{gap:6px}` already spaces it; the circles
      are taller than the chips either side, so a hair of optical breathing room keeps the
      status chip from reading as attached to the first face.

   THE RING IS ALREADY THE RIGHT COLOUR and is deliberately left alone: `.contrib-avatars .a-av`
   paints `box-shadow:0 0 0 2px var(--panel)`, and `--a-panel` IS `var(--panel)`
   (CSS/alt/alt-tokens.css) — the same token `.a-row` fills itself with. Restating it here would
   be a second declaration of one value.

   THE OVERFLOW CIRCLE borrows `.a-av.more` from the conversation header's participant stack
   (`.a-conv-who > .a-av.more`, CSS/alt/alt-conversation.css) — the same modifier for the same
   idea, re-scoped because that rule is bound to the header it was written in. Both themes come
   free: every value is a token, and `--a-raised`/`--a-dim` are both redefined under the dark
   palette with no hardcoded colour anywhere in this block. */
.a-row-collab.contrib-avatars{ flex-wrap:nowrap; max-width:96px; margin-left:1px; }
.a-row-collab .a-av.more{ background:var(--a-raised); color:var(--a-dim); font-weight:700; }
/* THE ADD CIRCLE IS A BUTTON AND MUST SHOW A FOCUS RING. CSS/contributor-field.css gives it a
   background, a border and a hover; it never needed a focus style there because it sits in a
   form where it is the only thing to tab to. On a row it is one of six tab stops, and the row's
   own `.a-star`/`.a-more` both carry this exact pair — reused verbatim rather than invented. */
.a-row-collab-add:focus-visible{ outline:2px solid var(--a-ring); outline-offset:1px; }
/* Same zero-size defect every bare glyph on this row has: CONTRIB_ADD_ICON ships explicit 13px
   width/height attributes, which suit the field's 24px circle and overflow an 18px `.a-av sm`.
   11px is the `.a-av sm` equivalent of the 13-in-24 the field already chose. */
.a-row-collab-add > svg{ width:11px; height:11px; flex:0 0 auto; }
.a-chip.okr{ border-color:var(--a-purple, var(--purple)); color:var(--a-text); font-weight:600; }
/* ---------- THE ACTION ZONE IS THE SAME WIDTH ON EVERY ROW ----------
   Each of these is a fixed track, not a box sized by its own content — a row with a date and an
   avatar once left its title 60px short of the row above it, so no two titles ended in the same
   place. `flex:0 0 <w>` on all four; the avatar's slot is drawn even unassigned, since a column
   that only sometimes exists moves everything beside it. */
/* The date is a <button> now but keeps its old track — the button reset (font/padding/border/
   background) is what stops titles starting in different places; it reads as text until pointed
   at, like `.a-star`/`.a-more` one track over. alt-notes.js/alt-team-board.js draw the same class
   as a <span>; the hover/focus rules are scoped to `button.a-row-due` so neither is affected. */
/* 84px, left-aligned: measured against the widest real string ("Wed, Sep 30" needs 73px) plus an
   11px slack for a wider glyph or fallback font — sizing to the exact measured width with nothing
   to spare has already ellipsed a date column once elsewhere. Left, not right, because right
   alignment put every date's edge in a different place and read as ragged in a fixed track;
   asked for directly: "make sure the left of the date all aligns left". */
.a-row-due{ flex:0 0 84px; font-size:var(--a-fs-12); color:var(--a-dim); white-space:nowrap;
  min-width:84px; text-align:left; overflow:hidden; text-overflow:ellipsis; }
button.a-row-due{ font-family:var(--a-body); font-size:var(--a-fs-12); line-height:var(--a-lh-ctl); font-variant-numeric:tabular-nums; padding:0; border:none; background:none;
  cursor:pointer; border-radius:var(--a-r-sm); }
button.a-row-due:hover:not(:disabled){ color:var(--a-blue-text); text-decoration:underline; }
button.a-row-due:focus-visible{ outline:2px solid var(--a-ring); outline-offset:1px; }
.a-row-due.late{ color:var(--a-red); font-weight:600; }
/* The AI-suggested date: the same pill, wearing the purple an AI suggestion already uses. Beats `.a-chip`'s own padding and 170px cap so the
   84px track and its left edge are unchanged; the label ellipses rather than widening the row. */
button.a-row-due.st-ai{ box-sizing:border-box; display:inline-flex; align-items:center; height:var(--a-chip-h); padding:0 6px;
  width:84px; max-width:84px; font-size:var(--a-fs-11); font-weight:500; border:1px solid var(--a-purple); border-radius:var(--a-r-pill);
  background:var(--a-purple-soft); color:var(--a-purple); }
/* The glyph is dropped in the row: a date label needs the whole 84px, and purple plus the title and aria-label carry the meaning. */
button.a-row-due.st-ai .a-ai-mark{ display:none; }
/* PENDING: the normal pill plus a small purple AI badge. Forced visible below 640px, where the shared `.a-ai-mark` fold would hide the only cue. */
button.a-row-due.ai-hint{ display:inline-flex; align-items:center; gap:5px; }
button.a-row-due.ai-hint .a-ai-mark{ display:inline-block; width:var(--a-glyph-xs); height:var(--a-glyph-xs); background-color:var(--a-purple); }
button.a-row-due.st-ai:hover:not(:disabled){ color:var(--a-purple); border-color:var(--a-purple); text-decoration:none; }
/* The date field the row's "Pick a date…" opens, drawn over the pill it came from. Fixed,
   because the list scrolls inside a box with overflow hidden and anything positioned inside a
   clipped ancestor is clipped with it. Its z-index is above the menu it replaces. */
.a-due-pick{
  position:fixed; z-index:520; height:var(--a-ctl-sm); padding:0 var(--a-sp-8);
  font-family:var(--a-body); font-size:var(--a-fs-ctl-sm); font-weight:400; line-height:var(--a-lh-ctl);
  color:var(--a-text); background:var(--a-field-bg); border:1px solid var(--a-ctl-edge);
  border-radius:var(--a-r-sm); box-shadow:var(--a-shadow-lg);
}
/* ---------- THE "ASSIGNED BY SOMEONE ELSE" BADGE — BETWEEN THE DATE AND THE AVATAR ----------
   Owner's own placement: "put the icon between the date and the assigned-to chip." A fixed
   track like its neighbours, so this badge's presence never shifts the avatar after it. Built by
   taskAssignedBadgeEl() (JS/components/task-row.js) — never returns null; `.none` is
   `visibility:hidden`, not removed, so the track and the columns after it never move. */
.a-row > .a-assign-badge{
  flex:0 0 20px; display:inline-flex; align-items:center; justify-content:center;
  color:var(--a-dim);
}
.a-assign-badge.none{ visibility:hidden; }
/* Same zero-size defect as `.a-more`/`.a-chip-rep`/`.a-chip-rem` svgs — 14px, between `.a-more`'s
   15 and a chip's 12, since this is a bare glyph with no pill around it. */
.a-assign-badge > svg{ width:14px; height:14px; flex:0 0 auto; }
.a-row > .a-av{ flex:0 0 24px; }
.a-av.none{ visibility:hidden; }
.a-star{ background:none; border:none; cursor:pointer; color:var(--a-line-strong); padding:0;
  display:inline-flex; align-items:center; flex:0 0 var(--a-ctl-sm); width:var(--a-ctl-sm); height:var(--a-ctl-sm); justify-content:center; border-radius:var(--a-r-sm); }
.a-star.on{ color:var(--a-gold); }
.a-star:hover:not(:disabled){ color:var(--a-gold); }
.a-star:focus-visible{ outline:2px solid var(--a-ring); outline-offset:1px; }
.a-more{ background:none; border:none; cursor:pointer; color:var(--a-faint); padding:0;
  display:inline-flex; align-items:center; flex:0 0 var(--a-ctl-sm); width:var(--a-ctl-sm); height:var(--a-ctl-sm); justify-content:center; border-radius:var(--a-r-sm); }
.a-more:hover{ color:var(--a-text); background:var(--a-raised); }
/* ---------- THE ADD ROW, DECLARED ONCE ----------
   `+ Add task` sat off-centre because two different components (the board's <button>, the task
   list's <div> wrapping two `.a-btn ghost sm`) wore this one class and it was declared twice,
   the second overriding both with asymmetric padding. One declaration now, `8px 12px`, symmetric
   vertically by construction. */
.a-add-row{
  display:flex; align-items:center; gap:var(--a-sp-8); height:var(--a-ctl); padding:0 var(--a-sp-12); margin-bottom:var(--a-gap-row);
  border:1px dashed var(--a-line); border-radius:var(--a-r); background:none; color:var(--a-faint);
  font-family:var(--a-body); font-size:var(--a-fs-13); font-weight:400; line-height:var(--a-lh-ctl); cursor:pointer; width:100%; text-align:left;
}
.a-add-row:hover{ border-color:var(--a-blue); color:var(--a-blue-text); }
.a-add-live{ display:flex; align-items:center; gap:var(--a-sp-8); margin-bottom:var(--a-gap-row); flex-wrap:wrap; }
.a-add-row.a-add-live{ height:auto; min-height:var(--a-ctl); padding-block:var(--a-sp-4); }   /* the open composer holds ladder-height fields, so it grows around them */
.a-add-live .a-input{ flex:1 1 auto; }   /* the edge goes accent on focus only (the shared :focus rule, DS-33) */
.a-list-foot{
  display:flex; align-items:center; gap:10px; padding:10px 4px 0; margin-top:4px;
  border-top:1px solid var(--a-line-soft); font-size:var(--a-fs-12); color:var(--a-faint);
}
.a-list-foot .a-bar{ flex:0 0 120px; }
/* THE "N/M today" TEXT, MADE INTO A BUTTON — altRenderListFoot() (JS/alt/alt-tasks.js). Reset
   to plain text in its row, not a chip. It reads the reader's body face with tabular figures
   (see the figures rule below), the same as every other count on the page. */
.a-list-foot-done{
  background:none; border:none; padding:0; margin:0; font-size:inherit; color:inherit;
  cursor:pointer; border-radius:var(--a-r-sm);
}
.a-list-foot-done:hover{ color:var(--a-text); text-decoration:underline; }
.a-list-foot-done:focus-visible{ outline:2px solid var(--a-ring); outline-offset:2px; }

/* ---------- the left column: one task, and the whole height of the page ----------
   The column is the panel now — it used to stack three cards and scroll as a column, so the
   drawer grew to its own content and nested a scrollbar inside a scrollbar. With one child, the
   panel fills the column and its BODY scrolls instead. By id, because `.a-left` is also the
   notes page's groups-and-list column, which is still a stack that scrolls together. */
#altLeft{ overflow:hidden; }
#altLeft > .a-drawer{ flex:1 1 auto; min-height:0; }
/* THE EMPTY PANE IS COMPACT WHEN THE REGIONS STACK — 2026-10-12. Below 1024 the details pane sits
   ABOVE the list rather than beside it, and since the owner ruled that only the reader closes it
   ("Any function to auto close should not auto close at all.") it now stays open on "Nothing
   selected" after a task leaves the list. At the full `.a-empty` padding that held pane was ~240px
   tall and pushed the first task row below the fold on a 420px phone. Only the EMPTY state, and
   only when stacked: a filled pane and every wider layout are untouched. Tokens, not values. */
@media (max-width:1023px){
  #altLeft .a-drawer-b > .a-empty{ padding:var(--a-3) var(--a-4); gap:var(--a-1); }
}

/* ---------- task details drawer ---------- */
.a-drawer{ display:flex; flex-direction:column; min-height:0; background:var(--a-panel);
  border:1px solid var(--a-line-soft); border-radius:var(--a-r-lg); overflow:hidden; }
.a-drawer-h{ display:flex; align-items:center; gap:8px; padding:10px 12px;
  border-bottom:1px solid var(--a-line-soft); background:var(--a-float); flex:0 0 auto; }
/* ---------- THE ACTIONS ROW SITS ABOVE THE TITLE ----------
   `.stack` rather than a change to `.a-drawer-h` itself — the EMPTY state's header is still one
   row, and turning the shared rule into a column would stack those two for no reason. The title
   keeps the panel's full width; six icon buttons sharing its line would ellipsis a long name. */
.a-drawer-h.stack{ flex-direction:column; align-items:stretch; gap:8px; }
.a-drawer-h-acts{ display:flex; align-items:center; gap:2px; }
.a-drawer-h-acts{ gap:var(--a-sp-2); }   /* glyphs are the shared 15px (DS-21) */
/* Two groups: star/complete/delete on the left, the watch pair and more/expand/close on the
   right, pushed apart by the right group's own `margin-left:auto` (replacing a now-removed empty
   spacer span). `#dWatchActions` is always emitted, even empty, so this holds either way. */
.a-drawer-h-acts > .ph-right{ margin-left:auto; }
/* The drawer's one status row under the title: the live-editing group first, then the save words. It takes no
   room until something in it shows. */
.a-drawer-status{ display:flex; align-items:center; gap:var(--a-2); min-width:0; }
.a-drawer-status:not(:has(> :not(:empty))){ display:none; }
.a-drawer-status > .save-status{
  min-width:0; margin:0; text-align:left; font-size:var(--a-fs-12); line-height:var(--a-lh-tight); color:var(--a-dim);
  overflow:hidden; text-overflow:ellipsis; white-space:nowrap;
}
.a-drawer-status > .save-status .proc{ overflow:hidden; text-overflow:ellipsis; max-width:100%; }
.a-drawer-status > .save-status:empty{ display:none; }
/* Restated: components.css's .cfg-status.ok/.err load first and tie on weight. */
.a-drawer-status > .save-status.ok{ color:var(--green-text); }
.a-drawer-status > .save-status.err{ color:var(--red-text); }
.a-drawer-status > .save-status.ok{ color:var(--green-text); }
.a-drawer-status > .save-status.err{ color:var(--red-text); }
/* Keyed off `aria-pressed`, not a `.on` class — state can't be visually true and semantically
   false, and `.a-btn.on` is the toolbar's solid-blue toggle, wrong for a star. Fills gold/green,
   the same colours the row's own star and completion already use. */
.a-drawer-h-acts #dStar[aria-pressed="true"]{ color:var(--a-gold); }
.a-drawer-h-acts #dComplete[aria-pressed="true"]{ color:var(--green); }
/* Delete is quiet until pointed at — `.a-btn.danger`'s red border (alt-components.css) would
   otherwise paint a permanent alarm in every task's header for no reason. */
.a-drawer-h-acts .a-btn.danger{ color:var(--a-faint); border-color:transparent; background:transparent; }
.a-drawer-h-acts .a-btn.danger:hover,
.a-drawer-h-acts .a-btn.danger:focus-visible{ color:var(--a-red); background:var(--a-red-soft); }
/* The empty state's header says what the panel is, so an empty column reads as a panel waiting
   rather than as something that failed to draw. */
.a-drawer-h-t{ flex:1 1 auto; min-width:0; font-family:var(--a-display); font-size:var(--a-fs-13);
  font-weight:600; color:var(--a-dim); overflow:hidden; text-overflow:ellipsis; white-space:nowrap; }
/* ---------- THEY ARE TABS, SO THEY LOOK LIKE TABS ----------
   A tab strip with a rule under it and the active tab sitting ON that rule says "there is more
   behind these", rather than reading as a segmented control. Padding matches the header above —
   fixing "the details button is too close to the edge" (3px of tray vs 12px of everything else). */
/* It scrolls sideways: measured at 390px, five of nine tabs sat past the strip's right edge with
   no way to reach them (`overflow-x:visible`, `scrollLeft` pinned, card `overflow-x:hidden`) —
   the strip is their only route in. Same answer the OKR drawer already gives (alt-okrs.css
   `.a-okr-drawer-h .a-tabs`): the scrollbar is hidden (a thin bar under tabs reads as a fault,
   not an affordance) and a mask fades the edge to signal "more this way" instead. `nowrap` stays,
   since a second row would move the card's body down and read as two groups of tabs; keyboard
   Tab still reaches every button and the strip scrolls to follow focus. */
.a-drawer-tabs{
  display:flex; gap:2px; padding:0 12px; flex:0 0 auto;
  background:var(--a-float); border-bottom:1px solid var(--a-line);
  flex-wrap:nowrap; overflow-x:auto; overscroll-behavior-x:contain; scrollbar-width:none;
}
.a-drawer-tabs::-webkit-scrollbar{ display:none; }
/* Without this the buttons shrink to fit instead of overflowing, and the labels truncate — the
   same width problem wearing different clothes. */
.a-drawer-tabs > button{ flex:0 0 auto; }
/* THE BUBBLE ON A TAB — PROMOTED OUT OF THIS FILE, 2026-10-10. It used to be one rule, scoped
   `.a-drawer-tabs .a-tab-dot`, worn by the comments count and by the B/N chips on "Where it
   lives" because they are the same signal in two places: this tab has something in it. Now
   that three more surfaces outside this strip want the same chip (a task editor, a board
   modal, an OKR surface, the Message Center), the rule is renamed AND unscoped —
   `.a-count-chip` in CSS/alt/alt-components.css's "chips and badges" section, picking up the
   name a sibling lane had already converged on for the same signal in the framed task editor
   (JS/features/task-editor-markup.js) before this rule existed anywhere to define it — one rule
   reaching every host that loads it, rather than a tab-strip rule a second caller would have
   had to either depend on this stylesheet for or re-derive. This strip needed no override once
   the rule left: its geometry (16px, `line-height:1`, the 6px gap after a label) was never
   actually about being inside a tab, only about sitting beside 13px text at a fixed button
   height, which is true of every host the chip now reaches. See that file for the colour
   source, the reserved-slot `.none` modifier and the 99+ cap. */
.a-drawer-tabs{
  padding-right:var(--a-5);
  -webkit-mask-image:linear-gradient(to right, #000 calc(100% - 28px), transparent);
  mask-image:linear-gradient(to right, #000 calc(100% - 28px), transparent);
}
@media print{
  .a-drawer-tabs{ -webkit-mask-image:none; mask-image:none; }
}
/* Panel tabs (DS-24): 34px, 13/600, 0 12px, a 2px underline in blue when selected. The drawer's tabs share the width equally while
   there is room and overflow the scroller when there is not (`min-width:max-content`). */
.a-drawer-tabs button{
  height:var(--a-tab-h); padding:0 var(--a-sp-12); border:0; border-bottom:2px solid transparent; background:none;
  color:var(--a-faint); font-family:var(--a-body); font-size:var(--a-fs-ctl); font-weight:var(--a-fw-ctl); line-height:var(--a-lh-ctl);
  cursor:pointer; white-space:nowrap; display:inline-flex; align-items:center; gap:7px;
}
.a-drawer-tabs button:hover{ color:var(--a-dim); }
.a-drawer-tabs button:focus-visible{ outline:var(--a-focus); outline-offset:var(--a-focus-inset); }
.a-drawer-tabs button[aria-selected="true"]{ color:var(--a-text); border-bottom-color:var(--a-blue); }
#altDrawerTabs .a-tab{ flex:1 1 0; min-width:max-content; justify-content:center; }
.a-drawer-b{ flex:1 1 auto; min-height:0; overflow:auto; padding:var(--a-3) 12px var(--a-4);
  display:flex; flex-direction:column; gap:var(--a-3); }
/* The open item's title field (DS-13): the one title box, display face 18px/600, 40px. A contenteditable single row that scrolls
   rather than clips, scrollbar hidden. */
.a-drawer-title{
  width:100%; height:var(--a-title-h); font-family:var(--a-display); font-size:var(--a-fs-18); font-weight:600; line-height:var(--a-lh-tight);
  background:var(--a-field-bg); border:1px solid var(--a-ctl-edge); border-radius:var(--a-r-sm);
  color:var(--a-text); padding:var(--a-sp-8) 10px;
  white-space:nowrap; overflow-x:auto; overflow-y:hidden; scrollbar-width:none;
}
.a-drawer-title:focus-visible{ outline:var(--a-focus); outline-offset:var(--a-focus-offset); }
.a-drawer-title::-webkit-scrollbar{ display:none; }
/* VIEW ONLY IN THE DRAWER (2026-10-14, altDrawerTaskEditable() in JS/alt/alt-drawer.js). The disabled
   Status and Due are the shared `.a-input:disabled`/`.a-select:disabled` (CSS/alt/alt-components.css);
   only the two contenteditable boxes are this file's own primitives, so their read-only look is here,
   with the board dialog's value (`.rich-text-field[contenteditable="false"]`, CSS/alt/alt-team.css). */
.a-drawer-title[contenteditable="false"],
.a-rte[contenteditable="false"]{ opacity:.65; cursor:default; }
.a-two{ display:grid; grid-template-columns:1fr 1fr; gap:10px; }
/* The drawer's Details fields are the task editors' field tier: `--a-field-h`, the same 32px as the framed editor and the board dialog at
   every density and width (`--a-ctl` is 28px compact, 34px on the phone). Scoped to `.a-two`, so the checklist/link inputs keep their own. */
#altDrawer .a-two .a-field > :is(.a-input, .a-select){ height:var(--a-field-h); }
#altDrawer .a-two .person-select-input{ min-height:var(--a-field-h); }
#altDrawer .contrib-field{ min-height:var(--a-field-h); }
.a-three{ display:grid; grid-template-columns:1fr 1fr 1fr; gap:10px; }
.a-disc{ border-top:1px solid var(--a-line-soft); padding-top:10px; }
.a-disc-h{
  display:flex; align-items:center; gap:var(--a-sp-8); width:100%; height:var(--a-ctl); padding:0 var(--a-sp-6); background:none;
  border:none; border-radius:var(--a-r-sm); color:var(--a-dim); font-family:var(--a-body); font-size:var(--a-fs-11); font-weight:700;
  line-height:var(--a-lh-tight); letter-spacing:.08em; text-transform:uppercase; cursor:pointer; text-align:left;
}
.a-disc-h:hover{ background:var(--a-raised); }
.a-disc-h .cv{ transition:transform var(--a-quick) var(--a-ease); display:flex; }
.a-disc-h[aria-expanded="false"] .cv{ transform:rotate(-90deg); }
.a-disc-h .sum{ margin-left:auto; text-transform:none; letter-spacing:0; font-weight:500;
  color:var(--a-dim); font-size:var(--a-fs-11); overflow:hidden; text-overflow:ellipsis; white-space:nowrap; max-width:55%; }
.a-disc-b{ display:flex; flex-direction:column; gap:10px; padding-bottom:4px; }
.a-disc[data-open="false"] .a-disc-b{ display:none; }

/* ---------- THE FOLLOW-UP ROW COLLAPSES WHEN IT HAS NOTHING TO SHOW ----------
   PRODUCT OWNER: "Remove the follow up email label. Just having the draft email follow up is
   sufficient." `#dFollowupField` can end up empty two ordinary ways (the card adopted its button
   onto a saved-message card, or no assistant is configured and `.ai-unavailable` hides it) — one
   `:has()` selector covers both without the drawer needing to be told which happened, same
   approach as `#followupField:has(...)` in CSS/task-editor-panel.css. */
#dFollowupField:not(:has(button:not(.ai-unavailable))){ display:none; }

/* ---------- THE DRAWER'S SCHEDULE MEETING ROW ----------
   `#dMeetingField` is a sibling of the follow-up row, drawn empty and filled by taskMeetingEditorMount() (JS/features/task-meeting-link.js).
   It is absent, not blank, until the dialog is admitted (no button, no row). The meetings made from the task follow as the quiet
   `.source-note-ref` rows the framed editor draws (an empty host is `hidden`, which the base layer's `[hidden]` rule hides); their rules live in task-editor-core.css, which an ordinary tasks.html load never
   adopts, so the drawer carries its own, mirroring the `#dSource[data-surface="drawer"]` block above with the drawer's tokens. */
#dMeetingField:not(:has(#tmlEditorBtn)){ display:none; }
/* `#dMeetingRows` is a pass-through host: while its rows are hidden it adds no flex item, so an empty row leaves no extra gap under the button. */
#dMeetingRows{ display:contents; }
#dMeetingField .tml-rows{ display:flex; flex-direction:column; gap:6px; }
#dMeetingField .source-note-ref{ display:flex; align-items:center; flex-wrap:wrap; gap:4px 6px; background:var(--a-blue-soft); border:1px solid var(--a-blue); border-radius:var(--a-r); padding:var(--a-2) var(--a-3); font-size:var(--a-fs-12); line-height:var(--a-lh-ui); color:var(--a-dim); }
#dMeetingField .source-note-ref-link{ background:none; border:0; padding:0; cursor:pointer; color:var(--a-blue-text); font:600 var(--a-fs-12)/var(--a-lh-ui) var(--a-body); text-decoration:underline; text-align:left; }
#dMeetingField .source-note-ref-link:hover{ color:var(--a-text); }
#dMeetingField .source-note-ref-link:focus-visible{ outline:2px solid var(--a-ring); outline-offset:1px; }
.a-rte{
  min-height:var(--a-rte-min); max-height:340px; overflow:auto; padding:var(--a-sp-8) 10px;
  background:var(--a-field-bg); border:1px solid var(--a-ctl-edge); border-radius:var(--a-r-sm);
  font-family:var(--a-body); font-size:var(--a-fs-13); line-height:var(--a-lh-body); color:var(--a-text);
}
.a-rte:focus{ border-color:var(--a-blue); }
.a-rte:focus-visible{ outline:var(--a-focus); outline-offset:var(--a-focus-offset); }
.a-drawer-f{ flex:0 0 auto; padding:8px 12px; border-top:1px solid var(--a-line-soft);
  display:flex; align-items:center; gap:8px; font-size:var(--a-fs-11); color:var(--a-faint); }

/* The repeat selector and its "i", on one line: the control
   takes the room, the affordance stays its own width, `.a-btn.icon.sm` lines up with the
   select's height and clears the 24px pointer floor. */
.a-recur-row{ display:flex; align-items:center; gap:6px; }
.a-recur-row .a-select{ flex:1 1 auto; min-width:0; }
.a-recur-row .a-btn{ flex:0 0 auto; color:var(--a-faint); }
.a-recur-row .a-btn:hover,
.a-recur-row .a-btn[aria-expanded="true"]{ color:var(--a-blue-text); background:var(--a-raised); }

/* A description bubble, not a menu and not a dialog — wears `.a-menu`'s float treatment with two
   differences: `position:fixed` (placed from the anchor's own rect; absolute would clip inside
   the drawer's scroller), and no authored z-index (openPopover() writes layerNextZ() inline,
   the only answer that knows what this opens on top of — the `.a-due-pick` finding repeated). */
.a-info-pop{
  /* `width`, not `max-width` — a fixed element with `width:auto` is shrink-to-fit against its
     STATIC position, which at 390px rendered this as a 110px column 568px tall; an explicit
     width is the same number at every viewport and every stage of placement. */
  position:fixed; width:min(320px, 92vw); padding:10px 12px;
  background:var(--a-float); border:1px solid var(--a-line-strong); border-radius:var(--a-r);
  box-shadow:var(--a-shadow);
  font-size:var(--a-fs-13); line-height:var(--a-lh-ui); color:var(--a-text);
}
.a-tagpick{ display:flex; flex-wrap:wrap; gap:5px; }
.a-tagpick .a-chip{ cursor:pointer; }
/* ONE ROW, the same dashed zone as the task editor's .attach-dropzone: the picker, then the limit. It wraps on a phone. */
.a-attach{ display:flex; flex-wrap:wrap; align-items:center; gap:4px 8px; padding:4px 10px; border:1.5px dashed var(--a-line); border-radius:var(--a-r); }
.a-attach .a-hint{ margin:0; }
.a-attach .a-hint::before{ content:"· "; }
/* The conversation is styled in alt-conversation.css, not here — this file declared
   `.a-comments`/`.a-comment` twice, disagreeing with itself, and notes.html inherited whichever
   copy won. One component, one home, prefixed `.alt-app` there. */

/* ---------- pieces the row and the drawer name ---------- */
.a-row-main{ flex:1 1 auto; min-width:0; display:flex; flex-direction:column; gap:3px; }
/* The title is a button and must not look like one — it SELECTS on a single click like the rest
   of the row and no longer opens anything on its own (see the row's `dblclick` listener in
   alt-tasks.js), so the old hover underline read as a link to somewhere else and fired on every
   row the pointer passed over. `.a-row:hover` above is the row's real affordance now. */
button.a-row-t{
  background:none; border:0; padding:0; margin:0; text-align:left; color:inherit;
  font-family:var(--a-body); font-size:var(--a-fs-13); font-weight:600; line-height:var(--a-lh-ui);
  cursor:pointer; width:100%;
}
button.a-row-t:focus-visible{ outline:2px solid var(--a-ring); outline-offset:2px; border-radius:var(--a-r-sm); }
.a-empty-a{ display:flex; gap:var(--a-2); justify-content:center; margin-top:12px; }
/* --a-blue-text, not --a-blue. The fill colour is for a shape; on a panel at 11px it measures
   4.05:1 against the surface behind it, under the 4.5 the design system requires for text.
   The text variant exists for exactly this and measures 5.93. */
.a-chip.unread{ border-color:var(--a-blue); color:var(--a-blue-text); font-weight:600; }
/* Plain background first — dropped, the attachment drop zone gives no drag-over feedback
   at all. --a-blue-soft is the same tint at a fixed alpha. */
.a-attach.over{ border-color:var(--a-blue); background:var(--a-blue-soft); background:color-mix(in srgb, var(--a-blue) 10%, transparent); }

/* ---------- a group in the list ---------- */
.a-group{ display:flex; flex-direction:column; gap:2px; }
.a-group + .a-group{ margin-top:6px; }
/* THE COMPLETED TAB'S "Older" FOOT — Show older and its "N of M loaded" (altOlderFoot(),
   JS/alt/alt-tasks.js; pagination Phase 2 wireframes). A NEW RULE BECAUSE A GROUP HAS NEVER HAD A
   FOOT ROW: the button and the hint are the existing .a-dist-more and .a-hint, and this only lays
   them on one line that WRAPS at phone width, the way the list foot already does. */
.a-group-foot{ display:flex; flex-wrap:wrap; align-items:center; gap:4px 10px; padding:6px 4px 2px; }
/* ---------- A GROUP WITH NOTHING IN IT IS A DROP TARGET AND NOTHING ELSE ----------
   "Overdue 0"/"No date 0" each drew a full header and affordance above a list with no room left
   — a group exists so there's somewhere to drop into, which only matters while dragging.
   `a-dragging-on` goes on the body at dragstart, before the first dragover can fire. */
.a-group.vacant{ display:none; }
body.a-dragging-on .a-group.vacant{ display:flex; }
body.a-dragging-on .a-group.vacant .a-group-h{ padding:5px 4px; color:var(--a-faint); }
body.a-dragging-on .a-group.vacant .a-group-h b,
body.a-dragging-on .a-group.vacant .a-group-h .lb{ font-size:var(--a-fs-12); font-weight:600; }
.a-tab.sm{ height:var(--a-ctl-sm); padding:0 9px; font-size:var(--a-fs-ctl-sm); }
.a-btn .n{ margin-left:5px; font:600 var(--a-fs-11)/var(--a-lh-ctl) var(--a-body); font-variant-numeric:tabular-nums; opacity:.8; }
/* An empty group or section says so, quietly, and is still a drop target. */
.a-col-empty{ padding:8px 6px; text-align:center; }
/* The composer row: the primary way to add on the left, the others behind one control. The box
   itself is declared once, above — this block is deliberately only the composer's additions. */
/* Hidden means unclickable — an invisible button inside a row that's now a whole hit target
   would be a trap. Hover and keyboard focus both reveal it and hand its clicks back together. */
.a-add-more{ opacity:0; pointer-events:none; transition:opacity var(--a-quick) var(--a-ease); }
.a-add-row:hover .a-add-more,.a-add-more:focus-visible{ opacity:1; pointer-events:auto; }
.a-add-live .a-input:first-child{ flex:1 1 200px; min-width:140px; }

/* ---------- the conversation, in this design's clothes ----------
   It was the canonical comment markup with none of this design's typography on it: a wall of
   body-sized text with no separation between one person's remark and the next. */
.a-conv{ display:flex; flex-direction:column; gap:var(--a-3); min-height:0; }
.a-conv .a-composer{
  margin-top:var(--a-2); padding-top:var(--a-3); border-top:1px solid var(--a-line-soft);
}

/* ---------- where it lives ----------
   The smallest thing on the tab, set at the smallest size. It was `.a-mono` at the inherited
   body size, which made three dates the loudest text on the panel. */
.a-meta{ display:flex; flex-direction:column; gap:3px; }
.a-meta-row{ display:flex; align-items:baseline; gap:8px; font-size:var(--a-fs-12); }
.a-meta-row .k{ flex:0 0 88px; color:var(--a-faint); }
.a-meta-row .v{
  flex:1 1 auto; min-width:0; color:var(--a-dim);
  font-size:var(--a-fs-11); font-variant-numeric:tabular-nums; overflow-wrap:anywhere;
}
@media (prefers-reduced-motion: no-preference){
  .a-analytics{ transition:outline-color var(--a-quick) var(--a-ease); }
}

/* ================= MOTION: THE MICRO RESPONSE =================
   Parity with the classic application's `.micro` primitive (CSS/components.css: transform on
   --ease-move, colour/opacity linear, all on --dur-micro) — the token is shared, the selectors
   are this page's, since nothing in JS/alt/ emits the `micro` class itself. `--dur-micro`
   (140ms), not `--a-quick`: past ~150ms a hover reads as lag, which is why it skipped the +200ms
   the travel durations took (sys_design-system.md §2b) — a disclosure or a hover-revealed
   control like `.a-add-more` is travel, not response, and keeps `--a-quick`. No layout property
   is in this list — only what actually changes. Reduced motion is answered at the token
   (alt-tokens.css zeroes `--dur-micro` on `.alt-app`), so no @media block is needed here. */
.a-row,
.a-check,
.a-note-line,
.a-add-row,
button.a-row-due,
.a-star,
.a-more,
.a-drawer-tabs button,
.a-drawer-h-acts .a-btn.danger{
  transition:background-color var(--dur-micro, 140ms) linear,
             border-color     var(--dur-micro, 140ms) linear,
             color            var(--dur-micro, 140ms) linear,
             opacity          var(--dur-micro, 140ms) linear;
}

/* ---------- THE SECOND FIGURE ON A TAB ----------
   The total is `.a-count-chip.mute` and the overdue count beside it `.a-count-chip.late`
   (CSS/alt/alt-components.css), a badge of its own so a total never turns red and implies "wrong"
   rather than "how much". The tab's aria-label carries the word "late" too, not colour alone.
   RED, NOT AMBER, since 2026-10-16 (owner: "change the late warning from yellow to red to match
   the mobile") -- the phone's .m-seg-late and every late due date (.a-row-due.late) are red. */

/* ---------- THE EMAILED TAB'S ATTENTION STATE ----------
   PRODUCT OWNER: "The system shall color the tab to 'Yellow' with the count so it will draw the
   user's attention to review the emails inbound that need to be accepted or rejected." `.attn`
   is added by `tabsHtml` (alt-tasks.js) only once the emailed count is known and > 0. Tokens,
   not a hardcoded yellow: `--a-amber`/`--a-amber-soft` are the same pair `.a-heavy`
   uses, since plain `--yellow` reads ~3.1:1 as text (below the AA floor). Not colour alone — the
   badge is `.a-count-chip.attn` (CSS/alt/alt-components.css) and the aria-label prepends "Needs review: ". */
.a-tab.attn,
.a-tab.attn:hover{ color:var(--a-amber); }

/* ================= THE HEAVY DAY ================= */
/* A day with more on it than the reader said they wanted, said where the day is — see
   `tasks.heavyDayThreshold`. Tokens, not a hardcoded amber: --a-amber/--a-amber-soft measure
   correctly in both themes where a mid-tone accent picked for one panel would not. Not colour
   alone — the ⚠ and the sentence carry it; the wash is a third signal, not the only one. */
.a-heavy{
  display:flex; align-items:flex-start; gap:6px;
  margin:2px 4px 6px; padding:6px 10px;
  font-size:var(--a-fs-12); line-height:var(--a-lh-ui); color:var(--a-amber);
  background:var(--a-amber-soft); border:1px solid var(--a-amber-soft);
  border-radius:var(--a-r);
}
.a-heavy .m{ flex:1 1 auto; min-width:0; }
/* The mark is decoration for a reader who can see it and noise for one who cannot — the
   sentence beside it already says "more than you asked for". */
.a-heavy .i{ flex:0 0 auto; }
/* AT THE HEAD OF THE LIST rather than inside a group, which is where it goes when the reader
   has grouped by something that has no Today in it. Same box, more room around it. */
.a-list > .a-heavy{ margin:0 0 8px; }

/* The double-click hint moved into `.a-toolbar-hint` above the list (TASKS-TOOLBAR-CONTRACT.md's
   footer) — the line inside the list (`.a-list > .a-list-hint`) is retired, not duplicated; LANE
   JS drops the matching element in the same change. */

/* ================= THE PRINTED TASK PACKET =================
   JS/features/task-print.js stages `.a-note-print.a-task-print` as a direct child of <body>
   and JS/features/note-print.js's notePrintNow() prints it. Everything below is @media print
   and has no effect on screen — the packet is `hidden` until printed.
   Not alt-notes.css's rules: that file dresses `.a-note-print` for notes.html, which tasks.html
   does not load. The two documents share a printer and a shape; the vocabulary (`a-np-*`) is
   per document — a third document would move these to alt-components.css instead. */
@media print{
  /* The application comes off — notePrintNow() also hides these; this is the belt to that pair
     of braces, catching anything the shell adds later that the JS list does not know about. */
  .alt-app .a-top,
  .alt-app .a-page,
  .alt-app .a-status,
  .alt-app .a-scrim,
  .alt-app .a-menu,
  .alt-app .a-info-pop,
  .alt-app .a-grip,
  .alt-app .a-vgrip,
  .alt-app .modal-overlay,
  .alt-app .session-boot{ display:none !important; }

  /* The shell is the viewport on screen and must not be on paper: a fixed height with hidden
     overflow prints exactly one screenful and throws the rest away. */
  .alt-app{
    height:auto; min-height:0; max-height:none; overflow:visible; display:block;
    background:#fff; color:#000;
  }

  /* Deliberately not var(--a-body) — the same decision alt-notes.css's `.a-note-print` rules
     (serving JS/features/note-print.js) and JS/features/board-export.js make; classic_tasks.html's
     own printNote() made the same call before it retired with that page. A packet is a document
     sent to other people, not carrying the sender's chosen face. */
  .alt-app .a-task-print{
    display:block; background:#fff; color:#000;
    font-family:-apple-system, BlinkMacSystemFont, "Segoe UI", Arial, sans-serif;
    font-size:11pt; line-height:var(--a-lh-ui);
  }
  .alt-app .a-task-print *{ box-sizing:border-box; }

  .alt-app .a-task-print .a-tp-title{ font-size:19pt; font-weight:700; margin:0 0 4pt; color:#000; }
  /* IS IT DONE, WHOSE IS IT, WHEN IS IT WANTED — the line somebody reads before anything else,
     so it is not small print. */
  .alt-app .a-task-print .a-tp-meta{ font-size:10pt; font-weight:600; color:#000; margin:0 0 6pt; }

  .alt-app .a-task-print .a-tp-facts{
    margin:0 0 8pt; padding:0; break-inside:avoid; page-break-inside:avoid;
  }
  .alt-app .a-task-print .a-tp-fact{ display:flex; gap:6pt; font-size:9pt; margin:0 0 1pt; }
  .alt-app .a-task-print .a-tp-fact dt{ flex:0 0 84pt; font-weight:700; color:#333; margin:0; }
  .alt-app .a-task-print .a-tp-fact dd{ flex:1 1 auto; min-width:0; margin:0; color:#000;
    overflow-wrap:anywhere; }

  .alt-app .a-task-print .a-tp-tags{ margin:0 0 6pt; }
  .alt-app .a-task-print .a-tp-tag{
    display:inline-block; font-size:9pt; color:#000;
    border:1px solid #999; border-radius:9pt; padding:1pt 6pt; margin:0 4pt 3pt 0;
  }
  /* The dot keeps the tag's own colour where a colour printer is in use, and the LABEL beside
     it is what carries the meaning everywhere else. */
  .alt-app .a-task-print .a-tp-dot{
    display:inline-block; width:6pt; height:6pt; border-radius:50%;
    border:1px solid #666; margin-right:4pt; vertical-align:baseline;
    -webkit-print-color-adjust:exact; print-color-adjust:exact;
  }

  .alt-app .a-task-print .a-tp-sec{ margin:14pt 0 0; }
  /* A SECTION SHORT ENOUGH TO FIT ON A PAGE SHOULD NOT BE SPLIT ACROSS TWO. The description
     and a note's pages are deliberately NOT in this class: a rule the browser cannot honour is
     answered by breaking wherever it likes, which is worse than asking for nothing. */
  .alt-app .a-task-print .a-tp-keep{ break-inside:avoid; page-break-inside:avoid; }
  .alt-app .a-task-print .a-tp-h{
    font-size:9pt; font-weight:700; text-transform:uppercase; letter-spacing:.4pt;
    color:#333; margin:0 0 5pt; padding-bottom:3pt; border-bottom:1px solid #999;
    break-after:avoid; page-break-after:avoid;
  }
  .alt-app .a-task-print .a-tp-summary{
    font-size:10pt; border-left:3px solid #999; padding:4pt 8pt; color:#000; margin:0;
  }
  .alt-app .a-task-print .a-tp-note{ font-size:8.5pt; color:#333; margin:4pt 0 0; }

  .alt-app .a-task-print .a-tp-body{ font-size:10pt; color:#000; }
  .alt-app .a-task-print .a-tp-body img{ max-width:100%; }
  .alt-app .a-task-print .a-tp-body ul,
  .alt-app .a-task-print .a-tp-body ol{ margin:4pt 0 4pt 18pt; padding:0; }
  .alt-app .a-task-print .a-tp-body a{ color:#000; text-decoration:underline; }
  .alt-app .a-task-print .a-tp-body table{ width:100%; border-collapse:collapse; font-size:9pt; }
  .alt-app .a-task-print .a-tp-body td,
  .alt-app .a-task-print .a-tp-body th{ border:1px solid #ccc; padding:2pt 4pt; text-align:left; }
  /* The editor's highlight classes survive sanitizeRichHtml() and therefore reach paper. On
     screen they are a wash of colour; here they are a rule under the phrase, because a pale
     background prints as nothing on most printers. */
  .alt-app .a-task-print .a-tp-body mark{ background:none; color:#000; border-bottom:1px solid #000; }

  .alt-app .a-task-print .a-tp-okr{ margin:0 0 5pt; break-inside:avoid; page-break-inside:avoid; }
  .alt-app .a-task-print .a-tp-okr-o{ font-size:11pt; font-weight:700; color:#000; margin:0; }
  .alt-app .a-task-print .a-tp-okr-m{ font-size:8.5pt; color:#333; margin:0; }
  .alt-app .a-task-print .a-tp-okr-k{ font-size:10pt; color:#000; margin:1pt 0 0; }

  .alt-app .a-task-print .a-tp-note-doc{ margin:0 0 10pt; }
  .alt-app .a-task-print .a-tp-page{ margin:0 0 8pt; }
  .alt-app .a-task-print .a-tp-page-h{ break-after:avoid; page-break-after:avoid; margin:0 0 3pt; }
  .alt-app .a-task-print .a-tp-page-h h3{ display:inline; font-size:12pt; font-weight:700; margin:0; color:#000; }
  .alt-app .a-task-print .a-tp-page-h h4{ display:inline; font-size:10.5pt; font-weight:700; margin:0; color:#000; }
  .alt-app .a-task-print .a-tp-page-d{ font-size:9pt; color:#333; margin-left:6pt; }

  .alt-app .a-task-print .a-tp-cat{ break-inside:avoid; page-break-inside:avoid; margin:0 0 6pt; }
  .alt-app .a-task-print .a-tp-cat-h{
    font-size:10pt; font-weight:700; margin:0 0 3pt; color:#000;
    break-after:avoid; page-break-after:avoid;
  }
  .alt-app .a-task-print .a-tp-list,
  .alt-app .a-task-print .a-tp-files{ list-style:none; margin:0; padding:0; }
  .alt-app .a-task-print .a-tp-files li{ font-size:10pt; color:#000; margin:0 0 2pt; }
  .alt-app .a-task-print .a-tp-item{
    display:flex; align-items:flex-start; gap:6pt; font-size:10pt; margin:0 0 2pt; color:#000;
    break-inside:avoid; page-break-inside:avoid;
  }
  .alt-app .a-task-print .a-tp-box{
    flex:0 0 auto; width:8pt; height:8pt; border:1px solid #000; border-radius:1pt; margin-top:2pt;
  }
  .alt-app .a-task-print .a-tp-item-body{ flex:1 1 auto; min-width:0; }
  .alt-app .a-task-print .a-tp-item-t{ display:block; }
  .alt-app .a-task-print .a-tp-item-d{ display:block; font-size:9pt; color:#333; margin-top:1pt; white-space:pre-wrap; }
  /* DONE IS A RULE THROUGH THE TEXT AND A FILLED BOX — two signals, neither of them colour. */
  .alt-app .a-task-print .a-tp-item.done .a-tp-box{
    background:#000; -webkit-print-color-adjust:exact; print-color-adjust:exact;
  }
  .alt-app .a-task-print .a-tp-item.done .a-tp-item-t{ text-decoration:line-through; }
  /* A flagged open checklist item: the words, boxed and bold, so it survives a monochrome printer (task-print.js). */
  .alt-app .a-task-print .a-tp-hi{ font-weight:700; font-size:8pt; letter-spacing:.04em; text-transform:uppercase;
    margin-right:4pt; border:1px solid #000; border-radius:2pt; padding:0 2pt; }
  .alt-app .a-task-print .a-tp-item.hi .a-tp-item-t{ font-weight:700; }

  .alt-app .a-task-print .a-tp-comment{ break-inside:avoid; page-break-inside:avoid; margin:0 0 6pt; }
  .alt-app .a-task-print .a-tp-comment-h{
    font-size:9pt; font-weight:700; color:#000; margin:0;
    break-after:avoid; page-break-after:avoid;
  }
  .alt-app .a-task-print .a-tp-comment-b{ font-size:10pt; color:#000; margin:1pt 0 0; }

  .alt-app .a-task-print .a-tp-foot{
    margin-top:16pt; padding-top:4pt; border-top:1px solid #ccc;
    font-size:8.5pt; color:#333;
  }
}

/* Quick actions in the filter row: the bolt names the group (the words are .a-sr), the + is a dashed door to Customize. */
#altControls .a-qf-label{ gap:0; }
#altControls .a-qf-label > svg{ width:14px; height:14px; }
.a-qf-add{ flex:0 0 auto; background:transparent; border-style:dashed; border-color:var(--a-line-soft); color:var(--a-faint); }
.a-qf-add:hover{ color:var(--a-text); border-color:var(--a-line-strong); }
#altPaneQuick .a-qf-add{ display:none; }
.a-qf-add svg{ width:12px; height:12px; flex:none; }
/* In the filter row the quick chips sit inline: the shared .a-actions card (border, padding, radius) is for the page's own bar. */
#altControls #altQuickActions{ padding:0; background:none; border:0; border-radius:0; gap:var(--a-1); flex-wrap:nowrap; }
#altListFoot > .a-toolbar-hint{ margin-left:auto; flex:0 1 auto; max-width:100%; }
/* The quick-actions row is the card's last line — folding (Hide, or Focused) folds the controls
   row and the hint either side of it and keeps this one, so Hide stays reachable rather than
   leaving an empty "Show >" bar (JS/alt/alt-tasks.js's altApplyToolbarOpen()). `.solo` is the
   whole card when #altControls is hidden: its own top edge, both radii, no seam-closing margin. */
.alt-app .a-quick-strip.solo{
  border-top:1px solid var(--a-line-soft);
  border-radius:var(--a-r-lg);
  margin-top:0;
}
/* The parked cluster is a row, not a wrapping one — it holds exactly two controls side by side;
   the STRIP around it is what wraps when the window runs out of room. */
.alt-app .a-quick-strip > #altFilterChips{ flex:0 0 auto; }

/* ---------- 12. THE FOLD KEEPS THE FIGURES ----------
   PRODUCT OWNER: "hiding the work at a glance shall always display the 4 tiles and hide should
   be on the RIGHT side of the 4 tiles." Folding used to hide the whole band body, costing the
   reader the counts along with the detail. `data-fold` already drew the right line — "Your
   work" carries none, "By status"/"By tag" both do, matching what the narrow-row block and
   alt-minimal.css already treat as detail — so the fold reuses that distinction. */
.a-glance.is-folded > .a-glance-part[data-fold]{ display:none; }

/* ---------- FOLDED IS A ONE-ROW LAYOUT, AND THE CONTROL SITS AFTER THE FIGURES ----------
   PRODUCT OWNER: "when you hide, the section should be one row instead of keeping its size and
   move the hide to the right most area of the section." Hiding the detail alone wasn't enough —
   `.a-analytics` is a flex column, so the header still sat stacked above the tiles. Folded and
   Minimalist share this block rather than drifting as two descriptions of one arrangement.
   `display:contents` on the header wrapper is load-bearing: `.a-panel-actions` is a grandchild
   of this row, and `order` can't move it past a sibling of its own parent — dissolving the
   wrapper promotes its children so the actions can be ordered last. */
body.a-minimal .a-analytics{
  flex-direction:row; align-items:center; flex-wrap:nowrap; gap:var(--a-3);
}
body.a-minimal .a-analytics > .a-sec-h{ display:contents; }
body.a-minimal .a-analytics > .a-sec-h > .a-w-fold{ order:0; flex:0 0 auto; }
body.a-minimal .a-analytics > .a-glance{ order:1; flex:1 1 auto; min-width:0; }
body.a-minimal .a-analytics > .a-sec-h > .a-panel-actions{ order:2; margin-left:auto; flex:0 0 auto; }

/* The figures are a row while folded, not the auto-fit grid the open card uses — a grid inside a
   single-row section would keep reserving tile-sized columns and give back none of the height. */

/* ================= NOTHING HERE YET — WHAT THE FIRST-RUN CARD REPLACES =================
   PRODUCT OWNER: "when a user has not tasks, create a notice in the main tasks area that there
   are no tasks, click here to add your first task ... It should hide all the panels by default
   when there is not tasks, and have a create your first task in the same style as 'Create
   organization'."
   The card itself is not drawn here — JS/components/first-run-card.js renders it, dressed by the
   same `.ofr-stage`/`.ofr-card` the Organization-creation state uses. This page owns only WHAT
   DISAPPEARS: the component toggles one body class and leaves the meaning to the host, the same
   contract team_board.html has with `ofr-board-hidden`. One rule hides the three panels inside
   #altMain (tab row, utilities rail, task drawer); #altContext (a sibling of #altMain) and
   #altBand need naming separately — #altBand goes too since neither the momentum count nor the
   Focused toggle survives having no tasks to focus. CSS only, never a JS-set `.hidden`, so this
   feature's markup is never mistaken by its real owner for an attribute it set itself. */
/* `body.alt-app.frc-first-run`, not `body.frc-first-run` — `.alt-app #altBand{display:flex}`
   above is (0,1,1), the same specificity a bare class selector would have, so without the extra
   class this would win only by being appended last, one reorder away from the band reappearing
   over the card. */
/* Scoped to this page's #altMain specifically — `#altMain` is shared by notes.html, calendar.html
   and team_board.html too, all bare `alt-app`, so an unscoped rule collapsed the notes card to
   0x0 the moment notes.html entered its own first-run state. Fixed in the selector (an id beats
   a class-only override) via `a-main-tasks`, the page class this page alone lacked. */
/* #altDidYouKnow goes too, per the same "centered middle screen" request — kept at first as the
   one thing worth saying on an empty page, until measurement showed it sits 255px tall above the
   card, pushing the card 214px below the viewport's middle. */
body.alt-app.frc-first-run #altBand,
body.alt-app.frc-first-run #altContext,
body.alt-app.frc-first-run #altDidYouKnow,
body.alt-app.frc-first-run #altMain.a-main-tasks{
  display:none;
}

/* The host costs nothing until the card is in it — `#altFirstRun` is an empty div, `display:none`
   on every ordinary load. It cannot disagree with the card: firstRunCardShow() sets
   `stage.hidden` and toggles the body class in the same statement pair. `flex:1 1 auto` on both
   so the card sits in the middle of the space #altMain gave up, not pinned under the topbar. */
#altFirstRun{ display:none; }
body.frc-first-run #altFirstRun{
  display:flex; flex:1 1 auto; min-height:0; min-width:0;
}
/* min-height:0 defeats `.ofr-stage`'s own min(60vh,520px) floor — right for a stage inside a
   page's flow, wrong for one that IS the page, where the floor made the stage taller than its
   496px slot and the card centred in the cap instead of the real space. */
body.frc-first-run #altFirstRun > .ofr-stage{ flex:1 1 auto; min-width:0; min-height:0; }

/* ---------- the calendar surface (List | Calendar) ----------
   alt-tasks.js unhides #altCalendar and sets `data-cal="month|week|day"` on #altMain; with the
   attribute absent nothing below applies and the page is the list. The grid itself is
   CSS/alt/alt-calendar-grid.css; this only places it, its No date tray and the drawer. */
#altMain[data-cal]:not([data-cal-split]) #altList,
#altMain[data-cal]:not([data-cal-split]) #altListFoot{ display:none; }
/* The grid keeps a 320px floor, so on a short window the column scrolls rather than clipping the grid, and the
   empty-week card centred in it, out of reach (.a-centre is overflow:hidden in alt-shell.css). */
#altMain[data-cal] > .a-centre{ overflow-y:auto; }
.a-cal{ display:flex; flex:1 1 auto; gap:var(--a-3); min-width:0; min-height:0; position:relative; }
/* The arrival status: the canonical working indicator (.proc, CSS/processing.css) centred across the grid and at its top, held on screen while the column scrolls, never taking a click.
   altTasksCalPaintArrival() fills and hides it; it is empty and hidden when nothing is loading. */
.a-cal-loading{ position:absolute; inset:0; z-index:2; pointer-events:none; }
.a-cal-loading .proc{
  padding:var(--a-3) var(--a-4); background:var(--a-panel); border:1px solid var(--a-line); border-radius:var(--a-r-lg);
  box-shadow:var(--a-shadow-lg); font:600 var(--a-fs-14)/var(--a-lh-tight) var(--a-display); color:var(--a-text); gap:var(--a-2);
  position:absolute; left:50%; transform:translateX(-50%); top:var(--a-3);   /* top is set by altTasksCalPlaceArrival() to the visible slice */
}
.a-cal-host{
  flex:1 1 auto; min-width:0; min-height:320px; overflow:auto;
  background:var(--a-panel); border:1px solid var(--a-line-soft); border-radius:var(--a-r-lg);
}
/* THE NO DATE TRAY: a dashed vertical tab along the right edge, a 240px list once opened. */
/* The calendar bar and add-to-day dialog, rehomed from the parked calendar sheet. */
/* Scoped to the Calendar surface (#altMain[data-cal]): the bar is drawn by altTasksCalRenderBar() in JS/alt/alt-tasks.js. */
#altMain[data-cal] .a-cal-bar{ display:flex; align-items:center; gap:var(--a-2); flex-wrap:wrap; min-width:0; }
.a-cal-fsgrp{ display:inline-flex; align-items:center; flex-wrap:nowrap; flex:none; gap:var(--a-2); }
/* The Free time and Completed toggles: one non-wrapping group of icon-only buttons, the pager arrows' size, 44px where the pointer is coarse. */
.a-cal-quick{ display:inline-flex; align-items:center; flex-wrap:nowrap; flex:none; gap:var(--a-2); }
@media (pointer:coarse){ .a-cal-quick .a-btn.icon.sm{ height:var(--a-touch); width:var(--a-touch); } }
.a-tcal-range{ font:600 var(--a-fs-14)/var(--a-lh-ui) var(--a-display); min-width:150px; color:var(--a-text); text-align:center; }
.a-cal-note{ min-width:0; }
.a-tcal-new{ width:min(460px, 92vw); height:auto; max-height:88vh; }
.a-tcal-new .a-drawer-b{ display:flex; flex-direction:column; gap:var(--a-3); }
.a-tcal-new .a-drawer-f{ flex-wrap:wrap; }
/* "Add to a note checklist" (JS/features/note-checklist-from-task.js; row menu and both task editors): the footer
   wraps like its siblings, and on a phone width the hint takes its own line so the primary button stays on screen. */
#ncftCard .a-drawer-f{ flex-wrap:wrap; }
#ncftCard #ncftFoot{ flex:1 1 auto; min-width:0; }
@media (max-width:480px){ #ncftCard #ncftFoot{ flex-basis:100%; } }
.a-tcal-new .a-drawer-h h2{ flex:1 1 auto; min-width:0; }
@media (max-width:639px){
  .a-tcal-range{ min-width:0; }
}
/* THE DRAWER OVER THE GRID, in every calendar view (Month, Week, Day, Day with tasks beside): it covers the left of
   the region and the grid keeps its full width. The List stays docked. Below 1024 the
   page is one column and the drawer takes the whole overlay. alt-tasks.js drops the left track
   from the grid in these cases, so the centre column keeps the whole row. */
#altMain[data-cal]{ position:relative; }
@keyframes a-cal-slide{ from{ opacity:0; transform:translateX(-12px); } }
@media (min-width:1024px){
  #altMain[data-cal] > #altLeft:not([hidden]){
    position:absolute; z-index:5; top:var(--a-3); bottom:var(--a-4); left:var(--a-4);
    width:min(var(--a-left, 320px), 92%); box-shadow:var(--a-shadow-lg); border-radius:var(--a-r-lg);
    background:var(--a-panel); animation:a-cal-slide var(--a-quick) var(--a-ease);
  }
  /* The drawer's own grip, on its right edge: the same #altGripLeft the list uses, lifted out of the grid. --a-left is the clamped width. */
  #altMain[data-cal] > #altGripLeft:not([aria-disabled="true"]):not([hidden]){
    display:block; position:absolute; z-index:6; top:var(--a-3); bottom:var(--a-4);
    left:calc(var(--a-4) + min(var(--a-left, 320px), 92%) - 4px); width:8px; margin:0;
  }
}
@media (max-width:1023px){
  #altMain[data-cal] > #altLeft:not([hidden]){
    position:absolute; z-index:5; inset:var(--a-3); max-height:none;
    box-shadow:var(--a-shadow-lg); border-radius:var(--a-r-lg); background:var(--a-panel);
    animation:a-cal-slide var(--a-quick) var(--a-ease);
  }
  .a-cal{ flex-direction:column; }
}
@media (prefers-reduced-motion: reduce){
  #altMain[data-cal] > #altLeft{ animation:none !important; }
}

/* ---------- full screen calendar: the bar and the grid fill the window ----------
   #altCalRegion (tasks.html) holds the bar and the grid; alt-tasks.js adds `.full` and sets data-calfull on #altMain.
   Unexpanded it is display:contents, so the pair lays out in .a-centre exactly as before. The layer launcher gives it its z-index;
   the task drawer (outside the region) is lifted over it from the left, below the bar, by the rules at the end of this block. */
.a-cal-region{ display:contents; }
@keyframes a-cal-full{ from{ opacity:0; transform:scale(.985); } }
.a-cal-region.full{
  display:flex; flex-direction:column; gap:var(--a-3); position:fixed; inset:0; box-sizing:border-box;
  height:100vh; height:100dvh; background:var(--a-bg); overflow:hidden;
  padding:max(var(--a-3), env(safe-area-inset-top, 0px)) max(var(--a-3), env(safe-area-inset-right, 0px))
          max(var(--a-3), env(safe-area-inset-bottom, 0px)) max(var(--a-3), env(safe-area-inset-left, 0px));
  animation:a-cal-full var(--a-quick) var(--a-ease);
}
.a-cal-region.full > .a-cal-bar{ flex:0 0 auto; max-height:40dvh; overflow-y:auto; }
.a-cal-region.full > .a-cal{ flex:1 1 auto; min-height:0; }
.a-cal-region.full .a-cal-host{ min-height:0; overscroll-behavior:contain; }
.a-cal-region.full .a-cal-host{ display:flex; flex-direction:column; }
.a-cal-region.full .a-cg{ display:flex; flex-direction:column; flex:1 0 auto; }
.a-cal-region.full .a-cg > .a-cg-week, .a-cal-region.full .a-cg > .a-cg-month{ flex:1 0 auto; }
.a-cal-region.full .a-cg-month{ grid-auto-rows:minmax(var(--cz-cell,112px),1fr); }
@media (max-width:900px){ .a-cal-region.full .a-cg-month{ grid-auto-rows:minmax(96px,1fr); } }
@media (max-width:640px){ .a-cal-region.full .a-cg-month{ grid-auto-rows:minmax(64px,1fr); } }
/* The drawer inside full screen: an overlay at the left from the bottom of the bar down, whatever the view or width. */
/* --a-calfs-top is the bar's measured bottom edge, set inline by altTasksCalFullMeasure(); this is its pre-measure default. */
#altMain[data-calfull]{ --a-calfs-top:56px; }
#altMain[data-calfull][data-cal] > #altLeft:not([hidden]){
  position:fixed; z-index:5; top:var(--a-calfs-top, 56px); bottom:max(var(--a-3), env(safe-area-inset-bottom, 0px));
  left:max(var(--a-3), env(safe-area-inset-left, 0px)); right:auto; max-height:none;
  width:min(var(--a-left, 320px), 92%); box-shadow:var(--a-shadow-lg); border-radius:var(--a-r-lg);
  background:var(--a-panel); animation:a-cal-slide var(--a-quick) var(--a-ease);
}
#altMain[data-calfull][data-cal] > #altGripLeft:not([aria-disabled="true"]):not([hidden]){
  display:block; position:fixed; z-index:186; top:var(--a-calfs-top, 56px); bottom:max(var(--a-3), env(safe-area-inset-bottom, 0px));
  left:calc(max(var(--a-3), env(safe-area-inset-left, 0px)) + min(var(--a-left, 320px), 92%) - 4px); width:8px; margin:0;
}
@media (max-width:1023px){
  #altMain[data-calfull][data-cal] > #altGripLeft{ display:none; }
  #altMain[data-calfull][data-cal] > #altLeft:not([hidden]){ width:auto; right:max(var(--a-3), env(safe-area-inset-right, 0px)); }
}
@media (prefers-reduced-motion: reduce){
  .a-cal-region.full{ animation:none; }
}

/* ---------- Day, Tasks beside: the region is two columns, the day and the page's own task column ----------
   altTasksCalPanePlace() (JS/alt/alt-tasks-calendar.js) moves #altTaskCol in after the grip and sets data-cal-split on #altMain.
   Not split, the column is display:contents, so the toolbar and list lay out in .a-centre exactly as before. */
.a-task-col{ display:contents; }
.a-cal-region.a-cal-split{
  display:grid; grid-template-rows:auto minmax(0,1fr); column-gap:0; row-gap:var(--a-3);
  grid-template-columns:minmax(360px,1fr) 8px minmax(340px, var(--cal-pane-w, 1fr));
  flex:1 1 auto; min-width:0; min-height:0;
}
.a-cal-region.full.a-cal-split{ display:grid; }
.a-cal-split > .a-cal-bar{ grid-column:1 / -1; grid-row:1; }
.a-cal-split > .a-cal{ grid-column:1; grid-row:2; min-height:0; }
.a-cal-split > .a-cal-split-grip{ grid-column:2; grid-row:2; width:auto; }
.a-cal-split > .a-task-col{
  grid-column:3; grid-row:2; display:flex; flex-direction:column; gap:var(--a-3);
  min-width:0; min-height:0; overflow:hidden;
}
/* Unexpanded, the centre column still scrolls and the split keeps a usable height; each track scrolls itself. */
.a-cal-region.a-cal-split:not(.full){ flex:1 0 auto; height:min(720px, calc(100dvh - 96px)); min-height:480px; }
.a-cal-split .a-cal-host{ min-height:0; }
/* The pane head (drawn by the list's renderer): "Tasks", the scope switch, the count. */
.a-tpane-h{ display:flex; align-items:center; gap:var(--a-2); flex-wrap:wrap; flex:0 0 auto; min-width:0; }
.a-tpane-h .a-cg-side-h{ margin:0; }
.a-tpane-h .a-count-chip{ margin-left:auto; }

/* The first-run card's own Customize button (altTasksFirstRunSync): the toolbar that normally holds it is hidden here. */
#altFirstRunCustomizeBtn{ display:flex; width:fit-content; margin:var(--a-3) auto 0; }
#altFirstRunCustomizeBtn .lbl{ display:inline; }   /* the card has the room the toolbar lacked, so the word stays at every width */

/* ---------- TASK SIZE: the list's rows read the one scale (alt-size-scale.css) ----------
   Scoped to #altList: `.a-row` is also drawn by pickers and the team board, which keep their own
   size. The id beats `button.a-row-t{ font:inherit }`, which otherwise pins the title to the
   browser default (16px). Comfortable height/padding follow the level; Compact is one line. */
#altList .a-row{ min-height:var(--z-row); padding-top:var(--z-pad); padding-bottom:var(--z-pad); }
body.a-compact #altList .a-row{ min-height:var(--z-row1); padding-top:3px; padding-bottom:3px; }
#altList .a-row .a-row-t{ font-size:var(--z-p); }
#altList .a-row .a-row-due, #altList .a-row button.a-row-due{ font-size:var(--z-s); }
#altList .a-row .a-row-desc{ font-size:var(--z-s); }
#altList .a-row .a-chip{ font-size:var(--z-c); }
#altList .a-group-h .lb{ font-size:var(--z-p); }
#altList .a-group-h .a-hint, #altList .a-group-h .n{ font-size:var(--z-c); }
/* #altListFoot is a sibling of #altList, so it cannot read data-z: it stays at the Default secondary size. */
#altListFoot{ font-size:var(--z-s,12px); }
/* From Detailed (3+) a Comfortable title and description wrap to --z-tl / --z-dl lines instead of
   an ellipsis; levels 1-2 and Compact keep the single ellipsed line. */
body:not(.a-compact) #altList:is([data-z="3"],[data-z="4"],[data-z="5"]) .a-row .a-row-t,
body:not(.a-compact) #altList:is([data-z="3"],[data-z="4"],[data-z="5"]) .a-row .a-row-desc{
  display:-webkit-box; -webkit-box-orient:vertical; white-space:normal; overflow:hidden;
  text-overflow:clip; -webkit-line-clamp:var(--z-tl);
}
body:not(.a-compact) #altList:is([data-z="3"],[data-z="4"],[data-z="5"]) .a-row .a-row-desc{
  -webkit-line-clamp:var(--z-dl);
}
/* Counts and the foot figure: the reader's body face, aligned by tabular figures. */
#altCompletedTodayBtn{ font-family:var(--a-body); font-variant-numeric:tabular-nums; }

/* ---------- THE FOCUS STRIP: what is Tasks's own ----------
   The strip's anatomy (row, figures, fold, quick run, tools, drop-down) is the shared CSS/alt/alt-page-top.css. What stays here is
   the content this page puts INTO its hosts: the quick cluster. */
/* This strip's row is 4px tall-padded (the list's top is 219 at 1440x900); the shared `.a-fs-row` is 6px. Named by id so it also holds on a phone, where the shared row narrows to 8px. */
#altAnalytics > #altStripRow{ padding:4px var(--a-3); }
#altStripQuick #altQuickActions{ display:flex; flex-wrap:nowrap; align-items:center; gap:6px; padding:0; margin:0; border:0; background:none; border-radius:0; }
#altContext{ max-width:100%; }

/* Below 1800 the strip stays one row: Organize ("Grouped by date · Smart") keeps its glyph and drops the words. The sentence is its aria-label. */
@media (max-width:1799px){
  #altStripTools #altOrganizeLink .a-lbl{ display:none; }
}
