MC-4345

Elmar mobile QA feedback: the MC mobile site is still failing the intended AionUi/Codex-style 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 AionUi reference pattern to emulate: - Sessions/history live in the navigation rail/sidebar with New Chat; on phone this must become an obvious drawer/sheet/tab, not disappear. - Main pane is the selected chat/session workspace. - Composer is the primary action surface. - Agent/provider choices live adjacent to the composer; exact model is visible as a pill in/near the composer. Required UX correction: 1. Mobile Home/Cockpit must make active chats/sessions immediately visible and openable. Show active runtime sessions plus recent chats in a clear session rail/list. 2. The Controller must not be a special dominant card. Treat Controller as just one session/chat in the session list when relevant. 3. Recent chats must not look like controller internals. Each item needs readable title, status/runtime hint, age/active indicator, and a clear tap target to open the conversation. 4. New Chat must remain top-level and obvious. 5. Provider/model/profile controls must be visible near the composer at send time, not buried in settings. 6. Runtime honesty/shared-runtime copy should be compact/help text only; it must not crowd out sessions or the composer above the fold. 7. Preserve desktop behavior where appropriate, but optimize 375px mobile first. Implementation constraints: - Follow /dev-loop before code changes. - Use screenshot-discovery first: capture current live desktop + 375px mobile screenshots before editing and post findings on the ticket. - Use Worker Design Gate standards: Linear × Vercel × Sentry spacing, touch targets, no clipped/indistinguishable chat titles, no DOM-only approval. - This is a follow-up to the failed MC-4327 mobile UX outcome; do not close because tests pass if the live 375px screenshot is still dashboard/controller-first. Acceptance gate: - Live Tailscale route http://100.118.207.3:3001/ on 375px shows a clear mobile session/chat list entry point and/or visible active sessions above the fold. - Opening an existing chat/session and starting a new chat both work on mobile. - Controller appears as a normal session/chat, not a separate primary dashboard object. - Composer shows current provider/model/profile context at send time. - Attach fresh 375px screenshot and desktop screenshot; mobile_review_required must be APPROVED at width 375 before in_review/done. - Run relevant home/chat regression tests plus browser smoke on the live page. Expected check-in: within 45 minutes of pickup with current screenshot findings or a blocked reason. ORCHESTRATOR UPDATE 2026-05-28 06:18 SAST — broaden scope after Elmar's latest screenshot / QA: This is NOT a mobile-only bug. Desktop/wide layout is also nowhere near AionUi. Treat the current page as a failed design direction, not a small responsive fix. Latest evidence: - /home/lucienne/.hermes/image_cache/img_1f7ca6f534d5.jpg Critical findings from visual review: - It is a desktop cockpit/admin layout squeezed into a phone: persistent sidebar + desktop top nav + center pane all remain at once. - Desktop/wide version is also structurally wrong: too much controller/cockpit framing, not a clean AionUi-like chat workspace. - The current "Controller" card must be demoted/removed from primary layout. Controller/runtime is context metadata or a normal session, not the product's main object. - The target is a full AionUi-style Home shell across desktop and mobile: sessions rail/drawer + active conversation workspace + composer + visible agent/provider/model controls. Revised acceptance: 1. Desktop: resembles AionUi structurally — left sessions rail with New Chat + history; main active chat/workspace; composer as primary task surface; model/provider/profile controls in/near composer. No cockpit/controller-dominant landing page. 2. Mobile: no desktop sidebar/top-tab squeeze. One primary pane at a time; sessions behind drawer/sheet or a clear chats tab; full-width active workspace/composer. 3. Controller is represented only as compact runtime/session context or an ordinary session entry if needed. 4. Top navigation collapses appropriately; no tiny desktop tab strip on 375px. 5. Runtime honesty copy is hidden/collapsed/help text; it cannot occupy primary above-the-fold real estate. 6. Must provide fresh desktop and 375px screenshots and pass vision review against AionUi before in_review/done. If existing implementation is trending toward incremental CSS tweaks, stop and redesign the Home IA first.