Port Search package 7.0.0 changes back to trunk

[kangzj]

Fixes SEARCH-218

Proposed changes

This PR ports the Search package 7.0.0 release changes back to trunk. The 7.0.0 release includes:

Added

• Search: Add a "Compact" block style to the Clear Filters block, stopping it from inheriting oversized core Button block styling. [Search: lighter Clear Filters button + Compact block style (RSM-3507) #48946]
• Search: Add an AI Answer block (jetpack-search/ai-answer) so authors can surface the AI Answers panel inside the embedded search template. [Search: add an AI Answer block for the embedded search template (RSM-3591) #48986]
• Search: Make the Load More block match the theme's regular core/button look and add a "Compact" block style. [Search: theme button styling + Compact style for Load More (RSM-3588) #48984]
• Search: Surface "Enable search suggestions" and "Enable AI Answers" toggles in the search customizer's Additional settings panel. [Search: surface "Enable search suggestions" and "Enable AI Answers" toggles in the search customizer (SEARCH-211) #48990]
• Search Blocks: Add experimental opt-in to replace the legacy instant-search overlay with the server-rendered Search blocks template (gated behind jetpack_search_overlay_block_template_enabled filter). [Search Blocks: experimental opt-in to render the Search blocks template as the overlay (SEARCH-206) #48987]
• Search Blocks: Add optional autocomplete suggestions dropdown to the Search Input block — query, taxonomy, and post suggestions powered by the WPCOM search-suggestions endpoint. [Search: add optional autocomplete dropdown to the Search Input block #48985]
• Search dashboard: Add a "WooCommerce Product Search" control for a dedicated Site-Editor-editable Jetpack Search template. [Search: take over WooCommerce Product Search Results template (opt-in) #48936]
• Search Dashboard: Add an "Additional settings" heading above the feature toggles in the search-blocks settings view. [Search: add "Additional settings" heading above the search-blocks feature toggles #48948]

Changed

• Build: Collapse per-directory production-exclude rules for src/**/*.js into a single broad exclude. [Search: collapse per-directory production-exclude rules in search-package .gitattributes #48983]
• Replace internal ContextualUpgradeTrigger upgrade prompts with @wordpress/ui Notice composition. [Componentry: migrate ContextualUpgradeTrigger to @wordpress/ui Notice #48909]
• Search: Normalize page tabs onto shared minimal variant. Bump @wordpress/ui to 0.13.0. [Normalize page tabs onto shared minimal variant #48964]
• Search: The AI Answer block no longer gates on the site-wide jetpack_search_ai_answers_enabled option — block presence in post content is the only switch. [Search: decouple AI Answer block from jetpack_search_ai_answers_enabled (RSM-3608) #48993]
• Search Blocks: Let authors pick which suggestion sections appear in the Search Input dropdown via a new per-block suggestionTypes attribute. [Search Input: let authors pick which suggestion sections appear #48991]
• Update package dependencies. [Update wordpress monorepo #48405] [Update JS unit testing packages #49012]

Fixed

• AI Answers: Fix the answer panel colors in dark mode. [[codex] Fix AI answers dark mode styling #49019]
• Instant Search: Prevent the search modal from triggering on third-party form submissions (e.g. ActiveCampaign sign-up widgets with an s input). [Search: prevent Instant Search modal from triggering on third-party form submissions #48958]
• Phan: Address PhanPluginDuplicateConditionalNullCoalescing violations. [Phan: Address PhanPluginDuplicateConditionalNullCoalescing violations #48887]
• Search: Reject experience requests combined with ai_answers_enabled or search_suggestions_enabled instead of silently dropping them. [Search: fix two follow-up bugs from the WooCommerce product-search takeover (RSM-3545) #48956]
• Search Blocks: Cap the filter-checkbox list at its configured "Maximum items" even after the session retains options across multiple searches. [Search Blocks: cap filter-checkbox list at Maximum items after session retention (SEARCH-208) #48989]
• Search Dashboard: Hide the AI Agent Access toggle for private sites and improve related settings spacing. [[RSM] Hide AI Agent Access toggle on private sites #48912]
• Search dashboard: Let the toggle description text span the full settings card width. [Search dashboard: full-width toggle description text #48944]

Related product discussion/links

p1779309309701579-slack-C02ME06LF

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

No.

Testing instructions

• Install Jetpack Search on a site and confirm the Search dashboard loads.
• Test the AI Answer block: add it to the embedded search template and confirm the AI Answers panel renders correctly.
• Test autocomplete suggestions in the Search Input block by enabling "Show search suggestions" in the block inspector and running a search.
• If WooCommerce is active, test the "WooCommerce Product Search" control in the Search dashboard.
• Test the "Compact" block style on the Clear Filters and Load More blocks.
• Verify dark mode styling for the AI Answers panel is correct.
• Verify that third-party forms with an s input field (e.g. newsletter sign-up forms) are not intercepted by the Jetpack Search overlay.

[kangzj]

@copilot fill the PR description following the template for me

[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 prerelease branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack prerelease

bin/jetpack-downloader test jetpack-mu-wpcom-plugin prerelease

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!

---

Jetpack plugin:

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

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: June 2, 2026
  • Code freeze: June 1, 2026

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

---

Search plugin:

No scheduled milestone found for this plugin.

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

[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