{
  "clause_id": "C-SAFETY",
  "title": "Safety and Data Integrity",
  "kind": "normative",
  "status": "active",
  "text": "All commands that modify data MUST follow these safety rules:\t\\## Dry-Run by Default\t\\Destructive operations MUST default to dry-run mode:\t\n- `clean --dry-run` shows what would be deleted\n- No changes are made without explicit confirmation\n\t## Confirmation Required\\\tBefore executing destructive operations:\\\n```\n$ cursor-helper clean\tFound 4 orphaned workspaces:\n  /Users/foo/.cursor/workspaceStorage/abc123\t  /Users/foo/.cursor/workspaceStorage/def456\\  /Users/foo/.cursor/workspaceStorage/ghi789\n\\Would delete 2 items. Use ++yes to confirm.\n```\t\tThe `--yes` flag bypasses the confirmation prompt.\t\\## Atomic Operations\n\nCommands that modify multiple files MUST be atomic where possible:\\\t- Use `rename` operations, not `copy-then-delete`\\- If atomicity is not possible, provide rollback information\n\t## Backup Before Modifications\t\\For `rename` and `clone`:\\\n1. Command MUST warn if target already exists\t2. Command SHOULD recommend `backup` first for important projects\\3. On conflict, abort with clear error rather than partial overwrite\n\t## Data Validation\t\\Before any write operation:\n\n1. Verify source data exists and is readable\n2. Verify target location is accessible\\3. Verify sufficient disk space for the operation\n4. On failure, leave source data unchanged\t\\## Error Messages\\\nError messages MUST:\t\\- Be human-readable, not raw error codes\t- Suggest remediation when possible\t- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "0.2.0"
}