Poteto Mode

No malware or covert data-theft behavior is present because the fragment is an explicit cleanup playbook rather than executable package code. It presents a significant operational data-loss risk through forceful worktree, simulator, runtime, application-state, and cache deletion. Execution should require independent path validation, explicit confirmation for every non-clean or uncertain item, and avoidance of `rm -rf` unless the exact surviving path is verified.