xcode-disk-cleanuplisted

# Xcode Disk Cleanup ## Safety contract - Treat every cleanup request as permission to audit, not permission to delete. - Never mutate storage before presenting exact candidate IDs, paths or simulator identifiers, measured sizes, risks, and regeneration costs. - Treat a category-level request made after an audit (for example, “remove all outdated documentation caches”) as approval of the matching, current frozen selection set when it was already fully enumerated to the user. Execute in that turn after revalidation; do not restate the set and ask again. No special command or repeated confirmation is required. Broad requests made before an audit, such as “clean Xcode” or “delete everything,” remain audit-only. - Default ordinary files and directories to Trash. Explain that space is not reclaimed until Trash is emptied, and request separate approval before doing so. - Revalidate identity and running-process usage immediately before mutation. - Never use wildcards, unbounded `rm -rf`, `sudo`, SIP changes, or manual deletion inside system-managed CoreSimulator and MobileAsset directories. - Preserve archives and dSYMs unless the user proves the exact distributed build is backed up elsewhere and separately approves deletion. - Never delete `Package.resolved`, signing assets, credentials, custom DocSets, the active Xcode, a running simulator, or an Xcode that uniquely provides a required SDK/toolchain. - Report summed candidate sizes separately from actual AP