Strategy — No Untested Refactor

When to use

• The user asks for a behavior-preserving refactor and expects the tests to prove the behavior did not change.
• The user wants to restructure or clean up existing behavior and needs characterization tests to lock in current behavior first.
• The user asks to refactor a class, service, or function that currently has no automated tests covering its behavior.

When NOT to use