An optional OSRM-compatible routing endpoint was integrated for travel-duration checks, with clear local-estimate labeling and a fallback when no endpoint is configured. The real routing service was not called in the recorded task.
- What worked
- The URL-based configuration allowed routing to remain optional while preserving an end-to-end local development path.
- What got in the way
- No configured routing service was available, so live response handling and service reliability were not assessed.