gentle-engram 0.5.0

Source: fe897f66. Changes since gentle-engram 0.4.2 / pi-v0.4.2 (the npm predecessor, not the older GitHub Pi release).

Highlights

• Session-owned core startup/shutdown and bundled-store recovery across core upgrades.
• Align the default Pi memory tool profile with the Go-owned Agent contract and share compound workflow validation.
• Compact memory search and paginated observation history through the HTTP/Pi workflows.
• Canonical search/read/update memory workflow and unified protocol guidance.
• Package the Go-owned runtime comparison assets and add local package validation plus real HTTP workflow coverage.
• Keep post-compaction recovery instructions out of the system prompt to reduce unnecessary prompt re-reading.
• Isolate primary-runtime contract fixtures from inherited delegated-agent roles and improve Windows fixture portability.

Upgrade from 0.4.2

Version 0.5.0 and the matching core setup pins include migration of the known managed 0.4.2 predecessor while preserving unrelated settings and MCP configuration (#1924).

Compatibility and publication

Core publication status: the v3.5.0 core release stopped at the module-checksum preflight before producing release assets. The replacement Engram 3.5.1 is being prepared and is not published yet. gentle-engram 0.5.0 remains on npm's candidate channel until the supported pair is verified. Publication initially uses npm's candidate dist-tag; latest promotion is separate and follows pair verification. Full Go/Pi semantic parity and every downstream Shell bundle upgrade are not claimed. Back up data and configuration before upgrading.

Verification and limits

• Source CI passed for the exact release commit.
• Staged Windows x64 core/companion passed an isolated genuine Pi 1.3.0 search/save/search smoke, authentication, managed-settings migration and owned-process shutdown checks. Published artifact provenance and checksums are verified separately.
• No real-user database or installation was used. These checks do not certify every downstream Shell bundle upgrade.
• Windows binaries are not Authenticode-signed; Smart App Control and Defender reports remain separate open investigations (#1703, #1912).

Contributors

Thank you @dnlrsls, @Alan-TheGentleman, @josegarvinvictoria and @pablon for changes in the Pi package/setup range. Credits below identify the associated contributions.

Changes since pi-v0.4.2

• feat(pi): add canonical topic workflow to the memory protocol by @josegarvinvictoria in #1653

• docs: unify memory protocol across all agent surfaces by @pablon in #1787

• fix(pi): preserve fake CLI invocation logs on Windows by @dnlrsls in #1829

• fix: recover bundled stores across core upgrades and stop session-owned servers with Pi by @Alan-TheGentleman in #1854

• fix(pi): preserve owned startup fixture checks on Windows by @dnlrsls in #1862

• feat(search): expose compact search through HTTP and Pi by @dnlrsls in #1863

• feat(history): expose paginated observation history through HTTP and Pi by @dnlrsls in #1869

• feat(release): add rejection-only candidate checker by @dnlrsls in #1874

• feat(release): validate local Pi package tarballs by @dnlrsls in #1882

• fix(pi): integrate Go-owned agent profile on main by @dnlrsls in #1884

• test(pi): integrate real HTTP workflow coverage on main by @dnlrsls in #1886

• feat(capture): preserve optional project provenance by @dnlrsls in #1885

• feat(runtime-contract): generate current Go-owned HTTP projection by @dnlrsls in #1893

• feat(pi): package Go runtime comparison assets by @dnlrsls in #1904

• feat(release): guard companion publication order by @dnlrsls in #1936

• fix(pi): keep compaction recovery out of the system prompt by @dnlrsls in #1946

• fix(pi): isolate native contract fixtures from delegated roles by @dnlrsls in #1950

• feat(release): prepare compatible session-owned candidate pair by @dnlrsls in #1924

Full repository comparison: pi-v0.4.2...pi-v0.5.0