VS Code extension fails to load project when directory name ends with "--"

Description

The VS Code extension cannot load past conversations / project data when the generated project directory name ends with --.

Steps to reproduce

1. Open VS Code on a drive root like Q:\ (e.g. a Samba network share mapped to a drive letter)
2. Claude Code generates the project directory ~/.claude/projects/q-- (the : and \ are replaced by -, resulting in q--)
3. The VS Code extension fails to load this project (past conversations panel doesn't work)

The same issue occurs with UNC paths like \\192.168.8.2\config which generates --192.168.8.2-config (starts with --).

Context

• All other projects with longer names (e.g. c--Users-frevi-Desktop-..., Q--custom-components-multicraft) work fine
• The issue seems specific to directory names that are very short and end/start with --, which may be interpreted as end-of-options markers in CLI argument parsing
• Windows symlinks/junctions to network shares are not a viable workaround (Windows does not support junctions to UNC paths, and symlinks to UNC paths don't resolve correctly)

Expected behavior

The extension should handle project directory names containing -- without issues, regardless of position in the name.

Environment

• OS: Windows 11 Pro
• Claude Code VS Code extension
• Working directory: Q:\ (Samba share from Home Assistant OS mapped as network drive)