xcode-simulator-testing

# Xcode simulator test ## Contract | Field | Bound contract | |---|---| | Trigger | /xcode-simulator-testing [scheme name or 'current' to use default] | | Authority | Reversible local: build, install, and launch the app in a local iOS simulator, capture logs and screenshots, and boot or shut a simulator created for this run. No project source, VCS, credential, or remote mutation. | | Side effect | Builds and launches the iOS app in a simulator, captures logs and screenshots, and reports evidence. | | Done | A completed run reports overall PASS, FAIL, or PARTIAL with per-surface evidence and residual failures. | ## Inputs - Scheme argument (optional): empty or `current` selects the default or last-used scheme; a named argument selects that scheme. Ask only when the scheme cannot be resolved or project discovery is materially ambiguous. - The user's request and the changed iOS surface define the screens and flows to exercise. - Required environment, which this skill does not install or configure: XcodeBuildMCP connected as an MCP server, Xcode and its command-line tools, a valid project or workspace, and an available iOS simulator. ## Procedure 1. Run the availability gate. Confirm that the active harness exposes XcodeBuildMCP's simulator-listing capability and that the call succeeds; host-specific MCP tool prefixes are adapters, not the contract. If the capability is absent or errors, stop before discovery or build. Report that XcodeBuildMCP must be installed and connect...