preserving-original-during-refactor

To preserve original file behavior during refactoring, you need version tracking that saves original files as backups. This allows code reviewers to compare pre-refactor and post-refactor behavior to verify no unintended changes occurred.

The best way to track file versions for behavior comparison is creating `.original` backup files of the code being refactored. This ensures the pre-refactor state remains accessible for an old vs. new comparison during the review process.

You set up version tracking when modifying existing files by initiating the refactor task with a file versioning tool. The tool automatically creates backup copies of the original files, enabling behavior auditing and rollback if necessary.

Behavior preservation works with any refactoring task that modifies existing files. It requires careful version tracking to ensure the original behavior is saved and can be audited by reviewers or rolled back if issues arise.

You need to save original versions of files when refactoring code to enable a reliable behavior comparison during code review. Keeping an `.original` backup ensures reviewers can audit changes and safely initiate a rollback if necessary.