-
v1.6.4 — fork tool actually loads; pi 0.83.0 audited clean
Publish Docker Image / resolve-versions (push) Successful in 5sLint / hadolint (push) Successful in 13sLint / actionlint (push) Successful in 15sPublish Docker Image / base-decide (push) Successful in 7sPublish Docker Image / build-base (push) Successful in 41m24sPublish Docker Image / smoke-studio (push) Successful in 5m11sPublish Docker Image / smoke (push) Successful in 12m23sPublish Docker Image / build-variant-studio (push) Successful in 22m46sPublish Docker Image / build-variant (push) Successful in 22m58sPublish Docker Image / update-description (push) Successful in 6sPublish Docker Image / promote-base-latest (push) Successful in 13sreleased this
2026-07-30 01:10:19 +02:00 | 5 commits to main since this release- fix: pi-fork registration guard inspected the whole settings.json and matched
the pi-fork config block the template merge plants, sopi install /opt/pi-fork
never ran. The fork tool has been absent since v1.0.0. Guard now checks
packages[] via jq; existing volumes self-heal on next start. - fix: both test suites asserted the bug as green (same whole-file grep); now
assert against packages[]. - change: pi 0.82.1 -> 0.83.0. Upstream Breaking Change (TypeBox 1.3.7) cannot
reach any baked extension; extension .d.ts surface diffs clean, pi-fork's six
child CLI flags present, SESSION_VERSION unchanged at 3. No pin needed. - change: settings template defaults to Claude Opus 5.
- docs: pi-extensions skill now documents the mechanism behind fork boundary
violations (full parent-transcript inheritance) and corrects two wrong claims.
Downloads
- fix: pi-fork registration guard inspected the whole settings.json and matched