memtrace-skills 0.8.11 → 0.8.13

package/dist/transformers/cursor.js

@@ -28,6 +28,41 @@ function writeSkill(skill, rootDir) {
 function isRecord(value) {
     return typeof value === 'object' && value !== null && !Array.isArray(value);
 }
+function hasGitDir(dir) {
+    return fs.existsSync(path.join(dir, '.git'));
+}
+function isFolderGroup(dir) {
+    if (hasGitDir(dir))
+        return false;
+    let count = 0;
+    let entries;
+    try {
+        entries = fs.readdirSync(dir, { withFileTypes: true });
+    }
+    catch {
+        return false;
+    }
+    for (const entry of entries) {
+        if (!entry.isDirectory())
+            continue;
+        if (hasGitDir(path.join(dir, entry.name)))
+            count++;
+        if (count >= 2)
+            return true;
+    }
+    return false;
+}
+function cursorWorkspaceBoundaryWarnings(ctx) {
+    if (ctx.scope !== 'local')
+        return [];
+    if (!isFolderGroup(ctx.cwd))
+        return [];
+    if (fs.existsSync(path.join(ctx.cwd, '.memtrace-workspace')))
+        return [];
+    return [
+        `Cursor install target ${ctx.cwd} contains multiple sibling git repos but is not a blessed Memtrace workspace. For separate MemDBs, install/open each repo root. To intentionally share one MemDB, run 'memtrace start --bless-workspace' from ${ctx.cwd}, then verify with 'memtrace workspace status ${ctx.cwd}'.`,
+    ];
+}
 export function registerCursorMcpAt(mcpFile, binary) {
     const { value, corrupted, backupPath } = safeReadJson(mcpFile);
     if (corrupted) {
@@ -59,6 +94,7 @@ export const cursorTransformer = {
     name: 'cursor',
     async install(skills, ctx) {
         const rootDir = skillsRoot(ctx);
+        const warnings = cursorWorkspaceBoundaryWarnings(ctx);
         if (fs.existsSync(rootDir)) {
             for (const entry of fs.readdirSync(rootDir)) {
                 if (entry.startsWith('memtrace-')) {
@@ -72,6 +108,9 @@ export const cursorTransformer = {
         if (!ctx.skipMcp) {
             const result = registerCursorMcpAt(mcpPath(ctx), ctx.memtraceBinary);
             mcpRegistered = result.registered;
+            if (!mcpRegistered && result.backupPath) {
+                warnings.push(`Cursor MCP config was malformed; backed up to ${result.backupPath}.`);
+            }
         }
         // ─── memtrace-rail ─── Wire the Memtrace-first discovery hook (default
         // observe). Failure must not block the rest of the install.
@@ -87,7 +126,7 @@ export const cursorTransformer = {
             skillsDir: rootDir,
             mcpConfigPath: mcpPath(ctx),
             mcpRegistered,
-            warnings: [],
+            warnings,
         };
     },
     async uninstall(ctx) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memtrace-skills",
-  "version": "0.8.11",
+  "version": "0.8.13",
   "description": "Memtrace skills for AI coding agents — codebase exploration, temporal evolution, impact analysis, and more.",
   "type": "module",
   "bin": {

package/plugins/memtrace-skills/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "memtrace-skills",
   "description": "Memtrace skills for codebase exploration, code search, relationship analysis, temporal evolution, blast radius impact, code quality, graph algorithms, API topology, GitHub PR code review, multi-agent fleet coordination (branch-scoped intents, conflict classification, and agent-judged Class C resolution), and multi-step workflows for change impact, incident investigation, refactoring, session continuity, co-change analysis, and episode replay, Cortex decision memory (decision recall, provenance, intent verification), session bookends (daily briefing, hotspots, self-audit), and single-symbol pre-edit preflight checks.",
-  "version": "0.8.11",
+  "version": "0.8.13",
   "author": {
     "name": "Syncable",
     "email": "support@syncable.dev"

package/plugins/memtrace-skills/skills/memtrace-code-review/SKILL.md

@@ -31,7 +31,10 @@ Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bun
 - Do not create benchmark-specific or PR-specific findings. The review must come from general Memtrace detectors, graph evidence, and policy ranking.
 - If the tool reports missing auth, tell the user to run `memtrace auth login`.
 - If the tool reports missing GitHub App installation, tell the user to install Memtrace Code Reviewer on that repository.
-- If the tool reports missing local graph context, tell the user to run `memtrace index .` at the workspace root.
+- If the tool reports missing local graph context, tell the user to run
+  `memtrace index .` from the actual repo root. If the open folder is a parent
+  containing multiple independent repos, do not index the parent unless the user
+  explicitly wants a shared workspace.
 
 ## Output
 

package/plugins/memtrace-skills/skills/memtrace-first/SKILL.md

@@ -51,6 +51,24 @@ Memtrace:
    root with `incremental: true` (or ask before `clear_existing: true`).
 5. Report the indexing coverage problem instead of silently switching to grep.
 
+### Workspace Boundary Check
+
+Before indexing or reindexing, make sure the target path is the repo the user
+asked about. If the current folder is only a parent that contains multiple
+independent git repos, do **not** index the parent just because it is the open
+editor folder. That creates or reuses a shared `.memdb` and can make agents
+answer from stale repos.
+
+- For separate repos: use the actual git repo root as the `index_directory`
+  path, or ask the user to open/run the agent from that repo root.
+- For an intentional shared workspace: the user should bless it explicitly with
+  `memtrace start --bless-workspace`, then verify it with
+  `memtrace workspace status <path>`; the workspace marker should be present.
+- If `list_indexed_repositories` returns empty or its metadata says the MCP
+  child resolved a data dir from cwd because no workspace marker/git root was
+  found, surface the workspace mismatch. Do not "fix" it by indexing the broad
+  parent folder.
+
 **Never say "the index only covers X, so grep is right" when the target path is
 inside the indexed repository.** That is an indexing freshness/coverage issue,
 not permission to abandon Memtrace.

package/plugins/memtrace-skills/skills/memtrace-index/SKILL.md

@@ -41,6 +41,13 @@ Use the `index_directory` MCP tool:
 - Set `incremental: true` if re-indexing after changes
 - Set `clear_existing: true` only if a full rebuild is needed
 
+If the selected path is just a folder containing multiple independent git repos,
+do not index that parent folder unless the user explicitly wants a shared
+workspace. For separate repos, index each repo root separately. For intentional
+sharing, ask the user to bless the parent explicitly with
+`memtrace start --bless-workspace` first, then verify the boundary with
+`memtrace workspace status <path>`.
+
 **Success criteria:** You receive a `job_id` immediately.
 
 ### 3. Poll for completion

package/skills/commands/memtrace-index.md

@@ -51,6 +51,13 @@ Use the `index_directory` MCP tool:
 - Set `incremental: true` if re-indexing after changes
 - Set `clear_existing: true` only if a full rebuild is needed
 
+If the selected path is just a folder containing multiple independent git repos,
+do not index that parent folder unless the user explicitly wants a shared
+workspace. For separate repos, index each repo root separately. For intentional
+sharing, ask the user to bless the parent explicitly with
+`memtrace start --bless-workspace` first, then verify the boundary with
+`memtrace workspace status <path>`.
+
 **Success criteria:** You receive a `job_id` immediately.
 
 ### 3. Poll for completion

package/skills/workflows/memtrace-code-review.md

@@ -40,7 +40,10 @@ Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bun
 - Do not create benchmark-specific or PR-specific findings. The review must come from general Memtrace detectors, graph evidence, and policy ranking.
 - If the tool reports missing auth, tell the user to run `memtrace auth login`.
 - If the tool reports missing GitHub App installation, tell the user to install Memtrace Code Reviewer on that repository.
-- If the tool reports missing local graph context, tell the user to run `memtrace index .` at the workspace root.
+- If the tool reports missing local graph context, tell the user to run
+  `memtrace index .` from the actual repo root. If the open folder is a parent
+  containing multiple independent repos, do not index the parent unless the user
+  explicitly wants a shared workspace.
 
 ## Output
 

package/skills/workflows/memtrace-first.md

@@ -84,6 +84,24 @@ Memtrace:
    root with `incremental: true` (or ask before `clear_existing: true`).
 5. Report the indexing coverage problem instead of silently switching to grep.
 
+### Workspace Boundary Check
+
+Before indexing or reindexing, make sure the target path is the repo the user
+asked about. If the current folder is only a parent that contains multiple
+independent git repos, do **not** index the parent just because it is the open
+editor folder. That creates or reuses a shared `.memdb` and can make agents
+answer from stale repos.
+
+- For separate repos: use the actual git repo root as the `index_directory`
+  path, or ask the user to open/run the agent from that repo root.
+- For an intentional shared workspace: the user should bless it explicitly with
+  `memtrace start --bless-workspace`, then verify it with
+  `memtrace workspace status <path>`; the workspace marker should be present.
+- If `list_indexed_repositories` returns empty or its metadata says the MCP
+  child resolved a data dir from cwd because no workspace marker/git root was
+  found, surface the workspace mismatch. Do not "fix" it by indexing the broad
+  parent folder.
+
 **Never say "the index only covers X, so grep is right" when the target path is
 inside the indexed repository.** That is an indexing freshness/coverage issue,
 not permission to abandon Memtrace.