@cerefox/memory 1.12.1 → 1.13.1

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

@@ -344,7 +344,8 @@ Deno.serve(async (req: Request) => {
 
   const contentHash = await sha256hex(normalizeContent(content));
   const headers = { "Content-Type": "application/json", "Access-Control-Allow-Origin": "*" };
-  const reviewStatus = author_type === "agent" ? "pending_review" : "approved";
+  // review_status is decided by cerefox_ingest_document from author_type and
+  // the store's review_workflow_enabled flag (#241); the EF no longer sends it.
 
   // ── ID-based update path ────────────────────────────────────────────────────
   // When document_id is provided, update that exact document regardless of
@@ -424,7 +425,6 @@ Deno.serve(async (req: Request) => {
       p_source: source,
       p_content_hash: contentHash,
       p_metadata: metadata,
-      p_review_status: reviewStatus,
       p_chunks: chunkData,
       p_author: author,
       p_author_type: author_type,
@@ -543,7 +543,6 @@ Deno.serve(async (req: Request) => {
         p_source: source,
         p_content_hash: contentHash,
         p_metadata: metadata,
-        p_review_status: reviewStatus,
         p_chunks: chunkData,
         p_author: author,
         p_author_type: author_type,
@@ -655,7 +654,6 @@ Deno.serve(async (req: Request) => {
     p_source: source,
     p_content_hash: contentHash,
     p_metadata: metadata,
-    p_review_status: reviewStatus,
     p_chunks: chunkData,
     p_author: author,
     p_author_type: author_type,

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

@@ -105,12 +105,12 @@ async function handleToolsCall(
 
   // Configurable caller identity enforcement.
   // When require_requestor_identity is "true" in cerefox_config, all tool calls
-  // must include a requestor (reads) or author (writes) parameter.
-  // When requestor_identity_format is set, the value must match the regex.
-  const identityParam = toolName === "cerefox_ingest" || toolName === "cerefox_set_document_projects"
-    ? "author"
-    : "requestor";
-  const identityValue = args[identityParam] as string | undefined;
+  // must include the caller's identity; when requestor_identity_format is set,
+  // the value must match the regex. Since v1.13.1 every tool takes `author`
+  // and silently accepts `requestor` as the pre-1.13.1 alias (mirrors
+  // `callerIdentity()` in _shared/mcp-tools/identity.ts).
+  const identityParam = "author";
+  const identityValue = (args.author ?? args.requestor) as string | undefined;
 
   // deno-lint-ignore no-explicit-any
   const supabase: any = makeSupabaseClient();

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

@@ -2,6 +2,7 @@ import "jsr:@supabase/functions-js/edge-runtime.d.ts";
 import { createClient } from "jsr:@supabase/supabase-js@2";
 import { isVersionRequest, versionResponse } from "../../../_shared/ef-meta/index.ts";
 import { efAuthGate } from "../../../_shared/ef-auth/index.ts";
+import { reviewWorkflowEnabled } from "../../../_shared/mcp-tools/feature-flags.ts";
 
 /**
  * cerefox-metadata-search -- Supabase Edge Function
@@ -27,7 +28,9 @@ import { efAuthGate } from "../../../_shared/ef-auth/index.ts";
  *   include_content  boolean      optional  Include full text (default: false)
  *   max_bytes        number       optional  Byte budget when include_content=true
  *
- * Response (200): Array of matching documents
+ * Response (200): Array of matching documents. `review_status` is present
+ *                 only while the review workflow is on (#241); with the flag
+ *                 off the key is absent, as on every other surface.
  * Response (400): { error: "..." }
  */
 
@@ -160,7 +163,14 @@ Deno.serve(async (req: Request): Promise<Response> => {
       p_project_id: project_id,
     })).catch(() => {});
 
-    return new Response(JSON.stringify(data ?? []), {
+    // Presentation only: the same shared reader every other surface uses.
+    const rows = (data ?? []) as Array<Record<string, unknown>>;
+    const showReview = await reviewWorkflowEnabled(supabase);
+    const out = showReview
+      ? rows
+      : rows.map(({ review_status: _hidden, ...rest }) => rest);
+
+    return new Response(JSON.stringify(out), {
       status: 200,
       headers: { ...CORS_HEADERS, "Content-Type": "application/json" },
     });

package/docs/guides/access-paths.md

@@ -265,7 +265,7 @@ before "completing" the parity table by adding purge to agent-facing access path
 | Tier | Operations | Reversible? | Where exposed |
 |---|---|---|---|
 | 1. Reads + soft mutations | search, get, list-*, ingest (create/update), metadata-search, get-audit-log | n/a (reads) / yes (versioned) | All paths — MCP, Edge Functions, CLI, web UI |
-| 2. Soft-destructive + recovery | `delete_document` (soft delete to trash), `restore_document` (un-trash), `set_review_status` | yes — delete is restorable; restore recovers | CLI (`cerefox document delete` / `restore`), web UI, and — since v1.7.0 (#208, #210) — MCP (`cerefox_delete_document`, which requires the caller's read-hash, and `cerefox_restore_document`). **Not** the primitive GPT-Actions Edge Functions (deliberately deferred). |
+| 2. Soft-destructive + recovery | `delete_document` (soft delete to trash), `restore_document` (un-trash), `set_review_status` (web only; a `404` while `review_workflow_enabled` is off) | yes — delete is restorable; restore recovers | CLI (`cerefox document delete` / `restore`), web UI, and — since v1.7.0 (#208, #210) — MCP (`cerefox_delete_document`, which requires the caller's read-hash, and `cerefox_restore_document`). **Not** the primitive GPT-Actions Edge Functions (deliberately deferred). |
 | 3. **Hard-destructive** | `purge_document` (permanent), `set_version_archived` (toggle version retention) | no (purge) | **Web UI only** |
 
 ### Why purge is web-UI-only

package/docs/guides/cli.md

@@ -50,7 +50,7 @@ cerefox document ingest --paste --title "<title>" [OPTIONS]   # stdin
 | `--last-write-wins` | — | flag | off | Skip the concurrency check and overwrite regardless of concurrent changes. For re-sync flows where an external source of truth makes conflicts meaningless. Recorded in the audit log. |
 | `--source` | — | str | `paste` / `file` | Source label recorded on the document. |
 | `--author` | — | str | `CEREFOX_AUTHOR_NAME` or `unknown` | Audit-log author identity. |
-| `--author-type` | — | `user`\|`agent` | `CEREFOX_AUTHOR_TYPE` or `user` | Caller type. Agent writes auto-routed to `pending_review`. |
+| `--author-type` | — | `user`\|`agent` | `CEREFOX_AUTHOR_TYPE` or `user` | Caller type. Agent writes are recorded `pending_review`, user writes `approved`; the store's `review_workflow_enabled` flag decides whether that status is shown. |
 
 **Examples**:
 ```bash
@@ -216,7 +216,7 @@ cerefox document list [OPTIONS]
 | `--deleted` | flag | off | List soft-deleted (trashed) documents instead of active ones, newest-deleted first. Pair the ids with `cerefox document restore` / `cerefox document delete`. |
 | `--json` | flag | off | Machine-readable JSON output. |
 
-**Output**: tabular `id | title | source | status | updated_at` listing (or `deleted_at` with `--deleted`).
+**Output**: tabular `id | title | source | status | updated_at` listing (or `deleted_at` with `--deleted`). The `status` column (and the `review_status` key in `--json`) is present only while the review workflow is on — see `review_workflow_enabled` in [configuration.md](configuration.md#review-workflow).
 
 **MCP equivalent**: scope-by-project / metadata / time listing maps to [`cerefox_metadata_search`](../../AGENT_GUIDE.md) — e.g. `cerefox_metadata_search(project_name="research")` lists that project's documents (the `metadata_filter` may be empty when another scope is supplied). The `--deleted` (trash) view and unscoped whole-KB listing remain CLI-only.
 
@@ -506,6 +506,8 @@ cerefox metadata search --metadata-filter '{"type":"decision-log"}' --updated-si
 cerefox metadata search --metadata-filter '{"status":"active"}' --project-name "research" --include-content
 ```
 
+**Output**: a `## title [id: …]` block per document with its metadata, projects, size, review status and update date (plus content with `--include-content`), or JSON with `--json`. As with `document list`, the review status (and the `review_status` key in `--json`) is present only while the review workflow is on — see `review_workflow_enabled` in [configuration.md](configuration.md#review-workflow).
+
 **MCP equivalent**: [`cerefox_metadata_search`](../../AGENT_GUIDE.md).
 
 ---
@@ -702,11 +704,16 @@ Agents see 15 tools with the flag off and 19 with it on. See
 
 **Synopsis**:
 ```
-cerefox config list           # all current key/value pairs
+cerefox config list [--json]  # every settable key, grouped, with kind + default (from the shared catalog)
 cerefox config get KEY
 cerefox config set KEY VALUE [--author NAME] [--author-type user|agent]
 ```
 
+`config list` is derived from the same catalog the web Settings page renders
+(v1.13.0, #239 — the earlier hand-written list had drifted and hid three
+working keys). `--json` returns `{ keys: string[], catalog: [{ key, kind,
+default, group, description }] }`; `keys` keeps its pre-1.13 shape.
+
 Since v1.9.0 every `config set` is recorded in the audit log by the server
 itself (`config-change`, with the old → new value), in the same transaction
 as the write — pass `--author` (or set `CEREFOX_AUTHOR_NAME`) so the entry
@@ -766,7 +773,7 @@ These flat commands handle install, configuration, and health. Run any with `--h
 | Command | Purpose |
 |---|---|
 | `cerefox init` | Interactive first-run setup; writes `~/.cerefox/.env`, offers `server deploy` + self-docs ingest. |
-| `cerefox doctor` | Diagnose the install (credentials, DB reachability, schema version). |
+| `cerefox doctor` | Diagnose the install (credentials, DB reachability, schema version, whether the review workflow is on). |
 | `cerefox status` | Show connection + schema status. |
 | `cerefox configure-agent --tool <client>` | Write MCP client config (`claude-code`, `claude-desktop`, `cursor`, `codex`, `gemini`). |
 | `cerefox token generate` / `rotate` / `list` | Manage the Cerefox access token (`cfx_pat_…`) — the Edge Function Bearer credential (remote MCP, GPT Actions, curl). See the [`cerefox token`](#cerefox-token-generate--cerefox-token-rotate--cerefox-token-list) section above. |
@@ -804,21 +811,21 @@ Every MCP parameter has an exact-name CLI flag (kebab-cased). Short forms exist
 
 | MCP tool | CLI command |
 |---|---|
-| `cerefox_search(query, match_count, project_name, metadata_filter, requestor)` | `cerefox search "<q>" --match-count N --project-name <name> --metadata-filter '<json>' --requestor <name>` |
+| `cerefox_search(query, match_count, project_name, metadata_filter, author)` | `cerefox search "<q>" --match-count N --project-name <name> --metadata-filter '<json>' --requestor <name>` |
 | `cerefox_ingest(title, content, project_name, metadata, update_if_exists, document_id, expected_content_hash, last_write_wins, source, author, author_type)` (file) | `cerefox document ingest <path> --title <t> --project-name <n> --metadata '<json>' --update-if-exists\|--document-id <uuid> --expected-content-hash <hash>\|--last-write-wins --source <s> --author <a> --author-type <t>` |
 | `cerefox_ingest(...)` (paste) | `printf '...' \| cerefox document ingest --paste --title "<t>"` (same flags) |
-| `cerefox_get_document(document_id, version_id, outline, requestor)` | `cerefox document get <id> --version-id <vid> --outline --requestor <name>` |
-| `cerefox_insert(document_id, text, position, anchor_heading, section_part, expected_content_hash, requestor)` | `cerefox document insert <id> -t <text\|-\|@file> -p <position> -a <anchor> --section-part <part> --expected-hash <hash> --requestor <name>` |
-| `cerefox_edit(document_id, operations, expected_content_hash, requestor)` | `cerefox document edit-parts <id> -o <json\|-\|@file> --expected-hash <hash> --requestor <name>` |
-| `cerefox_list_versions(document_id, requestor)` | `cerefox document version list <id> --requestor <name>` |
-| `cerefox_list_projects(requestor)` | `cerefox project list --requestor <name>` |
+| `cerefox_get_document(document_id, version_id, outline, author)` | `cerefox document get <id> --version-id <vid> --outline --requestor <name>` |
+| `cerefox_insert(document_id, text, position, anchor_heading, section_part, expected_content_hash, author)` | `cerefox document insert <id> -t <text\|-\|@file> -p <position> -a <anchor> --section-part <part> --expected-hash <hash> --requestor <name>` |
+| `cerefox_edit(document_id, operations, expected_content_hash, author)` | `cerefox document edit-parts <id> -o <json\|-\|@file> --expected-hash <hash> --requestor <name>` |
+| `cerefox_list_versions(document_id, author)` | `cerefox document version list <id> --requestor <name>` |
+| `cerefox_list_projects(author)` | `cerefox project list --requestor <name>` |
 | `cerefox_set_document_projects(document_id, project_names, author)` | `cerefox document set-projects <id> <name...> --author <a> --author-type <t>` (or `--clear` to remove all) |
 | `cerefox_list_metadata_keys()` | `cerefox metadata keys` |
-| `cerefox_metadata_search(metadata_filter, project_name, updated_since, created_since, limit, include_content, requestor)` | `cerefox metadata search --metadata-filter '<json>' --project-name <n> --updated-since <iso> --created-since <iso> --limit N --include-content --requestor <name>` |
-| `cerefox_get_audit_log(document_id, author, operation, since, until, limit, requestor)` | `cerefox audit list --document-id <id> --author <a> --operation <op> --since <iso> --until <iso> --limit N --requestor <name>` |
+| `cerefox_metadata_search(metadata_filter, project_name, updated_since, created_since, limit, include_content, author)` | `cerefox metadata search --metadata-filter '<json>' --project-name <n> --updated-since <iso> --created-since <iso> --limit N --include-content --requestor <name>` |
+| `cerefox_get_audit_log(document_id, by_author, operation, since, until, limit, author)` | `cerefox audit list --document-id <id> --author <a> --operation <op> --since <iso> --until <iso> --limit N --requestor <name>` |
 | `cerefox_set_document_metadata(document_id, metadata, replace, author)` | `cerefox document set-metadata <id> --set key=value` (also `--remove key`, `--json '<json>'`, `--replace`) |
-| `cerefox_delete_document(document_id, expected_content_hash, reason, author, requestor)` | `cerefox document delete <id> --reason <text> --author <a> --author-type <t> --yes` (confirms interactively instead of requiring the hash) |
-| `cerefox_restore_document(document_id, reason, author, requestor)` | `cerefox document restore <id> --reason <text> --author <a> --author-type <t>` |
+| `cerefox_delete_document(document_id, expected_content_hash, reason, author)` | `cerefox document delete <id> --reason <text> --author <a> --author-type <t> --yes` (confirms interactively instead of requiring the hash) |
+| `cerefox_restore_document(document_id, reason, author)` | `cerefox document restore <id> --reason <text> --author <a> --author-type <t>` |
 
 ## CLI ↔ MCP parity matrix
 

package/docs/guides/configuration.md

@@ -378,9 +378,13 @@ enable it.
 ### How it works
 
 A `cerefox_config` table in Postgres stores runtime configuration as key-value
-pairs. The allow-list lives in the `cerefox_set_config` RPC; run `cerefox config
-list` (or open **Settings** in the web UI) for the current set — today that is
-usage tracking, the two requestor-identity keys, three retrieval tunables, and
+pairs. Every key is declared once in the shared catalog
+(`_shared/config-catalog/index.ts`: kind, default, group, description); the
+`cerefox_set_config` RPC's allow-list stays authoritative for writes and a unit
+test pins the two together. Run `cerefox config list` (or open **Settings** in
+the web UI) for the current set — today that is usage tracking, the two
+requestor-identity keys, three retrieval tunables, two version-retention keys,
+the document-size warning threshold, `review_workflow_enabled` and
 `relations_enabled`. Usage logging is the illustrative case below: every logging
 call goes through the
 `cerefox_log_usage` RPC, which checks this config value first:
@@ -414,15 +418,17 @@ cerefox config get usage_tracking_enabled
 
 **Via the web UI:** `cerefox web` → **Settings**. Every runtime key is listed
 with its description, current value and default, grouped into Retrieval,
-Governance and Features.
+Retention, Governance and Features.
 
 Two things the page does deliberately:
 
 - **Keys that change what agents see require confirmation.** Turning on
-  `relations_enabled` adds four tools to every connected agent's tool list, and
+  `relations_enabled` adds four tools to every connected agent's tool list,
   `require_requestor_identity` starts rejecting agents that don't identify
-  themselves. Neither is a bare toggle — you get a dialog naming the
-  consequence first.
+  themselves, `review_workflow_enabled` hides or reveals the review status on
+  every surface, and `version_cleanup_enabled` decides whether old versions are
+  pruned. None is a bare toggle — you get a dialog naming the consequence
+  first.
 - **Retired `.env` lines are flagged.** If a variable that used to control a
   setting is still present in the server's environment, the row says so — it no
   longer does anything, and the value shown is what actually runs. The page
@@ -474,14 +480,20 @@ cerefox config get usage_tracking_enabled
 
 ## Requestor Identity Enforcement
 
-By default, the `requestor` parameter on MCP read tools (and `author` on ingest) is
-optional. When omitted, it defaults to `"mcp-agent"`. This means the usage log shows
-`"mcp-agent"` for all calls that don't explicitly identify themselves, making analytics
-less useful in multi-agent setups.
+By default, the `author` parameter on the MCP tools is optional. When omitted, it
+defaults to `"mcp-agent"`. This means the usage log shows `"mcp-agent"` for all calls
+that don't explicitly identify themselves, making analytics less useful in
+multi-agent setups.
 
-You can optionally enforce caller identification so that MCP tool calls must include
-a requestor/author identity. Calls without identity receive a JSON-RPC `-32602` error
-with a helpful message telling the agent what to provide.
+Since v1.13.1 every MCP tool takes the caller's identity as **`author`**, reads and
+writes alike; `requestor` (the pre-1.13.1 name on most tools) is still accepted as
+a silent alias. (On `cerefox_get_audit_log` the entries filter, formerly `author`,
+is now `by_author`.) The primitive Edge Functions used by GPT Actions keep their
+original body fields (`requestor` on reads, `author` on ingest).
+
+You can optionally enforce caller identification so that tool calls must include
+an identity. Calls without one receive a JSON-RPC `-32602` error with a helpful
+message telling the agent what to provide.
 
 ### What it actually covers
 
@@ -510,7 +522,7 @@ tenth copy of the same block. Raise an issue rather than assuming it is there.
 ### Enabling enforcement
 
 ```bash
-# Require all MCP tool calls to include requestor/author
+# Require all MCP tool calls to include author (or the requestor alias)
 cerefox config set require_requestor_identity true
 
 # Optionally override the default naming format (regex)
@@ -526,7 +538,7 @@ cerefox config set requestor_identity_format "^[a-z]+:[a-z]+$"
 | `^[a-z]+:[a-z]+$` | `conclave:agent` format only | Multi-conclave setups (e.g., `personal:steward`) |
 | (empty string) | Any non-empty string | No format restriction |
 
-The format is applied to both `requestor` (read tools) and `author` (ingest).
+The format is applied to whichever identity field the call carries (`author`, or the `requestor` alias).
 
 ### Disabling enforcement
 
@@ -534,14 +546,59 @@ The format is applied to both `requestor` (read tools) and `author` (ingest).
 cerefox config set require_requestor_identity false
 ```
 
-When disabled, the requestor parameter remains optional with the `"mcp-agent"` default.
+When disabled, the identity parameter remains optional with the `"mcp-agent"` default.
 This is the default state -- no configuration needed for backward compatibility.
 
 ---
 
+## Review Workflow
+
+Cerefox can queue agent-authored writes for a person to approve: with the
+workflow **on**, a document written with `author_type: agent` lands as
+`pending_review`, a human write lands as `approved`, and every surface shows the
+status (a pill on the document page, badges on the dashboard, a search filter,
+a `status` column in the CLI, the field in API and MCP output). Review status
+never gates retrieval — a pending document is exactly as searchable as an
+approved one — it is a governance signal, nothing more.
+
+Since v1.13.0 the workflow is a store-level switch, `review_workflow_enabled`,
+kept in `cerefox_config` like every other store setting so two clients on one
+database cannot disagree about whether it exists:
+
+| Situation | Value |
+|---|---|
+| Fresh install (v1.13.0+) | **`false`** — most single-operator stores never review anything |
+| Upgraded from an earlier version | **`true`** — an upgrade never changes what your store does |
+
+```bash
+cerefox config get review_workflow_enabled
+cerefox config set review_workflow_enabled true    # or false; also in Settings → Governance
+cerefox doctor                                      # prints "review workflow  ON …" / "OFF …"
+```
+
+**With the workflow off, the feature is hidden, not dimmed.** No surface
+shows or enforces a `review_status`: the web pill, badges and search chip do
+not render; the CLI drops its `status` column; API, MCP and Edge Function rows
+carry no `review_status` key; `GET /api/v1/search?review_status=…` is a `400`;
+and `POST /api/v1/documents/{id}/review-status` is a `404`.
+
+**The flag hides; it never rewrites.** Writes are recorded the same way in
+both states — agent writes `pending_review`, user writes `approved`, decided
+once inside the `cerefox_ingest_document` RPC so every access path (CLI, local
+and remote MCP, Edge Functions, web) behaves alike, including older clients.
+Flipping the flag off does not approve anything and flipping it on does not
+queue anything; documents that were `pending_review` are still pending, and a
+document an agent wrote while the workflow was off is pending too, shown as
+such the moment the flag is on again. (v1.13.0 stored `approved` for every
+write while off; v1.13.1 corrected that.) Attribution and the audit log are
+unaffected in both states — who wrote what is always recorded. Config changes
+are audited too.
+
+Design: [`docs/specs/review-workflow-toggle.md`](../specs/review-workflow-toggle.md).
+
 ## Checking Your Configuration
 
-Run the doctor to verify everything is connected (credentials, DB reachability, schema version):
+Run the doctor to verify everything is connected (credentials, DB reachability, schema version, review workflow on/off):
 
 ```bash
 cerefox doctor       # or: cerefox status

package/docs/guides/connect-agents.md

@@ -221,7 +221,7 @@ You have access to a personal knowledge base via Cerefox MCP tools.
 When answering questions, always call cerefox_search first with a relevant query.
 Cite doc_title for every claim drawn from the knowledge base.
 Use cerefox_ingest to save anything the user asks you to remember.
-Always set your requestor/author parameter to identify yourself.
+Always set the author parameter to identify yourself.
 For the full tool reference, search Cerefox for "How AI Agents Use Cerefox".
 ```
 
@@ -638,7 +638,7 @@ In the action editor, paste this schema (replace `<your-project-ref>`):
 openapi: 3.1.0
 info:
   title: Cerefox Knowledge Base
-  version: 3.3.0
+  version: 3.4.1
 servers:
   - url: https://<your-project-ref>.supabase.co/functions/v1
 paths:
@@ -798,8 +798,10 @@ paths:
                   default: agent
                   description: >
                     Whether this write is from a human user or an AI agent.
-                    Controls review_status auto-transition: agent writes set
-                    the document to pending_review, user writes set it to approved.
+                    Always recorded for attribution. Agent writes are recorded
+                    pending_review and user writes approved; the store's review
+                    workflow flag (review_workflow_enabled) only decides whether
+                    that status is shown.
       responses:
         '200':
           description: >
@@ -1033,9 +1035,11 @@ paths:
         '200':
           description: >
             Array of matching documents:
-            [{ document_id, title, doc_metadata, review_status, source, created_at,
+            [{ document_id, title, doc_metadata, source, created_at,
                updated_at, total_chars, chunk_count, project_ids, project_names,
-               version_count, content_hash, content }].
+               version_count, content_hash, content }], plus review_status
+            only while the store's review workflow is on (the key is absent
+            when it is off).
             content_hash is the concurrency token — pass it back as
             expected_content_hash when updating via ingestNote.
 ```

package/docs/guides/upgrading.md

@@ -11,7 +11,7 @@ cerefox guides ingest    # 3. the bundled guides, into your KB
 ```
 
 The order matters: a release may require its own schema (the version notes
-say so — v1.9.x is one), and until `server deploy` runs, the freshly updated
+say so — v1.9.x and v1.13.0 are two), and until `server deploy` runs, the freshly updated
 client is talking to the previous release's server. That is why
 `self-update` no longer runs the guides sync automatically — it used to fire
 at the one moment in the upgrade where it cannot succeed against a
@@ -60,6 +60,32 @@ schema-requiring release.
 
 ## End-user upgrade
 
+> ### Upgrading to v1.13.0 — `cerefox server deploy` is required
+>
+> v1.13.0 makes the review workflow optional and moves the "agent writes land
+> `pending_review`" decision out of the clients and into the
+> `cerefox_ingest_document` RPC (#241). A v1.13.0 client no longer decides
+> the status itself, so against an older server every agent write would
+> silently land `approved` — a behaviour change, not a missing feature — and
+> the new review-status search filter would fail outright. The **minimum
+> supported schema is therefore `0.16.0`**: until you run `cerefox server
+> deploy`, `cerefox web` refuses to start and `doctor` says exactly why.
+>
+> Migration 0031 seeds `review_workflow_enabled = true` on every existing
+> store, so **your store keeps behaving exactly as before**. The flag now
+> exists and `cerefox doctor` prints its state; flip it with
+> `cerefox config set review_workflow_enabled false` (or Settings → Governance)
+> if nobody reviews the queue. See
+> [configuration.md → Review Workflow](configuration.md#review-workflow).
+>
+> **v1.13.1** (schema 0.16.1) corrects one thing in the above: the flag
+> governs only what is *shown*. v1.13.0 also stored `approved` for every
+> write while the flag was off; v1.13.1 records agent writes as
+> `pending_review` regardless, so turning the workflow back on shows the
+> statuses the store would have had all along. It is an RPC-only change —
+> `cerefox server deploy` (or `--schema-only`) picks it up; nothing refuses
+> to run until you do, but a 0.16.0 server keeps the v1.13.0 write behaviour.
+
 > ### Upgrading to v1.1.0 — `cerefox server deploy` is required
 >
 > Most releases let you postpone the server step. **This one does not.** Until
@@ -166,6 +192,11 @@ knowing about:
   that ingested fine before now need deduplication, or are refused on edit.
 - **v1.7.0 — trashed documents refuse content updates.** A soft-deleted
   document must be restored before its content can be updated.
+- **v1.13.0 — the review workflow is a store setting.** Upgraded stores keep
+  it on; fresh installs start with it off. See the callout above.
+- **v1.13.1 — the flag hides, it does not rewrite.** Agent writes are
+  recorded `pending_review` whether or not the workflow is shown (v1.13.0
+  stored `approved` while off). Redeploy to pick it up.
 
 ## Notable: v1.8.0 storage reclaim (migration 0027)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cerefox/memory",
-  "version": "1.12.1",
+  "version": "1.13.1",
   "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",