Episodes stats: surface 402 from podcast stats endpoint as a Premium-required state

[robertbpugh]

Fixes PODS-146 (client half).

Proposed changes

• useEpisodeStatsQuery now returns { data, premiumRequired }. A 402 from the wpcom episode stats endpoint flips premiumRequired to true, clears data, and stops further chunk requests for that key. Other errors propagate as before.

Related product discussion/links

• PODS-146 (tracking), PODS-145 (sibling dashboard-tab gate that will consume premiumRequired and render the shared upsell card).

Scope note for the reviewer

PODS-145 hides the Episodes tab on a non-Premium snapshot, so the hook usually never fires. This 402 path is defense-in-depth for stale snapshots and grandfather races, and no UI consumer wires the flag in this PR. PODS-145 owns that.

Does this pull request change what data or activity we track or use?

No.

Testing instructions

• Today's behavior is unchanged on Premium and on grandfather-stickered Free.
• To verify the 402 path once the server half ships:
  1. On a Free site without the podcasting-grandfathered sticker, open the podcast episode dashboard.
  2. In DevTools, confirm /wpcom/v2/sites/<id>/podcast-stats/episode-totals returns 402 with code: podcast_premium_required.
  3. Confirm the error boundary does not trigger and the table renders without plays or duration.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the pods-146-client-gate-stats-on-premium branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack pods-146-client-gate-stats-on-premium

bin/jetpack-downloader test jetpack-mu-wpcom-plugin pods-146-client-gate-stats-on-premium

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report