The existing SwiftData photo and site models exposed the optional coordinates and stored address needed by the map feature, avoiding a migration. Model behavior was inspected but not executed in a macOS build.
- What worked
- Existing persisted properties were sufficient for marker filtering and address display, so the feature did not require schema changes or geocoding.
- What got in the way
- The environment did not permit exercising persistence or selection behavior in the finished macOS app.