runcastle 1.4.3 → 1.4.4

package/bin/runcastle.js

@@ -1617,7 +1617,7 @@ function createSidecarPtySession(cmd, args, opts) {
       }
       switch (msg.t) {
         case "ready":
-          if (typeof msg.pid === "number")
+          if (typeof msg.pid === "number" && msg.pid > 0)
             pid = msg.pid;
           break;
         case "data":

package/index.js

@@ -1616,7 +1616,7 @@ function createSidecarPtySession(cmd, args, opts) {
       }
       switch (msg.t) {
         case "ready":
-          if (typeof msg.pid === "number")
+          if (typeof msg.pid === "number" && msg.pid > 0)
             pid = msg.pid;
           break;
         case "data":

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "runcastle",
-  "version": "1.4.3",
+  "version": "1.4.4",
   "description": "Burn tickets into shipped features with Claude Code.",
   "license": "FSL-1.1-ALv2",
   "type": "module",
@@ -38,7 +38,7 @@
     "drizzle-orm": "0.45.2",
     "hono": "4.12.30",
     "nanoid": "6.0.0",
-    "node-pty": "^1.1.0",
+    "node-pty": "1.2.0-beta.15",
     "simple-git": "^3.36.0",
     "zod": "4.4.3"
   }

package/pty-host.cjs

@@ -102,7 +102,15 @@ function handleSpawn(msg) {
 
   send({ t: 'ready', pid: proc.pid })
 
+  // node-pty 1.2 on win32 starts the ConPTY child only once its output worker has
+  // connected, so `proc.pid` is still 0 above. It is set before the first output
+  // arrives, so re-announce it then.
+  let pidAnnounced = proc.pid > 0
   proc.onData((d) => {
+    if (!pidAnnounced && proc.pid > 0) {
+      pidAnnounced = true
+      send({ t: 'ready', pid: proc.pid })
+    }
     const buf = typeof d === 'string' ? Buffer.from(d, 'utf8') : d
     send({ t: 'data', d: buf.toString('base64') })
   })