context-lifecycle

Context checkpointing saves your working state before compaction events or git pushes. It reads existing progress files and coordinates memory flushes to ensure no implementation context is lost during session transitions.

The best way to resume work after compaction is to read the latest checkpoint file and execute the next explicit action. This validates the resume boundary and restores the full session state before continuing the coding task.

You save agent state by triggering a checkpoint before phase endings and git push events. This orchestrates a session handoff by flushing memory and writing a progress file, ensuring safe recovery after the transition.

Cross-session handoff coordinates context packing and neural memory workflows to transfer state across boundaries. It compacts the previous session and restores it in the new one, allowing extended implementation work to proceed without context loss.

You should trigger a context checkpoint at phase endings, pre-compact and post-compact transitions, and git push events. This ensures state and next steps are saved before any session boundary or context window compression occurs.