release: pi-codex-goal 0.2.0

Raise the supported Pi floor to 0.84.0, migrate emitted API contracts, and validate the packed extension with isolated Pi 0.84 runtime and tmux goal flows.

Author: fitchmultz

AGENTS.md

@@ -17,7 +17,7 @@ pi install -l npm:pi-codex-goal
 pi install -l https://github.com/fitchmultz/pi-codex-goal@vX.Y.Z
 ```
 
-Those write duplicate package entries under `.pi/` for the current project, causing `get_goal`, `create_goal`, and `update_goal` tool-registration conflicts with the global local-checkout install. For install-path release verification, use an isolated temp project/config directory or remove the project-local entries immediately after the check. With Pi 0.79+ project trust, pass `--approve` for isolated project-local package install/list/non-interactive smoke commands when those commands must load `.pi/settings.json`. If conflicts appear, inspect `pi list --approve` and `.pi/settings.json`, then remove any project-local `pi-codex-goal` npm/GitHub installs so only the global local-checkout package remains active.
+Those write duplicate package entries under `.pi/` for the current project, causing `get_goal`, `create_goal`, and `update_goal` tool-registration conflicts with the global local-checkout install. For install-path release verification, use an isolated temp project/config directory or remove the project-local entries immediately after the check. On Pi 0.84.0 or later, pass `--approve` for isolated project-local package install/list/non-interactive smoke commands when those commands must load `.pi/settings.json`. If conflicts appear, inspect `pi list --approve` and `.pi/settings.json`, then remove any project-local `pi-codex-goal` npm/GitHub installs so only the global local-checkout package remains active.
 
 ## Verify before finishing
 
@@ -50,4 +50,4 @@ The required gate runs the full suite plus a real model-backed goal-tool smoke o
 | Recovery | `recovery*.ts` |
 | Domain | `state.ts`, `types.ts`, `goal-persistence.ts` |
 
-Current structural audit and remediation record: `docs/CODEBASE_AUDIT.md`.
+Historical 0.1.33 structural audit and remediation record: `docs/CODEBASE_AUDIT.md`.

CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## 0.2.0 - 2026-08-06
+
+- Raise the minimum supported Pi version to 0.84.0 and pin the development/type-validation baseline to the exact 0.84.0 release.
+- Align the SDK runtime smoke with Pi 0.84.0's public `Agent.streamFunction` API and use current pi-ai root exports instead of the compatibility subpath.
+- Align the extension test harness with Pi 0.84.0's `registerMarkdownTransformer()` and read-only `scopedModels` context contracts, and serialize the mutating goal tools because they share one session state machine.
+- Audit the full repository against every Pi 0.84.0 breaking change; the extension does not use JSON/RPC streaming, model-auth forwarding, dynamic providers, pi-agent-core harness sessions, custom harness filesystems, or remote sessions, so those migrations require no runtime compatibility code.
+- Require Pi 0.84.0 or later in install and compatibility documentation while retaining optional wildcard Pi peers as required by Pi package loading.
+- Refresh the development lockfile, including the patched `protobufjs` 7.6.5 transitive dependency.
+
+### Validation
+
+- Ran `npm run verify` and a clean public-registry `npm ci && npm run verify` under Pi 0.84.0: `tsc --noEmit`, 6 platform-smoke checks, and 333 regular tests passed in each run.
+- Ran `npm audit --omit=optional` with no vulnerabilities and `npm publish --dry-run --ignore-scripts --registry=https://registry.npmjs.org`; both passed.
+- Packed the release and installed it project-locally with an isolated Pi 0.84.0 executable/config, verified extension and prompt discovery over RPC, and completed a tmux model-backed `/goal` flow that created and read an exact file, called `get_goal`, called `update_goal`, and rendered the final fullscreen `Goal achieved` status.
+- The Crabbox macOS/Ubuntu/native-Windows matrix could not start on this shared host: its doctor stopped before every product suite because Crabbox, model-auth environment, localhost SSH, and Parallels `prlctl` were unavailable. No Crabbox product test ran or failed; the matrix remains required and unchanged for capable environments.
+
 ## 0.1.39 - 2026-07-28
 
 - Pause active goals when a hidden continuation run only calls `get_goal` / namespaced `*__get_goal` and makes no actionable progress, so blocked status-inspection loops stop and surface `/goal resume` attention instead of spinning forever (#47).

README.md

@@ -12,6 +12,8 @@ Goal state is stored in pi session custom entries, so it follows session history
 
 ## Install
 
+Requires Pi 0.84.0 or later.
+
 Install from npm:
 
 ```sh
@@ -45,7 +47,7 @@ pi install .
 
 On this maintainer machine, the active install is a global/user package that already points at this checkout; do not also leave a project-local install under this repository's `.pi/` settings. Duplicate local and global installs both try to register `get_goal`, `create_goal`, and `update_goal`, which causes tool-registration conflicts. For install-path release checks, use an isolated temp project/config directory or remove the project-local entry immediately after the check.
 
-Compatibility note: this package is tested against the current pi release during each package update. The current source tree targets Pi 0.80.10 on Node 24 for the next package release. The latest published npm artifact remains the reproducible source of truth for its own published version's metadata. Pi-bundled runtime packages remain optional wildcard peers, so npm peer ranges do not hard-block users from trying newer pi releases; runtime behavior is only verified against the tested baseline until a follow-up package release confirms it.
+Compatibility note: this package supports Pi 0.84.0 or later on Node 24. The latest published npm artifact remains the reproducible source of truth for its own published version's metadata. Pi-bundled runtime packages remain optional wildcard peers as required by Pi package loading; the support floor is declared here and validated by the source tree's exact Pi 0.84.0 development dependencies.
 
 Release note: npm installs and pinned GitHub tags are the reproducible release artifacts. Installing from the repository default branch can include unreleased changes that will ship in a future package release, even when `package.json` still identifies the latest published version.
 
@@ -81,10 +83,10 @@ npm run smoke:platform:all
 
 `smoke:platform:all` runs the doctor before any target suite.
 
-That local gate runs `npm run verify`, packs the package, installs the packed package into a clean pi project, checks `pi list`, and runs a real model-backed goal-tool smoke on macOS, Ubuntu Linux, and native Windows. Pi 0.79+ project trust is handled explicitly with `--approve` inside the isolated smoke projects so project-local package settings and the packed extension load in non-interactive runs. The runtime smoke defaults to `zai/glm-5.2`; override it with `PLATFORM_SMOKE_MODEL` and configure forwarded auth env vars with `PLATFORM_SMOKE_AUTH_ENV`. Setup and artifact details: [docs/platform-smoke.md](docs/platform-smoke.md).
+That local gate runs `npm run verify`, packs the package, installs the packed package into a clean pi project, checks `pi list`, and runs a real model-backed goal-tool smoke on macOS, Ubuntu Linux, and native Windows. Pi 0.84.0-or-later project trust is handled explicitly with `--approve` inside the isolated smoke projects so project-local package settings and the packed extension load in non-interactive runs. The runtime smoke defaults to `zai/glm-5.2`; override it with `PLATFORM_SMOKE_MODEL` and configure forwarded auth env vars with `PLATFORM_SMOKE_AUTH_ENV`. Setup and artifact details: [docs/platform-smoke.md](docs/platform-smoke.md).
 
 Project agent notes and module map: [AGENTS.md](AGENTS.md).
-Current structural audit and remediation record: [docs/CODEBASE_AUDIT.md](docs/CODEBASE_AUDIT.md).
+Historical 0.1.33 structural audit and remediation record: [docs/CODEBASE_AUDIT.md](docs/CODEBASE_AUDIT.md).
 
 ## Interactive smoke tests
 

docs/platform-smoke.md

@@ -76,14 +76,14 @@ Each required target runs `platform-build` and `goal-runtime-smoke`.
 4. Run `npm pack`.
 5. Create a clean target-local pi project.
 6. Install the packed tarball into that project with `npm install --no-save`.
-7. Run `pi install -l ./node_modules/pi-codex-goal --approve` from the clean project so Pi 0.79+ can read and write project-local package settings for this isolated command.
+7. Run `pi install -l ./node_modules/pi-codex-goal --approve` from the clean project so supported Pi 0.84.0-or-later hosts can read and write project-local package settings for this isolated command.
 8. Run `pi list --approve` and assert `pi-codex-goal` is registered from the packed install.
 9. Assert the smoke never used the source shortcut `pi -e .` or `pi --extension .`.
 
 ### `goal-runtime-smoke`
 
 1. Re-pack and install the package into a clean target-local pi project.
-2. Run real `pi --approve --model <model> -p <prompt>` against that packed install so non-interactive Pi 0.79+ loads the isolated project-local package settings.
+2. Run real `pi --approve --model <model> -p <prompt>` against that packed install so non-interactive Pi 0.84.0-or-later hosts load the isolated project-local package settings.
 3. Prompt the model to call the actual goal tools, create a marker file, verify it with the built-in `read` tool, call `update_goal`, and confirm completion.
 4. Capture pi stdout/stderr and session JSONL.
 5. Assert the final marker, verified file, `pi-codex-goal` custom entries, built-in `read` tool evidence, and complete goal status.
@@ -142,7 +142,7 @@ The suites record failures as artifacts before reporting failure so the host can
 - Keep `platform-build` behavior in the shared Node orchestrator; native Windows may use only a thin PowerShell wrapper to launch it.
 - Run the repository's existing validation command on every required target.
 - Test the packed package, not `pi -e .`.
-- Pass `--approve` for isolated project-local package smoke commands and non-interactive runtime smokes; Pi 0.79+ otherwise skips project-local settings and packages when no saved trust decision exists.
+- Pass `--approve` for isolated project-local package smoke commands and non-interactive runtime smokes; Pi 0.84.0-or-later hosts otherwise skip project-local settings and packages when no saved trust decision exists.
 - Include a real model-backed pi run so release claims are not based on unit tests alone.
 - Assert built-in `read` evidence in the model-backed runtime smoke so post-tool goal completion stays covered.
 - Keep project-specific defaults in `platform-smoke.config.mjs`; use environment variables only for local overrides.