pi-crew 0.9.54 → 0.9.56

package/CHANGELOG.md

@@ -3,6 +3,59 @@
 > **Note:** `atomic-write-v2.ts` / `AtomicWriter` mentioned in historical entries below was consolidated into `atomic-write.ts` as of v0.9.42. This changelog is preserved as historical record — the migration was completed (the v2 class was never adopted; v1 won on simplicity + symlink-safety + link+unlink atomicity). See `docs/migration/atomic-write-v2-migration.md` for the decision rationale.
 
 
+## [0.9.56] — performance remediation + team-tool schema fix (2026-07-30)
+
+Follows the verified `performance-audit-2026-07-29.md` (16 findings addressed). Independently deep-reviewed by a 4-agent review team (explore/code-review/security-review/verify — no P0/P1), full unit 6486/0 + integration 190/0, CI green on ubuntu/macos/windows.
+
+### Performance
+- **P0-1**: new `BoundedTail` segment ring replaces the O(n²) `appendBoundedTail` rebuild-per-line on stdout/stderr (5000 CJK lines: 112s → 26ms).
+- **P0-2**: per-eventsPath rotation counter — the async append path's `% 100` gate was always true (counter never incremented there) so `needsRotation` ran every event; now ticked on all three append paths.
+- **P0-3**: the per-batch hot-loop `saveCrewAgents` switched to `saveCrewAgentsCoalesced` (removes the `Atomics.wait`/`sleepSync` main-thread block); terminal writes flush coalesced first.
+- **P0-4**: async event append drops from 5 fsyncs to ~0 (non-terminal) / 1 (terminal) — best-effort pid/`.seq` + F3a-style terminal-only data fsync.
+- **P1-5**: memoize validated agent paths per task (~60 syscalls/event → ~0 after first).
+- **P1-6**: redaction pre-filter `mayContainSecret` skips the ~14 redaction passes on clean strings (no bypass — every secret type still redacted).
+- **P1-7**: scheduler consults the global worker cap (no more over-dispatch on low-core machines).
+- **P1-8**: tail readers use `readJsonlTail`; `status.ts` O(events×messages) → O(events+messages).
+- **P1-9**: manifest cache-hit skips the redundant path re-validation.
+- **P1-10**: `before_task_start` hooks run via `Promise.all`.
+- **P1-11**: `git worktree prune` memoized per-repo (coalesces concurrent calls + once per process).
+- **P1-12**: `resolveRunStateRoot` memoized (containment check was ~8-12 syscalls/call).
+- **P2-21**: drop `dist/build-meta.json` from the npm tarball (−470KB).
+- **P2-25**: `supervisor_contact` events now reach `recordSupervisorContact` (was fully dead — the compact pipeline stripped the payload and `onStdoutLine` received display prose).
+- **H2**: archive retention sweep (`.archive.jsonl` no longer accumulate forever).
+- **H5**: `tasks.find` O(N²) → `Map` at all scheduler sites.
+
+### Platform fix
+- **team-tool schema flatten**: `TeamToolParams` was `Type.Union([5 domain objects])`, emitting a giant `anyOf` that LLM tool-callers could not reliably satisfy → empty/malformed calls → the tool silently defaulted to `list`. Flattened to a single `Type.Object` (all 54 actions + shared fields optional); the handler still validates per-action fields at runtime (defense-in-depth, unchanged).
+
+### Review follow-ups
+- Tighten the `"gh"` redaction marker to `gh[pousr]_` (reduces false-positives like "though"/"highlight").
+- Test guard: `allActionLiterals.length === 54` (schema-derivation regression guard).
+
+## [0.9.55] — HOTFIX: ship src/ (child workers load src/prompt/prompt-runtime.ts by path) (2026-07-29)
+
+**Fixes the delegation / team-run regression** that affected 0.9.52–0.9.54. The extension loaded fine (0.9.54), but delegation/team-run failed with "pi-crew run failed" — the child worker `pi` process could not find its extension.
+
+### Root cause (third consequence of PKG-2)
+pi-crew spawns a child `pi` worker per agent task and passes it `--extension <packageRoot>/src/prompt/prompt-runtime.ts` (pi-args.ts `PROMPT_RUNTIME_EXTENSION_PATH`). The child loads that file BY PATH as its extension. PKG-2 (Sprint 6) removed `src/` from the npm tarball to slim it, so the file did not exist in published installs → child failed → "pi-crew run failed".
+
+This was masked in 0.9.52/0.9.53 by the load failure (extension never loaded, so delegation was never reached). 0.9.54 fixed the load, surfacing this. (Not Windows-specific — my Linux repro passed only because the dev checkout has `src/`; published installs do not.)
+
+`prompt-runtime.ts` also imports 3 more src/ files (crew-broker-child, internal-error, safe-paths), so shipping just it is insufficient.
+
+### Fix
+- **Ship `src/` again** — add `"src/"` to package.json `files`. Reverts the PKG-2 src/ removal. The child worker can now find prompt-runtime.ts. Tarball stays lean (2.4MB compressed / 8.9MB unpacked).
+- **prepack hook** (`scripts/clean-strip-types.mjs`): strips the ~290 strip-types `.js` companion files (dev-only cache, gitignored) from `src/` before every pack/publish, keeping the tarball clean regardless of local dev state.
+- esbuild stays in `dependencies` (0.9.54 fix retained).
+
+### Regression guards (CI Test step)
+- `test/unit/package-ships-src.test.ts` — **new**. Asserts `files` includes `src/` and the path-loaded files exist. Would have caught the PKG-2 regression.
+- `test/unit/bundle-deps-consistency.test.ts` (0.9.54) — bundle external imports declared as runtime deps (caught the esbuild-devDep bug).
+- `test/unit/extension-entry-load.test.ts` (0.9.53) — index.ts has no static src/ imports.
+
+### Note on PKG-2 / 0.9.52–0.9.54
+PKG-2's tarball-slimming caused THREE bugs (load failure, esbuild-devDep mask, delegation failure). 0.9.52–0.9.54 are deprecated. `latest` → 0.9.55.
+
 ## [0.9.54] — HOTFIX (real root cause): esbuild runtime dep mis-declared as devDependency (2026-07-29)
 
 **Fixes the TRUE root cause** of the extension-load regression that affected 0.9.52 AND 0.9.53. Both are deprecated; `latest` now points here.