pi-crew 0.9.25 → 0.9.26

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-crew",
-  "version": "0.9.25",
+  "version": "0.9.26",
   "description": "Pi extension for coordinated AI teams, workflows, worktrees, and async task orchestration",
   "author": "baphuongna",
   "license": "MIT",
@@ -58,7 +58,7 @@
     "lint": "biome check --linter-enabled=true --formatter-enabled=false --max-diagnostics=50 --diagnostic-level=error .",
     "format:check": "biome format .",
     "test": "npm run test:unit && npm run test:integration",
-    "test:unit": "node scripts/test-runner.mjs --test-concurrency=4 --test-timeout=300000 --test-force-exit test/unit/*.test.ts",
+    "test:unit": "node scripts/test-runner.mjs --test-concurrency=4 --test-timeout=180000 --test-force-exit test/unit/*.test.ts",
     "test:watch": "tsx --watch --test --test-concurrency=4 --test-timeout=30000 --test-force-exit test/unit/*.test.ts",
     "test:integration": "node scripts/test-runner.mjs --test-concurrency=1 --test-timeout=300000 test/integration/*.test.ts",
     "test:smoke": "node scripts/test-runner.mjs --test-concurrency=1 --test-timeout=180000 test/smoke/*.smoke.ts",

package/src/state/event-log.ts

@@ -410,15 +410,18 @@ export function resetEventLogMode(): void {
  * foreground-control, etc.), prefer this over the sync `appendEvent()`.
  */
 export async function appendEventAsync(eventsPath: string, event: AppendTeamEvent): Promise<TeamEvent> {
-	// Non-terminal events: route through buffer for coalesced writes (20ms default).
-	// This eliminates per-event fsync + persistSequence overhead for high-frequency events.
-	// The buffer timer is kept alive (ref'd) so standalone contexts (tests, short-lived
-	// scripts) get their events flushed before the loop drains — no per-event keepAlive
-	// intervals needed (which previously starved the event loop at high fan-out).
-	if (!TERMINAL_EVENT_TYPES.has(event.type)) {
-		return appendEventBuffered(eventsPath, event);
-	}
-	// Terminal events: direct async path for immediate durability guarantee
+	// FIX (v0.9.26): Do NOT route non-terminal events through appendEventBuffered.
+	// The buffer uses a 20ms timer + withEventLogLockAsync (promise chain), while
+	// the sync appendEvent path uses withEventLogLockSync (file lock with sleepSync).
+	// Mixing these two lock mechanisms on the same eventsPath causes a deadlock:
+	// the buffer timer can't fire while sleepSync blocks the event loop, and
+	// sleepSync can't acquire the lock while the buffer holds it via the promise
+	// chain. This deadlocked adaptive-implementation, implementation-fanout,
+	// parallel-research-dynamic, run-analysis, and team-run tests (>300s timeout).
+	// Reverted to v0.9.19 behavior: ALL events use the asyncQueues direct path.
+	// The buffer (appendEventBuffered) is still available for explicit callers
+	// that want coalesced writes (e.g., appendEventFireAndForget), but
+	// appendEventAsync itself does NOT buffer.
 	const queueKey = eventsPath;
 	const prev = asyncQueues.get(queueKey) ?? Promise.resolve();
 	const next = prev.then(async (): Promise<TeamEvent> => {