Town: Pleroma joins, and a rerun finds what it made

Pleroma 2.10.2 runs in the pasture from its OTP release (libvips, the
dedupe question, and hackney pointed at the system CA bundle); its driver is
Akkoma's on its own container and database. The pair passes 241 cells, after
its first run showed Pleroma dropping Follows it could not verify yet.

The PrivaPub driver finds the group an earlier run made instead of failing
on the name; the seeder posts a quote or reply of a post from its own round
after that post.

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

docs/INTEROP.md

@@ -417,6 +417,18 @@ Seen along the way:
 - It records our `Block` (`user_relationships`) but never reports a remote blocker as `blocked_by`.
 - Its streamer crashes rendering a new DM conversation (`ConversationView`, a nil `last_status`); delivery is unaffected.
 
+**Town evidence (2026-10-05, Pleroma 2.10.2, `town.sh seed pleroma-pair`):** 241 cells pass between two personas and
+three Pleroma accounts: delivery and confinement at every visibility both ways, likes, boosts, reactions and votes
+counted, threads, edits and deletes, follows of locked accounts, and the privacy rows. Its first run found two things:
+- **A Follow taken and then lost.** Pleroma answers an inbox POST 200 and checks the signature in a worker; while it
+  could not fetch our actor, it dropped our Follows there, and they stayed pending on our side for good. A pending
+  request is now sent again when the persona follows again (FEDERATION.md, Delivery).
+- **Duplicates are refused, harmlessly.** A Create whose object Pleroma already holds (fetched for a reply, or
+  delivered to another inbox first) is cancelled with "The object to create already exists".
+
+Pleroma federates through hackney, which trusts certifi's compiled-in roots, never a file: the pasture's image names the
+system bundle in its config.
+
 ### Lemmy: 0.19.20 live (lemmy.ml); 1.0.0-beta.2 (2026-09-25) in beta since May
 
 join-lemmy.org's federation page is out of date. Current Lemmy neither sends nor reads `stickied` or `commentsEnabled`