refactor(e10): move the platform components into components/ui/ and enforce the boundary

The app HAS a platform layer -- AnchoredPopover (22 importers, with
arrows/typeahead/Escape/anchor-flip), QueryState (21), Modal (17),
PageShell, DataTable, Tabs, Tooltip and ~26 more -- but it sat flat among
~160 feature components with nothing marking it as one. Several of those
files describe themselves as 'the one place' or 'canonical' and were
still bypassed by hand-rolled markup, because a layer nobody can see is a
layer nobody uses; three separate inventory passes of this codebase
misread it the same way.

Moves the 33 domain-free modules into components/ui/, rewrites the
imports in 89 files, and makes the boundary a lint rule rather than a
convention: inside ui/ a one-level-up import (a feature component) and
any lib/api slice are errors. The rule was verified to fire on both and
to leave generic lib/ helpers alone. README.md states which side of the
line a component belongs on and why.

No behaviour change: 3x tsc, eslint, knip, prettier and 687 vitest tests
all green; no backend file touched.

frontend/src/lib/channelsUrlState.dom.test.ts

@@ -10,7 +10,7 @@ import {
   hasChannelsParams,
   type ChannelsUrlState,
 } from "./channelsUrlState";
-import type { FilterMap } from "../components/tableHeader";
+import type { FilterMap } from "../components/ui/tableHeader";
 
 // A concrete non-default filter map exercising both wire shapes: scalars (the sync chip, a select) and
 // an array (a multi column).

frontend/src/lib/channelsUrlState.ts

@@ -6,7 +6,7 @@
 // emitted, so URLs stay clean. The manager's name search is deliberately EPHEMERAL (like the feed/plex
 // rail search) and stays OUT of the shared contract.
 import { decodeSortParam, encodeSortParam, type SortState } from "./columnSort";
-import { type FilterMap } from "../components/tableHeader";
+import { type FilterMap } from "../components/ui/tableHeader";
 
 // The content state S8 mirrors. `view` is the raw tab string (the provider clamps it); `sort` is the
 // raw provider SortState (healed against live columns only at the point of use), so the user's real

frontend/src/lib/playlistView.test.ts

@@ -1,6 +1,6 @@
 import { describe, expect, it } from "vitest";
 import { applyView, sameOrder } from "./playlistView";
-import type { Column } from "../components/tableHeader";
+import type { Column } from "../components/ui/tableHeader";
 import type { Video } from "./api";
 
 // The playlist's view derivation (E4 S4). What makes it worth a test: the column sort and the

frontend/src/lib/sortOptions.ts

@@ -1,4 +1,4 @@
-import { type Column } from "../components/tableHeader";
+import { type Column } from "../components/ui/tableHeader";
 import { type SortOption } from "./columnSort";
 
 /** The `SortOption[]` a table exposes for sorting — its sortable columns, labelled by header. Bridges

frontend/src/lib/useFilterState.ts

@@ -1,7 +1,7 @@
 import { useCallback, useState } from "react";
 import { getAccountRaw, setAccountRaw } from "./storage";
 import { useAccountRehydrate } from "./useAccountRehydrate";
-import type { FilterMap } from "../components/tableHeader";
+import type { FilterMap } from "../components/ui/tableHeader";
 
 // The per-account persisted column-filter map for a DataTable whose filters are CONTROLLED by the
 // caller (so a second view of the same rows — the channel manager's card grid, the top status chips