pathToClaudeCodeExecutable setting ignored; extension hardcodes embedded binary path

Environment

• OS: Linux (glibc)
• VS Code Insiders: with claude-code 2.1.282-linux-x64
• Claude Code CLI: 2.1.282 (working fine at /home/jean/.local/bin/claude)

Problem

The claudeCode.pathToClaudeCodeExecutable setting is not being respected. The extension ignores it and always attempts to launch the embedded binary at ~/.vscode-insiders/extensions/anthropic.claude-code-2.1.282-linux-x64/resources/native-binary/claude, which fails to launch.

Reproduction

1. Configure claudeCode.pathToClaudeCodeExecutable in settings.json pointing to a working Claude binary
2. Restart VS Code Insiders
3. Try to use Claude Code
4. Extension fails with: "Claude Code native binary... exists but failed to launch"

Logs

Error in extension logs (Claude VSCode.log):

Spawning Claude with SDK query function - cwd: /home/jean/Projets/infra/lcb-infra, permission mode: undefined, version: 2.1.282, /home/jean/.vscode-insiders/extensions/anthropic.claude-code-2.1.282-linux-x64/resources/native-binary/claude, resume: undefined

Error spawning Claude: ReferenceError: Claude Code native binary at /home/jean/.vscode-insiders/extensions/anthropic.claude-code-2.1.282-linux-x64/resources/native-binary/claude exists but failed to launch. This usually means the binary does not match this system's libc — e.g. spawning a musl-linked binary on a glibc Linux host fails because the musl dynamic loader (/lib/ld-musl-*) is missing. Specify a matching binary with options.pathToClaudeCodeExecutable.

The extension hardcodes the embedded binary path instead of checking/using the configured setting.

Notes

• The CLI binary works fine when called directly: /home/jean/.local/bin/claude --version returns 2.1.282
• The embedded binary exists and is glibc-compiled (ELF 64-bit with interpreter /lib64/ld-linux-x86-64.so.2) but extension fails to launch it
• Setting was verified in ~/.config/Code - Insiders/User/settings.json
• After fixing JSON syntax error and restarting, the setting still isn't being used by the extension