Rust Code Review

Use this for Rust review work where consistency, safety, and maintainability matter.

Follow ths standards in https://github.com/apollographql/rust-best-practices

Mandatory pre-merge checks

• Ownership and data flow are intentional.
• Error handling is explicit and aligns with crate/binary boundaries.
• Clippy and format quality are clean in touched files.
• Performance changes are measured before acceptance.
• Public APIs are documented; docs match runtime behavior.
• Tests cover intended behavior and error paths.
• Unsafe or raw-pointer usage is justified and constrained.

Severity matrix