Blaze: rename Advertising to Blaze Ads, move under the Jetpack menu, add migration notice

[jjolmo]

Fixes ADS-796 (supersedes #47858, reapply of #47582 with the revised scope)

Proposed changes

• Rename the Blaze menu label from "Advertising" to "Blaze Ads". The product name is used verbatim and is intentionally not translatable.
• Move the menu from Tools to a context-aware parent: Jetpack (WPCOM platform or connected sites), WooCommerce Marketing (when the Marketing menu is registered), or Tools as a fallback.
• Register under Jetpack through Admin_UI\Admin_Menu::add_menu() to avoid the page-hookname race condition on WordPress.com Simple sites that forced the revert of Rename Advertising to Blaze Ads, add context-aware menu and campaign promotion #47582 (the Jetpack top-level menu is created at priority 1000, after this package's priority-999 registration).
• Leave a temporary "Blaze Ads has a new home" notice entry at the old Tools location (same pattern as the Jetpack Forms and Stats menu moves), disableable via the jetpack_blaze_show_migration_notice filter. A follow-up PR will remove it ~1 month after deploy.
• Redirect the legacy tools.php?page=advertising URL to admin.php?page=advertising, only when the menu has actually moved.
• Add jetpack_blaze_menu_slug / jetpack_blaze_menu_label / jetpack_blaze_menu_parent filters so the standalone Blaze Ads plugin can customize the registration.
• Declare the previously missing automattic/jetpack-admin-ui dependency in the blaze package and refresh the affected plugin lock files.
• Unlike Reapply: Rename Advertising to Blaze Ads, add context-aware menu and campaign promotion #47858, this PR does not include campaign-based top-level menu promotion — dropped per the product discussion (menu auto-shifting confuses users; pinning will be a standardized mechanism later).

Related product discussion/links

• ADS-796
• Internal P2 discussion and scope change: see the links in ADS-796 (April update)

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

No.

Testing instructions

• Apply this branch to a Jetpack-connected test site (or use the Beta plugin build).
• Jetpack site (no WooCommerce): the menu appears as Jetpack → Blaze Ads, the dashboard loads at admin.php?page=advertising, and Tools shows a temporary "Blaze Ads" entry rendering the moved notice with a working button.
• Old URL: visiting tools.php?page=advertising redirects to admin.php?page=advertising.
• WooCommerce + Jetpack: the menu appears as Marketing → Blaze Ads.
• WordPress.com Simple site: verify the Jetpack → Blaze Ads menu URL points to admin.php?page=advertising (regression check for the Rename Advertising to Blaze Ads, add context-aware menu and campaign promotion #47582 revert).
• Post list: the Blaze row action / promote links still open the dashboard correctly.
• Unit tests: jetpack test php packages/blaze (83 tests green locally).

[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 jjolmo/ADS-796-blaze-ads-menu-rename branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack jjolmo/ADS-796-blaze-ads-menu-rename

bin/jetpack-downloader test jetpack-mu-wpcom-plugin jjolmo/ADS-796-blaze-ads-menu-rename

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: July 7, 2026
  • Code freeze: July 6, 2026

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

---

Mu Wpcom plugin:

• Next scheduled release: WordPress.com Simple releases happen semi-continuously (PCYsg-Jjm-p2)

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

---

Wpcomsh plugin:

• Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2)

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/jetpack-mu-wpcom/src/features/wpcom-admin-menu/wpcom-admin-menu.php	99/422 (23.46%)	-0.06%	1 ❤️‍🩹
projects/packages/blaze/src/class-blaze.php	169/239 (70.71%)	15.77%	-12 💚

Full summary · PHP report · JS report