Skip to content

v0.7.1: 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 25 Oct 15:10
4d97d35

SLICE v0.7.1 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/pi-context-compaction@extension-v0.7.1

Start a new persistent text session and run /compaction-doctor to check it without calling a model. Source tag v0.7.1 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/pi-context-compaction@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 118 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: 4d97d35. Preview runtime: stock-preview+src.1a4f2d4911b1a0a3. Resident runtime keeps its v0.3.0 fingerprint.

Usage and recovery · Validation

Changes

v0.7.1 is the first extension built on the v0.7.0 host-neutral core, and the first release under the SLICE name. It adds official Pi 1.4.0 as the primary host beside 1.3.0, 1.2.0 and 1.1.0 and behaves as extension-v0.6.0 did: the core lifts were byte-identical on scripted inputs, and the checkpoint schema, the source-hash format, the resident build fingerprint and the evaluation pin are unchanged. The core's import gate now also refuses module loads it cannot verify. Every result is offline, on official Pi installations with loopback services; real-provider behavior is not part of this release.

Added

  • Official Pi 1.4.0 is supported and becomes the primary host, beside 1.3.0, 1.2.0 and 1.1.0. Its extension API declarations, extension runner and session storage match 1.3.0, and it installs the same seven runtime packages, without chord. Stock-Pi acceptance runs on all four hosts: each older host compacts a checkpoint written on 1.4.0, and 1.4.0 reopens the result. Pi 1.4.0's summary changes, the ignored reserveTokens and custom instructions on a split turn, concern Pi's own summarizer, which the extension does not call. Its persistent omission of a truncated attempt's tool results arrives as context edits, which the extension already validates in full before the next request.

Changed

  • The project is now called SLICE, Source-Linked Indexed Compaction of Everything, in the documentation, the release notes and the package description, and the README is rewritten for first-time readers. Its commit diagram is redrawn for the extension's checks and disk readback, and the opening illustration no longer says that checkpoints are written only on a manual /compact. The repository, the install source, the package name pi-context-compaction-preview, the /compaction-* commands, the pi-context-memory.json configuration file and stored checkpoint identifiers keep their names, so existing installations and sessions need no change.

Fixed

  • The core's import gate checked a dynamic import only when its specifier was a literal, so import(name) or an interpolated template passed unchecked. Such a specifier now fails the gate with its location and expression. A regression covers both forms beside the literal ones that stay allowed.
  • The core's import gate never saw a module loaded by name through node:module's createRequire, through process.getBuiltinModule, which needs no import at all, or through a bare require. node:module now fails the gate, and require(x) and process.getBuiltinModule(x) are checked like import(x), so a specifier that is not a literal fails closed. Nothing in the core used any of these routes. A regression plants each form beside a builtin that stays allowed.

Security

Maintenance

  • The Publish extension preview workflow recognizes a source release. A v* tag whose version differs from the extension package it builds, while that package version is already published, now ends after the build with a notice and publishes nothing, instead of running stock-Pi acceptance and failing at the publish step as v0.7.0 did. A tag beside an unpublished package version still fails, before any official Pi is installed.
  • The stock-Pi scenarios add tool-loadout. With arm B off, the provider is offered context_history and not context_note in a fresh session, after a restart and after /tree navigation; a branch that called context_note while B was on is offered it again after a restart; and a session started before the extension was installed stays usable without context_note. Pi 1.4.0 activates an extension tool a restored branch never recorded unless the tool registers with defaultActive: false, which context_note does while B is off, so the v0.5.3 saving of about 1,209 tokens per request holds. The case passes on official Pi 1.4.0 and 1.3.0.