@mrclrchtr/supi-code-intelligence 1.3.1 → 1.4.0

package/node_modules/@mrclrchtr/supi-lsp/src/tsconfig-scope.ts

@@ -1,156 +0,0 @@
-// tsconfig-aware file scope detection.
-//
-// Determines whether a file is within the compilation scope of its nearest
-// tsconfig.json by checking `include` and `exclude` patterns. Used by the
-// diagnostic filter to suppress LSP errors on files that TypeScript itself
-// would not type-check.
-
-import * as fs from "node:fs";
-import * as path from "node:path";
-
-interface TsconfigInfo {
-  dir: string;
-  include: string[] | undefined;
-  exclude: string[] | undefined;
-}
-
-const cache = new Map<string, TsconfigInfo | null>();
-
-/**
- * Check whether a file is excluded by its nearest tsconfig.json.
- *
- * @param filePath - Project-relative file path (e.g., "packages/foo/__tests__/x.test.ts")
- * @param cwd - Absolute project root directory
- * @returns `true` if the file is excluded from compilation scope
- */
-export function isFileExcludedByTsconfig(filePath: string, cwd: string): boolean {
-  const absolutePath = path.resolve(cwd, filePath);
-  const tsconfig = findNearestTsconfig(path.dirname(absolutePath), cwd);
-  if (!tsconfig) return false;
-
-  const relativeToTsconfig = path.relative(tsconfig.dir, absolutePath).replaceAll("\\", "/");
-
-  // Check exclude patterns first
-  if (tsconfig.exclude) {
-    for (const pattern of tsconfig.exclude) {
-      if (matchesPattern(relativeToTsconfig, pattern)) return true;
-    }
-  }
-
-  // If include is specified, the file must match at least one pattern
-  if (tsconfig.include) {
-    let included = false;
-    for (const pattern of tsconfig.include) {
-      if (matchesPattern(relativeToTsconfig, pattern)) {
-        included = true;
-        break;
-      }
-    }
-    if (!included) return true;
-  }
-
-  return false;
-}
-
-/**
- * Find the nearest tsconfig.json walking upward from `startDir`,
- * stopping at `rootDir`.
- */
-function findNearestTsconfig(startDir: string, rootDir: string): TsconfigInfo | null {
-  let dir = startDir;
-  while (true) {
-    const cached = cache.get(dir);
-    if (cached !== undefined) return cached;
-
-    const tsconfigPath = path.join(dir, "tsconfig.json");
-    if (fs.existsSync(tsconfigPath)) {
-      const info = parseTsconfig(dir, tsconfigPath);
-      cache.set(dir, info);
-      return info;
-    }
-
-    if (path.relative(rootDir, dir).startsWith("..") || dir === rootDir) {
-      // Don't look above the project root
-      return null;
-    }
-
-    const parent = path.dirname(dir);
-    if (parent === dir) {
-      return null;
-    }
-    dir = parent;
-  }
-}
-
-function parseTsconfig(dir: string, tsconfigPath: string): TsconfigInfo | null {
-  try {
-    const raw = fs.readFileSync(tsconfigPath, "utf-8");
-    // Strip comments without touching content inside double-quoted strings.
-    const cleaned = raw
-      .replace(/("(?:\\.|[^"\\])*")|\/\/.*$/gm, "$1")
-      .replace(/("(?:\\.|[^"\\])*")|\/[\s\S]*?\*\//g, "$1");
-    const json = JSON.parse(cleaned);
-    return {
-      dir,
-      include: json.include as string[] | undefined,
-      exclude: json.exclude as string[] | undefined,
-    };
-  } catch {
-    return null;
-  }
-}
-
-/**
- * Lightweight pattern matching for tsconfig include/exclude patterns.
- * Handles directory names, extensions, recursive globs, and literal paths.
- */
-function matchesPattern(filePath: string, pattern: string): boolean {
-  const normalizedPattern = pattern.replaceAll("\\", "/");
-
-  // Directory-prefixed recursive glob: prefix/**/*.ext
-  if (normalizedPattern.includes("/**/")) {
-    const idx = normalizedPattern.indexOf("/**/");
-    const prefix = normalizedPattern.slice(0, idx);
-    const suffix = normalizedPattern.slice(idx + 4);
-    return (
-      filePath.startsWith(`${prefix}/`) && matchesPattern(filePath.slice(prefix.length + 1), suffix)
-    );
-  }
-
-  // Recursive glob: **/*.ext
-  if (normalizedPattern.startsWith("**/")) {
-    const suffix = normalizedPattern.slice(3); // e.g., "*.ts"
-    return matchesPattern(filePath, suffix) || filePath.includes(`/${suffix}`);
-  }
-
-  // Directory match: pattern has no glob chars and no "."
-  // e.g., "node_modules" or "__tests__"
-  if (!normalizedPattern.includes("*") && !normalizedPattern.includes(".")) {
-    return (
-      filePath === normalizedPattern ||
-      filePath.startsWith(`${normalizedPattern}/`) ||
-      filePath.includes(`/${normalizedPattern}/`)
-    );
-  }
-
-  // Simple glob: *.ext — match basename
-  if (normalizedPattern.startsWith("*.")) {
-    const ext = normalizedPattern.slice(1); // e.g., ".ts"
-    return filePath.endsWith(ext) && !filePath.includes("/", filePath.length - ext.length - 1);
-  }
-
-  // Literal path
-  if (!normalizedPattern.includes("*")) {
-    return filePath === normalizedPattern || filePath.startsWith(`${normalizedPattern}/`);
-  }
-
-  // Fallback: path contains the pattern segment
-  return filePath.includes(`/${normalizedPattern}`) || filePath === normalizedPattern;
-}
-
-/**
- * Clear the tsconfig cache. Useful for testing or after filesystem changes.
- */
-export function clearTsconfigCache(): void {
-  cache.clear();
-}

package/src/guidance.ts

@@ -1,42 +0,0 @@
-// Prompt guidance and tool description for the code_intel tool.
-
-export const toolDescription = `Code intelligence tool — architecture briefs, semantic relationships, impact analysis, structured text search, and project indexing.
-
-Actions:
-- brief: Architecture overview or focused brief for a project, package, directory, file, or anchored symbol
-- callers: Find call sites for a symbol, or analyze a file-level export surface when only \`file\` is provided
-- callees: Best-effort outgoing calls from a symbol (structural tree-sitter analysis across supported grammars)
-- implementations: Find concrete implementations of an interface or abstract type
-- affected: Blast-radius analysis for a symbol or exported file surface — direct references, downstream dependents, risk level, likely tests
-- pattern: Bounded text search with grouped matches, context lines, structured \`kind\` filters (\`definition\` | \`export\` | \`import\`), partial-result warnings on oversized structured scans, and regex opt-in via \`regex: true\`
-- index: Factual project map — file counts by language, top-level directory tree, landmark config files
-
-Coordinates are 1-based (line, character) with UTF-16 character columns, matching lsp and tree_sitter conventions.
-Relative paths resolve from the session working directory. A leading @ on path/file is stripped automatically.
-
-Examples:
-  { "action": "brief" }
-  { "action": "brief", "path": "packages/supi-lsp/" }
-  { "action": "brief", "file": "packages/supi-lsp/lsp.ts", "line": 42, "character": 7 }
-  { "action": "callers", "file": "packages/supi-core/index.ts" }
-  { "action": "callers", "symbol": "registerSettings", "path": "packages/supi-core/" }
-  { "action": "callees", "file": "src/handler.ts", "line": 88, "character": 12 }
-  { "action": "implementations", "symbol": "SessionLspService", "path": "packages/" }
-  { "action": "affected", "file": "packages/supi-core/index.ts" }
-  { "action": "pattern", "pattern": "registerSettings", "path": "packages/", "maxResults": 10 }
-  { "action": "pattern", "pattern": "register(Settings|Config)", "path": "packages/", "regex": true, "maxResults": 10 }
-  { "action": "pattern", "pattern": "payment", "kind": "definition", "path": "src/" }`;
-
-export const promptSnippet =
-  "Use the code_intel tool for architecture orientation, semantic relationships, impact analysis, and structured search before broad file reads.";
-
-export const promptGuidelines = [
-  "Use `code_intel brief` before editing an unfamiliar package, directory, or file to get architecture context and reduce blind reads.",
-  "Use `code_intel affected` before changing exported APIs, shared helpers, config surfaces, or cross-package contracts to check blast radius and risk; file-only requests now expand across exported targets when possible.",
-  "Use `code_intel callers` before modifying a function to verify all call sites; use `callees` and `implementations` for dependency and interface analysis, and use file-only `callers` when you need the export surface of a module.",
-  'Use `code_intel pattern` for bounded, scope-aware text search when the question is textual rather than semantic; it treats patterns as literal strings by default, supports `regex: true`, supports `kind: "definition" | "export" | "import"` for structured searches, and may return a partial-result warning when a structured scan is too broad.',
-  "Use `code_intel brief` and `code_intel affected` priority signals to notice diagnostics, low coverage, or unused-code hints before editing risky files.",
-  "Use `code_intel index` for a factual project map (file counts, directory structure, landmark files) when you need to orient yourself in a new codebase.",
-  "After `code_intel` narrows the target, use raw `lsp` and `tree_sitter` tools for precise drill-down on exact symbols, types, or AST nodes.",
-  "Do not prefer `code_intel` over direct file reads or lower-level tools for trivial, already-localized edits or exact symbol/AST drill-down tasks.",
-];