Three @neuledge/registry tests fail on Windows, blocking windows-latest in CI #153

We can't currently add windows-latest to the CI test matrix because three pre-existing @neuledge/registry failures abort the run before anything else executes. This came up in #147, where Windows was added, failed, and then removed again — so the rename/replacement path that PR is entirely about still has no Windows coverage.

From run 289 on that PR's branch, the failures were:

• definition.test.ts — ENOENT on @apollo\client.yaml
• two publish-all summary assertions

None of them relate to #147's change; they're all in the registry package and look platform-path-related. Worth noting #136 fixed a scoped-name separator bug in loadDefinition that was in the same area, so the @apollo\client.yaml one may be a leftover of the same class — the test fixture creating a real file with a backslash in the name behaves differently on Windows than the byte-identical string #136's regression test uses on Linux.

Turbo aborts the whole run on the first package failure, which is why @neuledge/context never got to run its suite on Windows at all. So the cost of these three is the entire platform's coverage.

Two ways forward: fix them properly, or skip these three on Windows with a link back here so the rest of the matrix can start running. I'd rather fix them, but the skip is a reasonable interim step if it unblocks real coverage of the filesystem code, which is where we actually expect Windows to differ.