@mjasnikovs/pi-task 0.38.7 → 0.38.8

package/dist/task/auto-orchestrator.js

@@ -25,7 +25,7 @@ import { requestCancel, resetCancel, isCancelRequested, cancelCheckpoint } from
 import { armCancelListener, disarmCancelListener } from './cancel-input.js';
 import { beginRun, endRun } from './mid-run-input.js';
 import { reportDroppedInput } from './dropped-input.js';
-import { refineExistingFilesBlock } from './phases.js';
+import { refineExistingFilesBlock, SINGLE_READ_EXTENSION_PATH } from './phases.js';
 import { SessionUI, registerBridgeCommand, publishLifecycleNotice } from '../remote/bridge.js';
 import { pushNotify } from '../remote/push.js';
 import { startAutoLoader } from './widget.js';
@@ -1079,6 +1079,13 @@ function defaultDeps(ctx, cwd, signal, title) {
         cwd,
         taskId: '',
         signal,
+        // IN-RUN thrash guard for the planning children (mx5-n 2026-08-14: a
+        // decompose child re-read DESIGN/marketplace.html until it filled a
+        // 120k window, and ran 16m23s without returning). Every planning child
+        // gets its source doc INLINED in its prompt, so a second read of a file
+        // it has already opened can only be thrash — which makes the read-once
+        // block safe here in a way it is not for a phase that must explore.
+        childExtensions: [SINGLE_READ_EXTENSION_PATH],
         onChildOutput: (line) => {
             lastLine = line;
         },

package/dist/task/child-runner.d.ts

@@ -58,14 +58,16 @@ export interface PhaseRunResult {
     /** Set when the child's final turn failed with stopReason "error" (model/provider failure). */
     modelError?: string;
 }
-export declare function childArgs(tools: string): string[];
+export declare function childArgs(tools: string, extensions?: readonly string[]): string[];
 export declare const USER_CANCELLED = "__user_cancelled__";
 /**
  * Run a child pi process with JSON event-stream output, loop detection, and
  * context-usage tracking. This is the typed convenience wrapper used by
  * phase-level code.
  */
-export declare function runChild(cwd: string, tools: string, prompt: string, signal: AbortSignal, onLine?: (line: string) => void, onContextUsage?: (snapshot: ContextSnapshot) => void, onToolCall?: (call: ToolCall) => LoopHit | null, spawnFn?: SpawnFn): Promise<PhaseRunResult>;
+export declare function runChild(cwd: string, tools: string, prompt: string, signal: AbortSignal, onLine?: (line: string) => void, onContextUsage?: (snapshot: ContextSnapshot) => void, onToolCall?: (call: ToolCall) => LoopHit | null, spawnFn?: SpawnFn, 
+/** Internal `-e` extension paths for in-run guards (see childArgs). */
+extensions?: readonly string[]): Promise<PhaseRunResult>;
 interface PhaseDeps {
     cwd: string;
     taskId: string;
@@ -79,6 +81,17 @@ interface PhaseDeps {
      */
     recordSubStep?: (label: string, ms: number) => void;
     spawn?: SpawnFn;
+    /**
+     * Internal `-e` extension paths loaded into this child for IN-RUN guards.
+     *
+     * The point of a guard that runs inside the child is that it does not have
+     * to kill it: pi turns a `tool_call` handler's `{block, reason}` into an
+     * error tool result, so the model reads the reason as its own tool output
+     * and continues with its context intact. The host's only alternative is to
+     * kill and re-spawn from nothing, which just re-runs a model that
+     * deterministically re-thrashes (workers/single-read-guard.ts).
+     */
+    childExtensions?: readonly string[];
     /**
      * Wall-clock budget for ONE spawn of this child, in ms. Defaults to
      * PHASE_CHILD_TIMEOUT_MS; `0` disables the cap. Mirrors runWorker's

package/dist/task/child-runner.js

@@ -127,7 +127,7 @@ export function connectionRetryBackoffMs(attempt) {
 }
 const defaultSleep = (ms) => new Promise(resolve => setTimeout(resolve, ms));
 // ─── Spawn helpers ───────────────────────────────────────────────────────────
-export function childArgs(tools) {
+export function childArgs(tools, extensions = []) {
     // `--mode json` puts the child into the structured event stream the
     // unified runner parses in `mode: 'json-events'`. Without it the child
     // emits plain text, every line fails JSON.parse, finalText stays empty,
@@ -142,8 +142,13 @@ export function childArgs(tools) {
     // The prompt is NOT an argv element: it goes to the child over stdin (see
     // runChild below / getPiInvocation), so a large inlined-design prompt can't
     // overflow the OS command-line limit (Windows `spawn ENAMETOOLONG`).
+    //
+    // `extensions` are internal `-e` loads for in-run guards (the caller supplies
+    // the path). A no-tools child cannot make a tool call, so it never carries
+    // one — the guards all hang off pi's `tool_call` hook.
     const toolFlags = tools === '' ? ['--no-tools'] : ['--tools', tools];
-    return [...childBaseArgs(), '--mode', 'json', ...toolFlags];
+    const internal = tools === '' ? [] : extensions;
+    return [...childBaseArgs(internal), '--mode', 'json', ...toolFlags];
 }
 // Sentinel error thrown when the user dismisses a grill-me dialog.
 // Defined here (not in failure-classifier.ts) to avoid circular dependency.
@@ -154,8 +159,10 @@ export const USER_CANCELLED = '__user_cancelled__';
  * context-usage tracking. This is the typed convenience wrapper used by
  * phase-level code.
  */
-export async function runChild(cwd, tools, prompt, signal, onLine, onContextUsage, onToolCall, spawnFn) {
-    const invocation = getPiInvocation(childArgs(tools), prompt);
+export async function runChild(cwd, tools, prompt, signal, onLine, onContextUsage, onToolCall, spawnFn, 
+/** Internal `-e` extension paths for in-run guards (see childArgs). */
+extensions) {
+    const invocation = getPiInvocation(childArgs(tools, extensions), prompt);
     let loopHit;
     const result = await runChildUnified(spawnFn ?? spawn, invocation, cwd, signal, {
         mode: 'json-events',
@@ -289,7 +296,7 @@ export async function runPhaseChild(deps, name, tools, prompt) {
         const clock = phaseTimeout(deps.signal, budgetMs);
         let r;
         try {
-            r = await runChild(deps.cwd, tools, prependHint(hint, prompt), clock.signal, deps.onChildOutput, deps.onContextUsage, call => detector.record(call), deps.spawn);
+            r = await runChild(deps.cwd, tools, prependHint(hint, prompt), clock.signal, deps.onChildOutput, deps.onContextUsage, call => detector.record(call), deps.spawn, deps.childExtensions);
         }
         finally {
             clock.cleanup();

package/dist/task/phases.d.ts

@@ -111,6 +111,15 @@ export declare function searchConfigured(getEnv?: (k: string) => string | undefi
 /** Extra prompt block for the APIS worker when search is available — trigger-framed
  *  (the validated shape for getting a local model to actually reach for search). */
 export declare const RESEARCH_SEARCH_HINT: string;
+/**
+ * In-process guards loaded into the TOOLING worker only: block a re-read of any
+ * file already read, and block any byte-identical grep/find/ls repeat, feeding
+ * the model "you already have this, answer now" instead of letting it re-run.
+ * TOOLING reads each file once and never needs an identical search twice in any
+ * healthy recorded run, so neither rule has a legitimate false positive here.
+ * See single-read-guard.ts.
+ */
+export declare const SINGLE_READ_EXTENSION_PATH: string;
 /**
  * The TOOLING worker only needs to know which verification commands the task
  * cares about — never the per-file edit list. Big refined prompts embed a long

package/dist/task/phases.js

@@ -332,7 +332,7 @@ export const RESEARCH_SEARCH_HINT = '\n\nLIVE WEB — use pi-worker-search for e
  * healthy recorded run, so neither rule has a legitimate false positive here.
  * See single-read-guard.ts.
  */
-const SINGLE_READ_EXTENSION_PATH = fileURLToPath(new URL('../workers/single-read-extension.js', import.meta.url));
+export const SINGLE_READ_EXTENSION_PATH = fileURLToPath(new URL('../workers/single-read-extension.js', import.meta.url));
 /**
  * Task-file heading under which a research worker's validated output is cached.
  * A resumed research phase reads these to skip workers that already succeeded,

package/package.json

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