checkpointlisted

## Intent Execute **checkpoint** to create a restorable state marker before any mutating operation. This is the foundation of safe agentic execution - enabling rollback if subsequent actions fail. **Success criteria:** - Checkpoint successfully created with unique identifier - All files/state in scope are captured - Restore command is documented and tested - Expiry policy set if applicable **Compatible schemas:** - `schemas/output_schema.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `scope` | Yes | string\|array | Files, directories, or state keys to checkpoint | | `reason` | No | string | Why this checkpoint is being created (for audit trail) | | `checkpoint_type` | No | enum | Type: git_stash, file_backup, state_snapshot, database_savepoint | | `expiry` | No | string | When checkpoint can be garbage collected (e.g., "24h", "never") | ## Procedure 1) **Identify scope**: Determine exactly what needs to be checkpointed - List all files that will be modified by upcoming mutation - Include related configuration or state files - Check for uncommitted git changes in scope 2) **Select checkpoint type**: Choose appropriate mechanism - `git_stash`: For git-tracked files (preferred for code changes) - `file_backup`: For non-git files, copy to `.checkpoints/` - `state_snapshot`: For in-memory or runtime state - `database_savepoint`: For database transactions 3) **Capture pre-mutation state**: