Subscription intent output schema restructured; effectiveBehavior now required
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The output object for subscription plan-change intents has been significantly restructured. The changedResources items previously used a oneOf with four distinct typed variants (set_plan_item_quantity, increase_plan_item_quantity, decrease_plan_item_quantity, adjust_plan_item_quantity) — each with its own type discriminator and required fields — and have been collapsed into a single unified object schema. The type discriminator field is gone, resourceIds semantics changed, and the new field effectiveBehavior ("end_of_term" | "immediate") has been added to the output required fields, meaning any client that previously relied on the oneOf variant shapes or omitted effectiveBehavior will break.