memorix 1.8.3 → 1.8.5

package/CHANGELOG.md

@@ -4,6 +4,59 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+## [1.8.5] - 2026-08-30
+
+### Fixed
+- **Modern MCP transport** -- `memorix serve` and the HTTP control plane now
+  use the official MCP v2 server path for 2026-07-28 discovery, request
+  metadata, result envelopes, response metadata, stateless requests, and the
+  subscriptions listen surface while forwarding business tools through the
+  existing Memorix implementation.
+- **Background start race (#259)** -- background startup now holds an
+  exclusive, heartbeating lock across the check/spawn/readiness window. Lock
+  contention fails closed with a retry message instead of starting an unlocked
+  duplicate control plane; stale dead-owner locks are recoverable.
+- **Windows and EOF behavior** -- stdio discovery remains compatible before
+  and after readiness, roots-based project switching and deferred maintenance
+  are preserved, and stdin EOF closes the official transport cleanly.
+- **Local build reliability** -- the large runtime, CLI, and memcode bundles
+  build sequentially, reducing Windows memory pressure without changing
+  published entry points. Slow CLI uninstall tests now use asynchronous,
+  hidden child processes so the full test run exits cleanly.
+- **Time-stable graph evaluation** -- graph-context fixtures pin their
+  reference date so retention policy changes do not make the test depend on the
+  calendar.
+
+### MCP Compatibility Boundary
+- Modern Tasks are explicitly unsupported because Memorix does not expose a
+  durable task store for MCP task semantics.
+- List responses expose a private zero-TTL protocol hint; Memorix does not
+  claim a reusable server-side list cache.
+- The external `@hasmcp/mcp-spec-test` runner currently fails on this Windows
+  host before reaching the target because it imports drive-letter paths as ESM
+  URLs. Production verification therefore includes official v2 direct tests,
+  real stdio/HTTP smoke, and the legacy compatibility path; this external
+  runner result is not reported as a pass.
+
+## [1.8.4] - 2026-08-27
+
+### Fixed
+- **Stateless HTTP MCP requests (#255)** -- clients such as Claude Code that
+  send the current protocol header on every request can list and call tools
+  without echoing a custom project handle. Durable handles are still created
+  on `initialize` and remain available when a client opts into them.
+- **MCP protocol self-description (#257)** -- discovery and HTTP response
+  headers now advertise the legacy revisions implemented by the pinned SDK,
+  instead of claiming complete support for the newer 2026 revision.
+- **MCP stdio smoke contract** -- the release smoke script now checks the
+  truthful advertised revision set after the compatibility fix.
+
+### MCP Compatibility
+- The 1.8.4 line supports legacy stateful MCP, versionless stdio tool calls,
+  pre-initialize discovery, and the narrow stateless HTTP compatibility path.
+  It does not claim full 2026 result metadata, Tasks, subscriptions, or list
+  caching support.
+
 ## [1.8.3] - 2026-08-25
 
 ### Fixed

package/CLAUDE.md

@@ -76,6 +76,9 @@ to enable them).
 | `memorix_resolve` | Mark completed/outdated memories |
 | `memorix_session_start` | Load session context (handoff, team coordination) |
 | `memorix_timeline` | See chronological context around a memory |
+| `memorix_evidence` | Check a memory's source, freshness, and verification state |
+| `memorix_feedback` | Record whether a memory helped, conflicted, or was corrected |
+| `memorix_media` | Inspect or import controlled local media; generation stays explicitly gated |
 | `memorix_retention` | Check memory health and archive expired items |
 | `memorix_promote` (MEMORIX_MODE=full) | Turn repeated patterns into permanent skills |
 | `memorix_rules_sync` (MEMORIX_MODE=full) | Inspect or sync rules across agents |

package/README.md

@@ -210,7 +210,7 @@ CLI, MCP, and HTTP are different entry points:
 
 - `memorix` CLI is the direct command surface for setup, memory search/store, Git Memory, import/export, dashboard, orchestration, diagnostics, and automation.
 - `memorix serve` is the stdio MCP bridge used by IDEs and coding agents. Its default tool profile is `micro`, so agents see only the compact core tool set.
-- `memorix background start` / `memorix serve-http` run the HTTP service for a shared endpoint, dashboard, Docker, or multiple clients.
+- `memorix background start` / `memorix serve-http` run the HTTP service for a shared endpoint, dashboard, VPS Docker deployment, or multiple clients.
 
 <h2 id="install"><picture><source media="(prefers-color-scheme: dark)" srcset="assets/tags/light/section-install.svg"><img src="assets/tags/section-install.svg" alt="Install" height="32" /></picture></h2>
 
@@ -298,7 +298,7 @@ If your agent only needs a manual MCP entry, use stdio:
 
 For a manually managed Claude Code entry, add `"alwaysLoad": true` inside the `memorix` server object. This lets Claude Code expose Memorix tools during print-mode startup; `memorix doctor agents --agent claude` can detect and repair a missing setting.
 
-HTTP is not required for normal setup. Use it only when you intentionally want a shared background service, dashboard, Docker, or multiple clients using the same endpoint:
+HTTP is not required for normal setup. Use it only when you intentionally want a shared background service, dashboard, VPS Docker deployment, or multiple clients using the same endpoint. Local development uses the Node service directly and does not require Docker:
 
 ```bash
 memorix background start
@@ -456,7 +456,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` into the installed MCP config so every tool taught in the generated guidance is reachable. Use `--mode team` for coordination tools, or `--mode full` 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` (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.
 
 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.
 
@@ -509,7 +509,7 @@ generation is explicit; MCP generation additionally requires
 
 <h2 id="docker"><picture><source media="(prefers-color-scheme: dark)" srcset="assets/tags/light/section-docker.svg"><img src="assets/tags/section-docker.svg" alt="Docker" height="32" /></picture></h2>
 
-Docker is for the HTTP service, not stdio MCP:
+Docker is a VPS/hosted HTTP deployment option, not a requirement for local development or stdio MCP:
 
 ```bash
 docker compose up --build -d

package/README.zh-CN.md

@@ -209,7 +209,7 @@ CLI、MCP 和 HTTP 是不同入口：
 
 - `memorix` CLI 用于直接操作：setup、记忆搜索/写入、Git Memory、导入导出、Dashboard、编排、诊断和自动化。
 - `memorix serve` 是给 IDE / Coding Agent 使用的 stdio MCP 桥。
-- `memorix background start` / `memorix serve-http` 是 HTTP 服务，用于共享端点、Dashboard、Docker 或多客户端。
+- `memorix background start` / `memorix serve-http` 是 HTTP 服务，用于共享端点、Dashboard、VPS Docker 部署或多客户端。
 
 <h2 id="安装"><picture><source media="(prefers-color-scheme: dark)" srcset="assets/tags/light/section-install.svg"><img src="assets/tags/section-install.svg" alt="安装" height="32" /></picture></h2>
 
@@ -297,7 +297,7 @@ memorix setup --agent dsh --global
 
 如果是手动维护 Claude Code 的 MCP 配置，需要在 `memorix` server 对象里加上 `"alwaysLoad": true`。这样 Claude Code 在 print-mode 启动时就会暴露 Memorix tools；`memorix doctor agents --agent claude` 可以检查并修复缺失的设置。
 
-普通安装不需要 HTTP。只有在你明确需要共享后台服务、Dashboard、Docker，或多个客户端共用一个端点时才使用：
+普通安装不需要 HTTP。只有在你明确需要共享后台服务、Dashboard、VPS Docker 部署，或多个客户端共用一个端点时才使用。本机开发直接运行 Node 服务，不需要 Docker：
 
 ```bash
 memorix background start
@@ -438,6 +438,8 @@ 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 orchestrate` 单 worker 默认使用当前 checkout；多 worker 时会在 `.worktrees/` 下为任务创建隔离 worktree，并把成功的任务分支 merge 回来。用 `--isolated` 可强制单 worker 也隔离，用 `--no-worktree` 禁用 worktree，用 `--allow-dirty` 允许带未提交改动运行，用 `--no-auto-merge` 保留任务 worktree 方便人工 review。
 
 <h2 id="memcode内置终端-agent"><picture><source media="(prefers-color-scheme: dark)" srcset="assets/tags/light/section-memcode.svg"><img src="assets/tags/section-memcode.svg" alt="memcode" height="32" /></picture></h2>
@@ -483,7 +485,7 @@ formation = "active"
 
 <h2 id="docker"><picture><source media="(prefers-color-scheme: dark)" srcset="assets/tags/light/section-docker.svg"><img src="assets/tags/section-docker.svg" alt="Docker" height="32" /></picture></h2>
 
-Docker 用于 HTTP 服务，不是 stdio MCP：
+Docker 只作为 VPS/托管环境的 HTTP 部署方式，不是本机开发或 stdio MCP 的必需品：
 
 ```bash
 docker compose up --build -d