VS Code extension v2.1.51 fails to activate on Windows: hardcoded Linux CI path in extension.js

Bug Description

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

Error

From exthost.log:

Activating extension Anthropic.claude-code failed due to an error:
TypeError: 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'
    at Object.<anonymous> (c:\Users\A\.vscode\extensions\anthropic.claude-code-2.1.51-win32-x64\extension.js:45:4602)

Impact

• All claude-vscode.* commands fail with "command not found" (e.g., claude-vscode.editor.openLast, claude-code.insertAtMentioned)
• The extension never activates, so no VS Code integration features work
• Claude Code CLI itself works fine

Environment

• OS: Windows 11 Pro 10.0.26200
• VS Code: 1.109.5 (x64)
• Extension: anthropic.claude-code v2.1.51 (win32-x64)
• Claude CLI: 2.1.51

Steps to Reproduce

1. Install Claude Code extension v2.1.51 on Windows
2. Open VS Code
3. Extension fails to activate silently
4. Any claude-vscode.* command shows "command not found"

Root Cause

The build artifact (extension.js line 45) contains a hardcoded file:///home/runner/work/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs path from the GitHub Actions CI runner environment. This path is invalid on Windows and causes a TypeError during activation.

Workaround

None found. Reinstalling does not help since the path is baked into the distributed extension bundle.