pi-crew 0.9.23 → 0.9.25

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-crew",
3
- "version": "0.9.23",
3
+ "version": "0.9.25",
4
4
  "description": "Pi extension for coordinated AI teams, workflows, worktrees, and async task orchestration",
5
5
  "author": "baphuongna",
6
6
  "license": "MIT",
@@ -58,7 +58,7 @@
58
58
  "lint": "biome check --linter-enabled=true --formatter-enabled=false --max-diagnostics=50 --diagnostic-level=error .",
59
59
  "format:check": "biome format .",
60
60
  "test": "npm run test:unit && npm run test:integration",
61
- "test:unit": "node scripts/test-runner.mjs --test-concurrency=4 --test-timeout=180000 --test-force-exit test/unit/*.test.ts",
61
+ "test:unit": "node scripts/test-runner.mjs --test-concurrency=4 --test-timeout=300000 --test-force-exit test/unit/*.test.ts",
62
62
  "test:watch": "tsx --watch --test --test-concurrency=4 --test-timeout=30000 --test-force-exit test/unit/*.test.ts",
63
63
  "test:integration": "node scripts/test-runner.mjs --test-concurrency=1 --test-timeout=300000 test/integration/*.test.ts",
64
64
  "test:smoke": "node scripts/test-runner.mjs --test-concurrency=1 --test-timeout=180000 test/smoke/*.smoke.ts",
@@ -250,7 +250,7 @@ export class PipelineRunner {
250
250
  // pending". The buffered flush uses a 20ms ref'd timer that fires
251
251
  // asynchronously; without this explicit drain, the test runner sees
252
252
  // pending appendEventAsync promises and cancels the test file.
253
- await flushEventLogBuffer(eventsPath);
253
+ await flushEventLogBuffer();
254
254
  }
255
255
  }
256
256
 
@@ -817,6 +817,14 @@ export async function executeTeamRun(input: ExecuteTeamRunInput): Promise<{ mani
817
817
  // final buffered progress events are durable alongside the failure state.
818
818
  await flushEventLogBuffer();
819
819
  return result;
820
+ } finally {
821
+ // M7+follow-up (v0.9.24): drain buffer on the success path too.
822
+ // Previously only the catch path flushed; under --test-force-exit the
823
+ // success path left pending appendEventAsync promises that the test
824
+ // runner detected as 'Promise resolution is still pending'. The catch
825
+ // still has its own flush for M7 backward compat — flushEventLogBuffer
826
+ // is idempotent on an empty queue.
827
+ await flushEventLogBuffer();
820
828
  }
821
829
  }
822
830