Naiyuan Qing 51bc5a818f fix(onboarding): decouple from workspace state and route invitees correctly (#1936) ...

PR #1868 conflated "has workspace" with "completed onboarding" —
restore `onboarded_at` as the single signal, and route invited users
through a dedicated /invitations page before they ever see onboarding.

- Backend: CreateWorkspace + AcceptInvitation atomically set
  onboarded_at alongside the member insert, establishing the
  invariant "member row exists ↔ onboarded_at != null" at the DB
  layer.
- Migration 065: one-shot backfill closes the dirty rows produced
  by PR #1868 (users with a workspace but onboarded_at == null).
- Entry points (web callback, login, desktop App): if onboarded_at
  is null, look up pending invitations by email and route to the
  new batch /invitations page; otherwise the resolver picks
  workspace / new-workspace as before.
- OnboardingPage: stops bouncing on hasWorkspaces; only
  hasOnboarded bounces. Unblocks the user from completing
  Step 3 (workspace creation) → Steps 4 / 5.
- StarterContentPrompt: only shows when the user is the solo
  member of the workspace, so invited users never get prompted to
  import starter content into someone else's workspace.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-30 16:05:53 +08:00

..

client_test.go

feat(analytics): full PostHog pipeline + 6 funnel events (MUL-1122) (#1367)

2026-04-21 14:42:52 +08:00

client.go

feat(analytics): instrument onboarding funnel (MUL-1250) (#1489)

2026-04-22 16:28:08 +08:00

events.go

fix(onboarding): decouple from workspace state and route invitees correctly (#1936)

2026-04-30 16:05:53 +08:00

posthog.go

feat(analytics): instrument onboarding funnel (MUL-1250) (#1489)

2026-04-22 16:28:08 +08:00