pi-crew 0.11.2 → 0.11.5

package/CHANGELOG.md

@@ -1,6 +1,88 @@
 # Changelog
 
-## [Unreleased]
+## [0.11.5] — Phase A + Buổi 1 quick wins: G1 fence, NEW-1 data-loss, G18 breakdown, Node-24 matrix (2026-09-30)
+
+### fix(security): G1 — sanitize the dependency-output fence body (mirror ADR-5 seams)
+
+- `renderDependencyOutputContext` (`src/runtime/task-output-context.ts`) inlined worker-controlled text (dependency `resultSummary`, `structuredResults` JSON, sharedRead content) into the next worker's prompt with only a `.trim()` — the last of the 4 prompt seams without the trust fence. A malicious/compromised dependency could smuggle a literal `</dependency-context>` to close the fence early and promote its payload to the instruction channel, or smuggle control chars. Now a local `sanitizeFencedBody()` (mirroring `renderAskAnswer`/`renderDelegateResult` in `src/prompt/prompt-runtime.ts`) strips control chars and neutralizes the closing-tag literal, applied once at the return so future fields are covered automatically. Pinned RED-first by `test/unit/runtime/core/task-output-context-fence.test.ts` (6 cases: 3 smuggling sinks, control-char strip, benign-unchanged snapshot, wrapper-opens/closes-once).
+
+### fix(state): NEW-1 — persist the FULL task array on individual-stale repair (data-loss)
+
+- The individual-stale branch of `reconcileStaleRun` returned `repairedTasks` already FILTERED to the stale subset, and the crash-recovery caller full-overwrote `tasks.json` with it — every healthy task silently vanished from disk until the parent merged (permanent loss if the parent crashed in that window; the 12m27s heartbeat-freeze trigger was observed live). New `persistTasks` field (option A2): the individual-stale branch also returns the full mutated array, the caller persists `persistTasks ?? repairedTasks`, while `repairedTasks` keeps its exact meaning (what was repaired — the upsert/detail loop is untouched). Pinned RED-first by 3 new cases in `test/unit/runtime/core/stale-reconciler.test.ts` (full-shape, caller-persists-all-4-tasks via `reconcileAllStaleRuns`, regression guard that the other 4 branches leave `persistTasks` unset).
+
+### feat(inspect): G18 — `breakdown` action reads per-task prompt-breakdown artifacts
+
+- New status-domain action `{ action: 'breakdown', runId, taskId? }` (57th schema action) surfaces the opt-in `metadata/<taskId>.prompt-breakdown.json` artifacts (recorded when the host session starts with `PI_CREW_PROMPT_BREAKDOWN=1`): per-task `estTokens` totals, top-5 largest sections, run total — text table + structured `data.perTask`/`data.runTotal` for the leader prompt and W-F token decisions. Runs without breakdowns get a pointer to the env gate instead of an error. Schema/dispatch/docs synced in one commit: `STATUS_ACTIONS` + `STATUS_DOMAIN_ACTIONS` + `domainForAction`, `docs/actions-reference.md` Quick Reference + section, CLAUDE.md domain table (status 16→17), README count, `team-tool-schema-actions.test.ts` 56→57 derivation guard. Follow-up fix in this release: `pre-execution.ts` used to discard the breakdown `writeArtifact` descriptor, so live-run manifests never indexed it — the descriptor now flows through `ctx.breakdownArtifact` into the manifest merge (pinned by `post-execution-breakdown-index.test.ts`, 2 cases).
+
+### docs: correct stale bundle comments
+
+- `index.ts` + `scripts/bench-cold-start.mjs` carried 2025-era numbers: "2.9MB single file", "1100 .ts files", "src/ is excluded by the files field, ~5MB instead of ~16MB", "~19% faster total cold-start". Re-measured 2026-09-30 at this commit: `dist/index.mjs` = 1,614,662 B ≈ 1.6MB, `src/` = 520 `.ts` files, and the `files` field DOES include `src/`. Comments now state the tarball ships the bundle as entry AND includes src/, and the bundle's value is correctness + deterministic startup (warm `NODE_COMPILE_CACHE` shrinks the speed gap to ~2%).
+
+### fix(test): Node-24 compatible cancelled-suite fixtures
+
+- Node 24 changed `node:test` to hold event-loop refs while subtests are pending, so the RR-021 unref'd-timer loop-drain fixtures no longer produced cancelled tests (verified: v24.21.0 `cancelled 0` vs v22 `cancelled 2`) — caught by the first-ever Node-24 CI run of the matrix added earlier in this release. The two empirical cancelled-suite cases in `test-runner-exit.test.ts` now use the AbortSignal-abort shape, which yields `# cancelled 2` deterministically on BOTH Node 22 and Node 24 (21/21 on both locally; CI 33/33 green).
+
+### ci: Node 24 added to the test matrices
+
+- `.github/workflows/ci.yml`: both matrix jobs (`unit`, `test`) now run `[22, 24]` — Node 24 (LTS since 2025-10) gets first-class coverage while engines stay `>=22.0.0` and `.nvmrc` stays `22`. Nightly/smoke/weekly pins intentionally untouched. Opens the door for the strip-types-flag removal and tsconfig ES2023 bump once the ≥22.18 floor decision lands (upgrade plan §5 Q3).
+
+### chore(deps): semver-in-range batch
+
+- In-range bumps only: `@biomejs/biome` 2.5.3→2.5.14, `@sinclair/typebox` 0.34.50→0.34.52, `acorn` 8.17.0→8.18.0, `esbuild` 0.28.1→0.28.2, `yaml` 2.9.0→2.9.1, `tsx` 4.23.0→4.23.15, `@types/node` 25.9.5→25.9.8. Deliberately NOT bumped (per plan): `diff` (P1-4), `@earendil-works/*` (Phase D), `@types/node` 26 (floor decision). `test:critical` 116/116 green under the new deps.
+
+### docs: action-count truth-sync + drift gate
+
+- The repo carried five different action totals (53/54/55/56, and "28 total" in CLAUDE.md). Verified programmatically via `allActionLiterals.length === 56` (10 run + 16 status + 7 control + 17 manage + 6 automate, incl. `compare`), then synced the header comment in `src/schema/team-tool-schema.ts`, `README.md`, `CLAUDE.md`, `docs/actions-reference.md`, and `skills/real-test-pi-crew/SKILL.md`; fixed the `child-pi.ts`→`child-pi/` reference drift and backfilled the missing `compare` row in the actions reference.
+- New gate `test/unit/schema/team-tool-docs-sync.test.ts` (precedent: `config-schema-sync.test.ts`) fails when docs drift from `allActionLiterals` again — negative-tested before landing.
+
+### chore(perf): perf-report runtime writes leave `docs/` root
+
+- `scripts/analyze-run.mjs` now writes runtime perf reports to `docs/perf/` (existed, now the default write target) with a narrow `.gitignore` pattern (`docs/perf/perf-report-team_*`) so curated `docs/perf/` content stays tracked. Verified 0 runtime perf-report files tracked; audit suite 28/28 + live smoke confirm the new path.
+
+## [0.11.4] — test-gate hardening + RR-023 battery fixes (2026-09-29)
+
+### fix: grandchild relay empty — inherit the parent task's model on model-less delegate (RR-023, 2026-09-29 battery finding #3)
+
+- **Root cause (run `team_20260929041427_5c40c4fd7e950443`)**: the relay/capture chain (`delegate-spawn.ts` capture → broker fence/mailbox → prompt-runtime poll) was FAITHFUL — all 3 delegate calls omitted `model`, so the broker spawned the grandchild model-less, the child pi booted on the pi GLOBAL default (`minimax/MiniMax-M3` while the parents ran `zai/glm-5.3`), and that model returned empty completions (assistant `content: []` ×3, per the gc session jsonl) — `rawFinalText` undefined + stdout `""` → the relay delivered an empty fenced body as `ok:true`. Same family as finding #1 (75502b68). **Fix**: the `delegate.request` admission now threads the parent task's `model` out of the locked record read and the spawner inherits it when the request omits `model` (explicit `model` still wins; no-model-everywhere passthrough unchanged) — the grandchild can no longer silently fall through to the global default. **Diagnosability guard**: the capture expression is extracted as pure `grandchildResultText()` and an exit-0-with-zero-assistant-text result now renders `[grandchild exited 0 with no assistant output]` instead of an empty mailbox body indistinguishable from a relay bug. Pinned RED-first by `test/unit/runtime/broker/delegate-grandchild-model.test.ts` (fake-spawner harness, 3 ACs) + `test/unit/runtime/delegate-grandchild-result-text.test.ts` (5 unit cases on the helper).
+
+### fix: broker run.lock contention — typed busy frame instead of connection kill (RR-023, 2026-09-29 battery finding #4)
+
+- **`wait.request`/`delegate.request` busy degradation**: both handlers ran their state RMW inside `withRunLockSync`; a live cross-process run.lock holder (e.g. the detached runner persisting task state) made `acquireLockWithRetry` throw immediately and the throw escaped `handleData` → `closeConnection` — direct-async workers saw an untyped `code=close` socket death within ~5ms (evidence: `team_20260929041005` ask-probe / `team_20260929041020` delegate-probe; the sync foreground run was the zero-contention control). New `protocol/lock-busy.ts` classifies the lock-busy throw by its exported message identity, retries on a bounded async-back-off schedule (new `CrewBrokerOptions.lockBusyRetryDelaysMs`, default 50/100/200/400/800ms), then answers a typed `busy` error frame with the connection SURVIVING (ping still answers); the delegate path additionally records `delegate.rejected(reason=run-lock-busy)` in events.jsonl — never silent. `locks.ts` steal semantics untouched (lock family v0.9.26 invariant). Pinned by `test/unit/runtime/broker/crew-broker-lock-contention.test.ts` (3 tests incl. the default-schedule retry-absorbs-transient-hold case).
+
+### fix: test-gate integrity (RR-021 review rounds 2-3)
+
+- **Test runner cancelled-test guard** (`scripts/test-runner.mjs`): a dual reporter keeps stdout UX unchanged (spec under TTY, TAP otherwise) while a full TAP stream is written to a temp file; `# cancelled N > 0` now fails the run loudly in BOTH the single-run and batch paths — independent of node:test's exit-code mapping. Belt-and-suspenders against the round-1 incident class (unref'd-race-timer tests cancelled while the harness reported green).
+- **Test runner missing-file pre-check** (round-3 B1): node:test v22 silently skips an explicitly-listed file that does not exist (when other files still run) and exits 0 — a renamed/deleted test file would silently drop out of `test:critical`-style gates forever. The runner now refuses to spawn and names the missing paths; glob-shaped args are left to node:test's own expansion.
+- **`test:bundle` now routes through the guarded runner** (was a bare `node --test` bypass — the only CI gate without the cancelled/missing-file/fail-closed wrappers).
+- **`check:lazy-imports` hardened**: composite `import()` forms that escaped every earlier rule are now caught (`[(,\[\{]\s*import(`, `>\s*import(`, `=\s*import(`); a zero-match `git grep` (fully-clean `src/`) no longer crashes the gate; the type-annotation skip now requires a member-access suffix `import("...").T` so compound runtime forms are never false-skipped; dist-side regex is whitespace-proof. Remaining gaps (ternary-else, object-property, case/label) are documented in the script.
+
+## [0.11.3] — optimization audit fixes: correctness, hang-risks, bundle, DX, dead code (2026-09-27)
+
+### fix: correctness + hang-risks (RR-021 M1)
+
+- **`classifyReviewOutcome` word-boundary bug**: the `"\baccept\b"`/`"\breject\b"` signals were TS string literals — `\b` is a BACKSPACE char there, so the two strongest verdict signals never matched anything. All 49 signals are now precompiled module-scope regex literals, and a negation guard stops "I cannot accept this" counting as approval. Reject-first precedence unchanged.
+- **Git precondition probes** (`rev-parse`/`status` in the verification worktree sandbox) gained a 5s timeout — a wedged git no longer blocks the extension forever; the existing catch degrades to `available:false`.
+- **`detectRipgrep` hardening**: a spawned-but-wedged `rg --version` is SIGKILLed by an unref'd 3s timer (defaults to unavailable); concurrent first calls share ONE in-flight detection promise instead of spawning one rg per caller.
+- **`markDeadAsyncRunIfNeeded`** reroutes to the async `withRunLock` (same v0.9.26 lock family — live-token interop); the 5s notifier tick no longer holds the event loop on a sync acquisition. The notifier tick keeps no-overlap semantics. `async-runner.ts`'s in-process test seam keeps its one-shot sync lock by design.
+- **`reconcileAllStaleRuns`** is async and reconciles runs with `mapConcurrent` bound 4 (per-run lock files are independent); results keep snapshot order, plan-approval re-check and re-read-inside-lock semantics unchanged.
+
+### perf: bundle + startup hygiene (RR-021 M2)
+
+- esbuild/acorn/diff load lazily through sync `createRequire` shims (model: `syntax-highlight.ts`) — three eager module-scope imports no longer paid on every extension load; `diff` wildcard import narrowed to `diffWords` (+ type-only `Change`).
+- `ajv` marked external (it is only reached via a lazy `await import`) — the bundle shrank 1.65 MB → 1.53 MB and skips parse cost for a rarely-taken path.
+- `check:lazy-imports` catches the common runtime `import()` positions (the old gate matched only `await import(` — audit blind-spot #2) and asserts the committed `dist/index.mjs` contains no module-scope hoisted import of esbuild/acorn/diff/jiti/cli-highlight/yaml/ajv. 23 runtime import sites across 9 files gained `// LAZY:` markers. (Wording corrected post-0.11.3: exotic positions — ternary-else, object-property, case/label — remain documented gaps; see Unreleased.)
+
+### perf(dx): incremental typecheck + flake-resistant waits (RR-021 M3)
+
+- `tsconfig.json` enables `incremental` + a cached `tsBuildInfoFile` (gitignored) — measured with TS 7.0.2: cold 4.10s → warm 1.41s.
+- Three flake-prone suites (`post-exit-stdio-guard`, `preload-idle-render`, `prompt-runtime-steer-boot-window`) replace fixed sleeps with poll-based `waitFor`/`waitForQuiet` (25ms poll, deadlines sized ≥2× the worst-case timer, quiet windows derived from a measured render timeline). Each file verified ×3 consecutive runs with zero flakes.
+
+### perf: scale + hygiene (RR-021 M4)
+
+- The notifier tick and run picker read a bounded `listRecentRuns` window (40→20 after the session filter) instead of scanning the full run index every debounce window; the startup seed keeps its full scan by design.
+- Dead code deleted (−1.6k lines, all verified 0-production-consumer): `src/benchmark/` + its two test files, `ui/card-colors.ts`, `utils/completion-dedupe.ts`, `utils/resolve-shell.ts` + their tests; the affected suites were trimmed to their live checks.
+- Eleven drive-by fixes: Set/Map lookups for hot `includes`/`find` loops (settled batch filter, task-list dependency labels, agents-pane first-wins live-handle map, group-join task resolution), allocation-free reverse scans replacing `[...arr].reverse().find()` copies (×3), a 256-entry cap for `stableComponentCache`, `TypeCompiler.Compile(TeamToolParams)` compiled once (STATIC) instead of per-call `Value.Check` schema walks, a 30-min WALL-CLOCK poll deadline (the old 1800-poll cap silently assumed a 1s configurable interval), a bounded `waitForRecord` (300s deadline racing wedged promises; expiry returns the current record — never undefined), collision-free `msg_<randomUUID>` mailbox ids, and module-scope precompiled regexes for the crew-input router + implicit-tag detector.
+- Spinner isolation (`run-dashboard` `spinnerBucket`/`metricsSig`) deferred to a follow-up — needs a live TUI profile first.
 
 ## [0.11.2] — runtime hygiene, in-process async test seam, slash-command fixes (2026-09-26)
 

package/README.md

@@ -34,7 +34,7 @@ repo:  https://github.com/baphuongna/pi-crew
 
 ## Features
 
-- **One `team` tool, 55 actions** — run, monitor, steer, schedule, and manage agents/teams/workflows ([actions reference](docs/actions-reference.md)).
+- **One `team` tool, 57 actions** — run, monitor, steer, schedule, and manage agents/teams/workflows ([actions reference](docs/actions-reference.md)).
 - **Real child Pi workers** — each task spawns an isolated `pi` process; `runtime.mode: "scaffold"` gives a dry-run with prompts only.
 - **Built-in teams & adaptive planning** — 6 teams and 11 workflows ship in the box; the `default` and `implementation` workflows let a planner agent pick the smallest effective crew.
 - **Parallel execution + worktree isolation** — tasks in the same phase run concurrently; `workspaceMode: "worktree"` gives each task its own git worktree for safe parallel edits.