VS Code extension fails to activate on Windows — hardcoded Linux CI path in extension.js

Bug

Claude Code VS Code extension (v2.1.55) fails to activate on Windows with:

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'

The error is at extension.js:45:4848. A Linux CI build path was baked into the extension bundle and doesn't resolve on Windows.

Repro

1. Install Anthropic.claude-code v2.1.55 on Windows
2. Open VS Code
3. Any command (e.g. claude-vscode.terminal.open) → "command not found"
4. Error visible in: %APPDATA%\Code\logs\<session>\window1\exthost\exthost.log

Environment

• VS Code: 1.109.5 (x64)
• Extension: anthropic.claude-code@2.1.55-win32-x64
• CLI: claude 2.1.55 (works fine)
• OS: Windows 11 Pro 10.0.26200
• Platform: win32-x64

Full exthost log excerpt

ExtensionService#_doActivateExtension Anthropic.claude-code, startup: false, activationEvent: 'onStartupFinished'
[error] Activating extension Anthropic.claude-code failed due to an error:
[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\<user>\.vscode\extensions\anthropic.claude-code-2.1.55-win32-x64\extension.js:45:4848)

Notes

• Reinstalling / force-installing doesn't fix it — same version is served
• CLI (claude in terminal) works normally
• The path file:///home/runner/work/claude-cli-internal/... appears to be a GitHub Actions CI artifact that leaked into the production build