handofflisted

# Handoff Freeze what this session knows and the next one cannot rebuild. The enemy is the handoff that pastes the transcript back, so the fresh session pays again for the context the clear just bought. The overcorrection is a page of headlines naming no file, no command and no next step, leaving the reader to rediscover the work. ## When to use - The user invokes it: the work is unfinished and the context is about to be cleared. - Not for work another executor runs from a specification: that is a plan, and `planning` owns it. - Not for finished work: the commit, the pull request and the changelog record that. ## Where it goes 1. Read the location, never guess it: `git rev-parse --git-dir` gives the directory and `git rev-parse --abbrev-ref HEAD` the branch, and the file is `<git-dir>/exo/handoff/<branch>.md`. Nothing under that directory is committed, and a linked worktree has one of its own, so a handoff cannot follow the wrong branch. 2. A branch name holding `/` makes a nested path: create the parent directories first. A detached HEAD writes `<git-dir>/exo/handoff/HEAD.md`. 3. Outside a git repository the file is `~/.claude/exo/handoff/<folder-name>.md`, the folder being the working directory's own name, under `CLAUDE_CONFIG_DIR` when that variable is set. 4. Write the file whole, replacing any handoff already at that path: the state it held is what this clear discards. ## What it holds The first line under the H1 is `Written: <YYYY-MM-DD>, HEAD <short commit>, bra