pi-memory-evolution 0.2.1 → 0.2.2

package/CHANGELOG.md

@@ -2,6 +2,19 @@
 
 All notable changes to pi-memory-evolution are documented here.
 
+## [0.2.2](https://github.com/btnalit/pi-memory-evolution/compare/v0.2.1...v0.2.2) (2026-09-08)
+
+
+### Bug Fixes
+
+* support npm 12 pack output and gate CLI compatibility ([#7](https://github.com/btnalit/pi-memory-evolution/issues/7)) ([4fde298](https://github.com/btnalit/pi-memory-evolution/commit/4fde29844b6d2c9e9497a656f75d8655e812d4c6))
+
+
+### Maintenance
+
+* **deps-dev:** bump the development-minor-patch group across 1 directory with 3 updates ([#9](https://github.com/btnalit/pi-memory-evolution/issues/9)) ([03ef2be](https://github.com/btnalit/pi-memory-evolution/commit/03ef2beed637cfaa5c9dae22b26060c6f330d754))
+* **deps-dev:** bump typescript from 5.9.3 to 7.0.2 ([#5](https://github.com/btnalit/pi-memory-evolution/issues/5)) ([dc97e2c](https://github.com/btnalit/pi-memory-evolution/commit/dc97e2c3306a0c1b07c34675d1eebaa7c73aaa8d))
+
 ## [0.2.1](https://github.com/btnalit/pi-memory-evolution/compare/v0.2.0...v0.2.1) (2026-09-08)
 
 

package/docs/releasing.md

@@ -9,6 +9,8 @@ Use Conventional Commit PR titles, such as `fix: retain work evidence` or
 
 - Node 22.19.0 and Node 24: typecheck, regression/release-policy tests, package and
   automation assertions, and an npm audit that fails on high/critical findings.
+- Node 24 with explicit npm 10 and 12: checks, native installation and package builds;
+  both npm compatibility lanes are mandatory parts of the gate.
 - Node 24: native Pi installation tests and real-host/fake-model integration.
 - Workflow syntax checks with a checksum-pinned actionlint binary.
 - Build an npm tarball, `SHA256SUMS` and a source-commit/integrity manifest. Pi loads
@@ -45,6 +47,11 @@ Release Please uses the built-in `GITHUB_TOKEN`, not a personal GitHub credentia
 Because events generated by that token do not start normal push/PR workflows,
 it explicitly dispatches CI for its same-repository release PRs. Publication is a
 job in the same workflow, not a separate listener waiting for a suppressed event.
+GitHub can additionally create a bot-PR run with `action_required`. If that run blocks
+PR checks, a maintainer must review the changes and approve that run in Actions;
+a successful dispatch alone does not override GitHub's platform approval policy.
+The initial rollout required this approval. The workflow does not self-approve or
+delete blocked checks to bypass it.
 
 Version behavior follows Conventional Commits. `fix` normally bumps patch, `feat`
 bumps minor, and breaking changes before 1.0 bump minor. Visible maintenance/docs/CI

package/docs/testing.md

@@ -17,6 +17,41 @@ helper scripts and memory state must not ship in the package.
 
 `check:package` inspects `npm pack --dry-run --json`; it does not publish to npm.
 
+## npm CLI compatibility
+
+All consumers of `npm pack --json` share `scripts/lib/npm-pack.mjs`. npm 10/11
+return an array; npm 12 returns a package-name map. The helper accepts both and
+rejects invalid, empty, multi-package or mismatched results rather than picking an
+arbitrary package. It is development tooling, not part of the runtime tarball.
+
+CI explicitly installs and verifies npm majors **10 and 12** on Node 24, and runs
+checks, installation and packaging in both lanes. The ordinary Node 22/24 jobs
+also exercise their bundled npm. Node version alone does not define coverage of an
+npm major. The pinned setup-node action has no `npm-version` input, so selecting
+npm uses an explicit `npm install --global --ignore-scripts` step instead.
+
+For local reproduction without changing the global npm installation:
+
+```bash
+npx --yes npm@12 run check
+npx --yes npm@12 run test:install
+npx --yes npm@10 run check
+npx --yes npm@10 run test:install
+```
+
+For an older checkout whose pack parser still fails under npm 12, the npm 10
+commands are a temporary workaround until you update. `npm run` retains the npx
+npm shim on PATH, so nested `execFileSync('npm', ...)` calls use the selected CLI;
+the installation test prints the actual Node/Pi/npm versions. Declaring npm in
+`engines` can document a requirement, but does not replace compatible parsing or
+explicit version testing.
+
+npm 12 also gates dependency lifecycle scripts through its script-allow policy.
+This repository installs with `--ignore-scripts`; do not turn on all scripts merely
+to make an installation pass. If a future dependency requires postinstall compilation,
+review that dependency and update the isolated tests/policy explicitly. Pi's bundled
+runtime and currently tested dependencies work with scripts disabled.
+
 ## Installation smoke test
 
 ```bash
@@ -44,6 +79,10 @@ host explicitly. The script prints the tested host version. The test:
 6. Serves the actual tarball through a loopback npm registry, with a fresh cache,
    then checks native `pi install npm:pi-memory-evolution`, repeat installation,
    normal loading and removal. No host peer packages are served or installed.
+7. Intentionally installs local and npm copies together, reproduces the host's
+   duplicate `memory_recall` failure, removes the unwanted source through the CLI,
+   and verifies startup and unchanged memory/history. This is configuration recovery,
+   not silently choosing which installed version should win.
 
 The test whitelists child environment variables, gives Pi a fresh agent directory
 and HOME, disables startup network operations, and uses private npm caches/config with

package/docs/usage.md

@@ -57,6 +57,31 @@ the old source before switching between npm/Git/local forms, which Pi treats as
 different package identities. `pi remove <source>` does not erase memory state.
 Restart or `/reload` all sessions using the extension after changing versions.
 
+### Recovering from duplicate installation sources
+
+Pi treats npm, Git and local paths as different package identities. Installing the
+same source twice is idempotent, but keeping both a dev checkout and an npm copy can
+register `memory_recall` twice and prevent Pi from starting. Updating either copy
+does not remove the other. This is not a failure of a single-source upgrade.
+
+Use terminal commands, not commands inside the broken Pi session:
+
+```bash
+pi list
+# Keep npm; remove the local source shown by pi list:
+pi remove /absolute/path/to/pi-memory-evolution
+# Or keep the checkout; remove npm instead:
+# pi remove npm:pi-memory-evolution
+```
+
+Choose only the removal matching your intended source. If installed project-locally,
+run `pi list --approve` and `pi remove <source> -l --approve` from that trusted project.
+A manually configured `extensions` entry is not a package entry: remove that explicit
+entry from the appropriate settings file as well. Then restart Pi and run
+`/memory status`. Package CLI operations work without loading the conflicting
+extensions, and removal leaves memory data intact. Do not delete the database or
+rename the tool to hide the conflict; an old installation would still run its hooks.
+
 ## What happens automatically
 
 - A successful `session_compact` saves a sanitized source and extracts up to 16

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-memory-evolution",
-	"version": "0.2.1",
+	"version": "0.2.2",
 	"description": "Automatic cross-session memory using Pi's active model, transactional local storage, and topic-based recall across directories.",
 	"license": "MIT",
 	"publishConfig": {
@@ -58,10 +58,10 @@
 		"check:package": "node scripts/check-package.mjs"
 	},
 	"devDependencies": {
-		"@earendil-works/pi-coding-agent": "0.85.0",
-		"@types/node": "22.18.0",
-		"typebox": "1.3.7",
-		"typescript": "5.9.3",
+		"@earendil-works/pi-coding-agent": "0.85.1",
+		"@types/node": "22.20.1",
+		"typebox": "1.3.27",
+		"typescript": "7.0.2",
 		"yaml": "2.9.0"
 	}
 }