@cerefox/memory 1.19.1 → 1.19.2

package/dist/frontend/index.html

@@ -15,7 +15,7 @@
       href="https://fonts.googleapis.com/css2?family=Geist:wght@300;400;500;600;700&display=swap"
     />
     <title>Cerefox</title>
-    <script type="module" crossorigin src="/app/assets/index-HNs8rgY1.js"></script>
+    <script type="module" crossorigin src="/app/assets/index-CQcG9JWM.js"></script>
     <link rel="stylesheet" crossorigin href="/app/assets/index-01k5C3sG.css">
   </head>
   <body>

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.19.1";
+export const EF_VERSION = "1.19.2";
 
 /**
  * The Cerefox RELEASE version — what `cerefox --version` reports and what npm
@@ -36,7 +36,7 @@ export const EF_VERSION = "1.19.1";
  * is imported by the Deno Edge Functions, which cannot reach into the npm
  * package.
  */
-export const CEREFOX_VERSION = "1.19.1";
+export const CEREFOX_VERSION = "1.19.2";
 
 /**
  * The most recent version whose EF-side SOURCE actually changed (#127).

package/docs/guides/api.md

@@ -233,6 +233,20 @@ so you can re-read without a second round trip. Sending no hash (and no
 (a file you are syncing, say) makes a conflict meaningless; there is no implicit
 default. Creating a new document needs no hash.
 
+**Metadata has its own token** (v1.19.0). `GET /documents/{id}` also returns
+`metadata_revision`, which goes up by one whenever the metadata changes.
+
+- `POST /documents/{id}/edit` **replaces** the whole metadata object, so send
+  `expected_metadata_revision` with `metadata`. A stale one is a `409` with
+  `error: "metadata_conflict"`: re-read, reapply your change and retry. Sending
+  none is accepted for now as last-write-wins, with a `warnings` entry in the
+  response and `[last-write-wins]` in the audit log; a future release will
+  require it, announced in advance.
+- A content update through `POST /ingest` **merges** `metadata`: keys you send
+  are set, keys you leave out are kept, and a key sent as `null` is removed.
+  `metadata: {}` changes nothing. `expected_metadata_revision` is optional
+  there.
+
 **Check the status code, not just the body.** Every refusal is a real HTTP
 status: `400` for a malformed or incomplete request (including a body field the
 route does not know, which is refused rather than ignored), `404` for a missing

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cerefox/memory",
-  "version": "1.19.1",
+  "version": "1.19.2",
   "description": "Cerefox \u2014 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",