Prove the rewrite is correct: keep golden tests, validate integration behavior, and measure risk.
After migrating code, your job is to prove you didn’t change behavior accidentally. “It compiles” is not validation.
This section focuses on practical validation layers: unit tests for the pure core, integration tests for boundaries, and production-like checks (fixtures, golden tests, load tests) when correctness or performance risk is high.