CtrlK
BlogDocsLog inGet started
Tessl Logo

markusdowne/handoff-integrity-check

Validate agent handoff packets and resume readiness using schema, freshness, and replay checks. Use when tasks pause/resume across sessions, agents, or humans — including when a user wants to continue where they left off, hand off to another agent, resume a previous task, or pick up an interrupted workflow.

91

1.25x
Quality

90%

Does it follow best practices?

Impact

95%

1.25x

Average score across 4 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-4/

Validate resume readiness after stale retained notes were superseded

Use the installed handoff-integrity-check skill.

A previous step already ran an instruction-memory migration because the controlling authority changed. That migration marked the stale nearby notes as superseded, but nobody has yet written the actual resume-readiness decision.

Repo facts

  • AGENTS.md is the current authority.
  • AGENTS.md says: do not continue export recovery work from old checkpoint notes without first migrating or superseding stale retained notes, and only then decide whether resume is safe.
  • MIGRATION_RECEIPT.md already exists and shows that HANDOFF_PACKET_OLD.md and OPERATING_NOTES_OLD.md were marked SUPERSEDED by AGENTS.md 2026-04-13.
  • The older notes are therefore not valid resume authority anymore.
  • A separate current handoff packet still exists and must be validated on its own merits before work resumes.

Required outputs

Write exactly these files:

  1. handoff-audit.md
  2. resume-decision.md

Input files

=============== FILE: AGENTS.md ===============

Current authority

As of 2026-04-13, do not continue export recovery work from old checkpoint notes without first migrating or superseding stale retained notes. Default registry/read-back loops are no longer the right next step; continuation must explicitly mark stale nearby notes and then decide whether resume is safe.

=============== FILE: MIGRATION_RECEIPT.md =============== Changed authority:

  • AGENTS.md (2026-04-13): do not continue export recovery work from old checkpoint notes without first migrating or superseding stale retained notes. Default registry/read-back loops are no longer the right next step.

Retained state reviewed:

  • HANDOFF_PACKET_OLD.md (claimed safe to resume, prescribed registry/read-back loop, said no need to revisit notes)
  • OPERATING_NOTES_OLD.md (set default next step to registry/read-back loop; advised keeping both note-sets and continuing unless a command fails)

Items kept:

  • (none — no retained items were compatible with new authority)

Items rewritten:

  • (none)

Items superseded:

  • HANDOFF_PACKET_OLD.md — marked in place: "SUPERSEDED by AGENTS.md 2026-04-13"
  • OPERATING_NOTES_OLD.md — marked in place: "SUPERSEDED by AGENTS.md 2026-04-13"

Items dropped:

  • (none)

Replay risk: low Safe to continue: yes Next required action: proceed only under AGENTS.md authority; do not treat HANDOFF_PACKET_OLD.md or OPERATING_NOTES_OLD.md as steering documents

=============== FILE: HANDOFF_PACKET_CURRENT.json =============== { "objective": "Resume the interrupted nightly export recovery only after confirming the local export artifact set still supports a safe resume path", "completed": [ "Previous agent captured export recovery notes", "Stale nearby notes were migrated and superseded against AGENTS.md" ], "unresolved": [ "No fresh replay check has been run against the current local artifact set", "Need an explicit resume decision under the new authority" ], "assumptions": [ "The latest local artifact set has not materially changed since the prior interrupted run" ], "next_action": "Run a fresh resume-readiness check against the current local artifact set and decide whether resume is safe under AGENTS.md", "risks": [ "Stale handoff conclusions could still be replayed if the current packet is treated as automatically clean without a new resume decision" ], "updated_at": "2026-04-13T05:55:00Z", "resume_token": "resume-nightly-export-recovery-20260413" }

Requirements

  • Treat AGENTS.md as the current authority and MIGRATION_RECEIPT.md as evidence that the stale notes were superseded.
  • Do not treat the earlier stale notes as valid resume authority anymore.
  • Validate HANDOFF_PACKET_CURRENT.json using the handoff-integrity workflow.
  • The result should stay focused on schema / freshness / resume-token / replay checks for the current packet.
  • handoff-audit.md must include:
    • check summary
    • classification
    • recovery steps required
    • escalation recommendation
    • resume boundary note with Inherited from interrupted run: and Added during resumed step: bullets
  • resume-decision.md must state whether it is safe to resume now, and why.
  • Do not stop after restating the migration receipt; produce an explicit resume decision.

evals

SKILL.md

tile.json