gentle-engram v0.6.0

gentle-engram 0.6.0

Source: 1e4bea1e (tag pi-v0.6.0, head of #2239). The published package is byte-identical to plugin/pi on main at ec2bf048. Changes since gentle-engram 0.4.2 / pi-v0.4.2, the previous npm latest. Versions 0.5.0 and 0.5.1 were published through the candidate channel.

Highlights

0.6.0

• Consolidation release. Synchronizes the package manifest, lockfile and core installer pin. It adds no new adapter or runtime functionality (#2239).
• Clean upgrade from 0.5.1. pi-engram init and engram setup pi replace a managed npm:gentle-engram@0.5.1 pin rather than keeping both versions. Earlier managed migrations, custom/local/object entries, unrelated settings and MCP configuration are preserved, and repeated setup is byte-idempotent (#2239).
• Selective memory capture guidance. The injected memory protocol now asks agents to persist verified, durable knowledge (decisions with rationale, non-obvious root causes, real constraints, resumption-relevant pending work), to skip routine progress and raw dumps, to search only when it materially helps, and to call mem_session_summary at significant closure or handoff (#2128).

From 0.5.1

• mem_update find and replace (#1986).
• Older context history (#1992).
• Stored prompt search through MCP and Pi (#2000).
• Memory dispatch and input projections qualified against the Go runtime, with real schema drift diagnostics (#1905, #2005, #1995).
• The detached engram serve spawn no longer inherits session-scratch temporary variables (#2053).
• Independent core/Pi version-pair validation (#1990) and native host compaction and resume ownership checks (#1993).

From 0.5.0

Session-owned core startup and shutdown (package metadata declares engram.startupPolicy: 1 and engram.sessionOwned: 1), bundled-store recovery across core upgrades, compact search and paginated history, and the canonical memory workflow. See the gentle-engram 0.5.0 release.

Install and compatibility

• Matching core: Engram v3.6.2, whose engram setup pi pins npm:gentle-engram@0.6.0. Core v3.6.1 and earlier pin older companions, so upgrade the core and the companion together.

• Install with engram setup pi from core 3.6.2, or directly:

  pi install npm:gentle-engram@0.6.0

• Back up Engram data and configuration before upgrading and keep a known-good installation until the upgrade is accepted. See the release and rollback policy.

Verification and limits

• The npm tarball matches its registry integrity. All 56 files match plugin/pi on main at ec2bf048 byte for byte.
• From #2239: native Windows installed-host lifecycle and persistent 0.5.1→0.6.0 upgrade checks passed. The full Pi suite ran 640 tests: 639 passed and 1 was skipped because it requires an installed Pi host.
• Not claimed: a direct 0.4.2→0.6.0 upgrade on a real user installation, cross-platform installed-host qualification, or downstream Shell bundle upgrades.

Contributors

Thank you @dnlrsls and @decode2 for the changes in this range.

Changes since pi-v0.5.0

• feat(pi): expose mem_update find and replace (#1986)
• fix(release): validate independent core and Pi version pairs (#1990)
• feat(pi): expose older context history (#1992)
• test(pi): verify native host compaction and resume ownership (#1993)
• feat(memory): expose stored prompt search to MCP and Pi (#2000)
• feat(pi): diagnose real schema drift without certifying parity (#1995)
• feat(pi): qualify memory dispatch against the Go runtime (#1905)
• feat(protocol): verify Go-owned Pi input projections (#2005)
• test(protocol): complete bounded MCP-Pi behavioral evidence (#2010)
• fix(pi): drop session-scratch temp variables from the detached serve spawn (#2053) by @decode2
• chore(release): prepare core 3.5.3 and Pi 0.5.1 (#2063)
• docs(memory): align selective durable knowledge capture (#2128)
• chore(pi): prepare 0.6.0 consolidation candidate (#2239)

Full comparison: pi-v0.5.0...pi-v0.6.0