test(frontend): a React Compiler ratchet over everything the build ships

compilerCoverage.contract.test.ts used to check two files. It now runs the
real compiler over all of src (minus tests) and holds the exact set it skips
today, file -> function -> category: 93 functions. A new skip or a category
change is red, and so is a listed skip that has gone, so the list only
shrinks. Channels and DataTable must also show up as compiled, so a harness
that compiled nothing cannot pass.

Measured against the audit's scan: no function this sprint touched started
to skip. PlexPersonView and useOverlayOrder now compile.

reactPlugin.ts claimed the compiler's rules were linted, which was false
while react-hooks/refs was off. That comment and the refs block in
eslint.config.js now say what holds the line and why refs is still off:
245 real hits, pinned by the ratchet, burned down from S3.

frontend/reactPlugin.ts

@@ -11,8 +11,14 @@ import reactCompiler from "babel-plugin-react-compiler";
 //
 // The React Compiler auto-memoises: it infers what `useCallback`/`useMemo` were being hand-written
 // for and applies the equivalent itself. It is enabled repo-wide with no opt-out list because it
-// bails out on its own for anything it cannot prove safe (its rules are also linted, via
-// eslint-plugin-react-hooks). `target` follows the installed React major and must move with it.
+// bails out on its own for anything it cannot prove safe — SILENTLY: `panicThreshold` is "none" and
+// there is no logger here, so a skipped component still works and simply re-renders everything under
+// it. This comment used to say "its rules are also linted"; it was false while `react-hooks/refs` was
+// off, and 95 functions sat uncompiled behind it (E32). What actually holds the line now is
+// src/components/compilerCoverage.contract.test.ts, which runs THIS compiler over the shipped source
+// and fails on any skip not on its list; the react-hooks lint rules are the early warning, with the
+// one still switched off recorded in docs/gates.md. `target` follows the installed React major and
+// must move with it.
 //
 // The plugin is IMPORTED rather than named by the usual `"babel-plugin-react-compiler"` string. Two
 // reasons, both about the gate: a string is invisible to knip, which then reports the dependency as