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,4 +1,4 @@
-- v1.38.19 (Wave E) — the daily coach ledger gains a cost-owner dimension.
-- v1.38.19 — the daily coach ledger gains a cost-owner dimension.
--
-- `coach_usage` counted one number per (user, day), so tokens the USER's own
-- plan paid for (a `codex` fallback hop after the operator's shared key
@@ -1,4 +1,4 @@
-- v1.38.19 (Wave E, fix round 1) — the arrival reaction remembers who paid for
-- v1.38.19 — the arrival reaction remembers who paid for
-- its reservation.
--
-- The row persisted the reserved amount and the date key but not the cost
+2 -2
View File
@@ -6271,7 +6271,7 @@ model CoachUsage {
userId String @map("user_id")
dateKey String @map("date_key")
totalTokens Int @default(0) @map("total_tokens")
/// v1.38.19 (Wave E) — the share of `totalTokens` served by a provider the
/// v1.38.19 — the share of `totalTokens` served by a provider the
/// OPERATOR funds (`admin-openai` / `admin-codex`). The operator-cost cap is
/// enforced against this counter and the user-plan cap against
/// `totalTokens`, so background work served by the user's own plan can no
@@ -6761,7 +6761,7 @@ model ArrivalReaction {
/// `coach_usage` increment. A reclaimed pre-provider attempt reuses it.
generationReservedTokens Int? @map("generation_reserved_tokens")
generationBudgetDateKey String? @map("generation_budget_date_key")
/// v1.38.19 (Wave E) — who the reservation above was booked to, `"operator"`
/// v1.38.19 — who the reservation above was booked to, `"operator"`
/// or `"user"`. Persisted rather than recomputed: the supersede refund in
/// `data-arrival.ts` has no chain to ask, and the resume path's chain may
/// have been reordered by the health ledger since the reservation was made.