Path Normalization Fails for Forward Slashes on Windows Environment Variables

Bug Description
Path handling appears to be inconsistent on Windows environments. Windows should natively support forward slashes
(/) as path separators, but the CLAUDE_CODE_GIT_BASH_PATH environment variable only works correctly with
backslashes (\). While I haven't confirmed if this issue affects other environment variables, I suspect it may be
related to the frequent malfunctioning of the lsmcp MCP server on Windows environments.

Steps to Reproduce

1. Set CLAUDE_CODE_GIT_BASH_PATH with forward slashes on Windows
2. Observe that the path is not recognized correctly
3. Change to backslashes - functionality works as expected

Expected Behavior
Windows should accept both forward slashes and backslashes for path separators, as this is standard Windows
behavior.

Actual Behavior
Only backslashes work for CLAUDE_CODE_GIT_BASH_PATH, suggesting inconsistent path normalization.

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 1.0.81
• Feedback ID: 8e36f261-27ac-4761-8ed9-e25ebb1ddacf