fix(mcp): render full detailed recall metadata

Author: jack-arturo

docs/METADATA_BEHAVIOR.md

@@ -23,10 +23,9 @@ on memories. It is intentionally a product/runtime spec, not an experiment note.
   on the caller path.
 - The MCP server's `json` recall format passes the raw response through, so it
   exposes the full metadata object. The MCP `detailed` format renders a
-  size-capped `Metadata:` line (single-line JSON truncated to 300 characters
-  with a trailing ellipsis) plus an `Updated:` line when present, and omits the
-  metadata line entirely for empty or missing metadata. The `text` and `items`
-  formats do not include metadata.
+  full `Metadata:` line as single-line JSON plus an `Updated:` line when
+  present, and omits the metadata line entirely for empty or missing metadata.
+  The `text` and `items` formats do not include metadata.
 - Final scoring can use metadata terms as weak evidence for candidates that are
   already present from another channel.
 

mcp-sse-server/server.js

@@ -19,7 +19,6 @@ const DEFAULT_UPSTREAM_MAX_RETRIES = 2;
 const DEFAULT_HEALTH_TIMEOUT_MS = 5000;
 const DEFAULT_HEALTH_PROBE_INTERVAL_MS = 30000;
 const TRANSIENT_STATUS_CODES = new Set([408, 429, 502, 503, 504]);
-const DETAILED_METADATA_MAX_CHARS = 300;
 
 function readIntEnv(name, fallback) {
   const raw = process.env[name];
@@ -391,10 +390,7 @@ export function formatRecallAsItems(results, { detailed = false } = {}) {
         metaJson = '';
       }
       if (metaJson && metaJson !== '{}') {
-        const capped = metaJson.length > DETAILED_METADATA_MAX_CHARS
-          ? `${metaJson.slice(0, DETAILED_METADATA_MAX_CHARS)}…`
-          : metaJson;
-        lines.push(`Metadata: ${capped}`);
+        lines.push(`Metadata: ${metaJson}`);
       }
     }
     if (score !== undefined) lines.push(`Score: ${score.toFixed(3)}`);

mcp-sse-server/test/server.test.js

@@ -125,7 +125,7 @@ test("formatRecallAsItems supports detailed output including relations", () => {
   assert.ok(!compact.includes("Metadata:"));
 });
 
-test("formatRecallAsItems detailed output caps metadata size and omits empty metadata", () => {
+test("formatRecallAsItems detailed output renders full metadata and omits empty metadata", () => {
   const bigMetadata = { notes: "x".repeat(400) };
   const results = [
     {
@@ -144,9 +144,7 @@ test("formatRecallAsItems detailed output caps metadata size and omits empty met
   const metadataLine = big.split("\n").find(line => line.startsWith("Metadata: "));
   assert.ok(metadataLine, "expected a Metadata line for oversized metadata");
   const rendered = metadataLine.slice("Metadata: ".length);
-  assert.ok(rendered.endsWith("…"));
-  assert.equal(rendered.length, 301); // 300 chars + ellipsis
-  assert.equal(rendered.slice(0, 300), JSON.stringify(bigMetadata).slice(0, 300));
+  assert.equal(rendered, JSON.stringify(bigMetadata));
 
   assert.ok(!empty.includes("Metadata:"));
   assert.ok(!none.includes("Metadata:"));