v3: comments say what the code can't — the documentation pass wanted JSDoc on every export and every field of an exported interface, which filled the code with restatements ("The dump.", "Whether it is loading.", "The props of X.", "Renders the X.") and module docs that told a reader nothing ("The hot and new feeds, and the props every main feed of the index takes."); some were wrong as well as vague. Every comment in api/, shared/ and src/ is rewritten under one rule, now stated in the README's "Comments" section: every module and export still has a JSDoc, and it gives context (who uses it and where), usage (what a caller must know: a precondition, what it leaves to the caller, a side effect) or its place in the chain (where its input comes from, where its output goes); a field, parameter, private function or local gets one only when it adds to its parent's, and context about a whole type goes on the type; a type's doc is phrased from the value's side ("Returned to Y by X when Z", "Passed to Y by X"); full sentences, as short as they can be, no label-colon-list; // goes wherever the code isn't obvious and says why, and the section banners and narration go. Every claim was checked against the code, which turned up some forty comments that were wrong: DumpCard's claimed it was only used by the hot and new feeds, the WebSocket welcome claimed to be a socket's first message (presence comes first), UpdateUserRequest said null removes a description (it keeps it), deletedDumpIds leaves out that it also holds dumps made private, THEME_COLOR claimed to mirror index.html's, and the like. The routers' JSDoc now says where they are mounted and what becomes of a thrown APIException. doc-lint.ts lets a field without a doc through; a module or export without one still fails. No code changes; 204 backend and 628 frontend tests pass, and doc:lint, deno check, deno lint and tsc are clean.

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

src/components/feed/JournalFeed.tsx

@@ -1,5 +1,6 @@
 /**
- * The journal feed: the editorial mosaic.
+ * The "journal" tab of the index page, which lays the feed out as a mosaic of
+ * tiles of several sizes.
  *
  * @module
  */
@@ -13,8 +14,9 @@ import { composeJournal } from "../../utils/feed/journalLayout.ts";
 import type { MainFeedProps } from "./DumpFeed.tsx";
 
 /**
- * Renders the dumps as the journal's mosaic, block by block, loading more at
- * its end.
+ * Renders the feed `Index` passes as blocks of {@link JournalCard}, laid out
+ * by `composeJournal`, followed by the infinite-scroll sentinel. It also
+ * renders the loading, error and empty states.
  */
 export function JournalFeed(
   {
@@ -52,10 +54,9 @@ export function JournalFeed(
   return (
     <>
       {
-        /* Each sub-block is its own grid, with a themable <hr> between them.
-          A break sits between two grids rather than inside one because a grid
-          item would be stretched to the 9rem row track — out here its height
-          is its own, down to nothing for a theme that wants no separation. */
+        /* Each block is its own grid, with a themable <hr> between them. Inside
+          a grid the <hr> would be stretched to a 9rem row, while out here a
+          theme can shrink it to nothing. */
       }
       <div className="journal-feed">
         {blocks.map((block, index) => (