v3: every paged list loads its pages one way, PlaylistDetail is split like the profile, and the comments keep the README's rules — Index, FollowedFeed, useUserDumpFeed, UserPlaylists, UserListPopover, Notifications, Search and the profile's followed users each hand-wrote "fetch the next page, append it, clear loadingMore on failure". A list the API pages is now a PagedList whose next page useLoadMore appends, and a list that loads on its own goes through usePagedList, which is useFetchState (now taking an initial value, as a restored cache, that starts loaded) plus useLoadMore. Pages are read by pageUrl with readPage (a refusal throws) or readFirstPage (a refusal is empty, as fetchFirstPage was), signed-in reads go through authFetch, and useFeedCache's saveState takes the list. Notifications keeps the socket's arrivals as their own list merged at render, as Index does with recentDumps, and marks them read in one effect. PlaylistDetail (963 lines) only puts the pieces together (146): usePlaylist holds the playlist, its live sync and its edits, PlaylistHeader, PlaylistEditForm and PlaylistDumpList are one file each, and LiveDumpCard is the vote wiring DumpCardList and the playlist both use. What it re-invented is shared: the load is useFetchState, a dump going private and back is usePositionAwareSync, deletes and edits are useDumpListSync (which also keeps comment counts, which the page didn't). A removal is sent when its fade ends, or as the page is left, so an undo sends nothing: the removal/re-add/reorder dance, the pending-undo order and the 80 ms debounce of its echoes are gone. A refused reorder goes back to the server's last order and says so, instead of reloading the page. The comments written since the documentation pass broke its rules in places: module docs as a label and a colon ("The "dumps" tab of a profile: …"), noun-phrase fragments on types, fields and constants, stale lists of callers, over-long lines; they are sentences now, and the ones the refactor made wrong (PlaylistDetail as useFading's and FollowPlaylistButton's caller, "the profiles" as usePositionAwareSync's only users) say what is true. 650 frontend and 214 backend tests pass (new: usePagedList, useFetchState's initial, pageUrl/readPage, the deferred removal, a dump returning at its place in a playlist), and tsc, eslint, doc:lint, deno check, deno lint and deno fmt are clean.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/contexts/theme/ThemeContext.ts

@@ -8,9 +8,9 @@
 import { createContext } from "react";
 
 /**
- * Every site style, which `ThemeProvider` checks a stored choice against. Each
- * has a stylesheet under `src/themes/`, keyed on the root element's
- * `data-style`, which is absent for "smooth".
+ * Lists every site style, which `ThemeProvider` checks a stored choice
+ * against. Each has a stylesheet under `src/themes/`, keyed on the root
+ * element's `data-style`, which is absent for "smooth".
  */
 export const STYLE_NAMES = [
   "smooth",
@@ -20,12 +20,12 @@ export const STYLE_NAMES = [
   "kanagawa",
   "melange",
 ] as const;
-/** One of {@link STYLE_NAMES}. */
+/** Held by `ThemeProvider` for the style chosen in this browser. */
 export type StyleName = typeof STYLE_NAMES[number];
 
-/** Every color scheme; "auto" follows the system's. */
+/** Lists every color scheme. "auto" follows the system's. */
 export const COLOR_SCHEMES = ["auto", "light", "dark"] as const;
-/** One of {@link COLOR_SCHEMES}. */
+/** Held by `ThemeProvider` for the color scheme chosen in this browser. */
 export type ColorScheme = typeof COLOR_SCHEMES[number];
 
 /**