pi-memory-evolution 0.2.3 → 0.2.4

package/CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to pi-memory-evolution are documented here.
 
+## [0.2.4](https://github.com/btnalit/pi-memory-evolution/compare/v0.2.3...v0.2.4) (2026-09-09)
+
+
+### Bug Fixes
+
+* correct the schema marker in docs and state the promise up front ([#12](https://github.com/btnalit/pi-memory-evolution/issues/12)) ([2a651c4](https://github.com/btnalit/pi-memory-evolution/commit/2a651c484af606ab66b0381b8a73afc11a660585))
+
 ## [0.2.3](https://github.com/btnalit/pi-memory-evolution/compare/v0.2.2...v0.2.3) (2026-09-09)
 
 

package/README.cn.md

@@ -42,7 +42,7 @@ pi install https://github.com/btnalit/pi-memory-evolution
 /memory status
 ```
 
-出现 `SQLite ok (schema 5)` 表示存储初始化成功。后续正常使用 Pi 即可，学习和召回会自动运行。
+出现 `SQLite ok (schema 6)` 表示存储初始化成功。后续正常使用 Pi 即可，学习和召回会自动运行。
 
 ## 使用
 

package/README.md

@@ -46,7 +46,7 @@ Choose **one** source, then run these commands inside Pi:
 /memory status
 ```
 
-`SQLite ok (schema 5)` confirms storage initialization. Continue using Pi normally;
+`SQLite ok (schema 6)` confirms storage initialization. Continue using Pi normally;
 learning and recall run automatically.
 
 ## Use

package/docs/core-quality.md

@@ -195,7 +195,7 @@ reset, automatic state revival or fabricated verification occurs.
 Reads validate evidence/feedback shape and tool-observation kind, and return independent
 copies of nested metadata. Status validates receipt fields in addition to existing
 record/job/history integrity. Unsupported schema versions fail before DDL. Old builds
-reject schema 5: do not manually downgrade its marker.
+reject schema 6: do not manually downgrade its marker.
 
 Stop all Pi processes sharing the state directory and back up the complete state before
 activation. Update/restart all those processes together (or reload after a consistent

package/docs/testing.md

@@ -67,7 +67,7 @@ host explicitly. The script prints the tested host version. The test:
 1. Builds and extracts the actual npm tarball, outside the development checkout.
 2. Uses real `pi install`, `pi list` and default package discovery—no explicit `-e`
    entry or memory-extension wrapper. Checks `/memory status`, `/memory learning`
-   and `/memory explain`, including schema 5, with no checkout `node_modules`.
+   and `/memory explain`, including schema 6, with no checkout `node_modules`.
 3. Verifies repeated installation does not duplicate the package setting, then
    removes it and confirms the command disappears while records/history remain.
 4. Creates a local Git origin from the packed files and the real lockfile. A
@@ -75,7 +75,7 @@ host explicitly. The script prints the tested host version. The test:
    `file` transport is permitted. No GitHub access is needed.
 5. Exercises the native Git installer and its real npm dependency step, updates to
    a new commit, switches from an old pinned tag back to the default branch, and
-   verifies source switching and removal preserve schema-5 state.
+   verifies source switching and removal preserve schema-6 state.
 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.

package/docs/usage.md

@@ -289,6 +289,9 @@ These are optional direct controls, **not approval gates**:
 /memory status                       # integrity + retries + processed-versus-changed outcomes
 /memory history                      # last 10 events across all origins
 /memory evolve                       # optional one-off retry, overriding delay/failure limit
+/memory evolve <source-id>            # retry one named source without clearing other failure counts
+/memory import [directory]            # explicit, repeat-safe legacy JSONL import; never replays a completed one
+/memory archive-legacy                # copy inactive legacy plan files to a timestamped archive; originals kept
 /memory undo <event-id>               # reverse actual changes, if not modified since
 /memory feedback <id> <verdict>       # useful | unhelpful | accurate | incorrect
 /memory correct <id> <replacement>    # literal replacement, 4–480 characters
@@ -353,7 +356,7 @@ contract (plus missing retry fields for older schemas). Existing records, IDs, h
 evidence dates remain unchanged. Missing evidence stays unknown, with no fabricated backfill.
 Existing failures below the limit become automatically eligible; their old error cause/time
 remain labeled unknown rather than invented. No copying, manual marker reset or JSONL
-re-import is needed. Older builds reject schema 5; rollback requires a matching backup,
+re-import is needed. Older builds reject schema 6; rollback requires a matching backup,
 not editing the marker. Existing records are immediately eligible for global relevance-based recall.
 Legacy claims previously excluded by cwd filtering become eligible too. This shares
 relevant stored claims with the active Pi session/provider, not raw session archives.
@@ -408,4 +411,4 @@ JSONL, not changes made in the new database.
   stopped; do not mix one backup's database with another's WAL/SHM files.
 
 Diagnostics intentionally do not echo provider error bodies, which may contain secrets.
-`SQLite ok (schema 5)` checks database structure/record validity, not the truth of model claims.
+`SQLite ok (schema 6)` checks database structure/record validity, not the truth of model claims.

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "pi-memory-evolution",
-	"version": "0.2.3",
-	"description": "Automatic cross-session memory using Pi's active model, transactional local storage, and topic-based recall across directories.",
+	"version": "0.2.4",
+	"description": "Memory that maintains itself. Pi learns what matters, injects what this session needs, and recalls the rest — nothing to configure, no commands to learn.",
 	"license": "MIT",
 	"publishConfig": {
 		"access": "public",