- Shipped
- August 11, 2026 at 12:49 AM UTC
- Author
- Kamo
- Commit
- e681793
The mapping stored only which price id to use, so a catalog price change could not even be noticed. ensurePlanPrices short-circuited on the row's existence and the unique key forbade a second one, which meant raising a plan from $72 to $79 updated the marketing page, the in-app quote and the plan DTO and changed nothing about what anybody was charged — with nothing reporting the divergence. unit_amount_cents and currency give the reconciler something to compare against. Both nullable and left NULL for existing rows: null means "unknown", which is true of every row predating the column, and treating unknown as mismatched would recreate every price in the estate on the first run.