@rubytech/create-maxy-lite 0.1.7 → 0.1.9

package/index.mjs

@@ -136,9 +136,27 @@ const installDeps = async () => {
   // built artifact directly to recover the actual dlopen error, and carry THAT into
   // err= — the true reason (ABI/NODE_MODULE_VERSION/symbol/ELF), not the swallowed miss.
   if (runIn(ptyLoadCommand()).code !== 0) {
+    // proot emits `can't sanitize binding /proc/self/fd/*` lines on every
+    // non-interactive login; they are noise that buries the real error. Strip them.
+    const clean = (s) =>
+      String(s || '')
+        .split('\n')
+        .filter((l) => !/proot warning: can't sanitize binding/.test(l))
+        .join(' ')
+        .replace(/\s+/g, ' ')
+        .trim()
     const direct = runIn(ptyDirectLoadCommand())
-    const cause = direct.stderr.replace(/\s+/g, ' ').trim() || `no stderr; ${PTY_NODE}`
-    throw new Error(`node-pty native module did not load after build: ${cause}`)
+    const cause = clean(direct.stderr) || `no stderr; ${PTY_NODE}`
+    // The load error is a libc-link failure (`libc.so: cannot open shared object
+    // file`). Capture which libraries pty.node actually needs (ldd) and any leaked
+    // Termux linker env (LD_*/LIBRARY_PATH) so the next run names the exact cause
+    // and we fix from certainty, not a guess.
+    const diag = runIn(
+      `ldd ${PTY_NODE} 2>&1; echo '|env:'; env | grep -iE 'LD_PRELOAD|LD_LIBRARY_PATH|LIBRARY_PATH' || echo '(no LD_* env)'`,
+    )
+    throw new Error(
+      `node-pty native module did not load after build: ${cause} || ldd+env: ${clean(diag.stdout + ' ' + diag.stderr)}`,
+    )
   }
 }
 

package/lib/paths.mjs

@@ -66,12 +66,15 @@ export function ptyDirectLoadCommand({ ptyNode = PTY_NODE } = {}) {
  * was the divergence from Q2. The toolchain step guarantees python3/make/g++.
  */
 export function webchatInstallCommand({ webchatDir = WEBCHAT_DIR } = {}) {
-  // Reproduce the spike's exact working command (`npm install node-pty` in the
-  // Ubuntu layer, scripts on) verbatim — that built a loadable pty.node. `npm
-  // install node-pty` also resolves the rest of package.json (ws), so it covers
-  // the webchat's deps too. The env prefix forces scripts on to match the spike's
-  // environment regardless of any ambient ignore-scripts in the Ubuntu image.
-  return `cd ${webchatDir} && npm_config_ignore_scripts=false npm install node-pty`
+  // Reproduce the spike's working condition VERBATIM, including its freshness: the
+  // spike ran `npm install node-pty` in an EMPTY dir (`mkdir ~/pty`), which forced a
+  // real source build of pty.node that loaded. On a re-installed device the webchat
+  // node_modules already holds a prior (broken) pty.node, so a plain `npm install`
+  // reports "up to date" and rebuilds nothing — leaving the bad binary. So clean
+  // node_modules first, then install: that recreates the spike's empty-dir build.
+  // `npm install node-pty` also resolves package.json (ws). The env prefix forces
+  // scripts on to match the spike's environment regardless of ambient ignore-scripts.
+  return `cd ${webchatDir} && rm -rf node_modules package-lock.json && npm_config_ignore_scripts=false npm install node-pty`
 }
 
 // The shipped skills, as bundled into the app dir, and the path the on-device

package/package.json

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