VSCode extension /resume doesn't respect CLAUDE_CONFIG_DIR from claudeCode.environmentVariables

Bug Description

The VSCode extension passes CLAUDE_CONFIG_DIR to the CLI subprocess via the claudeCode.environmentVariables setting, but the extension's own session lookup (used by /resume) still reads from the default ~/.claude/ path. Sessions exist in the configured directory but aren't listed when using /resume.

Steps to Reproduce

1. Set CLAUDE_CONFIG_DIR in VSCode settings:

``json
"claudeCode.environmentVariables": [
{
"name": "CLAUDE_CONFIG_DIR",
"value": "/home/user/data/.claude"
}
]
``

1. Use Claude Code — sessions are correctly written to /home/user/data/.claude/projects/
2. Run /resume — no sessions are listed

Evidence

• Session .jsonl files exist in the configured directory (/home/user/data/.claude/projects/)
• The extension writes its own IDE lock file to the default ~/.claude/ide/ rather than the configured directory, confirming it doesn't use CLAUDE_CONFIG_DIR for its own operations
• No ide/ directory exists in the configured CLAUDE_CONFIG_DIR path

Expected Behavior

/resume should list sessions from the directory specified by CLAUDE_CONFIG_DIR in claudeCode.environmentVariables.

Environment

• Running in a cloud VM (code-server / VS Code remote)
• CLAUDE_CONFIG_DIR is needed because the default ~/.claude/ doesn't persist between VM sessions