You are leaving a project and another developer is inheriting it. Between professionals, the handover is supposed to be easy. With an agent-built codebase it quietly is not, because the most important context never made it into the repository, and you are the only one who knows which parts to distrust.
Not your opinions about the code; they will form their own within a week. What they cannot form on their own is the evidence picture: which setup steps have actually been executed recently and on what, which of the README’s claims are real, which architectural choices were deliberate decisions versus whatever the agent produced at 11pm, and which corners of the codebase nobody, human or agent, has ever exercised. In a traditional project a good successor reconstructs some of this from commit history and review threads. In an agent-built one the reasoning lived in your sessions, and it leaves when you do.
Run the CLI before your last week, from the project root where your agent sessions live. The scan pulls facts, claims and decisions out of the repository and the transcripts, verify executes the real setup in a clean sandbox, and the resulting passport is the handover document you were never going to have time to write: architecture, reproduced setup, the decision log with your recorded reasoning, and the unknowns stated as unknowns.
The decision log is the part successors say they value most. Your recorded words in the transcripts become creator-confirmed entries, which means the next developer reads why sessions moved to JWTs or why the queue got dropped, from the record, not from folklore. The labelling rules that keep the document honest are the truth model.
If you are the inheritor, ask for a passport, and check it rather than reading it: npx mantyl receive compares the delivered code file-by-file against the manifest and re-executes the recorded checks on your machine. Divergence comes back named, before you have staked anything on the codebase. If there is no passport and the departing developer has no time, you can still run the scan and verify yourself on what you received; you lose their session history but keep the executed evidence and the contradiction detection, which is most of the safety. The buyer-grade version of this posture is covered in verifying AI-built software.
The traditional dev-to-dev handover is a document nobody finished and three weeks of you answering messages at your new job. The passport does not eliminate the conversation; it eliminates the archaeology, so the conversation you do have is about the interesting parts. Leaving a contract engagement rather than a team? The commercial edges of the same move are in contractor offboarding. And the checklist of everything around the code, credentials, runbooks, access, is the handover checklist.