Jetpack AI: Send the editor and Settings links to the Jetpack AI Hub

[ariskataoka]

Proposed changes

The My Jetpack product card opens the Jetpack AI Hub, but three links still open the old My Jetpack AI page: "Discover all features" in the AI Assistant block, "Learn more about Jetpack AI" in the Jetpack sidebar, and "Learn more about all Jetpack AI features" under Settings › Writing › Composing. This PR points them at the same place the card goes.

• My Jetpack prints where Jetpack AI is managed (myJetpack.aiManageUrl in the admin script data) for users with manage_options, reusing Jetpack_Ai::get_manage_url(). Nobody else can open the pages it points at, so nobody else pays for the lookup.
• @automattic/jetpack-shared-extension-utils gets getJetpackAiManageUrl(), which reads that value and falls back to the old My Jetpack page when it is absent. It lives there rather than in @automattic/jetpack-script-data on purpose: script-data is a page-level global served by whichever plugin's assets package wins, so a brand-new export there is undefined wherever an older bundle is served. On WordPress.com Atomic that bundle comes from wpcomsh, and an earlier version of this branch crashed the AI Assistant block for exactly that reason. shared-extension-utils is bundled into each plugin's own build.
• The editor links ("Discover all features" in the AI Assistant block, "Learn more about Jetpack AI" in the Jetpack sidebar) and the Settings › Writing › Composing link ("Learn more about all Jetpack AI features") send administrators to that URL.
• Users without manage_options get the jetpack.com AI page instead. The Jetpack AI Hub is an administrator page, so sending an Editor there would show "Sorry, you are not allowed to access this page."

The old page itself is untouched. Removing it is a separate step that waits on a product decision for WordPress.com Atomic sites.

Related product discussion/links

• FORNO-596
• FORNO-504 (background: deleting the old page)

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

No.

Testing instructions

Self-hosted, as an administrator (Jetpack connected)

• Go to Jetpack → My Jetpack. On the AI card, click View (or Manage). You land on the Jetpack AI Hub (wp-admin/admin.php?page=jetpack-ai). Keep that URL in mind: every link below should match it.
• Go to Jetpack → Settings → Writing. In the Composing section, click "Learn more about all Jetpack AI features". You land on the Jetpack AI Hub, not on My Jetpack.
• Create a new post and add an AI Assistant block. The block renders. Click "Discover all features" in the block. You land on the Jetpack AI Hub.
• In the same post, open the Jetpack sidebar and expand "Improve with AI". Click "Learn more about Jetpack AI". You land on the Jetpack AI Hub.

Self-hosted, as an Editor

• Create a new post and add an AI Assistant block. Click "Discover all features". You land on the Jetpack AI page on jetpack.com.
• Open the Jetpack sidebar, expand "Improve with AI", and click "Learn more about Jetpack AI". You land on the Jetpack AI page on jetpack.com.
• The Composing section under Settings → Writing is not shown to Editors, so there is nothing to check there.

WordPress.com Atomic, as an administrator (install the branch with the Jetpack Beta plugin)

• Create a new post and add an AI Assistant block. The block renders.
• Click "Discover all features" in the block, then open Jetpack → Settings → Writing → Composing and click "Learn more about all Jetpack AI features". Both go where the My Jetpack AI card's View link goes: the Jetpack AI Hub on sites where it is open, otherwise the My Jetpack AI page. The three must agree.
• The Jetpack sidebar shows the WordPress Agent notice instead of "Improve with AI" here, so there is no sidebar link to check.

WordPress.com Simple (this branch cannot be installed there; this only confirms nothing changes)

• Create a new post and add an AI Assistant block. Click "Discover all features". You land on the Jetpack AI page on jetpack.com, as before.

🤖 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 (Jetpack or WordPress.com Site Helper), and enable the update/jetpack-ai-my-jetpack-ai-page-links branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/jetpack-ai-my-jetpack-ai-page-links

bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/jetpack-ai-my-jetpack-ai-page-links

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

Coverage changed in 2 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/my-jetpack/src/class-initializer.php	387/466 (83.05%)	0.07%	0 💚
projects/plugins/jetpack/extensions/blocks/ai-assistant/hooks/use-ai-product-page/index.ts	4/4 (100.00%)	100.00%	-4 💚

1 file is newly checked for coverage.

File	Coverage
projects/js-packages/shared-extension-utils/src/get-jetpack-ai-manage-url.js	1/1 (100.00%) 💚

Full summary · PHP report · JS report

[Copilot]

🟢 Approval recommended

The routing, compatibility fallback, capability gating, changelogs, and targeted tests are consistent and complete.

0 open findings

1 resolved since last review

• Add documented getJetpackAiManageUrl API and reuse it

🧠 Review effort: Balanced

[t-wright]

LGTM!