pi-crew 0.11.24 → 0.11.26

package/CHANGELOG.md

@@ -2,6 +2,74 @@
 
 ## [Unreleased]
 
+### Fixed (live battery 2026-10-18 — real-test v0.11.24)
+
+- **fix(gate): RT24-F1 root-gate config/autonomy read over-block** — `rootGateBlockReason` counted the `args` subcommand carrier as a config patch key, so worker-origin `config {args:"show"}` READS were rejected as "writes user-scope config" (live-caught in the v0.11.24 real-test battery; docblock promised reads open). `args` added to the carrier-key sets for `config` and `autonomy`; unknown junk keys stay write-classified (fail-closed). Pinned: reads with carrier keys open, writes hidden behind the same key still gated (`unset`/patch keys), user config byte-untouched. Live-verified end-to-end (fresh `pi -p`, worker env): read allowed + dumps config; `unset` write gate-blocked verbatim "root-session required".
+
+## [0.11.26] — Fix: verifier verdict consumer blocked runs whose verifier returned a prose verdict (live-caught by the post-release real-test battery)
+
+### Fixed
+- **Verifier verdict consumption (R47-3/V4 follow-up, live regression)**: the wave-6 verdict consumer required the exact `PASS:`/`FAIL:` line, but every child-process verifier prompt still asked for a prose verdict ("Give PASS or FAIL with evidence"). A FAILED-gate run whose verifier followed its prompt wrote a bare/decorated verdict → the consumer read `none` → `observed=none` → the green contract **blocked** the run (`green_unsatisfied`) instead of resolving it. Live-proven twice (before/after). Fix, two sides:
+  - `extractVerifierVerdict` now accepts bare/decorated verdicts at line start (`PASS`, `**PASS**`, `PASS — …`, `PASS. …`, `PASS (…)`) while still rejecting mid-line mentions and word continuations (`PASSED`, `PASSing`); FAIL-wins and source-priority semantics unchanged. Pins 11/11 incl. mutation.
+  - Prompts now demand the exact line: `workflows/{fast-fix,plan-execute,review,strict-fast-fix,default}.workflow.md`, `agents/verifier.md`, and both `plan-templates.ts` verifier taskTemplates require `PASS: <what verified> — <evidence>` / `FAIL: <what failed> — <reason>` (green-contract consumer reads it; no verdict line = UNVERIFIED).
+- **Settings catalog refresh**: `docs/ui-samples/captures|png/18-settings` regenerated — the Runtime tab now renders the schema key `runtime.isolationPolicy.defaultRuntime` (was a stale label/key).
+
+### Verified
+- Post-release battery (docs/real-test/reports/real-test-2026-10-19-fix-wave-6-battery.md): T1 124/124 · T2 3-path · T3/T4/T8 md5 · T5 /team-help live · T7×2 (PASS skipVerifier / FAIL verifier-with-context, verdict consumed) · T9a 13/13 · T9b 5 paths · T9b-W ask round-trip + message + delegate + loadout · T9g steer boot-window · T10a tmux 4/4 + herdr 5/5 · T10b live surface run (provider=tmux, spawn/close ×2, 0 degraded) · T11 a–j · T12 18 agents both parsers · T13 real-run render, sweeps clean + PNG inspected.
+
+## [0.11.25] — Fix-wave 6: deep-review R1-R51 close-out (security cluster, state/verification families, doc tail) (2026-10-19)
+
+Close-out wave for the 51-round / ~150-finding deep review recorded in
+`pi-crew-deep-review-2026-10-16.md` (R51 evidence-hardening: 24/24 hardest-class
+findings CONFIRMED, 0 refuted). ~100 work items across 4 milestones, each
+gated on `typecheck` + `test:critical` (124/124) with mutation-pins
+(revert-fix → test RED) on every security item.
+
+### Fixed (M1 — HIGH security cluster, 8 items)
+
+- **fix(config): R24-H1/H2 proto-pollution at the parse boundary** — drop `__proto__`/`constructor`/`prototype` keys in the shared patch/merge helper (config patch, team-settings set/unset, autonomy, i18n `addTranslations` R46-7) instead of mirroring the handler predicate. `team-settings set __proto__.polluted` → clean; `unset __proto__.toString` → rejected. 5 mutation-pins RED.
+- **fix(security): R11-F1/F2 + R11-S1 scope-carrier + workflow-* root-gate** — gate and handlers read the SAME scope source (carrier-key `scope`) with a gate-vs-handler parity matrix for every scope-carrying action; `workflow-create/update/delete/save/import/export` now route through the root-gate (previously ungated). Planted `~/.pi/agent/agents/evil.md` blocked on both paths; worker-origin `workflow-create` blocked. 5/3/1 RED.
+- **fix(prompt): R38-C1 chain-executor worker-text fencing** — worker text fenced (strip ANSI, mark provenance, escape fence) before entering the privileged session.
+- **fix(security): R43-S1 delegate role-tier containment is now TRANSITIVE** — grandchild admission = min(parent tier, requested role tier) via `roleToolPolicy` threading; a read-only parent can no longer spawn a write-capable `executor` grandchild at depth ≥ 2.
+- **fix(artifacts): R44-N1 prune containment** — `unlink` only when the resolved path is under runDir/artifacts (realpath + prefix), blocking `..`/absolute-outside deletion; regression probe (victim file survives).
+- **fix(verify): R47-1 verify-gate ground truth is host-owned** — check commands come from the frozen manifest spec, never re-derived from the worker-mutable task-cwd `package.json`; mismatch → INCONCLUSIVE → verifier spawns (fail-closed). Replay: tampered `scripts.typecheck` now FAILs the gate instead of deterministic PASS + verifier-skip.
+- **fix(config): R45-S2 run-param tier honours the sensitive-drop + kill-switch** — `params.config` can no longer set `executeWorkers:true` over an explicit user `executeWorkers:false`, nor bypass otlp/webhook/policy drops.
+
+### Fixed (M2 — family epics: one change per member-family)
+
+- **fix(prompt/ui/broker): EP1 unfenced-worker-text rollout (≥6 IDs: R4-B1, R11-F2/S3, R31-S1, R38-C1, R46-1, R2-M-B3)** — one `fenceWorkerText()` helper applied at every interpolation of worker text into privileged/orchestrator output (status/dashboard/transcript/tool-result); status-line forgery probe blocked. 5-red/2-red pins.
+- **fix(effectiveness): EP2 provenance-tagged gate-skip (R9-F3 + R47-V7, complementary halves)** — synthesized gate-skip results are tagged `synthetic` and excluded from observable-activity accounting while genuine `delegate.completed` counts; a forged gate PASS is no longer certified "effective".
+- **fix(observability): EP3 read-fault vs corruption + orphan/progress truth (R39-M1/M2/M3, R48-N1/N2/N10a)** — `EACCES`/`EMFILE` no longer quarantine a valid manifest (only SyntaxError does); zombie-sync orphan detection drops the magic-string heuristic; the reaper reclaims PID-1 orphans; transient write errors degrade instead of killing the host. 2-red/1-red/1-red pins.
+- **fix(state): EP4 event-log compaction generation bump (R32-M1 ≡ R4-N1/FS10)** — compaction increments `.gen` so readers cache-miss instead of reading a stale prefix. 3-red pin.
+
+### Fixed (M3 — MED cluster, 28 items)
+
+- **fix(trust-chain): R47-2/V3 fence-escape scrub** — failed-check output entering the bash-capable verifier prompt is now scrubbed/escaped (SEC-4 parity at the dependency seam).
+- **fix(verify): R47-3/V4 `PASS:`/`FAIL:` verdict is a real consumer** — a `FAIL:` verdict now fails the task instead of completing green; `PASS:` is required for "verified".
+- **fix(budget/broker): R43-N1..N4 delegate budget made real** — `tokensGranted` seeded at grant time (unbudgeted delegate refused), delegate spend counted broker-side (not self-reported), terminal signals propagate to grandchildren, grandchild results no longer dropped.
+- **fix(scheduler/state): R21-F1 scoped waitState clear · R22-F2 scheduler persist-in-lock · R23-F1 terminal-write clobber guard on every late path · R33-1 group fan-out dedupe by (group, recipient) · R34 one token unit across 3 call sites.**
+- **fix(lifecycle): R41-1 persistent control-request dedupe (no replay after crash/resume) · R41-4 eviction disposes + aborts with a deadline before removing the record.**
+- **fix(config): R45-F1 `updateConfig` preserves unknown on-disk keys (merge, not replace-whitelist) · R46-7 proto-safe `addTranslations` via the shared helper.**
+- **fix(core-api/robustness): R49-F1 resilient-edit reads a real tool seam (phantom keys gone) · R47-V2/V4adj dead classifier-pre-gate mount removed · R36-1/2 worktree untracked-file artifact + add-failure isolation · R37-1 timeout clamp · R14-1 chain `parallel()` partial-fail visible · R15-1 renderTick async/cached tasks read (bench 0.84→0.014 ms) · R13-1/2 init/cleanup safety · R26-1/2 `prepublishOnly` + real env-vars gate (24 env-param sites migrated) · R18-1/2/3 CI-gate fixes (lazy-import depth-1, template emits, `.js` suffix) · R19-M1 macOS reader · R12-* herdr watcher dispose + caps · R31-1 `AgentOverridesSubmenu.onApply` wired · R28-2 phantom `chain.workflow.md` steps relocated.**
+
+### Changed (M4 — LOW/doc tail, ~60 items: docs follow code)
+
+- **docs: R27 doc-drift ×8** — trust-model v1.2 (DWF gate scope, cold-verifier isolation, telemetry census), `README`/`ui-samples` Node floor `≥ 22.19.0`, README action count 55→57, `publishing.md` test counts (97/120→124) + current config path, `usage.md` `widgetPlacement` default `bottom`, `/team-cleanup` removed (unregistered), `dynamic-workflows.md` default-deny `PI_CREW_TRUST_PROJECT_DWF=1` documented, `read-only-explorer` SKILL tool-availability note (explorer has no `bash`), `CLAUDE.md` Runtime Modes table gains `auto`.
+- **docs: R45-F2/F3/F4** — `autoRepairIntervalMs` comment 60s→300s; both `EFFECTIVE_DEFAULTS` maps report `telemetry.enabled` default ON; `PI_CREW_DEBUG`/`PI_TEAMS_DEBUG` raw-truthiness documented (`=0` still enables → unset to disable) in the registry + troubleshooting.
+- **docs: R48 doctor false-negative catalogue + telemetry egress census** — anomaly-detection matrix in `failure-mode-inventory.md`, operator guidance + mux (R42) sharp edges in `troubleshooting.md`.
+- **docs: R26/R29 packaging notes** — shipped `skills/**/__pycache__`, dev tooling in the tarball, consumer-side `.githooks` referencing unpublished scripts, unbounded `pi-coding-agent` peer, committed-dist requirement.
+- **docs: R28-2/R28-3** — designer/orchestrator capability contradictions documented in-body (the frontmatter-tools de-advertise vs `WRITE_ROLES` decision is left open, see below).
+- **comments (R49-F3/F4/F6/F7, R17-minor):** phantom `pi-core/i18n/*` channels, `pi.on()` never-throws (real degradation = never-fire), crew-cleanup switch-flag vs reason-gate divergence, phantom `ctx.workspaceFolder`, `task.verifier_pre_gate` registration now landed.
+- **docs: R17 event-types CI note** — `docs/TEST_MATRIX.md` records that the LOCAL `check:event-types` is report-only while `ci.yml` runs `--enforce`.
+
+### Known residuals (declared, not hidden)
+
+- `agents/designer.md` / `agents/orchestrator.md` still advertise tool capabilities their permission class denies (`edit`/`write`/`bash` / `delegate`). Both fixes are behaviour-affecting (WRITE_ROLES entry — code — or frontmatter de-advertise — resource metadata); documented in-body pending sign-off.
+- `check:event-types` LOCAL wiring still lacks `--enforce` (one line; verified safe at HEAD).
+- `pi-coding-agent` peer remains unbounded (R49-F2).
+
+## [0.11.24] — Deep review waves 2-4: terminal-escape injection, broker replay/overflow, state read-error wipes (2026-10-18)
+
 ### Fixed (deep review 2026-10-16/17 — Waves 2-4; report `pi-crew-deep-review-2026-10-16.md`, 128/128 cold-verified)
 
 - **fix(state): FS2 + R5-M-B4 + family-2 read-error wipes** — readCrewAgents/plan-store/ownership-map/active-run-registry/orphan-worker-registry no longer collapse non-ENOENT read faults to empty feeding a locked full overwrite (sentinel + skip-save + loud log; ST-4-style guards).
@@ -13,6 +81,8 @@
 - **fix(reliability — Wave 4):** R9-F3 effectiveness counts delegate.completed; R9-OPS2 stale /tmp pc-*.sock sweep (24h); spawnedRunIds pruned; tmux-watcher/BatchBarrier disposal; cron scan hoisted+hopped (no 527k-iteration stall); prune digest head-2/tail-2 fallback for all tools; herdr 10s request timeout + error-ack → mux-dead; oscillation period-2 detection; parked-ask shield derives from clamped deadline (+ broker stamps manifest.waitState.deadline); purgeStaleActiveRunIndex isIntentionalWait + waitState clear; rpcPool overwrite guard; FS6 liveness-before-exactly-once; FS7 fallback attempt enters accounting; FS8 writer-timeout terminates wedged worker; client per-request timer unref'd; steer.push requestId dedupe; missed-cron one-time skipped event.
 - **fix(hardening one-liners):** TMPDIR in child env allowlists (macOS run-lock dual-guard actually contends); escalate `to` validated; deadletter assertSafePathId; PI_TEAMS_PI_BIN path-separator boundary; submit_result error-result on throw; launch-script env-key regex; quoted `command -v` probe; classifier failureSummary redacted; tool_execution args/supervisor_contact compacted + 64KiB line cap; env-vars numeric defaults route through parsers; mock-seam double-gated; sqlite 0600; theme atomic write + no corrupt-wipe; OTLP CUMULATIVE temporality + header precedence; goal-wrap spawn-failure → blocked (no zombie goal); CI-only concurrency clamp; sweep-test-tmp age guard; watch-bundle recursion; temp-root realpath both sides; agent frontmatter ceilings; non-finite heartbeat = corrupt lock; agent-events cursor seq-sort; settings enums derived from schema (+ drift test); mailbox seam sanitize; R10-C1 duplicate-condition fix.
 
+## [0.11.23] — Deep review wave 1: state-loss HIGHs (tasks.json orphan reconcile, coalesced dispatch, agents.json requeue) + broker delegate param validation (2026-10-17)
+
 ### Fixed (deep review 2026-10-16/17 — Wave 1; report `pi-crew-deep-review-2026-10-16.md`, 128/128 cold-verified)
 
 - **fix(recovery): R2-H1 — orphan reconcile persisted the FILTERED zombie subset** (tasks.json data loss, runtime-proven). `/tmp` orphan reconcile wrote `result.repairedTasks` (stale-only subset) via full-overwrite — every sibling record destroyed on a timer tick. Now persists `result.persistTasks ?? repairedTasks` (mirror of `crash-recovery.ts`); caller retention pinning test (3-task fixture: alive + zombie + completed all retained).
@@ -24,6 +94,8 @@
 - **fix(event-log): FS1 + FS3**. FS1: agent-events `.seq` sidecar trusted with no regression guard — crash-window re-mints duplicate seqs that `> sinceSeq` consumers drop forever; now max(sidecar, tail-scan) like EL-1. FS3: cursor `nextSeq=max-delivered` + file-order slice stranded lower-seq events forever on documented non-monotonic files (field-confirmed in 7 runs); `filtered` is now seq-sorted before the limit slice (2 sites); the 2 file-order test pins updated to seq-order contract.
 - **fix(run): R5-M-B3 — 4 bare `void appendEventAsync` in `run.ts`** (probe-proven host crash via unhandledRejection, exit=7); all now `.catch`-logged (17 other sites already were).
 
+## [0.11.22] — DR-01 false-green P0 + rounds 4-7 audit waves (DR-02/DR-03/DR-04) (2026-10-16)
+
 ### Fixed (rounds 4–7 audit waves — DR-02/DR-03/DR-04, reports `docs/reviews/pi-crew-audit-round{4,5,6,7}-*.md`)
 
 - **fix(state): DR-03 C1 — disk-terminal status preserved + delegate allocation max-merge** (R6-1 HIGH). `persistSingleTaskUpdate` reloaded disk inside the lock but `updateTask` replaced by id UNCONDITIONALLY — a detached runner's late settle overwrote a crash-recovery `cancelled` task with `completed` and emitted `task.completed` after `crew.run.orphan_cancelled`. New `mergeTaskUpdateWithDisk()` preserves a differing disk-terminal status (result fields still recorded); post-execution derives the persisted status from the persist return (terminal events via `TERMINAL_TASK_EVENT_TYPES` — never `task.completed` over cancelled). R6-4: delegate budget reserve/roll-up now merges `tokensSpent=max(disk,incoming)` — the 1s heartbeat whole-record replace could no longer clobber a reservation (lost update), and refund over-subtraction self-heals.

package/README.md

@@ -52,7 +52,7 @@ pi install npm:pi-crew
 ```
 
 > The `npm:` prefix is required — without it, `pi install` treats the argument
-> as a local path. Requires Node ≥ 22.
+> as a local path. Requires Node ≥ 22.19.0 (`engines.node`).
 
 Local development (from a clone):
 
@@ -176,7 +176,7 @@ config only, so an untrusted repo cannot point your runs at an attacker URL.
 |-----|----------|
 | [docs/README.md](docs/README.md) | index of all docs (living + archive) |
 | [docs/usage.md](docs/usage.md) | usage patterns + config examples |
-| [docs/actions-reference.md](docs/actions-reference.md) | all 55 `team` actions with examples |
+| [docs/actions-reference.md](docs/actions-reference.md) | all 57 `team` actions with examples |
 | [docs/commands-reference.md](docs/commands-reference.md) | slash commands + `/team-api` |
 | [docs/architecture.md](docs/architecture.md) | internal architecture + run flow |
 | [docs/troubleshooting.md](docs/troubleshooting.md) | common errors, recovery, error codes |

package/agents/designer.md

@@ -35,6 +35,29 @@ When handing off to implementers:
 - Visual excellence first, code perfection second — but never ship broken interactions.
 - Implement only the design scope you were given; surface adjacent issues in NOTES.
 
+## Enforcement note (R28-M2 — capability/gate contradiction, documented not resolved)
+
+This persona is **not** in `WRITE_ROLES` (`src/runtime/role-permission.ts:18`), so
+`permissionForRole("designer")` resolves to **`read_only`** by default-deny. The
+consequences at HEAD are mechanical:
+
+- the runner injects the **read-only contract** block into your system prompt
+  (`src/runtime/task-runner/prompt-builder.ts:29`),
+- the **plan-approval gate is bypassed** for this role
+  (`src/runtime/plan-approval.ts:65`),
+- **MCP tools are cut** (`src/runtime/mcp-proxy.ts:136`),
+- a design-tier task's grandchild spawn tier is floored to `read_only`
+  (`src/runtime/spawn-policy.ts:184`).
+
+Meanwhile this file's frontmatter advertises `edit`/`write`/`bash` and `useWhen`
+claims implementation. That mismatch is a **known open contradiction** — do not
+assume the read-only contract is the enforced one for *tool availability*, and do
+not assume edit/write are sanctioned. Until the leader signs off either
+(a) adding `designer` to `WRITE_ROLES` (a CODE change) or (b) dropping
+`edit`/`write`/`bash` from the frontmatter (a resource-metadata change), treat
+designer as **design + review + handoff**, and route implementation to `executor`
+or `test-engineer`.
+
 ## Output format
 
 End with exactly this block:

package/agents/orchestrator.md

@@ -17,6 +17,23 @@ You are an orchestrator — a delegated orchestration specialist. You own a mult
 ## Canonical routing source (READ THIS)
 Lane routing tables are NOT duplicated in this body. The discovered resources guidance (teams, workflows, agents with `useWhen`/`avoidWhen`/`cost`/`category`) injected at session start — or `team action='list'` when you need it live — is the SINGLE canonical source. When this body and the discovered guidance disagree, the guidance wins; report the discrepancy rather than routing from memory.
 
+## Enforcement note (R28-M3 — the `delegate` tool is DENIED for this role)
+
+This file's frontmatter advertises `delegate`, but **`orchestrator` is not in
+`WRITE_ROLES`** (`src/runtime/role-permission.ts:18`), so
+`permissionForRole("orchestrator")` is `read_only` and
+`checkSubagentSpawnPermission` refuses the spawn at call time
+(`src/runtime/role-permission.ts:51-61`, enforced in
+`src/extension/registration/subagent-tools.ts:129-135`): *"Role 'orchestrator' is
+read-only and cannot spawn additional subagents."*
+
+Practical consequence: you **cannot** spawn subagents yourself. Route work by
+returning a routing/dispatch plan in your output (the leader or root session
+dispatches it), or by using the `team` tool actions that are not subagent spawns.
+Do not advertise nested orchestration you cannot perform. (De-advertising the
+frontmatter `delegate` entry, or adding `orchestrator` to `WRITE_ROLES`, is an
+open decision requiring leader sign-off — both are behaviour-affecting.)
+
 ## Workflow phases
 1. **Route** — classify each unit of work against the discovered lanes (useWhen/avoidWhen/cost). Prefer the cheapest sufficient lane. Escalation-tier lanes (expensive) only when the decision cost justifies them.
 2. **Dispatch** — one owner per file/symbol; parallelize only lanes with no shared write surface. Pass handoff context, not conversation history.

package/agents/verifier.md

@@ -74,7 +74,7 @@ For **implementation** workflows:
 
 ## Output Format
 
-End with exactly this block:
+Start your report with the verdict line — `PASS: <what verified> — <evidence>` or `FAIL: <what failed> — <reason>` (exact single-line format, colon required or the line may be bare `PASS`/`FAIL`; the leader's green-contract consumer reads this line — a report with no verdict line is treated as UNVERIFIED). Then end with exactly this block:
 
 ```
 VERIFICATION: PASS|FAIL