Fix Create AI Podcast free credit copy

[mmtr]

Fixes #

Proposed changes

• Update the Create AI Podcast credits UI to treat resetsAt: "never" as a one-time free trial credit.
• Stop showing reset/trial text next to the remaining-credit count when credits never reset.
• Show an upgrade banner that explains the free trial is limited to one generated podcast.

Related product discussion/links

• Follow-up to Refine post-publish podcast promo modal #48950 testing flow.

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

No.

Testing instructions

• Apply these changes to your WP.com site.
• Use a free site where the Posts to Podcast quota endpoint returns resetsAt: "never".
• Go to Media > Create AI Podcast.
• Confirm the credits card says 1 remaining without any reset or trial text next to it.
• Confirm an upgrade banner appears below the credits meter with copy explaining that the free trial is limited to one podcast.
• Generate one podcast, or use a free site where the trial credit has already been used.
• Reload Media > Create AI Podcast.
• Confirm the out-of-credits banner says the one-time trial credit has been used and prompts the user to upgrade for more credits.
• Confirm paid plans with a real resetsAt timestamp still show the relative reset copy, for example Resets in 12 days.

[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 (WordPress.com Site Helper), and enable the fix-create-ai-podcast-free-credit-copy branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack-mu-wpcom-plugin fix-create-ai-podcast-free-credit-copy

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