milens 0.7.2 → 0.7.3

package/dist/server/mcp.js

@@ -376,62 +376,62 @@ function loadGrepIgnoreRules(rootPath) {
     return ig;
 }
 // ── Server instructions (sent to client via MCP protocol on initialize) ──
-const MILENS_INSTRUCTIONS = `⚠️ CRITICAL: This project is indexed by milens (knowledge graph). Use milens MCP tools BEFORE reading files directly.
-
-WHY: The knowledge graph already knows every symbol, dependency, and reference. Reading files manually = slower, more expensive, and misses hidden connections.
-
-RULE: Before opening ANY file to understand code, call the appropriate milens tool:
-- overview({name: "X"}) — understand a symbol (context + impact + grep). Replaces 3-5 file reads.
-- impact({target: "X", mode: "strict"}) — check blast radius BEFORE editing. strict mode BLOCKS if >5 deps.
-- guard_edit_check({name: "X", session_id}) — HARD safety gate. Call BEFORE every edit. Returns BLOCKED if high risk.
-- grep({pattern: "X"}) — find ALL text references (code, templates, docs, configs, styles).
-- codebase_summary() — 500-token project overview. Use INSTEAD of reading README or exploring directories.
-- detect_changes() — verify changes before committing. Shows changed symbols + risk scores.
-- query({query: "X"}) — find symbol definitions by name. FTS5 instant search.
-
-AUDIT: session_end reports which symbols were safety-checked. Editing without checks = audit gap.
-
-TOKEN SAVINGS: Using milens first typically means far fewer tokens than manual exploration, and fewer missed dependencies — impact/context track code-level references; pair with grep for templates/configs/docs.
-
-milens — code intelligence engine. Indexes codebases into symbol graphs.
-
-## Tool selection
-- \`query\` — find symbol definitions (code identifiers only)
-- \`grep\` — text search ALL files. Use \`scope\` param: all (default), code (source only), imports, definitions
-- \`context\` — 360° view: incoming + outgoing for a symbol
-- \`impact\` — blast radius: what breaks if symbol changes
-- \`overview\` — combined context + impact + grep in one call (preferred for editing workflows)
-- \`guard_edit_check\` — HARD pre-edit gate: blocks if dependents > 5, tracks checks for session audit
-- \`edit_check\` — pre-edit safety: callers + export status + re-export chains + test coverage + ⚠ warnings (fastest for edits)
-- \`trace\` — execution flow: call chains from entrypoints to a symbol (or downstream from it)
-- \`routes\` — detect framework routes/endpoints (Express, FastAPI, NestJS, Flask, Go, PHP, Rails)
-- \`smart_context\` — intent-aware context: understand/edit/debug/test (returns only what matters for intent)
-- \`domains\` — show domain clusters: groups of files forming logical modules based on dependency graph
-- \`repos\` — list all indexed repositories with summary stats (multi-repo support)
-- \`detect_changes\` — git diff → affected symbols
-- \`explain_relationship\` — shortest path between two symbols
-- \`find_dead_code\` — unused exports
-- \`get_file_symbols\` — all symbols in a file
-- \`get_type_hierarchy\` — inheritance tree
-
-## Rules
-- Before editing a symbol: run \`guard_edit_check\` or \`edit_check\` or \`smart_context\` with intent=edit
-- \`guard_edit_check({name, session_id})\` — HARD gate: records check for audit, blocks if dependents > 5
-- \`impact({mode: "strict"})\` — strict mode returns BLOCKED when depth-1 deps > 5
-- For debugging: run \`smart_context\` with intent=debug or \`trace\` to=symbol
-- For writing tests: run \`smart_context\` with intent=test — shows deps to mock + callers to cover
-- \`impact\` only tracks code deps — always pair with \`grep\` for templates/configs
-- Use \`query\` for camelCase/PascalCase identifiers, \`grep\` for display text or multi-word strings
-- impact depth: 1=WILL BREAK, 2=LIKELY AFFECTED, 3=MAY NEED TESTING
-- ⚠ markers indicate unresolved INTERNAL references — external package imports/calls are tracked separately
-- ✓ test coverage shown on edit_check — symbols with no test coverage get a warning
-- ⏳ staleness: files not re-analyzed in 24h are flagged — consider re-running \`milens analyze\`
-
-## Resources (MCP Resources protocol)
-- \`milens://overview\` — index overview (stats, domains, coverage, staleness)
-- \`milens://symbol/{name}\` — symbol context by name
-- \`milens://file/{path}\` — all symbols in a file
-- \`milens://domain/{name}\` — domain cluster details
+const MILENS_INSTRUCTIONS = `⚠️ CRITICAL: This project is indexed by milens (knowledge graph). Use milens MCP tools BEFORE reading files directly.
+
+WHY: The knowledge graph already knows every symbol, dependency, and reference. Reading files manually = slower, more expensive, and misses hidden connections.
+
+RULE: Before opening ANY file to understand code, call the appropriate milens tool:
+- overview({name: "X"}) — understand a symbol (context + impact + grep). Replaces 3-5 file reads.
+- impact({target: "X", mode: "strict"}) — check blast radius BEFORE editing. strict mode BLOCKS if >5 deps.
+- guard_edit_check({name: "X", session_id}) — HARD safety gate. Call BEFORE every edit. Returns BLOCKED if high risk.
+- grep({pattern: "X"}) — find ALL text references (code, templates, docs, configs, styles).
+- codebase_summary() — 500-token project overview. Use INSTEAD of reading README or exploring directories.
+- detect_changes() — verify changes before committing. Shows changed symbols + risk scores.
+- query({query: "X"}) — find symbol definitions by name. FTS5 instant search.
+
+AUDIT: session_end reports which symbols were safety-checked. Editing without checks = audit gap.
+
+TOKEN SAVINGS: Using milens first typically means far fewer tokens than manual exploration, and fewer missed dependencies — impact/context track code-level references; pair with grep for templates/configs/docs.
+
+milens — code intelligence engine. Indexes codebases into symbol graphs.
+
+## Tool selection
+- \`query\` — find symbol definitions (code identifiers only)
+- \`grep\` — text search ALL files. Use \`scope\` param: all (default), code (source only), imports, definitions
+- \`context\` — 360° view: incoming + outgoing for a symbol
+- \`impact\` — blast radius: what breaks if symbol changes
+- \`overview\` — combined context + impact + grep in one call (preferred for editing workflows)
+- \`guard_edit_check\` — HARD pre-edit gate: blocks if dependents > 5, tracks checks for session audit
+- \`edit_check\` — pre-edit safety: callers + export status + re-export chains + test coverage + ⚠ warnings (fastest for edits)
+- \`trace\` — execution flow: call chains from entrypoints to a symbol (or downstream from it)
+- \`routes\` — detect framework routes/endpoints (Express, FastAPI, NestJS, Flask, Go, PHP, Rails)
+- \`smart_context\` — intent-aware context: understand/edit/debug/test (returns only what matters for intent)
+- \`domains\` — show domain clusters: groups of files forming logical modules based on dependency graph
+- \`repos\` — list all indexed repositories with summary stats (multi-repo support)
+- \`detect_changes\` — git diff → affected symbols
+- \`explain_relationship\` — shortest path between two symbols
+- \`find_dead_code\` — unused exports
+- \`get_file_symbols\` — all symbols in a file
+- \`get_type_hierarchy\` — inheritance tree
+
+## Rules
+- Before editing a symbol: run \`guard_edit_check\` or \`edit_check\` or \`smart_context\` with intent=edit
+- \`guard_edit_check({name, session_id})\` — HARD gate: records check for audit, blocks if dependents > 5
+- \`impact({mode: "strict"})\` — strict mode returns BLOCKED when depth-1 deps > 5
+- For debugging: run \`smart_context\` with intent=debug or \`trace\` to=symbol
+- For writing tests: run \`smart_context\` with intent=test — shows deps to mock + callers to cover
+- \`impact\` only tracks code deps — always pair with \`grep\` for templates/configs
+- Use \`query\` for camelCase/PascalCase identifiers, \`grep\` for display text or multi-word strings
+- impact depth: 1=WILL BREAK, 2=LIKELY AFFECTED, 3=MAY NEED TESTING
+- ⚠ markers indicate unresolved INTERNAL references — external package imports/calls are tracked separately
+- ✓ test coverage shown on edit_check — symbols with no test coverage get a warning
+- ⏳ staleness: files not re-analyzed in 24h are flagged — consider re-running \`milens analyze\`
+
+## Resources (MCP Resources protocol)
+- \`milens://overview\` — index overview (stats, domains, coverage, staleness)
+- \`milens://symbol/{name}\` — symbol context by name
+- \`milens://file/{path}\` — all symbols in a file
+- \`milens://domain/{name}\` — domain cluster details
 `;
 // ── Server setup ──
 export function createMcpServer(rootPath) {