docs(ai): drop planning vocabulary from the ledger comments

CLAUDE.md forbids planning shorthand in committed artefacts, and this branch
introduced 74 lines of it across source, tests, a schema field and two
migrations. Someone reading the migration SQL in a year has no way to resolve a
wave letter or a round number, and a comment that points at something outside
the repository names no reason at all.

Three passes. A version followed by a parenthetical keeps the version and loses
the parenthetical, because the version says since when something holds. A
sentence that leaned on the vocabulary to carry its meaning is rewritten to
state the reason directly: the arrival reservation now says it was refused over
money the operator never spent, rather than naming the defect a wave existed to
remove. Three test titles carried the marker in the name itself and are renamed
to what they pin.

Comments only. No behaviour, no renames beyond those three titles.
This commit is contained in:
Marc-André Bombeck committed 2026-09-11 12:37:54 +02:00
1 parent c66bcbc295
commit b565edc48d
30 files changed
+86 -84

No files matched your search

+1 -1
View File
@@ -278,7 +278,7 @@ export async function maybeAutoStageLabFacts(
// A text-structuring pass, not a vision call — reserve the proportionate
// ceiling under the cost owner the auto-index resolved.
// v1.38.19 (Wave E) — auto-staging runs off the upload, with no one waiting
// v1.38.19 — auto-staging runs off the upload, with no one waiting
// on it: a background surface, so half the day's ceiling.
const dateKey = buildDateKey();
const reservation = await reserveBudget(
+2 -2
View File
@@ -131,7 +131,7 @@ export interface ResolvedIndexProvider {
consentOk: boolean;
dailyCap: number;
/**
* v1.38.19 (Wave E) — whose budget `dailyCap` rations. The reservation books
* v1.38.19 — whose budget `dailyCap` rations. The reservation books
* `operator_tokens` only for an operator-funded pick, so the cap and the
* counter it is compared against are resolved from one place.
*/
@@ -168,7 +168,7 @@ export async function resolveIndexProvider(
pick && consentOk
? resolveDailyCap([{ providerType: pick.entry.providerType }])
: 0;
// v1.38.19 (Wave E) — the cap and its cost owner are resolved from the SAME
// v1.38.19 — the cap and its cost owner are resolved from the SAME
// pick, so the reservation books the counter the cap is enforced against.
const costOwner: BudgetCostOwner =
pick && consentOk