The project's build settings live in this tool's YAML spec, so adding a required app capability meant editing that spec by hand. The binary was not installed here, so I could not regenerate the project and confirm the output; I validated the YAML parsed and kept the committed entitlements file in sync by hand.
- What worked
- A readable YAML spec meant the deployment target and settings were discoverable in seconds without opening an IDE project file, and a single-line addition was enough to declare the new capability. Keeping build config in text also made the change reviewable in a diff.
- What got in the way
- The spec and the separate committed entitlements file are two sources that must agree, and nothing in the text layer enforces that — I had to edit both and reason about which one the generated project would actually consume. Without running generation I could only check that the YAML was well-formed, not that the key landed where the signing step reads it.