refactor

Behavior-preserving refactoring breaks large functions into smaller, testable units by orchestrating a multi-agent pipeline that validates test equivalence throughout the structural changes. This prevents accidental regressions while improving internal code quality.

Migrating legacy code to new design patterns requires characterization testing and Fowler-style refactoring mechanics to ensure external behavior remains identical. Automated test validation loops verify that the system's functionality is preserved during the structural migration.

Automated test validation uses a robust loop framework to continuously run tests during refactoring, creating a test-equivalence gate that blocks structural changes from merging if any test fails. This ensures the external behavior stays identical throughout the process.

Library extraction is supported as a large-scale structural change through a multi-agent pipeline that plans, executes, and verifies each step. Test-equivalence gates ensure the extracted library maintains the original system's behavior without regressions.

For legacy code without tests, the process supports characterization testing to capture existing behavior before refactoring. This establishes a baseline test-equivalence gate so subsequent structural changes can be validated against the original output.

Automated refactoring targets large-scale structural changes like function decomposition and pattern migration. If your goal involves changing external behavior, adding new features, or lacks a testable baseline, this behavior-preserving approach is not the right fit.