dotagent:validate

Rust validation is executed by running cargo fmt, cargo clippy, cargo test, and a smoke test sequentially. This pipeline ensures code changes are green and ready for review, mirroring CI checks locally to prevent build failures before merging.

Reproducing a failing Rust CI pipeline locally requires running the full validation pipeline from the repository root. It executes formatter, lints, tests, and a smoke test to identify the exact failure point and verify runtime integrity before attempting fixes.

A Rust workspace validation pipeline enforces code quality by executing cargo clippy with denied warnings across all targets, checking formatting, and running tests. Catching issues early in the development cycle ensures reliability and maintains consistent standards before merge.

Yes, cargo clippy and cargo fmt checks can be applied to an entire Rust workspace. The validation process runs clippy on all targets with warnings denied and checks formatting across all files to ensure strict code quality and stylistic consistency.

A Rust smoke test fails during end-to-end validation when the minimal runtime integrity check encounters build or execution errors. This indicates issues not caught by standard tests, requiring local reproduction of the validation pipeline to diagnose and fix the runtime defect.

Yes, cargo is required to run Rust project validation checks. The end-to-end validation pipeline depends on cargo to execute formatting checks, clippy lints, workspace tests, and the final smoke test to verify build and runtime integrity.