Windows: detected launchers (venv, mvnw, gradlew, bin/rails) do not run in cmd.exe #8

Found by reading the code while reviewing #5. Not yet reproduced on a Windows machine.

Problem

When commands.runner is unset, frameworks.mjs picks a launcher for the project. Three of the choices do not run on Windows, where the record command goes through cmd.exe (runShell in manage.mjs uses shell: true, which is %ComSpec%).

Note on the wrappers: cmd.exe does add the PATHEXT suffixes when it looks up a command, and searches the current directory first. So mvnw test alone finds mvnw.cmd, and gradlew appmap test finds gradlew.bat. The ./ prefix is the only problem. (This works in PowerShell and Git Bash, but the engine runs cmd.exe.)

Suggested fix

Give resolveRunner and the detectRunner functions a platform parameter (default process.platform), the way detectMaxCommandLength already takes one.

On win32:

• venvBin also checks for appmap-python.exe, and pythonLauncher returns .venv\Scripts\appmap-python .venv\Scripts\pytest.
• maven returns mvnw test when mvnw.cmd exists (no ./).
• gradle returns gradlew appmap test when gradlew.bat exists (no ./).
• rails-test defaults to ruby bin/rails test.

Also update the runner: example in appmap-gold-traces/SKILL.md (it shows .venv/bin/appmap-python pytest) to mention the Windows form.

Test cases needed

Unit tests in frameworks.test.mjs, next to the existing detect: tests, passing platform: 'win32' so they run on any machine. Each one builds a temp directory with the marker files:

• A dir holding .venv/Scripts/appmap-python.exe gives .venv\Scripts\appmap-python .venv\Scripts\pytest.
• The same for venv/ and for unittest (... python -m unittest).
• A dir holding both mvnw and mvnw.cmd gives mvnw test on win32 and ./mvnw test elsewhere.
• The same for gradlew and gradlew.bat.
• A dir holding only mvnw (no .cmd) falls back to mvn test on win32.
• rails-test gives ruby bin/rails test on win32 and bin/rails test elsewhere.
• An explicit commands.runner is still never overridden on win32.
• uv, Poetry and Pipenv detection is unchanged on win32.

One test that runs on the real shell, to settle the cmd.exe behaviour with evidence (CI runs the tests on Windows now, #11): make a temp dir with a mvnw.cmd that exits 0, run mvnw test and ./mvnw test through spawnSync(command, { shell: true }), and assert that the first starts and the second does not. On macOS and Linux the same test can use a mvnw script and assert that ./mvnw test starts.