@bli-cockpit/memory-mcp 0.1.1 → 0.1.3

package/README.md

@@ -132,6 +132,14 @@ memories it has today. The **remote** is the identity, so every worktree of one
 repo shares a space. A folder that is not a git repository still gets its own
 space (`dir_<name>__<sha16>`), because a folder is a legitimate workspace.
 
+One repository can still have TWO tags on the shelf — the vendor's, kept
+verbatim when its memories were imported, and the one derived above. Tower
+reconciles them server-side (`agent_memory_container_aliases`, BLI-3620):
+`search_memory` is answered from every tag that names the same space, and
+`save_memory` lands in the canonical one. That is why a saved memory can report
+a space you did not pass — the tool names where the row actually went, not what
+it asked for.
+
 ## The stdio contract
 
 **stdout carries the JSON-RPC stream and nothing else.** Every operational

package/dist/server.js

@@ -200,6 +200,11 @@ export function createServer(deps) {
         return textResult(lines.join("\n"), {
             query: args.query,
             containerTag,
+            // BLI-3620: every space the door actually searched. One repository can
+            // have two container tags — the vendor's and the one this scheme
+            // derives — and the alias table is what makes a question asked under
+            // either find both. Echoed so a caller can see it happened.
+            searchedContainerTags: response.body.containerTags ?? [containerTag],
             results,
             recent,
             degraded: response.body.degraded ?? null,
@@ -227,10 +232,16 @@ export function createServer(deps) {
             return doorFailure("save", response);
         const outcome = String(response.body.outcome ?? "created");
         const id = response.body.id === null ? "—" : String(response.body.id ?? "—");
+        // BLI-3620: the space the SERVER used, which is the canonical tag when
+        // this repository has more than one on the shelf. Saying the tag we sent
+        // would name a space the row is not in.
+        const landedIn = typeof response.body.containerTag === "string" && response.body.containerTag
+            ? response.body.containerTag
+            : containerTag;
         const embedNote = response.body.embedded === false && response.body.embedSkippedReason
             ? ` It was stored without a search vector (${String(response.body.embedSkippedReason)}), so it is findable by keyword and not yet by meaning.`
             : "";
-        return textResult(`Memory ${outcome} in ${containerTag} (id: ${id}).${embedNote}`, response.body);
+        return textResult(`Memory ${outcome} in ${landedIn} (id: ${id}).${embedNote}`, response.body);
     });
     server.registerTool("update_memory", {
         title: "Correct a memory",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bli-cockpit/memory-mcp",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "private": false,
   "description": "BLI Memory — an MCP server for the memory layer BLI owns (save, search, update, forget).",
   "type": "module",
@@ -28,7 +28,7 @@
     "start": "node dist/index.js"
   },
   "dependencies": {
-    "@bli-cockpit/telemetry-core": "0.1.26",
+    "@bli-cockpit/telemetry-core": "0.1.28",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^4.3.6"
   },