[Bug] Session resume picker invisible for projects on mapped network drives

Bug Description
Sessions started on mapped network drives are invisible to the resume picker.
Setup: Windows Server 2025, project on a mapped NAS drive (V:\). Sessions save correctly to ~/.claude/projects/v/*.jsonl, but claude --resume (picker) and the VS Code extension's Session history both show nothing for the project; resume works only by explicit session ID.
Root cause found: the picker is driven by the ~/.claude/history.jsonl index, not by scanning project folders — and prompts from sessions run on the mapped-drive path were not being appended to that index. Manually repairing the index (adding display/project/sessionId lines) instantly made the sessions appear.
Impact: anyone working from a mapped/remote drive loses session resume via picker. Cost me ~2 hours of diagnosis (including chasing a false path-encoding theory).
Suggested fix: ensure history.jsonl indexing fires for sessions with remote/mapped cwd, or fall back to scanning project-folder .jsonl files when the index has no entries for an existing project folder.

Environment Info

• Platform: win32
• Terminal: vscode
• Version: 2.1.201
• Feedback ID: b1561a40-50c5-4741-b506-8954eb2263a5

Errors

[]