refactor(frontend): honest effect deps in the app shell and the ui layer (E27 S2)

Burns the first 14 of the 113 hook suppressions. Three verdicts, applied per site:

A useEffect that should not exist (6):
- Avatar remembered "the image failed" as a boolean an effect reset on src change. The
  component is recycled across items in the virtualized feed, so after one avatar 429s the
  next item's slot committed the fallback initial over a perfectly good image and only the
  post-paint effect cleared it. The failure is now keyed BY URL; derived state cannot be stale.
- Combobox cleared the typed query from an effect on `open`. Moved into setOpenAnd, the single
  funnel every close goes through. That also stops a spurious onQueryChange("") AT MOUNT, which
  told a controlled caller its own initial query had been cleared before the user touched it.
- CommandPalette reset query + picked row from an effect. Closed now means UNMOUNTED, not
  hidden, so a fresh open starts blank because mounting already means that -- and the ranking
  memo over every channel, playlist and saved view stops running while the palette is shut.
- Pager's page box held a copy of the page that an effect re-synced; it now derives it and
  keeps a draft only while being edited.
- App's ?link= / ?oauth= / ?admin= one-shots asserted "once per mount" with an empty dep list.
  The ref guard the codebase already uses in 22 places ENFORCES it, so the honest deps can
  include `t` -- which a language switch legitimately changes, and which would otherwise have
  re-fired the toast.

Honest deps that also fix something (5):
- App's module preload was keyed on the account id, so a permission change that alters the
  module set without moving the id never re-preloaded. `preload()` is idempotent, so depending
  on `me` costs nothing.
- App's access-request nudge now re-issues on a language switch; it used to stay in the old
  language until the pending count changed.
- App's diagnostics effect: applyDiagnostics already no-ops on an unchanged effective level,
  so picking four fields out by hand was guarding nothing and missed any field added later.
- DataTable's two filter effects: a ref holds the latest onFiltersChange so commitFilters can
  be stable, which is what lets the effects name it instead of switching the check off.

Genuine escape hatches (7) moved OUT of eslint-suppressions.json into inline directives that
name the invariant at the site -- the toast handover's render-phase global, the live region's
deliberate arming tick, the docked one-slot component, the popover engine's floating-ui list
state, dnd-kit's per-drag `moved` flag, BackToTop's DOM read and the palette's debounced
announcement. A reader of the code now sees why; a JSON file no one opens does not.

Tests: Avatar (3, new file) and Pager (3) pin the derived-state frames with a layout-phase
probe -- layout effects run before any passive effect, so they read the frame the browser would
paint. Combobox (2) pins the close-clears-query contract and the no-callback-at-mount rule.
All three sets mutation-checked against the effect-based originals.

Suppressions 113 -> 99; exhaustive-deps 45 -> 35.

frontend/src/components/ui/Avatar.dom.test.tsx

@@ -0,0 +1,64 @@
+// @vitest-environment jsdom
+import { useLayoutEffect } from "react";
+import { describe, it, expect, afterEach } from "vitest";
+import { render, screen, fireEvent, cleanup } from "@testing-library/react";
+
+import Avatar from "./Avatar";
+
+afterEach(cleanup);
+
+// The failure state is keyed by URL rather than held as a boolean an effect resets, and the reason
+// is a frame the user could see: Avatar is recycled across items in the virtualized feed, so after
+// ONE image 429s (Google's avatar CDNs throttle bursts — see the component's own note), the next
+// item to land in that slot rendered with its new `src` and the previous item's `failed`. The
+// fallback initial was therefore committed and painted over a perfectly good image, and only the
+// post-paint effect put it right.
+//
+// `useLayoutEffect` is what makes that observable instead of a race: layout effects run against the
+// committed DOM BEFORE any passive effect, so the snapshot it takes is exactly the frame the browser
+// would paint — the one the old reset effect had not repaired yet.
+function Probe({ src, painted }: { src: string; painted: string[] }) {
+  useLayoutEffect(() => {
+    painted.push(document.body.innerHTML);
+  });
+  return <Avatar src={src} alt="avatar" fallback="Zed" />;
+}
+
+describe("Avatar · a failed image must not follow the component to the next item", () => {
+  it("shows the new src in the SAME commit that changes it, with no fallback frame between", () => {
+    const painted: string[] = [];
+    const { rerender } = render(<Probe src="https://cdn.test/a.jpg" painted={painted} />);
+
+    fireEvent.error(screen.getByRole("img", { name: "avatar" }));
+    expect(screen.queryByRole("img")).toBeNull();
+    expect(screen.getByText("Z")).toBeTruthy();
+
+    painted.length = 0;
+    rerender(<Probe src="https://cdn.test/b.jpg" painted={painted} />);
+
+    // The FIRST frame after the src change already carries the image. Reading the last snapshot
+    // instead would let a passive-effect repair pass, which is precisely the bug.
+    expect(painted.length).toBeGreaterThan(0);
+    expect(painted[0]).toContain("https://cdn.test/b.jpg");
+    expect(painted[0]).not.toContain(">Z<");
+  });
+
+  it("keeps the fallback for the URL that actually failed, not for whatever is current", () => {
+    const { rerender } = render(
+      <Avatar src="https://cdn.test/a.jpg" alt="avatar" fallback="Zed" />,
+    );
+    fireEvent.error(screen.getByRole("img", { name: "avatar" }));
+    expect(screen.getByText("Z")).toBeTruthy();
+
+    rerender(<Avatar src="https://cdn.test/b.jpg" alt="avatar" fallback="Zed" />);
+    expect(screen.getByRole("img", { name: "avatar" }).getAttribute("src")).toBe(
+      "https://cdn.test/b.jpg",
+    );
+  });
+
+  it("falls back when there is no src at all", () => {
+    render(<Avatar src={null} alt="avatar" fallback="Zed" />);
+    expect(screen.queryByRole("img")).toBeNull();
+    expect(screen.getByText("Z")).toBeTruthy();
+  });
+});

frontend/src/components/ui/Avatar.tsx

@@ -1,4 +1,4 @@
-import { useEffect, useState } from "react";
+import { useState } from "react";
 
 // Avatar image with a graceful fallback.
 //
@@ -20,8 +20,13 @@ export default function Avatar({
   fallback?: string; // a name/title; its first letter is shown when there's no image
   className?: string;
 }) {
-  const [failed, setFailed] = useState(false);
-  useEffect(() => setFailed(false), [src]);
+  // The failure is remembered BY URL, not as a boolean that an effect resets when `src` changes.
+  // That distinction is visible: this component is recycled across items in the virtualized feed, so
+  // one avatar's 429 used to paint the fallback initial over the NEXT item's perfectly good image
+  // for a frame — React committed the render with the new `src` and the stale `failed`, and only the
+  // post-paint effect cleared it. Derived state cannot be stale, so there is nothing to reset.
+  const [failedSrc, setFailedSrc] = useState<string | null>(null);
+  const failed = !!src && failedSrc === src;
 
   if (src && !failed) {
     return (
@@ -30,7 +35,7 @@ export default function Avatar({
         alt={alt}
         loading="lazy"
         referrerPolicy="no-referrer"
-        onError={() => setFailed(true)}
+        onError={() => setFailedSrc(src)}
         className={className}
       />
     );

frontend/src/components/ui/BackToTop.tsx

@@ -36,6 +36,7 @@ export default function BackToTop({ dep, threshold = 600 }: { dep?: unknown; thr
   useEffect(() => {
     const el = document.querySelector("main");
     scrollerRef.current = el;
+    // eslint-disable-next-line react-hooks/set-state-in-effect -- reading the DOM is the point — <main> is swapped by the page switch above us, and only after that commit can its scrollTop be read at all. Nothing derivable in render knows where the new page is scrolled to.
     setShow(!!el && el.scrollTop > threshold);
   }, [dep, threshold]);
 

frontend/src/components/ui/Combobox.dom.test.tsx

@@ -246,6 +246,54 @@ describe("Combobox", () => {
     expect(onChange).toHaveBeenCalledWith(["Action"]); // replaced, not appended
     expect(screen.getByRole("combobox").getAttribute("aria-expanded")).toBe("false"); // closed
   });
+
+  // The typed query is discarded when the list closes, and it happens IN the close — the clear used
+  // to be an effect on `open`, which fired a render later and, in controlled mode, reported the
+  // empty query outside any event (E27 S2). The list is for "find and pick": a leftover filter would
+  // hide everything worth seeing the next time it opens.
+  it("discards the typed query when the list closes, so the next open shows everything", () => {
+    wrap(<Combobox label="Genre" options={OPTIONS} selected={[]} onChange={vi.fn()} />);
+    const input = screen.getByRole("combobox");
+    fireEvent.focus(input);
+    fireEvent.change(input, { target: { value: "com" } });
+    expect(input).toHaveProperty("value", "com");
+    expect(screen.queryByText("Drama")).toBeNull(); // filtered away
+
+    fireEvent.keyDown(input, { key: "Escape" });
+    expect(input.getAttribute("aria-expanded")).toBe("false");
+    expect(input).toHaveProperty("value", "");
+
+    fireEvent.focus(input);
+    expect(screen.getByText("Drama")).toBeTruthy(); // the whole list is back
+  });
+
+  it("does not report a query change until something actually changes it", () => {
+    // A clear driven by an effect on `open` fires at MOUNT too — `open` starts false — so a
+    // controlled caller was told its own initial query had been cleared before the user touched
+    // anything. Driving it from the close event instead means no event, no callback.
+    const onQueryChange = vi.fn();
+    const onOpenChange = vi.fn();
+    wrap(
+      <Combobox
+        label="Collection"
+        multiple={false}
+        options={OPTIONS}
+        selected={[]}
+        onChange={vi.fn()}
+        query="com"
+        onQueryChange={onQueryChange}
+        onOpenChange={onOpenChange}
+        clientFilter={false}
+      />,
+    );
+    expect(onQueryChange).not.toHaveBeenCalled();
+
+    fireEvent.focus(screen.getByRole("combobox"));
+    expect(onQueryChange).not.toHaveBeenCalled();
+    fireEvent.click(screen.getByText("Action"));
+    expect(onOpenChange).toHaveBeenLastCalledWith(false);
+    expect(onQueryChange.mock.calls).toEqual([[""]]);
+  });
 });
 
 // PageUp/PageDown (E11, owner request): the sidebar's channel filter and the Plex pickers run to

frontend/src/components/ui/Combobox.tsx

@@ -106,6 +106,13 @@ export default function Combobox({
   const setOpenAnd = (next: boolean) => {
     setOpen(next);
     onOpenChange?.(next);
+    // Closing discards the typed query: the list is for "find and pick", and a leftover filter would
+    // hide everything worth seeing on the next open. It belongs HERE, not in an effect on `open`,
+    // because this is the single funnel every close goes through — floating-ui's dismiss, Escape and
+    // outside-click all arrive as onOpenChange, and the single-select commit calls it directly
+    // (verified: `setOpen` is called nowhere else). So the clear lands in the same commit as the
+    // close, and the controlled caller's onQueryChange fires once, from an event rather than a render.
+    if (!next) setQuery("");
   };
   const pop = useAnchoredPopover({ open, onOpenChange: setOpenAnd, mode: "combobox" });
   // The input is the combobox reference for floating-ui AND our own focus target (the field's
@@ -127,12 +134,6 @@ export default function Combobox({
   // would make Enter a no-op over a highlighted row.
   const { activeIndex, highlightIndex } = pop;
 
-  // Clear the typed query when the list closes.
-  useEffect(() => {
-    if (!open) setQuery("");
-    // eslint-disable-next-line react-hooks/exhaustive-deps
-  }, [open]);
-
   const filtered = useMemo(() => {
     if (!clientFilter) return options;
     const q = query.trim().toLowerCase();

frontend/src/components/ui/CommandPalette.tsx

@@ -81,6 +81,15 @@ export default function CommandPalette({
   onClose: () => void;
   groups: CommandGroup[];
 }) {
+  // Closed means UNMOUNTED, not merely hidden, and that one line replaces the effect that used to
+  // blank the query and the picked row on every open: fresh state is what mounting already means.
+  // It also stops the ranking memo below — which folds and scores every channel, playlist and saved
+  // view — from re-running on every parent render while the palette is shut.
+  if (!open) return null;
+  return <CommandPaletteBody onClose={onClose} groups={groups} />;
+}
+
+function CommandPaletteBody({ onClose, groups }: { onClose: () => void; groups: CommandGroup[] }) {
   const { t } = useTranslation();
   const listId = useId();
   const groupId = useId();
@@ -94,15 +103,6 @@ export default function CommandPalette({
   const activeRef = useRef<HTMLButtonElement | null>(null);
   const listRef = useRef<HTMLDivElement | null>(null);
 
-  // A fresh open starts from a blank field: the palette is for "take me somewhere", and a leftover
-  // query from last time hides everything you might want now.
-  useEffect(() => {
-    if (open) {
-      setQuery("");
-      setPicked(null);
-    }
-  }, [open]);
-
   // The GROUP order stays fixed — modules, channels, playlists, views, actions read the same every
   // time — and the rows are ranked inside each group. The best row overall starts highlighted, so
   // Enter takes the best match even when it sits in a later group.
@@ -144,6 +144,7 @@ export default function CommandPalette({
   const [announced, setAnnounced] = useState("");
   useEffect(() => {
     if (!summary) {
+      // eslint-disable-next-line react-hooks/set-state-in-effect -- the announcement is DEBOUNCED on purpose (ANNOUNCE_DELAY_MS above): a polite region rewritten per keystroke queues one utterance per letter. A timer's result cannot be derived in render, and the empty branch is the same timer's cancel.
       setAnnounced("");
       return;
     }
@@ -151,8 +152,6 @@ export default function CommandPalette({
     return () => window.clearTimeout(timer);
   }, [summary]);
 
-  if (!open) return null;
-
   // Close, wait for this dialog's own Back-to-close entry to be reclaimed, THEN run: most commands
   // navigate, and a pushState issued before that reclaim is undone by it. Only THIS dialog closes —
   // a command that navigates closes whatever is underneath itself, one that does not (a theme) must

frontend/src/components/ui/DataTable.tsx

@@ -1,4 +1,4 @@
-import { useEffect, useRef, useState, type ReactNode } from "react";
+import { useCallback, useEffect, useRef, useState, type ReactNode } from "react";
 import { useTranslation } from "react-i18next";
 import { sortRows, cycleSort, type SortState } from "../../lib/columnSort";
 import Pager from "./Pager";
@@ -149,10 +149,19 @@ export default function DataTable<T>({
   // `filters` as a dep (which would re-run them on every filter change).
   const filtersRef = useRef(filters);
   filtersRef.current = filters;
-  const commitFilters = (next: FilterMap) => {
-    if (controlledFilters) onFiltersChange!(next);
-    else setInternalFilters(next);
-  };
+  // …and the same trick for the CALLBACK, one line further: a controlled caller almost always
+  // passes an inline arrow, so `onFiltersChange` is a fresh function on every render. Reading it
+  // through a ref is what lets `commitFilters` be stable, and a stable commitFilters is what lets
+  // the two effects below NAME it in their dep lists instead of switching the check off.
+  const onFiltersChangeRef = useRef(onFiltersChange);
+  onFiltersChangeRef.current = onFiltersChange;
+  const commitFilters = useCallback(
+    (next: FilterMap) => {
+      if (controlledFilters) onFiltersChangeRef.current!(next);
+      else setInternalFilters(next);
+    },
+    [controlledFilters],
+  );
 
   // Persist page/size always, but only the sort/filter slices this table actually OWNS — a controlled
   // caller persists those itself, so writing them here would just leave a stale, never-read duplicate.
@@ -169,12 +178,16 @@ export default function DataTable<T>({
     );
   }, [persistKey, controlledSort, controlledFilters, sort, filters, page, size]);
 
+  // Destructured so the deps are the values the body actually reads. `externalFilter` itself is an
+  // object literal at every call site, so depending on it would re-apply the filter — and reset the
+  // page — on every parent render.
+  const externalKey = externalFilter?.key;
+  const externalValue = externalFilter?.value;
   useEffect(() => {
-    if (!externalFilter) return;
-    commitFilters({ ...filtersRef.current, [externalFilter.key]: externalFilter.value });
+    if (externalKey === undefined || externalValue === undefined) return;
+    commitFilters({ ...filtersRef.current, [externalKey]: externalValue });
     setPage(0);
-    // eslint-disable-next-line react-hooks/exhaustive-deps
-  }, [externalFilter?.key, externalFilter?.value]);
+  }, [externalKey, externalValue, commitFilters]);
 
   // Clear column filters when the reset token advances. The ref starts at 0 (not at the prop)
   // so a navigation that bumped the token still clears even when it remounts this table fresh
@@ -186,8 +199,7 @@ export default function DataTable<T>({
     resetRef.current = resetFiltersToken;
     commitFilters({});
     setPage(0);
-    // eslint-disable-next-line react-hooks/exhaustive-deps
-  }, [resetFiltersToken]);
+  }, [resetFiltersToken, commitFilters]);
 
   const sorted = sortRows(filterRows(rows, columns, filters), columns, sort);
 

frontend/src/components/ui/Pager.dom.test.tsx

@@ -1,4 +1,5 @@
 // @vitest-environment jsdom
+import { useLayoutEffect } from "react";
 import { describe, it, expect, vi, afterEach } from "vitest";
 import { render, screen, fireEvent, cleanup } from "@testing-library/react";
 
@@ -32,3 +33,80 @@ describe("Pager · rows per page", () => {
     expect(onSizeChange.mock.calls).toEqual([[50], [0]]);
   });
 });
+
+// The page box DERIVES the current page (E27 S2): it holds a draft only while being edited, so the
+// parent moving the page needs no re-sync effect. The layout-phase probe is what proves "derived"
+// rather than "re-synced after paint" — a passive effect could not have run yet when it reads.
+describe("Pager · the page box follows the page without an effect", () => {
+  function Probe({ page, painted }: { page: number; painted: string[] }) {
+    useLayoutEffect(() => {
+      painted.push(
+        (document.querySelector('input[type="number"]') as HTMLInputElement | null)?.value ?? "",
+      );
+    });
+    return (
+      <Pager
+        page={page}
+        size={10}
+        total={100}
+        pageSizeOptions={[10, 25]}
+        onPageChange={() => {}}
+        onSizeChange={() => {}}
+        sizeLabel="Rows per page"
+      />
+    );
+  }
+
+  it("shows the new page in the first frame after the parent moves it", () => {
+    const painted: string[] = [];
+    const { rerender } = render(<Probe page={0} painted={painted} />);
+    expect(screen.getByLabelText("datatable.pager.pageLabel")).toHaveProperty("value", "1");
+
+    painted.length = 0;
+    rerender(<Probe page={4} painted={painted} />);
+    expect(painted[0]).toBe("5");
+  });
+
+  it("keeps what you type until you commit it, then follows the page again", () => {
+    const onPageChange = vi.fn();
+    render(
+      <Pager
+        page={0}
+        size={10}
+        total={100}
+        pageSizeOptions={[10, 25]}
+        onPageChange={onPageChange}
+        onSizeChange={() => {}}
+        sizeLabel="Rows per page"
+      />,
+    );
+    const box = screen.getByLabelText("datatable.pager.pageLabel");
+    fireEvent.change(box, { target: { value: "7" } });
+    expect(box).toHaveProperty("value", "7");
+    fireEvent.keyDown(box, { key: "Enter" });
+    expect(onPageChange).toHaveBeenCalledWith(6);
+    // The parent in this test never moves, so dropping the draft must put page 1 back — proof the
+    // box stopped holding its own copy rather than merely being overwritten.
+    expect(box).toHaveProperty("value", "1");
+  });
+
+  it("discards an unparseable entry instead of committing it", () => {
+    const onPageChange = vi.fn();
+    render(
+      <Pager
+        page={2}
+        size={10}
+        total={100}
+        pageSizeOptions={[10, 25]}
+        onPageChange={onPageChange}
+        onSizeChange={() => {}}
+        sizeLabel="Rows per page"
+      />,
+    );
+    const box = screen.getByLabelText("datatable.pager.pageLabel");
+    fireEvent.change(box, { target: { value: "abc" } });
+    fireEvent.blur(box);
+    expect(onPageChange).not.toHaveBeenCalled();
+    expect(box).toHaveProperty("value", "3");
+  });
+});

frontend/src/components/ui/Pager.tsx

@@ -1,4 +1,4 @@
-import { useEffect, useState } from "react";
+import { useState } from "react";
 import { useTranslation } from "react-i18next";
 import { ChevronLeft, ChevronRight } from "lucide-react";
 import { hasPagerContent, pageCount } from "./pagerContent";
@@ -34,9 +34,13 @@ export default function Pager({
   const totalPages = pageCount(total, size);
   const safePage = Math.min(page, totalPages - 1);
 
-  // Local text for the editable "jump to page" box (committed on Enter/blur).
-  const [pageInput, setPageInput] = useState(String(safePage + 1));
-  useEffect(() => setPageInput(String(safePage + 1)), [safePage]);
+  // Local text for the editable "jump to page" box (committed on Enter/blur). `null` means "not
+  // being edited", so the box simply DERIVES the current page instead of holding a copy that an
+  // effect has to re-sync after every page change — one render instead of two, and no window in
+  // which the box shows the page you just left. The draft is dropped on commit, which is the only
+  // place the two can disagree: clicking any other pager control blurs the input first.
+  const [draft, setDraft] = useState<string | null>(null);
+  const pageInput = draft ?? String(safePage + 1);
 
   // Turning the page — or resizing it, which re-slices from a different first item — swaps the whole
   // list, so put the reader at its top; landing mid-list in a page you haven't seen is disorienting.
@@ -51,8 +55,10 @@ export default function Pager({
   }
   function commitPageInput() {
     const n = parseInt(pageInput, 10);
+    // Dropping the draft either way is what makes the box follow the real page again — on a valid
+    // jump because the page moves to it, on garbage because there is nothing to commit.
+    setDraft(null);
     if (!isNaN(n)) goToPage(Math.min(totalPages - 1, Math.max(0, n - 1)));
-    else setPageInput(String(safePage + 1));
   }
 
   if (!hasPagerContent(total, size)) return null;
@@ -75,7 +81,7 @@ export default function Pager({
               min={1}
               max={totalPages}
               value={pageInput}
-              onChange={(e) => setPageInput(e.target.value)}
+              onChange={(e) => setDraft(e.target.value)}
               onBlur={commitPageInput}
               onKeyDown={(e) => e.key === "Enter" && commitPageInput()}
               aria-label={t("datatable.pager.pageLabel")}

frontend/src/components/ui/Toaster.tsx

@@ -89,10 +89,12 @@ export default function Toaster({
   // AFTER the snapshot above has read the outgoing host's screen — this host's own first render as
   // top would otherwise overwrite the handover with the toasts it is about to classify. Writing the
   // same value twice is harmless; that is the point of the ref.
+  // eslint-disable-next-line react-hooks/globals -- the handover between toast hosts is module-level BY DESIGN and must be written during render — see the 12 lines above, which record why a useMemo produced the wrong answer under StrictMode. The write is idempotent, which is what makes a repeated render invocation safe.
   if (isTop) lastTopIds = toasts.map((n) => n.id);
   const [armed, setArmed] = useState(false);
   useEffect(() => {
     if (!isTop) {
+      // eslint-disable-next-line react-hooks/set-state-in-effect -- arming is a TIMER, not derived state: the live region must be mounted and empty for a tick before content lands in it or a screen reader never announces the first toast. Deriving `isTop && armed` would let a host that regains top skip that tick.
       setArmed(false);
       return;
     }
@@ -196,6 +198,10 @@ export default function Toaster({
       </div>
       {isTop && Docked && (
         <div className="pointer-events-auto w-max max-w-full">
+          {/* lib/toastDock is a one-slot registry: this identity changes only when a surface docks
+              or undocks, and remounting is then the correct behaviour, not the hazard the rule
+              warns about. */}
+          {/* eslint-disable-next-line react-hooks/static-components */}
           <Docked />
         </div>
       )}

frontend/src/components/ui/anchoredPopoverHooks.ts

@@ -143,6 +143,7 @@ export function useAnchoredPopover(opts: AnchoredPopoverOptions) {
   // menu opens; clear it whenever the surface closes.
   useEffect(() => {
     if (!opts.open) {
+      // eslint-disable-next-line react-hooks/set-state-in-effect -- both indices are also floating-ui's list-navigation state (passed to useListNavigation below), so they cannot be derived from `open` without lying to the library about where the cursor is. Clearing on close is what stops a stale row stealing the next open's initial focus.
       setActiveIndex(null);
       setHoverIndex(null);
     }

frontend/src/components/ui/sortableA11y.ts

@@ -61,6 +61,11 @@ export function useSortableA11y(describe: (id: UniqueIdentifier) => SortableSubj
         },
         onDragOver: ({ active, over }) => {
           if (!over || (!moved && over.id === active.id)) return undefined;
+          // `moved` is per-DRAG state, and the announcement closures capturing it is the point:
+          // dnd-kit reports the item over ITSELF in the pick-up tick (see above), and this flag is
+          // the only thing separating that from a real move. A ref would be the wrong lifetime —
+          // one drag, not the component.
+          // eslint-disable-next-line react-hooks/immutability
           moved = true;
           return t("common.dnd.movedOver", landing(active.id, over.id));
         },