Feature/multi client distribution#4
Closed
nTEG-dev wants to merge 3 commits into
Closed
Conversation
… tool Tool descriptions and field hints now guide agents to frame scars as knowledge discoveries rather than self-criticism. Baseline measured: 34% explicit, 43% passive, 21% dead weight. Target: explicit ↑ 45%+, dead weight ↓ 10%. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
record_scar_usage and record_scar_usage_batch now fall back to detectAgent() and getCurrentSession() when caller omits agent/session_id. Reduces null entries in scar_usage table. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…horitative (OD-726) Local-only threads (in threads.json but not in Supabase active set) were being unconditionally preserved, assuming they were mid-session creates not yet synced. In reality, most were resolved/archived in Supabase — the NOT-IN query excluded them, making them indistinguishable from truly local threads. Now only preserves local-only threads that have a valid ID and were created within the last 24h. Stale ghosts are dropped with a log message. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
CLCrawford-dev
pushed a commit
that referenced
this pull request
May 25, 2026
Setup SQL now handles upgrades gracefully: - ALTER TABLE ADD COLUMN IF NOT EXISTS for all columns (runs before indexes so embedding columns exist before ivfflat index creation) - DROP POLICY IF EXISTS before CREATE POLICY (policies have no IF NOT EXISTS clause) - DROP TRIGGER IF EXISTS before CREATE TRIGGER - CREATE OR REPLACE FUNCTION for RPC functions (already idempotent) Users can re-run `gitmem-mcp activate` or apply setup SQL again after upgrading gitmem-mcp and any new columns/tables will be added without errors or data loss. Verified: schema applies cleanly on fresh DB and re-runs without error on existing DB with data. Resolves GIT-45 concern #6 (no schema migration path). Also resolves concern #4 (pgvector confirmed available on Supabase free tier). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Brief description of what this PR does.
Why
Motivation — what problem does this solve?
How to Test
Steps to verify the change works:
Checklist
npm run test:unitpassesnpm run test:e2epasses (if tool/CLI changes)Breaking Changes
None / Describe what breaks and migration path.