@jhizzard/termdeck 0.2.2 → 0.2.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jhizzard/termdeck",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "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/cli/src/index.js

@@ -7,9 +7,9 @@
 //   termdeck init --rumen  [flags]   # Tier 3 async learning deploy
 //
 // Note (Sprint 3): the `--mnestra` flag name matches the current init-mnestra.js
-// filename. When the main orchestrator completes the Mnestra → Ingram rename
+// filename. When the main orchestrator completes the Mnestra → Mnestra rename
 // sweep over this repo, both the flag name and the filename should flip to
-// `--ingram` / `init-ingram.js` together.
+// `--mnestra` / `init-mnestra.js` together.
 
 const path = require('path');
 const { execSync } = require('child_process');
@@ -43,7 +43,7 @@ if (args[0] === 'init') {
     return;
   }
   console.error('Usage: termdeck init --mnestra | --rumen');
-  console.error('  termdeck init --mnestra   Configure Tier 2 memory (Supabase + Ingram)');
+  console.error('  termdeck init --mnestra   Configure Tier 2 memory (Supabase + Mnestra)');
   console.error('  termdeck init --rumen    Deploy Tier 3 async learning (Rumen)');
   process.exit(1);
 }
@@ -66,7 +66,7 @@ for (let i = 0; i < args.length; i++) {
     termdeck --port 8080        Start on custom port
     termdeck --no-open          Don't auto-open browser
     termdeck --session-logs     Write per-session markdown logs to ~/.termdeck/sessions/
-    termdeck init --mnestra      Configure Tier 2 memory (Supabase + Ingram)
+    termdeck init --mnestra      Configure Tier 2 memory (Supabase + Mnestra)
     termdeck init --rumen       Deploy Tier 3 async learning (Rumen)
 
   Keyboard shortcuts (in browser):

package/packages/cli/src/{init-engram.js → init-mnestra.js}

@@ -1,12 +1,12 @@
 #!/usr/bin/env node
 
-// `termdeck init --engram` — interactive wizard for TermDeck's Tier 2 memory
-// layer. Wraps the six manual Engram setup steps into one command.
+// `termdeck init --mnestra` — interactive wizard for TermDeck's Tier 2 memory
+// layer. Wraps the six manual Mnestra setup steps into one command.
 //
 // Steps:
 //   1. Collect Supabase URL, service_role key, direct DB URL, OpenAI + Anthropic keys
 //   2. Connect via `pg` using the direct URL
-//   3. Apply the six bundled Engram migrations in order
+//   3. Apply the six bundled Mnestra migrations in order
 //   4. Write ~/.termdeck/secrets.env (merge-aware, preserves existing values)
 //   5. Update ~/.termdeck/config.yaml to enable RAG + point at ${VAR} refs
 //   6. Verify with a memory_status_aggregation() call
@@ -35,9 +35,9 @@ const {
 
 const HELP = [
   '',
-  'TermDeck Engram Setup',
+  'TermDeck Mnestra Setup',
   '',
-  'Usage: termdeck init --engram [flags]',
+  'Usage: termdeck init --mnestra [flags]',
   '',
   'Flags:',
   '  --help            Print this message and exit',
@@ -48,10 +48,10 @@ const HELP = [
   'What this does:',
   '  1. Prompts for Supabase URL, service_role key, direct Postgres connection',
   '     string, OpenAI API key, and (optional) Anthropic API key.',
-  '  2. Applies the six Engram schema + RPC migrations via node-postgres.',
+  '  2. Applies the six Mnestra schema + RPC migrations via node-postgres.',
   '  3. Writes ~/.termdeck/secrets.env (merge-aware, preserves existing values).',
   '  4. Updates ~/.termdeck/config.yaml to enable RAG and reference ${VAR} keys.',
-  '  5. Verifies the Engram store is reachable via memory_status_aggregation().',
+  '  5. Verifies the Mnestra store is reachable via memory_status_aggregation().',
   '',
   'Every secret stays on your machine. Nothing is ever printed once entered.',
   ''
@@ -70,10 +70,10 @@ function parseFlags(argv) {
 
 function printBanner() {
   process.stdout.write(`
-TermDeck Engram Setup
+TermDeck Mnestra Setup
 ─────────────────────
 
-This wizard configures TermDeck's Tier 2 memory layer (Engram) by:
+This wizard configures TermDeck's Tier 2 memory layer (Mnestra) by:
   1. Asking for your Supabase URL and service_role key
   2. Asking for a direct Postgres connection string
   3. Applying six SQL migrations to the database
@@ -166,9 +166,9 @@ async function promptSecretWithValidation(validator) {
 }
 
 async function applyMigrations(client, dryRun) {
-  const files = migrations.listEngramMigrations();
+  const files = migrations.listMnestraMigrations();
   if (files.length === 0) {
-    throw new Error('No Engram migrations found. TermDeck install looks corrupted.');
+    throw new Error('No Mnestra migrations found. TermDeck install looks corrupted.');
   }
 
   for (const file of files) {
@@ -257,7 +257,7 @@ function writeLocalConfig(inputs, dryRun) {
 
 function printNextSteps() {
   process.stdout.write(`
-Engram is configured.
+Mnestra is configured.
 
 Next steps:
   1. Restart TermDeck: termdeck
@@ -280,7 +280,7 @@ async function main(argv) {
   try {
     inputs = await collectInputs({ yes: flags.yes });
   } catch (err) {
-    process.stderr.write(`\n[init --engram] ${err.message}\n`);
+    process.stderr.write(`\n[init --mnestra] ${err.message}\n`);
     return 2;
   }
 
@@ -322,7 +322,7 @@ async function main(argv) {
       }
     }
   } catch (err) {
-    process.stderr.write(`\n[init --engram] ${err.message}\n`);
+    process.stderr.write(`\n[init --mnestra] ${err.message}\n`);
     return 5;
   } finally {
     try { await client.end(); } catch (_err) { /* ignore */ }
@@ -336,7 +336,7 @@ if (require.main === module) {
   main(process.argv.slice(2))
     .then((code) => process.exit(code || 0))
     .catch((err) => {
-      process.stderr.write(`\n[init --engram] unexpected error: ${err && err.stack || err}\n`);
+      process.stderr.write(`\n[init --mnestra] unexpected error: ${err && err.stack || err}\n`);
       process.exit(1);
     });
 }

package/packages/cli/src/init-rumen.js

@@ -2,13 +2,13 @@
 
 // `termdeck init --rumen` — interactive wizard for deploying Rumen as a
 // Supabase Edge Function + pg_cron schedule against the same Supabase
-// project that holds the Mnemos store.
+// project that holds the Mnestra store.
 //
 // Requirements checked at runtime:
 //   - `supabase` CLI on PATH
 //   - `deno` on PATH
 //   - `~/.termdeck/secrets.env` with SUPABASE_URL + SUPABASE_SERVICE_ROLE_KEY +
-//     DATABASE_URL + ANTHROPIC_API_KEY populated (run `termdeck init --mnemos` first)
+//     DATABASE_URL + ANTHROPIC_API_KEY populated (run `termdeck init --mnestra` first)
 //
 // Steps:
 //   1. Preflight: which supabase, which deno, read secrets.env
@@ -47,7 +47,7 @@ const HELP = [
   '  --skip-schedule   Deploy the function but do not install the pg_cron schedule',
   '',
   'Requires: Supabase CLI and Deno already installed.',
-  'Requires: `termdeck init --mnemos` has already run (needs secrets.env).',
+  'Requires: `termdeck init --mnestra` has already run (needs secrets.env).',
   ''
 ].join('\n');
 
@@ -112,14 +112,14 @@ function preflight() {
   }
   ok();
 
-  step('Reading Mnemos config from ~/.termdeck/secrets.env...');
+  step('Reading Mnestra config from ~/.termdeck/secrets.env...');
   const secrets = dotenv.readSecrets();
   const required = ['SUPABASE_URL', 'SUPABASE_SERVICE_ROLE_KEY', 'DATABASE_URL', 'ANTHROPIC_API_KEY'];
   const missing = required.filter((k) => !secrets[k]);
   if (missing.length > 0) {
     fail(`missing keys: ${missing.join(', ')}`);
     process.stderr.write(
-      '\nRun `termdeck init --mnemos` first — it writes the keys this wizard needs.\n'
+      '\nRun `termdeck init --mnestra` first — it writes the keys this wizard needs.\n'
     );
     return null;
   }
@@ -363,7 +363,7 @@ Next steps:
   1. Monitor:  psql "$DATABASE_URL" -c "SELECT * FROM rumen_jobs ORDER BY started_at DESC LIMIT 5"
   2. Store the service_role key in Supabase Vault as \`rumen_service_role_key\`
      so the cron call in migrations/002_pg_cron_schedule.sql can authenticate.
-  3. Rumen insights flow back into Mnemos's memory_items via rumen_insights.
+  3. Rumen insights flow back into Mnestra's memory_items via rumen_insights.
   4. TermDeck's Flashback will surface cross-project patterns automatically.
 `);
 }

package/packages/server/src/setup/migrations.js

@@ -1,15 +1,15 @@
 // Discover the SQL migration files that ship bundled inside the TermDeck
-// package. Both init wizards call this — init-engram for the six Engram
+// package. Both init wizards call this — init-mnestra for the six Mnestra
 // migrations, init-rumen for the two Rumen migrations.
 //
-// The wizards intentionally do NOT fall back to a sibling `../../engram`
+// The wizards intentionally do NOT fall back to a sibling `../../mnestra`
 // working copy. Resolution order:
 //
-//   1. Files bundled at `packages/server/src/setup/engram-migrations/*.sql`
+//   1. Files bundled at `packages/server/src/setup/mnestra-migrations/*.sql`
 //      (this directory is covered by the root package.json `files` glob).
-//   2. Files at `node_modules/@jhizzard/engram/migrations/*.sql` if that
+//   2. Files at `node_modules/@jhizzard/mnestra/migrations/*.sql` if that
 //      package is installed alongside TermDeck (future-proof path — shipping
-//      `@jhizzard/engram` as an optional peer would let us drop the bundled
+//      `@jhizzard/mnestra` as an optional peer would let us drop the bundled
 //      copy).
 
 const fs = require('fs');
@@ -44,10 +44,10 @@ function tryNodeModules(packageName, migrationSubdir = 'migrations') {
   }
 }
 
-function listEngramMigrations() {
-  const fromNm = tryNodeModules('@jhizzard/engram');
+function listMnestraMigrations() {
+  const fromNm = tryNodeModules('@jhizzard/mnestra');
   if (fromNm.length > 0) return fromNm;
-  return listBundled('engram-migrations');
+  return listBundled('mnestra-migrations');
 }
 
 function listRumenMigrations() {
@@ -73,7 +73,7 @@ function readFile(filepath) {
 }
 
 module.exports = {
-  listEngramMigrations,
+  listMnestraMigrations,
   listRumenMigrations,
   rumenFunctionDir,
   readFile

package/packages/server/src/setup/{engram-migrations/001_engram_tables.sql → mnestra-migrations/001_mnestra_tables.sql}

@@ -1,10 +1,10 @@
--- Engram v0.1 — core tables
+-- Mnestra v0.1 — core tables
 --
 -- Run against a Postgres 15+ database that has pgvector installed
 -- (Supabase already ships with it). Apply in order:
---   001_engram_tables.sql
---   002_engram_search_function.sql
---   003_engram_event_webhook.sql
+--   001_mnestra_tables.sql
+--   002_mnestra_search_function.sql
+--   003_mnestra_event_webhook.sql
 
 create extension if not exists "vector";
 create extension if not exists "pg_trgm";

package/packages/server/src/setup/{engram-migrations/002_engram_search_function.sql → mnestra-migrations/002_mnestra_search_function.sql}

@@ -1,4 +1,4 @@
--- Engram v0.1 — memory_hybrid_search
+-- Mnestra v0.1 — memory_hybrid_search
 --
 -- Reciprocal rank fusion over full-text and semantic search, with the
 -- three SQL-side fixes from RAG-MEMORY-IMPROVEMENTS-AND-TERMDECK-STRATEGY.md:

package/packages/server/src/setup/{engram-migrations/003_engram_event_webhook.sql → mnestra-migrations/003_mnestra_event_webhook.sql}

@@ -1,11 +1,11 @@
--- Engram v0.1 — real-time event webhook (Fix 6)
+-- Mnestra v0.1 — real-time event webhook (Fix 6)
 --
 -- Fix 6 from RAG-MEMORY-IMPROVEMENTS-AND-TERMDECK-STRATEGY.md is a
 -- real-time event intake path so TermDeck (or any other client) can
 -- POST terminal events — "server started on :8080", "tests failing",
 -- "error detected" — and have them land in memory immediately.
 --
--- That intake is implemented as an HTTP endpoint inside the Engram MCP
+-- That intake is implemented as an HTTP endpoint inside the Mnestra MCP
 -- server process, not as a SQL trigger. This file exists as a placeholder
 -- so the migration history is explicit and future database-side changes
 -- (e.g. an events queue table for async ingestion) have a home.

package/packages/server/src/setup/{engram-migrations/004_engram_match_count_cap_and_explain.sql → mnestra-migrations/004_mnestra_match_count_cap_and_explain.sql}

@@ -1,4 +1,4 @@
--- Engram v0.2 — match_count cap + EXPLAIN variant
+-- Mnestra v0.2 — match_count cap + EXPLAIN variant
 --
 -- Two changes to the search surface:
 --
@@ -6,13 +6,13 @@
 --      Default cap: 200. The original function was unbounded, which risks
 --      runaway queries at scale (10k+ rows pulled per call).
 --
---      Override per-database:   ALTER DATABASE your_db SET engram.max_match_count = 500;
---      Override per-session:    SET engram.max_match_count = 500;
+--      Override per-database:   ALTER DATABASE your_db SET mnestra.max_match_count = 500;
+--      Override per-session:    SET mnestra.max_match_count = 500;
 --      Leave unset:             cap defaults to 200.
 --
 --   2. A new function `memory_hybrid_search_explain` that returns
 --      EXPLAIN (ANALYZE, BUFFERS) output for an equivalent call. Used by
---      `engram diagnose` to troubleshoot slow recall queries.
+--      `mnestra diagnose` to troubleshoot slow recall queries.
 --
 -- Rerun-safe: CREATE OR REPLACE on both.
 
@@ -140,7 +140,7 @@ from scored s
 order by s.score desc
 limit least(
   greatest(match_count, 1),
-  coalesce(nullif(current_setting('engram.max_match_count', true), '')::int, 200)
+  coalesce(nullif(current_setting('mnestra.max_match_count', true), '')::int, 200)
 );
 $$;
 

package/packages/server/src/setup/{engram-migrations → mnestra-migrations}/005_v0_1_to_v0_2_upgrade.sql

@@ -1,8 +1,8 @@
--- Engram v0.2 — minimal additive delta for stores provisioned against the
+-- Mnestra v0.2 — minimal additive delta for stores provisioned against the
 -- original rag-system schema.
 --
 -- This migration is idempotent and non-destructive:
---   • adds only the single column (`archived`) that Engram v0.2 reads/writes
+--   • adds only the single column (`archived`) that Mnestra v0.2 reads/writes
 --     but which is absent from the original rag-system `memory_items` table;
 --   • re-creates the two partial indexes under v2 names so they cannot
 --     collide with any pre-existing same-named index that uses a different
@@ -11,7 +11,7 @@
 --     other SQL function — those remain on their production versions.
 --
 -- Apply once, in the Supabase SQL editor, against any existing store that
--- pre-dates Engram v0.2's `archived` soft-delete column.
+-- pre-dates Mnestra v0.2's `archived` soft-delete column.
 
 alter table memory_items
   add column if not exists archived boolean not null default false;

package/packages/server/src/setup/{engram-migrations → mnestra-migrations}/006_memory_status_rpc.sql

@@ -1,4 +1,4 @@
--- Engram migration 006 — memory_status_aggregation RPC
+-- Mnestra migration 006 — memory_status_aggregation RPC
 --
 -- Why: `memoryStatus()` previously did a plain
 --   supabase.from('memory_items').select('project, source_type, category')

package/packages/server/src/setup/prompts.js

@@ -8,7 +8,7 @@
 // hangs. The event-driven path works for both TTY and piped input, which lets
 // us drive the wizard non-interactively in tests:
 //
-//   printf 'a\nb\nc\n' | termdeck init --engram --dry-run
+//   printf 'a\nb\nc\n' | termdeck init --mnestra --dry-run
 //
 // Secret prompts still mute stdout echo when TTY is attached; on non-TTY
 // stdin they fall back to visible input so piped test runs work.

package/packages/server/src/setup/rumen/migrations/001_rumen_tables.sql

@@ -1,6 +1,6 @@
 -- Rumen v0.1 schema
 -- Non-destructive: creates three new tables under the rumen_ namespace.
--- Does NOT modify or reference Engram's existing memory_items / memory_sessions tables.
+-- Does NOT modify or reference Mnestra's existing memory_items / memory_sessions tables.
 --
 -- Apply with:
 --   psql "$DIRECT_URL" -f migrations/001_rumen_tables.sql

package/packages/server/src/setup/supabase-url.js

@@ -1,7 +1,7 @@
 // Parse + validate Supabase URLs and derive what we can from them without the
 // database password. Useful for both init wizards:
 //
-//   - init-engram needs the project ref to show in status output and also
+//   - init-mnestra needs the project ref to show in status output and also
 //     needs a full DATABASE_URL to apply migrations; since the DB password
 //     cannot be derived from the project URL alone, the wizard prompts for
 //     the direct connection string separately.

package/packages/server/src/setup/yaml-io.js

@@ -1,4 +1,4 @@
-// Targeted writer for ~/.termdeck/config.yaml that the `init --engram` wizard
+// Targeted writer for ~/.termdeck/config.yaml that the `init --mnestra` wizard
 // uses to flip `rag.enabled: true` and point secret fields at `${VAR}` refs
 // instead of inline values.
 //
@@ -56,8 +56,8 @@ function updateRagConfig(updates) {
     openaiApiKey: updates.openaiApiKey || rag.openaiApiKey || '${OPENAI_API_KEY}',
     anthropicApiKey: updates.anthropicApiKey || rag.anthropicApiKey || '${ANTHROPIC_API_KEY}',
     syncIntervalMs: rag.syncIntervalMs != null ? rag.syncIntervalMs : 10000,
-    engramMode: rag.engramMode || 'direct',
-    engramWebhookUrl: rag.engramWebhookUrl || 'http://localhost:37778/engram'
+    mnestraMode: rag.mnestraMode || 'direct',
+    mnestraWebhookUrl: rag.mnestraWebhookUrl || 'http://localhost:37778/mnestra'
   };
 
   // Preserve any fields we didn't explicitly handle (e.g. tables, developerId).