[Enhancement] Admin deep-dive (trust/safety): Reported content is shown as raw text only — no inline preview/context of the offending post

Area: Admin deep-dive (trust/safety) (audit p15a) · Surface: /admin/moderation/{id} (AdminModerationController@show) · Dimension: UI/UX opportunity (#3) · Severity: minor

Discourse's review queue and Zendesk both show the flagged content in context — the post rendered as users see it, plus the conversation around it — so a moderator decides without leaving the queue. A Mobieus mod opening a report often sees a bare source_url and has to navigate away to the live thread to understand it, then come back to act. Adding inline rendered context (the reported post plus a couple of neighbors) turns a multi-tab investigation into a single-screen decision, which is the difference Discourse markets as 'review without context-switching'.

Evidence

show() only joins the reported message when reported_message_id is set (AdminModerationController.php:167-177) and renders the row. ModerationAIController@loadReportedContent (ModerationAIController.php:154-171) falls back to bio/signature or source_url when there's no message — confirming most report types carry only a URL string, not rendered context. There is no thread-surrounding-context fetch (no neighboring posts, no rendered HTML preview).

Suggested fix. In show(), when the report points at a forum post/thread, fetch the rendered post plus N surrounding posts and display them inline; for user-profile reports show the rendered bio/signature. The data-fetch shape already exists in loadReportedContent — promote it from AI-only into the human review template.

Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.