05821d4e62
On Windows the launcher links another launcher's client jar with a hard link (a copy across volumes) and its libraries and assets with a junction, since symlinks need developer mode. canonicalize() of a hard link is its own path, so the sources tests, which compared canonical paths, failed on Windows and blocked every launcher release since launcher-v0.4.0. They now check that the linked jar is the launcher's file (a byte written through one shows in the other), which holds for a symlink and a hard link alike. The modpack profile test compares paths as paths rather than strings ending in "a/carry". mklink /J's paths are always quoted: Rust only quotes arguments with spaces, and cmd reads an unquoted & or ^ in a user folder as its own syntax. CI runs every launcher test target, not just the library's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>