refactor(ui): the popover engine and every render-phase ref write compile under the React Compiler

E32 S3. The compiler skipped 93 functions; it now skips 29 (try/finally shapes, two suppressions,
VirtualGrid). react-hooks/refs hits 245 -> 31.

- Popover engine: `ref={pop.refs.setReference}` made the compiler treat the whole popover handle as
  a ref, so every component holding one was skipped (21 call sites, the engine and its surface
  among them). The setter is destructured now; the same for useScrollFade and useReturnFocus.
- Render-phase `ref.current = x` writes moved to `useEffectEvent` where only effects read them,
  else to the new `useLatest` (written in a layout effect) / `useStableCallback`.
- FocusSafeButton (under every Button) read the focused element during render; it reads it through
  useSyncExternalStore, which React asks on every render instead of a cached memo.

Bugs this surfaced, fixed:
- Combobox: a chip could keep showing its raw id. The label cache was a ref an effect filled after
  the render that needed it; it is state merged during render now (test seen RED).
- useUndoable rendered from a ref plus a forced re-render; compiled, that memoizes a stale value.
  The history is state now, mirrored in a ref for the stable callbacks.
- ConfigPanel and the saved-views editor re-seeded their drafts in an effect, painting the stale
  draft for a frame; both adjust during render against the remembered key.
- Toaster's handover is written after commit instead of during render; a new test pins that the
  inherited set is taken once, at the takeover (seen RED on a per-render re-read).
- IssueComposer mutated a ref prop as a one-shot focus token; it is plain state.
- PlexBrowse wrote its info-scroll memory from an effect declared before the ref, past its own
  "one writer" rule; the writer comes first now and the effect goes through it.

The compiler ratchet drops to the measured 29 and now also requires FocusSafeButton and the popover
engine to compile.

frontend/src/components/Messages.tsx

@@ -1,4 +1,4 @@
-import { useEffect, useRef, useState } from "react";
+import { useEffect, useEffectEvent, useState } from "react";
 import { qk } from "../lib/queryKeys";
 import { useTranslation } from "react-i18next";
 import { useQuery } from "@tanstack/react-query";
@@ -90,20 +90,20 @@ function ConversationList({
   const [previews, setPreviews] = useState<Record<number, string>>({});
 
   // Decrypt conversation previews when fresh data arrives. The TRIGGER is `dataUpdatedAt` and the
-  // payload is read through a ref, which is what makes the dep list below complete without making
-  // the identity of `q.data` a trigger. That distinction is load-bearing: the `?? []` fallback is a
+  // payload is read through an effect event, which is what makes the dep list below complete without
+  // making the identity of `q.data` a trigger. That distinction is load-bearing: the `?? []` fallback is a
   // new array every render, and anything handing back a fresh object per render (a stub, a caller
   // that rebuilds it) turns "re-run when the data changes" into a render loop through setPreviews.
   // Measured the hard way — E27 S2 keyed this on `q.data`, and Messages.keyboard.dom.test hung.
-  const conversationsRef = useRef(q.data);
-  conversationsRef.current = q.data;
+  const latestConversations = useEffectEvent(() => q.data);
   useEffect(() => {
     if (!ready) return;
     let cancelled = false;
+    const conversations = latestConversations();
     // Each decrypt is caught (a failure previews as "⚠"), so this never rejects.
     void (async () => {
       const out: Record<number, string> = {};
-      for (const c of conversationsRef.current?.items ?? []) {
+      for (const c of conversations?.items ?? []) {
         const m = c.last_message;
         if (m.kind === "user" && m.ciphertext && m.iv) {
           try {