refactor-guardian

Verify behavioral equivalence during refactoring by enforcing no-behavior-change contracts, collecting real build and test artifacts via terminal access, and comparing pre- and post-change states to detect any regressions.

Validate API stability during module extraction, renaming, or architectural restructuring to ensure public interfaces remain unchanged. Apply automated guardrails during these operations to detect interface changes and prevent unauthorized contract modifications.

Check that code movement preserves behavior by running automated guardrails that enforce hard constraints and collect artifacts from builds and tests. This generates a structured report with actionable remediation guidance for any detected changes.

Refactor verification works for large-scale architectural restructuring by acting as a last-line safety net before merges. It validates refactor intent and scope to prevent regressions across complex code movement and module extraction operations.

The best way to detect persistence and interface changes during refactoring is to apply hard constraints that validate refactor intent, collect real artifacts, and output a structured report detailing behavioral, interface, and persistence modifications.