rollbacklisted

## Intent Execute **rollback** to restore system state to a previously created checkpoint. This is the recovery mechanism in the CAVR (Checkpoint-Act-Verify-Rollback) pattern - used when mutations fail or produce undesired outcomes. **Success criteria:** - State fully restored to checkpoint state - Post-rollback hash matches checkpoint hash - No orphaned artifacts remain from failed mutation - Audit trail of what was reverted **Compatible schemas:** - `schemas/output_schema.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `checkpoint_id` | Yes | string | ID of checkpoint to restore to | | `scope` | No | array | Specific files/keys to rollback (default: all in checkpoint) | | `verify_restore` | No | boolean | Whether to verify state matches checkpoint after restore (default: true) | | `reason` | No | string | Why rollback is being performed (for audit) | ## Procedure 1) **Validate checkpoint**: Confirm checkpoint exists and is valid - Look up checkpoint by ID in `.checkpoints/` or git stash - Verify checkpoint integrity (hash check) - Confirm checkpoint has not expired - If checkpoint missing: FAIL immediately with clear error 2) **Capture current state**: Record what will be reverted - List all files/state that differ from checkpoint - Compute hash of current state for audit - Document changes that will be undone 3) **Execute restoration**: Apply the restore command - For git_stash: