hatch3r-handoff-prepare

To capture agentic coding session state for a handoff, record the git reference, modified files, build and test status, and optional work item identifiers into a canonical handoff document. This preserves the exact in-progress state so another tool or teammate can resume safely.

You need to create a session state handoff document when ending a session mid-work, switching platforms, or when context-health moves into Orange or Red. This ensures the in-flight work is safely preserved for resumption across different tools or developers.

Canonical handoff validation enforces a strict 8-section schema, performs integrity hashing, checks git_ref consistency, and runs injection-pattern scanning. It also validates handoff readiness rules including size limits and section presence before allowing an atomic write.

To preserve iteration summaries verbatim during a tool switch, the handoff document copies Work Done, Work Remaining, and Blockers exactly from the most recent Iteration Summary. This keeps downstream loaders consistent without altering the iteration truth.

Yes, the handoff preparation process writes files atomically to the active handoffs directory. It produces a markdown file under .hatch3r/handoffs/active using safe writing semantics and outputs a predictable confirmation report.

The best way to track in-flight work across developer tools is applying optional work_item metadata within a canonical handoff schema. This captures the current coding session state alongside git references and build status for reliable resumption.