feat(scheduled): edit a queued post content and destinations, not just its time #55

Summary

macOS can cancel and reschedule a queued post. The web can edit its content and its destinations too. And the schedule dialog itself differs: the web picks per-network destinations at schedule time, the Mac does not.

What the web does (/help/messages ▸ Scheduled posts)

Scheduling flow:

Open the advanced options (gear icon) … Click the calendar icon … Pick a date and time in the future. The dialog also shows a checkbox for each connected cross-post account (Mastodon, Bluesky, LinkedIn, X/Twitter) so you can choose which networks receive the post when it goes live. … A note below the compose button shows the scheduled date and time. To cancel scheduling and post immediately instead, click the displayed date.

Managing them:

Each scheduled post shows its content, scheduled time, and the destinations selected. Click the edit icon to change the time, the message content, or which networks will receive the post. If LinkedIn is selected, the same LinkedIn destination picker from the compose box appears here. To cancel a scheduled post, open it and delete it.

What macOS ships today

ScheduledPostsViewModel (App/Features/Scheduled/ScheduledPostsViewModel.swift) exposes:

• load()
• cancel(post:)
• reschedule(post:to:)

No content edit. No destination edit. No destination display.

The composer (ComposerWindowView.swift:298 scheduleSection, :161 crossPostSection) has schedule and cross-post as two independent sections rather than the web's combined schedule-with-destinations dialog. Verify whether cross-post selections made in the composer are actually carried onto a scheduled post — if they are dropped, that is a second defect hiding inside this one and should be called out in the PR.

Division of labor

Kit

• Confirm the scheduled-post update route and the fields it accepts (content, scheduledAt, cross-post flags). Message edit is PATCH /api/messages/{id} since PR fix(api): correct seven live-verb defects and repoint the GitHub issue routes #24 — confirm a scheduled message edits the same way and that cross-post flags are mutable post-scheduling. Probe before building.

Domain

• Extend the scheduled-post model to carry its selected destinations.
• A single updateScheduled(...) covering time, content, and destinations, replacing the narrow reschedule.
• Reuse the existing LinkedIn posting-target projection so the destination picker is the same code in both places.

App

• Composer: fold the per-network checkboxes into the schedule dialog, matching the web, and keep the "click the date to post now instead" affordance.
• ScheduledPostsRootView: show each post's destinations; an edit sheet covering time, content, and destinations, including the LinkedIn destination picker.
• Keep cancel/delete as-is.

Tests

• happy — edit content, time, and destinations on a queued post; all three persist
• invalid — reschedule into the past → rejected client-side with a clear message
• upstream-failure — update rejected → the sheet keeps the user's edits and surfaces the error
• boundary — a post scheduled with zero destinations; one with every network selected; editing a post seconds before it fires

Acceptance criteria

• Everything the web lets you change about a queued post can be changed on the Mac.
• A scheduled post's destinations are visible without opening an editor.
• Full E2E gate green.

Notes

New finding from the 2026-09-07 parity sweep. Size S–M. Touches the same LinkedIn destination model as the Integrations and Organizations issues — sequence it after at least one of them so the projection exists.