My Jetpack: Change Jetpack AI product page limit handling

[CGastrell]

Proposed changes:

Add a notice for unlimited plans over fair usage on Jetpack AI product page
Show current period request count alongside the already all time requests count on Jetpack AI product page
Remove unnecessary conditional to determine if user is on unlimited plan

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

p1724872002295049/1724866663.901329-slack-C054LN8RNVA

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

No

Testing instructions:

Sandbox the public API. Disable the tier plans and set the licensed amount above the usage limit (refer to D159560-code for setting up an unlimited plan over limit).

Go to My Jetpack and user the "View" button on Jetpack AI card to get to the product page.
There should be new card showing current period request count
There should be a notice stating when the next period reset will happen and inviting to upgrade

Enabling tier plans again should show remaining requests (default) instead of current period usage.

Exception to unlimited plans: there should be no upgrade button.

[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 WordPress.com Simple 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, and enable the change/jetpack-ai-product-page-limit-handling branch.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack change/jetpack-ai-product-page-limit-handling
  

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 Team 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 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[lhkowalski]

Code looks good and is working nicely.

With tiers disabled, over the limit, I see this (both monthly and all time counter):

Still with tiers disabled, but under the limit, I see this (the notice is gone, as expected):