VSCode extension loses conversation history scroll after WSL reconnection

Description

When using Claude Code VSCode extension in WSL2 environment, after WSL reconnection (e.g., PC sleep/wake, Developer: Reload Window), the conversation history in the UI becomes limited to only the most recent exchange. Users cannot scroll back to see previous messages in the same session.

Environment

• OS: Windows 11 + WSL2 (Ubuntu)
• Claude Code Version: 2.1.15
• VSCode: Running with Remote - WSL extension
• IDE: Antigravity IDE (VSCode-based)

Steps to Reproduce

1. Start a conversation in Claude Code VSCode extension (WSL environment)
2. Have multiple back-and-forth exchanges (e.g., 10+ messages)
3. Put PC to sleep and wake up, OR run Developer: Reload Window
4. Open the same session from the dropdown menu
5. Result: Only ~1 message exchange is visible; cannot scroll up to see earlier conversation

Expected Behavior

After reconnection, the full conversation history should be visible and scrollable in the UI.

Actual Behavior

• Only the most recent exchange is displayed
• Cannot scroll back to see previous messages
• This happens even within the same session

Evidence

The session files contain the full history (verified via CLI):

# Session file has 50 user messages
$ grep -c '"type":"user"' ~/.claude/projects/-home-midor-wtrn-dev/3ab56475-b9f4-44fa-96b4-e352f3d17b06.jsonl
50

# File size shows substantial content
$ ls -la ~/.claude/projects/-home-midor-wtrn-dev/3ab56475-b9f4-44fa-96b4-e352f3d17b06.jsonl
-rw------- 1 midor midor 1906042 Jan 22 16:45 ...

Workaround

Using CLI with claude --resume or claude --continue preserves full history access.

Additional Context

• The conversation data is fully persisted to disk (.jsonl files)
• The issue appears to be in the VSCode extension's UI layer not loading full history after reconnection
• sessions-index.json correctly tracks the sessions