A restore on the live pasture: its own scenario, and two fixes it found

tools/pasture/scenarios/restore.sh backs the pasture up from the administrator's endpoint, then alice_restore deletes a
post and makes another, mastouser follows her, she blocks bob_restore and carol_restore is made; the restore, asked for
from the endpoint, keeps every protective act (19 checks). town.sh renew <peer> signs a peer's town accounts in again,
since a restore ends every session.

It found that a backup listed media files already missing when it was made, so verifying it failed and the restore was
refused: a manifest now lists only the files it holds (refusals are cut to five lines). And a local post made after the
backup now comes back as a deleted row, as a deletion leaves it, so it answers 410 and its id is never given again;
DeletedObject holds remote tombstones only.

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

PrivaPub/Infrastructure/Backup/ServerRestore.cs

@@ -52,7 +52,7 @@ namespace PrivaPub.Infrastructure.Backup
 		{
 			var problems = await Check(context, id, token);
 			if (problems.Count > 0)
-				return string.Join("; ", problems);
+				return string.Join("; ", problems.Take(5)) + (problems.Count > 5 ? $"; and {problems.Count - 5} more" : string.Empty);
 			var waiting = RestoreMarker.Read(context.BackupsRoot);
 			if (waiting != default && waiting.Attempts < RestoreMarker.MaxAttempts)
 				return $"the restore of {waiting.Backup} is already {waiting.State}";