4fbb61c915
* fix(#372): use non-login shell in bug-3668 resolver test for hermetic PATH bash -lc re-sourced profile files (e.g. Homebrew shellenv) that prepended real bin dirs ahead of the test's injected PATH, so the installed-gsd-tools fallback subtest resolved a host-global gsd-tools instead of the injected fake — failing on dev machines and CI-adjacent benches while passing on clean CI. Use bash -c (non-login) so the injected PATH is authoritative. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(#372): split workflow snippet on CRLF in bug-3668 resolver test extractResolverSnippet split on '\n' and exact-matched the closing \`fi\` line, so on a Windows checkout (CRLF) the line was \`fi\r\`, the end marker was never found, and the test failed with "SDK resolution snippet must end with fi". Split on /\r?\n/ so extraction works on LF and CRLF checkouts and the snippet handed to bash is carriage-return-free. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(#372): assert resolver bin by normalized suffix, not exact OS path On Windows the snippet runs under Git bash, so GSD_TOOLS is reported POSIX- style / mixed-separator while the test built its expected regex from Node path.join (backslashes) — the resolver was correct (installed:/runtime: output proves the right bin ran) but the exact-path assertions failed. Normalize separators and assert the GSD_TOOLS path suffix, keeping the behavioral installed:/runtime: assertions as the primary checks. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3.8 KiB
3.8 KiB