gitmem-mcp 1.5.1 → 1.6.1

package/CHANGELOG.md

@@ -7,6 +7,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.6.1] - 2026-05-25
+
+### Fixed
+- **Embeddings not generated on Pro tier**: `embedding.ts`, `variant-generation.ts`, and `transcript-chunker.ts` only checked `process.env.OPENROUTER_API_KEY` — never read the key from `.gitmem/config.json` written by `activate`. Now falls back to `getProConfig()` matching how `supabase-client.ts` already resolves credentials.
+- **Lossy free→pro migration**: Migration sent all local JSON fields to PostgREST — unknown columns caused 400 rejections, silently dropping records (only first 3 errors shown). Added `KNOWN_COLUMNS` whitelist per table, type coercion for `action_protocol`/`self_check_criteria` (array→TEXT), and full error visibility (no cap).
+- **Migration log file**: `.gitmem/migration.log` now written with per-record outcomes (OK/FAIL/SKIP) for debugging.
+- **Mid-migration recovery**: `activate` now detects `.pre-migration` backup files from a previous failed upgrade and re-imports them automatically. No new command — just re-run `activate`.
+- **Credential exposure**: `activate` now auto-adds `.gitmem/` to the project's `.gitignore` when inside a git repo.
+
+### Changed
+- **E2E stress test v1.4**: Restructured from 6 to 8 simulated days. Day 0 wipes Supabase to blank slate. Day 1 seeds realistic 3+ month free-tier user data (starter scars, unknown fields, type mismatches, mixed projects) and tests full upgrade journey including mid-failure recovery and real embeddings from config.json (not env var). 178 tests total.
+
+## [1.6.0] - 2026-05-25
+
+### Added
+- **Free→Pro migration**: Running `activate` with existing local `.gitmem/` data automatically migrates learnings, sessions, decisions, and scar usage to Supabase. Local files are archived with `.pre-migration` suffix.
+- **Schema auto-apply via DATABASE_URL**: `activate` now falls back to direct Postgres connection when `SUPABASE_ACCESS_TOKEN` is unavailable, using `DATABASE_URL` from env, config, or interactive prompt.
+
+### Fixed
+- **Idempotent schema SQL**: `setup.sql` now uses `CREATE TABLE IF NOT EXISTS`, `CREATE OR REPLACE`, and `DO $$ ... END $$` guards throughout — safe to re-run for upgrades without errors.
+
 ## [1.5.1] - 2026-05-13
 
 ### Fixed

package/README.md

@@ -124,11 +124,16 @@ Add this to your MCP client's config file:
 | `npx gitmem-mcp init --client <name>` | Setup for specific client (`claude`, `cursor`, `vscode`, `windsurf`, `generic`) |
 | `npx gitmem-mcp init --yes` | Non-interactive setup |
 | `npx gitmem-mcp init --dry-run` | Preview changes |
+| `npx gitmem-mcp activate <key>` | Activate Pro tier (auto-applies schema) |
+| `npx gitmem-mcp deactivate` | Remove Pro credentials, free device slot |
+| `npx gitmem-mcp setup` | Output schema SQL (for manual Supabase setup) |
 | `npx gitmem-mcp uninstall` | Clean removal (preserves `.gitmem/` data) |
 | `npx gitmem-mcp uninstall --all` | Full removal including data |
 | `npx gitmem-mcp check` | Diagnostic health check |
 
-## Pro Tier — Coming Soon
+## Pro Tier
+
+Self-hosted on your own Supabase. You bring the infrastructure, gitmem sets it up.
 
 | What you get | Why your agent cares |
 |-------------|---------------------|
@@ -136,11 +141,23 @@ Add this to your MCP client's config file:
 | **Session analytics** | Spot patterns in what keeps going wrong |
 | **Sub-agent briefing** | Hand institutional context to sub-agents automatically |
 | **Cloud persistence** | Memory survives machine changes, shareable across team |
-| **A/B testing analytics** | Measure which scar phrasings actually change agent behavior (free tier includes `GITMEM_NUDGE_VARIANT` for manual testing) |
+| **A/B testing analytics** | Measure which scar phrasings actually change agent behavior |
 
-The free tier gives you everything for solo projects. Pro makes recall smarter and memory portable.
+### Quick start
+
+```bash
+npx supabase login                                          # one time
+export SUPABASE_URL="https://yourproject.supabase.co"
+export SUPABASE_SERVICE_ROLE_KEY="eyJ..."
+export OPENROUTER_API_KEY="sk-or-v1-..."
+npx gitmem-mcp activate <your-license-key>
+```
+
+The activate command creates all tables, views, RPC functions, and indexes automatically. No manual SQL needed.
 
-[Join the mailing list](https://gitmem.ai) to get notified.
+See **[docs/pro-setup-guide.md](docs/pro-setup-guide.md)** for the full guide.
+
+The free tier gives you everything for solo projects. Pro makes recall smarter and memory portable.
 
 ## GitMem + MEMORY.md
 

package/bin/gitmem.js

@@ -44,6 +44,10 @@ Usage:
   npx gitmem-mcp uninstall         Clean removal of gitmem from project
   npx gitmem-mcp uninstall --all   Also delete .gitmem/ data directory
 
+Pro Tier Activation:
+  npx gitmem-mcp activate           Activate Pro tier (license key + credentials wizard)
+  npx gitmem-mcp deactivate         Remove Pro credentials from config
+
 Other commands:
   npx gitmem-mcp setup             Output SQL for Supabase schema setup (pro/dev tier)
   npx gitmem-mcp configure         Generate .mcp.json config for Claude Code / Cursor
@@ -876,6 +880,12 @@ switch (command) {
     // New interactive wizard (replaces old cmdInit for CLI usage)
     import("./init-wizard.js");
     break;
+  case "activate":
+    import("../dist/commands/activate.js").then((m) => m.main(process.argv.slice(3)));
+    break;
+  case "deactivate":
+    import("../dist/commands/deactivate.js").then((m) => m.main(process.argv.slice(3)));
+    break;
   case "uninstall":
     import("./uninstall.js");
     break;

package/dist/commands/activate.d.ts

@@ -0,0 +1,20 @@
+/**
+ * GitMem Pro Activation Wizard
+ *
+ * Usage: npx gitmem-mcp activate [license-key]
+ *
+ * Credential resolution (priority order):
+ *   1. Environment variables (SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, OPENROUTER_API_KEY)
+ *   2. Existing values in .gitmem/config.json (re-activation)
+ *   3. Interactive prompt (TTY only)
+ *
+ * Steps:
+ *   1. Accept key as argument or prompt for it
+ *   2. Validate key against our endpoint (register device)
+ *   3. Resolve Supabase URL + service role key (env → config → prompt)
+ *   4. Test Supabase connection (verify tables exist)
+ *   5. Resolve OpenRouter API key (env → config → prompt)
+ *   6. Write everything to ~/.gitmem/config.json
+ */
+export declare function main(args: string[]): Promise<void>;
+//# sourceMappingURL=activate.d.ts.map