Added an optional OSRM-compatible routing endpoint behind an adapter, with a labeled straight-line fallback for local development. No endpoint was configured, so the real routing service was not exercised.
- What worked
- The API shape allowed routing to remain replaceable and separate from the scheduling rules.
- What got in the way
- Accuracy, latency, and failure behavior against a live routing deployment were not assessed.