Search Dashboard: Hide AI Agent Access on P2 sites

[kat3samsin]

Fixes #

Proposed changes

• Hide the Search dashboard AI Agent Access control on P2 / WP for Teams sites by including Status\Host::is_p2_site() in the initial-state availability flag.
• Add PHP coverage for the P2 availability gate, including the non-P2 public-site control path.
• Add a Search package changelog entry.

Related product discussion/links

• Internal Slack discussion.

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

No.

Testing instructions

• jetpack test php packages/search -v
• cd projects/packages/search && pnpm test-scripts
• jetpack test php packages/sync -v
• jetpack changelog validate packages/search
• On a P2 WPCOM site, load the Jetpack Search dashboard and confirm the AI Agent Access toggle is absent.
• On a public non-P2 WPCOM site, confirm the AI Agent Access toggle is still available.

Notes

• Automattic\Jetpack\Status\Host::is_p2_site() exists in projects/packages/status/src/class-host.php and checks the local WPCOM site ID plus the P2/WP for Teams signals.
• This PR only hides the Jetpack Search dashboard control. The paired WPCOM PR enforces the backend Search Voice / AI Agent Access P2 rejection.

[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), and enable the codex/search-voice-no-p2 branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack codex/search-voice-no-p2

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