@mjasnikovs/pi-task 0.38.26 → 0.38.28

package/dist/workers/pi-worker.js

@@ -8,6 +8,7 @@
  */
 import { Text } from '@earendil-works/pi-tui';
 import { Type } from '@sinclair/typebox';
+import { getConfig } from '../config/config.js';
 import { groupThinkingArgs } from '../config/reasoning-args.js';
 import { runWorker } from './pi-worker-core.js';
 import { childFailureReason, formatChildFailure, makeWorkerTool, workerAnswer, workerUnavailable } from './shared.js';
@@ -47,12 +48,12 @@ export function registerPiWorker(pi) {
                 prompt: params.prompt,
                 cwd: ctx.cwd,
                 signal,
-                // `adhoc` is every guard at its default — which is what this call
-                // site already got by naming none of them. Named now so it is a
-                // decision, and so the one asymmetry it carries (a FIXED 240s cap
-                // where a research worker gets 240s without progress) is written
-                // down. See the `adhoc` row in workers/worker-profiles.ts.
                 profile: 'adhoc',
+                // The user's own `stuck reply retry` is what bounds this worker
+                // now — it kills on SILENCE, never on slowness. It is an INPUT and
+                // not policy for the same reason the gate's two ceilings are: the
+                // number is the user's, the decision to arm it is the profile's.
+                policyInputs: { streamInactivityMs: getConfig().streamInactivityMs },
                 thinking: groupThinkingArgs('research')
             });
             const details = { exitCode: result.exitCode };

package/dist/workers/worker-profiles.d.ts

@@ -295,7 +295,7 @@ export declare const WORKER_PROFILES: {
     readonly adhoc: {
         readonly id: "adhoc";
         readonly why: string;
-        readonly resolve: () => {
+        readonly resolve: (inputs: WorkerPolicyInputs) => {
             guards: WorkerGuards;
             carryForward: false;
         };

package/dist/workers/worker-profiles.js

@@ -175,18 +175,38 @@ export const WORKER_PROFILES = {
     },
     adhoc: {
         id: 'adhoc',
-        why: 'The model-dispatched `pi-worker` tool. Every guard at its default, and '
-            + 'this row exists so that is a DECISION rather than the absence of one — '
-            + 'the call site passed nothing, and nobody could see what it therefore '
-            + 'got. What the table now makes visible is an asymmetry: this is the '
-            + 'strictest-clocked of the three children. It runs a FIXED 240s cap, '
-            + 'because `progressCeilingMs` is null and the deadline re-arm is inert '
-            + 'without one, while a research worker doing the same read-only '
-            + 'exploration gets 240s WITHOUT PROGRESS up to 20 minutes. That '
-            + 'difference is preserved exactly here and is NOT defended: the progress '
-            + 'deadline was measured for the research workers (nexttask 9) and has '
-            + 'never been measured for this tool. It is a candidate, not a bug.',
-        resolve: () => ({ guards: baseGuards(), carryForward: false })
+        why: 'The model-dispatched `pi-worker` tool: a read-only child with '
+            + '`read,grep,find,ls` and nothing else, asked a question the MODEL wrote. '
+            + 'It has NO WALL CLOCK, and that is a decision with evidence behind it. '
+            + 'It used to run a FIXED 240s cap — total elapsed, not idle — inherited by '
+            + 'naming no guards at all. A fixed wall clock on a read-only worker makes '
+            + "answer quality a function of the user's hardware: the same prompt on a "
+            + 'slower local model loses its work and degrades, which is the argument '
+            + 'research-fanout-budget.ts already records against every wall-clock lever '
+            + '("no constant fixes that"). THAT ARGUMENT IS WHAT DECIDES THIS, and it '
+            + 'needs no measurement. The constant was also already stale: it was sized '
+            + 'against "~25-130s on the local backend" — its only stated basis, with no '
+            + 'entry in magicknumbers.md — and replaying 28 real recorded prompts after '
+            + 'nothing but a MODEL swap on the SAME machine gave median 56s, p90 160s, '
+            + 'max 280s, with 5/28 above the 130s it was calibrated to. A bound that '
+            + 'must be re-measured whenever the model changes is the wrong bound. '
+            + "What replaces it is `stream-stall`, armed from the user's own "
+            + '`stuck reply retry` setting: it kills on SILENCE, never on slowness — '
+            + '"one token every 30s is a working local model and must never be killed; '
+            + 'zero events for the whole window is a hang" — so it needs no calibration '
+            + 'and no new setting. Real thrash is still caught by the two runaway '
+            + 'detectors and the dead-backend probe, all of which stay on.',
+        resolve: inputs => {
+            const guards = baseGuards();
+            // No wall clock. See `why`: a fixed elapsed-time cap on a read-only
+            // worker is a hardware test, not a work test.
+            guards['worker-timeout'] = { timeoutMs: 0, progressCeilingMs: null, fanout: null };
+            // The silence bound that replaces it — the user's own setting, not a
+            // new one. 0 when the caller hands none, which is off, exactly as
+            // before: a harness must not silently acquire a guard.
+            guards['stream-stall'] = inputs.streamInactivityMs ?? 0;
+            return { guards, carryForward: false };
+        }
         // `as const satisfies`, not an annotation — the same reason RESTART_ORDER
         // gives: an annotation widens each row back to `WorkerProfile`, and the
         // `why` strings and literal ids stop being visible to a reader or a test.

package/package.json

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