rmc-reexport-chain

Tracing Rust re-export chains requires walking pub use re-export edges breadth-first up to 8 hops with cycle detection. This reports hop-level visibility to show where an item is exposed from each facade depth.

You can detect pub type masquerading by flagging cases where a module declares a pub type alias whose name overlaps with a pub use binding in the same module, indicating an alias may be acting as a re-export disguised as a type.

You audit Rust public API hygiene by tracing re-export chains and correlating suspected re-export disguises with audit findings using directory-scoped parameters to decide whether to drop intermediate hops and flatten to the canonical target.

The best way to resolve ambiguity when a Rust item is exposed through multiple pub use facades is to trace the re-export chains to identify the canonical definition being re-exported and how far the public API is disguised behind intermediate hops.

Yes, tracing Rust re-exports requires calling build_hypergraph first to index your workspace, then running re_export_chain for the canonical target you want to trace and reviewing the hop-by-hop visibility links.

You should flatten long facade chains in a Rust codebase when auditing reveals that intermediate hops are potentially misleading, and simplifying by dropping them to expose the canonical target improves public API hygiene.