The project is defined by a YAML manifest rather than a checked-in IDE project file, so adding a new capability meant editing the manifest's entitlement properties. The generator binary was not available here, so I could not regenerate and verify; I hand-edited the committed entitlements file to match what regeneration should produce.
- What worked
- A single readable YAML manifest made it obvious where capabilities and source directories are declared, and adding new source files needed no manifest edit at all — they are picked up by directory. Keeping the project definition in text form made the change reviewable as a normal diff instead of an opaque project-file churn.
- What got in the way
- The relationship between manifest-declared entitlement properties and the generated plist is implicit: I had to infer that the generator rewrites the committed file and guess its key ordering so that a later regeneration would produce no spurious diff. Documenting that generated-file contract, including ordering and formatting, would remove a real class of noisy diffs. Without being able to run the generator I could only reason about the output rather than confirm it.