fix(design): claim audit part 1b — whole-row switches, the field-family edge, state-layer hovers, icon links, reason-disabled controls, 24/44 targets (E28)

- F12 (owner: A): SwitchRow, the whole settings row toggles; a Config boolean toggles from its title
  and hint (a label pointed at the switch).
- F14 (owner: B): the form dropdown trigger wears the field frame (see-through, the >= 3:1 edge);
  labelled pills keep the faint edge and the accent-edge hover. DESIGN says so, with log rows.
- F6: ~15 bg-card / bg-border / opacity hovers onto the B3 state layer; a lint rule (HOVER_SWAP)
  refuses the swap, contract-tested.
- F10: bare 14px icon links onto IconLink / LinkButton; a local lint rule refuses a glyph-only <a>.
- F13: reason-disabled controls are aria-disabled (Users, Channels backfill, Discovery, Scheduler
  runs, Config tests); FocusSafeButton now swallows the click of a caller's aria-disabled; the
  Config tests say why while dirty (testDirty, HU/EN).
- F5/F11: every control measured live at 24 (mouse) and 44 (coarse) across every page; touch-target
  is a utility that wins over a caller's min-h-6; link variants carry it too; SegmentedToggle,
  Tabs, NavRail, menu rows, PriorityStepper, sliders, CheckRow, InnerInput, card links and the rest.
- F9: DismissibleChip's label reaches the chip's 24; the Combobox chips are DismissibleChips.
- F15: the "+N" / "More..." open state worded as it renders.

frontend/src/components/ui/README.md

@@ -64,11 +64,13 @@ change at 1024x768, 820x1180 and a desktop size. That contract lives in these co
   against a container's own pixel width rather than sized against text. A px-frozen BOX utility
   (`w-[Npx]`, `max-w-[Npx]`, …) is an eslint error too, since the 2026-09 sweep: use the spacing
   scale (`w-37.5` is 150px at the default size and grows with the slider).
-- **Minimum target: 2.75rem, on coarse pointers only** (`.touch-target`, index.css). A 32px icon
+- **Minimum target: 2.75rem, on coarse pointers only** (the `touch-target` utility, index.css). A 32px icon
   button is fine with a mouse and not with a thumb, so the box grows where there is no precise
   pointer. It grows the real box rather than painting an invisible hit area: two expanded hit areas
   on neighbouring icon buttons would overlap, and an overlap fires the _wrong_ button.
-- The link variants are excluded from the minimum: they are text inside a sentence.
+- The link variants carry it too (and the 24 mouse floor): every one stands on its own. Text inside a
+  sentence is a plain `<a>`, which WCAG 2.5.8 exempts. On a coarse pointer the target wins over a
+  caller's own `min-h-6` / `min-w-6` (it is `!important` there), or a control carrying both stays 24.
 
 E28 S3b brings every button in the app onto these primitives (the chips and the player's overlay
 buttons last), after which a raw `<button>` outside this directory is a lint error.