Problem

tests/integration/build-parity.test.ts > Build parity: native vs WASM — sample-project (JS) > produces identical edges fails pre-existing on fix/issue-1656:

- Expected (WASM): no receiver edge main → Calculator
+ Received (native): extra receiver edge from main to Calculator

The native engine emits an extra receiver edge:

{ kind: 'receiver', source_name: 'main', target_name: 'Calculator' }

that the WASM engine does not emit. Both engines produce the correct calls edge from main to Calculator.

Steps to reproduce

npx vitest run tests/integration/build-parity.test.ts

Notes

• Confirmed pre-existing on fix/issue-1656 (before the roles fix for fix: build-parity roles diverge — native classifies main/square as dead-unresolved vs leaf in WASM #1659)
• Unrelated to issue fix: build-parity roles diverge — native classifies main/square as dead-unresolved vs leaf in WASM #1659 (roles divergence)
• Likely the native engine emits receiver edges for new Calculator() constructor calls while WASM does not