test(e24): close the review's coverage gaps, and correct a comment that was untrue

`test_only_a_show_row_pays_for_a_resolution` seeded no watch state, so every rail query
inner-joined its way to zero rows and the loop body — with it the assertion — never ran. It
now seeds a video, a movie and an episode, and asserts all three kinds are present before
the loop, so it cannot go vacuous again.

The Plex half of the surprise rail had no test for either of its promises: every test that
reached `plex_surprise` passed budget="any" against a library with no state rows, so the
duration bounds and the already-started exclusion could both be deleted with the suite
green. The YouTube half has had tests for the same two rules since S1 — the asymmetric half
of one principle.

`plex_item` and `plex_show` — two of the five pinnable kinds — were pinned by no test at
all, leaving the rating_key → internal-id translation and both shelf arms uncovered,
including the self-reference cycle that once 500'd the shelf. And `GET /api/discover/pick`
was exercised only through its domain function, so the route's own query-string translation
could regress silently; the new test excludes all three candidates, which is what proves the
whole list parsed rather than one unsplit string.

`PIN_COLUMNS`/`PIN_KINDS` claimed in a comment to be the one place the pin vocabulary is
spoken and had no readers anywhere: `resolve_ref` re-spelled the column names and the route
re-typed the kind list. Both now drive off the constants.

The `_NO_TS` sentinel was introduced as a crash fix and is not one. The key it replaced,
`(ts is not None, ts)`, cannot raise — tuple comparison finds the first UNEQUAL element via
`==`, so two null keys compare equal and `None < None` is never reached; three independent
runs confirmed it over every permutation. The rationale now says what the sentinel actually
buys, lives once in `plex.rollup`, and the third rail that was still on the older spelling
has been swept to match. Its test is renamed and re-scoped to the mutation it does catch.

Frontend: the reroll's second press asserted `expect.any(Array)`, which cannot tell an
accumulating exclusion window from a replacing one — both that and SEEN_WINDOW = 1 (each
reinstating the measured nine-card cycle) left the suite green. And `onInfo`'s jump type was
untested while `onPlay`'s was pinned twice, so pointing the ⓘ affordance at the player
typechecked and shipped green.

All eight fixes mutation-checked; every mutant died on its intended test.

frontend/src/components/Home.dom.test.tsx

@@ -443,6 +443,31 @@ describe("Home", () => {
     expect(setPage).toHaveBeenCalledWith("plex");
   });
 
+  it("sends the ⓘ affordance to the item's page, not to the player", async () => {
+    // `onInfo` and `onPlay` differ by one ternary arm, and confusing them is the defect the play
+    // test above was written for — but only `onPlay` was pinned, so swapping ⓘ's "movie" for "play"
+    // typechecked (both are members of `PlexJumpTarget["type"]`) and shipped green. ⓘ is the one
+    // action on this surface a user presses precisely because they do NOT want to start watching.
+    const movie = {
+      ...ytCard("m1", "A Film"),
+      source: "plex",
+      kind: "movie",
+      aspect: "poster",
+      video: null,
+      plex: { id: "m1", type: "movie", title: "A Film", thumb: "" },
+    };
+    discover.mockResolvedValue({
+      budget: "any",
+      hero: null,
+      continue_watching: [movie],
+      comfort: [],
+    });
+    mount();
+    fireEvent.click(await screen.findByLabelText("plex.info.title"));
+    expect(setJumpTo).toHaveBeenCalledWith({ id: "m1", type: "movie", replace: true });
+    expect(setPage).toHaveBeenCalledWith("plex");
+  });
+
   it("rotates the tier on each press so the button offers a different KIND of answer", async () => {
     // Measured 2026-09-06: exclusion alone left it walking the resume rail and cycling nine cards,
     // never once reaching the shelf. The press count travels to the server as the rotation.
@@ -462,7 +487,11 @@ describe("Home", () => {
       expect(discoverPick).toHaveBeenLastCalledWith(
         "any",
         expect.any(Number),
-        expect.any(Array),
+        // The exact list, not `expect.any(Array)`: the window has to ACCUMULATE. A one-element list
+        // is identical whether it accumulates or replaces, so the first press cannot tell them
+        // apart — and with the loose matcher both "replace, never grow" and SEEN_WINDOW = 1 (which
+        // reinstate the measured nine-card cycle) left the whole suite green.
+        ["youtube:v1", "youtube:v9"],
         2,
       ),
     );