On completion → set user.onboardedAt = now() → redirect to /dashboard.

Schema gaps before we can build it — design captures more than the current schema holds:

1. user.handle (text, unique) — for holo.bio/<handle>. Not in schema.

2. persona — 4 options, not in schema. Either user.persona (text or new persona_t enum) or a separate table.

3. audience target — user.target_followers (int) + user.target_date (date). Not in schema.

4. posting cadence — user.posting_cadence (text or new cadence_t enum). Not in schema.

5. weekly check-ins toggle — notification preference, not in schema.

6. platform_t enum is missing linkedin and twitch that the design uses.

Recommendation: before touching apps/web, decide which of those 6 to add to the schema first (probably all of them — they're cheap and the design is already validated). Then build the routes top-down: /onboarding (welcome) → /onboarding/name → /.../niche → /.../connect → /.../goal → finalize → /dashboard. Auth-guard everything via beforeLoad so unfinished onboarding can't slip past.

Want me to:

• (a) brainstorm the schema additions + flow details first (run /brainstorm for a proper exploration), or

• (b) sketch a concrete implementation plan now (writes a plan file, you approve, then we execute), or

• (c) just implement step 1 end-to-end first as a vertical slice and iterate from there?