feat(platform): Backend completion of Onboarding tasks

[kcze]

Make onboarding task completion backend-authoritative which prevents cheating (previously users could mark all tasks as completed instantly and get rewards) and makes task completion more reliable. Completion of tasks is moved backend with exception of introductory onboarding tasks and visit-page type tasks.

Changes 🏗️

• Move incrementing run counter backend and make webhook-triggered and scheduled task execution count as well
• Use user timezone for calculating run streak
• Frontend task completion is moved from update onboarding state to separate endpoint and guarded so only frontend tasks can be completed
• Graph creation, execution and add marketplace agent to library accept source, so appropriate tasks can be completed
• Replace client.ts api calls with orval generated and remove no longer used functions from client.ts
• Add resolveResponse helper function that unwraps orval generated call result to 2xx response

Small changes&bug fixes:

• Make Redis notification bus serialize all payload fields
• Fix confetti when group is finished
• Collapse finished group when opening Wallet
• Play confetti only for tasks that are listed in the Wallet UI

Checklist 📋

For code changes:

• I have clearly listed my changes in the PR description
• I have made a test plan
• I have tested my changes according to the test plan:
  • Onboarding can be finished
  • All tasks can be finished and work properly
  • Confetti works properly

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 4 🔵🔵🔵🔵⚪

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Type Validation The POST /onboarding/step handler validates the 'step' argument using get_args on FrontendOnboardingStep. FastAPI/Orval may coerce values differently; ensure the request body schema strictly restricts values and that invalid enum strings are rejected as intended. async def onboarding_complete_step( user_id: Annotated[str, Security(get_user_id)], step: FrontendOnboardingStep ): if step not in get_args(FrontendOnboardingStep): raise HTTPException(status_code=400, detail="Invalid onboarding step") return await complete_onboarding_step(user_id, step) Concurrency increment_runs reads onboarding then updates counters and computes milestones based on old completedSteps. In concurrent executions, milestones or counters might race. Consider doing the update and step computation in a transaction or re-fetching state after update to avoid duplicate or missed completions. async def increment_runs(user_id: str): """ Increment a user's run counters and trigger any onboarding milestones. """ user_timezone = await _get_user_timezone(user_id) onboarding = await get_user_onboarding(user_id) new_run_count = onboarding.agentRuns + 1 last_run_at, consecutive_run_days = _calculate_consecutive_run_days( onboarding.lastRunAt, onboarding.consecutiveRunDays, user_timezone ) await UserOnboarding.prisma().update( where={"userId": user_id}, data={ "agentRuns": new_run_count, "lastRunAt": last_run_at, "consecutiveRunDays": consecutive_run_days, }, ) milestones = _get_run_milestone_steps(new_run_count, consecutive_run_days) new_steps = [step for step in milestones if step not in onboarding.completedSteps] for step in new_steps: await complete_onboarding_step(user_id, step) Backward Compatibility Notification payload now enforces event type and OnboardingNotificationPayload.step as OnboardingStep and allows extras via model_config. Verify all producers/consumers (WS, Redis serializer) handle this shape and that older clients expecting string step don't break. type: str event: str model_config = pydantic.ConfigDict(extra="allow") class OnboardingNotificationPayload(NotificationPayload): step: OnboardingStep

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[0ubbe]

Code looks good, nice cleanp Front-end side 👍🏽 💯