rust-review

To audit a Rust port without manual code reading, execute an audit pipeline that generates structured behavioral traces and audit findings. This validates module slices by capturing rule-cited traces and simplification deltas, appending the results to JSONL files for dashboard rendering.

A behavioral trace in Rust port verification is a structured record capturing spec-to-implementation rule citations and simplification deltas. It traces decisions and flowchart updates for a targeted module slice, replacing prose reports with append-only JSONL evidence.

Track deferred, ignored, and test gaps in a Rust module slice by running an audit pipeline that refreshes derived JSONL context. It detects existing gaps and appends review-specific findings rows to your audit-data JSONL files.

Yes, rust-review works with mermaid flowcharts and JSONL data by validating Rust ports through spec fidelity checks. It generates audit findings tied to extracted spec rules and diagrams, appending structured data to reviews and findings JSONL files.

Yes, you can verify a standalone Rust module without the porting-to-rs workflow. The audit pipeline executes standalone verification by generating behavioral traces and detecting deferred or test gaps, requiring only the module or slice name as input.

The best way to manage Rust port audit findings is using an append-only workflow that writes to findings.jsonl and reviews.jsonl. This method preserves historical audit data while appending new review rows and dashboard-ready evidence artifacts.