Gentleman-Programming/engram pi-v0.8.0

gentle-engram 0.8.0

on GitHub

gentle-engram 0.8.0

Minor companion for Engram 3.7.2.

• Shared daemon lifecycle: shared-mode startup now probes engram run -d first, so the standard engram ps, stop, logs and restart commands can manage the server the companion starts. The probe is bounded and version-free; older cores or a failed handoff still fall back to detached engram serve, implicit recovery reuses the same path, and session-owned mode is unchanged (#2368).
• Deferred memory protocol: setting ENGRAM_DEFER_MEMORY=1 skips injection of the Memory Protocol text into the system prompt at both call sites while the mem_* tools stay registered and functional. An absent variable or any other value keeps the current injection (#2371).
• Package guidance and the native setup pin move together to 0.8.0. Managed 0.7.1, 0.7.0 and 0.6.0 entries migrate while custom/local/object entries and unrelated settings remain intact (#2374).

Use the matching core's engram setup pi to preserve custom same-name npm sources across installation. Direct pi install can replace one before pi-engram init runs. Setup retains a recovery copy on unrecognized changes and does not lock concurrent settings edits.

The package declares engram.startupPolicy: 1 and engram.sessionOwned: 1, and the published runtime contract asset is unchanged.

The npm package is published at gentle-engram 0.8.0 with provenance. Its registry integrity is sha512-lc9bVl+SJZZ9VWyK6MPjozT/7RxymUWH89C+IPzDV+6oZjs6+coHd2JRrtQIkvqKsY9w2hAnHdbd61m1kzr9qQ==, and the published tarball's SHA-512 matches the registry metadata.

Publication used npm's candidate dist-tag. A read-only public registry check after publication shows candidate at 0.8.0 and latest still at 0.7.0. Promotion of 0.8.0 to latest is pending human browser-based 2FA and was not performed by this release; this GitHub release does not move that dist-tag. Downstream Gentle Shell consumption follows the latest channel after promotion.

Provenance

• Previous companion: 0.7.1 -> a5d4fa7be7f7e41054f5578ce3d21b7da616bb1d (v3.7.1 shares that commit)
• Release target: pi-v0.8.0 -> c6ba9e3c0e98ffa0d5591481d8670a575e7b70b0
• Release workflow: Publish gentle-engram run 43533315134 succeeded; every job step completed successfully, including the tag/version check, release-candidate build, plugin tests and npm publish with provenance.
• Verification: npm 0.8.0 is publicly observed with provenance, engram.startupPolicy: 1 and engram.sessionOwned: 1; the registry integrity is recorded above and the published tarball matches it.
• Source range: three commits and 15 changed files from pi-v0.7.1 (+246/-44).
• Included work: #2368, #2371, #2374

Full comparison: pi-v0.7.1...pi-v0.8.0