compact-handofflisted

# compact-handoff compact-handoff preserves task continuity before or after context compaction. It does not trigger automatic compaction, add hooks, or create background summaries. It only defines the quality bar for a handoff that a human or future agent can safely resume. ## Contents - [When To Use](#when-to-use) - [Pre-Compaction Record](#pre-compaction-record) - [Do Not Compact When](#do-not-compact-when) - [Resume Procedure](#resume-procedure) - [Validator Rules](#validator-rules) - [Warnings](#warnings) ## When To Use - Context is long enough that work state may be lost. - Another session or agent must continue the implementation. - Test results, changed files, remaining work, forbidden surfaces, or rollback paths need to survive compaction. ## Pre-Compaction Record Write a short handoff with these fields, then validate it with `scripts/compact_handoff.py <handoff-file> --json`. If validation returns `status=fail`, fix the handoff before compacting. ```text [compact-handoff] - objective: <current objective> - completed: <completed work> - in-progress: <current item> - next-step: <one next action> - files-changed: <absolute paths> - tests-run: <commands and results> - forbidden-surface: <paths or actions not to touch> - rollback: <nearest rollback path> ``` ## Do Not Compact When - A RED test is failing and the root cause is still unknown. - A live configuration file is being edited without a rollback path. - The next step is a user approval gate. - Secret, t