The subfolder resolution tests were hitting real GitHub APIs and git ls-remote, causing flaky failures when HTTP HEAD checks returned non-ok responses (rate limiting, network issues), which made the resolver take the private repo path instead of the tarball path.