feat: Add setup wizard integration and data-less task discovery

[charlesvien]

Problem

New users had no guided path between onboarding and their first task, leaving them on a blank screen.

Changes

1. Add SetupView with animated scan feed showing real-time agent activity during repo analysis
2. Integrate PostHog wizard task that configures SDK integration (cloud or worktree mode)
3. Add data-less task discovery that scans the repo for quick wins (bugs, dead code, stale flags, etc.)
4. Wire setup flow into sidebar, navigation store and onboarding completion
5. Add analytics events constants and tracking for setup lifecycle
6. Add SuggestedTasks component displaying categorized discovered tasks with icons

How did you test this?

Manually

[charlesvien]

• feat(code): enricher run #2016
• feat: Add setup wizard integration and data-less task discovery #1745 👈 (View in Graphite)
• feat: Revamped product tours #1661
• feat: Revamped onboarding #1657
• chore: Delete the tutorial #1656
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Prompt To Fix All With AI

Fix the following 3 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 3
apps/code/src/renderer/features/setup/services/setupRunService.ts:335-338
**Duplicate `subscribeToWizardEvents` call creates two active tRPC subscriptions**

`onTaskReady` already calls `setWizardTaskId`, `invalidateQueries`, and `subscribeToWizardEvents` when the task is ready. Because `onTaskReady` fires inside `saga.run()`, these are called again unconditionally when `saga.run()` resolves. The result is two independent polling loops both eventually calling `trpcClient.agent.onSessionEvent.subscribe` for the same `taskRunId`, so every wizard activity event is pushed to the feed twice (duplicate feed entries). The second call also overwrites `this.wizardSubscription`, leaking the first subscription until the abort signal fires. The post-`saga.run()` block should be removed; `onTaskReady` is already the correct place for this work.

```suggestion
      // onTaskReady already called setWizardTaskId / subscribeToWizardEvents;
      // nothing more to do after saga.run() resolves.
```

### Issue 2 of 3
apps/code/src/renderer/features/onboarding/stores/onboardingStore.ts:12
**`isConnectingGithub` is unused dead state**

`isConnectingGithub` is declared in the interface and initialised in `initialState`, but has no corresponding setter action, is never read anywhere in this PR, and is excluded from `partialize`. It appears to be leftover scaffolding that was never wired up. Leaving it here violates the "no superfluous parts" rule and will confuse future readers who look for where it is toggled.

### Issue 3 of 3
apps/code/src/renderer/features/onboarding/components/context-collection/SuggestedTasks.tsx:26-43
**`CATEGORY_CONFIG` duplicated across two files**

An identical `CATEGORY_CONFIG` record (mapping `DiscoveredTask["category"]` → icon + colour) exists in both `SuggestedTasks.tsx` and `DiscoveredTaskDetailPane.tsx`. If a new category is added to `DiscoveredTask`, both files need to be updated independently. Extracting the config to a shared module (e.g. `@features/setup/utils/categoryConfig.ts`) would satisfy the OnceAndOnlyOnce rule and remove the risk of the two configs drifting.

_{Reviews (1): Last reviewed commit: "Wizard integration and first data-less t..." | Re-trigger Greptile}

[adboio]

slack stamp from charles 🫡