@cerefox/memory 1.3.0-beta.3 → 1.3.0

package/AGENT_GUIDE.md

@@ -163,6 +163,16 @@ Change parts of a document: **one to many operations applied atomically in a sin
 
 **Put changes that belong together in ONE call.** Operations apply in order against the evolving document (op 2 sees op 1's result), and a half-applied state is impossible — so a table row and the running total it feeds cannot end up disagreeing. If any operation fails (bad anchor, ambiguity), nothing at all is written and the error names the failing operation.
 
+**When NOT to use partial edits.** They are for localized changes. If what you
+are changing recurs across the document — a "last updated" date in the header, a
+heading, and the footer — that is a whole-document change wearing a local
+disguise, and `cerefox_ingest` is the right tool. Section-scoped edits would take
+several calls, each individually valid, with the document briefly inconsistent
+between them. An agent hit exactly this and correctly stopped rather than
+contorting the tools. Related: **a heading's own text cannot be changed** —
+`replace_section` preserves it by design — so a stale date inside a heading needs
+a re-ingest too.
+
 **One sharp edge worth knowing.** A section runs to the next heading of the same
 or higher level — **or to the end of the document**. So the last section owns
 everything appended after it: an `end_of_document` insert becomes part of that

package/dist/bin/cerefox.js

@@ -7438,7 +7438,7 @@ var exports_meta = {};
 __export(exports_meta, {
   PKG_VERSION: () => PKG_VERSION
 });
-var PKG_VERSION = "1.3.0-beta.3";
+var PKG_VERSION = "1.3.0";
 var init_meta = () => {};
 
 // ../../_shared/config/paths.ts
@@ -70216,10 +70216,8 @@ function buildServer() {
       const text = await tool.handler(supabase, args, ctx);
       return { content: [{ type: "text", text }] };
     } catch (err) {
-      if (err instanceof McpInvalidParams)
-        throw err;
       const message = err instanceof Error ? err.message : String(err);
-      throw new Error(message);
+      return { content: [{ type: "text", text: message }], isError: true };
     }
   });
   return {
@@ -76321,8 +76319,8 @@ import { homedir as homedir6 } from "node:os";
 import { join as join9 } from "node:path";
 
 // ../../_shared/ef-meta/index.ts
-var EF_VERSION = "1.3.0-beta.3";
-var EF_LAST_CHANGED = "1.3.0-beta.3";
+var EF_VERSION = "1.3.0";
+var EF_LAST_CHANGED = "1.3.0-beta.4";
 
 // src/cli/util/checks.ts
 init_config();

package/dist/server-assets/_shared/ef-meta/index.ts

@@ -18,7 +18,7 @@
  * doesn't touch `supabase/functions/` leaves it alone).
  */
 
-export const EF_VERSION = "1.3.0-beta.3";
+export const EF_VERSION = "1.3.0";
 
 /**
  * The most recent version whose EF-side SOURCE actually changed (#127).
@@ -28,7 +28,7 @@ export const EF_VERSION = "1.3.0-beta.3";
  * `cut_release.ts` ONLY when EF source changed since the last tag; doctor
  * uses it to stay silent on label-only drift.
  */
-export const EF_LAST_CHANGED = "1.3.0-beta.3";
+export const EF_LAST_CHANGED = "1.3.0-beta.4";
 
 /**
  * The 8 peer EFs the cerefox-mcp aggregator probes (excludes cerefox-mcp

package/dist/server-assets/supabase/functions/cerefox-mcp/index.ts

@@ -176,9 +176,18 @@ async function handleToolsCall(
       result: { content: [{ type: "text", text }] },
     });
   } catch (err) {
+    // Tool failures are RESULTS, not protocol errors — same rule as the local
+    // stdio server (packages/memory/src/server.ts), and for the same reason:
+    // a client may render a JSON-RPC error however it likes, and at least one
+    // major one replaces the body with a generic failure dialog. The message is
+    // the actionable part; it has to travel where the model can read it.
+    // Protocol errors above this point (unknown tool, bad JSON) are unchanged.
     const message = err instanceof Error ? err.message : String(err);
-    const code = err instanceof McpInvalidParams ? -32602 : -32603;
-    return errorResponse(id, code, message);
+    return jsonResponse({
+      jsonrpc: "2.0",
+      id,
+      result: { content: [{ type: "text", text: message }], isError: true },
+    });
   }
 }
 

package/docs/guides/migration-1.0.md

@@ -61,7 +61,9 @@ The migration is **lazy and safe**:
 - Existing documents keep the legacy format and reconstruct **exactly as before** — nothing
   re-processes, nothing re-embeds.
 - A document moves to the new format automatically the next time it is edited/saved. To
-  convert everything now instead, run `cerefox server reindex`.
+  convert everything now instead, run `cerefox server migrate-format` (v1.1.0-beta.4 or
+  later). **Not `cerefox server reindex`** — reindex re-embeds chunks in place and never
+  re-chunks, so the stored format does not advance (#164).
 - `cerefox doctor` shows how many documents still use the legacy format.
 
 Details: `cerefox guides show content-format` (or [`content-format.md`](content-format.md)).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cerefox/memory",
-  "version": "1.3.0-beta.3",
+  "version": "1.3.0",
   "description": "Cerefox — user-owned shared memory for AI agents. CLI + stdio MCP server + web UI + ingestion for a knowledge base on your own Supabase project (or fully self-hosted with Cerefox Local).",
   "license": "Apache-2.0",
   "homepage": "https://github.com/fstamatelopoulos/cerefox",