rmc-refactor-plan

To decide if a Rust pub item can be downgraded to pub(crate), you analyze cross-crate importer usage patterns to measure blast radius. This produces an evidence-backed verdict indicating whether the visibility downgrade is safe or blocked.

Assess blast radius before deleting dead Rust symbols by selecting an evidence-gathering recipe that orchestrates call graph and semantic similarity tool calls. This generates summarized tool evidence to prioritize deletions by complexity.

Plan a Rust crate move or facade re-export by comparing consumer and importer usage patterns across crates. This cross-crate impact analysis detects API hygiene issues and yields a go, block, or conditional verdict.

Yes, you can use static analysis to find duplicate Rust logic by applying semantic dedupe recipes. These recipes use semantic similarity and call-graph signals to target extraction opportunities and prioritize refactors.

Yes, a built and indexed hypergraph workspace is required. The refactoring plan orchestrates tool calls against this indexed environment to gather evidence for symbol-level and crate-level changes.