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.

src/components/admin/__tests__/provider-health-spend-today.test.tsx

@@ -4,7 +4,7 @@ import { renderToStaticMarkup } from "react-dom/server";
 import { I18nProvider } from "@/lib/i18n/context";
 
 /**
- * v1.38.19 (Wave E) — the day's spend, split by who paid for it.
+ * v1.38.19 — the day's spend, split by who paid for it.
  *
  * `/api/admin/provider-health` answers `spendToday` and nothing rendered it,
  * which is the "the reader is the follow-up" shape the two-ended rule exists to

src/components/admin/provider-health-section.tsx

@@ -27,7 +27,7 @@ import { formatDateTime } from "@/lib/format";
  */
 
 /**
- * v1.38.19 (Wave E) — the day's spend, split by who pays for it. The operator
+ * v1.38.19 — the day's spend, split by who pays for it. The operator
  * opens this card when a surface refuses on budget, and one mixed number could
  * not answer the question that raises: a day at 1.24 M tokens is alarming until
  * you see that 151 200 of them were the instance's own key and the rest ran on