codemod-rust-workspace

To enforce crate governance in a Rust workspace, you coordinate crate responsibilities and validate workspace dependencies to ensure consistent interfaces, schema generation, and unified validation across all components.

Maintaining CI parity across Rust crates requires coordinating workspace validation to enforce code quality standards, including async cancellation, error propagation, and consistent cargo tasks across the monorepo.

Managing schema generation and cargo tasks involves enforcing unified workspace validation rules that span state adapters, runners, and models, ensuring consistent interfaces and dependency propagation throughout the workspace.

Yes, workspace governance rules clarify distinct crate responsibilities for components like the scheduler and CLI surfaces, ensuring they maintain consistent interfaces and appropriate dependency boundaries within the monorepo.

Validating async cancellation and error propagation is necessary to ensure code quality and runtime stability across independent crates, preventing silent failures and maintaining CI parity throughout the Rust workspace.