- Shipped
- September 7, 2026 at 12:42 AM UTC
- Author
- Kamo
- Commit
- ebb1911
The reconciler compared mapped prices against the catalogue and returned early whenever nothing was mapped at all. So a term the catalogue had gained since the prices were first created was reported by nothing, forever. On KamoCRM that was every TRIENNIAL price: the plans are priced at $49 and $99 on three years, the picker offers the term, and the only thing that would ever have created the Stripe price was somebody actually buying it. That still sold — resolvePlanPriceId creates a missing price on demand — but it created it INSIDE the customer's own transaction. Six Stripe objects built while somebody waits on a Confirm button, where a hiccup surfaces as a refused purchase rather than as a background job to retry. An unmapped price is now reported as its own kind of fault, distinct from drift, so a reader can tell "pointing at the wrong number" from "pointing at nothing". And an apply run calls getOrCreatePricesForOrg first — idempotent, it skips everything that exists — which turns "this term cannot be sold until somebody buys it" into a job that has already run. Found while applying the repoint the audit called for: the drift report came back clean afterwards, and clean was not the same as complete. 299 tests green, 2 added.