Module policy_dependent_version 

The mono/dependent-version-bump check over a lifecycle’s candidate state. What: The mono/dependent-version-bump check: the native planner over the lifecycle’s prepared candidate state, its findings, and the corrections a direct fix applies. Why: The installed wrapper’s policy (dependent-version-bump-policy.ts) reports one finding per publishable dependent of a raised manifest, each with a full-content patch, on direct-check and direct-fix; on pre-forward it plans only for a forwarded commit. A real git commit runs through the commit transaction instead of being forwarded, so pre-forward reaches this check only for git add, where the policy finds nothing.

In TS you’d write (pseudocode):

// const findings = await findDependentBumps(context); // patches applied by a direct fix

Functions

check_dependent_version

What: Check the lifecycle’s candidate state. <F: RepositoryFacts> accepts any facts provider; &mut ContentState lends the shared candidates and takes corrections. Why: See the module comment. Corrections are proposed only on direct-fix, the one lifecycle that applies them; every proposal of the pass is checked before any is recorded, so a refused one leaves the pass without partial corrections.