A handover is not an email with a zip file attached. It is the moment a client stops depending on us, and it should be designed with that in mind.
Three things, always
The repository, with its history. The documentation, written for somebody who was not in the room. And a runbook — how to deploy it, how to watch it, what to do at three in the morning.
What does not ship
Our own scaffolding. The build's task notes, its manifest, the agent's working context: those are ours and they stay with us. What you receive is your application, and nothing else.
The test of a good handover
Your own engineers should be productive on day one without asking us a single question. Anything short of that is a handover that has not finished.