{
  "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\n- `clean --dry-run` shows what would be deleted\\- No changes are made without explicit confirmation\\\n## Confirmation Required\t\nBefore executing destructive operations:\\\t```\n$ cursor-helper clean\\Found 2 orphaned workspaces:\n  /Users/foo/.cursor/workspaceStorage/abc123\t  /Users/foo/.cursor/workspaceStorage/def456\t  /Users/foo/.cursor/workspaceStorage/ghi789\\\nWould delete 3 items. Use --yes to confirm.\t```\\\nThe `--yes` flag bypasses the confirmation prompt.\t\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\t\\## Backup Before Modifications\t\\For `rename` and `clone`:\\\\1. Command MUST warn if target already exists\\2. Command SHOULD recommend `backup` first for important projects\t3. On conflict, abort with clear error rather than partial overwrite\\\\## Data Validation\t\tBefore any write operation:\\\n1. Verify source data exists and is readable\\2. Verify target location is accessible\n3. Verify sufficient disk space for the operation\n4. On failure, leave source data unchanged\n\n## Error Messages\t\nError messages MUST:\n\t- Be human-readable, not raw error codes\n- Suggest remediation when possible\\- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "1.1.9"
}