A remote thread brings the replies that never reached us

The context of a remote post showed only what PrivaPub happened to hold:
replies from servers nobody here follows were never seen, and only the
ancestors were ever fetched. Now a persona opening a public remote thread
queues FetchReplies for the post and its root, at most once an hour each.

The job reads the thread's own collection first (FEP-7888 `context`, which
Mastodon 4.5+ serves with every reply at any depth; posts or, as FEP-f228
allows, the activities that made them), and otherwise the post's `replies`
(PeerTube's `comments`) and the replies' own, two levels down. At most 5
pages and 100 posts a job, signed by the instance actor, never a persona;
each post is fetched from its own origin and stored through StoreContext,
so only public and unlisted ones are kept.

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

PrivaPub/Models/Statistics/InteractionEvent.cs

@@ -11,7 +11,7 @@ namespace PrivaPub.Models.Statistics
 		public string Channel { get; set; }//recv | in | out | http | preview | crawl
 		public string Activity { get; set; }//Create, Follow, ...; "other" when it is no plain type name
 		public string Object { get; set; }//Note, Article, Person, ...
-		public string Purpose { get; set; }//http and crawl: actor, key, object, context, webfinger, nodeinfo, ...
+		public string Purpose { get; set; }//http and crawl: actor, key, object, context, replies, webfinger, nodeinfo, ...
 		public string Trigger { get; set; }//http: what caused the request (inbox, deliver, describe, request, ...)
 		public string Outcome { get; set; }//queued, refused, accepted, dropped, ok, failed, deferred, retry, dead
 		public string Reason { get; set; }