[Puma7]

Named JS/TS class expressions currently omit their class, member ownership and inheritance. Extract that structure in both WASM and native TS/JS, while keeping the expression's inner name scoped to its body.

Closes #2499.

Retain real class-header signatures across persistence and reject leaked inner-name targets, including references from Vue/Svelte. Preserve independently visible outer bindings. The fallback scope map is cached, uses compact integer storage and is only needed to recover competing outer bindings; other language targets return immediately.

Validation: 32 expression/scope tests plus 120 native/WASM parity tests pass with the native kernel active (152 total, no skips). Ruby and node-identity controls are included. Anonymous traversal and the database/kernel ABI are unchanged. Re-index after upgrading.

Combined validation against main 80e4b459 (Windows, Node 24, WASM, two workers): 6,752 passed, zero failed, 406 skipped under existing platform/kernel gates; standard timeouts unchanged. Separate active-native checks passed 152 class/parity and 112 constructor/super cases. These are local results, not GitHub CI or other-OS claims.

[Puma7]

Updated validation after the supplied review:

The scope guard is retained: removing it links new Widget() outside register(class Widget {}) even though JavaScript throws ReferenceError, and can steal a real same-named outer binding. It now skips other language targets and retains a compact scope map without the unused source copy. The supplied minimal patch passes 10/32 current class tests; 16 failures are header-signature assertions, six cover persisted/scope behavior. The exact version behind the reported 26/32 result was not supplied. All 152 selected tests pass on the revised native build.

[inth3shadows]

Thanks for this. Indexing named class expressions with their members and extends edge is useful. I found one case where it adds a cross-file edge, though, tested on the PR head (9f31a24) against its base (80e4b45) and current main (847f1df):

// a.js
function register(c) { return c; }
register(class Widget { run() {} });

// b.js — no import of anything from a.js
export function use() {
  const w = new Widget();
  w.run();
}

• This branch: use → a.js:Widget::run
• Base and main: no such edge
• Expected: none. A class expression's name is only in scope inside its own body, so Widget in b.js can't refer to it.

It looks like an instance-method result is accepted whenever the receiver isn't the class's inner name (w ≠ Widget), including from another file. Gating it on whether the receiver's constructor binding can actually see the class expression (same file, or an outer binding initialised by it) would close this.

The branch is also 171 commits behind and conflicts in src/extraction/languages/typescript.ts and codegraph-kernel/src/tsjs/mod.rs. I'm happy to share the test file I used.

[colbymchenry]

Thanks @Puma7 for #2499 and this PR. Named class expressions are now indexed as classes with their own methods, extends and super calls, in both the native and WebAssembly parsers, through #2825, which ships in the next release. Your named-class-expression tests pass on current main. Closing as superseded. Thank you!