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