[Enhancement] Admin deep-dive (trust/safety): Canned moderation responses (ModTemplate) exist but are absent from the report queue

Area: Admin deep-dive (trust/safety) (audit p15a) · Surface: /admin/moderation/{id}/warn, suspend, ban (AdminModerationController) · Dimension: Existing feature to improve vs industry (#4) · Severity: minor

Saved replies / macros are table stakes in Zendesk (macros), Intercom (saved replies), and Help Scout (saved replies) — they keep moderator messaging consistent and fast. Mobieus already built the macro store (mod_templates) and wired it into the user page, but the busiest enforcement surface — acting on an inbound report — can't use it. A mod warning a user from a report types free-text or accepts a generic default, so the same violation gets worded ten different ways across ten mods. The fix is small because the model and templates already exist.

Evidence

ModTemplate macros are loaded only on the user-detail page: AdminUserController.php:141-143 passes warnTemplates/suspendTemplates/banTemplates. In AdminModerationController@warn the message defaults to a single hardcoded string (AdminModerationController.php:208) with no template picker, and the report show() view (lines 179-184) passes no templates at all.

Suggested fix. Pass ModTemplate::getByCategory('warn'/'suspend'/'ban') into the moderation show() render and add a template <select> that fills the reason/message textarea, mirroring the user-detail page.

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