fix(gold-traces): quote record-command arguments for cmd.exe on Windows

[kgilpin]

Fixes #7.

shellQuote quoted arguments with single quotes, which cmd.exe does not understand. On Windows a test name with spaces split into several arguments, and a jest, vitest, mocha, minitest or rails-test run with two or more tests put a | in the name filter, which cmd.exe read as a pipe.

How it quotes now on Windows

cmd.exe gets the whole command line as one string, and the program splits it itself using C runtime rules (double quotes group, \" is a literal quote). So the argument is wrapped in double quotes for the program, and every character cmd.exe acts on, the quotes included, is escaped with ^. cmd.exe then never enters quote mode and hands the string over untouched. This is the scheme cross-spawn uses.

Argument	POSIX	Windows
tests/test_a.py::test_x	as is	as is
creates an order	'creates an order'	^"creates an order^"
(adds|removes)	'(adds|removes)'	^"^(adds^|removes^)^"
100%	as is	^"100^%^" (a bare % can name a variable to cmd.exe)

Nothing changes on macOS or Linux. shellQuote takes a platform (default process.platform), and buildCommand passes it through, so the Windows cases are tested on any machine.

Evidence

One test writes a Node script that prints its argv, runs it through the real shell with every kind of argument (spaces, a regex union, escaped parentheses, quotes, & < > ^, %, a trailing backslash), and checks that each one arrives as written. On the Windows runner that shell is cmd.exe.

🤖 Generated with Claude Code