rmc-trait-audit

To audit Rust trait usage for dead code, analyze trait definitions, method inventory, and workspace-wide dispatch call sites. This produces verdicts like delete, seal, inline, or keep based on observed importer and call traffic patterns.

Determining if a Rust trait is a real abstraction boundary involves measuring usage imports, implementer patterns, and workspace-wide dispatch call sites. The audit generates structured verdicts indicating whether to keep, seal, or delete the trait.

Tracing dynamic dispatch and generic bound calls requires computing who uses the trait and who calls specific methods across the workspace. The audit identifies dispatch through `dyn T` receivers and generic bounds to map call traffic.

Yes, you can get a per-method usage and dispatch verdict by running a trait audit on the qualified name. It enumerates methods, associated items, and fan-in to produce structured refactoring decisions for each method.

Yes, you need to run build_hypergraph before auditing a Rust trait. After that, use find_definition and module_tree to enumerate methods, then who_uses_summary, who_imports, and who_calls to generate the verdict report.