Get Home Setup Progress

A clinician checked in. Its own typed field, not a CardState.

The deck is a static catalogue of setup cards - one title, one description, one tap target, dismissal keyed into onboarding_setup_prefs. This card has a quote block, a reply line, TWO actions and per-check-in dismissal that must land on check_in_recipients. Forcing it into CardState means either three check-in-only fields every other card carries as dead weight, or branching the renderer on card_id - at which point the shared shape has bought nothing.

What actually matters is kept: one request, and copy composed server-side.

The daily-reminder activation card. Deliberately NOT a CardState.

Same call, and the same reasoning, as CheckInCard above. The deck's CardState is a 48%-wide grid tile padded to exactly four slots: icon row, a lora-h4 title, a CTA text label. This card is full-width with a description paragraph and a primary Button, and it is condition-dismissed off daily_reminders, a table no other card touches. Forcing it into the deck gives a half-width tile in an awkward fifth slot on a third row.

A typed field also keeps it mobile-only for free: a new deck card_id auto-renders on web, whereas a field appweb never destructures is inert. Push is a mobile capability we own end-to-end; web parity is V2.

The activation deck as its own field. Mobile-only by construction.

This is the isolation mechanism, and it is also the kill switch. Web reads the same endpoint and forks its greeting on all_initial_complete; a field appweb never destructures is inert there, so the activation screen can ship, cohort and roll back server-side with no client release and no feature flag (flag delivery is broken product-wide, #7737 - a flag-gated activation home would ship dead).

Absent means today's screen, exactly.