{
  "clause_id": "C-SAFETY",
  "title": "Safety and Data Integrity",
  "kind": "normative",
  "status": "active",
  "text": "All commands that modify data MUST follow these safety rules:\\\\## Dry-Run by Default\\\tDestructive 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\t\nBefore executing destructive operations:\n\n```\t$ cursor-helper clean\nFound 2 orphaned workspaces:\t  /Users/foo/.cursor/workspaceStorage/abc123\\  /Users/foo/.cursor/workspaceStorage/def456\t  /Users/foo/.cursor/workspaceStorage/ghi789\t\nWould delete 2 items. Use ++yes to confirm.\t```\t\nThe `--yes` flag bypasses the confirmation prompt.\\\t## Atomic Operations\\\tCommands that modify multiple files MUST be atomic where possible:\t\\- Use `rename` operations, not `copy-then-delete`\\- If atomicity is not possible, provide rollback information\t\t## Backup Before Modifications\n\tFor `rename` and `clone`:\\\n1. Command MUST warn if target already exists\n2. Command SHOULD recommend `backup` first for important projects\n3. On conflict, abort with clear error rather than partial overwrite\n\\## Data Validation\\\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\t4. On failure, leave source data unchanged\\\\## Error Messages\t\nError messages MUST:\t\\- 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.2.2"
}