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

PrivaPub/Infrastructure/Http/FederationOptions.cs

@@ -11,5 +11,8 @@ namespace PrivaPub.Infrastructure.Http
 		// At two the inbox kept up with about 110 activities a second (tools/pasture/load.sh)
 		public int InboxConcurrency { get; set; } = 8;
 		public int DeliveryConcurrency { get; set; } = 8;
+		// relays the instance actor subscribes to, by their actor's (or inbox's) address: their public posts come to the
+		// federated timeline, and nothing is sent to them but the subscription
+		public List<string> Relays { get; set; } = new();
 	}
 }