aibdd-refactor-execute

To refactor code safely without changing observable behavior, execute structure-only moves under a confirmed green acceptance test net. This approach enforces one-move-at-a-time discipline, immediately reverting any change that causes a test failure.

Behavior safety in refactoring ensures structural changes preserve original externally observable outputs. You need it when modifying product code under a green target feature set to prevent regressions and validate that runtime references remain stable.

Execute refactoring by validating an incoming green handoff, verifying runtime references match, and running acceptance tests before and after each candidate move. Apply structure-only changes according to a move policy and immediately revert on any red result.

You cannot apply multiple structural changes simultaneously. Refactoring requires a one-move-at-a-time discipline to preserve the scope of target feature files and versioned specs, ensuring that any failed move is isolated and immediately reverted.

If a refactor move fails during runtime refs validation or acceptance testing, the system immediately reverts the change. It then generates a structured refactor handoff reporting applied versus reverted moves, modified files, and stop reasons.

Yes, safe refactoring requires interaction gates for higher-risk actions to enforce acceptance safety. These gates prevent unsafe refactors by ensuring strict runtime drift verification and baseline acceptance runner execution before proceeding with structural changes.