MC-4367

Elmar mobile QA follow-up after MC-4345/MC-4366: Home still feels "shocking" on phone and does not match the AionUI interaction model. User evidence: - /home/lucienne/.hermes/image_cache/img_91b8e2d9ed84.jpg - /home/lucienne/.hermes/image_cache/img_f94f7301633c.jpg - /home/lucienne/.hermes/image_cache/img_7ae01a21c7c0.jpg Specific failures to fix: 1. Mobile must make active chats/sessions immediately obvious/openable; no hidden/unclear route to active sessions. 2. Recent chats must not appear to be "with the controller"; Controller is just one session row, not a special mental model. 3. Mobile Chats/session sheet should mirror AionUI: New Chat + active sessions + recent sessions in one obvious list/drawer, with selected session opening the workspace. 4. Main mobile Home should be chat/workspace-first: selected session and composer dominate; avoid dashboard/cockpit language if it confuses the IA. 5. Ticket/session rows should distinguish: open chat/session primary, ticket chip secondary. 6. Must keep MC-4366 routing: session row primary href stays Home/thread, never /ticket/<id>. Acceptance: - Inspect the AionUI reference pattern captured in ticket context/screenshots and current Home mobile at 375px. - Implement a mobile IA/polish pass so active sessions are visible in an obvious Chats/session surface and Controller is just a row. - Add/adjust regression tests for mobile session visibility/copy and Controller-as-normal-session behavior. - Live 375px screenshot/vision review required; attach screenshot path. - Run focused tests and smoke route checks. - Commit + push. Report REVIEW with commit, tests, screenshots, and live mobile verdict. Expected check-in: within 45 minutes.