[Windows] Project working directory check fails on UNC/Network paths. #125
Description
I'm unlucky enough to have to work on projects that are windows only.
I run claude/happy inside of a Windows VM to contain damage caused by AI going rogue in yolo mode.
I expose projects I work on over SMB/Network sharing from my host machine, and mount them in the VM under a drive letter (Z:\ etc), however the mount is effectively pointing at \MyPc\project.
I run claude/happy inside Z:\ as a lot of tools fall over when working under UNC paths.
Trying to view diffs in the mobile app, I always get an error saying that the file is not under the projects working directory, as happy must be doing path resolution, which turns Z:\foo into \MyPc\project\foo and fails the check.
It should probably do project working directory resolution and accept both as valid variants, or do some sort os "IsSame" checks on the file handles.