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

@@ -347,7 +347,7 @@ describe("/api/integrations/status — the freshness read failed", () => {
});
/**
* v1.38.19 (wave B / I5) — the never-connected provider on the wire.
* v1.38.19 — the never-connected provider on the wire.
*
* The ledger's synthetic "no row" snapshot reads `unknown`, and the envelope
* publishes it verbatim. A client that reads `state` must see a value that