fix(ui): the card's channel name is a real link too; call sites the bug hunt left untested now have tests

Deep-review R6 — the small items:

- The video card's channel name was still a <button> (pre-existing): ctrl/middle-click did nothing
  there while the title above it and the player's channel name honoured them. It renders through
  ChannelNameLink now, which grew a forwarded ref (the clamp measurement), pass-through attributes,
  a `tooltip`, and an opt-in `stopPropagation` so no click reaches the card's row.
- ChannelNameLink rendered an empty, still-tabbable <a> for a channel with no title yet (a stub first
  seen through a live search; pre-existing at this site). It falls back to the translated "Channel".
- The feed's SortKey→SortOption mapping existed twice in Feed.tsx; one `feedSortOptions` in
  feedSort.ts serves both modes (DIRECTIONLESS is module-private again).
- The backfill refresh's comment claimed a one-page cost. It refetches every loaded page of the
  grid, and that is the right price: backfilled videos are older, so they land below the head.

Tests for call sites that could be deleted with every lane green: the channel page running the
backfill refresh (knip had been blinded by the hook test's import), Feed handing the grid the live
results in the chosen key AND direction, the card using the link. Plus the alt-click arm of the shared
click predicate, and a plex filter-chip test that claimed it made no request while firing a real one.
Verified on localdev: the feed's channel names are anchors (same 14 px muted look), a plain click
opens the channel in-app. 7 mutations, each red on its assertion.

frontend/src/lib/feedSort.ts

@@ -2,6 +2,7 @@
 // …); the UI thinks in a key + direction. Kept here rather than inside Feed so the active-filter
 // chips can label a sort without re-deriving the mapping.
 import type { Video } from "./api";
+import type { SortOption } from "./columnSort";
 
 export type SortKey =
   | "date"
@@ -24,7 +25,7 @@ export const SORT_KEYS: SortKey[] = [
 ];
 
 /** Sorts with no meaningful asc/desc flip. */
-export const DIRECTIONLESS: SortKey[] = ["shuffle", "relevance"];
+const DIRECTIONLESS: SortKey[] = ["shuffle", "relevance"];
 
 const SORT_MAP: Record<Exclude<SortKey, "shuffle" | "relevance">, { asc: string; desc: string }> = {
   date: { desc: "newest", asc: "oldest" },
@@ -58,6 +59,20 @@ export function buildSort(key: SortKey, dir: "asc" | "desc"): string {
   return SORT_MAP[key][dir];
 }
 
+/** Feed sort keys as options for the shared SortControl. ONE mapping for the library feed and the
+ *  live search results, which share the vocabulary: two copies could hand the same key a different
+ *  direction default, or lose its directionless flag, depending on which mode you were in. */
+export function feedSortOptions(keys: SortKey[], label: (k: SortKey) => string): SortOption[] {
+  return keys.map((k) => ({
+    key: k,
+    label: label(k),
+    directionless: DIRECTIONLESS.includes(k),
+    defaultDir: DIRECTIONLESS.includes(k)
+      ? undefined
+      : SORT_DEFAULT_DIR[k as Exclude<SortKey, "shuffle" | "relevance">],
+  }));
+}
+
 // --- Live YouTube search results ----------------------------------------------------------------
 //
 // The results view had NO sort control at all — the order was the provider's and that was that. It is