Hi @millionmeme
As per Adobe, If the page was already activated, moving the page will automatically deactivate it. By default, it will be reactivated when the move is complete, but this can changed by unchecking the Republish field for the page in the Move window.
1. If a page is already activated, moving or renaming it will deactivate it anyhow which will remove the page reference from publish instance.
2. Now if the Republish checkbox is checked, then the updated (moved or renamed) page will be moved to publish.
3. If it's not checked, the new page will not be moved to publish but at this point #1 is already completed. So we will not be getting the previous page back here.
Please refer:
https://experienceleague.adobe.com/docs/experience-manager-64/classic-ui/authoring/classic-page-author-manage-pages.html?lang=en#authoring
It is not recommended to modify this feature as it's the OOTB functionality. But if still you want to try out something you can check for Pre-Processor. Pre-processors are invoked just before the activation/deactivation.
This will run for all type of activation and deactivation and is not limited to page move action.
Reference:
https://helpx.adobe.com/experience-manager/6-5/sites/developing/using/reference-materials/javadoc/co...
http://wemcode.wemblog.com/replication-preprocessor
https://labs.tadigital.com/index.php/2019/06/25/aem-preprocessor/
Thanks!
Thanks!