Skip to content

v0.7.2: SLICE extension preview for Pi 1.4.0, 1.3.0, 1.2.0 and 1.1.0

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 26 Oct 10:00
738722a

SLICE v0.7.2 supplies an ordinary extension for unmodified official Pi 1.4.0, 1.3.0, 1.2.0 and 1.1.0.

Install this release's extension package (a fixed package tag) from your terminal, then restart Pi:

pi install git:github.com/youxi-huang/slice@extension-v0.7.2

Start a new persistent text session and run /compaction-doctor to check it without calling a model. Source tag v0.7.2 selects the development monorepo, not the package. To follow later previews instead, install the moving extension-preview branch in place of the tag and update only this package with pi update --extension git:github.com/youxi-huang/slice@extension-preview. A plain pi update updates Pi itself.

This pre-release supports manual /compact and Pi's threshold compaction after completed text turns, source-linked history retrieval and explicit disk-confirmed failure recovery. In the sessions it handles, overflow recovery still requires explicit /compact, and background cache warming is paused. Sessions it never protected and cannot check, such as ones with native checkpoints, images or another Pi version, are left to Pi without a failure marker. Other checkpoint formats, parent-history grants, attachments, concurrent writers and Windows are outside its verified scope.

Ordinary Agent retries after transient provider failures are supported, including partial-response connection drops. Existing retry-related blocks and text-only context-overflow failures can use explicit /compact recovery when sufficient completed source history exists. Arbitrary context edits and unfinished tool-call omissions remain unsupported.

Optional preparation has two arms, both disabled by default: A prepares with the configured writer; B merges data-only work notes from the session model. A validated candidate can commit its covered prefix without a writer call while every later original stays verbatim. B carries covered user messages in full and falls back to the configured writer when they do not fit. Every writer call is journaled, including cancelled or discarded preparation and unknown usage. These are experimental paths; real-provider pause, total cost, cache behavior and recovery benefits remain unproven.

Validation: this publication run passed 122 stock-Pi package and lifecycle checks on official Pi 1.4.0, 1.3.0, 1.2.0 and 1.1.0 and the full default-settings scenario suite on Pi 1.4.0 with strict acceptance and no performance exceptions or known gaps. Scenario evidence is bound to this exact package and source commit; the 50 ms request-overhead target and checkpoint-growth bound are required checks. Focused, security and frozen evaluator checks also remain required on final main. Services are synthetic and loopback only; no real-provider quality, latency or interactive TUI claim is made.

Source commit: 738722a. Preview runtime: stock-preview+src.ae7bb53ee105c16a. Resident runtime keeps its v0.3.0 fingerprint.

Usage and recovery · Validation

Changes

v0.7.2 moves the repository and its install source to youxi-huang/slice, and a second installed copy no longer pauses the session: a copy that finds another one loaded stands aside, so only one compacts. The extension otherwise compacts as v0.7.1 did, and the checkpoint schema, the source-hash format, the resident build fingerprint and the evaluation pin are unchanged. The source tree also gains retrieval-only previews for DSH and OpenCode, built from source and not published. Results are offline, on official Pi installations with loopback services, except GitHub's redirect, which was tested against the renamed repository; real-provider behavior is not part of this release.

Added

  • Source-only retrieval previews for DSH 0.2.1-rc.3 and OpenCode 1.19.4. Each adds one context_history tool that searches and reads the current session's original records through the host's public storage API and the shared core, citing native event and part IDs, with bounded pages, continuation cursors and source-change checks. They keep no second history database and refuse forked or seeded sessions. Neither writes SLICE checkpoints yet: DSH's pinned persistence contract cannot carry a required external checkpoint record, and OpenCode keeps its native compactor.

Changed

  • The repository moved from youxi-huang/pi-context-compaction to youxi-huang/slice, and the install source is now git:github.com/youxi-huang/slice. GitHub redirects the old address, so existing installations keep loading and updating, and pi update and pi remove still name the address they were installed from. Pi counts the two addresses as two packages: moving means removing the old address and installing the new one, never installing both, since Pi then loads both copies. The release script, the package's repository and homepage, and the install commands in the README and the preview guide follow the new name. The package name, the commands, the configuration file and stored checkpoints are unchanged.
  • The README now shows how to build and load the DSH and OpenCode previews. Both sets of steps were run on the official hosts.

Fixed

  • Two installed copies of the extension, from two addresses or two scopes, no longer pause the session at their next compaction. Pi loads both and runs both copies' handlers, so each wrote its own checkpoint for one attempt and the commit could not be confirmed. A copy now finds the others in Pi's command list: one compacts, the first loaded unless a copy of v0.7.1 or earlier is loaded, since that one cannot stand aside, and every other copy stands aside, says once which copy compacts and names the pi remove command that keeps one, preferring the youxi-huang/slice address. /compaction-doctor:1 and :2, as Pi names the commands of two copies, list both. Two copies of v0.7.1 or earlier still conflict. On official Pi 1.4.0, 1.3.0, 1.2.0 and 1.1.0 a v0.7.2 copy installed after or before v0.7.1 leaves one writer request per compaction and a committed checkpoint; the stock-Pi acceptance gains the case with two v0.7.2 copies.

Security

  • DSH 0.2.1-rc.3 pins zod 4.4.3, affected by GHSA-mrhx-c7xc-m3w5. A root override lifts the new development dependencies to 4.6.7, so npm audit still reports no advisories. The OpenCode adapter imports zod 4.6.7 directly rather than the plugin package, whose V2 runtime it does not use.
  • Remove the unused upstream sandbox example, whose @anthropic-ai/sandbox-runtime dependency held zod at 3.25.76, affected by GHSA-mrhx-c7xc-m3w5. No zod 3 release carries the fix, and even the latest sandbox runtime requires zod 3. With the example gone, every remaining dependent accepts zod 4, so the root lockfile moves zod to 4.6.7 and npm audit reports no advisories. zod was never in the coding-agent install lock or the independent Pi extension; before the new OpenCode adapter, it arrived only through the example, as an optional peer of the provider SDKs and as a dependency of the upstream evaluation tools.

Maintenance

  • Regressions for the v0.7.2 install-source move show, on Pi's real package and settings managers over a local repository, what happens when the old address is replaced, when both addresses are installed and when either scope is changed: configuration and sessions survive, checkpoints still validate, and a pending or failed compaction stays guarded through the reinstall. The same cases run against an official Pi on request. GitHub's redirect itself was tested after the rename, on each official host.
  • CI runs its full pipeline on every push to main, including a merge that changes Markdown documents alone; only such a pull request still skips it. Publication accepts a tagged commit only after its verify check concluded success, and a skipped job concludes skipped, so a release tagged on a documentation-only merge would have failed at its last step, after the whole stock-Pi acceptance had run. A regression runs the workflow's scope step on a documentation-only commit for a pull request, a push and a manual run.