Area: Forums (audit p2) · Surface: GET /thread/{slug} (ForumController@showThread), post display · Dimension: competitor-gap · Severity: minor
Circle and Discourse both offer one-click inline translation of community posts so multilingual communities can participate across languages without copy-pasting into Google Translate. We already have the exact capability (dmTranslate) and the AI plumbing; it is simply not exposed on forum posts. For tenants running international communities this directly limits cross-language participation, and it is low-effort given the DM implementation already exists.
Evidence
Translation is implemented and wired ONLY for DMs: platform/src/Services/AI/MemberAI.php:108 `public static function dmTranslate(...)` calling feature key ai_dm_translate, surfaced in platform/templates/messages/conversation.php. grep for translate across templates/forums/thread.php and ForumController returns only an unrelated CSS `translateY`. There is no per-post 'Translate' affordance and no ai_forum_translate feature key in AIFeatureCatalog (the 30 forum AI features cover title/body/summary/tone but not translation).
Suggested fix. Add an ai_forum_translate feature key and a per-post 'Translate' button in templates/partials/post-toolbar.php / the post action row that POSTs the post body to a thin wrapper around the existing MemberAI translate call, rendering the translation inline beneath the original (same UX pattern as the AI thread-summary card already in thread.php:818).
Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.
Patrick Bass
@mobieus