v1.1.1

Docs-and-packaging release. No behaviour change from 1.1.0.

Changed

• The repository moved to sudo-holla/pi-rcompact in PR #4, but the v1.1.0 tag was cut before that landed, so the published tree, npm tarball and README install pins still recorded the old address. v1.1.1 is main re-published so every artifact carries the new path.
• version.ts and the README pins moved with the package version, so /rcompact, the doctor, the request-source label and the documented install line report 1.1.1.

No behaviour change

• No logic, test, workflow or capability change. Nothing to reconfigure; existing settings carry over untouched.

Verification

npm run typecheck exit 0; full npm test green (166 unit checks plus real Pi SDK integration in both payload-hook orders, budget / normal-recovery / headroom integration, upgrade test, screenshot integration); compatibility-check PASS on Pi 1.3.0; CI passed on Node 22 + 24, typescript, actions and the newest-Pi-SDK advisory. Fake loopback provider only, no production writes.

Install

pi install git:github.com/sudo-holla/pi-rcompact@v1.1.1 · commit a76fe8422f7a89062a16bd54c8673d45b2c0520e · tag object 39212618dd9d55f254238f9b42b611bd79bd3f83 · 26-file tarball.

v1.1.0

Added

• Configurable engine capabilities (betterCompaction.engineCapabilities): engine-dependent behaviour — reasoning-budget bound, focused-extraction instruction, prefill-capacity recovery, request-capture affinity, output-headroom guard and restarting-engine error classification — is now granted per provider id or provider/modelId glob instead of by a built-in id comparison, so an engine this project has not been developed against can be enabled from configuration. The built-in table reproduces the previous grants, so existing setups behave identically. /rcompact reports the capabilities granted to the current model.
• Every runtime module is asserted to be in the published tarball; the new module was missing from it before that check caught it.

Compatibility

Capability grants decide what an engine supports, not where a request is sent: generation-time parameters and tokenizer preflights stay loopback-http://-only, request capture stays OpenAI-completions-only.

Install

pi install git:github.com/RickyHolland/pi-rcompact@v1.1.0 · commit c43e2e2b43ddb760e6a6a70962adaee2f5710b8c · tag object 8f752320d9c6a89c85546e9c938d79d867826ac9 · 26-file tarball.

Superseded by v1.1.1. The install line above names the pre-move repository path; behaviour is identical, so re-pin to v1.1.1 to get artifacts that match the current address.

rcompact v1.0.4 — neutral identifiers

rcompact v1.0.4

Cache-aware context compaction for Pi. Request markers and persisted identifiers now derive from the /rcompact command name and are declared in one place.

Changed

• Prompt text. The evidence-review sentinel in the verification prompt reads RCOMPACT EVIDENCE REVIEW instead of carrying a project-prefixed marker into every request.
• Persisted identifiers now derive from the /rcompact command name: strategy rcompact, entry types rcompact-report / rcompact-review, telemetry directory telemetry/rcompact/, and rcompact.* for the versioned global Symbol.for keys. They are declared once in identifiers.ts, and a check in identifiers.test.ts fails if runtime code hard-codes a persisted identifier instead of importing it.
• License. The project-side copyright line is now Copyright (c) 2026 pi-rcompact contributors; the upstream project's own notice is unchanged.

Upgrade effect (read this before pinning)

Renamed persisted identifiers are a storage contract, so records written by earlier builds are no longer recognised by name:

• old report/review entries stay in the transcript and render as plain custom entries (no data loss);
• a checkpoint created before the rename is attributed to native compaction on the next run, so a pre-existing rejected-review durability check will not fire for it;
• telemetry written before the rename stays in the previous directory — nothing reads telemetry back, so it is inert history.

Kept for compatibility: the betterCompaction settings section, the /bc command alias, reading the earlier better-compaction strategy value, and rendering the earlier better-compaction-report entry type.

Verifying this release

• tag object: b5269c25a6b6b6db86655c225baa5a9d25500b26
• commit: cc4d57eca555e16215a53f61dd4576e740676b9c

git ls-remote https://github.com/RickyHolland/pi-rcompact refs/tags/v1.0.4   # -> b5269c25a6b6
git cat-file -p b5269c25a6b6                                                     # -> object b5269c25a6b6, commit cc4d57eca555

Install pinned to the tag:

pi install git:github.com/RickyHolland/pi-rcompact@v1.0.4

main is protected: CI must pass, changes arrive through a merged pull request, direct pushes are rejected, force-push and deletion are blocked, and a ruleset blocks deleting released v* tags. Passing CI is not the same promise as being released, so keep pinning the tag.

Verification

npm run typecheck clean · node run-tests.mjs 154/154 · npm test exit 0 (7 suites, both payload-hook orders, zero extension errors, fake loopback provider only) · npm pack --dry-run 25 files including the runtime identifiers.ts.