Gergo Magyar 3f17cb7fd5 test(cfg): isolate the non-terminating-loop hazard in worker CDG asserts (#2195 U3) ... The pipeline-pdg worker-mode blocks asserted a whole-fixture cdg>0 aggregate (satisfied by any branching fn) while the comment claimed it proved the non-terminating-loop EXIT-reachability end-to-end. Add a per- language `hazard` marker + isolate the assertion: locate the hazard function's BasicBlocks by its anchor and assert >=1 CDG edge is sourced within it (a marker mutation now fails the test — non-vacuous). C# keeps the aggregate (its fixture has no infinite loop). Comments corrected. Switch the 7 visitor unit tests (java/csharp/dart/kotlin/php/swift/c-cpp) from the local exitReachableFromAll CFG-shape helper to the production isExitReachableFromAllBlocks + computeControlDependence on the hazard function, matching go/python/ruby/rust/vue. 241 unit + 30 pipeline green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-14 16:16:12 +00:00
..
fixtures	fix(cpp): suppress deleted overload winners (#2094)	2026-06-10 18:41:30 +01:00
helpers	test(cfg): language-agnostic CFG unit-test harness (#2195 U1)	2026-06-14 10:43:00 +00:00
integration	test(cfg): isolate the non-terminating-loop hazard in worker CDG asserts (#2195 U3)	2026-06-14 16:16:12 +00:00
unit	test(cfg): isolate the non-terminating-loop hazard in worker CDG asserts (#2195 U3)	2026-06-14 16:16:12 +00:00
utils	perf(hooks): cmdline-first Linux db-lock scan, drop the lsof fallback (#2180) (#2183)	2026-06-13 11:52:14 +01:00