An account that moves shows where it went

PrivaPub dropped Move as an unknown type and showed no `moved` on accounts.
Now a Move is believed as Mastodon believes it: the moving account sends it
about itself, and the new account, read again from its own server, names it
in alsoKnownAs (now kept on remote accounts). The old account then shows the
new one as `moved` in the Mastodon API. The personas following it keep
following it: following the new account on their behalf would tell another
server about them, so that waits for the owner.

Checked live against GoToSocial (scenarios/moves.sh: an alias, a move, 6
checks).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw

docs/ROADMAP.md

@@ -651,7 +651,8 @@ it, raw where it doesn't.
   `interaction_policy`; `ReplyRequest`/`LikeRequest`/`AnnounceRequest` where approval is needed; `Accept{result}`
   verified and carried; replies a policy does not let in kept only with an authorization.
 - **Accounts and follows:**
-  - inbound `Move` with Mastodon's checks;
+  - inbound `Move` with Mastodon's checks: **done 2026-10-05** (the old account shows `moved`, checked live against
+    GoToSocial); moving the personas' follows to the new account is left to them until the owner decides;
   - re-run WebFinger on a rename;
   - inbound `Block`, plus `Add`/`Remove` of pins;
   - FEP-8fcf followers sync;