Summary
Using /c/Projects/... MSYS paths on Windows git-bash produces Error: Cannot find module 'C:\c\Projects\...' (doubled drive letter). Users must use native Windows paths with proper quoting.
Verification
Tested on main HEAD c3e58e9 (v2.0.0). Shell: MSYS/git-bash on Windows 10.
# BROKEN — MSYS path
$ node /c/Projects/agent-harness/dist/cli.js --version
Error: Cannot find module 'C:\c\Projects\agent-harness\dist\cli.js'
# WORKS — native Windows path
$ node "C:\Projects\agent-harness\dist\cli.js" --version
2.0.0
Root Cause
MSYS/bash auto-converts /c/... to C:/... but Node's module resolver sometimes re-applies the drive letter prefix, producing C:\c\....
Impact
- README examples using
/c/... paths won't work on the most common Windows shell
- First-run experience broken for Windows git-bash users
- README quick start "from source" instructions unreliable
Acceptance Criteria
Priority / Effort
Priority: P2 Effort: S
Summary
Using
/c/Projects/...MSYS paths on Windows git-bash producesError: Cannot find module 'C:\c\Projects\...'(doubled drive letter). Users must use native Windows paths with proper quoting.Verification
Tested on
mainHEADc3e58e9(v2.0.0). Shell: MSYS/git-bash on Windows 10.Root Cause
MSYS/bash auto-converts
/c/...toC:/...but Node's module resolver sometimes re-applies the drive letter prefix, producingC:\c\....Impact
/c/...paths won't work on the most common Windows shellAcceptance Criteria
Priority / Effort
Priority: P2 Effort: S