Jetpack AI: Update sidebar fair usage messaging

[lhkowalski]

Proposed changes:

• Move the AI Assistant sidebar fair usage message up, at the top of the sidebar
• Add fair usage message to the AI Assistant block inspector (design proposed it over the block description, but I think we can only show it under the description, so I proceeded this way)
• Change sidebar fair usage message style to a "muted" version (plan text, greyed style), as per proposed design
• Fix the colors of the links on the fair usage message so they follow the same color as the text around them

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

p1HpG7-tUE-p2

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

Testing instructions:

• Run this branch on your testing site
• Sandbox the public-api domain and change the 0-sandbox.php file to add the following filters, so we simulate an unlimited plan over the fair usage limit:

add_filter( 'jetpack_ai_tier_licensed_quantity', function() { return 1; } );
add_filter( 'jetpack_ai_current_period_requests_count', function() { return 3001; } );

• On all test cases below, confirm the UI you see matches the proposed design from p1HpG7-tUE-p2 and the links on the messages are using the same color of the text
• Go to the block editor
• Confirm the fair usage message is showing correctly on the Jetpack sidebar and the post sidebar, following the proposed design:

• Add an AI Assistant block
• Confirm the fair usage message is showing correctly on block inspector, following the proposed design:

• Now let's confirm the link colors on already existing messages
• Add an image block and click the "Generate with AI" button; confirm the link on the fair usage limit message is in the same color as the message text:

• Add an AI Assistant block; confirm the link on the fair usage limit message above it is in the same color as the message text

• Go to the post settings sidebar and look for the excerpt tool; confirm the link on the fair usage limit message is in the same color as the message text

• Go back to the 0-sandbox.php file and change the filters to:

add_filter( 'jetpack_ai_tier_licensed_quantity', function() { return 1; } );
add_filter( 'jetpack_ai_current_period_requests_count', function() { return 2900; } );

• Confirm the fair usage messages are gone

[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 update/jetpack-ai-update-sidebar-fair-usage-messaging branch.

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

  bin/jetpack-downloader test jetpack update/jetpack-ai-update-sidebar-fair-usage-messaging
  

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!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen daily.
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for September 3, 2024 (scheduled code freeze on September 2, 2024).

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[dhasilva]

LGTM