cgraphx 2.0.2 → 2.0.3

package/dist/core/code/engine/core/ingestion/scope-resolution/contract/scope-resolver.js

@@ -0,0 +1,282 @@
+"use strict";
+/**
+ * `ScopeResolver` — the per-language contract consumed by the generic
+ * scope-resolution orchestrator (`runScopeResolution`).
+ *
+ * ## Migration cookbook (next language)
+ *
+ * To add a language to the registry-primary path:
+ *
+ *   1. Implement `ScopeResolver` in
+ *      `cgraph/src/core/ingestion/languages/<lang>/scope-resolver.ts`.
+ *      Nine required fields (language, languageProvider,
+ *      importEdgeReason, resolveImportTarget, mergeBindings,
+ *      arityCompatibility, buildMro, populateOwners, isSuperReceiver)
+ *      plus optional toggles / hooks:
+ *        - propagatesReturnTypesAcrossImports (default true)
+ *        - fieldFallbackOnMethodLookup (default true — turn OFF for
+ *          statically-typed languages; the heuristic over-connects)
+ *        - elementTypeOf — container element type, by subscript or accessor
+ *        - collapseMemberCallsByCallerTarget — one edge per caller/target
+ *        - populateNamespaceSiblings — cross-file implicit visibility
+ *        - hoistTypeBindingsToModule — enable ONLY when method return
+ *          types are stored on the enclosing Module scope; most
+ *          languages attach them to the class scope and leave this off
+ *   2. Export a thin entry point:
+ *      `runYourLangScopeResolution(input) = runScopeResolution(input, yourScopeResolver)`.
+ *   3. Register the provider in
+ *      `cgraph/src/core/ingestion/scope-resolution/pipeline/registry.ts`
+ *      (the `SCOPE_RESOLVERS` map). That registration is all it takes — the
+ *      `scopeResolutionPhase` runs every registered resolver.
+ *   4. Verify the resolver integration test at
+ *      `cgraph/test/integration/resolvers/<lang>.test.ts` passes (it runs
+ *      in the standard test suite). Scope-resolution is the only resolution
+ *      path — the legacy call-resolution DAG was removed in RING4-1 #942.
+ *
+ * No new pipeline phase, no orchestrator copy-paste, no workflow
+ * change. The generic `scopeResolutionPhase` auto-discovers everything via
+ * the `SCOPE_RESOLVERS` map.
+ *
+ * ## ScopeResolver vs LanguageProvider
+ *
+ * The codebase has two provider contracts. Their lifecycles differ:
+ *
+ *   - `LanguageProvider` (`language-provider.ts`) is the
+ *     **parsing-side** contract — how to emit captures, classify
+ *     scopes, interpret imports / typeBindings. ~40 fields covering
+ *     both legacy and new pipelines. Consumed by `ScopeExtractor`,
+ *     once per file at extract time.
+ *   - `ScopeResolver` (this file) is the **emit-side** contract — how
+ *     the resolution pipeline dispatches references to graph edges.
+ *     8 fields total. Consumed by `runScopeResolution`, once per
+ *     workspace at resolve time.
+ *
+ * They share three concept names (`arityCompatibility`, `mergeBindings`,
+ * `resolveImportTarget`) because the emit pipeline reuses a few
+ * finalize hooks. Per-language wiring passes the SAME function
+ * reference through both interfaces — no second copy of the logic.
+ * Rationale for not collapsing: lifecycle separation, and merging
+ * would create a god-interface complicating future migrations.
+ *
+ * ## Reference implementation
+ *
+ * `cgraph/src/core/ingestion/languages/python/scope-resolver.ts` —
+ * `pythonScopeResolver` is the canonical example. Read that file when
+ * migrating a new language; this interface lists the fields that
+ * implementation populates.
+ *
+ * ## Contract Invariants the orchestrator depends on
+ *
+ * These are non-obvious behaviors that the orchestrator and the
+ * existing Python + C# resolvers depend on. Future implementers will
+ * break them silently if not documented.
+ *
+ *   - **I1 — Phase 4 emission order is load-bearing.** `emitReceiverBoundCalls`
+ *     runs FIRST (populates `handledSites`), then `emitFreeCallFallback`,
+ *     then `emitReferencesViaLookup` (consumes `handledSites` as a skip
+ *     set), then `emitImportEdges`. Reordering breaks same-name collision
+ *     resolution: the shared lookup can mis-resolve `app_metrics.get_metrics()`
+ *     to a same-named local function, and only the precise per-receiver
+ *     pass running first prevents the wrong edge.
+ *
+ *   - **I2 — `handledSites` semantics.** A site is added to
+ *     `handledSites` IFF a `tryEmitEdge` call returned `true` for it.
+ *     Sites a pass touched but couldn't resolve do NOT get marked —
+ *     they still get a chance from the shared resolver. Exception:
+ *     the free-call fallback marks the site unconditionally after
+ *     attempting emission (even on dedup-collapse), because the
+ *     per-(caller, target) collapse semantics require multiple call
+ *     sites in the same caller body not produce multiple edges.
+ *     `preEmitInheritanceEdges` also pre-marks every `inherits` site so
+ *     the generic bridge cannot remap class heritage into method-owned
+ *     EXTENDS edges via `resolveCallerGraphId`.
+ *
+ *   - **I3 — `propagateImportedReturnTypes` mutation timing + ordering.**
+ *     The pass mutates `Scope.typeBindings` (a plain `new Map(...)` from
+ *     `draftToScope`, NOT frozen). It MUST run AFTER `finalizeScopeModel`
+ *     (so `indexes.bindings` is populated) and BEFORE
+ *     `resolveReferenceSites` (so resolution sees the propagated types).
+ *     The pass also re-runs `followChainPostFinalize` on every scope's
+ *     typeBindings because scope-extractor's pass-4 already ran and
+ *     missed any chain whose terminal lives in a foreign file.
+ *     Within the pass, files are walked in `indexes.sccs` reverse-
+ *     topological order (leaves first) so multi-hop alias chains
+ *     (e.g. `models.User → service.user → app.user`) collapse to the
+ *     terminal class in a single pass — every importer sees its
+ *     source's already-chain-followed typeBindings. Cyclic SCCs reach
+ *     a partial fixpoint within a single pass without iterating to
+ *     convergence; `ts-circular` only asserts pipeline-no-throw.
+ *
+ *   - **I4 — `emitReceiverBoundCalls` case order.** Cases are evaluated
+ *     in this order; the FIRST that emits an edge wins:
+ *       1. super branch (`provider.isSuperReceiver(receiverName)`)
+ *       2. Case 0 compound (`receiverName` has `.` or `(`)
+ *       3. Case 0.5 implicit-`this` chain walk — GATED: fires only for
+ *          languages that set `resolveThisViaEnclosingClass === true`;
+ *          it intercepts every bare-`this` call/read/write site ahead of
+ *          Case 4 and does NOT emit the interface-dispatch fan-out that
+ *          Cases 0, 3b and 4 all perform (Case 0 gained it in #2829 and
+ *          Case 3b in #2832, leaving 0.5 the only INSTANCE-receiver case
+ *          that folds or walks to a receiver type without fanning out.
+ *          Read that narrowly: Case 2 also walks an MRO and its binding
+ *          admits `Interface`, but its receiver IS the type name, so the
+ *          site is static dispatch and a fan-out would be wrong; Cases 3
+ *          and 5 resolve by direct lookup rather than a fold or MRO walk,
+ *          and no language is known to reach Case 3 with an Interface —
+ *          every one that could strips the namespace qualifier first,
+ *          sending it to Case 4), so enabling the toggle
+ *          for a language changes that language's `this` dispatch
+ *          semantics (see the toggle's doc below)
+ *       4. Case 1 namespace-receiver
+ *       5. Case 2 class-name receiver
+ *       6. Case 3 dotted typeBinding for namespace prefix
+ *       7. Case 3b chain-typebinding (compound resolver + interface-dispatch
+ *          fan-out on an Interface fold, #2832)
+ *       8. Case 4 simple typeBinding (MRO walk + findOwnedMember)
+ *     Reordering or merging cases changes resolution semantics. The
+ *     numbering is part of the contract — keep the comments.
+ *
+ *   - **I5 — Pre-seeding `seen` from `referenceIndex` is forbidden.**
+ *     Earlier versions of the receiver-bound pass pre-populated `seen`
+ *     to avoid double-emit. After Phase 4 was reordered, pre-seeding
+ *     became actively harmful: it suppresses correct emissions for
+ *     sites the shared resolver happened to resolve to a wrong target.
+ *     The orchestrator MUST NOT pre-seed.
+ *
+ *   - **I6 — `Scope.typeBindings` is mutable post-finalize.** `draftToScope`
+ *     (in `scope-extractor.ts`) builds `typeBindings` as a plain
+ *     `new Map(...)` — not frozen, intentionally. Passes below rely on
+ *     this. Do NOT freeze `typeBindings` in any downstream refactor.
+ *
+ *   - **I7 — `ScopeResolver` and `LanguageProvider` are distinct contracts.**
+ *     Python and C# pass the SAME function reference through both
+ *     interfaces where they share a hook name — no second copy of the
+ *     logic. Rationale for not collapsing them: lifecycles differ
+ *     (parsing-side runs once per file at extract time, emit-side runs
+ *     once per workspace at resolve time), and merging would create a
+ *     god-interface that complicates future migrations.
+ *
+ *   - **I8 — Binding-channel lifecycle.** Post-finalize binding lookup
+ *     fans across several channels (`lookupBindingsAt` /
+ *     `findReceiverTypeBinding` consult them in precedence order):
+ *     `indexes.bindings` (frozen finalize output), `Scope.bindings`
+ *     (lexical local, first-tier shadowing), `indexes.bindingAugmentations`
+ *     (per-scope append-only), `indexes.workspaceFqnBindings` +
+ *     `indexes.workspaceTypeBindings` (scope-independent / global, consulted
+ *     unconditionally), and `indexes.namespaceFqnBindings` +
+ *     `indexes.namespaceTypeBindings` (per-namespace, consulted only for the
+ *     namespaces in `indexes.accessibleNamespacesByScope` for the caller's
+ *     module). All but `indexes.bindings` are mutable post-finalize and
+ *     populated by hooks; only `indexes.bindings` is frozen.
+ *
+ *     `indexes.bindings` is the **finalize-output channel**. After
+ *     `finalizeScopeModel` returns, its inner `BindingRef[]` arrays
+ *     are deep-frozen by `materializeBindings` and MUST NOT be
+ *     mutated by any post-finalize hook. Treat `indexes.bindings` as
+ *     immutable from the moment `finalizeScopeModel` returns.
+ *
+ *     `indexes.bindingAugmentations` is the **post-finalize
+ *     append-only channel**. Hooks like `populateNamespaceSiblings`
+ *     append cross-file bindings synthesized after finalize (C#
+ *     same-namespace visibility, `using static` member exposure)
+ *     into this channel, NOT into `indexes.bindings`. Inner arrays
+ *     here are NEVER frozen — hooks `push()` directly. Any consumer
+ *     that reads post-finalize workspace bindings MUST query both
+ *     index channels via `lookupBindingsAt`
+ *     (`scope-resolution/scope/walkers.ts`); the helper returns
+ *     finalized refs first, appends unique augmentation refs after,
+ *     and dedupes by `def.nodeId` so finalized metadata wins on
+ *     duplicate defs. Per-`Scope.bindings` local declarations are the
+ *     lexical extraction channel and remain a separate first-tier
+ *     lookup for local shadowing.
+ *
+ *     `Scope.typeBindings` remains mutable post-finalize per I6 (it
+ *     is intentionally not frozen at any point).
+ *
+ *     The `ReadonlyMap<...>` types on `ScopeResolutionIndexes` are
+ *     compile-time read-guidance for consumers; structural mutation
+ *     of `bindingAugmentations` is performed via a deliberate
+ *     `as Map<...>` cast inside the hook implementations and is the
+ *     ONLY sanctioned channel for post-finalize binding fanout.
+ *
+ *     The dev-mode runtime validator
+ *     (`validateBindingsImmutability` in
+ *     `scope-resolution/validate-bindings-immutability.ts`) surfaces
+ *     any drift — i.e. a hook writing to `indexes.bindings` instead
+ *     of `bindingAugmentations`, or producing a non-frozen finalized
+ *     bucket — via `onWarn` when explicitly enabled by
+ *     `NODE_ENV === 'development' || VALIDATE_SEMANTIC_MODEL === '1'`
+ *     (`VALIDATE_SEMANTIC_MODEL=0` is an explicit off switch).
+ *
+ *   - **I9 — `SemanticModel` is the single authoritative symbol store.**
+ *     Every symbol-indexed lookup (key = `nodeId | simpleName |
+ *     qualifiedName | filePath`) resolves through
+ *     `SemanticModel.{symbols,types,methods,fields}`. Scope-resolution
+ *     passes MUST NOT maintain parallel owner-keyed or name-keyed
+ *     symbol indexes — `WorkspaceResolutionIndex` is reserved for
+ *     `Scope`-valued lookups that `SemanticModel` structurally cannot
+ *     carry.
+ *
+ *     The `runScopeResolution` orchestrator guarantees this invariant
+ *     in two steps:
+ *       1. The legacy `parse` phase populates `SemanticModel` via
+ *          `symbolTable.add(...)`. For languages whose extractor
+ *          resolves `enclosingClassId` at parse time, class-body defs
+ *          are correctly owner-keyed there.
+ *       2. The `reconcileOwnership` pass runs after
+ *          `provider.populateOwners(parsed)` and registers any def in
+ *          `parsed.localDefs[i]` with a corrected `ownerId` that the
+ *          legacy pass missed (primarily Python class-body methods).
+ *          Idempotent — duplicates are skipped by `nodeId`.
+ *
+ *     Contract for consumers: `model` is `MutableSemanticModel` only
+ *     during those two write phases. Downstream passes receive a
+ *     narrowed `SemanticModel` (read-only) handle. This is enforced by
+ *     `runScopeResolution`'s type-level narrowing at the phase
+ *     boundary.
+ *
+ *     The dev-mode runtime validator (`validateOwnershipParity`)
+ *     surfaces any drift between `parsed.localDefs` ownership and the
+ *     registries via `onWarn` when
+ *     `NODE_ENV !== 'production' && VALIDATE_SEMANTIC_MODEL !== '0'`.
+ *
+ *     This invariant is a **transitional shim**: the architectural
+ *     end state is for every language's parse-time extractor to emit
+ *     the correct `ownerId` directly, removing the need for
+ *     reconciliation. Tracked as a follow-up; see ARCHITECTURE.md §
+ *     "Semantic-model source of truth".
+ *
+ * ## Semantic-model source of truth
+ *
+ * `ParsedFile` (from `cgraph-shared/src/scope-resolution/parsed-file.ts`)
+ * is the single semantic model consumed by both the legacy DAG and the
+ * scope-resolution pipeline. Scope-resolution passes MUST NOT build a
+ * parallel parse representation; if a pass needs AST-level facts that
+ * `ParsedFile` doesn't expose, it should reuse the orchestrator's
+ * `treeCache` (see `RunScopeResolutionInput.treeCache`) rather than
+ * re-invoke `parser.parse(...)` on its own.
+ *
+ * ## Same-graph guarantee
+ *
+ * Edges emitted by `runScopeResolution` and edges emitted by the legacy
+ * DAG are indistinguishable to downstream consumers:
+ *   - Node identity: same `generateId(...)` helper, same qualified-name
+ *     keyspace, same File/Folder/Method/Class node labels.
+ *   - Edge vocabulary: `'import-resolved' | 'global' | 'local-call' |
+ *     'same-file' | 'interface-dispatch' | 'read' | 'write'` — both
+ *     paths emit the same reasons (see
+ *     `cgraph/src/core/ingestion/call-processor.ts` for the legacy
+ *     emitter and `passes/receiver-bound-calls.ts` /
+ *     `passes/free-call-fallback.ts` for the scope-resolution emitters).
+ *   - Overload disambiguation: both paths use
+ *     `generateId('Method', ...)` suffixed with `parameterTypes` when a
+ *     method has overloads — see `graph-bridge/ids.ts`.
+ *
+ * The CI parity workflow (`.github/workflows/ci-scope-parity.yml`)
+ * runs both paths on every migrated language's fixture corpus and
+ * fails if the graph outputs diverge.
+ *
+ * Plan that introduced most of these invariants:
+ * `docs/plans/2026-04-20-001-refactor-emit-pipeline-generalization-plan.md`.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/core/code/engine/core/ingestion/scope-resolution/graph-bridge/callee-id-sink.js

@@ -0,0 +1,72 @@
+"use strict";
+/**
+ * Resolved-callee-id capture sink (#2227 follow-up plan U2).
+ *
+ * During Phase-4 scope-resolution CALLS-edge emission, each resolved call
+ * site's `(callSiteLine, callSiteCol) → resolvedCalleeId` mapping is
+ * accumulated here — across ALL THREE CALLS emit paths
+ * (`emitReceiverBoundCalls` via `tryEmitEdge`/`tryEmitEdgeWithExplicitTargetId`,
+ * and the inline `graph.addRelationship` in `emitFreeCallFallback` and
+ * `emitReferencesViaLookup`), each BEFORE its dedup (KTD6/R8). A later unit
+ * (U3) joins this map to CFG `BasicBlock`s by exact call-site position and
+ * emits a `BasicBlock.calleeIds` set.
+ *
+ * KEY ALIGNMENT (plan KTD7 — load-bearing): the key is the call/new
+ * expression node's start position — `line` 1-based (`startPosition.row + 1`),
+ * `col` 0-based (`startPosition.column`). This MUST equal the U1
+ * `SiteRecord.at` so the U3 position join lands. The CALLS resolution exposes
+ * the same node's range via `site.atRange` (`atRange: anchor.range`,
+ * scope-extractor.ts:1030), whose `startLine`/`startCol` are built by
+ * `nodeToCapture` as `row + 1` / `column` (1-based line, 0-based col — see the
+ * `Range` doc in cgraph-shared). So a capture keyed on
+ * `(atRange.startLine, atRange.startCol)` is byte-equal to U1's `at` — no
+ * normalization needed.
+ *
+ * Gating (R4): the concrete sink is created in `run.ts` when PDG is enabled OR
+ * always-on callable-flow facts need direct call targets for actual→formal
+ * propagation. The read-side CFG join remains strictly PDG-gated.
+ *
+ * Multi-target dispatch (R2/KTD8): one site → multiple emit calls → the `Set`
+ * accumulates every resolved target. Capture is per-emit-call, so the
+ * candidate set is complete and a real target is never dropped.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.calleeIdPosKey = calleeIdPosKey;
+exports.createCalleeIdAccumulator = createCalleeIdAccumulator;
+/** Build the position key from a call-site anchor. Single source of truth so
+ *  producer (this sink) and consumer (U3's CFG join) encode positions
+ *  identically. */
+function calleeIdPosKey(line, col) {
+    return `${line}:${col}`;
+}
+/**
+ * Create the concrete nested-`Map` accumulator for PDG callee capture or
+ * callable-value-flow's direct-target index.
+ */
+function createCalleeIdAccumulator(shouldCapture) {
+    const byFile = new Map();
+    return {
+        add(filePath, line, col, calleeId) {
+            if (shouldCapture?.(filePath, line, col) === false)
+                return;
+            let byPos = byFile.get(filePath);
+            if (byPos === undefined) {
+                byPos = new Map();
+                byFile.set(filePath, byPos);
+            }
+            const key = calleeIdPosKey(line, col);
+            let ids = byPos.get(key);
+            if (ids === undefined) {
+                ids = new Set();
+                byPos.set(key, ids);
+            }
+            ids.add(calleeId);
+        },
+        get(filePath) {
+            return byFile.get(filePath);
+        },
+        delete(filePath) {
+            byFile.delete(filePath);
+        },
+    };
+}

package/dist/core/code/engine/core/ingestion/scope-resolution/graph-bridge/edges.js

@@ -0,0 +1,194 @@
+"use strict";
+/**
+ * Graph edge emission primitives.
+ *
+ * Two functions:
+ *   - `mapReferenceKindToEdgeType` — translate a scope-resolution
+ *     `Reference.kind` into the corresponding graph edge type.
+ *   - `tryEmitEdge` — given a reference site + target def, resolve
+ *     caller + target to graph ids and emit the edge with
+ *     language-provided reason text, dedup-keyed by
+ *     `(edgeType, callerId, targetId, line, col)`.
+ *
+ * Next-consumer contract: any language provider can call `tryEmitEdge`
+ * from its own post-pass to emit edges it resolves Python-specific
+ * (or TypeScript-specific, etc.) logic. The dedup key is
+ * language-agnostic — no language needs to change it.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.mapReferenceKindToEdgeType = mapReferenceKindToEdgeType;
+exports.tryEmitEdge = tryEmitEdge;
+exports.tryEmitEdgeWithExplicitTargetId = tryEmitEdgeWithExplicitTargetId;
+const symbol_table_js_1 = require("../../model/symbol-table.js");
+const ids_js_1 = require("../graph-bridge/ids.js");
+/**
+ * Map a `Reference.kind` to a graph edge type. `import-use` is dropped
+ * (no edge type today — provenance lives on the IMPORTS edge emitted
+ * by `emitImportEdges`).
+ */
+function mapReferenceKindToEdgeType(kind) {
+    switch (kind) {
+        case 'call':
+            return 'CALLS';
+        case 'read':
+        case 'write':
+            return 'ACCESSES';
+        case 'inherits':
+            return 'EXTENDS';
+        case 'type-reference':
+            return 'USES';
+        // A function registered as an object-literal property value emits a
+        // reference-class USES edge, NOT CALLS — a registration is not an
+        // invocation (Kythe `ref` vs `ref/call`; Joern `METHOD_REF`). The
+        // invocation side is synthesized by the property-dispatch pass (#2437).
+        case 'value-ref':
+            return 'USES';
+        // Macro invocations resolve to a `Macro` node (never a function), so
+        // they emit `USES` — kept out of the `CALLS` keyspace which denotes
+        // function/method dispatch (#1934 review).
+        case 'macro':
+            return 'USES';
+        case 'import-use':
+            return undefined;
+        default:
+            return undefined;
+    }
+}
+/**
+ * Is this read site a PHANTOM — a duplicate of the call happening beside it?
+ *
+ * Some languages' member-read capture also matches the callee of a member call,
+ * so `obj.f()` produces a `call` site on `f` AND a `read` site on `obj.f` at the
+ * same position (Go's `@reference.read` matches every `selector_expression`).
+ * The capture layer marks that second site `inCalleePosition` rather than
+ * dropping it, because the two cases it covers are indistinguishable there:
+ *
+ *   - tail resolves to a METHOD → phantom. The ACCESSES edge duplicates the
+ *     CALLS edge emitted for the same source position; suppress it.
+ *   - tail resolves to a FIELD  → genuine. `h.dep.Work()` where
+ *     `Work func() error` reads a func-typed struct field and calls the value
+ *     it holds. That read is the field's only ACCESSES evidence — keep it.
+ *
+ * Only the resolved target's kind separates them, which is why this decision
+ * lives at emission and not in any language's capture code. Sites without the
+ * marker are untouched, so a genuine method VALUE (`f := obj.method`) — never in
+ * callee position — keeps its read.
+ *
+ * "Invoked rather than read" is `CALL_TARGET_TYPES` — the canonical callable
+ * target set (`FREE_CALLABLE_TYPES` ∪ Method/Constructor), not a local copy. A
+ * hand-rolled `{Function, Method, Constructor}` silently omits `Macro` (C/C++)
+ * and `Delegate` (C#), the two labels that set exists to add, and drops the
+ * `satisfies` guard in `symbol-table.ts` that compile-enforces every free
+ * callable label against `LABEL_BEHAVIOR`.
+ */
+function isPhantomCalleeRead(site, targetDef) {
+    if (site.kind !== 'read' || site.inCalleePosition !== true)
+        return false;
+    return symbol_table_js_1.CALL_TARGET_TYPES.has(targetDef.type);
+}
+/**
+ * Resolve caller + target to graph ids and emit the edge. Returns true
+ * if the edge was emitted (not deduped, not skipped).
+ *
+ * `seen` is a language-shared dedup set keyed by
+ * `${edgeType}:${callerGraphId}->${targetGraphId}:${line}:${col}` so
+ * multiple language-specific post-passes can share it and never
+ * double-emit a resolution one of them already produced.
+ */
+function tryEmitEdge(graph, scopes, nodeLookup, site, targetDef, reason, seen, confidence = 0.85, collapseByCallerTarget = false, calleeCapture) {
+    // A read that only exists because it is the callee of the call beside it, and
+    // whose tail resolved to a callable, is that call restated as an access —
+    // checked first because it needs no id resolution.
+    if (isPhantomCalleeRead(site, targetDef))
+        return false;
+    // Inheritance edges are emitted directly by `preEmitInheritanceEdges` (which
+    // owns the enclosing-class caller and the EXTENDS-vs-IMPLEMENTS type), so this
+    // generic bridge derives caller + edge type purely from the site.
+    const callerGraphId = (0, ids_js_1.resolveCallerGraphId)(site.inScope, scopes, nodeLookup, site.atRange);
+    const targetGraphId = (0, ids_js_1.resolveDefGraphId)(targetDef.filePath, targetDef, nodeLookup);
+    const edgeType = mapReferenceKindToEdgeType(site.kind);
+    if (callerGraphId === undefined)
+        return false;
+    if (targetGraphId === undefined)
+        return false;
+    if (edgeType === undefined)
+        return false;
+    // Resolved-callee-id capture (#2227 U2/KTD6/R8): record this CALLS site's
+    // resolved target BEFORE the dedup `seen` check, so collapsed same-target
+    // multi-line calls are still captured per site. Keyed on `site.atRange`
+    // (1-based line / 0-based col — byte-equal to U1's SiteRecord.at).
+    if (calleeCapture !== undefined && edgeType === 'CALLS') {
+        calleeCapture.sink.add(calleeCapture.filePath, site.atRange.startLine, site.atRange.startCol, targetGraphId);
+    }
+    // CALLS edges may collapse to `(caller, target)` granularity when
+    // the provider opts in (C# matches legacy DAG behavior this way).
+    // Write/read ACCESSES keep per-site dedup so multiple writes to the
+    // same field on different lines produce distinct edges.
+    const useCollapsed = collapseByCallerTarget && edgeType === 'CALLS';
+    const dedupKey = useCollapsed
+        ? `${edgeType}:${callerGraphId}->${targetGraphId}`
+        : `${edgeType}:${callerGraphId}->${targetGraphId}:${site.atRange.startLine}:${site.atRange.startCol}`;
+    if (seen.has(dedupKey))
+        return false;
+    seen.add(dedupKey);
+    graph.addRelationship({
+        id: `rel:${dedupKey}`,
+        sourceId: callerGraphId,
+        targetId: targetGraphId,
+        type: edgeType,
+        confidence,
+        reason,
+    });
+    return true;
+}
+/**
+ * Variant of `tryEmitEdge` that takes a pre-resolved target graph id
+ * instead of resolving it from a `SymbolDefinition`. Used by the
+ * value-receiver-owner bridge (`receiver-bound-calls.ts` Case 5) where
+ * the picked owner-indexed method def carries no `qualifiedName` (object
+ * literals have no class owner to seed it) and therefore cannot
+ * round-trip through `resolveDefGraphId`. The def's `nodeId` IS the
+ * canonical graph node id (written by the parse phase), so the caller
+ * passes it directly.
+ *
+ * All other invariants of `tryEmitEdge` apply: dedup key shape, collapse
+ * flag honoring, edge-type mapping, caller-id resolution.
+ *
+ * ONE deliberate exception: the {@link isPhantomCalleeRead} suppression is not
+ * applied here, because it keys on the target's node label and this entry point
+ * is handed an id rather than a def. Reachable only for a `read` site marked
+ * `inCalleePosition` whose receiver typed as an object-literal VALUE — a
+ * JS/TS-shaped registration. No language that sets the marker resolves through
+ * this bridge today (verified for Go, whose func-valued struct-literal fields
+ * resolve through the owned-member path instead). A language adding the marker
+ * must re-check this path.
+ */
+function tryEmitEdgeWithExplicitTargetId(graph, scopes, nodeLookup, site, targetGraphId, reason, seen, confidence = 0.85, collapseByCallerTarget = false, calleeCapture) {
+    const callerGraphId = (0, ids_js_1.resolveCallerGraphId)(site.inScope, scopes, nodeLookup, site.atRange);
+    const edgeType = mapReferenceKindToEdgeType(site.kind);
+    if (callerGraphId === undefined)
+        return false;
+    if (edgeType === undefined)
+        return false;
+    // Resolved-callee-id capture (#2227 U2/KTD6/R8) — before dedup, see
+    // `tryEmitEdge`. The explicit target id IS the resolved callee id.
+    if (calleeCapture !== undefined && edgeType === 'CALLS') {
+        calleeCapture.sink.add(calleeCapture.filePath, site.atRange.startLine, site.atRange.startCol, targetGraphId);
+    }
+    const useCollapsed = collapseByCallerTarget && edgeType === 'CALLS';
+    const dedupKey = useCollapsed
+        ? `${edgeType}:${callerGraphId}->${targetGraphId}`
+        : `${edgeType}:${callerGraphId}->${targetGraphId}:${site.atRange.startLine}:${site.atRange.startCol}`;
+    if (seen.has(dedupKey))
+        return false;
+    seen.add(dedupKey);
+    graph.addRelationship({
+        id: `rel:${dedupKey}`,
+        sourceId: callerGraphId,
+        targetId: targetGraphId,
+        type: edgeType,
+        confidence,
+        reason,
+    });
+    return true;
+}