From 00d4cc08cea0dbffcdd56ec6cc602f6758460a8c Mon Sep 17 00:00:00 2001
From: Gergo Magyar <gergomagyar@icloud.com>
Date: Tue, 12 May 2026 12:53:01 +0100
Subject: [PATCH] test(php): skip U1/U4 scope-resolver-only assertions in
 legacy DAG mode
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Four tests added by U1 and U4 assert correctness wins that only the
scope-resolution pipeline delivers. The legacy DAG path has no
equivalent narrowing, so it emits the over-broad edges these tests
forbid:

- U1: MRO arity narrowing on class-name receivers (Case 2 in
  receiver-bound-calls.ts) — legacy has no arity check between MRO
  iterations, so 'Child::method(1)' falls through to Parent::method.
- U1: single-class arity gating — legacy resolves by name without
  arity, so an arity-incompatible call on a class with no parent
  still emits an edge.
- U4: 'phpEmitUnresolvedReceiverEdges' exact-required-arity gate —
  the legacy DAG has no equivalent unresolved-receiver fallback hook,
  so default-param over-arity and variadic-below-required shapes
  resolve via a different code path that over-emits.

Backporting these narrowing checks to the legacy DAG is out of scope,
matching the existing pattern in LEGACY_RESOLVER_PARITY_EXPECTED_FAILURES
for record/pad zero-args (commit af9af4a9 U1) and the FQN cross-
namespace test (Codex PR #1497 finding 1).
---
 .../test/integration/resolvers/helpers.ts     | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/gitnexus/test/integration/resolvers/helpers.ts b/gitnexus/test/integration/resolvers/helpers.ts
index f005fbf91..571f2121f 100644
--- a/gitnexus/test/integration/resolvers/helpers.ts
+++ b/gitnexus/test/integration/resolvers/helpers.ts
@@ -58,6 +58,27 @@ const LEGACY_RESOLVER_PARITY_EXPECTED_FAILURES: Readonly<Record<string, Readonly
     // target from a same-simple-name class reachable via `use`. Scope-
     // resolver-only correctness win (Codex PR #1497 review, finding 1).
     '\\App\\Other\\User parameter resolves $u->record() to app/Other/User.php (NOT app/Models/User.php)',
+    // MRO arity-mismatch on class-name receivers (`Child::method(1)` where
+    // Child::method takes 2 args and Parent::method takes 1): the legacy
+    // DAG has no arity narrowing on Case 2 (class-name) MRO walk, so it
+    // emits a false CALLS edge to Parent::method on fallthrough. Scope-
+    // resolver-only correctness win (PR #1497 review Image 1 / U1).
+    'arity-incompatible most-derived override does NOT fall through to ParentModel::method',
+    // Class-name receiver with single-class arity mismatch (no parent in
+    // the MRO chain): legacy resolves the method by name without arity
+    // gating, so it emits a CALLS edge even when arity is definitively
+    // incompatible. The scope-resolver's `narrowOverloadCandidates` check
+    // in `receiver-bound-calls.ts` Case 2 rejects this post-fix. Scope-
+    // resolver-only correctness win (PR #1497 / U1).
+    'arity-incompatible class with no parent emits zero CALLS edges (regression check)',
+    // `phpEmitUnresolvedReceiverEdges` exact-required-arity gate (PR
+    // #1497 / U4): the legacy DAG has no equivalent unresolved-receiver
+    // fallback hook, so it resolves these untyped-receiver sites via a
+    // different code path that over-emits for default-parameter and
+    // variadic-required-mismatch shapes. Scope-resolver-only correctness
+    // wins; backporting to legacy is out of scope.
+    'argCount > required (2>1) on candidate with default param emits NO edge post-fix',
+    'variadic candidate, argCount < required (1<2) emits NO edge',
   ]),
   python: new Set([
     // Suffix-fallback lex tiebreak depends on the registry-primary