PR #2 Testing Checklist — Strip Hub/Mission Control Code

Critical

Extension cold start — Launch VS Code with the extension. No errors in Output panel ("Continue" channel) or Dev Tools console. (Found and fixed message.includes crash in webviewProtocol.ts + removed dead proxy-server error handling block.)
Fresh install onboarding — Delete/rename ~/.continue/config.yaml, restart. Onboarding card shows "Configure your models" (no Hub sign-in). (Removed "Credits" tab, fixed Ollama link padding, title font sizes, and "Google Gemini API API key" duplicate.)
Existing config loads — With existing config.yaml, models/context providers/MCP servers all load.
API key resolution from .env — Models using secrets from ~/.continue/.env or workspace .env authenticate and respond.
Config reload — Edit config.yaml while running, changes picked up without restart.

Profile/assistant switching — Assistant dropdown shows only local profiles. Switching works. (Fixed missing profiles list in GUI by adding profiles to configUpdate message. Also fixed initial Redux state label and adjusted dropdown styling.)
Compilation — tsc --noEmit passes for core, GUI, and VS Code extension.
Test suite — Vitest tests pass: LocalPlatformClient (8), LocalProfileLoader (2), doLoadConfig (2) — all 12 pass.
No telemetry network calls — Dev Tools Network tab shows no requests to posthog.com or sentry.io.
Agent mode tools — Start an agent conversation, all tools load correctly.

MCP servers connect — Configured MCP servers connect and tools appear.
Local blocks in YAML — Local model block files in .continue/models/ auto-merge into config correctly.
Background mode view — N/A, component removed from UI routing. No way to navigate to it.
Keyboard shortcut Cmd+Shift+' — Toggles between configs without errors.
Config settings page — Settings page renders cleanly, no Account dropdown or Organizations tab. (Removed GitHub issue/community links.)

"Main Config" naming — Fresh installs show "Main Config" as default profile name.
IntelliJ startup — Profiles load correctly after rebuilding core binary. (Core binary must be rebuilt for IntelliJ to pick up changes.)