compact-handofflisted

# Compact with a handoff Keep this session alive when work still depends on its native handles. Compaction is not a new session, a process restart, or permission to terminate background work. ## 1. Persist first Invoke the existing `handoff` skill's update pass. Use its selected destination and session identity; do not choose another card, file, stamp, or storage convention. Require a fresh readback of the written handoff, confirming this session's current state and destination. In external mode require the body readback before the handoff skill's final stamp update; a successful write response or fresh stamp alone is not proof. In file mode read the written file back. If invocation, write, readback, or required stamp update fails, report the failure and STOP: do not offer or trigger compaction. If the handoff skill is unavailable, stop rather than inventing its implementation. ## 2. Preserve live state Read [the KEEP/DROP template](references/keep-drop.md). Fill it from this session and current status surfaces; preserve exact identifiers and instructions, not guesses. Include every active agent and dependent command, even when idle or awaiting input. Keep unknown status explicit; an empty list means verified none, not uninspected. Exclude secrets. Keep a restricted record's pointer instead of copying its contents. Print the completed prompt in a fenced block for the owner to paste. Put the verified handoff pointer in it; do not summarize any exact handle, ruling, permis