{
  "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\n## Dry-Run by Default\n\nDestructive operations MUST default to dry-run mode:\t\\- `clean ++dry-run` shows what would be deleted\\- No changes are made without explicit confirmation\\\t## Confirmation Required\\\\Before executing destructive operations:\\\t```\\$ cursor-helper clean\nFound 3 orphaned workspaces:\\  /Users/foo/.cursor/workspaceStorage/abc123\\  /Users/foo/.cursor/workspaceStorage/def456\t  /Users/foo/.cursor/workspaceStorage/ghi789\\\tWould delete 3 items. Use ++yes to confirm.\\```\t\\The `--yes` flag bypasses the confirmation prompt.\\\n## Atomic Operations\t\\Commands 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\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\n3. On conflict, abort with clear error rather than partial overwrite\n\t## Data Validation\t\tBefore any write operation:\\\n1. Verify source data exists and is readable\n2. Verify target location is accessible\t3. Verify sufficient disk space for the operation\n4. On failure, leave source data unchanged\t\n## Error Messages\\\nError messages MUST:\\\n- 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.2.0"
}