chore(comments): drop epic, sprint and review-round ids from the code

The code cited its plan instead of saying why: `E28 review J4`, `(R6 S3b)`, `S1 justified…`, `deep-review round 5`. That plan lives in the private ops repo, so for every reader of this one the citation was noise, and a sentence whose subject was the plan step ("round 2 showed…") hid its lesson behind an id. Each one is gone and the "why" kept: a bare citation is deleted, a sentence carrying a lesson is reworded around it ("a later attempt showed…"). Measured (`scripts/audit_metrics.py`, product code): 652 lines in 270 files carried an epic code by the definition the next commit holds (507 / 241 by the old, two-digit-only one) -> 0. Across all code, tests, scripts and configs: ~1100 epic-code lines plus ~320 sprint/round ids. Behaviour unchanged, checked mechanically: every changed .py file has the same AST once docstrings are blanked; css/sh/toml/yml/json files are identical once comments are stripped; the only non-comment changes in TS/JS are test titles, one description string in a contract table, and five ESLint messages, whose text is all the gates snapshot diff holds. Not touched: Markdown (docs and the changelog keep their history), Alembic migrations, TV episode notation (`S2 · E5`), DESIGN.md ids (`C1`, `B4`, `S3h`), tracker ids (`SEC-16`, `DX-17`). One stale claim fixed on the way: test_hls_reaper's docstring said the player checkpoints "every 10 s whether or not it is playing", which plex/stream.py calls wrong; it now says what the code does.
2026-10-05 00:19:39 +02:00
parent c73d8be094
commit 4aaaaa7860
669 changed files with 1831 additions and 1904 deletions
@@ -1,14 +1,14 @@
 import { describe, expect, it } from "vitest";

 // Every push that opens a new view over the current one remembers the list item it was opened from
-// (`lib/history.rememberNavPosition`), so Back hands focus back to that item (E11 S5). A push that
+// (`lib/history.rememberNavPosition`), so Back hands focus back to that item. A push that
 // forgets strands keyboard focus on <body> again with no test noticing — the flow only shows in a real
 // browser, after a round trip. So the source is the check: each `history.pushState(` in the app has a
 // `rememberNavPosition(` right before it or inside its arguments. The overlay stack's own push is the
 // one exception — an overlay entry opens no view, and its list stays mounted underneath.
 //
 // The assertion pins the SET of offending sites and checks the scan found pushes at all: a guard whose
-// glob stops matching is green over nothing (E10 review round 4).
+// glob stops matching is green over nothing.

 const files = import.meta.glob(["../**/*.ts", "../**/*.tsx", "!../**/*.test.*"], {
  query: "?raw",