peaks-loop-internal-runtime 0.0.32 → 0.0.33

package/dist/index.d.ts

@@ -1,4 +1,4 @@
-export declare const RUNTIME_VERSION = "4.0.47";
+export declare const RUNTIME_VERSION = "4.0.48";
 export declare const RUNTIME_NPM_VERSION = "0.0.21";
 export { ClaudeAdapter } from './vendor/claude-adapter.js';
 export { CodexAdapter } from './vendor/codex-adapter.js';

package/dist/index.js

@@ -1,7 +1,7 @@
 // API contract: RUNTIME_VERSION tracks peaks-loop root version (4.0.x).
 // This is what consumers (sub-agents dispatched by peaks-code) check at
 // runtime to verify protocol compatibility.
-export const RUNTIME_VERSION = '4.0.47';
+export const RUNTIME_VERSION = '4.0.48';
 // npm version: independent 0.0.x SemVer. Runtime is its own package
 // (peaks-loop-internal-runtime@NPM_VERSION) on the registry; bumps
 // per peaks release notes when its public surface actually changes

package/dist/process-supervisor.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"process-supervisor.d.ts","sourceRoot":"","sources":["../src/process-supervisor.ts"],"names":[],"mappings":"AAAA,OAAO,EAAsB,YAAY,EAAqB,MAAM,oBAAoB,CAAC;AAIzF,MAAM,WAAW,SAAS;IACxB;;;;;;;;OAQG;IACH,MAAM,EAAE,OAAO,CAAC;IAChB,GAAG,EAAE,MAAM,CAAC;IACZ,KAAK,CAAC,EAAE,MAAM,GAAG,QAAQ,CAAC;CAC3B;AACD,MAAM,WAAW,WAAW;IAC1B,GAAG,EAAE,MAAM,CAAC;IACZ,KAAK,EAAE,YAAY,CAAC;IACpB,IAAI,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC,OAAO,GAAG,IAAI,CAAC;IACpC;;;;;;;OAOG;IACH,OAAO,EAAE,OAAO,CAAC,MAAM,CAAC,cAAc,GAAG,IAAI,CAAC,CAAC;CAChD;AAED,qBAAa,iBAAiB;IAChB,OAAO,CAAC,QAAQ,CAAC,GAAG;gBAAH,GAAG,EAAE;QAAE,UAAU,EAAE,MAAM,CAAA;KAAE;IAElD,KAAK,CAAC,MAAM,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,IAAI,EAAE,SAAS,GAAG,OAAO,CAAC,WAAW,CAAC;CAmDnF"}
+{"version":3,"file":"process-supervisor.d.ts","sourceRoot":"","sources":["../src/process-supervisor.ts"],"names":[],"mappings":"AAAA,OAAO,EAAsB,YAAY,EAAqB,MAAM,oBAAoB,CAAC;AAIzF,MAAM,WAAW,SAAS;IACxB;;;;;;;;OAQG;IACH,MAAM,EAAE,OAAO,CAAC;IAChB,GAAG,EAAE,MAAM,CAAC;IACZ,KAAK,CAAC,EAAE,MAAM,GAAG,QAAQ,CAAC;CAC3B;AACD,MAAM,WAAW,WAAW;IAC1B,GAAG,EAAE,MAAM,CAAC;IACZ,KAAK,EAAE,YAAY,CAAC;IACpB,IAAI,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC,OAAO,GAAG,IAAI,CAAC;IACpC;;;;;;;OAOG;IACH,OAAO,EAAE,OAAO,CAAC,MAAM,CAAC,cAAc,GAAG,IAAI,CAAC,CAAC;CAChD;AAED,qBAAa,iBAAiB;IAChB,OAAO,CAAC,QAAQ,CAAC,GAAG;gBAAH,GAAG,EAAE;QAAE,UAAU,EAAE,MAAM,CAAA;KAAE;IAElD,KAAK,CAAC,MAAM,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,EAAE,EAAE,IAAI,EAAE,SAAS,GAAG,OAAO,CAAC,WAAW,CAAC;CAiEnF"}

package/dist/process-supervisor.js

@@ -45,7 +45,21 @@ export class ProcessSupervisor {
         });
         const dir = join(this.cfg.runtimeDir, opts.rid);
         mkdirSync(dir, { recursive: true });
-        writeFileSync(join(dir, 'pid'), String(child.pid ?? ''));
+        // `<rid>/pid` exists IFF a real OS process was launched. `child.pid` is
+        // `undefined` until the OS confirms the spawn, so a failed launch used to
+        // write `String(undefined ?? '')` — an EMPTY pid file. That is not a
+        // cosmetic wart: `Number('')` is `0`, so a cleanup path doing
+        // `kill(Number(readFileSync(pid)))` would send its signal to pid 0 (the
+        // whole process group), and an existence check for "is something running
+        // here" reads `true` for a launch that never happened.
+        //
+        // Nothing is lost by omitting it: the launch failure is recorded as a
+        // VALUE on the dispatch record (`status: 'failed'` + `spawnError`), which
+        // is the surface a reader should consult. Absence in the pid file is the
+        // one encoding that cannot be misread as a pid.
+        if (child.pid !== undefined) {
+            writeFileSync(join(dir, 'pid'), String(child.pid));
+        }
         return {
             pid: child.pid ?? -1,
             child,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "peaks-loop-internal-runtime",
-  "version": "0.0.32",
+  "version": "0.0.33",
   "description": "Detached sub-agent runtime: ProcessSupervisor + LifecycleOwner + VendorAdapter (claude/codex/copilot) + G8 infinite-context auto-compact. Slice 2026-08-10.",
   "repository": {
     "type": "git",
@@ -16,7 +16,7 @@
     "access": "public"
   },
   "peerDependencies": {
-    "peaks-loop-shared": "0.0.81"
+    "peaks-loop-shared": "0.0.82"
   },
   "devDependencies": {
     "typescript": "^5.4.0",

package/src/index.ts

@@ -1,7 +1,7 @@
 // API contract: RUNTIME_VERSION tracks peaks-loop root version (4.0.x).
 // This is what consumers (sub-agents dispatched by peaks-code) check at
 // runtime to verify protocol compatibility.
-export const RUNTIME_VERSION = '4.0.47';
+export const RUNTIME_VERSION = '4.0.48';
 
 // npm version: independent 0.0.x SemVer. Runtime is its own package
 // (peaks-loop-internal-runtime@NPM_VERSION) on the registry; bumps

package/src/process-supervisor.ts

@@ -76,7 +76,21 @@ export class ProcessSupervisor {
 
     const dir = join(this.cfg.runtimeDir, opts.rid);
     mkdirSync(dir, { recursive: true });
-    writeFileSync(join(dir, 'pid'), String(child.pid ?? ''));
+    // `<rid>/pid` exists IFF a real OS process was launched. `child.pid` is
+    // `undefined` until the OS confirms the spawn, so a failed launch used to
+    // write `String(undefined ?? '')` — an EMPTY pid file. That is not a
+    // cosmetic wart: `Number('')` is `0`, so a cleanup path doing
+    // `kill(Number(readFileSync(pid)))` would send its signal to pid 0 (the
+    // whole process group), and an existence check for "is something running
+    // here" reads `true` for a launch that never happened.
+    //
+    // Nothing is lost by omitting it: the launch failure is recorded as a
+    // VALUE on the dispatch record (`status: 'failed'` + `spawnError`), which
+    // is the surface a reader should consult. Absence in the pid file is the
+    // one encoding that cannot be misread as a pid.
+    if (child.pid !== undefined) {
+      writeFileSync(join(dir, 'pid'), String(child.pid));
+    }
 
     return {
       pid: child.pid ?? -1,