GeezerVison

…r does

A prod node whose scope dependencyManagement sets sits in Maven's compile
root without a parent there; its edge lives in the test root. The
assembler merges a project's roots, so the facts are fine, but the
shared reachability assertion rejected the Maven records. Maven's smoke
test now checks each project with --per-project, which merges a
project's roots the way the assembler does. Gradle and sbt keep the
stricter per-root check, as their roots are independent resolutions.

Both modes now drop an edge whose ends are not both nodes of its root,
as the assembler does, so a dangling edge no longer makes a node look
reachable. The Maven fixture covers the managed-scope case.

Oskar Haarklou Veileborg (BarrensZeppelin) left a comment

assert-reachability.py was a hand-ported copy of the assembler's own
reachability check, and the per-project mode ported more of it. The
smoke tests now assemble the records with the real parseRecords and
assembleFacts, which throw on a resolved dependency no direct dependency
of its project reaches, so the check cannot drift from the assembler.
The assembler checks only the roots of known projects, so the runner
also rejects a root of any other project. The script, its unit tests
and the --per-project flag are gone; their shapes are now assembler
tests.