@mjasnikovs/pi-task 0.24.2 → 0.24.3

package/dist/shared/command-watchdog.d.ts

@@ -96,8 +96,14 @@ export declare class CommandWatchdog {
     private fire;
 }
 /**
- * Real-clock schedule/cancel, unref'd so a pending watchdog timer can never
- * itself keep the process alive on exit. Shared by both adapters; tests
- * substitute a fake scheduler instead.
+ * Real-clock schedule/cancel. Shared by both adapters; tests substitute a fake
+ * scheduler instead.
+ *
+ * REF'd, for the same measured reason as the stream watchdog's poll (see
+ * realStreamTimerDeps): under Bun on windows an unref'd timer never fires once
+ * nothing ref'd is pending, and a child sitting in a hung command is exactly
+ * that state — so the unref disabled the guard in the one case it exists for.
+ * The timer is cleared when the tool ends and in runWorker's `finally`, so it
+ * cannot outlive the call it watches.
  */
 export declare const realTimerDeps: Pick<WatchdogDeps, 'schedule' | 'cancel'>;

package/dist/shared/command-watchdog.js

@@ -141,18 +141,17 @@ export class CommandWatchdog {
     }
 }
 /**
- * Real-clock schedule/cancel, unref'd so a pending watchdog timer can never
- * itself keep the process alive on exit. Shared by both adapters; tests
- * substitute a fake scheduler instead.
+ * Real-clock schedule/cancel. Shared by both adapters; tests substitute a fake
+ * scheduler instead.
+ *
+ * REF'd, for the same measured reason as the stream watchdog's poll (see
+ * realStreamTimerDeps): under Bun on windows an unref'd timer never fires once
+ * nothing ref'd is pending, and a child sitting in a hung command is exactly
+ * that state — so the unref disabled the guard in the one case it exists for.
+ * The timer is cleared when the tool ends and in runWorker's `finally`, so it
+ * cannot outlive the call it watches.
  */
 export const realTimerDeps = {
-    schedule: (fn, ms) => {
-        const handle = setTimeout(fn, ms);
-        if (typeof handle.unref === 'function') {
-            ;
-            handle.unref();
-        }
-        return handle;
-    },
+    schedule: (fn, ms) => setTimeout(fn, ms),
     cancel: handle => clearTimeout(handle)
 };

package/dist/shared/stream-watchdog.d.ts

@@ -103,9 +103,23 @@ export declare class StreamWatchdog {
     check(): void;
 }
 /**
- * Real-clock poll deps, unref'd so a pending watchdog poll can never itself keep
- * the process alive on exit. `schedule` returns a repeating interval — the
- * machine cancels it on stop/fire.
+ * Real-clock poll deps. `schedule` returns a repeating interval — the machine
+ * cancels it on stop/fire, and runChild's cleanup() stops the watchdog on every
+ * settle path (close, error, abort), so it cannot outlive the child it watches.
+ *
+ * The poll is REF'd, deliberately. It used to be unref'd, on the reasoning that a
+ * pending watchdog poll should never keep the process alive at exit — but under
+ * Bun on WINDOWS an unref'd timer does not fire at all once nothing ref'd is
+ * pending. Measured on a windows-latest runner (bun 1.3.14): an unref'd interval
+ * with nothing else pending never fired in 20s, while the identical ref'd one
+ * fired at 101ms; on linux both fire at 100ms.
+ *
+ * That state — no ref'd work outstanding — is EXACTLY the state this watchdog
+ * exists to police: a child whose model stream has gone silent. So the unref
+ * disabled the guard precisely when it was needed, and every stream-stall
+ * integration test hung forever on windows (CI runs 30476786365, 30477802633,
+ * 30478455402 — it hangs at v0.24.1 too, so this predates that release).
+ * A poll that can delay exit by one interval is the cheaper failure.
  */
 export declare const realStreamTimerDeps: Pick<StreamWatchdogDeps, 'now' | 'schedule' | 'cancel'>;
 /**

package/dist/shared/stream-watchdog.js

@@ -148,20 +148,27 @@ export class StreamWatchdog {
     }
 }
 /**
- * Real-clock poll deps, unref'd so a pending watchdog poll can never itself keep
- * the process alive on exit. `schedule` returns a repeating interval — the
- * machine cancels it on stop/fire.
+ * Real-clock poll deps. `schedule` returns a repeating interval — the machine
+ * cancels it on stop/fire, and runChild's cleanup() stops the watchdog on every
+ * settle path (close, error, abort), so it cannot outlive the child it watches.
+ *
+ * The poll is REF'd, deliberately. It used to be unref'd, on the reasoning that a
+ * pending watchdog poll should never keep the process alive at exit — but under
+ * Bun on WINDOWS an unref'd timer does not fire at all once nothing ref'd is
+ * pending. Measured on a windows-latest runner (bun 1.3.14): an unref'd interval
+ * with nothing else pending never fired in 20s, while the identical ref'd one
+ * fired at 101ms; on linux both fire at 100ms.
+ *
+ * That state — no ref'd work outstanding — is EXACTLY the state this watchdog
+ * exists to police: a child whose model stream has gone silent. So the unref
+ * disabled the guard precisely when it was needed, and every stream-stall
+ * integration test hung forever on windows (CI runs 30476786365, 30477802633,
+ * 30478455402 — it hangs at v0.24.1 too, so this predates that release).
+ * A poll that can delay exit by one interval is the cheaper failure.
  */
 export const realStreamTimerDeps = {
     now: () => Date.now(),
-    schedule: (fn, ms) => {
-        const handle = setInterval(fn, ms);
-        if (typeof handle.unref === 'function') {
-            ;
-            handle.unref();
-        }
-        return handle;
-    },
+    schedule: (fn, ms) => setInterval(fn, ms),
     cancel: handle => clearInterval(handle)
 };
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@mjasnikovs/pi-task",
-    "version": "0.24.2",
+    "version": "0.24.3",
     "description": "Deterministic task planning and spec-orchestration for local models — crash-safe /task pipelines with verify/enforce gates, a real-time remote web view, and web/docs/fetch/worker subagent tools.",
     "type": "module",
     "main": "./dist/index.js",