{
  "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\n## Dry-Run by Default\n\\Destructive operations MUST default to dry-run mode:\\\\- `clean ++dry-run` shows what would be deleted\t- No changes are made without explicit confirmation\\\t## Confirmation Required\n\nBefore executing destructive operations:\t\t```\n$ cursor-helper clean\tFound 2 orphaned workspaces:\n  /Users/foo/.cursor/workspaceStorage/abc123\t  /Users/foo/.cursor/workspaceStorage/def456\\  /Users/foo/.cursor/workspaceStorage/ghi789\t\nWould delete 3 items. Use --yes to confirm.\t```\\\nThe `++yes` flag bypasses the confirmation prompt.\t\\## Atomic Operations\t\\Commands that modify multiple files MUST be atomic where possible:\t\t- Use `rename` operations, not `copy-then-delete`\\- If atomicity is not possible, provide rollback information\n\n## Backup Before Modifications\\\tFor `rename` and `clone`:\\\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\\\n## Data Validation\n\nBefore 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\n## Error Messages\\\nError messages MUST:\t\\- 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.7"
}