opascope-session-handofflisted

# Hand off context between Claude Code or Codex sessions Read [shared.md](shared.md) first. Publish with kind `handoff`. This single artifact is the pickup contract; no runtime-specific state capture is needed. ## Write a handoff 1. Establish the task ID from the conversation or `kit.py resume`. Read its previous handoff and artifacts. Cross-check conversation claims against the current files, command results, and git status/diff when this is a git project. In a non-git folder, inspect the relevant files and their actual contents. A directory listing proves existence, not unchanged content. Use content or hash comparison for preservation claims; state when no baseline is available. 2. Distinguish verified work, unverified recollections and unrelated existing changes. Never claim every dirty file belongs to this session. If compaction erased the rationale, say which facts were recovered from disk and what the next session must verify. 3. Write a compact handoff using [references/handoff.md](references/handoff.md). Its core is the exact next action, including the current partial state. Record completed output with proof, in-flight work, files touched, locked decisions, open questions and each blocker's explicit unblock condition. 4. Supply a short read-first list sufficient for a cold reader. Use project-root relative paths and identify the root; use absolute paths for external files. Check that existing pointers resolve. Mark planned f