rmc-snapshot-diff

To detect Rust API surface and dependency coupling drift, compare two workspace snapshots from different branches to quantify deltas in item counts, visibility distribution, and crate edge weights, providing evidence that structural invariants stayed intact during the refactor.

Checking for dead public items and complexity regressions involves diffing dead-public reports and analyze_complexity output between two builds, verifying that a Rust refactor didn't accidentally change public API exposure or introduce potential complexity spikes.

Compare two Rust workspace snapshots by running matching workspace_stats, dead_pub_report, crate_edges, and get_declared_reexports on each directory, then manually diffing the resulting JSON metrics to audit refactor impact and produce a structured delta summary.

No, comparing workspace snapshots does not require a dedicated hypergraph diff tool because none exists; you must build hypergraph snapshots for each directory, run the analysis commands, and manually diff the resulting JSON metrics to evaluate refactor drift.

Yes, you can validate complexity changes by running analyze_complexity on the same files from two prepared snapshot directories corresponding to different timestamps, comparing this output to flag potential complexity regressions caused by refactoring.