pi-crew 0.11.6 → 0.11.7

package/CHANGELOG.md

@@ -1,5 +1,100 @@
 # Changelog
 
+## [0.11.7] — Pi 1.0.0 adoption waves + deep-learn execution (2026-10-04)
+### Added — Pi 1.0.0 adoption wave (see docs/reviews/pi-1.0.0-adoption-review-2026-10-03.md)
+
+- **Session-file recovery for crash-killed workers (P1-1)** — workers now spawn with
+  deterministic `--session-id`/`--session-dir` (files live under the run's artifacts, not
+  `~/.pi`). On signal death (`exitCode === null`) the settle path tail-replays the worker's
+  session JSONL (SDK `parseSessionEntries`/`migrateSessionEntries`, torn-tail tolerant, 5s
+  bounded) and surfaces the last complete assistant message as a new `"session"` result
+  source — ranked below live captures, above stdout/stderr noise — plus a provenance sidecar
+  `results/<task>.session-recovery.json`. Config `runtime.sessionRecovery` (default **on**),
+  env `PI_CREW_SESSION_RECOVERY`.
+- **Worker auto-compaction observability (P2-2)** — the injected prompt-runtime extension now
+  listens for the SDK `session_before_compact` event and emits `worker.session_before_compact`
+  (scalar payload) through the worker-events channel. Hook is infra-proven in `-p` mode but
+  not yet live-fired at threshold (docs + host-analog evidence).
+- **Experimental RPC transport prototype (P2-3)** — new `src/runtime/rpc/`: strict-LF JSONL
+  frame client on SDK protocol types, `extension_ui_request` drain policy (count+drop), dialog
+  auto-answer policy `cancel`|`block` (auto-confirm deliberately absent). Config
+  `runtime.workerTransport: 'stdio' (default) | 'rpc'` + env `PI_CREW_WORKER_TRANSPORT` /
+  `PI_CREW_RPC_DIALOG_ANSWER`. The seam returns a structured not-implemented result until the
+  live-fire integration phase — default path is byte-identical.
+
+### Changed
+
+- **Surface TUI spawns pin `--tui-mode regular` (P0-1)** — Pi 1.0.0 defaults the TUI to
+  fullscreen, which silently empties the scrollback capture path (`capture-pane -S`) that
+  `readScreen` always uses. The pin restores pre-1.0.0 behavior for surface panes.
+- `parseRuntimeConfig` now emits `runtime.sessionRecovery` and `runtime.workerTransport`
+  (F19-1 discipline — both keys were previously parse-dead).
+- Legacy `@mariozechner/pi-coding-agent` fork resolution now warns once per process (staged
+  deprecation; canonical `@earendil-works` path unaffected).
+
+### Added — deep-learn round 3 execution (see docs/reviews/pi-1.0.0-deep-learn-r3-2026-10-03.md)
+
+- **Compaction-surviving worker header (R3-1)** — the run-static worker context (protocol
+  block, mailbox contract, workspace structure) moved from the user message to the
+  `--append-system-prompt` channel (byte-preserving move; probe-verified coexistence with
+  AGENTS.md discovery). Auto-compaction summarizes the user-message span but never the system
+  prompt, so long runs keep exactly the context that must not be lost. Prompt breakdown now
+  reports `userPrompt`/`userAppend` channels separately.
+- **Worker provenance self-report (R3-2)** — the handoff template's new `### Provenance`
+  section asks workers to echo their `PI_SESSION_ID`/`PI_SESSION_FILE`/`PI_MODEL`/`PI_PROVIDER`/
+  `PI_REASONING_LEVEL` env — model provenance without log parsing.
+- **Hermetic worker spawns (D5/R3-19)** — headless workers now spawn with `--no-extensions`
+  (default on; off-switch `runtime.hermeticWorkers` / `PI_CREW_HERMETIC_WORKERS`). Kills the
+  ~1.37 s/spawn ambient extension stack and the ambient untrusted tool surface (8 direct-exposure
+  MCP tools). Explicit `-e` prompt-runtime injection and `--skill` flags unaffected; surface TUI
+  panes keep the ambient stack.
+- **Trust pin (D1/R3-3)** — worker spawns pin `--no-approve` unconditionally: worker trust is
+  machine-state-free (no ambient `~/.pi/agent/trust.json` dependence). Project trust does not
+  gate write capability and AGENTS.md discovery is unaffected (probe-verified); surface TUI
+  spawns keep the interactive prompt.
+
+### Fixed
+
+- **Session args per-flag idempotency (live battery find)** — partial builder forwarding
+  (manifest `sessionId` without `sessionDir`) made the both-or-nothing guard self-disarm the
+  full activation: `--session-id` went out but `--session-dir` never did, so worker session
+  files silently landed in the cwd-keyed default dir and crash recovery read the wrong place.
+  Each missing flag is now filled independently; verified end-to-end by killing a real worker
+  (SIGKILL mid-tool) and recovering its last complete assistant message from the per-worker
+  artifacts dir in ~1s.
+- **engines floor raised to Node `>=22.19.0`** — aligns pi-crew with the SDK's own declared
+  floor (previously `>=22.0.0` let Node 22.0–22.18 users run an SDK that declares itself
+  unsupported).
+
+### Migration notes
+
+- **Hermetic worker spawns are ON by default** (`runtime.hermeticWorkers`): headless workers
+  no longer load ambient user extensions/MCP —
+  set `PI_CREW_HERMETIC_WORKERS=0` or `runtime.hermeticWorkers: false` to restore the old
+  behavior if a worker genuinely needs ambient tooling.
+
+### Fixed / removed
+
+- Dead `persist: true` widget option removed (call site + compat strip + type alias).
+- `--provider` without `--model` now has an argv contract test across every builder path
+  (Pi 1.0.0 turned the silent ignore into an error).
+
+
+### Security
+
+- **fast-uri 3.1.2 → 3.1.8** (transitive of `ajv`, shipped runtime tree): patched
+  the 9 GHSA advisories (host-confusion / SSRF-via-URI-parsing family). pi-crew
+  only compiles its own static JSON schemas with ajv, so exploitability was low,
+  but the package ships to users, so the lockfile bump is user-facing hardening.
+- Known-accepted (dev-tree only, NOT shipped — `npm pack` carries 0 copies):
+  `brace-expansion@5.0.9` nested under `@earendil-works/pi-coding-agent` →
+  `minimatch@10.2.6` carries 3 high ReDoS/stack-exhaustion advisories. Kept at
+  5.0.9 because npm's resolver deterministically re-nests 5.0.9 for this scoped
+  position (overrides, cache-clean, clean-room regen, and lockfile surgery all
+  fail or regress on plain `npm install`; only `npm ci` would hold the pin).
+  CI runs `npm ci --no-audit` and has no `npm audit` gate; revisit when the
+  SDK bumps minimatch.
+
 ## [0.11.6] — SDD-3/4 upgrade waves, W-E/W-I, small-wins, Pi 1.0.0 compat, GH #61 fix (2026-10-03)
 
 ### fix(extensions): GH-061 — normalize directory `pi.extensions` entries to entry-file identity (child workers double-load)