memorix 1.9.5 → 1.9.6

package/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

package/README.md

@@ -483,7 +483,7 @@ Long-term memory is deliberately not an automatic dump of every note. A source o
 | Use the bundled terminal agent | `memorix` or `memcode` |
 | Run orchestrated subagent work | `memorix orchestrate --goal "..."` |
 
-`memorix serve` defaults to `--mode micro` (9 tools) to keep MCP tool schemas small for agents. `memorix setup` writes `--mode lite` (20 tools) into the installed MCP config so the normal memory and session surface is reachable. Use `--mode team` (28 tools) for coordination tools, or `--mode full` (47 tools) for advanced and compatibility tools such as checkpoint inspection.
+`memorix serve` defaults to `--mode micro` (9 tools) to keep MCP tool schemas small for agents. `memorix setup` writes `--mode lite` (21 tools) into the installed MCP config so the normal memory, continuity, and session surface is reachable. Use `--mode team` (29 tools) for coordination tools, or `--mode full` (48 tools) for advanced and compatibility tools such as checkpoint inspection.
 
 Shortcuts and aliases: `memorix search` / `remember` / `recent` are direct query shortcuts, `bg`/`bs` start the background service, `hook` runs the hook launcher, and `memorix config get|path|migrate` inspects or migrates config files.
 
@@ -526,6 +526,11 @@ formation = "active"
 
 Use `[memory.llm]` and `[embedding]` for Memorix memory quality and retrieval. Use `[agent]` for the model memcode talks to while coding. Keep credentials in global config or environment variables, and do not commit secrets.
 
+For the optional Atlas Cloud memory preset, run `memorix init` and choose Atlas
+Cloud, or set `provider = "atlascloud"` in `[memory.llm]`. It uses the
+OpenAI-compatible `https://api.atlascloud.ai/v1` endpoint and reads
+`ATLASCLOUD_API_KEY` or the explicit `MEMORIX_LLM_API_KEY`.
+
 For OpenRouter embeddings, use `provider = "api"`, `base_url = "https://openrouter.ai/api/v1"`, and `model = "qwen/qwen3-embedding-8b"`. Memorix accepts `OPENROUTER_API_KEY` for that embedding endpoint; `MEMORIX_EMBEDDING_API_KEY` remains the explicit override.
 
 For controlled MiniMax media generation, set `MINIMAX_API_KEY` (global) or

package/README.zh-CN.md

@@ -458,7 +458,7 @@ memcode
 | 使用内置终端 Agent | `memorix` 或 `memcode` |
 | 运行编排式 subagent 工作 | `memorix orchestrate --goal "..."` |
 
-`memorix serve` 默认使用 `--mode micro`（9 个工具），保持 MCP 工具 schema 紧凑。`memorix setup` 写入 `--mode lite`（20 个工具），覆盖常用记忆、会话、证据和反馈入口。需要协作工具时使用 `--mode team`（28 个工具），需要高级和兼容工具时使用 `--mode full`（47 个工具）。
+`memorix serve` 默认使用 `--mode micro`（9 个工具），保持 MCP 工具 schema 紧凑。`memorix setup` 写入 `--mode lite`（21 个工具），覆盖常用记忆、连续性、会话、证据和反馈入口。需要协作工具时使用 `--mode team`（29 个工具），需要高级和兼容工具时使用 `--mode full`（48 个工具）。
 
 `memorix orchestrate` 单 worker 默认使用当前 checkout；多 worker 时会在 `.worktrees/` 下为任务创建隔离 worktree，并把成功的任务分支 merge 回来。用 `--isolated` 可强制单 worker 也隔离，用 `--no-worktree` 禁用 worktree，用 `--allow-dirty` 允许带未提交改动运行，用 `--no-auto-merge` 保留任务 worktree 方便人工 review。
 
@@ -499,6 +499,11 @@ formation = "active"
 
 `[memory.llm]` 和 `[embedding]` 负责记忆质量和检索；`[agent]` 是 memcode 编码时使用的模型。凭据放全局配置或环境变量，不要提交 secrets。
 
+如需使用可选的 Atlas Cloud 记忆模型预设，可以运行 `memorix init` 选择
+Atlas Cloud，或在 `[memory.llm]` 中设置 `provider = "atlascloud"`。它使用
+OpenAI-compatible 的 `https://api.atlascloud.ai/v1` endpoint，并读取
+`ATLASCLOUD_API_KEY` 或显式的 `MEMORIX_LLM_API_KEY`。
+
 如果使用 OpenRouter embedding，可以设置 `provider = "api"`、`base_url = "https://openrouter.ai/api/v1"`、`model = "qwen/qwen3-embedding-8b"`。这个 endpoint 下 Memorix 会读取官方 `OPENROUTER_API_KEY`；需要单独覆盖 embedding key 时仍可用 `MEMORIX_EMBEDDING_API_KEY`。
 
 受控 MiniMax 媒体生成可在环境变量或 `.env` 中设置全局 `MINIMAX_API_KEY`，或中国区 `MINIMAX_CN_API_KEY`。媒体库不会保存该 key、临时签名 URL 或 base64 负载。CLI 生成本身就是显式操作；若要让 MCP 中的 Agent 发起生成，还必须明确设置 `MEMORIX_MCP_MEDIA_GENERATION=1`。