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

@@ -2,7 +2,7 @@
* Structural guard — `coach_usage.total_tokens` and `coach_usage.operator_tokens`
* move together in EVERY raw statement.
*
* v1.38.19 (Wave E) gave the daily ledger a second counter: `operator_tokens`
* v1.38.19 gave the daily ledger a second counter: `operator_tokens`
* is the share of `total_tokens` an operator-funded provider served, and the
* operator ceiling is enforced against it. The counters are only meaningful
* while they stay in step. A statement that writes the total and forgets the
@@ -10,7 +10,8 @@
* reverses the total and forgets the operator share leaks budget permanently
* toward the operator cap, because nothing else ever subtracts it; a statement
* that RETURNS the total alone forces its caller to gate on the wrong number,
* which is the exact defect the wave exists to fix.
* which is how an operator-funded chain ends up refused over tokens the user's
* own plan paid for.
*
* Two of the three writers shipped with precisely those bugs, and both were a
* grep away. This guard is that grep, executable: every INSERT column list,