Plan mode rejects forced service steps as infeasible, but solve returns the same route

[nir-ben-menachem]

Summary
Plan/check mode (-c) fails with “Infeasible route for vehicle 39” with a route with forced service. The same input in solve mode returns the exact route we pass in steps, so it appears feasible. The forced service bounds are just the respective time windows.

Repro

• Run plan: bin/vroom -i request.json -c
• Plan mode exits: Infeasible route for vehicle 39

Expected

• Plan mode should accept the route, since solve returns the same sequence as provided in steps
  (start → break(40) → job 71 → job 100 → job 107 → end).

Control (works)

• bin/vroom -i request.json returns the same route as in steps

Possible cause (Codex hypothesis)

• In plan mode, earliest-date or lower-bound propagation may not account for break travel slack when the break has forced service_after/service_before bounds. This can over-constrain early arrival times and produce a false infeasibility even
  though solve mode can satisfy the same step sequence.

Version

• vroom 1.15.0-dev (commit 004faa4)
  request.json

[jcoupey]

Thanks for reporting and sharing an example, I can definitely reproduce.