hatch3r-handoff-resume

Resume a paused engineering handoff by validating its SHA-256 integrity hash, scanning for injection patterns, and checking frontmatter schema before surfacing the document. This deterministic process ensures the handoff content is safe, structurally sound, and treated as user-tier context for reliable continuation.

Git drift detection in an agent workflow evaluates git_ref, branch, and commit divergence against the original handoff state. You need it when resuming mid-work orchestration to ensure the underlying repository has not changed unexpectedly, preventing stale or invalid code context from corrupting the continuation.

Validate a handoff document schema by enforcing strict frontmatter rules, confirming required sections are present, and running injection-pattern scanning. The process checks structural integrity and expiry rules, rejecting invalid or expired documents before any status transition or work continuation occurs.

Resuming an in-progress handoff after a branch change triggers git drift evaluation, which surfaces the divergence between the saved git_ref and the current commit. The workflow prompts you to resolve the mismatch or archive the handoff, ensuring the continuation operates on verified repository state.

Handle expired handoff documents by enforcing expiry rules during the resume validation phase, which prompts you to either extend the validity or archive the stale handoff. This prevents resuming blocked or outdated work states and maintains pipeline integrity.

Handoff validation requires SHA-256 integrity checks and injection-pattern scanning to protect trust boundaries when treating handoff content as user-tier context. These security measures detect tampering and malicious content before the document is surfaced, ensuring safe agent workflow continuation.