A method call on a Map, an Array or a library-typed value links an unrelated project method of the same name #3036

What happens

A method call whose receiver has a declared type that is a builtin (Map, Set, Array) or comes from a library links to a project class's method that happens to share the name.

// cache.ts
export class Cache {
  has(k: string): boolean { return k.length > 0; }
}

// orch.ts
export class Orchestrator {
  private inputs: { paths: Map<string, string> } | null = null;

  check(rel: string): boolean {
    return this.inputs !== null && this.inputs.paths.has(rel);
  }
}

• Expected: no edge. paths is a Map, so has is Map.prototype.has.
• Actual on main (60b0d7a): Orchestrator.check calls cache.ts: Cache::has, with resolvedBy: exact-match.

In codegraph's own source, about 40 call sites do this. Examples:

• this.detectionInputs.diskPaths.has(rel) (a Map) links to LRUCache::has;
• this.extractor.functionTypes.includes(...) (a string[]) links to a property CfnptrFactsOut::includes;
• actionCommand.name() (commander's Command) links to Language::name in web-tree-sitter.d.ts;
• defaults.ignores(rel) (the ignore package) links to ScopeIgnore::ignores.

This is close to #3026 (browser globals), but here the receiver's declared type is written right there, on a field or member type, and the fallback still matches by bare name.

Found by diffing codegraph's call edges against scip-typescript on codegraph's own repo.