@herbertgao/pi-extensions 2026.8.15 → 2026.9.1

package/node_modules/pi-lens/dist/clients/project-diagnostics/scanner.js

@@ -33,27 +33,30 @@ const FACT_RULE_EXTENSIONS = new Set([
     ".mjs",
     ".cjs",
 ]);
-// Which languages the scan runs tree-sitter rules for: every language that has
-// (a loadable grammar) AND (a non-disabled rules/tree-sitter-queries/<lang>/ dir).
+// Which languages the scan runs tree-sitter rules for. Identical to the shared
+// per-edit resolver (EXT_TO_LANG), which since #2424 is itself a projection of
+// the canonical language registry — so the scan and the per-edit path cannot
+// disagree about `.tsx`→tsx / `.jsx`→javascript / the c-vs-cpp header split.
+// (`.tsx` resolves to the tsx grammar, not typescript: the typescript grammar
+// ERRORs on JSX; typescript RULES still apply because `queriesForLanguage(...)`
+// below merges the typescript rule set onto tsx.)
 //
-// The base is the shared per-edit resolver (EXT_TO_LANG — the single
-// ext→grammar-id authority), so c/cpp/csharp/php/css and the .tsx→tsx /
-// .jsx→javascript nuances can never drift from the per-edit path. `.tsx` resolves
-// to the tsx grammar (not typescript: the typescript grammar ERRORs on JSX); // spellchecker:disable-line
-// typescript RULES still apply because `queriesForLanguage(...)` below merges the
-// typescript rule set onto tsx.
+// java + kotlin used to be layered on here because EXT_TO_LANG lacked them:
+// they have loadable grammars and rule dirs (java: 24 rules, kotlin: 1) but no
+// per-edit runner `appliesTo` entry, so only this broad project scan runs them.
+// The registry now owns their extensions, so the spread is gone and this is a
+// plain alias. scanner.test.ts asserts this map covers every non-disabled rule
+// dir whose grammar is loadable, so adding a language dir fails a test until
+// its extension is registered in the registry.
 //
-// java + kotlin are layered on here: they have loadable grammars and rule dirs
-// (java: 24 rules, kotlin: 1) but no per-edit runner `appliesTo` entry, so only
-// this broad project scan runs them. scanner.test.ts asserts this map covers
-// every non-disabled rule dir whose grammar is loadable, so adding a language dir
-// fails a test until its extension is registered here (or in EXT_TO_LANG).
-export const TREE_SITTER_EXT_TO_LANG = {
-    ...EXT_TO_LANG,
-    ".java": "java",
-    ".kt": "kotlin",
-    ".kts": "kotlin",
-};
+// This map is the scan's language RESOLVER, not its eligibility gate: it now
+// answers for grammars with no rule dir too (bash/dart/elixir/lua/ocaml/swift/
+// zig), and the pass gates each file on `hasTreeSitterRules` so a grammar
+// without rules costs no read (#2424 review, F2).
+// `Readonly` because the projection is `Object.freeze`d at the source (#2424
+// review, S4) — the mutable `Record` type is what let the pre-#2424 spread
+// layer java/kotlin on by hand in the first place.
+export const TREE_SITTER_EXT_TO_LANG = EXT_TO_LANG;
 function normalizeSeverity(severity) {
     if (severity === "error" || severity === "warning" || severity === "hint") {
         return severity;
@@ -116,6 +119,29 @@ async function scanFileMajorRules(cwd, files, signal) {
     // file out, so the caller can report a truncated filesScanned honestly.
     let filesScanned = 0;
     let wasmAborted = isTreeSitterWasmAborted();
+    /**
+     * Does this project actually have ENABLED tree-sitter rules for `langId`?
+     *
+     * The gate below used to read "does the extension have a grammar", which was
+     * the same question only because the ext -> grammar map hand-listed exactly
+     * the twelve grammars that also ship a `rules/tree-sitter-queries/<lang>/`
+     * dir. #2424 projected that map from the registry's full grammar column, so
+     * bash/dart/elixir/lua/ocaml/swift/zig arrived WITHOUT rules and every such
+     * file started being read, walked and counted for a rule set that is empty
+     * (#2424 review, F2). Memoized per language: `queriesForLanguage` rebuilds
+     * and filters its array on every call, and the scan asks once per file.
+     */
+    const ruleCoverage = new Map();
+    const hasTreeSitterRules = (langId) => {
+        if (!queryMap || !client)
+            return false;
+        const memo = ruleCoverage.get(langId);
+        if (memo !== undefined)
+            return memo;
+        const covered = queriesForLanguage(queryMap, langId).length > 0;
+        ruleCoverage.set(langId, covered);
+        return covered;
+    };
     const scanTreeSitterFile = async (filePath, langId, content) => {
         if (!queryMap || !langId || !client || content === null)
             return;
@@ -166,6 +192,8 @@ async function scanFileMajorRules(cwd, files, signal) {
             const fileDiagnostics = evaluateAstGrepRules(filePath, rootNode, cwd, detectFileKind(filePath), {
                 maxMatchesPerRule: AST_GREP_SCAN_MAX_MATCHES_PER_RULE,
                 maxTotalDiagnostics: AST_GREP_SCAN_MAX_DIAGNOSTICS_PER_FILE,
+                content,
+                sgModule,
             });
             for (const diagnostic of fileDiagnostics) {
                 astGrep.push(fromDispatchDiagnostic(diagnostic, "ast-grep-napi"));
@@ -190,7 +218,10 @@ async function scanFileMajorRules(cwd, files, signal) {
             if (isTestFile(filePath))
                 continue;
             const ext = path.extname(filePath);
-            const langId = TREE_SITTER_EXT_TO_LANG[ext];
+            // A grammar is not a consumer: only a language this project has
+            // ENABLED rules for can turn this file's bytes into a finding.
+            const grammarId = TREE_SITTER_EXT_TO_LANG[ext];
+            const langId = grammarId && hasTreeSitterRules(grammarId) ? grammarId : undefined;
             const factEligible = FACT_RULE_EXTENSIONS.has(ext);
             let astGrepLang;
             if (sgModule && astGrepCanHandle(filePath)) {