fix(e10): review round 1 — the boundary that did not bind, and 14 more

The epic-end review found 32 verified issues. This is the first fix round:
the three highs, the user-facing mediums, and the tests that were passing
for the wrong reason. Docs and the remaining low-severity tail are next.

The boundary rule was the worst of them. Both `no-restricted-imports`
regexes were written in plain "..." literals, where `\.` is an unknown
escape that collapses to the any-char `.` — so the rule read like a
boundary and matched far less than one. `../../lib/api` (the barrel every
feature component imports) and `../../components/Feed` (the same file
`../Feed` names) both sailed through a green gate. String.raw, a third
pattern for the second spelling, and a vitest over ESLint.lintText so a
rule that silently matches nothing can never look like a clean codebase
again.

closeThenNavigate waited for exactly one reclaim popstate. With a second
Back-closable layer still mounted — a palette opened over the player —
the navigation unmounted that layer too, and its reconcile backed over
the entry the navigation had just pushed: "go to Channels" closed the
player and landed on the feed. It now waits for the LAST programmatic
back, then adopts the entries the navigation buried, and falls back after
250ms rather than hanging if no popstate is ever coming.

The rail's inline rename died on arrival. With no domReference, floating-
ui's returnFocus falls through to a module-global stack and restores some
unrelated element from an earlier popover — blurring the field into its
own commit-and-close, from the second popover of a session onward. The
context menu now owns the restore: back to the row, but only if the row
is still there and nothing else has claimed focus.

Also:
- Backspace under the cheat sheet stopped Plex playback and dropped to
  the grid; `back` now defers to any layer above, like `escape` beside it.
- A move invalidated only the source list, so the target kept serving
  pre-move contents for 30s while the rail already counted N+1.
- Every move error a user can reach is a 404, which `req` leaves to the
  caller — so the row snapped back in silence and the shipped moveErrors
  strings were unreachable.
- swallowClick armed on long-press but was disarmed only by the click it
  was armed for; any press that produced no click ate the next tap on the
  whole list.
- The context menu stayed parked over whatever row scrolled under it.
- overflow-clip on the chip lanes ate the focus ring's top and bottom.
- "Why is this off" rode on disabled rows, which show no tooltip and take
  no focus: a new `inert` item keeps the reason readable.
- Shift+F10 was advertised app-wide but wired only on Playlists; it has
  its own scope now, and useContextMenu matches through the shared parser
  instead of its own literals.
- Mod+K could not close the palette, `h` machine-gunned on auto-repeat,
  and both were bound above the branch that mounts their overlays.
- Palette options were in the tab order under aria-activedescendant, and
  a scroll-synthesised mousemove stole the keyboard selection.
- The OSD live region was created together with its own text.
- Ending a rename stranded focus on <body>.
- The Button variants' hover halves are `enabled:` — the one migrated
  site that had guarded its own lost the guard on the way in.
- HU builtinLocked named the list "Watch later" in a Hungarian sentence.

Tests: the chip-lane contract counted per FILE, so a second hand-rolled
lane in an already-compliant file was invisible; the closeThenNavigate
ordering test only passed on a popstate left behind by its neighbours and
failed alone, so it moved to its own file.

frontend/src/components/ui/Button.tsx

@@ -43,23 +43,30 @@ const VARIANTS: Record<ButtonVariant, string> = {
   // (ghost), while this primitive hovered to `fg` and filled with `surface` — so the 37 migrated sites
   // and the ~100 hand-rolled ones had drifted into two different looks. That split IS the
   // inconsistency this epic exists to remove; the primitive follows the majority, not the reverse.
-  outline: "font-medium border border-border text-muted hover:text-accent hover:border-accent",
-  "outline-accent": "font-medium border border-accent/40 text-accent hover:bg-accent/10",
+  outline:
+    "font-medium border border-border text-muted enabled:hover:text-accent enabled:hover:border-accent",
+  "outline-accent": "font-medium border border-accent/40 text-accent enabled:hover:bg-accent/10",
   // Neutral until you reach for it. NOT `danger-soft`, which is already red at rest — the difference
   // is whether the button should advertise the destruction before the pointer arrives.
   "outline-danger":
-    "font-medium border border-border text-muted hover:text-danger hover:border-danger/40",
-  "outline-warn": "font-medium border border-warn/40 text-warn hover:bg-warn/10",
-  ghost: "font-medium text-muted hover:text-fg hover:bg-card",
-  glass: "font-medium glass-card glass-hover hover:text-accent",
+    "font-medium border border-border text-muted enabled:hover:text-danger enabled:hover:border-danger/40",
+  "outline-warn": "font-medium border border-warn/40 text-warn enabled:hover:bg-warn/10",
+  ghost: "font-medium text-muted enabled:hover:text-fg enabled:hover:bg-card",
+  glass: "font-medium glass-card glass-hover enabled:hover:text-accent",
   "danger-soft":
-    "font-medium border border-danger/60 text-danger hover:bg-danger/10 hover:border-danger",
+    "font-medium border border-danger/60 text-danger enabled:hover:bg-danger/10 enabled:hover:border-danger",
   // No font-weight here on purpose: BASE already sets font-medium, and a second font-* utility would
   // be a coin-flip (both are single-class utilities of equal specificity, and without tailwind-merge
   // the winner is decided by the generated stylesheet order, not by the class list order).
-  link: "font-semibold text-accent hover:underline",
+  link: "font-semibold text-accent enabled:hover:underline",
 };
 
+// Why every hover above is `enabled:hover:` — Tailwind's `:not(:disabled)`. A disabled button that
+// still lights up on hover advertises a click that does nothing, and the ONE migrated call site that
+// had guarded its own hover (TagManager's Add) silently lost the guard when it moved onto this
+// primitive (E10 review round 1). The contract belongs here, not in ~160 call sites: BASE dims a
+// disabled button, and the variant must not paint over that dimming.
+
 // The geometry ladder, and the whole of it — a call site picks a rung, it does not invent one. The
 // rungs were derived from what the app actually used (counted during E10 S1b): `px-3 py-2 text-sm`
 // (22 sites), `px-2 py-1 text-xs` (12), `px-3 py-1.5 text-sm` (11). Every value is rem-derived, so