Survicate: suppress surveys while Help Center is open

[paulopmt1]

Summary

• Close any visible Survicate survey when the Help Center opens in wp-admin, mirroring the suppression logic added to wp-calypso in Suppress Survicate popups while Help Center is open wp-calypso#109989
• Subscribes to the automattic/help-center @wordpress/data store and calls window._sva.closeSurvey() when the Help Center transitions to open
• Gracefully degrades when the data store or wp.data is unavailable (try/catch + null checks)

Testing instructions

1. Open any wp-admin page on an Atomic/Simple site (English locale)
2. Verify Survicate SDK loads as before (check for survey.survicate.com in network tab)
3. Trigger a Survicate survey (or use window._sva.showSurvey() if available)
4. Open the Help Center — the survey should be dismissed
5. Close the Help Center — future surveys should work normally

Related PRs

• Add Survicate survey integration for wp-admin, block editor, and site editor #47107 (original Survicate integration)
• Suppress Survicate popups while Help Center is open wp-calypso#109989 (Calypso counterpart this mirrors)

🤖 Generated with Claude Code

[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 add/survicate-help-center-suppression branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/survicate-help-center-suppression

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 🤖

---

🔴 Action required: We would recommend that you add a section to the PR description to specify whether this PR includes any changes to data or privacy, like so:

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

My PR adds *x* and *y*.

---

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