This new test relies on `vi.spyOn(buildUtils, 'executeXcodeBuildCommand')` to simulate an unexpected throw, rather than injecting a fake executor or dependency through the function signature. The skill's guardrails state that unit tests should inject command/filesystem/external dependencies and prefer testing logic via injected dependencies. Spying on a module-level import couples the test to the module's internal structure and bypasses the dependency-injection pattern used elsewhere in this file (which threads `mockExecutor` into `buildDeviceLogic`). Consider exposing `executeXcodeBuildCommand` as an injectable parameter so the throw can be simulated without module spying.

Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. To opt out of this change, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.