Area: Forums (re-run) (audit p2r) · Surface: templates/partials/post-toolbar.php (reply box) vs templates/forums/create-thread.php (new-thread body) · Dimension: feature-improvement · Severity: minor
Members do the bulk of their writing in replies, not new threads, yet the reply editor has strictly less AI help than the new-thread editor. Competitor editors (Discourse AI composer, Notion AI, Circle's editor) offer the same proofread/improve/expand set everywhere you type. The asymmetry is inconsistent and leaves the most-used surface under-served — and the prompts (Prompts.php:352, :463) already exist, so this is wiring, not new capability.
Evidence
New-thread body wand offers tighten/expand/clarify (create-thread.php:126 comment 'wand: ai-assist.js opens its tighten / expand / clarify'; backed by Prompts.php:463 style tag 'tighten|expand|clarify' and Prompts.php:352 'finish and tighten a member rough forum draft ... fixes obvious grammar and spelling ... completes an unfinished final thought'). The reply box (post-toolbar.php, included by thread.php:1394) exposes only the tone-shift wand (post-toolbar.php:142-152, data-ai-feature='ai_forum_tone_shift'). No proofread/grammar/finish-draft control in the reply path: `grep -niE 'proofread|grammar|improve.?writing|finish' templates/forums/thread.php templates/partials/post-toolbar.php` returns nothing relevant.
Suggested fix. Surface the existing finish/improve-draft (Prompts.php:352) and tighten/expand/clarify (Prompts.php:463) wands in post-toolbar.php so replies get the same AI affordances as new threads, gated by the same per-tenant flags + spend cap.
Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.
Patrick Bass
@mobieus