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
@@ -43,7 +43,7 @@ vi.mock("@/lib/logging/context", () => ({
annotate: vi.fn(),
}));
// v1.38.19 (wave D) — the four preconditions the honest offer rides on.
// v1.38.19 — the four preconditions the honest offer rides on.
vi.mock("@/lib/ai/server-provider-health", () => ({
readServerProviderHealth: vi.fn(),
}));
@@ -441,7 +441,7 @@ describe("GET /api/user/ai-provider — the gateway's fields (#470)", () => {
});
/**
* v1.38.19 (wave D) — the honest shared-provider offer.
* v1.38.19 — the honest shared-provider offer.
*
* The setup flow's last screen used to promise that insights "work for you
* right away" whenever `managedBy` said `server`. That is a presence read:
+3 -3
View File
@@ -42,7 +42,7 @@ export const GET = apiHandler(async () => {
aiCompatModel: true,
// v1.22 (#89)
aiResponseTimeoutSeconds: true,
// v1.38.19 (wave D) — a managed profile is never the party that gives
// v1.38.19 — a managed profile is never the party that gives
// consent for itself; the offer below has to know.
managedProfileAt: true,
},
@@ -55,7 +55,7 @@ export const GET = apiHandler(async () => {
// `managedBy` reports the origin only; no admin keys/endpoints are leaked.
const { aiAvailable, managedBy } = await resolveProviderAvailability(user.id);
// ── v1.38.19 (wave D) — the shared provider, honestly ────────────────
// ── v1.38.19 — the shared provider, honestly ────────────────
// `managedBy: "server"` says the operator configured a key. It has never
// said the key WORKS, and the setup flow spent three releases promising
// that it did. It also says nothing about the consent receipt
@@ -125,7 +125,7 @@ export const GET = apiHandler(async () => {
hasCompatKey: Boolean(u?.aiCompatKeyEncrypted),
// v1.22 (#89) — per-user response timeout, in seconds (null = default).
responseTimeoutSeconds: u?.aiResponseTimeoutSeconds ?? null,
// v1.38.19 (wave D) — see the block above. A tri-state and two booleans;
// v1.38.19 — see the block above. A tri-state and two booleans;
// no count, no timestamp and no other account is inferable from them.
serverProviderHealth,
serverProviderOffer,