ios-build-cleanup

# iOS build cleanup ## Contract | Field | Bound contract | |---|---| | Trigger | The user runs /ios-build-cleanup. | | Authority | Human-gated: requires explicit human invocation and previews the target and consequence before any irreversible deletion. The model never invokes it autonomously. | | Side effect | Local deletion of DerivedData and build artifacts only. These artifacts are untracked and regenerable by a rebuild. No source, VCS, credential, or remote mutation. | | Done | A clean build state is restored: DerivedData and project build artifacts are removed and the next build starts from a clean cache. | ## Inputs - Project root directory (optional; defaults to the current working directory). Used to locate project-specific build artifacts. - DerivedData path (optional; defaults to `~/Library/Developer/Xcode/DerivedData`). ## Procedure 1. Resolve the DerivedData directory. Default to `~/Library/Developer/Xcode/DerivedData`. If the user supplies a path, use it. 2. Resolve the deletion targets. Within the project root, resolve project build artifacts: `.build`, `build/`, and `*.xcodeproj`/`*.xcworkspace` build outputs. Under the DerivedData directory, identify this project's entries by Xcode's DerivedData naming rule: each entry is named `<projectName>-<hash>`, where `<projectName>` is the basename of the `.xcodeproj` or `.xcworkspace` file with its extension removed and spaces replaced by the underscore character, and `<hash>` is Xcode's digest of that file's abs...