memorix 1.9.4 → 1.9.6

package/dist/memcode-runtime/CHANGELOG.md

@@ -2,7 +2,81 @@
 
 All notable changes to this project will be documented in this file.
 
-## [Unreleased]
+## Unreleased (1.9.x)
+
+No unreleased changes.
+
+## [1.9.6] - 2026-09-22
+
+### Added
+- **Task continuity ledger** -- adds a project-scoped append-only
+  ledger for requirements, decisions, verification, risks, and outcomes. The
+  bounded Project Context can include a ledger by `taskId`; no automatic
+  promotion or LLM summarization is performed.
+- **Continuity outcome projection** -- adds deterministic validated, at-risk,
+  in-progress, and unverified states plus replay coverage. Diagnostic scores are
+  exposed in receipts only and do not silently reorder memories.
+- **Infrastructure lifecycle closeout** -- bounds HTTP sessions and SQLite
+  handles, reuses project business runtimes behind fresh modern MCP protocol
+  shells, records event-loop/resource health, and adds a deterministic memory
+  quality gate.
+- **Atlas Cloud memory preset** -- `memorix init` and the configuration TUI can
+  select Atlas Cloud for optional background memory LLM work through its
+  OpenAI-compatible endpoint, with provider-specific key isolation.
+
+### Fixed
+- **Configuration scope isolation** -- explicit home/project resolution now
+  applies consistently to TOML, YAML, legacy JSON, and `.env` loading, so
+  long-lived processes and tests cannot reuse another configuration scope.
+- **OrcaRouter documentation** -- documents the existing OpenAI-compatible
+  gateway path with fixed-model and fallback guidance; no vendor-specific
+  provider branch is required.
+- **Capacity closeout** -- TeamStore queries, maintenance history, embedding
+  caches, HTTP project caches, and large-store behavior are bounded and
+  regression-covered.
+- **Stable coordination queue order** -- available tasks now dispatch FIFO with
+  a SQLite rowid tie-breaker, preventing cross-platform adapter-routing flakes
+  when task timestamps collide.
+- **Continuity correctness** -- verification obligations can move between
+  statuses by stable ID, retries are idempotent, open risks are visible in the
+  outcome state, and the 200-event cap is enforced transactionally.
+- **Replay-safe orchestration evidence** -- tool effects are recorded with
+  redacted fingerprints, risk tiers, replay policy, and unknown-after-crash
+  status without persisting raw tool arguments or output.
+
+## [1.9.5] - 2026-09-20
+
+### Added
+- **Setup HTTP MCP** -- `memorix setup --mcp http` honors Grok (writes a
+  `[mcp_servers.memorix]` URL in Grok `config.toml`) and rewrites installed
+  plugin/extension bundled MCP manifests from `memorix serve` to
+  `http://localhost:3211/mcp`. Default Grok MCP stays host-owned. Docs include
+  generic systemd user unit and LaunchAgent KeepAlive examples for
+  `memorix serve-http`.
+- **User-global store sync** -- `memorix sync store push|pull|status --scope user`
+  replicates every local project's eligible observations through the existing
+  opt-in relay. Default `--scope project` is unchanged. Privacy filters still
+  drop personal, agent-targeted, candidate, and ephemeral rows. The live
+  SQLite file is never copied.
+
+### Fixed
+- **HTTP control-plane safety** -- JSON request bodies are bounded, non-loopback
+  binds require an explicit Bearer token or unsafe opt-in, listen failures are
+  reported synchronously, background startup removes unverified state, and
+  shutdown waits for HTTP and SQLite resources to close.
+- **Project-scoped graph storage** -- graph entities and relations now carry a
+  project key, legacy JSONL migration recovers ownership from observation
+  references, and Dashboard/MCP graph access no longer crosses projects.
+- **Migration and lifecycle reliability** -- legacy observation/subdirectory
+  migrations use locks and atomic writes, malformed observation JSON fails
+  closed, stale file locks cannot evict a live writer, stateless MCP bindings
+  expire and are cleaned up, and SDK clients share resources safely.
+- **User-scope sync correctness** -- imported observation IDs are remapped on
+  collision, tombstones validate their source project, and user namespaces
+  must be explicit per-user values.
+- **Release contract** -- publish workflow validates tag/version/commit
+  identity, waits for npm visibility before MCP Registry publication, and
+  keeps prepublish checks non-mutating.
 
 ## [1.9.4] - 2026-09-18
 

package/dist/sdk.d.ts

@@ -120,6 +120,7 @@ declare class MemoryClient {
     private _oramaStore;
     private _obsStore;
     private _freshness;
+    private _sdkRefRegistered;
     /** @internal — use createMemoryClient() instead */
     constructor(projectId: string, projectRoot: string, dataDir: string);
     /** The canonical project ID (derived from Git remote or local path) */