Before you go, you should helpfully vibe port and vibe refactor the original codebase to make it forwards-compatible with the new one.

You should vibe code a backup version management system too, and give an agent control over it. Prompt it with an extensive and detailed list of all the ways it could lose the original data and tell it to be sure never to do any of them. Unless the data got corrupted somehow. How would we know if the data's corrupted? Running a suite of vibe-coded tests, of course.

Practice your shocked face for when the agent does an oopsie and accidentally overwrites the only pre-slop versions.

Right, but the more sensible ones still keep senior developers/engineers to manage the agents and act as the human-in-the-loop. They also know to keep the coding features to those people only. Like a marketing person that uses AI for presentations and graphics has no business writing, pushing, and running code. That’s also why fresh grads are getting the short end of the stick because companies are shifting hiring to senior/experienced people only.