Session rename reverts after switching sessions (requires Window reload to persist)

Description

When renaming a session in the VS Code extension's session list, the new name reverts to the original ("Start new coding session") as soon as a different session is selected. The rename only takes effect after a full VS Code Window reload.

This also explains why all recent sessions appear as "Start new coding session" — titles are not reflected in the UI until a reload occurs.

Steps to Reproduce

1. Open the Claude Code sidebar in VS Code
2. Rename a session (double-click or right-click the session name)
3. Enter a new name and confirm
4. Click on a different session
5. Return to the renamed session — the name has reverted

Expected Behavior

The renamed session retains the new name without requiring a Window reload.

Actual Behavior

The name reverts after switching sessions. After "Developer: Reload Window", the correct name is displayed.

Environment

• Extension: anthropic.claude-code 2.1.141
• OS: Windows 11 Pro (Build 26200)
• Shell: PowerShell 5.1

Notes

The rename appears to be persisted to disk successfully (the name survives a reload), so this is likely a UI state issue — the session list does not re-render after a rename operation.