Use the edited post date to compute default ActivityPub visibility

[arcangelini]

Fixes #3641

Proposed changes:

Backdate a post by more than a month, save it, and the editor immediately claims you have unsaved changes and warns you about leaving the page.

The plugin defaults posts older than a month to "Do not federate" and saves that choice onto the post. It was reading the date from the saved copy instead of the one you're editing, so it only noticed the new date after the save had finished — and writing its choice down that late looks like a fresh edit.

Now it reads the date you're actually editing.

Side effect worth knowing: publishing a backdated post no longer sends it to your followers. It used to go out anyway, despite the sidebar saying "Do not federate".

Doesn't fix the undo trap also described in #3641.

Testing instructions:

• New post, add content, set the date to over a month ago, save the draft.
• Editor should stay clean — no unsaved-changes warning when you navigate away.
• Fediverse ⁂ panel should read "Do not federate".
• Repeat with today's date: should read "Public", editor still clean.
• Publish a backdated post, confirm nothing queued: wp post list --post_type=ap_outbox

Changelog entry

Already committed as .github/changelog/fix-editor-dirty-after-save.

[Copilot]

Pull request overview

Updates the ActivityPub editor sidebar plugin so the default visibility calculation uses the edited post date (not the last-saved date), preventing the visibility sync effect from writing post meta after a save and incorrectly marking the editor as dirty.

Changes:

• Switch default visibility computation to read date via getEditedPostAttribute( 'date' ) inside the existing useSelect block.
• Add regression tests that render the real EditorPlugin with a mocked editor store to catch selector regressions.
• Add a patch-level changelog entry describing the user-facing fix.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/editor-plugin/plugin.js	Uses the edited post date selector for default visibility computation to avoid post-save dirty state.
src/editor-plugin/tests/visibility-sync.test.js	Adds regression coverage by rendering the real plugin and asserting meta sync behavior across saved-vs-edited date scenarios.
build/editor-plugin/plugin.js	Generated build output updated to reflect the source change.
build/editor-plugin/plugin.asset.php	Generated asset metadata/version updated.
.github/changelog/fix-editor-dirty-after-save	Patch changelog entry for the editor dirty-state fix.

Files not reviewed (1)

• build/editor-plugin/plugin.js: Generated file

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[mcsf]

LGTM, fixes it for me!