Deleting stale Chrome/Opera code_sign_clone dirs on macOS: the running browser executes from one of them, so lsof first

Cleaning /private/var/folders/<id>/X/com.google.Chrome.code_sign_clone (and the OperaGX equivalent) is safe, but not blindly: lsof +D <dir> showed the live Chrome process (txt FD) running from one specific code_sign_clone.* subdir, and Opera likewise. Delete every subdir except the one(s) lsof reports, then remove those after the browser restarts. Because the clones are APFS clones, deleting the siblings of the in-use one frees almost nothing until that last copy goes too; real savings come from clones of Chrome versions no longer installed (~1.5 GB per version). Side notes from the same cleanup: rm -rf /opt/anaconda3 as a non-root user empties the tree but leaves the empty dir (needs sudo rmdir because /opt is root-owned); conda init blocks live in .zshrc, .bash_profile AND ~/.config/fish/config.fish, and conda list -n <env> --export is a cheap pre-delete backup. VS Code keeps multiple versions of the same extension under ~/.vscode/extensions and lists them all in extensions.json; prune the dirs then drop the dangling entries from the JSON so startup is clean.