memorix 1.9.5 → 1.9.6

package/dist/memcode-runtime/CHANGELOG.md

@@ -2,6 +2,48 @@
 
 All notable changes to this project will be documented in this file.
 
+## 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