MC-4258

Follow-up from Elmar after MC-4252 was marked done. Elmar agrees the current Life Dashboard UX is not good enough. Problems observed: - "Ask Iris" is unclear: today it records a ticket handoff/comment and sets assigned_to=Iris/status=waiting, but it does not obviously reach the Iris Telegram/session work queue or produce a visible Iris response path. - After clicking Ask Iris, the card can recompute and show "Ask Luci", which feels like the action silently changed target. - Ask Iris / Ask Luci currently fire too quickly. They should first open an inline instruction composer with a text box and Send/Cancel, so Elmar can say what he wants done before work is queued. - Too many core actions are hidden behind Details. There is no quick card-level way to mark Done / No action needed / Cancel. - Training controls are unclear. "Training done" is especially confusing; it actually closes without adding a rule. Acceptance criteria: 1. Every Life Dashboard card exposes quick actions without opening Details: Done, No action needed, Ask Iris, Ask Luci, Details/Open ticket as appropriate. 2. Ask Iris and Ask Luci open an inline composer before sending. Composer includes instruction textarea plus Send and Cancel. No queue/handoff happens until Send. 3. After Ask Iris is sent, the card state persists as "Waiting on Iris" / "Sent to Iris" and must not flip back to "Ask Luci" just because the default primary action recalculates. 4. Define and implement the actual "Ask Iris reaches Iris" contract. At minimum, it must create/update a durable Iris-visible Life/MC handoff that Iris' proactive scan can pick up; ideally it also appears in Iris' Life queue with a clear receipt/status. 5. Rename or explain training actions in plain language: - Not important -> "Suppress similar subject" or equivalent - Noisy sender -> "Suppress this sender/domain" - Noisy subject -> "Suppress similar subjects" - Always sender/subject -> "Always surface..." - Wrong class -> "Needs re-triage" - Training done -> rename to "Close without changing rules" 6. Keep advanced training controls behind a clearly labelled "Teach Life Manager" area with short helper copy. 7. Add/adjust tests for the card quick actions, composer-before-send behaviour, Iris waiting state, and training label text. 8. Run browser/Tessa-style desktop + mobile verification before marking done. Reference: follow-up to MC-4252 Life Dashboard redesign.