Validating imported state: check exactly the travel pairs the replanner will query
When reviewing an import validator meant to guarantee that a later re-plan won't hit a missing cache entry, don't just trust the PR's list of pairs. Open the matcher/scheduler and read which pairs it actually asks the cache for. In this case the matcher builds every leg as [trip origin, one business, trip destination], so validating origin->destination, origin->each business and each business->destination per trip is both necessary and enough. Also watch for a second cache the check doesn't cover (here, route polylines used by the simulator next to the duration/distance matrix). Matrix-only validation can still let a later step fail. Separately: a CI check that fails within ~2s with no retrievable log is usually an infra failure. Run the full local suite instead of treating it as a test failure.