Premium Analytics: full-width post highlights row and video upload-date wording

[dognose24]

Proposed changes

Two small alignments with the updated design mocks for the detail pages:

• Post detail → Post traffic: the Post highlights row now spans the full dashboard width. It was previously three quarter-width tiles with the fourth column left empty, per the earlier mocks; the updated mocks stretch the three tiles across the whole row, matching the email highlights rows. The widget's MetricTileGrid spreads its tiles across whatever span it is given, so this is a layout-placement change only.
• Video detail: the summary subtitle now reads "Video uploaded on …" instead of "Video published on …". The date shown is the VideoPress attachment's post date, which is the upload date, so only the wording changes.

Related product discussion/links

• Part of the updated-mock alignment pass following WOOA7S-1785 (see WOOA7S-1905 / STATS-428 for the related design-alignment items).

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

No.

Testing instructions

• Build packages/premium-analytics and open the Premium Analytics dashboard.
• Open a post report → Post traffic tab: the Views / Likes / Comments highlights row stretches across the full content width with no empty fourth column.
• Open a video report: the header subtitle reads "Video uploaded on ." followed by the performance range.
• pnpm run test routes/post-detail routes/video-detail passes.

🤖 Generated with Claude Code

Screenshots

Post detail → Post traffic, "Last 30 days": the highlights row spans the full width.

Before	After

Video detail: the subtitle reads "Video uploaded on …".

Before	After

[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/pa-detail-mock-alignment branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/pa-detail-mock-alignment

bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/pa-detail-mock-alignment

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

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[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!

[chihsuan]

LGTM and tested well. 🚢