@aiquants/daily-report 0.50.0 → 0.51.1

package/CHANGELOG.md

@@ -4,6 +4,56 @@ All notable changes to `@aiquants/daily-report` are documented here.
 
 ## Unreleased
 
+### Fixed
+
+- **低い窓でもビューが 0 に潰れない (WCAG 1.4.10)**: 0.51.0 で操作列の帯がどのポインターでも 56px (折り返せば 112px)、検索の行の帯が 56〜112px になったため、
+  400 % の拡大 (320 × 256 CSS px、マウス) ではホストの見出し 148px と 2 つの帯 224px が列を使い切り、List と DetailList のビューの高さが 0 になって行に届かなかった。
+  ビューの根要素は最小の高さとして List の行の枠の高さ 1 つ分 P (`VIEW_MIN_BLOCK_SIZE_CLASS_NAME` = 4⌈(52px + 2rem + max(4.75rem, 44px)) / 4⌉。根 16px で 160。
+  `round()` を持たない描画エンジンは切り上げる前の和) を持ち、ページの箱からビューの根要素までの箱 (ページの枠・内容の列・ビューのタブ・タブの中身。
+  `PAGE_FILL_COLUMN_CLASS_NAME`) は中身の最小 (帯とビューの最小の高さ) より小さくならない。帯とビューの最小の高さが収まらない窓では、ページの箱がホストの列から
+  はみ出し、ホストの列 (かその祖先) の縦のスクロールがページ (見出し・帯・ビュー) を動かす。ホストはその列を `overflow-y: auto` にする (はみ出しを切る列ではビューが
+  隠れる。README の「Host scroll for short windows」)。ふつうの高さの窓では何も変わらない (ビューは列の残りを埋め、ページはスクロールしない)。
+- **側面ペインの記事のスクロールの箱が潰れない (WCAG 1.4.10)**: 同じ 400 % の拡大で List のカードから開くモバイルのオーバーレイ (ダイアログ 256px) では、ペインの帯
+  (見出しの列とタブの並び) の下で記事のスクロールの箱が 12px まで潰れ、スクロールで見せたスターと既読のボタン (44px) の中心が箱の外に落ちて押せなかった。
+  記事と相関のタブの中身は最小の高さとして的の行 1 行 (`SIDE_PANE_SCROLL_PANEL_MIN_BLOCK_SIZE_CLASS_NAME` = `--spacing(2)` + T + 4px。根 16px で 56px) を持ち、
+  帯 (`SIDE_PANE_HEADER_BOX_CLASS_NAME`) は縮まず、タブの根は中身に基づく最小の高さを保つ。ペインが帯と的の行 1 行を入れきれない高さでは、見出しの列とタブの根を
+  包む中身の箱 (`SIDE_PANE_CONTENT_BOX_CLASS_NAME`) が縦にスクロールする (見出し・タブ・記事が一緒に動く。デスクトップでは細いバーにビューのスクロールバーの組の色、
+  オーバーレイでは面の縦のスクロール領域 `SWIPE_OVERLAY_SCROLL_AREA_STYLE` で、閉じるボタンは箱の下に残る)。ふつうの高さでは何も変わらない (スクロールの範囲が
+  無い)。オーバーレイの中身の箱はスクロール領域なので、見出しとタブの並びで始まった縦の 1 本指の動きも記事の上と同じくブラウザーのスクロールへ渡る (横の動きは
+  今まで通りスワイプ)。
+- **オーバーレイの知らせの置き場が空のとき場所を取らない**: 置き場には知らせの提供者の警告の領域 (見えない `role="alert"`) が常に入るので `:empty` で隠れず、
+  高さ 0 の項目として列の間隔 16px を 2 つ並べていた (320 × 256 では日報の箱から 16px を奪った)。置き場は見える知らせを持つ間だけ flex の箱になり、それ以外は
+  箱を作らない (`display: contents`。警告の領域は読み上げの木に残る)。どの高さでもオーバーレイの日報の箱が 16px 高くなる (閉じるボタンの位置は変わらない)。
+
+## 0.51.0 (2026-10-25)
+
+### Breaking
+
+- **的の大きさと配置がどのポインターでも同じ (マウス・トラックパッド・ペンでも 44 × 44 CSS px。WCAG 2.5.5)**: 0.50.0 で粗いポインター
+  (`(pointer: coarse)`) にだけ当てた的の箱と配置が、媒体条件の無い規則になる。操作ボタン (List のカード・DetailList の見出し・側面ペインのスター・既読・編集・削除、
+  コメントのゴミ箱) は 44px の丸い的、ビューと側面ペインのタブ・作成のボタン・検索の切り替えと入力欄と消去のボタン・コメントの入力欄と送信・削除の確認・オーバーレイと
+  誤りの知らせの閉じるボタン・2 つの再試行・編集フォームの `Button` と `Input`・添付のダウンロードと行のリンクは 44px 以上の箱 (`TARGET_CLASS_NAME`)、自動既読のスイッチは
+  中央の 44 × 44 の当たりを持つ。List のカードは 2 列の格子 (スターと既読はプレビューの右の 2 行目。行の枠の高さ P は根 16px で 160 のまま)、側面ペインの操作ボタンは件名の
+  下の自分の 44px の行、操作列の帯の部品は 48px で、操作列の並びは 4 + 48 + 4 = 56px (折り返せば 112px)、検索の行の 1 行目は 56px、ビューの幅が 320px 未満なら検索の
+  絞り込みの切り替えは自分の行へ折り返す。添付のタイルの最後の行は 48px (タイルは h + 80)、コメントの削除の枠と失敗の札は 44px の行。デスクトップのホストでは操作列の帯が
+  32px から 56px (検索の行があれば 64px から 112px) になってビューの上端が下がり、DetailList の見出し・コメント・側面ペイン・List のカードの並びと高さが変わる。
+  大きさの段の高さが的を下回る部品は高さのクラスを持たない (的の箱だけが大きさを決める。操作列の作成のボタンは `Button` の大きさの段を持たない)。
+- **的のトークンの名前から `COARSE_` を外した** (どれもパッケージの外へは公開しない): `COARSE_TARGET_CLASS_NAME` → `TARGET_CLASS_NAME`、
+  `COARSE_FIELD_TARGET_CLASS_NAME` → `FIELD_TARGET_CLASS_NAME`、`COARSE_TARGET_LINE_CLASS_NAME` → `TARGET_LINE_CLASS_NAME`、
+  `COARSE_LATTICE_TARGET_CLASS_NAME` → `LATTICE_TARGET_CLASS_NAME`、`SEARCH_FILTERS_TOGGLE_COARSE_WRAP_CLASS_NAME` → `SEARCH_FILTERS_TOGGLE_WRAP_CLASS_NAME`。
+  細かいポインターのための値は消した: コメントのゴミ箱の負の余白 `ACTION_BUTTON_INLINE_INSET_CLASS_NAME`、操作ボタンと区切りのトリガーと検索の欄と切り替えの 24px の高さ、
+  添付のダウンロードの `after:` の 24px の的、List のカードの折り返す flex の行と、目印と切り替えの 2 つの群を包んでいた操作の並び (カードの要素は 1 つ減る)、
+  切り替えの的の大きさの探りの高さ 0 (`TARGET_SIZE_PROBE_CLASS_NAME` は `h-[44px]`)。
+
+### Changed
+
+- **粗いポインターの媒体条件のまま残す規則は、欄の 16px の文字 (`pointer-coarse:text-base`) だけ**: 編集フォームの `Input` と `Textarea`・コメントと検索の
+  入力欄は、粗いポインターでは 16px (iOS の Safari のフォーカスでの拡大を防ぐ)、細かいポインターでは 14px のまま。Tailwind でクラスを作るホストが v4.1 以上を
+  要るのはこの規則のため (それより前の v4 では 16px の文字が作られない)。的の例外 (List のリサイズの取っ手とスクロールバー・ホストの絞り込みの選択の部品・
+  開発用の箱の再読み込みとキャッシュの消去・VirtualScroll のタップスクロールの円) は今のままで、2.5.5 は全体としては主張しない。
+
+## 0.50.0 (2026-10-24)
+
 ### Breaking
 
 - **`@aiquants/swipe-overlay` のピアの下限が、`useSwipeOverlayDialog`・`useOverlayPresence`・`SWIPE_OVERLAY_SCROLL_AREA_STYLE` を持つ版へ上がる**。

package/README.md

@@ -180,9 +180,9 @@ utilities are generated in one canonical build, define the `dark:` variant, and
 
 The host must also:
 
-- Build with Tailwind CSS v4.1 or later. The coarse-pointer targets (**Coarse pointers** in Selection and focus appearance) are
-  `pointer-coarse:` utilities, a variant Tailwind added in v4.1; an older v4 build generates none of them, so every target keeps its fine-pointer
-  size on a touch screen.
+- Build with Tailwind CSS v4.1 or later. The fields' 16 px text on touch screens (**Target size** in Selection and focus appearance) is a
+  `pointer-coarse:` utility, a variant Tailwind added in v4.1; an older v4 build does not generate it, so focusing a field zooms the page on a touch
+  browser.
 - Load the `tailwindcss-animate` plugin. The components use `animate-in` / `fade-in` / `zoom-in-95` / `slide-in-from-bottom-2` entrance animations
   (all under `motion-safe:`); without `@plugin "tailwindcss-animate"` those classes are not generated and the animations silently no-op.
 - Define the shadcn CSS variables themselves (`--background`, `--muted`, `--radius`, ...).
@@ -2205,7 +2205,7 @@ failed, and the filter row while it is open.
 Enter, Esc and the debounce wait while an IME composes.
 The filter row is inside the landmark, so its cells belong to the search for assistive technology and Tab goes from the field to the filter toggle and
 on into the cells; the landmark has no name (the screen has one search landmark), and the filter row's own name comes from the filter toggle.
-The row's first line is one 32 px lattice block whose 24 px controls stand at its bottom, so they sit G = 8 under the toolbar's bar and, while the
+The row's first line is one 56 px lattice block whose 48 px controls stand at its bottom, so they sit G = 8 under the toolbar's bar and, while the
 filter row is closed and no search failed, their bottom edge is G above the view's first surface; its second line holds the failure line.
 The band carries the toolbar's start inset G and the active view's end inset, so the field ends where the cards end in both views, and it stacks above
 the view, so a control's focus outline paints over the view's G strip (**Origin on the lattice** in
@@ -2228,7 +2228,7 @@ while the screen shows searching as the indicator and a failure on the failure l
 line wraps instead of truncating;
 it comes first in the field's description (before the syntax help), and the field is `aria-invalid` only for an invalid query (busy, unavailable and
 other failures are no input errors).
-The AND / OR toggle and the filter toggle share one look: a 24 px pill with 12 px semibold text, in the field face (OR; the closed filter row), whose
+The AND / OR toggle and the filter toggle share one look: a 48 px tall pill (the band's control height) with 12 px semibold text, in the field face (OR; the closed filter row), whose
 boundary comes from the text-field token as the field's does, or the filled face (AND; the open filter row), blue-800 under white text (dark: a light
 blue-300 fill under slate-950 text) and `Highlight` under `HighlightText` in forced colours (**Text fields** in [Selection and focus appearance](#selection-and-focus-appearance)).
 The faces differ only in colour, so a toggle that changes its face moves nothing. Each toggle stacks its current label and an invisible reserved label
@@ -2786,9 +2786,16 @@ view, and no script computes or writes a height.
   (`display: flex; flex-direction: column`) whose height is bounded — a definite height, or the growing item of a column with a minimum height, such
   as a `min-height: 100dvh` shell whose footer follows the content. The header that `renderHeader` returns and the page box are items of that
   container, and the page box takes the rest of it. Nothing is bound and no host variable is read.
-  Outside such a container the view has no height to fill: its size is contained (below), so its content cannot size it, and it is 0 px tall.
+  Outside such a container the view has only its minimum (below): its size is contained, so its content cannot size it.
+- **Host scroll for short windows**: a view never gets shorter than one List row slot P (**The view's minimum** below). When the container is shorter
+  than the toolbar band plus that minimum (a 400 % zoom, a short window), the page box grows past the container instead of the view collapsing, so the
+  container or one of its ancestors must scroll in the block axis (`overflow-y: auto`, not `hidden` or `clip`): the page scrolls (the host's header,
+  the bands and the view) and every row stays reachable (WCAG 1.4.10). A container that clips its overflow hides the view. At ordinary window sizes the
+  minimum is below the space left, the page box just fills the container and nothing scrolls.
 - **The fill chain**: every box from the page box down to a view's root — the page box, its centred width-capped wrapper, the view-mode tabs and the
-  active tab panel — fills the rest of its parent column (`flex: 1 1 0%; min-height: 0`) and declares no height. The wrapper's padding is the block
+  active tab panel — fills the rest of its parent column (`flex: 1 1 0%`), never gets smaller than its content's minimum (`min-height: auto`: the band
+  and the view's minimum) and declares no height. The view's root fills the tab panel at `flex: 1 1 0%` with the view's minimum as its
+  `min-height`. The wrapper's padding is the block
   quantum q of the device-pixel lattice at the top and the sides (4 px, 8 px at the odd multiples of 1/8; **Row slots on the lattice**) and none at
   the bottom, so the view's box ends exactly at the page's bottom edge.
   Between the wrapper's top and the active tab panel sits the band of the view-mode toolbar (the search row too, when configured), which does not
@@ -2797,9 +2804,28 @@ view, and no script computes or writes a height.
   box (the fill rule and the page surface, slate-50 / dark slate-950) and its centred column (the fill rule, at most `max-w-6xl`, q from the frame's
   top and side edges, starting on the lattice; the column carries q itself). So the page keeps its colour in both schemes while loading ends (a dark
   page never shows the light surface first) and the content does not move sideways between the screens.
+- **The view's minimum**: one List row slot P = 4 · ⌈(52 px + 2 rem + max(4.75 rem, 44 px)) / 4⌉ (**List slot P**; 160 px at a 16 px root), the
+  smallest whole row the views draw, as the root's `min-height` in the slot's own expression (an engine without `round()` takes the unrounded sum,
+  less than 4 px below P). A view of that height shows at least one whole List card; a DetailList row, taller than P, scrolls inside the view.
+- **The side pane's minimum and its own scroll**: the side pane (the desktop frame beside the List and the mobile overlay's pane box) stacks two
+  bands, the header column (business date and author) and the tab list, above its tab panel, a scroll box. The bands never shrink, and the tab panel
+  never gets shorter than one whole target row inside its own block padding: `--spacing(2)` (its top padding) + T (44 px) + 4 px (the focus-ring
+  reach at its bottom), 56 px (14 lattice units) at a 16 px root, so a 44 px control scrolled into view lies inside the box with its focus ring
+  (4 + 44 + 4 = 52 within the scroll padding). The tabs root keeps its content's minimum (the tab list plus that row). When the pane cannot hold the
+  bands plus that row (a 400 % zoom, a short window), the pane's content box (around the header column and the tabs, its clipping edges 4 px
+  outside its content) overflows and scrolls in the block axis, so the header, the tabs and the article move together. On the desktop its thin bar
+  wears the views' scroll-bar colours; in the overlay it is a vertical scroll area of the swipe overlay's panel (`touch-action: pan-y pinch-zoom`
+  and `overscroll-behavior-y: contain`) and the close button stays below it. It never scrolls sideways, so a horizontal move on the overlay's pane
+  is still the swipe.
+  At ordinary heights the content fits, there is no scroll range and nothing moves. The pane scrolls inside the view's box, so the host needs
+  nothing for it.
+- **The overlay's notice slot takes room only for the notice**: the slot of the error notice in the overlay, between the pane box and the close
+  button, always holds the provider's alert region (a visually hidden `role="alert"` element), so it is never empty. It generates no box
+  (`display: contents`) unless it holds the visible notice, so the column keeps one 16 px gap between the pane box and the close button; the alert
+  region, absolutely positioned, stays in the accessibility tree.
 - **The view's root contains its size** (the fill rule, `contain: size` and `overflow: clip`, its children in block flow): its box is sized as if it
   were empty, so what the view renders — a `VirtualScroll` given the measured height — never feeds back into the root's size, into the intrinsic size
-  of an ancestor (a host column with a minimum height does not grow) or into the document's scroll height. The clip keeps rows drawn for the previous
+  of an ancestor (a host column with a minimum height does not grow) or into the document's scroll height; only the view's minimum does. The clip keeps rows drawn for the previous
   height from painting outside the box during the one frame before the view renders the new height.
   The root's layout and paint are not contained: either would make the root the containing block of the mobile overlay, a fixed-position descendant,
   and as a flex item of its column the root could not be a relayout boundary anyway (Chromium makes no flex or grid item one, contained or not).
@@ -3461,13 +3487,12 @@ luminance by 0.026 in the light theme, and a `shadow-md` brings the ring down to
   `resolution: <dpr>dppx` of each of the twelve ratios with `calc(⌊2·dpr⌋px / dpr)`), and the lift reads it
   (`translate-y-[calc(-1*var(--aqdr-hover-lift))]`); every class is a literal, so a host's Tailwind build and the package's standalone stylesheet
   compile the same rules.
-- **List slot P**: the List card's content is sized in rem (its toggles in px under a coarse pointer), so the slot follows the page's root font size R
+- **List slot P**: the List card's content is sized in rem (its toggles in px), so the slot follows the page's root font size R
   and the toggles' target size T on the card's second line: P(R, T) = 4 · ⌈(2G + 2 × (1 + 15) (the card's border and padding) + 4 (spare) + 2R +
   max(4.75R, T)) / 4⌉ = 4 · ⌈(52 px + 2 rem + max(4.75 rem, T)) / 4⌉, the sum rounded up to the 4 px layout lattice, so every row top stays on the
-  lattice. T is 0 under a fine pointer (the toggles sit on the header line) and 44 under a coarse one (the toggles move beside the preview, **List
-  card** below); at a 16 px root 4.75 rem = 76 px is taller than 44, so P is 160 under either pointer.
-  R is read from the root element's computed style and T from the height of a hidden probe that is 44 px tall only under a coarse pointer
-  (`data-daily-report-target-size-probe`); one `ResizeObserver` reads both again whenever the hidden 1 rem probe
+  lattice. T is 44, the toggles beside the preview (**List card** below); at a 16 px root 4.75 rem = 76 px is taller than 44, so P is 160.
+  R is read from the root element's computed style and T from the height of a hidden 44 px probe (`data-daily-report-target-size-probe`, 0 until it
+  is laid out); one `ResizeObserver` reads both again whenever the hidden 1 rem probe
   (`data-daily-report-root-font-size-probe`) or the target probe changes size, and the List renders its `VirtualScroll` only once P is known
   (measured before the first paint).
   That one value sizes the row frames, `VirtualScroll`'s rows and the keyboard's row geometry, and when it changes the List keeps the first visible
@@ -3504,17 +3529,14 @@ luminance by 0.026 in the light theme, and a `shadow-md` brings the ring down to
   8 px (2 u), and 440 px (110 u) until it has measured one; the view applies a changed estimate only at rest, with the first visible report kept in
   place — also on the lattice at every ratio of the domain, so the unmeasured rows above the window move the rows below by whole device pixels. An image attachment tile is padded to q as well (**Tile** in
   [Attachment display](#attachment-display)), so the rows below an image grid stay on whole device pixels.
-- **List card**: a wrapping row of the primary button and the action row (markers and toggles), with the preview always on the next line. The primary
-  button takes the remaining width but never less than 96 px, enough for the business-date pill, and the action row keeps to the card's end; on a card
-  too narrow for both (a phone with a pinned host menu), the action row wraps under the button instead of squeezing it to nothing, and the card clips
-  the preview lines that no longer fit.
+- **List card**: a two-column grid (`minmax(0, 1fr)` and `auto`): the primary button and the markers share the header line, and the 44 px star and
+  read toggles sit in the second column of the second line, 4 px apart, beside the preview, so the header line stays 1.5 rem and P keeps 160 at a
+  16 px root. The primary button takes the first column but never less than 96 px, enough for the business-date pill, and the card clips what no
+  longer fits. The markers and the toggles are two groups that are the grid's own items; no element wraps them.
   The content of a full card is 6.75 rem: the pills' line 1.5 rem + 0.5 + three one-line preview paragraphs of 1.25 rem, 0.5 rem apart (24 + 8 + 3 ×
   20 + 2 × 8 = 108 px at a 16 px root), inside a 1 + 15 inset at the top and the bottom (the inset counts the border, below), so 1 + 15 + 6.75R + 15 +
   1 ≤ P − 2G with at least 4 px to spare at every root font size (140 ≤ 144 at 16 px).
-  Under a coarse pointer the card is a two-column grid (`minmax(0, 1fr)` and `auto`): the primary button and the markers share the header line, and the
-  44 px star and read toggles sit in the second column of the second line, 4 px apart, beside the preview, so the header line stays 1.5 rem and P keeps
-  its value at a 16 px root. Under a fine pointer the two groups that hold the markers and the toggles make no box (`display: contents`), so the card
-  lays out exactly as above.
+
 - **Forced colours**: the ring (a box shadow) disappears, so the row frame draws the selection itself: a 2 px solid `Highlight` outline at offset −8
   (−G), which puts the line in the ring's band, 0–2 px outside the surface. The frame's corner radius is the surface's radius plus G
   (`calc(var(--radius-2xl) + 8px)`, 24 at a 16 px root), so the line is concentric with the surface at every root font size.
@@ -3750,7 +3772,7 @@ luminance by 0.026 in the light theme, and a `shadow-md` brings the ring down to
   The frame height is not snapped to 4 px: snapping moves the frame's shape more than 0.01 away from 3 : 2 (196 → 132 gives |t / h − 3 / 2| = 0.0152,
   171 → 116 gives 0.026) and letterboxes a 3 : 2 image, which fills an unsnapped frame exactly.
   The tile around the frame is on the lattice anyway: its last line carries the pad δ(t) = ⌈h / q⌉ · q − h (0 to q − 1 px, q the block quantum of
-  **Row slots on the lattice**) as a bottom margin, so every tile is ⌈h / q⌉ · q + 48 px tall, every tile row top and every grid's height are
+  **Row slots on the lattice**) as a bottom margin, so every tile is ⌈h / q⌉ · q + 80 px tall, every tile row top and every grid's height are
   multiples of q, and what follows a grid stays on whole device pixels (**Tile** in [Attachment display](#attachment-display)).
   A bordered box counts its border in its inset, so that its content edge sits on the grid measured from the visible edge: border + padding is on the
   ladder — 16 for the card surfaces, the error panel, the sides of the error notice and the mobile overlay's close button (1 + 15), 8 for the form
@@ -3761,8 +3783,8 @@ luminance by 0.026 in the light theme, and a `shadow-md` brings the ring down to
   posted comment and the bordered pill (1 + 11); a 24 px pill has the same 12 px padding at its round ends. The tab bars are not in that tier: their 4
   px inset makes them concentric with their 8 px tabs (12 − 4 = 8).
   The only other exceptions are the visually hidden text (Tailwind's `sr-only`, and inside virtualized rows and for every attachment file name the
-  package's transparent 1 px box, which clips nothing and contains its own layout) and the 48 px the search field keeps free at its end for the
-  searching indicator and the clear button inside its box. `src/client/ui/spacing-ladder.guard.spec.ts` checks every class the package writes, that every
+  package's transparent 1 px box, which clips nothing and contains its own layout) and the 68 px the search field keeps free at its end for the
+  24 px searching indicator and the 44 px clear target inside its box. `src/client/ui/spacing-ladder.guard.spec.ts` checks every class the package writes, that every
   bordered box's border + padding is on the ladder or equals its corner, and that every 12 px-corner panel's inset is 12.
 - **Origin on the lattice**: the views' centred column (at most 72 rem, `max-w-6xl`, centred with `mx-auto`) starts at the centring offset rounded
   down to a multiple of the block quantum q (`ml-[max(0px,round(down,calc((100%-72rem)/2),var(--aqdr-lattice-block)))]`, on the column that carries q
@@ -3771,16 +3793,14 @@ luminance by 0.026 in the light theme, and a `shadow-md` brings the ring down to
   8 px at the odd multiples of 1/8), so every inline edge built on the origin — G, the ladder steps of 8 and 16, the card, the row frame — starts on a
   whole device pixel: on a 412 px phone at 2.625 a DetailList surface's left edge is 16 px in, at device pixel 42.
   Below the column's top inset the view-mode toolbar sits in its band, as tall as its content rounded up to q (the search row, when configured, is
-  inside the band: one more 32 px block), so the views start q + the band below the column's top — 4 + 32 = 36 px at the multiples of 1/4 and 8 + 32 =
-  40 px at the odd eighths, or 4 + 64 = 68 px and 8 + 64 = 72 px with the search row — on the lattice at every ratio.
-  The search row's 24 px controls stand at its bottom, so the gap above them is 32 − 24 = 8 = G from the toolbar's bar and their bottom edge is G
-  above the view's first surface. Under a coarse pointer the band's controls are 48 px (44 rounded up to 8), so the bar is 4 + 48 + 4 = 56 px (112 px
-  when it wraps) and the search row's first line 8 + 48 = 56 px: all multiples of 8, so every edge inside the band, not only its bottom, lands on a
-  whole device pixel at every ratio. The band stacks above the views (`relative z-[1]`), so the 4 px focus outline of a search control that ends at the
-  view's top paints over the view's G strip.
-  Measured in Chromium at 1280 × 800 and 1.125 under a 32 px host header: the toolbar, the view and the first row surface start at device pixels 45,
-  81 and 90 (with a 4 px inset and no band they started at 40.5, 76.5 and 85.5, half a device pixel off, and every row edge, ring and outline below
-  inherited the half pixel).
+  inside the band: one more 56 px block), so the views start q + the band below the column's top — 4 + 56 = 60 px at the multiples of 1/4 and 8 + 56 =
+  64 px at the odd eighths, or 4 + 112 = 116 px and 8 + 112 = 120 px with the search row — on the lattice at every ratio.
+  The band's controls are 48 px (44 rounded up to 8), so the bar is 4 + 48 + 4 = 56 px (112 px when it wraps) and the search row's first line
+  8 + 48 = 56 px, its controls at its bottom G = 8 under the bar and G above the view's first surface: all multiples of 8, so every edge inside the
+  band, not only its bottom, lands on a whole device pixel at every ratio. The band stacks above the views (`relative z-[1]`), so the 4 px focus
+  outline of a search control that ends at the view's top paints over the view's G strip.
+  At 1280 × 800 and 1.125 under a 32 px host header the toolbar, the view and the first row surface therefore start at device pixels 45, 108 and 117
+  (with a 4 px inset and no band they would start half a device pixel off, and every row edge, ring and outline below would inherit the half pixel).
   Still off the lattice at the odd eighths (measured, open): an inline edge at an odd multiple of 4 px inside a surface (the 12 px tier's insets, the
   4 px insets of the tab bars and of the toolbar inside its band); the focus outline's 4 px offset, 10.5 device pixels at 2.625, which no CSS length
   moves, since Chromium 148 rounds `outline-offset` down to whole CSS px (`calc(10px / 2.625)` gives 3 px); and the positions the browser chooses
@@ -3829,8 +3849,8 @@ luminance by 0.026 in the light theme, and a `shadow-md` brings the ring down to
 - **Tab bars are one segmented control**: the side pane's tabs and the view-mode toolbar share one geometry. The bar has a 12 px corner (`rounded-xl`)
   and a total inset of 4 px that counts its border (4 px padding without a border; 1 px border + 3 px padding with one), the same at the top and at
   the sides.
-  The tabs are 24 px tall with 12 px labels and an 8 px corner (`rounded-lg`), so both bars are 4 + 24 + 4 = 32 px tall and every tab is concentric
-  with its bar: 12 − 4 = 8. Because xl − lg = 4 equals the inset both in Tailwind's scale and in a host `--radius` scale (lg = `--radius`, xl =
+  The tabs are 44 px tall (the target T; 48 px in the toolbar's band) with 12 px labels and an 8 px corner (`rounded-lg`), so the side pane's bar is
+  4 + 44 + 4 = 52 px and the toolbar's 4 + 48 + 4 = 56 px tall, and every tab is concentric with its bar: 12 − 4 = 8. Because xl − lg = 4 equals the inset both in Tailwind's scale and in a host `--radius` scale (lg = `--radius`, xl =
   `--radius` + 4 px), the pair stays concentric for any host radius; the toolbar's children at its end corners (the create button, the development
   box) are `rounded-lg` too.
 - **View-mode toolbar** (`DailyReportResolvedContent`, above every view): its band carries the insets, so the toolbar and the search row share them:
@@ -3885,57 +3905,58 @@ luminance by 0.026 in the light theme, and a `shadow-md` brings the ring down to
   refuses one without a registered surface, and measures each against its surfaces. The quiet text (section labels, metadata, placeholders, the empty
   view, inactive tabs) is one token, `--aqdr-text-quiet` (light `oklch(44% 0.046 257.417)`, dark `oklch(77% 0.040 256.788)`: slate-500's and
   slate-400's hue and chroma), whose lightness `src/client/ui/aaa-quiet-text.spec.ts` solves from the surfaces it sits on (light 7.06–7.73, dark
-  7.07–9.75). A source badge's colours are the host's (**External Source Badge Configuration**). Under a fine pointer targets stay at WCAG 2.5.8's
-  24 px, except the List's resize handle with its 10 px hit area and the 8 px scroll bar beside it (**Side pane** above); under a coarse pointer they
-  reach 2.5.5's 44 px (**Coarse pointers** below), so 2.5.5 is not claimed overall.
+  7.07–9.75). A source badge's colours are the host's (**External Source Badge Configuration**). Targets reach WCAG 2.5.5's 44 px under every pointer
+  (**Target size** below), except the List's resize handle with its 10 px hit area and the 8 px scroll bar beside it (**Side pane** above) and the
+  other exceptions listed there, so 2.5.5 is not claimed overall.
 - **WCAG 2.2 AAA beyond contrast**: met are 1.4.9 (no images of text), 2.1.3 (every function by the keyboard, the List splitter's arrow keys
   included), 2.2.3 (nothing on a timer; **The built-in notice**), 2.3.2 (no flashes), 2.3.3 (motion follows `prefers-reduced-motion`), 2.4.8 (the page
   and the report headings tell where the viewer is), 2.4.9 (links name their purpose), 2.4.10 (sections carry headings), 2.4.12 and 2.4.13 (the focus
   is never obscured, and its outline is 2 px at 3:1), 3.1.3, 3.1.4 (abbreviated source badges, **External Source Badge Configuration**), 3.2.5 and
   3.3.6. Not met, by decision: 2.2.4 (Interruptions): live updates (SSE) apply as they arrive, with no pause, and
-  the scroll anchoring keeps the rows on screen in place. Not met at AA: 2.5.8 for the List's resize handle and the scroll bar beside it (**Side pane** above): larger hit areas for the handle and the
-  bar wait for the same layout pass as 2.5.5 under a fine pointer. Met under a coarse pointer only: 2.5.5 (44 px targets; **Coarse pointers** below).
-  Not claimed yet: 2.5.5 under a fine pointer, 1.4.8 (a line measure and the List preview's
+  the scroll anchoring keeps the rows on screen in place. Not met at AA: 2.5.8 for the List's resize handle and the scroll bar beside it (**Side pane**
+  above), which keep their thin hit areas. Not claimed overall: 2.5.5, whose 44 px every other target of the package meets under every pointer
+  (**Target size** below), the exceptions listed there aside.
+  Not claimed yet: 1.4.8 (a line measure and the List preview's
   leading) and 3.3.5 (a help control for the search syntax), which need a layout pass, and 3.1.6 (readings of names), which needs readings from the
   host's directory. 2.2.5 (Re-authenticating) is met with the host: at a session end the package pauses without reloading and keeps every draft, the
   open edit form, the selection, the search and the scroll in memory; the host lets the viewer sign in again without leaving the page and advances
   `sessionEpoch`, and the package resumes and sends nothing again by itself ([Client wiring](#client-wiring)). 2.2.6 (Timeouts) is the host's: the
   package keeps unsent work only in the open tab's memory until it is closed, and the host states how long a session lasts and what ends it. The floating tap-scroll circle hides while the view root carries `data-daily-report-keyboard-focus` (through the class both views pass in
   `VirtualScroll`'s tap-scroll circle options).
-- **Coarse pointers (touch screens)**: under `@media (pointer: coarse)` every target is at least 44 × 44 CSS px (WCAG 2.5.5's enhanced size, T =
-  44 = 11 units of the 4 px lattice, written in px so it never shrinks with the root font size): the action buttons, the toolbar's and
-  the side pane's tabs (the side pane's bar becomes 4 + 44 + 4 = 52 px), the create button, the search box's toggles, field and clear button, the comment field
+- **Target size (every pointer)**: under every pointer (mouse, trackpad, pen or finger) every target is at least 44 × 44 CSS px (WCAG 2.5.5's enhanced
+  size, T = 44 = 11 units of the 4 px lattice, written in px so it never shrinks with the root font size): the action buttons, the toolbar's and
+  the side pane's tabs (the side pane's bar is 4 + 44 + 4 = 52 px), the create button, the search box's toggles, field and clear button, the comment field
   and its send button, the delete confirmation, the overlay's and the notice's close buttons, both retry buttons, `Button` and `Input` of the edit form,
-  and the attachments' download and row links (a tile's last line becomes 48 px, 44 rounded up to 8, so tiles stay on the device-pixel lattice). The toolbar band's
+  and the attachments' download and row links (a tile's last line is 48 px, 44 rounded up to 8, so tiles stay on the device-pixel lattice). The toolbar band's
   controls take that 48 px height too (the view tabs, the create button, the auto-read switch's line, the search field and both toggles), because
   both edges of each must land on whole device pixels at the odd-eighth ratios (a 44 px box is 115.5 device pixels at 2.625): the toolbar's bar
-  becomes 4 + 48 + 4 = 56 px (112 px when it wraps to two lines) and the search row's first line 8 + 48 = 56 px. A round
+  is 4 + 48 + 4 = 56 px (112 px when it wraps to two lines) and the search row's first line 8 + 48 = 56 px. A round
   or pill-shaped control also gets a transparent square hit area over its padding box, because hit testing follows the rounded corners and a 44 px circle
-  does not hold a 44 × 44 square (a bordered control about 44 px wide adds `pointer-coarse:before:-inset-px` so the square also covers its border,
-  as the search box's pills and the List's mobile overlay close button do). Each box grows only through a minimum size, so nothing changes under a fine pointer (mouse, trackpad, pen), where targets keep the 24 px geometry of WCAG
-  2.5.8; 2.5.5 is therefore met under a coarse pointer only and not claimed overall. The auto-read switch keeps its 40 × 24 look and gets a centred
-  44 × 44 hit area in the band's 48 px line; the side pane's action buttons move to a 44 px line of their own under the subject, at its end. Exceptions under a
-  coarse pointer: the List's resize handle and the views' scroll bars, the host's filter select controls, the dev toolbox's reload and clear-cache
-  icon buttons (24 × 24 targets in its 24 px box; its SSE switch has the switch's centred 44 × 44 hit area, and under a coarse pointer the toolbox
-  spaces its items 6 px apart, 4 + (44 − 40) / 2, so that hit area does not cover the reload button's target) and `VirtualScroll`'s tap-scroll
-  circle. A Tailwind host generates these coarse-pointer utilities from Tailwind CSS v4.1 on (**Tailwind v4 host** above). Text fields use 16 px text under a coarse pointer (14 px under a fine one), so focusing them does not zoom the page on touch
-  browsers; the search field's Enter key is labelled as search (`enterkeyhint="search"`) and the comment field's as send (`enterkeyhint="send"`). When
-  the views are narrower than 320 px (the search row's smallest coarse-pointer width: the band's insets, both toggles, two 8 px gaps and a field that
-  keeps one 44 px target of text room), the search box's filter toggle moves to a line of its own under the field. The mobile overlay keeps its
+  does not hold a 44 × 44 square (a bordered control about 44 px wide adds `before:-inset-px` so the square also covers its border,
+  as the search box's pills and the List's mobile overlay close button do). Each box grows through a minimum size, so a control that declares a larger
+  size keeps it (the edit form's `Button` sizes). The auto-read switch keeps its 40 × 24 look and gets a centred
+  44 × 44 hit area in the band's 48 px line; the side pane's action buttons take a 44 px line of their own under the subject, at its end, and the List
+  card puts its toggles beside the preview (**List card** above). Exceptions: the List's resize handle and the views' scroll bars, the host's filter
+  select controls, the dev toolbox's reload and clear-cache icon buttons (24 × 24 targets in its 24 px box; its SSE switch has the switch's centred
+  44 × 44 hit area, and the toolbox spaces its items 6 px apart, 4 + (44 − 40) / 2, so that hit area does not cover the reload button's target) and
+  `VirtualScroll`'s tap-scroll circle. Text fields use 16 px text under a coarse pointer (14 px under a fine one), so focusing them does not zoom the
+  page on touch browsers; this text is the only rule the package keys on the pointer, and a Tailwind host generates it from Tailwind CSS v4.1 on
+  (**Tailwind v4 host** above). The search field's Enter key is labelled as search (`enterkeyhint="search"`) and the comment field's as send
+  (`enterkeyhint="send"`). When the views are narrower than 320 px (the search row's smallest width: the band's insets, both toggles, two 8 px gaps
+  and a field that keeps one 44 px target of text room), the search box's filter toggle moves to a line of its own under the field. The mobile overlay keeps its
   content at least its 16 px padding and at least the display's safe-area insets (`env(safe-area-inset-*)`) from each edge.
 - **Action buttons and icons**: the List card's star and read toggles, the star, read, edit and delete buttons of the DetailList header and the side
-  pane, and the trash button of the viewer's comments share one 24 px round target under a fine pointer (44 × 44 under a coarse one, **Coarse
-  pointers** above), which never shrinks, with a 16 px SVG icon centred in it (4 px on every side, 14 px in the coarse box), so the icons sit on the
-  4 px grid without depending on a font. In the List card the markers and toggles stand 4 px apart; the header
-  pills and the source badge are 24 px tall like the targets.
+  pane, and the trash button of the viewer's comments share one 44 px round target (**Target size** above), which never shrinks, with a 16 px SVG
+  icon centred in it by flexbox (14 px on every side), so the icons do not depend on a font. In the List card the markers and toggles stand 4 px
+  apart; the header pills and the source badge are 24 px tall (they are not targets).
   The star is a regular five-pointed star, outlined when off and filled gold when on (with a darker gold edge in the light theme); read is a check,
   unread an 8 px dot, edit a pencil, delete a trash can. Every icon state reaches at least 3.59:1 against each background it sits on, the button's
   hover background included, in both themes; in forced colours the star is drawn in `CanvasText` (off) and `Highlight` (on). The side pane shows them
-  in the order star, read, edit, delete, centred on the first line of the subject.
+  in the order star, read, edit, delete, on a 44 px line of their own under the subject, at its end.
   Unread is shown by the dot on the read toggle and by the row state in the description; no surface changes its border or its layout for it (a card's
   border is the same 1 px in every state).
-  The comment's trash button takes the 16 px icon's place in the 20 px line of the comment header (its 24 px target overhangs by 2 px, so the header
-  keeps its height), turns red while its confirmation waits (at least 3.59:1 on the comment surfaces), and the confirmation pill carries the control
+  The comment's trash button sits in a 44 px line of the comment header that holds its whole 44 px target (an overhanging target would cover the
+  comment above and the text), turns red while its confirmation waits (at least 3.59:1 on the comment surfaces), and the confirmation pill carries the control
   focus outline.
 
 ### Attachment display
@@ -3981,9 +4002,9 @@ luminance by 0.026 in the light theme, and a `shadow-md` brings the ring down to
   pixel ratio of 2).
 - **Tile**: one link to the original wraps the thumbnail frame and the file name; below it one line holds the size and the download link. The frame is
   decorative (`aria-hidden="true"`, no link of its own), so the tile link is named by the file name and a tile has two Tab stops (the preview, then
-  the download). The download link has a 24 px hit area, and its accessible name is the download label followed by the file name.
+  the download). The download link's own box is its 44 × 44 target, and its accessible name is the download label followed by the file name.
   The tile root (the grid item) is the tile's one inline-size container, exactly as wide as its track, so `100cqi` inside the tile is t. A tile is the
-  frame (h, below), the 8 px gap, the 20 px name, the 4 px gap and the 16 px last line, h + 48 px in all (48 and the grid gap of 16 are multiples of
+  frame (h, below), the 8 px gap, the 20 px name, the 4 px gap and the 48 px last line, h + 80 px in all (80 and the grid gap of 16 are multiples of
   8), and h need not be a multiple of 4.
   The last line therefore carries a bottom margin, the lattice pad δ(t) = ⌈h / q⌉ · q − h
   (`margin-block-end: calc(round(up, h, var(--aqdr-lattice-block)) - h)`, where h is the frame height's own expression, resolved against the same