Summary

Closes #2085

A this-qualified call or property read (this.method() / this.prop) was always attributed to the nearest lexically enclosing class, even when a plain (non-arrow) function sat between the access site and that class. JS/TS does not bind this lexically through an ordinary function call, so:

class Session {
  isReady(): boolean { return this._ready; }
  private _ready = true;

  checkExplicit(): void {
    setTimeout(function () {
      return this.isReady(); // NOT the Session instance at runtime
    }, 100);
  }
}

previously produced a false Session.checkExplicit -> Session.isReady edge in both engines.

Changes

• src/extractors/helpers.ts: findParentNode gains an optional isBoundary predicate — when it matches an ancestor before a type-name match is found, the walk stops and returns null.
• src/extractors/javascript.ts: adds findParentClassForThisBinding (stops at a plain function_declaration/function_expression/generator_function_declaration/generator_function, but treats arrow_function as transparent since it inherits this lexically). An inline .bind(this) wrapper (function(){...}.bind(this)) is recognized as re-establishing the outer this and is not treated as a boundary. Used by:
  • collectAccessorPropertyRead's this.field accessor-read branch (ES6 getter/setter property reads are never extracted as call edges #1893/ES6 getter/setter property reads: cross-file accessor recognition (follow-up to #1893) #2030 same-file/cross-file accessor confirmation)
  • extractMemberExprCallInfo's general this.method() call path — when the boundary is crossed, the call is now flagged dynamic: true, dynamicKind: 'unresolved-dynamic' instead of resolving to the wrong class (the true target is statically unknowable, same treatment as other undecidable dynamic call shapes)
• crates/codegraph-core/src/extractors/helpers.rs: mirrors findParentNode's boundary support as find_enclosing_type_name_with_boundary.
• crates/codegraph-core/src/extractors/javascript.rs: mirrors findParentClassForThisBinding/isBoundToOuterThis/the call-site fix in extract_call_info and handle_accessor_property_read.
• Tests added on both sides covering: unbound plain-function callback (flagged), arrow-function callback (still resolves), .bind(this)-wrapped callback (still resolves), nested plain-function-inside-arrow (still flagged), and the accessor-read equivalent.

Verified end-to-end parity by rebuilding the native addon locally and comparing codegraph query output between --engine native and --engine wasm against the issue's repro — both now correctly report only checkArrow/checkBound as callers of Session.isReady, excluding checkExplicit.

Filed #2321 for an unrelated pre-existing artifact noticed during this investigation (.bind() called directly on an inline function expression emits a Call whose receiver is the entire function's raw source text) — out of scope for this fix.

Test plan

• cargo test -p codegraph-core --lib — 816 passed (including 4 new tests)
• npx vitest run tests/parsers/javascript.test.ts — 308 passed (including 5 new tests)
• npm test — full suite, 4542 passed
• npx tsc --noEmit clean
• cargo build -p codegraph-core --lib clean
• Manual native-vs-wasm parity check via codegraph build --engine native|wasm + codegraph query on the issue's repro fixture
• codegraph diff-impact --staged -T reviewed