docs: comments name what the code does, not how it was built

Thirty-one files carried internal build vocabulary and anchors pointing at
notes that are not in the repository: a reader of `checklist.ts` in a year
would find its rationale keyed to a research id they cannot open, inside a
comment that also names an internal build stage. Two test titles carried the
same anchors.

The version tags and the whole of the reasoning stay; only the vocabulary and
the dangling references go, with the few sentences that were built around an
anchor rewritten to stand on their own.
This commit is contained in:
Marc-André Bombeck committed 2026-09-11 11:03:04 +02:00
1 parent bdc23f34ff
commit 41596d1cb8
31 files changed
+63 -64

No files matched your search

+1 -1
View File
@@ -559,7 +559,7 @@ const aiProviderResponse = z
.describe(
"v1.22 (#89) — per-user response timeout for AI generation, in seconds (10–600). Null = the built-in comprehensive-briefing default (~120 s). Mainly for slow local/self-hosted backends.",
),
// v1.38.19 (wave D) — the setup flow's last screen used to promise
// v1.38.19 — the setup flow's last screen used to promise
// that insights "work for you right away" as soon as `managedBy` read
// `server`. That is a presence read; it never knew whether the key
// worked, and it said nothing about the consent receipt the egress