Repository navigation
v0.7.5: SLICE extension preview for Pi 1.4.0, 1.3.0, 1.2.0 and 1.1.0
Pre-releaseSLICE v0.7.5 supplies an ordinary extension for unmodified official Pi 1.4.0, 1.3.0, 1.2.0 and 1.1.0.
Install this release from npm, then restart Pi:
pi install npm:slice-pi@0.7.5Start a new persistent text session and run /compaction-doctor to check it without calling a model. To follow later releases, install npm:slice-pi without a version and update only this package with pi update --extension npm:slice-pi. A plain pi update updates Pi itself. The same package is on Git as the fixed tag extension-v0.7.5; source tag v0.7.5 selects the development monorepo, not the package:
pi install git:github.com/youxi-huang/slice@extension-v0.7.5An installation from Git keeps working and updating through extension-preview. To move it to npm, run pi remove git:github.com/youxi-huang/slice and install from npm; sessions and settings carry over.
OpenCode and DSH get SLICE's context_history from npm too, with no build. For OpenCode, add the package to plugin in opencode.json and restart it:
{ "plugin": ["slice-opencode@0.7.5"] }For DSH, add it to a profile built on DSH's base bundle; the package enables itself there:
dsh plugin --profile <profile> add slice-dsh@0.7.5Before publication each package was installed by name from a loopback registry on official OpenCode 1.19.4 and 1.19.5 and DSH 0.2.1-rc.3 and 0.2.1-rc.5, where a scripted session compacted natively and read its original history back. Both are retrieval only: compaction stays the host's.
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 150 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: dcdb270. Preview runtime: stock-preview+src.b0f389ab614f8cf3. Resident runtime keeps its v0.3.0 fingerprint.
Usage and recovery · Validation
Changes
v0.7.5 publishes SLICE on npm for all three hosts: the Pi extension as slice-pi, and the OpenCode and DSH history packages as slice-opencode and slice-dsh. The Pi extension compacts as v0.7.4 did; its one runtime change is which copy the duplicate notice keeps. This release changes no checkpoint format, resident build fingerprint or evaluation pin.
Added
- From 0.7.5 each release is published on npm as well as on Git, so none of the three hosts needs a clone or a build. Pi installs the extension with
pi install npm:slice-pi. OpenCode installsslice-opencodeat start once it is listed underplugininopencode.json. DSH installsslice-dshwithdsh plugin --profile <profile> add slice-dsh. The Git package and theextension-previewbranch stay, and the OpenCode and DSH packages are also taggedopencode-v<version>anddsh-v<version>for installation without npm. Before anything is published, the release workflow installs the OpenCode and DSH packages by name from a loopback registry on official OpenCode 1.19.4 and 1.19.5 and DSH 0.2.1-rc.3 and rc.5, where a scripted session compacts natively twice and reads its history back, and installs, runs and removes the Pi package by name on every supported Pi. All three are published with npm provenance.
Changed
- The Pi package is named
slice-pi, its npm name, on Git as well; it waspi-context-compaction-preview. Pi identifies a Git package by its address, so existing installations keep loading and updating. When an npm copy and a Git copy are both loaded, the duplicate notice keeps the npm one and names the Git one to remove; a second npm copy is named without its version,pi remove npm:slice-pi. - The DSH package declares a DSH bundle, so
dsh plugin addenables it with no hand-addedslice-historyrow in the profile'scordis.patch.yml. A profile that carries that row from an earlier build must drop it, since the tool refuses to register twice.dsh plugin --profile <profile> remove slice-dshremoves the package and deselects its bundle. - The OpenCode package declares
engines.opencode>=1.19.4 <2.0.0, which OpenCode checks before it loads an npm plugin. Both packages carry a README of their own.
Fixed
- The DSH package installs on DSH 0.2.1-rc.4 and rc.5. Its peers named rc.3 alone, and DSH checks them before installing and at startup, so it refused the package on any later release. They now admit rc.3 and every later 0.2.x release; nothing the adapter uses changed between rc.3 and rc.5.
Maintenance
scripts/context-memory-version.mjsholds the release version every package reads. CI gains anadaptersjob that runs the adapter checks and the install acceptance,scripts/context-memory-adapters-acceptance.mjs.context-memory-host-run.mjs --install registryinstalls an adapter by package name from a loopback registry,scripts/context-memory-loopback-registry.mjs. The release workflow gainsid-token: writefor npm trusted publishing and a 30-minute limit. The first npm publication uses anNPM_TOKENsecret, deleted once each package has a trusted publisher, as the extension guide's maintainer section describes.