fix(parity): native engine reports 1 fewer edge than WASM (30,609 vs 30,610)

[carlos-alm]

Summary

The v3.9.0 benchmark run (PR #853) shows a 1-edge divergence between engines on the same 567-file codebase:

• Native: 15,483 nodes, 30,609 edges
• WASM: 15,483 nodes, 30,610 edges

Node counts are identical, so the extraction layer agrees on symbols. The difference is in edge building or import resolution.

Context

Per project policy, both engines must produce identical results. Any divergence means the less-accurate engine has a bug that must be fixed.

Previous edge parity fixes in #810 resolved larger divergences; this 1-edge gap is a residual.

Next Steps

1. Identify which edge differs (run both engines with --json and diff the edge sets)
2. Determine which engine is correct
3. Fix the extraction/resolution bug in the incorrect engine

[carlos-alm]

Root Cause

The 1-edge divergence is a known bug already fixed in source — the prebuilt native binary (v3.8.1) predates the fix.

The missing edge

WASM has a dynamic-imports barrel edge (confidence 0.9) from tests/builder/pipeline.test.ts → src/domain/graph/builder/pipeline.ts that native is missing.

Why

tests/builder/pipeline.test.ts line 77:

const { buildGraph: fromBarrel } = await import('../../src/domain/graph/builder.js');

The old native collect_object_pattern_names extracted fromBarrel (the local alias) instead of buildGraph (the export name) from the pair_pattern destructuring. When barrel resolution searched for fromBarrel in builder.ts, it found nothing — so no barrel-through edge was created.

Fix

Already merged:

• 34a3d47 — fix: use child_by_field_name("key") instead of child_by_field_name("value")
• cd7dea3 — fix(native): extract export name for destructured dynamic imports (fix(native): extract export name for destructured dynamic imports #813)

Both are included in the v3.9.0 tag but not in the published native binary (@optave/codegraph-win32-x64-msvc is still v3.8.1). Rebuilding and publishing the native binary for v3.9.0 will resolve this.

Verification

Confirmed by building the graph with both engines and diffing edge sets — the single missing edge is exactly the barrel-through edge for this renamed dynamic import destructuring pattern.

[carlos-alm]

Closing — the source fix is already merged (cd7dea3). The edge parity gap will disappear once the native binary is rebuilt for v3.9.0.