@cerefox/memory 1.9.0 → 1.9.2

package/dist/bin/cerefox.js

@@ -7438,7 +7438,7 @@ var exports_meta = {};
 __export(exports_meta, {
   PKG_VERSION: () => PKG_VERSION
 });
-var PKG_VERSION = "1.9.0";
+var PKG_VERSION = "1.9.2";
 var init_meta = () => {};
 
 // ../../_shared/config/paths.ts
@@ -25802,7 +25802,7 @@ var init_bundled_docs = __esm(() => {
 });
 
 // ../../_shared/ef-meta/index.ts
-var EF_VERSION = "1.9.0", CEREFOX_VERSION = "1.9.0", EF_LAST_CHANGED = "1.9.0";
+var EF_VERSION = "1.9.2", CEREFOX_VERSION = "1.9.2", EF_LAST_CHANGED = "1.9.0";
 var init_ef_meta = () => {};
 
 // ../../_shared/compatibility/index.ts
@@ -73413,6 +73413,7 @@ Proceed with deployment to Supabase?`, true);
   println(c.green(`
 ✓ Server deploy complete.`));
   println(c.dim("Verify with: cerefox doctor"));
+  println(c.dim("Refresh the bundled guides: cerefox guides ingest"));
 }
 function registerDeployServer(program2) {
   program2.command("deploy-server").description("Deploy/update the Cerefox server side (schema + RPCs + Edge Functions) on Supabase.").option("--dry-run", "Print the plan + pre-flight without deploying.").option("--schema-only", "Deploy/update only the schema + RPCs (skip Edge Functions).").option("--functions-only", "Deploy only the Edge Functions (skip the schema/RPCs).").option("--project-ref <ref>", "Supabase project ref for Edge Function deploys (default: derived from CEREFOX_SUPABASE_URL).").option("--yes", "Non-interactive (skip the deployment confirmation).").action(action10);
@@ -80660,14 +80661,10 @@ async function action33(options) {
   println("");
   println(c.green(`✓ Upgraded to ${target}.`));
   println("");
-  println(c.dim("Refreshing bundled-docs ingest (using the new version)…"));
-  const sync = spawnSync5(process.execPath, [process.argv[1], "guides", "ingest"], {
-    stdio: "inherit"
-  });
-  if (sync.status !== 0) {
-    println(cErr.yellow("⚠ ") + "Could not refresh self-docs (see output above).");
-    println(c.dim("  Run `cerefox guides ingest` manually after a successful `cerefox init`."));
-  }
+  println("Next steps:");
+  println("  1. " + c.bold("cerefox server deploy") + "   apply this release's schema/RPC/EF updates");
+  println("  2. " + c.bold("cerefox guides ingest") + "   re-sync the bundled guides into your KB");
+  println(c.dim("  (order matters: the new client may require the new schema — run the deploy first)"));
 }
 function registerSelfUpdate(program2) {
   const desc = "Upgrade Cerefox in place. Alias: `cerefox upgrade`.";

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

package/dist/server-assets/db/migrations/0029_fix_project_edit_description_audit.sql

@@ -0,0 +1,105 @@
+-- Migration 0029 — fix cerefox_update_project's description-change audit
+-- (schema 0.14.1)
+--
+-- v1.9.0's cerefox_update_project appended the audit-diff fragment with
+-- `v_changes || 'description changed'`; Postgres resolves the untyped
+-- literal via the array||array overload and raises `malformed array
+-- literal`, rolling back EVERY project edit that changes a description
+-- (rename-only edits worked — their concatenation is typed TEXT). Found
+-- live in the v1.9.0 staging dress rehearsal before any production
+-- deployment. The fix is array_append on both branches.
+--
+-- The full corrected body ships inside this migration (repair-path closure,
+-- as 0027/0028), plus the same ACL lockdown 0028 gave the original.
+-- Re-runnable.
+
+DROP FUNCTION IF EXISTS cerefox_update_project(UUID, TEXT, TEXT, TEXT, TEXT);
+
+CREATE FUNCTION cerefox_update_project(
+    p_project_id  UUID,
+    -- NULL = keep the current value (the #191/#204 "NULL means not provided"
+    -- convention). An explicit empty name is rejected.
+    p_name        TEXT DEFAULT NULL,
+    p_description TEXT DEFAULT NULL,
+    p_author      TEXT DEFAULT 'unknown',
+    p_author_type TEXT DEFAULT 'user'
+)
+RETURNS TABLE (
+    project_id          UUID,
+    project_name        TEXT,
+    project_description TEXT,
+    created_at          TIMESTAMPTZ,
+    updated_at          TIMESTAMPTZ
+)
+LANGUAGE plpgsql
+SECURITY DEFINER
+SET search_path = public, pg_catalog
+AS $$
+DECLARE
+    v_old  cerefox_projects%ROWTYPE;
+    v_new  cerefox_projects%ROWTYPE;
+    v_changes TEXT[] := '{}';
+BEGIN
+    IF p_name IS NULL AND p_description IS NULL THEN
+        RAISE EXCEPTION 'Nothing to update: pass p_name and/or p_description' USING ERRCODE = '22023';
+    END IF;
+    IF p_name IS NOT NULL AND NULLIF(BTRIM(p_name), '') IS NULL THEN
+        RAISE EXCEPTION 'Project name cannot be empty' USING ERRCODE = '22023';
+    END IF;
+
+    SELECT p.* INTO v_old FROM cerefox_projects p WHERE p.id = p_project_id FOR UPDATE;
+    IF NOT FOUND THEN
+        RAISE EXCEPTION 'Project not found: %', p_project_id USING ERRCODE = '22023';
+    END IF;
+
+    UPDATE cerefox_projects SET
+        name        = COALESCE(BTRIM(p_name), name),
+        description = COALESCE(p_description, description),
+        updated_at  = NOW()
+    WHERE id = p_project_id
+    RETURNING * INTO v_new;
+
+    -- The trail records what actually changed, not which arguments arrived.
+    -- array_append, NOT `||`: with an untyped string literal on the right,
+    -- `TEXT[] || 'literal'` resolves to the array||array overload and dies
+    -- with `malformed array literal` — found LIVE on staging (v1.9.0; every
+    -- description-only edit failed; the rename branch only survived because
+    -- its parenthesized concatenation is typed TEXT).
+    IF v_new.name <> v_old.name THEN
+        v_changes := array_append(v_changes, 'renamed ''' || v_old.name || ''' → ''' || v_new.name || '''');
+    END IF;
+    IF COALESCE(v_new.description, '') <> COALESCE(v_old.description, '') THEN
+        v_changes := array_append(v_changes, 'description changed');
+    END IF;
+
+    PERFORM cerefox_create_audit_entry(
+        p_operation   := 'project-edit',
+        p_author      := p_author,
+        p_author_type := p_author_type,
+        p_description := 'Project ''' || v_new.name || ''' edited ('
+            || COALESCE(NULLIF(array_to_string(v_changes, '; '), ''), 'no-op') || ')'
+    );
+    RETURN QUERY SELECT v_new.id, v_new.name, v_new.description,
+                        v_new.created_at, v_new.updated_at;
+END;
+$$;
+
+DO $$
+DECLARE
+  r TEXT;
+BEGIN
+  REVOKE EXECUTE ON FUNCTION cerefox_update_project(UUID, TEXT, TEXT, TEXT, TEXT) FROM PUBLIC;
+  FOREACH r IN ARRAY ARRAY['anon', 'authenticated'] LOOP
+    IF EXISTS (SELECT 1 FROM pg_roles WHERE rolname = r) THEN
+      EXECUTE format('REVOKE EXECUTE ON FUNCTION cerefox_update_project(UUID, TEXT, TEXT, TEXT, TEXT) FROM %I', r);
+    END IF;
+  END LOOP;
+  IF EXISTS (SELECT 1 FROM pg_roles WHERE rolname = 'service_role') THEN
+    GRANT EXECUTE ON FUNCTION cerefox_update_project(UUID, TEXT, TEXT, TEXT, TEXT) TO service_role;
+  END IF;
+END $$;
+
+DO $$
+BEGIN
+    RAISE NOTICE 'Migration 0029: fixed the project-edit description audit (array_append; description-only edits no longer fail).';
+END $$;

package/dist/server-assets/db/rpcs.sql

@@ -2118,11 +2118,16 @@ BEGIN
     RETURNING * INTO v_new;
 
     -- The trail records what actually changed, not which arguments arrived.
+    -- array_append, NOT `||`: with an untyped string literal on the right,
+    -- `TEXT[] || 'literal'` resolves to the array||array overload and dies
+    -- with `malformed array literal` — found LIVE on staging (v1.9.0; every
+    -- description-only edit failed; the rename branch only survived because
+    -- its parenthesized concatenation is typed TEXT).
     IF v_new.name <> v_old.name THEN
-        v_changes := v_changes || ('renamed ''' || v_old.name || ''' → ''' || v_new.name || '''');
+        v_changes := array_append(v_changes, 'renamed ''' || v_old.name || ''' → ''' || v_new.name || '''');
     END IF;
     IF COALESCE(v_new.description, '') <> COALESCE(v_old.description, '') THEN
-        v_changes := v_changes || 'description changed';
+        v_changes := array_append(v_changes, 'description changed');
     END IF;
 
     PERFORM cerefox_create_audit_entry(
@@ -3012,7 +3017,7 @@ AS $$
     -- 0.11.0 supersedes 0.10.6 (v1.2.1, #191): this branch carries that fix plus
     -- the partial-edit surface, and both migrations (0019, 0020) are in the
     -- sequence, so a store deploying this gets everything from both lines.
-    SELECT '0.14.0'::TEXT;
+    SELECT '0.14.1'::TEXT;
 $$;
 
 -- ── cerefox_find_dead_links ──────────────────────────────────────────────────

package/dist/server-assets/db/schema.sql

@@ -5,7 +5,7 @@
 -- Requires extensions: vector (pgvector), uuid-ossp
 -- These are enabled at the top of db_deploy.py before this file is applied.
 --
--- @version: 0.14.0
+-- @version: 0.14.1
 -- The `@version` marker above is read by the schema-version-mismatch banner
 -- (see /api/v1/schema-version). Bump it whenever schema.sql OR rpcs.sql
 -- changes in a way that requires `cerefox server deploy` to be re-run —

package/docs/guides/upgrading.md

@@ -1,8 +1,21 @@
 # Upgrading Cerefox
 
-Upgrading is almost always two steps: **update the CLI, then re-deploy the
-server side if the release changed it.** Everything here is idempotent and safe
-to re-run.
+Upgrading is almost always three steps, **in this order**: update the CLI,
+re-deploy the server side if the release changed it, then re-sync the bundled
+guides. Everything here is idempotent and safe to re-run.
+
+```bash
+cerefox self-update      # 1. the client
+cerefox server deploy    # 2. schema + RPCs + Edge Functions (if the release changed them)
+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
+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
+schema-requiring release.
 
 ## Pick your path
 

package/package.json

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