pi-crew 0.9.17 → 0.9.19

package/src/state/atomic-write.ts

@@ -615,7 +615,7 @@ function flushOnePendingAtomicWrite(filePath: string): void {
 				throw error;
 			}
 			// Exponential backoff: base delay * 2^(retryCount-1), capped at 30 seconds
-			const backoffMs = Math.min(30000, current.coalesceMs * Math.pow(2, current.retryCount - 1));
+			const backoffMs = Math.min(30000, current.coalesceMs * 2 ** (current.retryCount - 1));
 			const timer = setTimeout(() => flushOnePendingAtomicWrite(filePath), backoffMs);
 			timer.unref();
 			current.timer = timer;

package/src/state/state-store.ts

@@ -422,10 +422,16 @@ export function saveRunTasks(manifest: TeamRunManifest, tasks: TeamTaskState[]):
  * see the previous on-disk content while the write is still buffered).
  * Bulk update paths that fan out into multiple writer call sites are the
  * intended use case. Single-update + read-update loops (e.g.
- * persistSingleTaskUpdate) should keep using saveRunTasks.
+ * persistSingleTaskUpdate) should keep using saveRunTasks — OR call
+ * `flushPendingAtomicWrites()` immediately before their read to force
+ * any pending coalesced writes to land on disk first.
+ *
+ * (perf review 2026-07 F4) — now used by persistSingleTaskUpdate's
+ * non-terminal checkpoint path; that caller calls flushPendingAtomicWrites()
+ * before its read-modify-write load to defeat the stale-read window.
  */
 /** @internal */
-function saveRunTasksCoalesced(manifest: TeamRunManifest, tasks: TeamTaskState[]): void {
+export function saveRunTasksCoalesced(manifest: TeamRunManifest, tasks: TeamTaskState[]): void {
 	// FIX: Invalidate cache BEFORE atomic write to prevent stale cache serving.
 	invalidateRunCache(manifest.stateRoot);
 	try {

package/src/ui/terminal-status.ts

@@ -64,9 +64,7 @@ const IDLE_REASSERT_MAX_MS = 5000;
 const COMPLETE_FLASH_MS = 1500;
 
 /** Injected for tests (defaults write to the real /dev/tty). */
-export interface GhosttyWriter {
-	(seq: string): void;
-}
+export type GhosttyWriter = (seq: string) => void;
 
 let ghosttyWriter: GhosttyWriter | undefined;
 

package/src/ui/tool-renderers/index.ts

@@ -6,7 +6,7 @@
  * Uses visibleWidth() for ANSI-aware padding so borders align correctly.
  */
 
-import { Container, Text, visibleWidth } from "@earendil-works/pi-tui";
+import { type Container, Text, visibleWidth } from "@earendil-works/pi-tui";
 import type { CrewAgentRecord } from "../../runtime/crew-agent-runtime.ts";
 import { truncateToWidth } from "../../utils/visual.ts";
 import type { CrewTheme } from "../theme-adapter.ts";

package/src/utils/safe-paths.ts

@@ -85,7 +85,7 @@ function resolveWindowsCanonical(p: string): string {
 		// containment checks: base (from cwd, often long-name) and target
 		// (from os.tmpdir()/mkdtempSync, often short-name) must normalize to
 		// the SAME form or a contained target is wrongly rejected as "outside".
-		let real = fs.realpathSync.native(p);
+		const real = fs.realpathSync.native(p);
 		// Guard against NTFS internal paths (e.g. C:\$Extend\$Deleted)
 		if (real.includes("$Extend") || real.includes("$Deleted")) throw new Error("NTFS internal path");
 		return real;
@@ -267,10 +267,6 @@ export function resolveRealContainedPath(baseDir: string, targetPath: string): s
 			if ((error as NodeJS.ErrnoException).code !== "ENOENT") throw error;
 			// For the final component (target itself), ENOENT is expected for non-existent targets.
 			if (i === resolvedParts.length - 1) continue;
-			// For non-final components (parent directories), ENOENT is also acceptable —
-			// the caller will create them before the write operation if needed.
-			// We only need to ensure no existing path component is a symlink.
-			continue;
 		}
 	}
 

package/workflows/plan-execute.workflow.md

@@ -0,0 +1,30 @@
+---
+name: plan-execute
+description: Plan and execute a goal already analyzed by the calling session (no explore step)
+topology: sequential
+---
+
+## plan
+role: planner
+output: plan.md
+reads: analysis.md
+
+Create a concise implementation plan for: {goal}
+
+The calling session has already analyzed the problem. Its analysis is provided
+as shared context (analysis.md). Build directly on that analysis; only re-verify
+file paths and facts you need. Do not redo full discovery.
+
+## execute
+role: executor
+dependsOn: plan
+
+Implement the plan for: {goal}
+
+## verify
+role: verifier
+dependsOn: execute
+verify: true
+
+Verify completion for: {goal}
+Run tests ONCE (cache to .crew/cache/), read changed files from executor context. Cross-reference test output with the changes. Do NOT re-run tests. Give PASS or FAIL with specific test evidence.