[tonyalaribe]

Choosing Free in the plan picker (pricingUpdateH, no order id) cleared sub_id but never cancelled the Stripe/LemonSqueezy subscription, so the customer kept being billed. It now calls cancelProjectSubscription first (an already-ended Stripe sub 404s and is logged at info).

Test: freePlanChoice_cancelsTheRunningStripeSubscription (Stripe Billing specs 15/15).

🤖 Generated with Claude Code

[claude]

Review: LGTM, one simplification.

• Pages/Projects.hs: project is already bound by Projects.sessionAndProject pid at the top of pricingUpdateH, so whenJustM (Projects.projectById pid) (...) is an extra DB query and an unneeded Maybe. Use Settings.cancelProjectSubscription envCfg project instead. That's shorter, and the cancel then acts on the same snapshot that handleOnboarding uses.
• Ordering: cancelling before updatePricing is the right call. The provider call is best-effort, because failures are logged at attention level and never thrown, so a provider outage can't block the downgrade. The cost is that a failed cancel leaves the sub billing with no sub_id pointing at it. The logAttention line is what surfaces that, and it's adequate.
• Test: covers the Stripe path and the resulting Free plan. It's a good regression guard. Optionally add a LemonSqueezy case, since cancelProjectSubscription branches on provider. That's low priority.

🤖 Generated with Claude Code