Price change complications

🔍 Problem Statement

Changing subscription prices in Pelcro is complex and error-prone. Past incidents include automation bugs where scheduled billing phases were not respected after a price update, and the Core API's batch update limitations have forced teams to fall back on direct Stripe API calls — bypassing Pelcro's control layer and creating reconciliation risk.

💡 User Story

As a Pelcro admin, I want a reliable, first-class way to change subscription prices through Pelcro, so that pricing updates are applied correctly on the next billing cycle, scheduled phases are honoured, and no direct Stripe API intervention is ever needed.

🎯 Definition of Done (DoD)

A feature is done when:

✔️ Given an active subscription with an existing price, when an admin applies a price change through the Pelcro admin interface or API, then the updated price takes effect on the correct billing cycle, all scheduled phases continue to be respected, and the change is fully completed without requiring any direct Stripe API calls or manual workarounds.