Hi team,
I'm experiencing unexpected webhook behavior when using `DEFERRED` proration mode for Google Play subscription changes.
## Expected Behavior (per documentation)
According to the [Event Flows documentation](https://www.revenuecat.com/docs/integrations/webhooks/event-flows#product-change-at-period-end):
> In the case of a product change at period end, a PRODUCT_CHANGE event will immediately be sent informing of the upcoming product change. [...] When the customer encounters their next renewal, a RENEWAL event will be dispatched (for App Store subscriptions) or an **INITIAL_PURCHASE event (for Google Play subscriptions)**.
## Actual Behavior
When using `GoogleProrationMode.DEFERRED` for a product change on Google Play:
1. `PRODUCT_CHANGE` event is received (as expected)
2. At next renewal, **RENEWAL** event is received instead of **INITIAL_PURCHASE**
This contradicts the documentation which states Google Play should trigger `INITIAL_PURCHASE`.
Additionally, the `original_transaction_id` in the RENEWAL event is **different from the old subscription's original_transaction_id**. This suggests it's actually a new subscription (which should be INITIAL_PURCHASE), not a renewal of the existing one.
## Environment
- Platform: Android (Google Play)
- Framework: Expo (React Native)
- SDK: react-native-purchases ^9.1.0
- Proration mode: `DEFERRED`
- Environment: Sandbox
## Questions
1. Is this the intended behavior, or is this a bug?
2. If intended, should the documentation be updated to reflect this?
3. Are there any known differences between Sandbox and Production for this flow?
Any clarification would be appreciated. This affects how we handle subscription changes on our backend.
Thanks!
