Premium Analytics: show File downloads only on WPCOM Simple sites

[chihsuan]

Fixes WOOA7S-1717
Fixes WOOA7S-1709

Proposed changes

File download tracking is provided only for WordPress.com Simple sites. The endpoint returns 404 elsewhere, but Premium Analytics registered and rendered the widget on every site.

• Treat jpa/file-downloads as unsupported outside WordPress.com Simple.
• Apply the same type-level policy to the widget registry and default layouts, keeping the REST list, import map, widget picker, and defaults consistent.
• Preserve saved layouts. Gutenberg intentionally renders missing types as removable ghost widgets, so availability changes do not silently rewrite user preferences (WordPress/gutenberg#78502).
• Keep environment, plugin/category, and shared type-level policies separate and composable. Future permanent type restrictions have one shared resolver; temporary plan or capability restrictions remain runtime concerns.
• Preserve non-array records supplied through the public default-layout filter so third-party callbacks remain compatible.
• Hide the /reports/downloads route outside WordPress.com Simple.
• Remove the widget's obsolete 404-specific UI.

Related product discussion/links

• WOOA7S-1717
• WOOA7S-1709
• WOOA7S-1716
• Premium Analytics: run JavaScript tests in CI #50770

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

No.

Testing instructions

Self-hosted Jetpack or another non-Simple site

1. Build the package: jetpack build packages/premium-analytics --deps.
2. Open Premium Analytics in wp-admin.
3. Reset the Traffic layout and confirm File downloads is not included.
4. Confirm File downloads is absent from the Add widget picker.
5. Confirm no stats/file-downloads requests are made.
6. Visit admin.php?page=jetpack-premium-analytics-wp-admin&p=%2Freports%2Fdownloads and confirm it redirects to the dashboard.
7. If the site has a layout saved before this branch with File downloads, confirm it appears as a removable unavailable widget. Enter Customize mode and remove it.

WordPress.com Simple

1. On a sandbox, fetch this branch's build: bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/wooa7s-1717-hide-file-downloads-on-self-hosted.

2. Sandbox the test site and public-api.wordpress.com in /etc/hosts.

3. Open Premium Analytics on a Simple site with the jetpack-premium-analytics sticker. To add the sticker, run this on the sandbox:

   wp blog-stickers add --sticker=jetpack-premium-analytics --who=<your_wpcom_login> --blog_id=<blog_id>
   

4. Confirm File downloads remains in the Traffic default and widget picker.

5. Confirm its request returns data and /reports/downloads still renders.

[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/wooa7s-1717-hide-file-downloads-on-self-hosted branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/wooa7s-1717-hide-file-downloads-on-self-hosted

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!

[jp-launch-control]

Code Coverage Summary

Coverage changed in 2 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/premium-analytics/src/widget-availability.php	34/41 (82.93%)	-4.95%	3 ❤️‍🩹
projects/packages/premium-analytics/src/dashboard-layout.php	384/390 (98.46%)	-0.24%	1 ❤️‍🩹

1 file is newly checked for coverage.

File	Coverage
projects/packages/premium-analytics/src/widget-type-support.php	19/19 (100.00%) 💚

Full summary · PHP report · JS report

[louwie17]

This looks good and tested well both on simple and self hosted.