@rubytech/create-maxy-lite 0.1.16 → 0.1.17

package/lib/paths.mjs

@@ -185,11 +185,13 @@ export function launcherScript({
 } = {}) {
   // Kill any prior relay before starting so `maxy-lite` always runs the freshly
   // installed server.mjs, never a stale process still holding the port (which made
-  // a new build appear to "have no effect"). The relay writes its pid to
-  // <vault>/.maxy-lite/relay.pid; kill via the bash builtin (no external tools),
-  // and a best-effort pkill catches a relay started before pid-file support. The
-  // relay's own EADDRINUSE handler makes any remaining conflict loud.
-  const killPrior = `P=$(cat ${vaultGuest}/.maxy-lite/relay.pid 2>/dev/null); [ -n "$P" ] && kill "$P" 2>/dev/null; pkill -f "node server.mjs" 2>/dev/null; sleep 1`
+  // a new build appear to "have no effect"). Kill ONLY the pid the relay recorded in
+  // <vault>/.maxy-lite/relay.pid, via the bash builtin (no external tools). A broad
+  // `pkill -f "node server.mjs"` is NOT used: pkill -f matches the full command line,
+  // and this launcher's own `bash -lc '… exec node server.mjs'` contains that string,
+  // so it would SIGTERM its own session (proot vpid 1). A stale relay with no pid file
+  // is caught loudly by the relay's own EADDRINUSE handler instead.
+  const killPrior = `P=$(cat ${vaultGuest}/.maxy-lite/relay.pid 2>/dev/null); [ -n "$P" ] && kill "$P" 2>/dev/null; sleep 1`
   const inner = `${killPrior}; cd ${webchatDir} && ${webchatRunEnv({ vaultGuest, port })} exec node server.mjs`
   return `#!${prefix}/bin/bash
 # maxy-lite launcher — starts the on-device web chat relay.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy-lite",
-  "version": "0.1.16",
+  "version": "0.1.17",
   "description": "Install maxy-lite on an Android phone: orchestrates proot-distro Ubuntu, glibc Node, claude, the web-chat relay, the vault and its bind-mount — run via npx in bare Termux.",
   "type": "module",
   "engines": {