MC-4252

Elmar feedback after reviewing MC-4247 live /life screenshots: The page now has the right capabilities, but the design/UX is not good enough. It is a very long page with lots of repeated buttons and confusing controls. Mobile is somewhat better/shorter, but it differs from desktop (for example runtime/profile choice visibility). Elmar also asked for clarity on what Comment does, who picks up Hermes Luci/Hermes Iris actions, and why Iris actions have no visible effect. Design direction / references: Use popular-web-designs skill as a design gate. Default target: Vercel light precision + Linear/Raycast productivity polish + Sentry-style data-dense dashboard clarity. The page should feel like a polished modern personal ops dashboard, not an admin form repeated per item. Current UX problems to fix: 1. Too many controls are visible on every item by default: comment box, done/cancel/not-needed, prompt, runtime/Luci/Iris, training. 2. No clear primary action per item; blue "Send to runtime" visually dominates even when not the normal action. 3. Labels are unclear/internal: Comment, Cancel, Not needed, Send to runtime, Hermes Luci, Hermes Iris. 4. The comment flow is passive but the UI does not say that. It only adds a note to the ticket/item and does not start work. 5. Hermes Luci routes/picks up via Luci/MC runtime; this needs visible confirmation with ticket/runtime link. 6. Hermes Iris currently makes the ticket assigned_to=Iris/waiting and calls an Iris comment tool, but does not show a visible Iris runtime/result. This is confusing and likely needs a visible handoff receipt/status/result link. 7. Desktop and mobile need consistent capability parity, with mobile using progressive disclosure rather than hiding important routing controls. 8. The page is too long; item controls should use progressive disclosure, compact rows/cards, selected-item detail/drawer, or action menus. Acceptance criteria: - Redesign /life item cards around compact scanning first: title, source, priority/due, suggested action, one clear primary CTA, and small secondary menu/actions. - Move comment/prompt/routing/training into an expanded detail drawer/action sheet/selected item panel, not repeated open fields on every card. - Rename actions into user language, e.g. Add note, Ask Luci, Ask Iris, Run with assistant, Mark complete, No action needed. Avoid exposing "runtime" as the default label unless in advanced mode. - Add visible post-click feedback for every action: what happened, who owns it now, status, and direct link to the ticket/runtime/Iris handoff. - Make Comment explicitly passive: "Add note only" or similar; it must not imply pickup. - Make Hermes Luci/Hermes Iris semantics explicit and working: Luci starts/queues MC work; Iris either creates a visible Iris task/thread/receipt or the UI says it is assigned to Iris and waiting. - Keep learning/training secondary and collapsed. - Preserve all existing functional APIs unless intentionally replaced. - Browser QA on desktop and mobile with screenshots. Gate against visual/design criteria from popular-web-designs: Vercel × Linear/Raycast/Sentry polish, not generic admin UI. Related: MC-4247 implemented first functional version. This ticket is the polish/clarity follow-up.