@jhizzard/termdeck 1.0.4 → 1.0.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jhizzard/termdeck",
-  "version": "1.0.4",
+  "version": "1.0.6",
   "description": "Browser-based terminal multiplexer with metadata overlays, panel flashback memory recall, and AI-aware session management",
   "bin": {
     "termdeck": "./packages/cli/src/index.js"

package/packages/server/src/setup/mnestra-migrations/001_mnestra_tables.sql

@@ -78,6 +78,45 @@ create index if not exists memory_relationships_target_idx on memory_relationshi
 
 -- ── match_memories helper RPC ─────────────────────────────────────────────
 -- Used by remember.ts (dedup) and consolidate.ts (cluster seeding).
+--
+-- Sprint 52.1 — signature-drift guard. On long-lived v0.6.x-era installs
+-- (Joshua's petvetbid, Brad's jizzard-brain), match_memories was created by
+-- a prior Mnestra version with a different RETURN-table column shape:
+--   (id, content, metadata, source_type, category, project, created_at, similarity)
+-- vs the canonical:
+--   (id, content, source_type, category, project, metadata, similarity)
+-- Postgres rejects `CREATE OR REPLACE FUNCTION` when the return-table
+-- column list changes — `cannot change return type of existing function`
+-- — and the migration replay throws exit 5. Sprint 51.7 fixed Class M
+-- (DB failure no longer strands hook upgrade) but this drift remained
+-- and was the only blocker keeping `termdeck init --mnestra` from
+-- finishing cleanly on existing v0.6.x installs. Sprint 51.8 fixed
+-- Class N (settings.json wiring lockstep).
+--
+-- The do-block below drops all `public.match_memories` overloads
+-- regardless of arg list, so the subsequent CREATE OR REPLACE always
+-- lands cleanly on greenfield AND existing-drift installs. Idempotent —
+-- on a brand-new project the loop iterates zero times. Scoped to schema
+-- `public` so we never touch a same-named function in another schema.
+-- No CASCADE: dependent objects in plpgsql/SQL function bodies (e.g.
+-- `memory_recall_graph` from migration 010) reference functions by
+-- name and resolve at call time, so the drop-then-recreate pattern is
+-- safe without CASCADE. If a true hard dependency (view, generated
+-- column) ever appears, the DROP fails loud — the right behavior.
+
+do $$
+declare
+  r record;
+begin
+  for r in
+    select p.oid::regprocedure as sig
+    from pg_proc p
+    join pg_namespace n on n.oid = p.pronamespace
+    where p.proname = 'match_memories' and n.nspname = 'public'
+  loop
+    execute 'drop function ' || r.sig::text;
+  end loop;
+end $$;
 
 create or replace function match_memories (
   query_embedding   vector(1536),

package/packages/server/src/setup/mnestra-migrations/002_mnestra_search_function.sql

@@ -12,6 +12,43 @@
 --
 --   Fix 5 — Project affinity scoring. Exact project match multiplies the
 --           score by 1.5x; mismatches are penalised 0.7x.
+--
+-- Sprint 51.9 — signature-drift guard. Same Class A pattern Sprint 52.1
+-- closed for `match_memories` (mig 001:81-95). Codex T4 surfaced the cousin
+-- 2026-05-04 14:42 ET during Sprint 51.5b dogfood: long-lived v0.6.x-era
+-- installs (Joshua's petvetbid, likely Brad's jizzard-brain) ALSO have a
+-- 10-arg drift overload of `memory_hybrid_search` coexisting with the
+-- canonical 8-arg signature. The drift overload carries the never-shipped
+-- `recency_weight`/`decay_days` parameters from a pre-canonical Mnestra
+-- iteration or the rag-system writer's bootstrap. PostgREST + MCP clients
+-- hit ambiguous-overload errors when calling `memory_hybrid_search` with
+-- the canonical 8-arg shape because Postgres can't disambiguate.
+--
+-- The do-block below drops all `public.memory_hybrid_search` overloads
+-- regardless of arg list, so the subsequent CREATE OR REPLACE always
+-- lands cleanly on greenfield AND existing-drift installs. Idempotent —
+-- on a brand-new project the loop iterates zero times. Scoped to schema
+-- `public`. No CASCADE — same reasoning as mig 001's guard: SQL function
+-- bodies that call this function (none currently exist) would resolve
+-- by name at call time.
+--
+-- mig 004 will subsequently `CREATE OR REPLACE` this function with the
+-- match_count cap variant (still 8 args). End state: ONE 8-arg version
+-- of memory_hybrid_search in public schema. Ambiguity gone.
+
+do $$
+declare
+  r record;
+begin
+  for r in
+    select p.oid::regprocedure as sig
+    from pg_proc p
+    join pg_namespace n on n.oid = p.pronamespace
+    where p.proname = 'memory_hybrid_search' and n.nspname = 'public'
+  loop
+    execute 'drop function ' || r.sig::text;
+  end loop;
+end $$;
 
 create or replace function memory_hybrid_search (
   query_text          text,

package/packages/server/src/setup/mnestra-migrations/016_mnestra_doctor_probes.sql

@@ -15,38 +15,24 @@
 --
 -- Idempotent: every function uses CREATE OR REPLACE; every GRANT is
 -- safe to re-run. No data mutation. Safe to re-apply on every install.
-
--- ── 1. cron.job_run_details lookup ───────────────────────────────────────
 --
--- Returns the most recent N runs of a named cron job, projecting only
--- the columns the doctor needs (status, start/end timestamps, return
--- message). The doctor parses `return_message` for the rumen-tick /
--- graph-inference all-zeros pattern.
+-- Sprint 51.9 — pg_cron-conditional cron probes. T3 caught 2026-05-04
+-- 14:55 ET that fresh Supabase projects (mnestra-only, no rumen) hit
+-- exit-5 on this migration: `cron.job_run_details` and `cron.job` are
+-- parse-time-resolved by `language sql` functions, and a fresh project
+-- does NOT have `pg_cron` enabled by default (only `pg_stat_statements,
+-- pg_trgm, pgcrypto, plpgsql, supabase_vault, uuid-ossp, vector` are in
+-- the default set). The two cron-touching functions
+-- (`mnestra_doctor_cron_runs`, `mnestra_doctor_cron_job_exists`) +
+-- their grants are now wrapped in a do$$ guard that only emits them
+-- when `pg_cron` is enabled. The doctor's cron-related probes return
+-- the existing `unknown` band (Sprint 51.5 T2 already established it)
+-- when the wrappers don't exist — graceful degradation. Petvetbid +
+-- jizzard-brain are unaffected because both have rumen installed,
+-- which enables pg_cron via rumen's mig 002. Closes the
+-- mnestra-only-no-rumen fresh-install path.
 
-create or replace function mnestra_doctor_cron_runs(
-  p_jobname text,
-  p_limit   int default 10
-)
-returns table (
-  jobname        text,
-  status         text,
-  start_time     timestamptz,
-  end_time       timestamptz,
-  return_message text
-)
-language sql
-security definer
-set search_path = cron, public
-as $$
-  select j.jobname, d.status, d.start_time, d.end_time, d.return_message
-  from cron.job_run_details d
-  join cron.job j on j.jobid = d.jobid
-  where j.jobname = p_jobname
-  order by d.start_time desc
-  limit greatest(coalesce(p_limit, 10), 1);
-$$;
-
--- ── 2. column existence probe (public schema only) ───────────────────────
+-- ── 1. column existence probe (public schema only — cron-independent) ───
 
 create or replace function mnestra_doctor_column_exists(
   p_table  text,
@@ -66,7 +52,7 @@ as $$
   );
 $$;
 
--- ── 3. RPC / function existence probe ────────────────────────────────────
+-- ── 2. RPC / function existence probe (cron-independent) ────────────────
 
 create or replace function mnestra_doctor_rpc_exists(p_name text)
 returns boolean
@@ -83,21 +69,12 @@ as $$
   );
 $$;
 
--- ── 4. cron.job existence probe (does the named job exist at all) ───────
-
-create or replace function mnestra_doctor_cron_job_exists(p_jobname text)
-returns boolean
-language sql
-security definer
-set search_path = cron, public
-as $$
-  select exists (select 1 from cron.job where jobname = p_jobname);
-$$;
-
--- ── 5. vault.secrets existence probe (no value disclosure) ──────────────
+-- ── 3. vault.secrets existence probe (no value disclosure) ──────────────
 --
 -- Existence-only — never returns the secret value. The doctor only needs
 -- to know whether the named vault entry was created during stack install.
+-- supabase_vault IS in the Supabase default extension set, so this is
+-- safe to emit unconditionally on greenfield projects.
 
 create or replace function mnestra_doctor_vault_secret_exists(p_name text)
 returns boolean
@@ -108,10 +85,68 @@ as $$
   select exists (select 1 from vault.secrets where name = p_name);
 $$;
 
--- ── 6. Grants ────────────────────────────────────────────────────────────
+-- ── 4. Grants for the cron-independent probes ───────────────────────────
 
-grant execute on function mnestra_doctor_cron_runs(text, int)             to service_role;
 grant execute on function mnestra_doctor_column_exists(text, text)        to service_role;
 grant execute on function mnestra_doctor_rpc_exists(text)                 to service_role;
-grant execute on function mnestra_doctor_cron_job_exists(text)            to service_role;
 grant execute on function mnestra_doctor_vault_secret_exists(text)        to service_role;
+
+-- ── 5. cron.* probes (only emit when pg_cron is enabled) ────────────────
+--
+-- The two SECURITY DEFINER wrappers below reference `cron.job_run_details`
+-- and `cron.job`. Because Postgres parse-time-resolves identifiers in
+-- `language sql` functions, the CREATE itself fails when `cron` schema
+-- doesn't exist — not just function execution. The do$$ guard checks
+-- pg_extension first; if pg_cron isn't enabled, we skip emitting these
+-- two wrappers entirely. The doctor's cron probes return `unknown`
+-- in that case (Sprint 51.5 T2 contract).
+--
+-- Idempotent: do$$ runs every replay; CREATE OR REPLACE keeps the
+-- function definitions in sync if pg_cron later gets enabled and the
+-- migration re-runs. Existing installs (petvetbid, jizzard-brain) have
+-- pg_cron from Rumen's install path and emit these unconditionally.
+
+do $cron_guard$
+begin
+  if exists (select 1 from pg_extension where extname = 'pg_cron') then
+    execute $stmt$
+      create or replace function mnestra_doctor_cron_runs(
+        p_jobname text,
+        p_limit   int default 10
+      )
+      returns table (
+        jobname        text,
+        status         text,
+        start_time     timestamptz,
+        end_time       timestamptz,
+        return_message text
+      )
+      language sql
+      security definer
+      set search_path = cron, public
+      as $body$
+        select j.jobname, d.status, d.start_time, d.end_time, d.return_message
+        from cron.job_run_details d
+        join cron.job j on j.jobid = d.jobid
+        where j.jobname = p_jobname
+        order by d.start_time desc
+        limit greatest(coalesce(p_limit, 10), 1);
+      $body$;
+    $stmt$;
+
+    execute $stmt$
+      create or replace function mnestra_doctor_cron_job_exists(p_jobname text)
+      returns boolean
+      language sql
+      security definer
+      set search_path = cron, public
+      as $body$
+        select exists (select 1 from cron.job where jobname = p_jobname);
+      $body$;
+    $stmt$;
+
+    execute 'grant execute on function mnestra_doctor_cron_runs(text, int) to service_role';
+    execute 'grant execute on function mnestra_doctor_cron_job_exists(text) to service_role';
+  end if;
+end
+$cron_guard$;