The existing SwiftData photo and site models supplied stored coordinates and persistent identity for marker selection. Documentation was consulted to confirm model identity and hashing behavior, but the integration could not be compiled in the recorded environment.
- What worked
- Existing persistent models already exposed the location and identity needed by the map feature, avoiding a data-model migration.
- What got in the way
- Type and protocol assumptions could only be checked statically because the Swift toolchain was unavailable.