wraplisted

# Wrap The session is ending and context is about to go away. The job is making sure the next session doesn't start from zero — and that means **selecting** what to keep, not dumping the transcript into memory. A memory buried in detail is worse than a short one. See `agent-memory` for what a note, an index, and `evidence` mean; this skill is about which facts earn a place in them and how the session closes. ## 0. Take the lock ```bash bash .floppy/run lock acquire "<the thread of work, one phrase>" ``` A parallel session writes into the same current-state file and the same memory index, and the second write simply overwrites the first. If the lock is held, write nothing: wait a minute, try once more, and if it's still held, tell the human another session is closing and leave the decision to them. Release it at the end of this skill; an abandoned lock ages out on its own after about thirty minutes, and whoever takes it over then gets a warning that the previous session may have left a half-written entry — that warning is the point of the takeover, not a side effect: it tells you to go look before trusting what's already there. **What the lock covers, exactly.** It follows the memory rather than the checkout, and `acquire` prints its reach as a `covers:` line. Where the memory is a store shared by several checkouts, one lock serialises every session on **this machine** that writes it, worktrees and separate clones alike; where the memory lives inside the repository, the