MC-4366

Elmar reported a live MC Home Chats drawer bug from mobile screenshot /home/lucienne/.hermes/image_cache/img_16a388c1e0fa.jpg. Observed behavior: - On Home mobile, opening Chats and tapping the active session "Build personalized NBLM radio curation pipeline / MC-4365" navigates to the ticket detail/Board page: /ticket/4365. - User expected clicking a chat/session in the Chats menu to open the chat/workspace conversation on Home, not the ticket detail page. Live reproduction evidence from orchestrator (375px Playwright on http://100.118.207.3:3001/): - Chats drawer active session link text: "Build personalized NBLM radio curation pipeline MC-4365 in progress claude_opus_1m_high ..." - href is currently http://100.118.207.3:3001/ticket/4365 - Recent chat rows below correctly link to /?thread=<id>, e.g. /?thread=472. Root-cause hypothesis: The active-session/ticket row macro uses the ticket detail URL for ticket-backed active sessions. For Home Chats, the primary tap target should select/open the associated chat/session workspace on Home. Ticket detail can remain a secondary chip/action, but not the main row tap. Required behavior: 1. In the Home Chats drawer/desktop sessions rail, tapping any chat/session row opens the Home chat/workspace pane, not Board/ticket detail. 2. Ticket-backed active sessions should prefer the associated chat_thread/session route (likely /?thread=<thread_id> or equivalent). If no chat thread exists, create/resolve one or show a secondary explicit ticket link rather than silently navigating to Board. 3. Keep a clearly labeled secondary ticket link/chip for MC-4365 if needed. 4. Regression test must verify active ticket/session rows do not use /ticket/<id> as the primary href in Home Chats. 5. Mobile 375px browser smoke: open Home -> Chats -> tap the MC-4365 active/session row -> remain on Home with selected chat/workspace, not /ticket/4365. 6. Keep MC-4345 AionUi gates passing: no inline mobile sessions; sessions behind Chats; provider/model near composer. Use /dev-loop before code edits. Screenshot discovery first per worker-design-gate. Run focused Home/chat tests and live browser smoke. Commit and push, then report REVIEW with screenshots/tests/commit.