[vitaliyslion]

Summary

With gortex installed as a .cmd or .bat shim on Windows (npm's global install), the hook bridge never ran. Node refuses to spawn batch files directly (EINVAL), and callHook swallowed the error. Pi's MCP spawns through cross-spawn, so the graph tools connected and the session looked healthy, but there was no briefing, no read discipline and no version check, and nothing reported it.

• src/runtime.ts: when a command resolves to a .cmd or .bat on Windows, the process seam runs it through cmd.exe with cross-spawn's escaping. The command is passed as written, so cmd.exe searches PATH the same way it does for Pi's MCP.
• Resolution on Windows follows cross-spawn too: PATHEXT extensions, and the bare name only when it already carries one. Before, the extensionless sh script npm puts beside gortex.cmd matched first, and Windows cannot spawn it. binaryResolves now uses this shared resolver.

Reproduction

Reproduced end to end under Windows Node 24 running in Wine in a Podman container. The extension ran under Pi's runner with its real process seam, and gortex was installed with npm's .cmd shim template and the sh script beside it, in a directory with spaces and parentheses.

	before	after
binaryResolves("gortex")	true	true
MCP tools connect (cross-spawn)	yes	yes
Briefing on first turn	no	yes
Pi read blocked by the hook	no	yes
Hook calls reaching gortex	none	session_start, tool_call Read

Closes #37

Testing

• npm run check passes
• New behaviour has a suite that drives it through Pi's ExtensionRunner (see docs/tests.md): test/runtime.test.ts tests the process seam directly, since the hook double replaces exactly this seam in the runner suites. The Wine repro above covered the runner path.
• Tried by hand in Pi (pi -e /path/to/checkout), if user-visible: not on a real Windows machine.

test/runtime.test.ts tests resolution and escaping as pure functions on every OS, and spawns real batch files on Windows only. Under Wine, the test that runs a .bat by a path with spaces fails. cross-spawn fails on the same path under Wine too, and the test passes on the windows-latest CI job, so the failure was Wine's cmd.exe.

Checklist

• No runtime dependencies added
• README configuration table updated, if config changed (no config change)
• docs/architecture.md updated briefly, only if a design decision changed (no design decision changed)
• Works on Windows paths and process spawning, if touching either: Wine repro, and the batch file spawn tests pass on windows-latest