@rubytech/create-maxy-lite 0.1.14 → 0.1.15

package/lib/paths.mjs

@@ -183,7 +183,14 @@ export function launcherScript({
   port = PATHS.webchatPort,
   distro = PATHS.distro,
 } = {}) {
-  const inner = `cd ${webchatDir} && ${webchatRunEnv({ vaultGuest, port })} exec node server.mjs`
+  // 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`
+  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.
 # Enters the glibc Ubuntu layer with the shared-storage vault bound in, then runs

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy-lite",
-  "version": "0.1.14",
+  "version": "0.1.15",
   "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": {

package/payload/webchat/server.mjs

@@ -34,6 +34,7 @@ const CLAUDE_BIN = process.env.LITE_CLAUDE_BIN || 'claude'
 const PROJECTS_DIR = path.join(os.homedir(), '.claude', 'projects')
 const STATE_DIR = process.env.LITE_STATE_DIR || path.join(AGENT_HOME, '.maxy-lite')
 const SESSION_FILE = path.join(STATE_DIR, 'session-id')
+const PID_FILE = path.join(STATE_DIR, 'relay.pid') // so the launcher can kill a prior relay before starting a fresh one
 const TAIL_MS = 250 // JSONL poll interval
 const QUIET_MS = 1500 // silence that ends a turn for op=done
 const NO_REPLY_MS = 8000 // a turn with NO transcript growth this long = swallowed; surface why
@@ -261,6 +262,22 @@ wss.on('connection', (ws) => {
   })
 })
 
+// A stale relay still holding the port is the usual cause of "new build installed
+// but old code serving". Make it loud instead of a silent stale-serve.
+server.on('error', (e) => {
+  log('listen-error', { code: e.code, port: PORT })
+  process.exit(1)
+})
 server.listen(PORT, '127.0.0.1', () => {
+  // Record our pid so the next launch can kill this relay and take over cleanly,
+  // and emit a build marker: op=relay-start proves THIS server.mjs (not a stale
+  // one) is the live process.
+  try {
+    fs.mkdirSync(STATE_DIR, { recursive: true })
+    fs.writeFileSync(PID_FILE, String(process.pid))
+  } catch {
+    /* pid file is best-effort */
+  }
+  log('relay-start', { pid: process.pid, port: PORT })
   log('listening', { port: PORT, sessionId, home: AGENT_HOME })
 })