mirror of
https://github.com/multica-ai/multica.git
synced 2026-06-17 03:38:32 +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>
2.1 KiB
2.1 KiB
What does this PR do?
Related Issue
Closes #
Type of Change
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Refactor / code improvement (no behavior change)
- Documentation update
- Tests (adding or improving test coverage)
- CI / infrastructure
Changes Made
How to Test
Checklist
- I have included a thinking path that traces from project context to this change
- I have run tests locally and they pass
- I have added or updated tests where applicable
- If this change affects the UI, I have included before/after screenshots
- I have updated relevant documentation to reflect my changes
- If I added a new runtime / coding tool / UI tab, I synced the change to landing copy (
apps/web/features/landing/i18n/) and relevant docs (apps/docs/content/docs/) - If this PR touches Chinese product copy, I checked it against
apps/docs/content/docs/developers/conventions.zh.mdx(terminology, mixed-rule fortask/issue/skill) - I have considered and documented any risks above
- I will address all reviewer comments before requesting merge
AI Disclosure
AI tool used:
Prompt / approach: