[Bug] CLI and desktop app generate different project memory paths for directories with spaces

Bug Description
Bug: CLI and desktop app encode the same working directory into different project memory paths

Working directory: M:\Dropbox\Development\Claude Code\_wp-plugins\Image Uploader

Encoded path from CLI: M--Dropbox-Development-Claude Code--wp-plugins-Image-Uploader

Encoded path from desktop app: M--Dropbox-Development-Claude-Code--wp-plugins-Image-Uploader

Steps to reproduce:

Open a working directory containing a space (e.g. Claude Code) in the CLI
Save a memory — it writes to ~/.claude/projects/M--Dropbox-Development-Claude Code--wp-plugins-Image-Uploader/memory/
Open the same working directory in the desktop app
Auto memory creates a separate directory at ~/.claude/projects/M--Dropbox-Development-Claude-Code--wp-plugins-Image-Uploader/memory/
Memories from the CLI session are not available in the desktop app and vice versa
Expected behavior: Both clients should produce the same encoded path for the same working directory.

Platform: Windows 10 Pro Education 10.0.19045

Environment Info

• Platform: win32
• Terminal: null
• Version: 2.1.89
• Feedback ID: 87f2895e-fb42-431f-b94c-973d0d062a01

Errors

[]