feat(code): include check for terminated for the instrumentation agent

[k11kirky]

Problem

The wizard feed's "done" state was hardcoded to false, meaning the UI never reflected when the wizard had actually completed, even after the underlying task reached a terminal status.

Changes

• Added a wizardCompleted boolean to the setup store along with a completeWizard action that sets it to true.
• Refactored subscribeToWizardEvents to separate the run ID polling loop from the event subscription logic. After subscribing, it now continuously polls the task run status and calls completeWizard when a terminal status is detected (up to 30 minutes).
• Exposed isWizardDone from useSetupRun and wired it into SetupView so the wizard feed displays the "Integration ready" done state when the wizard task finishes.

[k11kirky]

• feat(code): include check for terminated for the instrumentation agent #2026 👈 (View in Graphite)
• 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 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
apps/code/src/renderer/features/setup/services/setupRunService.ts:412-419
**All terminal statuses show "Integration ready"**

`completeWizard()` is called for every terminal status, including `failed`, `cancelled`, and `terminated`. This means a wizard that crashes or is cancelled will display "Integration ready" in the UI, giving users a false signal of success. Compare the discovery flow, which distinguishes `completed` from `failed`/`cancelled` and calls separate `finishSuccess`/`finishFailure` handlers. The wizard polling should only call `completeWizard()` when `taskRun.status === "completed"`, and handle error statuses separately (e.g., with an error state or at minimum by not marking the wizard as done).

### Issue 2 of 2
apps/code/src/renderer/features/setup/stores/setupStore.ts:169-172
The `log.info` call here is redundant — the service already logs `"Wizard task reached terminal status"` with richer context (`taskId`, `runId`, `status`) right before calling `completeWizard()`. Having the same message logged twice (once with context, once without) violates the OnceAndOnlyOnce rule and adds noise to logs.

```suggestion
      completeWizard: () => {
        set({ wizardCompleted: true });
      },
```

_{Reviews (1): Last reviewed commit: "feat(code): include check for terminated..." | Re-trigger Greptile}