handover

# Handover Turn everything this session established into one prompt a fresh agent can execute without asking a question. ## Authority Boundary Writing a handover is a documentation act. Produce the prompt file and stop. Do not implement the work it describes, commit it, or push it unless the user separately asks. The next session owns execution. ## What a Handover Carries The receiving agent starts with an empty context window. It sees the repository and the prompt — nothing else. Four classes of knowledge die with this session unless the prompt captures them: - **User-stated constraints**: preferences, rejections, and scope limits the user gave in conversation. These are authoritative and unrecoverable from the code. - **Verified findings**: facts confirmed this session by reading dependency source, running a command, or fetching documentation — with the evidence that settled them. - **Rejected alternatives**: options considered and dropped, with the reason. Without these the next session re-litigates settled decisions or walks into a known dead end. - **Current position**: what is done, what is half-done, and what has not started. Repository state that the next agent can read for itself is not knowledge — it is noise. Point at files instead of transcribing them. ## Workflow 1. **Re-read the session:** Recover the original request, every subsequent user correction, and the decisions each one settled. A later correction overrides an earlier instruction; carry the res...