Summary

• class D extends A { constructor(y) { super(y); } } where A is an ES5-style function-based pseudo-class (not an ES6 class) caused resolveCallTargets (call-resolver.ts, mirrored by resolve_call_targets_core in build_edges.rs) to fabricate a calls edge from D.constructor to any unrelated same-named constructor reachable via the bare same-file lookup or the project-wide "exact global match" fallback tier — because A has no qualified A.constructor node for resolveThisDispatch's CHA ancestor walk to find, and neither engine's super resolution excluded coincidental same-name matches the way this/self dispatch legitimately can.
• Excludes super from those non-CHA-aware fallback tiers, but only when the caller is inside a real class (RECEIVER_KINDS-kind declaration), where super is syntactically guaranteed to have a real extends target CHA can verify.
• An object-literal method using dynamic prototype linkage (Object.setPrototypeOf, obj.__proto__ = ...) has no static extends clause for CHA to check at all, so the bare/global fallback still applies there — confirmed by the jelly-micro super/super3 fixtures' own recall floors, which caught an initial overly-broad version of this fix during development.

Test plan

• New dual-engine regression test — fails without the fix (both engines), passes with it
• jelly-micro super/super3 recall floors hold (dynamic-prototype fallback preserved)
• Full test suite passes (4809 tests)
• node scripts/parity-compare.mjs — 42/42 fixtures identical
• codegraph diff-impact origin/main -T — blast radius limited to the 3 touched TS functions (+ Rust mirror)

Closes #2244