feat: add Altimate AI setup step and MCP gating to onboarding wizard

[ralphstodomingo]

Summary

Add the Altimate AI setup step to the onboarding wizard (stacked on #1819). This enables API key management, dbt integration creation, and MCP tool gating.

• Step 2 — Altimate Setup: AltimateSetupStep.tsx with API key validation, integration creation, sync status tracking, DataPilot installation, and progress cards
• API key input: AltimateKeySetup.tsx standalone component
• Backend handlers: 8 new message handlers in onboardingPanel.ts (saveAltimateKey, checkAltimateConfiguration, createDbtIntegration, getIntegrations, getIntegrationSyncStatus, checkDatapilotInstalled, installDatapilot, getAltimateConfig)
• MCP gating: Tools only register after Altimate setup completes (src/mcp/index.ts)
• Integration type change: dbtPowerUserExtension.ts now calls reinitialize() instead of reloading the window

Dependencies

Stacked on PR #1819 (feat/onboarding-dbt-troubleshooting).

Test plan

• npm run compile passes
• npm run test — all 13 suites pass (135/136, 1 pre-existing skip)
• Wizard now shows 3 steps: Prerequisites + Altimate Setup + Tutorials
• Step 2: API key validation, integration creation, sync status polling
• MCP tools only register after Altimate setup completes
• Changing dbt integration type reinitializes without window reload

🤖 Generated with Claude Code

---

Important

Adds Altimate AI setup step and MCP gating to onboarding wizard, with API key management and dbt integration support.

• Behavior:
  • Adds AltimateSetupStep.tsx for Altimate AI setup in onboarding wizard, handling API key validation, integration creation, sync status, and DataPilot installation.
  • Introduces AltimateKeySetup.tsx for standalone API key input.
  • Adds MCP gating in src/mcp/index.ts to register tools only after Altimate setup.
• Backend Handlers:
  • Adds 8 new message handlers in onboardingPanel.ts for Altimate setup (saveAltimateKey, checkAltimateConfiguration, createDbtIntegration, getIntegrations, getIntegrationSyncStatus, checkDatapilotInstalled, installDatapilot, getAltimateConfig).
• Integration Changes:
  • Changes dbtPowerUserExtension.ts to call reinitialize() on dbt integration type change instead of reloading window.
• Misc:
  • Updates SetupWizard.tsx to include Altimate setup step in the wizard.

^{This description was created by for 01d0dc2. You can customize this summary. It will automatically update as commits are pushed.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e4a1d7c2-eb8b-445f-884d-d95931e94b04

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/onboarding-altimate-setup

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 01d0dc2 in 20 seconds. Click for details.

• Reviewed 2070 lines of code in 6 files
• Skipped 0 files when reviewing.
• Skipped posting 0 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

Workflow ID: wflow_KYMobSZve4kNvEhj

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[sentry]

Bug: The altimate.onboardedMcpServer configuration flag is checked to gate MCP tool registration but is never set to true after onboarding, effectively disabling the feature.
_{Severity: CRITICAL}

Suggested Fix

Upon successful completion of the onboarding wizard, update the global configuration to enable MCP. This can be done by calling workspace.getConfiguration("altimate").update("onboardedMcpServer", true, ConfigurationTarget.Global).

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: src/mcp/index.ts#L109

Potential issue: The MCP registration logic in `src/mcp/index.ts` includes a check for
the `altimate.onboardedMcpServer` configuration flag. This flag is intended to be set to
`true` after a user completes the new onboarding wizard. However, no code path in the
pull request updates this flag's value from its default of `false`. As a result, the
registration code always returns early, preventing MCP tools from ever being registered
or becoming available to any user, regardless of their credential status. This
completely disables the Model Confidence Platform (MCP) functionality.

[sentry]

Bug: A race condition in fetchSyncStatus can display incorrect sync data. Rapidly switching environments causes concurrent updates to the shared integration.sync_history, leading to a data mismatch.
_{Severity: MEDIUM}

Suggested Fix

Modify the data structure to store sync_history on a per-environment basis instead of a single field on the Integration object. This could involve moving sync_history to the IntegrationEnvironment interface or changing it to a dictionary keyed by environment ID on the Integration object. Additionally, consider implementing a mechanism to cancel previous pending requests when a new one is initiated.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: webview_panels/src/modules/onboarding/AltimateSetupStep.tsx#L456

Potential issue: A race condition occurs when fetching the synchronization status for
different environments within the same integration. The `fetchSyncStatus` function is
called without `await` when a user changes the selected environment. If a user switches
environments quickly, multiple asynchronous requests are fired. Because the
`sync_history` is stored on the parent `Integration` object rather than per-environment,
a slower, earlier request can resolve after a newer one, overwriting the `sync_history`
with stale data. This causes the UI to display an incorrect sync status for the
currently selected environment.

[mdesmet]

I htink you should rebase this to latest master

[ralphstodomingo]

Superseded by stacked PRs #1847 (API key substep) and #1848 (integration substep).