Module dependent_version_bundled 

Which development dependencies each dependent bundles. What: Decide which development dependencies each dependent bundles, reading source only where an edge could carry a raised version. Why: A development dependency ships inside a dependent only when its non-test source imports it. Scanning every package’s source on every commit would read the whole workspace, so, as in the incumbent (dependent-bump-workflow.ts:176-278), only dependents that could reach a raised package if every development dependency were bundled are scanned, and only for edges that lead toward a raised package.

In TS you’d write (pseudocode):

// await bundledDevelopmentEdges({ reader, states, bumpedNames });

Functions

bundled_development_edges

What: For each state, in order, the development dependencies its source imports among those that could carry a raised version. Vec<Vec<String>> is one list per state. Why: These become edges of the plan’s walk alongside the runtime edges.