Test actual CLI binary in e2e tests, not just the script

Author: pimterry

package.json

@@ -19,7 +19,7 @@
     "start:dev": "tsx ./build-setup/skip-server.ts && cross-env HTK_DEV=true APP_URL='http://localhost:8080' npm run start:app",
     "start:app": "tsc-watch --onSuccess \"electron .\"",
     "build:cli": "tsx ./build-setup/build-cli.ts",
-    "test": "npm run server:setup && npm run build:src && npm run test:unit && npm run test:smoke",
+    "test": "npm run server:setup && npm run build:src && npm run test:unit && npm run build:cli && npm run test:smoke",
     "test:unit": "node --experimental-strip-types --import ./test/register-stubs.js --test test/ui-bridge.spec.ts",
     "test:smoke": "playwright test"
   },

test/mcp-e2e.spec.ts

@@ -133,10 +133,10 @@ test('MCP server exposes UI operations as tools', async () => {
 
         // --- MCP protocol test via CLI ---
 
-        mcpProcess = spawn('node', [
-            path.join(import.meta.dirname, '..', 'build', 'cli', 'cli.cjs'),
-            'mcp'
-        ], {
+        const cliBinary = path.join(import.meta.dirname, '..',
+            'httptoolkit-cli' + (process.platform === 'win32' ? '.exe' : '')
+        );
+        mcpProcess = spawn(cliBinary, ['mcp'], {
             stdio: ['pipe', 'pipe', 'pipe']
         });