fix(perf): add parser.ts to canary paths and free WASM tree on symbolsOnly inline path

Guard the inline-path optimization against regressions by adding
src/domain/parser.ts to the perf-canary paths filter — without it the
canary silently skips exactly the file this PR modifies.

Also free the WASM-backed tree when symbolsOnly=true in parseFilesWasmInline.
The tree was being parsed and then discarded without an explicit .delete() call,
leaking WASM linear memory on every incremental rebuild that triggers the inline
path.  The deletion is guarded by a typeof check, matching the pattern used by
the extractor-error path at line 1078.

Author: carlos-alm

.github/workflows/perf-canary.yml

@@ -19,6 +19,7 @@ on:
     paths:
       - "src/extractors/**"
       - "src/domain/graph/**"
+      - "src/domain/parser.ts"
       - "crates/**"
       - "scripts/benchmark.ts"
       - "scripts/incremental-benchmark.ts"

src/domain/parser.ts

@@ -1230,6 +1230,12 @@ async function parseFilesWasmInline(
     // are needed by callers like the this/super dispatch post-pass.
     if (!symbolsOnly) {
       symbols._tree = extracted.tree;
+    } else if (typeof (extracted.tree as any)?.delete === 'function') {
+      // Free the WASM-backed tree immediately — web-tree-sitter trees are backed
+      // by WASM linear memory and require explicit disposal.  When symbolsOnly is
+      // true the tree is never stored anywhere, so we must delete it here to
+      // avoid leaking WASM heap on every incremental rebuild.
+      (extracted.tree as any).delete();
     }
     symbols._langId = extracted.langId;
     result.set(relPath, symbols);