A status asked for by id is shown, and remote warnings are their own

GET /api/v1/statuses/:id applied the viewer's own blocks and mutes and
answered 200 with null for a post of an author the viewer had blocked;
decePub's thread page then showed nothing. As in Mastodon, a status asked
for by id (or acted on) is shown whatever the viewer blocked or muted,
and only lists leave such posts out; when nothing can be shown the
answer is 404, never null, and search leaves it out.

A remote post marked sensitive with an empty summary (Akkoma's sensitive
media, Lemmy's NSFW) got an invented "Content warning" that hid its
words. A remote post now keeps its own summary: sensitive without one
hides the media only. A local post warned without words still gets the
default warning.

Both found by decePub's end-to-end tests on the town.

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

PrivaPub/Api/Mastodon/Controllers/SearchController.cs

@@ -55,7 +55,8 @@ namespace PrivaPub.Api.Mastodon.Controllers
 				if (post == default && resolve && type is null or "statuses")
 					post = await _remotePosts.StoreContext(q, 0, token);
 				if (post != default && type is null or "statuses" && await VisibilityPolicy.CanSee(post, MyId, token))
-					results.Statuses.Add(await _mapper.Status(post, MyId, token));
+					if (await _mapper.Status(post, MyId, token) is { } status)
+						results.Statuses.Add(status);
 				if (results.Statuses.Count == 0 && type is null or "accounts")
 				{
 					var local = await _localActors.FindByUri(q, token);