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/app/api/admin/provider-health/__tests__/route.test.ts

@@ -207,7 +207,7 @@ describe("GET /api/admin/provider-health", () => {
   });
 
   /**
-   * v1.38.19 (Wave E) — the two spend figures side by side.
+   * v1.38.19 — the two spend figures side by side.
    *
    * The operator reads this card when the chat refuses. Until now it showed
    * delivery health only, and the day's token figure was one number that mixed

src/app/api/admin/provider-health/route.ts

@@ -111,7 +111,7 @@ export const GET = apiHandler(async () => {
     return a.providerType.localeCompare(b.providerType);
   });
 
-  // v1.38.19 (Wave E) — the day's spend, split by who pays for it.
+  // v1.38.19 — the day's spend, split by who pays for it.
   //
   // The operator opens this card when a surface refuses on budget. One mixed
   // number could not answer the question it raised: a day at 1.24 M tokens is