memorix 1.8.4 → 1.8.6

package/dist/memcode-runtime/CHANGELOG.md

@@ -4,6 +4,58 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+## [1.8.6] - 2026-09-01
+
+### Added
+- **WorkBuddy integration (#204)** -- adds project and user-level MCP setup,
+  project `AGENTS.md` guidance, safe no-op behavior for WorkBuddy's absent
+  hooks surface, and uninstall discovery. Thanks to @wjxn13 for the original
+  implementation and follow-up fixes; the contributor commits remain in the
+  merge history.
+
+### Fixed
+- **Continuation intent (#266)** -- a bare `继续`, `continue`, or `resume`
+  no longer triggers an expensive prior-work brief, while short substantive
+  requests such as `继续修复`, `resume bug`, and `继续 API` still receive
+  continuity context. Explicit handoff vocabulary remains supported. Thanks
+  to @Tom-Ma-Ming for the original fix and regression cases.
+- **Star History assets** -- refreshed the self-hosted chart data and light /
+  dark SVG assets.
+
+## [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

package/dist/sdk.js

@@ -149956,6 +149956,15 @@ __export(task_lens_exports, {
   scoreLensSource: () => scoreLensSource,
   shouldShowLensSource: () => shouldShowLensSource
 });
+function hasSubstantiveTask(text2, keyword) {
+  const withoutKeyword = text2.replace(
+    new RegExp(keyword.replace(/[.*+?^${}()|[\]\\]/g, "\\$&"), "gi"),
+    " "
+  );
+  const residual = withoutKeyword.replace(TASK_FILLER_WORDS, " ").replace(TASK_FILLER_PHRASES, " ").replace(/[\s\p{P}]/gu, "");
+  if (/^(?:任务|工作|一下|一起|接着)$/u.test(residual)) return false;
+  return Array.from(residual).length >= MIN_TASK_SUBSTANCE;
+}
 function normalizePath2(path35) {
   return path35.replace(/\\/g, "/");
 }
@@ -150015,8 +150024,12 @@ function resolveTaskLens(task) {
 }
 function isContinuationTask(task) {
   const normalized = (task ?? "").trim().toLowerCase();
-  return normalized.length > 0 && CONTINUATION_KEYWORDS.some(
-    (keyword) => containsTaskKeyword(normalized, keyword)
+  if (normalized.length === 0) return false;
+  if (EXPLICIT_HANDOFF_KEYWORDS.some((keyword) => containsTaskKeyword(normalized, keyword))) {
+    return true;
+  }
+  return AMBIGUOUS_CONTINUATION_KEYWORDS.some(
+    (keyword) => containsTaskKeyword(normalized, keyword) && hasSubstantiveTask(normalized, keyword)
   );
 }
 function pathKindScore(path35, lens) {
@@ -150162,7 +150175,7 @@ function shouldShowLensSource(source, lens, task) {
   if (lens.id === "onboarding" || lens.id === "release" || lens.id === "docs") return score >= 40;
   return score > 0;
 }
-var STOP_WORDS, LENSES, KEYWORDS, CONTINUATION_KEYWORDS, LENS_PRIORITY;
+var STOP_WORDS, LENSES, KEYWORDS, EXPLICIT_HANDOFF_KEYWORDS, AMBIGUOUS_CONTINUATION_KEYWORDS, TASK_FILLER_WORDS, TASK_FILLER_PHRASES, MIN_TASK_SUBSTANCE, LENS_PRIORITY;
 var init_task_lens = __esm({
   "src/codegraph/task-lens.ts"() {
     "use strict";
@@ -150283,18 +150296,31 @@ var init_task_lens = __esm({
       docs: ["doc", "docs", "readme", "\u6587\u6863", "\u8BF4\u660E"],
       test: ["coverage", "fixture", "smoke", "spec", "test", "tests", "testing", "vitest", "\u6D4B\u8BD5"]
     };
-    CONTINUATION_KEYWORDS = [
+    EXPLICIT_HANDOFF_KEYWORDS = [
+      "handoff",
+      "hand off",
+      "hand over",
+      "previous session",
+      "last session",
+      "pick up where",
+      "\u4EA4\u63A5",
+      // 覆盖「任务交接」「工作交接」
+      "\u63A5\u624B",
+      "\u4E0A\u6B21\u4F1A\u8BDD",
+      "\u4E0A\u6B21\u7684\u4F1A\u8BDD"
+    ];
+    AMBIGUOUS_CONTINUATION_KEYWORDS = [
       "continue",
       "resume",
-      "pick up",
       "carry on",
-      "previous session",
+      "pick up",
       "\u7EE7\u7EED",
-      "\u63A5\u624B",
       "\u6062\u590D",
-      "\u5EF6\u7EED",
-      "\u4E0A\u6B21\u4F1A\u8BDD"
+      "\u5EF6\u7EED"
     ];
+    TASK_FILLER_WORDS = /\b(?:please|task|work|the|a|an)\b/giu;
+    TASK_FILLER_PHRASES = /(?:吧|了|呢|啊|吗|嘛|呀|哦|噢|一下|一起|接着|请|帮我)/gu;
+    MIN_TASK_SUBSTANCE = 2;
     LENS_PRIORITY = [
       "bugfix",
       "release",
@@ -162443,6 +162469,9 @@ var init_official_skills = __esm({
           '| Specific past decision, bug, file, or change | `memorix_search` | `memorix memory search --query "<topic>"` |',
           "| Need the full source for a search hit | `memorix_detail` | `memorix memory detail --id <id>` |",
           "| Need the sequence around one memory | `memorix_timeline` | `memorix memory timeline --id <id>` |",
+          "| Check source and freshness for a memory | `memorix_evidence` | `memorix evidence list|get|events` |",
+          "| Record whether a memory helped, conflicted, or was corrected | `memorix_feedback` | `memorix feedback record|show|audit` |",
+          "| Inspect or import controlled media | `memorix_media` | `memorix media import|attach|list|show|status` |",
           '| Learned reusable project knowledge | `memorix_store` | `memorix memory store --type <type> --entity <name> --title "<title>" "<text>"` |',
           "| Task or bug is complete/outdated | `memorix_resolve` | `memorix memory resolve --ids <ids>` |",
           "",
@@ -162573,6 +162602,8 @@ var init_official_skills = __esm({
           "",
           "Promote memories into mini-skills only when they are reusable instructions, not just historical notes.",
           "",
+          "The standard setup uses the `lite` MCP profile. `memorix_skills` and `memorix_promote` are full-profile tools, so use the CLI fallback unless the current server was explicitly started with `MEMORIX_MODE=full` or `--mode full`. Do not probe hidden MCP tools repeatedly.",
+          "",
           "## Tool Router",
           "",
           "| Situation | Prefer | CLI fallback |",
@@ -162608,15 +162639,17 @@ var init_official_skills = __esm({
           "| Situation | Prefer | CLI fallback |",
           "|---|---|---|",
           '| Run managed subagent execution | CLI | `memorix orchestrate --goal "<goal>" --agents claude:1,codex:1` |',
-          "| Register coordination identity | `team_manage` action `join` | `memorix team join --agentType <agent>` |",
-          "| Create or inspect tasks | `team_task` | `memorix task create|list|claim|complete` |",
-          "| Send or read coordination messages | `team_message` | `memorix message send|broadcast|inbox` |",
-          "| Share structured handoff | `memorix_handoff` | `memorix handoff send` |",
-          "| Avoid file conflicts | `team_file_lock` | `memorix lock lock|unlock|status` |",
-          "| Poll joined coordination state | `memorix_poll` | `memorix poll` |",
+          "| Register coordination identity when team MCP tools are available | `team_manage` action `join` | `memorix team join --agentType <agent>` |",
+          "| Create or inspect tasks when team MCP tools are available | `team_task` | `memorix task create|list|claim|complete` |",
+          "| Send or read coordination messages when team MCP tools are available | `team_message` | `memorix message send|broadcast|inbox` |",
+          "| Share structured handoff when team MCP tools are available | `memorix_handoff` | `memorix handoff send` |",
+          "| Avoid file conflicts when team MCP tools are available | `team_file_lock` | `memorix lock lock|unlock|status` |",
+          "| Poll joined coordination state when team MCP tools are available | `memorix_poll` | `memorix poll` |",
           "",
           "## Boundaries",
           "",
+          "The standard setup uses the `lite` MCP profile. Coordination MCP tools are exposed only by `team` or `full`; use the CLI fallback for ordinary installations, or explicitly start the server with `--mode team`. Do not probe unavailable team tools in a loop.",
+          "",
           "- For ordinary memory, do not join coordination state.",
           "- For production multi-agent execution, prefer `memorix orchestrate` so the main process owns planning, dispatch, retries, and verification gates.",
           "- `memorix orchestrate` uses the current checkout for single-worker runs and task worktrees for parallel runs. Use `--isolated` to force worktree isolation, `--no-worktree` to disable it, `--allow-dirty` to run with uncommitted changes, and `--no-auto-merge` to preserve task worktrees for manual review.",
@@ -163231,6 +163264,8 @@ function getProjectConfigPath(agent, projectRoot) {
       return path33.join(projectRoot, ".agents", "hooks.json");
     case "gemini-cli":
       return path33.join(projectRoot, ".gemini", "settings.json");
+    case "workbuddy":
+      return "";
     default:
       return path33.join(projectRoot, ".memorix", "hooks.json");
   }
@@ -163264,6 +163299,8 @@ function getGlobalConfigPath(agent) {
       return path33.join(home, ".trae", "rules", "project_rules.md");
     case "dsh":
       return path33.join(process.env.DSH_HOME?.trim() || path33.join(home, ".dsh"), "AGENTS.md");
+    case "workbuddy":
+      return "";
     default:
       return path33.join(home, ".memorix", "hooks.json");
   }
@@ -163290,6 +163327,8 @@ function getAgentRulesPath(agent, root, global2 = false) {
         return path33.join(root, ".trae", "rules", "project_rules.md");
       case "dsh":
         return path33.join(process.env.DSH_HOME?.trim() || path33.join(root, ".dsh"), "AGENTS.md");
+      case "workbuddy":
+        return "";
       default:
         return path33.join(root, ".agent", "rules", "memorix.md");
     }
@@ -163316,6 +163355,8 @@ function getAgentRulesPath(agent, root, global2 = false) {
       return path33.join(root, ".trae", "rules", "project_rules.md");
     case "dsh":
       return path33.join(root, "AGENTS.md");
+    case "workbuddy":
+      return path33.join(root, "AGENTS.md");
     default:
       return path33.join(root, ".agent", "rules", "memorix.md");
   }
@@ -163404,6 +163445,11 @@ async function detectInstalledAgents() {
     agents.push("dsh");
   } catch {
   }
+  try {
+    await fs21.access(path33.join(home, ".workbuddy"));
+    agents.push("workbuddy");
+  } catch {
+  }
   return agents;
 }
 async function installHooks(agent, projectRoot, global2 = false) {
@@ -163417,6 +163463,16 @@ async function installHooks(agent, projectRoot, global2 = false) {
       }
     };
   }
+  if (agent === "workbuddy" && global2) {
+    return {
+      agent,
+      configPath: "",
+      events: [],
+      generated: {
+        note: "WorkBuddy has no hook system and no user-global guidance file \u2014 MCP only; no global guidance/hooks. Run `memorix setup --agent workbuddy` (without --global) to install project MCP config and AGENTS.md guidance."
+      }
+    };
+  }
   if (global2 && getGlobalConfigPath(agent) === "") {
     return {
       agent,
@@ -163499,6 +163555,17 @@ async function installHooks(agent, projectRoot, global2 = false) {
         }
       };
     }
+    case "workbuddy": {
+      const rulesPath = await installAgentRules(agent, projectRoot, global2);
+      return {
+        agent,
+        configPath: rulesPath,
+        events: [],
+        generated: {
+          note: "WorkBuddy has no hook system \u2014 installed AGENTS.md guidance only; the MCP row is installed by `memorix setup --agent workbuddy`."
+        }
+      };
+    }
     case "opencode": {
       const pluginContent = generateOpenCodePlugin();
       const pluginPath = global2 ? getGlobalConfigPath(agent) : getProjectConfigPath(agent, projectRoot);
@@ -163628,6 +163695,7 @@ async function installHooks(agent, projectRoot, global2 = false) {
   };
 }
 async function installAgentRules(agent, projectRoot, global2 = false) {
+  if (agent === "workbuddy" && global2) return "";
   const rulesContent = getAgentRulesContent(agent, global2 ? "global" : "project");
   const rulesRoot = global2 ? os5.homedir() : projectRoot;
   const rulesPath = getAgentRulesPath(agent, rulesRoot, global2);
@@ -163780,7 +163848,10 @@ alwaysApply: true
     "| `memorix_store` | Save something worth persisting |",
     '| `memorix_store_reasoning` | Save the "why" behind a decision |',
     "| `memorix_resolve` | Mark completed/outdated memories |",
-    "| `memorix_session_start` | Load session context (handoff, orchestration coordination) |"
+    "| `memorix_session_start` | Load session context (handoff, orchestration coordination) |",
+    "| `memorix_evidence` | Check a memory source, freshness, and verification state |",
+    "| `memorix_feedback` | Record whether a memory helped, conflicted, or was corrected |",
+    "| `memorix_media` | Inspect or import controlled local media |"
   ].join("\n");
 }
 async function uninstallHooks(agent, projectRoot, global2 = false) {
@@ -163790,6 +163861,9 @@ async function uninstallHooks(agent, projectRoot, global2 = false) {
   if (agent === "pi") {
     return false;
   }
+  if (agent === "workbuddy") {
+    return false;
+  }
   if (global2 && getGlobalConfigPath(agent) === "") {
     return false;
   }
@@ -167662,16 +167736,24 @@ function resolveToolProfile(opts) {
   return normalize(opts.explicit) ?? normalize(opts.envValue) ?? opts.fallback;
 }
 function describeProfile(profile) {
+  const count2 = countToolsInProfile(profile);
   switch (profile) {
     case "micro":
-      return "micro (agent-ready context + bounded recovery/media, ~9 tools)";
+      return `micro (agent-ready context + bounded recovery/media, ${count2} tools)`;
     case "lite":
-      return "lite (core memory + sessions, ~18 tools)";
+      return `lite (core memory + sessions, ${count2} tools)`;
     case "team":
-      return "team (lite + coordination tools + dashboard + knowledge workspace, ~26 tools)";
+      return `team (lite + coordination tools + dashboard + knowledge workspace, ${count2} tools)`;
     case "full":
-      return "full (all tools including advanced / KG-compat)";
+      return `full (all tools including advanced / KG-compat, ${count2} tools)`;
+  }
+}
+function countToolsInProfile(profile) {
+  let n = 0;
+  for (const name of Object.keys(TOOL_PROFILES)) {
+    if (isToolInProfile(name, profile)) n++;
   }
+  return n;
 }
 
 // src/server.ts
@@ -167816,7 +167898,7 @@ var MCP_SERVER_INFO_META_KEY = "io.modelcontextprotocol/serverInfo";
 function getMcpServerInfo() {
   return {
     name: "memorix",
-    version: true ? "1.8.4" : "1.0.1"
+    version: true ? "1.8.6" : "1.0.1"
   };
 }
 function createMcpDiscoverResult(capabilities, serverInfo) {

package/dist/types.d.ts

@@ -608,7 +608,7 @@ interface MemoryRef {
 /** MCP config format adapter interface */
 interface MCPConfigAdapter {
     /** Setup-only adapters may support a host that does not participate in workspace sync. */
-    readonly source: AgentTarget | 'codebuddy' | 'dsh';
+    readonly source: AgentTarget | 'codebuddy' | 'dsh' | 'workbuddy';
     /** Parse MCP server entries from a config file */
     parse(content: string): MCPServerEntry[];
     /** Generate config file content from MCP server entries */

package/docs/1.8.0-RELEASE-CANDIDATE-SPEC.md

@@ -1,6 +1,9 @@
-# Memorix 1.8.0 Release Candidate Specification
+# Memorix 1.8.5 Release Acceptance Specification
 
-Status: accepted implementation contract for Memorix 1.8.0.
+Status: accepted implementation contract for Memorix 1.8.5.
+
+This document keeps its historical filename for link stability. The current
+release contract supersedes the original 1.8.0 wording below.
 
 ## Acceptance Checklist
 
@@ -14,22 +17,25 @@ Status: accepted implementation contract for Memorix 1.8.0.
 - [x] Provide dashboard evidence/provenance views without replacing the existing UI.
 - [x] Preserve explicit project/session handles across restart and client shapes.
 - [x] Verify CLI fallback, Windows child-process hiding, HTTP old/new smoke, build, and package contents.
+- [x] Add the official MCP v2 transport path while retaining legacy clients.
+- [x] Reject unsupported durable Tasks explicitly instead of returning fake success.
 
 ## Compatibility Contract
 
 Memorix preserves the legacy 2025-era initialize contract, including stdio and
-stateful Streamable HTTP with `Mcp-Session-Id`. Memorix 1.8.4 also registers a
-low-level `server/discover` compatibility adapter for the 2026-07-28 request.
-Its `DiscoverResult` is complete for the required identity, versions,
-capabilities, and private zero-TTL cache hint. Versionless `tools/list` and
-`tools/call` are accepted by the pinned v1 SDK and retain its legacy result
-envelopes. The stdio startup gate reads bounded newline-delimited input before
-project initialization, answers discovery immediately, and replays all other
-messages in order; EOF is deferred until the queued input is released. HTTP
-stateless project handles remain a compatibility adapter: they
-own project routing, but do not turn the v1 SDK into a complete 2026 runtime.
-Tasks, subscriptions, and list-response caching are unsupported and are not
-advertised or simulated.
+stateful Streamable HTTP with `Mcp-Session-Id`. Memorix 1.8.5 uses the official
+MCP v2 transport for the modern stateless path and retains the legacy bridge
+for existing clients. The `server/discover` result is complete for the
+supported identity, versions, capabilities, result metadata, and private
+zero-TTL cache hint. Versionless `tools/list` and `tools/call` remain accepted
+for legacy clients. The stdio startup gate reads bounded newline-delimited
+input before project initialization, answers early discovery, and replays all
+other messages in order; EOF is deferred until queued input is released.
+Stateless HTTP project handles own project routing on the modern path.
+Subscriptions are supported with the official listen surface. Durable Tasks
+remain unsupported and are rejected explicitly because Memorix does not yet
+have a durable MCP task contract; list responses carry a zero-TTL hint rather
+than pretending to have a reusable server-side cache.
 
 Antigravity is the primary setup target. Gemini CLI remains a compatibility and
 migration path. GitHub issue #204 (WorkBuddy) is intentionally not merged or
@@ -73,8 +79,8 @@ is rejected for that task window.
 
 ## Explicit Non-goals for 1.8.0
 
-- No fake MCP Tasks/polling implementation when the pinned SDK does not expose
-  a durable server-side task contract.
+- No fake MCP Tasks/polling implementation when Memorix does not expose a
+  durable server-side task contract.
 - No remote memory hub, proxying of model traffic, or upstream installer.
 - No claim that the bundled Lite parser is a semantic CodeGraph.
 - No marketing landing page in place of an operator evidence console.

package/docs/AGENT_OPERATOR_PLAYBOOK.md

@@ -137,7 +137,7 @@ when the user wants:
 - explicit task/message/handoff/lock coordination
 - one shared HTTP service process
 
-Default recommendation: if the user wants memory inside an existing IDE or agent, start with `memorix setup --agent <agent> --global`. Use `memorix serve` only for manual MCP wiring. Use the CLI for direct workflows and automation because it does not depend on an IDE's MCP session lifecycle. Use memcode only when the user wants the bundled terminal agent. Reach for HTTP only when a shared background service, multi-client MCP access, Docker, or a live dashboard endpoint is actually needed.
+Default recommendation: if the user wants memory inside an existing IDE or agent, start with `memorix setup --agent <agent> --global`. Use `memorix serve` only for manual MCP wiring. Use the CLI for direct workflows and automation because it does not depend on an IDE's MCP session lifecycle. Use memcode only when the user wants the bundled terminal agent. Reach for HTTP only when a shared background service, multi-client MCP access, a VPS Docker deployment, or a live dashboard endpoint is actually needed. Local development runs Node directly.
 
 Use:
 
@@ -826,7 +826,7 @@ read this document first, then act.
 This playbook is the canonical AI-facing guide for installation, project binding, integration, hooks, troubleshooting, and safe usage.
 ## Docker Note
 
-When Memorix runs in Docker, treat it as an **HTTP service deployment**, not a stdio MCP process.
+When Memorix runs in Docker on a VPS/hosted machine, treat it as an **HTTP service deployment**, not a stdio MCP process. Docker is not required for local development.
 
 - Connect IDEs and agents to `http://host:3211/mcp`
 - Use `memorix_session_start(projectRoot=...)` with a path that is visible **inside** the container

package/docs/API_REFERENCE.md

@@ -28,7 +28,7 @@ Use **MCP** when:
 Use the **CLI** when:
 
 - you want to inspect or change project state from a terminal
-- you are on SSH / Docker / CI / NAS and want direct commands
+- you are on SSH / VPS Docker / CI / NAS and want direct commands
 - you want readable, namespaced actions instead of raw MCP tool payloads
 - you want full access to Memorix CLI capabilities without depending on an MCP client
 
@@ -150,17 +150,19 @@ feedback projection.
 ### MCP Compatibility
 
 Legacy clients use stateful Streamable HTTP with `Mcp-Session-Id` and the
-2025-era `initialize` handshake. The 1.8.4 stdio server starts a bounded
+2025-era `initialize` handshake. The 1.8.6 stdio server starts a bounded
 newline-delimited JSON-RPC gate before project initialization: it answers the
 2026-07-28 `server/discover` request before `initialize`, then replays other
 requests, notifications, and responses in order into the pinned SDK transport.
 Versionless `tools/list` and `tools/call` use the SDK's legacy result envelopes.
-HTTP stateless clients may use a durable
-`Mcp-Project-Handle`; `/protocol-diagnostics` labels this as compatibility-only.
-Modern result metadata is discovery-only with a private zero-TTL hint. Tasks,
-subscriptions, and list-response caching are unsupported. When MCP discovery
-is unavailable, use one bounded `memorix context --fallback` request for a
-task; repeated fallback probing is rejected by the local budget.
+HTTP modern clients may use the stateless `2026-07-28` path and a durable
+`Mcp-Project-Handle`; `/protocol-diagnostics` reports this as supported.
+Modern result metadata is returned for discovery, list, and call responses.
+The official subscriptions listen surface is available, but Memorix has no
+durable Tasks implementation, so task requests remain explicitly unsupported.
+List responses carry a private zero-TTL hint, not a reusable server-side cache.
+When MCP discovery is unavailable, use one bounded `memorix context --fallback`
+request for a task; repeated fallback probing is rejected by the local budget.
 
 The built-in Lite provider indexes common code files with lightweight file, symbol, and import facts. It is a structural fallback, not a language-server-quality graph. When a project already has a healthy local CodeGraph index, `[codegraph].external_context = "auto"` may add a validated, bounded semantic outline to the Workset. Memorix never initializes, syncs, or exports that external index, and never stores its raw source output. `memorix codegraph status --json`, `memorix doctor --json`, and Project Context JSON identify the actual provider quality.
 

package/docs/DASHBOARD.md

@@ -7,6 +7,19 @@ used by MCP and CLI. It shows each card's source reference, locator, captured
 hash, freshness, verification state, and audit-event count. It is project
 scoped and does not replace the underlying observation or code source.
 
+## Surface Boundaries
+
+Each Dashboard page maps to a real data surface: Overview shows overall state,
+Git Memory shows Git-derived memory, Knowledge shows source-backed knowledge
+pages, Memory Map shows the evidence-backed relation projection, Observations
+and Evidence show records and provenance, Retention/Config/Identity show
+runtime health, and Sessions/Coordination show session and persistent
+coordination state.
+
+These pages are not demo panels. Empty data is shown as empty, and failed reads
+are shown as unavailable; the UI does not substitute another data model or old
+graph renderer to make a result look healthy.
+
 ## Start
 
 ```bash
@@ -25,6 +38,16 @@ The Coordination Status page is a read-only projection of the selected project's
 
 The page reports agents, task status, file locks, and handoffs for the selected project. It exposes no team or task write endpoints and is not a task execution or full orchestration platform. If the SQLite read fails, the API returns an explicit degraded/error status and the page shows that the status is unavailable instead of presenting an empty result as healthy.
 
+## Memory Map
+
+The Graph page is the single visual graph surface. It renders the deterministic,
+source-backed `GET /api/knowledge-graph` projection with Apache ECharts. The
+older Cytoscape/Dagre renderer is removed from the Dashboard, so an empty or
+failed Memory Map no longer silently falls back to a different graph model.
+
+`GET /api/graph` remains available as a backend compatibility route for MCP,
+CLI, scripts, and older clients. It is not the Dashboard's visual data source.
+
 ## Maintenance Workbench
 
 The Observations page exposes three explicit maintenance actions:

package/docs/DEVELOPMENT.md

@@ -13,8 +13,8 @@ Memorix is a TypeScript project built around:
 
 ## Current Development Baseline
 
-The current release work targets the **1.8.4 release line** and package metadata
-is kept at `1.8.4` for this release commit.
+The current release work targets the **1.8.6 release line** and package metadata
+is kept at `1.8.6` for this release commit.
 
 Contributors should assume the following areas are part of the current release line:
 

package/docs/DOCKER.md

@@ -1,6 +1,9 @@
 # Docker Deployment
 
-Memorix supports Docker as an **HTTP service deployment path**.
+Memorix supports Docker as a **VPS/hosted HTTP service deployment path**.
+
+Local development and verification should run the Node service directly. Do
+not start Docker Desktop or build a local image just to use Memorix.
 
 This Docker flow is for:
 
@@ -83,7 +86,7 @@ It is not a promise that stdio MCP magically becomes container-friendly.
 
 ## Important Path Truth
 
-Docker works best when Memorix can **see the repositories it is asked to bind**.
+VPS Docker works best when Memorix can **see the repositories it is asked to bind**.
 
 Project-scoped features such as:
 
@@ -97,7 +100,7 @@ depend on the HTTP service being able to access the repository path.
 
 ### Good fit
 
-- Docker Desktop on the same machine as your IDE
+- a VPS or hosted machine that can see the repositories it is asked to bind
 - a compose setup that mounts the repo you are working on into the container
 - `memorix_session_start(projectRoot=...)` using a path visible **inside** the container
 

package/docs/INTEGRATIONS.md

@@ -26,7 +26,7 @@ That command installs the recommended Memorix package or config for the target a
 | memcode | Opens a terminal coding agent that already uses Memorix memory | `memorix`, `memcode` |
 | HTTP service | Runs one shared MCP endpoint plus dashboard | `memorix background start` |
 
-HTTP is not required for normal agent setup. Use it when you intentionally want a shared background process, dashboard, Docker deployment, or multiple clients using the same MCP endpoint.
+HTTP is not required for normal agent setup. Use it when you intentionally want a shared background process, dashboard, VPS Docker deployment, or multiple clients using the same MCP endpoint. Local verification runs the Node service directly; Docker is not required on a developer machine.
 
 CLI, MCP, and HTTP have separate jobs:
 
@@ -64,6 +64,7 @@ Generated guidance also has scope:
 | Antigravity | `memorix setup --agent antigravity --global` | **Primary supported target** | Plugin under `~/.gemini/config/plugins/memorix` or `.agents/plugins/memorix`, with `plugin.json`, `mcp_config.json`, `hooks.json`, rules, and skills | Uses Antigravity's official plugin layout. Dedicated MCP configs live at `~/.gemini/config/mcp_config.json` or `.agents/mcp_config.json`; legacy Gemini settings are read only for compatibility. |
 | Trae | `memorix setup --agent trae --global` | Trae MCP/rules config | MCP config and `.trae/rules/project_rules.md` | Current support is MCP plus project rules. |
 | DeepSeek Harness | `memorix setup --agent dsh --global` | DeepSeek Harness MCP patch | Memorix `@deepseek-ai/dsh-mcp-client` row in `$DSH_HOME/cordis.patch.yml` (default `~/.dsh/cordis.patch.yml`), guidance in the harness `AGENTS.md`, and official skills under `$DSH_HOME/skills` | Tools appear as `mcp__memorix__*`. No hooks surface. Project-local setup writes project `AGENTS.md` guidance and `.dsh/skills`; the MCP row always lives in the harness-level patch file. |
+| WorkBuddy | `memorix setup --agent workbuddy [--global]` | WorkBuddy MCP config | Memorix MCP server row in `<project>/.workbuddy/mcp.json` (project install) or `~/.workbuddy/mcp.json` (global), plus `AGENTS.md` guidance | Tools appear as `mcp__memorix__*`. No hooks surface. |
 | memcode | `memorix` or `memcode` | Bundled terminal agent | Built-in Memorix memory access | memcode uses the same project memory pool; it is not a separate memory silo. |
 | Any MCP client | Manual MCP config | MCP stdio or HTTP | `memorix serve` or `memorix background start` | Use stdio first unless you need a shared HTTP endpoint. |