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/AnchoredPopover.tsx

@@ -112,6 +112,19 @@ export interface AnchoredPopoverOptions {
    *  lands the roving focus on it instead of the first item — the behaviour a "pick one of these
    *  modes" menu needs. Leave unset for action menus and multi-select toggle lists. */
   selectedIndex?: number | null;
+  /** Close when a scroll container under the panel scrolls. Off by default, because a panel anchored
+   *  to a real trigger element simply MOVES with it. Turn it on when the anchor is a fixed point
+   *  rather than an element — a right-click menu, which otherwise stays parked over whatever row
+   *  scrolls under it while its actions still target the row you opened it on (E10 review round 1).
+   *  This is also what a native context menu does. */
+  dismissOnScroll?: boolean;
+  /** Hand the focus back to the trigger on close. On by default, and right whenever there IS a
+   *  trigger element. Turn it off when the anchor is a virtual point: floating-ui then has no
+   *  `domReference` to return to and falls back to a module-global "previously focused" stack, so it
+   *  restores some unrelated element from an earlier popover — which, in the rail's inline rename,
+   *  stole focus back from the field that had just opened and tore it down again (E10 review round
+   *  1). A caller that turns this off owns the restore. */
+  returnFocus?: boolean;
 }
 
 // Internal: call sites use the inferred hook return, they don't name the type.
@@ -215,7 +228,10 @@ export function useAnchoredPopover(opts: AnchoredPopoverOptions) {
   // off entirely. (Leaving it on for hover made an open tooltip's document-level handler either
   // stopPropagation the Escape away from a Modal/player underneath, or double-close both.) Outside-
   // press stays with floating-ui (tree-aware).
-  const dismiss = useDismiss(context, { escapeKey: false });
+  const dismiss = useDismiss(context, {
+    escapeKey: false,
+    ancestorScroll: opts.dismissOnScroll ?? false,
+  });
   // `role:"combobox"` makes Floating UI wire the whole typeable-combobox ARIA tree: the reference input
   // → role=combobox + aria-expanded/controls/autocomplete + aria-activedescendant (from the virtual nav),
   // the surface → role=listbox, the items → role=option + their option ids. (`combobox` maps to the
@@ -285,6 +301,7 @@ export function useAnchoredPopover(opts: AnchoredPopoverOptions) {
     roves,
     open: opts.open,
     selectedIndex: opts.selectedIndex ?? null,
+    returnFocus: opts.returnFocus ?? true,
     refs,
     floatingStyles,
     context,
@@ -509,6 +526,7 @@ function PopoverSurfaceInner({
     isNav,
     isCombobox,
     roves,
+    returnFocus,
     selectedIndex,
     activeIndex,
     highlightIndex,
@@ -606,7 +624,7 @@ function PopoverSurfaceInner({
             // — in an item-less menu (e.g. a first-run tag editor with only a create input) — the
             // input, so such a menu still has a keyboard entry point instead of stranding focus.
             initialFocus={initialFocus ?? (isNav && selectedIndex != null ? -1 : undefined)}
-            returnFocus
+            returnFocus={returnFocus}
           >
             {positioned}
           </FloatingFocusManager>