[Bug] Claude Code extension doesn't add bundled CLI to integrated terminal PATH on Windows

Bug Description
Subject: Claude Code extension doesn't add bundled CLI to integrated terminal PATH

Problem:
The Claude Code extension bundles its own claude.exe at resources/native-binary/, but doesn't contribute this path to the VSCode integrated terminal environment on Windows. As a result, claude command is not available in the terminal out of the box.

Expected behavior:
Other VSCode extensions that bundle CLI tools (e.g. language servers, linters) properly contribute their binaries to the terminal PATH via the terminal.integrated.env.* contribution point or equivalent mechanism. Claude Code should do the same.

Workaround (fragile):
Manually adding to VSCode settings.json:

"terminal.integrated.env.windows": {
    "PATH": "${env:PATH};C:\\Users\\<user>\\.vscode\\extensions\\anthropic.claude-code-2.1.71-win32-x64\\resources\\native-binary"
}

This breaks on every extension update because the version number is baked into the path.

Request:
Fix the extension to automatically contribute the bundled

Environment Info

• Platform: win32
• Terminal: vscode
• Version: 2.1.71
• Feedback ID: e3cb8662-da3b-44af-b80f-2af3fdb49ec7

Errors

[]