Premium Analytics: move a stored Top tags & categories tile from Insights to Traffic once

[dognose24]

Related to WOOA7S-2291

Draft, stacked on #53299. Parked until the product call on WOOA7S-2291: move a reader's Tags tile for them, or only add it on Traffic and leave their Insights layout alone. This is the first option, built; the second is a trim of it.

Proposed changes

• Premium Analytics: move Top tags & categories to Traffic and follow the date picker #53299 moves Top tags & categories from the Insights default layout to Traffic. A customized layout does not follow a default change, so this adds the dashboard's first section layout migration (routes/dashboard/config/section-layout-migrations.ts, run by useSectionLayoutMigrations() from the dashboard stage): a reader who customized Insights loses the Tags tile there, one who customized Traffic gains it at the end, once.
• The applied migration ids are recorded in a dashboardLayoutMigrations preference, so a tile the reader removes afterwards stays removed, and a reader with no stored layouts is untouched.
• docs/dashboard-sections.md describes the mechanism.

Related product discussion/links

• WOOA7S-2291 (the decision), WOOA7S-2236 (the move)

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

No. One new entry in the dashboard preferences, the list of applied migration ids.

Testing instructions

Needs #53299 merged first, or this branch built.

1. On trunk before the move, customize the Insights layout (move any tile) so it is stored, and leave Traffic uncustomized. Switch to this branch and reload: Tags is gone from Insights and sits at the bottom of Traffic (the new default).
2. Customize Traffic too, then reload on this branch: Tags is appended to your Traffic layout once.
3. Remove Tags from Traffic and reload: it stays removed.
4. A fresh reader with no stored layouts sees the new defaults and no migration entry in preferences.

🤖 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 add/premium-analytics-tags-layout-migration branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/premium-analytics-tags-layout-migration

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.

---

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.

---

Premium Analytics 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 7ee6ece, 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 7ee6ece is available.

Full summary · PHP report · JS report