rust-fix-discipline

Disciplined Rust fixes require targeting root causes reported in audits or code reviews rather than cosmetic changes. You must enforce a three-way decision between root-cause fixes, local correctness fixes, and narrow annotations, followed by explicit verification steps like cargo build and clippy.

The best way to triage failing Rust tests and lint sweep results is to apply a three-category model to every finding. This approach forces an explicit category decision and non-deferral, cross-checking each fix against context, tests, and workspace policy before implementation.

Managing cross-crate API changes during Rust code review fixes requires workspace-level coordination and mandatory checks. You must run cargo build, cargo clippy, tests, and workspace checks to ensure API changes do not break dependencies across the workspace.

Narrow annotations in Rust should be used when a finding does not warrant a root-cause or local correctness fix. The discipline enforces an explicit three-way decision between root-cause fixes, local correctness fixes, and narrow annotations to ensure honest reporting and prevent unnecessary architectural changes.

Yes, fixing Rust clippy errors mandates running workspace checks if the fixes involve API changes. The discipline requires explicit verification steps including cargo build, cargo clippy, tests, and workspace checks to ensure cross-crate coordination and maintain correctness.