@mjasnikovs/pi-task 0.39.3 → 0.39.4

package/dist/config/tool-list.d.ts

@@ -28,6 +28,16 @@ export interface GuardableTool {
     /** Provenance shown in the menu, e.g. "built in" or "npm:pi-fable (/path)". */
     origin: string;
 }
+/**
+ * pi-task's own tools whose child already carries the guard the host watchdog
+ * would duplicate — and duplicate WRONGLY. `pi-worker` runs the `adhoc` profile
+ * (workers/worker-profiles.ts): no wall clock by decision, bounded on model
+ * SILENCE via `stuck reply retry`, plus the loop, churn and dead-backend guards.
+ * A host wall clock on top killed healthy workers at the command ceiling while
+ * they were still reading. Never armed, never offered as a `watch:` row: the
+ * operator should not be handed a switch that is only ever correct one way.
+ */
+export declare const SELF_BOUNDED_TOOLS: ReadonlySet<string>;
 /**
  * Every tool in the live session, built-ins first and each extension's tools in
  * registration order after them, so the menu reads owner-by-owner.

package/dist/config/tool-list.js

@@ -1,5 +1,15 @@
 /** The `source` pi reports for its own tools rather than an extension's. */
 const BUILTIN_SOURCE = 'builtin';
+/**
+ * pi-task's own tools whose child already carries the guard the host watchdog
+ * would duplicate — and duplicate WRONGLY. `pi-worker` runs the `adhoc` profile
+ * (workers/worker-profiles.ts): no wall clock by decision, bounded on model
+ * SILENCE via `stuck reply retry`, plus the loop, churn and dead-backend guards.
+ * A host wall clock on top killed healthy workers at the command ceiling while
+ * they were still reading. Never armed, never offered as a `watch:` row: the
+ * operator should not be handed a switch that is only ever correct one way.
+ */
+export const SELF_BOUNDED_TOOLS = new Set(['pi-worker']);
 /**
  * Human provenance for a tool's source metadata. `source` is pi's own word for
  * where the owner came from ("builtin", "npm:...", "auto", "cli"); the two
@@ -30,7 +40,7 @@ export function toGuardableTools(tools) {
         // A duplicate name cannot be told apart by the watchdog (it only ever
         // sees `toolName`), so a second registration must not add a second row
         // that silently toggles the first one's guard.
-        if (seen.has(t.name))
+        if (seen.has(t.name) || SELF_BOUNDED_TOOLS.has(t.name))
             continue;
         seen.add(t.name);
         const entry = { name: t.name, origin: toolOrigin(t.sourceInfo.source, t.sourceInfo.path) };

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

@@ -20,9 +20,10 @@ import type { ExtensionAPI } from '@earendil-works/pi-coding-agent';
  *
  * Tool-agnostic by default: it arms on every tool except exact names listed in
  * `commandTimeoutExemptTools`, which /task-config fills from the live tool list
- * (config/tool-list.ts). Exemptions are for tools that already own a bounded
- * timeout and cancellation contract — the guard's whole justification is that
- * pi's bash has NO default timeout, which says nothing about a tool that does.
+ * (config/tool-list.ts), and pi-task's own SELF_BOUNDED_TOOLS, exempt in code.
+ * Exemptions are for tools that already own a bounded timeout and cancellation
+ * contract — the guard's whole justification is that pi's bash has NO default
+ * timeout, which says nothing about a tool that does.
  *
  * SCOPE — this covers the main session ONLY, which is where the implementation
  * turn runs (orchestrator hands the spec off via sendUserMessage). Gate

package/dist/task/command-watchdog.js

@@ -1,4 +1,5 @@
 import { getConfig } from '../config/config.js';
+import { SELF_BOUNDED_TOOLS } from '../config/tool-list.js';
 import { CommandWatchdog, realTimerDeps, reminderMessage } from '../shared/command-watchdog.js';
 /**
  * MAIN-SESSION adapter for the command watchdog.
@@ -21,9 +22,10 @@ import { CommandWatchdog, realTimerDeps, reminderMessage } from '../shared/comma
  *
  * Tool-agnostic by default: it arms on every tool except exact names listed in
  * `commandTimeoutExemptTools`, which /task-config fills from the live tool list
- * (config/tool-list.ts). Exemptions are for tools that already own a bounded
- * timeout and cancellation contract — the guard's whole justification is that
- * pi's bash has NO default timeout, which says nothing about a tool that does.
+ * (config/tool-list.ts), and pi-task's own SELF_BOUNDED_TOOLS, exempt in code.
+ * Exemptions are for tools that already own a bounded timeout and cancellation
+ * contract — the guard's whole justification is that pi's bash has NO default
+ * timeout, which says nothing about a tool that does.
  *
  * SCOPE — this covers the main session ONLY, which is where the implementation
  * turn runs (orchestrator hands the spec off via sendUserMessage). Gate
@@ -73,7 +75,8 @@ export function registerCommandWatchdog(pi) {
     const ctxByCall = new Map();
     const watchdog = new CommandWatchdog({
         getTimeoutMs: () => getConfig().requestTimeoutMs,
-        shouldWatch: toolName => !getConfig().commandTimeoutExemptTools.includes(toolName),
+        shouldWatch: toolName => !SELF_BOUNDED_TOOLS.has(toolName)
+            && !getConfig().commandTimeoutExemptTools.includes(toolName),
         ...realTimerDeps,
         onFire: (toolCallId, toolName, timeoutMs) => {
             const ctx = ctxByCall.get(toolCallId);

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@mjasnikovs/pi-task",
-    "version": "0.39.3",
+    "version": "0.39.4",
     "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",