mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-05 21:39:54 +02:00
591e47842d
* refactor(onboarding): remove starter-content kit, unify install-runtime issue across mark-onboarded paths (MUL-2438) Drops the post-onboarding ImportStarterContent / DismissStarterContent flow (handler + routes + StarterContentPrompt + templates + locale strings + analytics event). The bug — web onboarding seeding 6+ starter issues without a runtime — only existed through that path; with it gone the source disappears. The "install a runtime" issue from BootstrapOnboardingNoRuntime is now the canonical no-runtime onboarding seed. The title/description and a LockAndFindActiveDuplicate-deduped seeder move to handler/no_runtime_issue.go, and CompleteOnboarding / CreateWorkspace / AcceptInvitation seed it whenever the workspace has no runtime yet, so every mark-onboarded entry point lands the user on a concrete next step. starter_content_state column is kept and continues to be claimed as 'imported' in all five entry points so older desktop builds (which still render the legacy dialog on NULL) don't surface it to accounts created after this change. Co-authored-by: multica-agent <github@multica.ai> * fix(onboarding): backfill starter_content_state for in-window NULL users (MUL-2438) 054 only covered pre-feature users. Anyone onboarded between then and the starter-content kit removal could still sit at NULL, and old desktop clients gate the legacy StarterContentPrompt on `starter_content_state IS NULL`. The import/dismiss routes are gone, so leaving these rows NULL would surface a dialog whose buttons 404. Mark them 'imported' to match the new helper's claim semantics. Co-authored-by: multica-agent <github@multica.ai> --------- Co-authored-by: Lambda <lambda@multica.ai> Co-authored-by: multica-agent <github@multica.ai>
13 lines
716 B
SQL
13 lines
716 B
SQL
-- Backfill `starter_content_state` for users who finished onboarding between
|
|
-- the original 054 migration and the removal of the starter-content kit
|
|
-- (MUL-2438). 054 only covered pre-feature users; everyone onboarded in the
|
|
-- window since then could still be sitting at NULL. Old desktop clients gate
|
|
-- the legacy StarterContentPrompt on `starter_content_state IS NULL`, and the
|
|
-- /api/me/starter-content/import|dismiss routes no longer exist, so leaving
|
|
-- these rows NULL would surface a dialog whose buttons 404. Mark them
|
|
-- 'imported' to match the new helper's claim semantics.
|
|
UPDATE "user"
|
|
SET starter_content_state = 'imported'
|
|
WHERE onboarded_at IS NOT NULL
|
|
AND starter_content_state IS NULL;
|