It sounds like you want those to be steps that come after each other, like some sort of waterfall.
If you want to get with the times, you, the developer, should write a unit test for each file you think shouldn't be deleted on running the application.
Another way of looking at it is there shouldn't be a product update/release getting pushed out to hundreds of thousands of users (a guess), without passing an extensive validation suite. Developer unit tests are for a different purpose.
Nowadays I work in medical devices. It's nice because you're actually legally required to spend 5 minutes making sure your product does what you say it will before you're allowed to sell it, in contrast with what's happened to the rest of the industry.
People make mistakes during development... but there's no way this should have gotten past even basic QA testing. :(