The win32-x64 engine player crashes at startup (0xC0000409), even with --check-game #614

What happens

The Windows engine player that @threenative/runtime-native@0.3.11 installs (win32-x64-engine-player) exits at once with 0xC0000409 (fail-fast or abort). It prints nothing, even with --check-game, which needs no GPU.

> Start-Process .\player.exe -ArgumentList 'game.js','--check-game' -Wait -PassThru
exit=0xC0000409 (-1073740791)      # stdout and stderr empty

The same game (threenative-store/examples/fox-native) boots on Linux.

Evidence

• Store probe run on windows-latest: https://github.com/ThreeNativeHQ/threenative-store/actions/runs/41962301020. threenative build --target desktop --mode release passes (with the Windows: threenative build --target desktop reports core's own loaders as unbound game imports #612 fix, PR Desktop builds work on Windows: the native bundler handles backslash and drive-letter paths #613), then the boot step fails.
• The packaged player is a real PE (MZ). It imports only system DLLs (KERNEL32, USER32, GDI32, ole32, dbghelp, bcryptprimitives, ...).
• Git Bash shows exit 127 with no message for the same call.

Two packaging gaps on Windows (same run)

1. dist-native/<name>/tn-native-engine-player-v8 has no .exe suffix.
2. dist-native/<name>/<name> is a POSIX #!/bin/sh launcher, which Windows cannot run. A .cmd or an .exe launcher is needed.

Coverage gap

native-platforms.yml runs the --check-game starter boot on linux-x64 only. native-release.yml builds tn-native-engine-player-v8.exe but does not boot it. A Windows --check-game boot in the release job would have caught this.