VS Code extension v2.1.55 (win32-x64) fails to activate: hardcoded Linux CI path in extension.js

Bug Description

The Claude Code VS Code extension v2.1.55 (win32-x64) fails to activate on Windows due to a hardcoded Linux CI build path embedded in extension.js.

Error Message

Activating extension 'Anthropic.claude-code' failed: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received 'file:///home/runner/work/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs'.

Steps to Reproduce

1. Install Claude Code VS Code extension v2.1.55 on Windows (win32-x64)
2. Open VS Code
3. Click the Claude logo icon in the UI, or attempt to run any claude-vscode.* command

Expected Behavior

The extension should activate and the Claude Code panel should open.

Actual Behavior

• The extension fails to activate silently
• "Claude" does not appear in the Output panel dropdown
• Clicking the logo icon shows: command 'claude-vscode.editor.openLast' not found
• Developer Tools console shows the activation failure with the Linux path error above

Root Cause

The extension.js file in the anthropic.claude-code-2.1.55-win32-x64 build contains 3 references to file:///home/runner/work/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs — a path from the CI/CD build environment (GitHub Actions runner). This path does not exist on Windows and causes the extension to crash on activation.

Environment

• OS: Windows 11 Home (10.0.26200)
• VS Code: 1.109.5 (x64)
• Extension version: 2.1.55 (win32-x64)
• Claude CLI version: 2.1.55