Merge remote-tracking branch 'origin/main' into fix/native-this-dispatch-1413

Author: carlos-alm

src/domain/graph/builder/stages/build-edges.ts

@@ -852,6 +852,10 @@ function buildObjectRestParamPostPass(
               typeMap.set(orpb.restName, { type: pb.argName, confidence: 0.65 });
             }
           }
+          // restNames tracks every rest-parameter name found, regardless of whether the
+          // scoped key was already in typeMap.  This ensures the post-pass (below) processes
+          // all calls whose receiver matches a known rest binding — not just those whose
+          // typeMap entry was seeded in this iteration.
           restNames.add(orpb.restName);
         }
       }

tests/benchmarks/regression-guard.test.ts

@@ -82,11 +82,12 @@ const NOISY_METRICS = new Set<string>(['No-op rebuild', '1-file rebuild', 'fnDep
  * *real* algorithmic regression shows up on the native numbers too — and native
  * keeps the strict 25% / 50% thresholds. Native is the canary. WASM timing only
  * needs to catch gross WASM-specific catastrophes (the 100–220% blowups seen in
- * v3.0.1–3.4.0), which 70% still flags, while absorbing the ≤67% shared-runner
- * jitter. Size metrics (DB bytes/file) are engine-independent and excluded from
- * this widening via SIZE_METRICS below — they keep the strict threshold.
+ * v3.0.1–3.4.0), which 75% still flags, while absorbing observed shared-runner
+ * jitter (measured up to 72% on sub-30ms WASM metrics). Size metrics (DB
+ * bytes/file) are engine-independent and excluded from this widening via
+ * SIZE_METRICS below — they keep the strict threshold.
  */
-const WASM_TIMING_THRESHOLD = 0.7;
+const WASM_TIMING_THRESHOLD = 0.75;
 
 /**
  * Metric labels that measure size/count rather than wall-clock time. These are