Engram 3.7.1
Patch release with the matching gentle-engram@0.7.1 companion.
- Database recovery:
migrate-copyadmits the complete v3.4.0 and pre-org upgrade catalogs, plus SQLite-generated quotedsync_chunksheaders. Complete-catalog validation still rejects changed constraints, triggers and unknown objects (#2338, #2350, #2354). - Daemon diagnostics:
ps,stopand detached startup detect unmanaged or unknown listeners, report a best-effort owning PID on Windows, and keep health probes on the selected endpoint (#2351). - Project names: explicit project merges accept names containing ASCII spaces (#2337).
- Search: FTS query size is bounded deterministically (#944).
- Pi: native saves inherit configured organization, first capture waits for pinned-server startup, and the memory protocol is omitted when memory tools are absent while rarely used tools load on demand (#2335, #2336, #2348).
- Build security: current binaries use Go 1.26.11 (#2353).
- Privacy: judgment reasons and evidence redact private-tagged blocks before storage, responses and synchronization; previously stored rows are not rewritten (#2361).
- Pi setup: preserve custom same-name npm package sources across Pi installation; unexpected settings conflicts stop setup and retain a recovery copy (#2358).
Back up data and configuration before upgrading. Restart an existing server through its supervisor and verify the running server version. Pi users can run engram setup pi, then restart Pi. Use this matching core setup flow to preserve custom same-name npm sources: direct pi install npm:gentle-engram@0.7.1 may replace one before pi-engram init runs. Go setup stops on unrecognized settings changes and retains a recovery copy; it does not lock settings against concurrent edits.
Download the archive matching your OS/architecture and verify it against checksums.txt. See the release and rollback policy.
The final published pair passed an isolated Windows/amd64 persistence, restart and shutdown observation. The full Windows CI suite also passed on this exact source commit in the main run. Earlier merge-group Codex hook timeouts and their follow-up remain recorded in the release tracker.
At core publication, gentle-engram@0.7.1 is available under npm's candidate tag; promotion of the exact version to latest remains a separate package-owner action. The matching core installer pins 0.7.1 explicitly.
Full comparison: v3.7.0...v3.7.1