Relays: PrivaPub reads from the relays its configuration names

Federation:Relays names relays by their actor (or inbox) address; the instance actor follows Public at each, as Mastodon
subscribes, a minute after start and every six hours (asked again a day after no answer or a refusal, undone when a
relay is no longer named). What an accepted relay passes on comes to the federated timeline and nobody's home: a public
post it forwards (Activity-Relay), read again from its origin like any forwarded post, and a post it announces
(aode-relay), kept as its author's and never as the relay's boost. Nothing of a persona's is sent to a relay; sending
public posts there waits for the owner.

The pasture gains both relays (peers/relay.sh, peers/aoderelay.sh) and scenarios/relay.sh, 13 checks. The village
backlog is clean: 2574 checks pass, one known gap (Misskey's).

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

docs/ROADMAP.md

@@ -682,7 +682,9 @@ it, raw where it doesn't.
   - FEP-8b32 proof verification;
   - `hs2019` with SHA-512.
 - **Discovery:**
-  - a relay client for both relay styles;
+  - a relay client for both relay styles: **reading done 2026-10-05** (`Federation:Relays`; forwarded posts read again
+    from their origin, announces unwrapped; checked live against Activity-Relay and aode-relay); sending public posts to
+    relays waits for the owner;
   - instance actor discovery (FEP-d556, FEP-2677);
   - `implements` (FEP-844e).
 - **Mastodon API:** ~~streaming WebSocket~~ (done 2026-10-05: `/api/v1/streaming` as a WebSocket and as server-sent