Jetpack AI: make the Try it out links pre-open their surface

[ariskataoka]

Fixes #FORNO-424

Proposed changes

• Writing Assistant's "Try it out" now links to post-new.php?openSidebar=jetpack-ai-assistant. The AI Assistant plugin picks the arg up on mount and opens the Jetpack sidebar with the "Improve with AI" panel expanded — same approach as the existing openSidebar=global-styles handling.
• Image Editor's link now goes to upload.php?ai-assistant, which the Image Studio bundle already handles: it opens Generate mode and strips the param.
• If the extension isn't available, the args do nothing — the editor and Media Library load as before.
• Feature Clip keeps its plain post-new.php link (clips live in the Image Studio flow, not the AI sidebar). All three hrefs are pinned by tests.

Related product discussion/links

@ilonagl's comment

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

No.

Testing instructions

On a connected site with an AI plan and the features toggled on:

• From Jetpack -> AI, (set the toggle on if off), click "Try it out in the editor" on Writing Assistant -> the editor opens with the Jetpack sidebar open and "Improve with AI" expanded, no console errors
• (set the toggle on if off) Click "Try it out" on Image Editor-> the Media Library opens with Image Studio in Generate mode
• Open post-new.php directly -> sidebar should stay closed, as before
• Toggle Writing Assistant off and open post-new.php?openSidebar=jetpack-ai-assistant by hand-> normal editor, no errors.

[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 add/jetpack-ai-try-it-out-pre-open branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/jetpack-ai-try-it-out-pre-open

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:

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

No summary data is available for parent commit a31978b, so cannot calculate coverage changes. 😴

If that commit is a feature branch rather than a trunk commit, this is expected. Otherwise, this should be updated once coverage for a31978b is available.

Full summary · PHP report · JS report