verus-pm 0.2.16 → 0.3.2

package/bin/verus.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 
 const { existsSync } = require("node:fs");
-const { spawnSync } = require("node:child_process");
+const { spawn } = require("node:child_process");
 const { join } = require("node:path");
 
 const PLATFORM_NAMES = { darwin: "darwin", linux: "linux", win32: "windows" };
@@ -27,11 +27,30 @@ if (!binaryPath) {
   process.exit(1);
 }
 
-const result = spawnSync(binaryPath, process.argv.slice(2), { stdio: "inherit" });
-
-if (result.error) {
-  console.error(`Failed to launch Verus: ${result.error.message}`);
-  process.exit(1);
+// Use async spawn to properly forward signals and keep the child process
+// attached to this session. spawnSync doesn't forward signals correctly,
+// causing the child to become orphaned when the terminal closes.
+const child = spawn(binaryPath, process.argv.slice(2), {
+  stdio: "inherit",
+});
+
+// Forward signals to child process so Ctrl+C and terminal close work correctly
+for (const sig of ["SIGINT", "SIGTERM", "SIGHUP"]) {
+  process.on(sig, () => {
+    child.kill(sig);
+  });
 }
 
-process.exit(result.status ?? 1);
+child.on("error", (err) => {
+  console.error(`Failed to launch Verus: ${err.message}`);
+  process.exit(1);
+});
+
+child.on("exit", (code, signal) => {
+  if (signal) {
+    // Re-raise the signal so the parent shell sees the correct exit reason
+    process.kill(process.pid, signal);
+  } else {
+    process.exit(code ?? 1);
+  }
+});

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "verus-pm",
-  "version": "0.2.16",
+  "version": "0.3.2",
   "description": "AI-powered project management — CLI + Web Dashboard in one command",
   "bin": {
     "verus": "./bin/verus.js",