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/lib/useChipOverflowFit.ts

@@ -31,8 +31,16 @@ import { useLayoutEffect, useRef, useState, type RefObject } from "react";
  * fixed-layout column had assigned it. `clip`, not `hidden`, because clip creates no scrollport, so
  * nothing can ever scroll the mirror into view. The clip cannot disturb the measurement: offsetLeft and
  * offsetWidth are layout values, and clipping does not change layout.
+ *
+ * `overflow-clip-margin` is what keeps the clip from eating the KEYBOARD FOCUS RING. A bare
+ * `overflow: clip` cuts at the padding box, while the app-wide base ring is `outline: 2px` at
+ * `outline-offset: 2px` — i.e. it paints 4px OUTSIDE the border box. These lanes have no padding and
+ * their height is set by the chip itself, so the first commit of this fix silently cut the ring's top
+ * and bottom bands off every applied-filter chip and the tag lane's `+` trigger, leaving two floating
+ * side bars (E10 review round 1). 0.25rem is exactly the ring's reach and nowhere near the ~600px the
+ * mirror needs, so containment is unaffected.
  */
-export const chipLaneClass = "relative overflow-clip";
+export const chipLaneClass = "relative overflow-clip [overflow-clip-margin:0.25rem]";
 
 export interface ChipRowGeometry {
   /** Available lane width — the visible row's clientWidth. */