MC-5042

## Bugs reported by Elmar via Telegram Source screenshot: `/home/lucienne/.hermes/image_cache/img_cdc139079004.jpg` Related ticket: MC-4843 ### Bug 1 — controller responses do not look like responses On the ticket detail activity thread, controller/Luci responses are rendered as internal-looking text blocks (e.g. `CONTROLLER:` and `[visibility-only controller]`) instead of a clean reply from Luci. This creates a weird UX: the user cannot tell what is a response, system audit text, or internal controller narration. Expected: - Human-facing controller replies should render as clear Luci replies in the activity thread. - Internal visibility/audit metadata should be visually separated/collapsed or clearly labelled as system/internal, not duplicated as user-facing answer text. - Avoid duplicate controller answer blocks when one human comment is handled. ### Bug 2 — user cannot mark the ticket done On MC-4843, pressing Done produced a red toast: `Failed to update status`. The sidebar showed Waiting and the action card offered Done, but the transition failed. Expected: - The Done button succeeds for the allowed transition from Waiting to Done, or shows a specific actionable error if blocked. - Status/action controls stay consistent after failure/success. - Add regression coverage for ticket status updates from the ticket-detail UI. ### Acceptance criteria - Reproduce both behaviours against the current ticket detail page. - Fix root causes, not only CSS. - Browser QA: ticket detail page can mark a waiting ticket done; toast/status update correctly. - UX QA: controller response presentation is understandable to a normal user and not duplicated/internal-looking. - Screenshot evidence for desktop and mobile-width ticket detail after the fix. ### Notes Tier 2 Mission Control UI/API bug. dev-loop mandatory. Likely touches `templates/ticket.html` / ticket activity rendering, `static/app.js`, and status-update route handling.