Social: remove unused scheduled posts components

[gmjuhasz]

Fixes #

Proposed changes

• Remove the unused ScheduledPostsList and ScheduledPostItem components (_inc/components/scheduled-posts/), along with their styles and Storybook stories.
• These components were added in Social | Add scheduled post components #42221 for the old social post modal. Their only consumer, social-post-modal/scheduled-shares.tsx, was deleted in Social: Get rid of the UNIFIED_UI_V1 feature flag uses #47759 when the UNIFIED_UI_V1 flag was made the default, leaving them orphaned. The scheduled shares feature lives on in the unified modal's sharing-activity components, which are unchanged.
• Remove the stale scheduled-posts/ mention from the package AGENTS.md.

Related product discussion/links

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

No.

Testing instructions

• Verify nothing references the removed components: git grep -rn "scheduled-posts" projects/packages/publicize should return no hits in source files.
• Run the package tests: cd projects/packages/publicize && pnpm run test — all tests should pass.
• Smoke test scheduled shares in the unified modal: schedule a share for a published post and check it appears in the sharing activity list and can be deleted — that UI does not use these components.

[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), and enable the remove/publicize-scheduled-posts-components branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack remove/publicize-scheduled-posts-components

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

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