carto-md 2.0.5 → 2.0.7

package/CONTRIBUTING.md

@@ -44,9 +44,9 @@ Framework-specific route and model extraction lives inside the language plugins.
 
 ---
 
-## How to add a language (V2 pattern — tree-sitter based)
+## How to add a language (tree-sitter based)
 
-V2 uses tree-sitter for import and symbol extraction. Babel is only used for deep JS/TS route/model extraction on API handler files.
+Carto uses tree-sitter for import and symbol extraction. Babel is only used for deep JS/TS route/model extraction on API handler files.
 
 ### Step 1: Install the grammar
 
@@ -177,7 +177,7 @@ Test on at least 2 real open-source projects using the framework.
 
 ---
 
-## How domain clustering works (V2)
+## How domain clustering works
 
 Domain detection uses **Leiden+CPM graph clustering** (`src/agents/leiden.js`). Files that import each other heavily cluster together. Domain names are inferred from path tokens, with keyword hints for well-known patterns.
 
@@ -215,7 +215,7 @@ cd carto
 npm install
 node src/cli/index.js init   # test in any project
 node src/cli/index.js serve  # test MCP server
-npm test                     # run test suite (35 tests)
+npm test                     # run test suite (62 tests)
 node test/correctness.js     # run correctness tests (31 tests)
 node test/benchmark.js       # run benchmarks against real repos
 ```
@@ -258,7 +258,7 @@ npm run test:bench-ci        # self-bench (matches what bench.yml runs)
 - [ ] Extension added to `CODE_EXTS` and `detectLanguage()` in `sync-v2.js`
 - [ ] No changes to merger logic (unless explicitly fixing a merger bug)
 - [ ] No network calls added
-- [ ] `npm test` passes (35/35)
+- [ ] `npm test` passes (62/62)
 - [ ] `node test/correctness.js` passes (31/31)
 
 ---

package/README.md

@@ -7,93 +7,104 @@
 
 **The structural intelligence layer for AI coding tools.**
 
+Your AI coding tool sees files. Carto sees architecture — domains, blast radius, import graph, routes. Every AI tool you use stops guessing about your codebase and starts knowing it.
+
 ```bash
 npm install -g carto-md
 cd your-project
 carto init
 ```
 
-Carto indexes your codebase — routes, models, import graph, blast radius, domain clusters — and keeps it live via SQLite. Every AI tool you use gets accurate structural facts about your project instead of guessing.
+That's it. Carto auto-wires itself into every AI tool you have installed. Restart your AI tool and it now knows your codebase architecturally.
+
+**Works with:** Cursor · Claude Code · Kiro · Claude Desktop · Windsurf · VS Code Copilot · JetBrains · Zed
 
 ---
 
-## Benchmarks
+## Use it with your AI tool
 
-Measured on real open-source repos. Apple M-series, 8 CPUs, 8GB RAM.
+`carto init` auto-wires the MCP server into every AI tool it detects. If yours wasn't detected, here's the manual config — **one block, copy-paste, done.**
 
-| Repo | Language | Source Files | Indexed | First Run | Second Run | DB Size | Import Edges |
-|------|----------|-------------|---------|-----------|------------|---------|--------------|
-| [prisma/prisma](https://github.com/prisma/prisma) | TypeScript | 3,303 | 3,303 | **1.6s** | **178ms** | 2.2 MB | 3,590 |
-| [supabase/supabase](https://github.com/supabase/supabase) | TypeScript | 6,818 | 6,746 | **4.9s** | **725ms** | 4.3 MB | 5,754 |
-| [microsoft/vscode](https://github.com/microsoft/vscode) | TypeScript | 10,565 | 10,565 | **9.7s** | **1.2s** | 10.6 MB | 19,769 |
-| [zed-industries/zed](https://github.com/zed-industries/zed) | Rust | 1,837 | 1,837 | **2.7s** | **83ms** | 4.7 MB | 2,176 |
+### Cursor
 
-**Second run** = only changed files re-parsed. mtime+size checked before reading content — if nothing changed, nothing is re-parsed.
+`carto init` writes this for you. Manual: `~/.cursor/mcp.json`
+```json
+{ "mcpServers": { "carto": { "command": "carto", "args": ["serve"], "cwd": "/your/project" } } }
+```
 
-**All MCP queries** (blast radius, routes, structure, domains): **<5ms** on all repos.
+### Claude Code (CLI)
 
-### Domains detected
+One command from your project root:
+```bash
+claude mcp add carto -- carto serve
+```
+Or create `.mcp.json` at the project root:
+```json
+{ "mcpServers": { "carto": { "command": "carto", "args": ["serve"] } } }
+```
 
-| Repo | Domains |
-|------|---------|
-| prisma | DATABASE · CORE · EVENTS · AUTH |
-| supabase | CORE · AUTH · DATABASE · PAYMENTS · EVENTS · NOTIFICATIONS · TRPC |
-| vscode | CORE · AUTH · EVENTS · DATABASE · NOTIFICATIONS |
-| zed (Rust) | CORE · DATABASE · AUTH · EVENTS · PAYMENTS · NOTIFICATIONS |
+### Kiro
 
-vscode at 10,565 files in under 10 seconds. Rust import graph working on zed (2,176 edges from `mod` declarations and `use crate::` paths).
+`carto init` writes this for you. Manual: `~/.kiro/settings/mcp.json`
+```json
+{ "mcpServers": { "carto": { "command": "carto", "args": ["serve"], "cwd": "/your/project" } } }
+```
 
----
+### Claude Desktop
+
+`carto init` writes this for you. Manual: `~/Library/Application Support/Claude/claude_desktop_config.json`
+```json
+{ "mcpServers": { "carto": { "command": "carto", "args": ["serve"], "cwd": "/your/project" } } }
+```
 
-## What it does
+### VS Code Copilot
 
+`.vscode/mcp.json` in your project root, or Command Palette → `MCP: Add Server`
+```json
+{ "servers": { "carto": { "command": "carto", "args": ["serve"], "cwd": "/your/project" } } }
 ```
-carto init / carto sync
-  ↓
-Discovers all files (no cap — SQLite handles the volume)
-mtime+size check → skip unchanged files
-tree-sitter parse → imports + symbols (0.05–0.2ms/file)
-Babel deep parse → routes + models (API handler files only)
-Leiden+CPM graph clustering → auto-detects domains
-Computes reverse deps → blast radius for every file
-Writes AGENTS.md + .carto/context/*.md (lazy, on-demand)
-Auto-wires MCP into Kiro, Cursor, Claude Desktop
-  ↓
-carto watch
-  ↓
-File saved → debounce 50ms → re-parse 1 file → SQLite write → <50ms
+
+### Windsurf
+
+`~/.windsurf/mcp.json`
+```json
+{ "mcpServers": { "carto": { "command": "carto", "args": ["serve"], "cwd": "/your/project" } } }
 ```
 
+### Zed / JetBrains / VS Code (full agent mode)
+
+Carto also runs as a full **ACP agent** — not just a passive MCP server, but an active coding agent with architectural awareness. See [ACP Agent](#acp-agent-zed--jetbrains--vs-code) below.
+
 ---
 
-## 16 MCP tools
+## What changes for your AI
 
-`carto serve` exposes a local MCP server. Kiro, Cursor, and Claude query it mid-task.
+Without carto, your AI greps text and guesses. With carto, it queries structural facts:
 
-| Tool | What it returns |
-|------|----------------|
-| `get_architecture()` | 500-word project overview: domains, entry points, stack, key patterns. **Use this first.** |
-| `get_blast_radius(file)` | All files affected by changing a given file, with hop distance |
-| `get_context(file)` | Everything about a file: domain, blast radius, neighbors, routes, models |
-| `get_change_plan(intent)` | Given "add rate limiting to /api/users" → files to touch, domains affected, blast radius, similar patterns |
-| `get_file_summary(file)` | What a file does, its role, key deps and dependents |
-| `get_similar_patterns(file)` | Files with same domain, same route shape, or shared dependencies — find conventions before writing new code |
-| `get_routes()` | All API endpoints with file mapping |
-| `get_structure()` | Import graph, entry points, high-impact files, tech stack |
-| `get_domain(name)` | All routes, models, functions for a domain. Lazily regenerated when stale. |
-| `get_neighbors(file, hops)` | Import graph neighbors: nodes and edges |
-| `get_cross_domain()` | Import edges that cross domain boundaries |
-| `search_routes(query)` | Search API routes by path or method |
-| `get_models(domain?)` | All data models, optionally filtered by domain |
-| `get_high_impact_files(n)` | Top N files by blast radius |
-| `get_env_vars(domain?)` | All env vars with domain mapping |
-| `get_domains_list()` | All detected domains with file, route, model counts |
+> *"Add rate limiting to /api/users"*
+
+**Without carto:** AI grep-searches your codebase, finds 12 files mentioning "users", picks 3 at random, hopes for the best.
+
+**With carto:** AI calls `get_change_plan("add rate limiting to /api/users")` and gets back:
+- The exact route handler file
+- All 7 files that import it (blast radius)
+- The AUTH domain it lives in
+- Similar middleware patterns already in the codebase
+- Cross-domain dependencies that could break
+
+Your AI's response goes from "here's a guess" to "here's the right change with the architectural context."
+
+### In the wild
+
+![Claude Code reviewing the supabase repo through carto's MCP server](docs/screenshots/claude-code-supabase.png)
+
+*Claude Code analyzing the [supabase](https://github.com/supabase/supabase) repo via carto. Real session, no editing — 5,974 files indexed in ~780ms, 86 routes, 4,839 import edges, 7 domains. The agent's own verdict at the bottom: "useful, especially for a large codebase like supabase. The blast radius + cross-domain tools are the most valuable."*
 
 ---
 
 ## Languages and frameworks
 
-### Import graph + symbols (tree-sitter — works on any repo)
+### Import graph + symbols (any repo)
 
 | Language | Extensions |
 |----------|-----------|
@@ -106,16 +117,16 @@ File saved → debounce 50ms → re-parse 1 file → SQLite write → <50ms
 | C# | `.cs` |
 | Ruby | `.rb` |
 
-### Route extraction (framework-specific)
+### Route extraction (framework-aware)
 
 | Framework | Language |
 |-----------|---------|
-| Express, Next.js (App + Pages Router), tRPC, React Router | TypeScript / JavaScript |
+| Express, Next.js (App + Pages), tRPC, React Router | TypeScript / JavaScript |
 | FastAPI, Flask, Django | Python |
 | Gin, Echo, Chi, net/http | Go |
 | Actix-web, Axum, Rocket | Rust |
 | Spring MVC / Boot, JAX-RS | Java |
-| ASP.NET Core (attribute routing + minimal API) | C# |
+| ASP.NET Core | C# |
 | Rails, Sinatra | Ruby |
 
 ### Model extraction
@@ -127,52 +138,18 @@ File saved → debounce 50ms → re-parse 1 file → SQLite write → <50ms
 | Go structs | Go |
 | Rust structs | Rust |
 | JPA `@Entity`, Java records | Java |
-| EF Core classes, C# records | C# |
+| EF Core, C# records | C# |
 | ActiveRecord | Ruby |
 
 ### TypeScript path aliases
 
-Reads `tsconfig.json` / `jsconfig.json` for `paths` config. `@/components/Button` resolves to the actual file in the import graph — blast radius works correctly for Next.js and Vite projects.
-
----
-
-## Domain detection
-
-V2 uses **Leiden+CPM graph clustering** — files that import each other heavily cluster together. Domain names are inferred from path tokens, with keyword hints for well-known patterns (AUTH, PAYMENTS, DATABASE, etc.).
-
-Works on any repo — not just SaaS apps. vscode gets AUTH/EVENTS/DATABASE. zed (Rust) gets DATABASE/AUTH/EVENTS. A game engine would get RENDERER/PHYSICS/AUDIO.
-
-Custom domains via `carto.config.json`:
-
-```json
-{
-  "domains": {
-    "EDITOR": ["editor", "monaco", "text"],
-    "WORKBENCH": ["workbench", "layout", "panel"]
-  }
-}
-```
-
----
-
-## Commands
-
-| Command | What it does |
-|---------|-------------|
-| `carto init` | Detect project, index codebase, generate AGENTS.md, wire MCP |
-| `carto sync` | Full re-index (skips unchanged files via mtime+size cache) |
-| `carto watch` | Incremental live re-index on every file save (<50ms) |
-| `carto serve` | Start MCP server for Kiro / Cursor / Claude |
-| `carto agent` | Start ACP agent mode (for Zed / JetBrains / VS Code) |
-| `carto impact <file>` | Blast radius: risk level, affected files, routes at risk |
-| `carto check` | Cross-domain violations, high-risk uncommitted changes, domain health |
-| `carto remove` | Remove AGENTS.md and .carto/ from project |
+Reads `tsconfig.json` / `jsconfig.json` `paths` config. `@/components/Button` resolves to the actual file in the import graph — blast radius works correctly for Next.js and Vite projects.
 
 ---
 
 ## ACP Agent (Zed / JetBrains / VS Code)
 
-Carto works as a full **ACP agent** — not just a passive tool server, but an active coding agent with architectural awareness.
+Beyond MCP, Carto runs as a full **ACP agent** — an active coding agent with built-in architectural awareness.
 
 ```
 User: "Add rate limiting to /api/users"
@@ -189,20 +166,16 @@ Sends to LLM (your API key) → streams answer + diffs back to editor
 
 ### Setup in Zed
 
-Add to `~/.config/zed/settings.json`:
-
+`~/.config/zed/settings.json`:
 ```json
 {
   "agent_servers": {
-    "Carto": {
-      "command": "carto",
-      "args": ["agent"]
-    }
+    "Carto": { "command": "carto", "args": ["agent"] }
   }
 }
 ```
 
-### BYOK (Bring Your Own Key)
+### Bring Your Own Key
 
 Carto supports any LLM provider — configure in your editor:
 
@@ -217,60 +190,123 @@ Carto supports any LLM provider — configure in your editor:
 | Together AI | Open-source models |
 | Azure OpenAI | Enterprise deployments |
 
-### What makes it different
-
-Other agents are smart but blind. Carto sees the architecture:
-- Auto-indexes your project on first session (1-10s depending on size)
-- Injects structural context into every LLM call (blast radius, domains, routes)
-- 12 internal tools the LLM can call during reasoning
-- Zero cost to you beyond your own API key
-
 ---
 
-## V1 → V2 migration
+## The 16 MCP tools
 
-Run `carto sync` — it auto-migrates your existing `graph-cache.json` and `map.json` into SQLite and renames them to `.bak`. No manual steps.
+Once carto is wired in, your AI tool can call any of these mid-task. You don't need to memorize them — your AI will pick the right ones.
 
-What changed under the hood:
+| Tool | What it returns |
+|------|----------------|
+| `get_architecture()` | 500-word project overview: domains, entry points, stack, key patterns. **Use this first.** |
+| `get_change_plan(intent)` | Given "add rate limiting to /api/users" → files to touch, domains affected, blast radius, similar patterns |
+| `get_blast_radius(file)` | All files affected by changing a given file, with hop distance |
+| `get_context(file)` | Everything about a file: domain, blast radius, neighbors, routes, models |
+| `get_file_summary(file)` | What a file does, its role, key deps and dependents |
+| `get_similar_patterns(file)` | Files with same domain, route shape, or shared deps — find conventions before writing new code |
+| `get_routes()` | All API endpoints with file mapping |
+| `get_structure()` | Import graph, entry points, high-impact files, tech stack |
+| `get_domain(name)` | All routes, models, functions for a domain. Lazily regenerated when stale. |
+| `get_neighbors(file, hops)` | Import graph neighbors: nodes and edges |
+| `get_cross_domain()` | Import edges that cross domain boundaries |
+| `search_routes(query)` | Search API routes by path or method |
+| `get_models(domain?)` | All data models, optionally filtered by domain |
+| `get_high_impact_files(n)` | Top N files by blast radius |
+| `get_env_vars(domain?)` | All env vars with domain mapping |
+| `get_domains_list()` | All detected domains with file, route, model counts |
 
-| | V1 | V2 |
-|---|---|---|
-| Storage | JSON blobs | SQLite (WAL mode, indexed queries) |
-| Parsing | Babel-only | tree-sitter for all languages, Babel only for deep route/model extraction |
-| File limit | 300 cap | Unlimited |
-| Languages | JS/TS/Python/Go/R | + Rust/Java/C++/C#/Ruby |
-| Domain detection | Hardcoded keywords | Leiden+CPM graph clustering |
-| Watcher | Per-file chokidar | Single recursive directory watch (<20 file descriptors) |
-| MCP startup | Re-indexes on start | Opens SQLite instantly (<10ms) |
-| Path aliases | Not resolved | `@/`, `~/` resolved via tsconfig |
+**All MCP queries:** **<5ms** on every benchmarked repo.
 
 ---
 
-## MCP config (if auto-wire missed your IDE)
+## Domain detection
 
-**Kiro** — `~/.kiro/settings/mcp.json`
-```json
-{ "mcpServers": { "carto": { "command": "carto", "args": ["serve"], "cwd": "/your/project" } } }
-```
+Carto uses **Leiden+CPM graph clustering** — files that import each other heavily cluster together. Domain names are inferred from path tokens, with keyword hints for well-known patterns (AUTH, PAYMENTS, DATABASE, etc.).
+
+Works on any repo — not just SaaS apps. vscode gets AUTH/EVENTS/DATABASE. zed (Rust) gets DATABASE/AUTH/EVENTS. A game engine would get RENDERER/PHYSICS/AUDIO.
 
-**Cursor** — `~/.cursor/mcp.json`
+Custom domains via `carto.config.json`:
 ```json
-{ "mcpServers": { "carto": { "command": "carto", "args": ["serve"], "cwd": "/your/project" } } }
+{
+  "domains": {
+    "EDITOR": ["editor", "monaco", "text"],
+    "WORKBENCH": ["workbench", "layout", "panel"]
+  }
+}
 ```
 
-**Claude Desktop** — `~/Library/Application Support/Claude/claude_desktop_config.json`
-```json
-{ "mcpServers": { "carto": { "command": "carto", "args": ["serve"], "cwd": "/your/project" } } }
+---
+
+## CLI commands
+
+| Command | What it does |
+|---------|-------------|
+| `carto init` | Detect project, index codebase, generate AGENTS.md, auto-wire MCP into every AI tool found |
+| `carto sync` | Full re-index (skips unchanged files via mtime+size cache) |
+| `carto watch` | Incremental live re-index on every file save (<50ms) |
+| `carto serve` | Start MCP server (called by your AI tool — usually you don't run this directly) |
+| `carto agent` | Start ACP agent mode (for Zed / JetBrains / VS Code) |
+| `carto impact <file>` | Blast radius: risk level, affected files, routes at risk |
+| `carto check` | Cross-domain violations, high-risk uncommitted changes, domain health |
+| `carto remove` | Remove AGENTS.md and .carto/ from project |
+
+---
+
+## Benchmarks
+
+Measured on real open-source repos. Apple M-series, 8 CPUs, 8GB RAM. SHAs pinned in `~/carto-test-repos`.
+
+| Repo | Language | Indexed Files | First Run | Second Run | DB Size | Import Edges |
+|------|----------|---------------|-----------|------------|---------|--------------|
+| [prisma/prisma](https://github.com/prisma/prisma) | TypeScript | 961 | **649ms** | **110ms** | 0.7 MB | 1,387 |
+| [supabase/supabase](https://github.com/supabase/supabase) | TypeScript | 6,259 | **4.8s** | **751ms** | 4.0 MB | 5,321 |
+| [microsoft/vscode](https://github.com/microsoft/vscode) | TypeScript | 7,567 | **7.8s** | **387ms** | 6.7 MB | 13,420 |
+| [zed-industries/zed](https://github.com/zed-industries/zed) | Rust | 1,752 | **3.0s** | **182ms** | 4.4 MB | 2,113 |
+
+**Indexed Files** counts what Carto actually parses — `.ts/.js/.py/.go/.rs/...` after excluding `node_modules`, build output, and per-file `*.test.*` / `*.spec.*` / `*.stories.*` / `test_*.py` patterns. The on-disk file count of the repo is larger.
+
+**Second run** = only changed files re-parsed. mtime+size checked before reading content — if nothing changed, nothing is re-parsed.
+
+### Domains detected
+
+| Repo | Domains |
+|------|---------|
+| prisma | CORE · DATABASE · EVENTS · AUTH |
+| supabase | CORE · AUTH · DATABASE · PAYMENTS · EVENTS · NOTIFICATIONS · TRPC |
+| vscode | CORE · DATABASE · AUTH · EVENTS · NOTIFICATIONS |
+| zed (Rust) | CORE · DATABASE · AUTH · EVENTS · PAYMENTS · NOTIFICATIONS · TRPC |
+
+vscode at 7,567 indexed files in under 8 seconds. Rust import graph working on zed (2,113 edges from `mod` declarations and `use crate::` paths).
+
+---
+
+## How it works
+
+```
+carto init / carto sync
+  ↓
+Discovers all files (no cap — SQLite handles the volume)
+mtime+size check → skip unchanged files
+tree-sitter parse → imports + symbols (0.05–0.2ms/file)
+Babel deep parse → routes + models (API handler files only)
+Leiden+CPM graph clustering → auto-detects domains
+Computes reverse deps → blast radius for every file
+Writes AGENTS.md + .carto/context/*.md (lazy, on-demand)
+Auto-wires MCP into every AI tool found
+  ↓
+carto watch (optional)
+  ↓
+File saved → debounce 50ms → re-parse 1 file → SQLite write → <50ms
 ```
 
 ---
 
 ## What Carto never does
 
-- Sends your code anywhere. Local only. SQLite on disk.
-- Writes secrets into AGENTS.md. `.cartoignore` blocks `.env` and credential files by default.
-- Touches your manual notes. Writes only between `<!-- CARTO:AUTO:START -->` and `<!-- CARTO:AUTO:END -->`.
-- Costs money. MIT license. Free forever.
+- **Sends your code anywhere.** Local only. SQLite on disk.
+- **Writes secrets into AGENTS.md.** `.cartoignore` blocks `.env` and credential files by default.
+- **Touches your manual notes.** Writes only between `<!-- CARTO:AUTO:START -->` and `<!-- CARTO:AUTO:END -->`.
+- **Costs money.** MIT license. Free forever.
 
 ---
 

package/index.js

@@ -4,17 +4,27 @@
  * carto-md — public module API
  *
  * Usage:
- *   const { Carto } = require('carto-md');
- *   const carto = new Carto();
+ *   const { StoreAdapter } = require('carto-md');
+ *   const carto = new StoreAdapter();
  *   await carto.index('/path/to/project');
  *
- *   // Get everything Kepler needs for a file
+ *   // Get everything an editor agent needs for a file
  *   const ctx = carto.getContextForFile('src/auth/auth.service.ts');
  *
- *   // Listen for live updates
- *   carto.on('updated', ({ file, blastRadius }) => { ... });
+ *   // Read structural facts
+ *   const routes = carto.getRoutes();
+ *   const radius = carto.getBlastRadius('src/auth/auth.service.ts');
+ *   carto.close();
+ *
+ * Back-compat: `Carto` is exported as an alias for `StoreAdapter`.
+ * Existing programs that did `const { Carto } = require('carto-md')`
+ * continue to work without changes. The alias (and the `terminate()`
+ * method on StoreAdapter) will be removed in 3.0.0.
  */
 
-const { Carto } = require('./src/engine/carto');
+const { StoreAdapter } = require('./src/store/store-adapter');
 
-module.exports = { Carto };
+module.exports = {
+  StoreAdapter,
+  Carto: StoreAdapter, // deprecated alias, removed in 3.0.0
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "carto-md",
-  "version": "2.0.5",
+  "version": "2.0.7",
   "description": "Structural intelligence layer for AI coding tools. Indexes your codebase into SQLite — routes, models, import graph, blast radius, domains — and exposes 16 MCP tools for Kiro, Cursor, and Claude.",
   "bin": {
     "carto": "src/cli/index.js"
@@ -29,7 +29,7 @@
     "tree-sitter-typescript": "0.23.2"
   },
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=18.0.0 <26.0.0"
   },
   "author": {
     "name": "Ansh Sonkar",

package/src/acp/agent.js

@@ -70,19 +70,12 @@ class CartoAgent {
   }
 
   // Provider methods
-  async unstable_listProviders(_params) {
-    return { providers: this.providers.list() };
-  }
-
-  async unstable_setProvider(params) {
-    this.providers.set(params);
-    return {};
-  }
-
-  async unstable_disableProvider(_params) {
-    this.providers.disable();
-    return {};
-  }
+  // The custom `unstable_*` provider-management methods (list / set / disable)
+  // were removed in 2.0.7 (Spec 7 Bug 3). The ACP SDK only dispatches the
+  // methods declared in its AGENT_METHODS constant, so those custom routes
+  // returned -32601 "Method not found" anyway. Provider config flows
+  // through env vars / editor settings; ProviderRegistry remains as the
+  // internal configuration carrier.
 
   // Session list/load stubs
   async listSessions(_params) { return { sessions: [] }; }

package/src/acp/providers/index.js

@@ -30,20 +30,12 @@ class ProviderRegistry {
     this._config = null;
   }
 
-  /**
-   * list() — Returns supported providers for ACP providers/list.
-   */
-  list() {
-    return SUPPORTED_PROVIDERS.map(p => ({
-      id: p.id,
-      name: p.name,
-      defaultModel: p.defaultModel,
-      models: p.models,
-    }));
-  }
+  // list() was removed in 2.0.7 (Spec 7 Bug 3). It was only called by the
+  // dropped custom provider-list ACP method, which the SDK never dispatched.
+  // SUPPORTED_PROVIDERS is still exported for external callers / tests.
 
   /**
-   * set(params) — Configures the active provider from ACP providers/set.
+   * set(params) — Configures the active provider.
    * params: { providerId, apiKey, baseUrl?, model? }
    */
   set(params) {

package/src/acp/session.js

@@ -3,7 +3,7 @@
 const crypto = require('crypto');
 const fs = require('fs');
 const path = require('path');
-const { Carto } = require('../engine/carto');
+const { StoreAdapter } = require('../store/store-adapter');
 
 class Session {
   constructor(id, workingDir) {
@@ -23,20 +23,16 @@ class Session {
     if (this._indexed) return null;
 
     const dbPath = path.join(this.workingDir, '.carto', 'carto.db');
-    this.carto = new Carto();
+    const wasIndexed = fs.existsSync(dbPath);
 
-    if (fs.existsSync(dbPath)) {
-      // DB exists — just load the index (fast path, <10ms)
-      await this.carto.index(this.workingDir);
-      this._indexed = true;
-      return null;
-    }
-
-    // No DB — run full indexing
+    this.carto = new StoreAdapter();
     const start = Date.now();
-    await this.carto.index(this.workingDir, { useWorkers: true });
+    await this.carto.index(this.workingDir, { writeOutputs: false });
     this._indexed = true;
 
+    if (wasIndexed) return null;
+
+    // Fresh index — surface status message
     const meta = this.carto.getMeta();
     const duration = ((Date.now() - start) / 1000).toFixed(1);
     const domains = this.carto.getDomainsList();
@@ -64,6 +60,8 @@ class SessionManager {
   }
 
   delete(id) {
+    const s = this._sessions.get(id);
+    if (s && s.carto) s.carto.close();
     this._sessions.delete(id);
   }
 }

package/src/cli/impact.js

@@ -1,7 +1,7 @@
 'use strict';
 
-const path = require('path');
-const { Carto } = require('../../index.js');
+const { StoreAdapter } = require('../store/store-adapter');
+const { normalizeFileArg } = require('../store/path-utils');
 const { checkForUpdate } = require('./update-check');
 
 async function run(projectRoot, fileArg) {
@@ -11,17 +11,22 @@ async function run(projectRoot, fileArg) {
     process.exit(1);
   }
 
-  const carto = new Carto();
+  // Normalize so `./lib/x.js`, absolute paths, and Windows separators
+  // all resolve to the same `files.path` value stored in SQLite.
+  const file = normalizeFileArg(projectRoot, fileArg);
+
+  const carto = new StoreAdapter();
   try {
-    await carto.index(projectRoot, { useWorkers: false });
+    await carto.index(projectRoot);
   } catch (err) {
     console.error(`[CARTO] Error loading index: ${err.message}`);
     process.exit(1);
   }
 
-  const br = carto.getBlastRadius(fileArg);
+  const br = carto.getBlastRadius(file);
   if (!br) {
     console.error(`[CARTO] File not found in project graph: ${fileArg}`);
+    carto.close();
     process.exit(1);
   }
 
@@ -55,7 +60,7 @@ async function run(projectRoot, fileArg) {
   }
 
   console.log('');
-  carto.terminate();
+  carto.close();
 }
 
 module.exports = { run };