The first draft dealt clients ranked by Priority view. That surface is Post-V1. This one deals tasks from the coach task inbox — a V1 surface with a fixed priority score, severity, due dates, and the three snooze presets the session needs.
It's also no longer the whole app. Rounds is one tab beside Clients and Chat, because coach mobile owes V1 client context, progress and nutrition review, and messaging too.
Reads GET /coach-tasks sorted by priority_score — the fixed V1 weights. No rankScore, no PriorityTier, no reason stack. Severity chips replace tiers.
Rounds is the default tab. Clients and Chat carry profile, progress, nutrition review, and messaging. You can always reach a client you weren't dealt.
Review tasks can't resolve in the inbox. Instead of hiding it, the card changes shape and says where it's sending you — and that it'll bring you back.
Warmer palette: cream, apricot light, indigo ink. Colour carries severity — coral is urgent, amber is high, sky is normal — and mint only ever means done.
BadgeCountPolicy.MESSAGE_SENT with the message linked.Workout review can't be closed from here — it resolves when you finish the review. You'll land back at card 6.
DirectResolutionPolicy made visible. Review tasks leave the session and return — the card admits it rather than faking a resolve./coach-tasks and /summary; writes /start, /snooze, /resolve, /dismiss. Uses the fixed V1 priority weights for deck order.ONE_HOUR, TOMORROW_MORNING, NEXT_CHECK_IN.PROGRESS_ALERT tasks, so they arrive in the deck at urgent severity. Handling a flag beyond message/snooze still needs a flag screen under Clients.priority_score to rankScore, the summary block grows the reason stack, and a ranked Clients tab appears. Nothing here has to be thrown away.The list-versus-session question is yours, not mine. Everything else here is now inside V1 scope, but the task inbox page explicitly specifies a grouped list for coach mobile. Picking Rounds means editing that page — which is fine, it's a design decision the doc recorded before a designer looked at it, but it should be a decision rather than a drift.
The card got weaker and I want to be clear about that. The first draft's reason stack — reply gap +70, adherence +30 — was the most persuasive thing in the whole exploration, and it's gone, because that arithmetic only exists in Priority view. What's left is a task summary and whatever counters the payload can safely carry. Rounds is still worth building on the inbox; just don't expect this version to feel as sharp as the one you liked.
Two things I'd prototype before committing: whether the hand-off round-trip actually feels like it returns you to the session or breaks it, and whether the session survives RTL. Both are cheap to test and both can sink the direction.