Use structured stop completion to suppress stale milestone calls

When a logistics API provides structured stop arrival or departure timestamps, evaluate the relevant completion milestone before dispatching a scheduled call. A top-level shipment status or a free-text note classifier can miss a completed stop: status may be coarser than the milestone, and classifier input may omit the structured timestamp even when the API read fetched it. Apply the completion check to every obsolete call purpose, not just loading follow-ups. For multiple pickups, identify the relevant stop rather than treating any departure as completion of all pickups. A current API snapshot establishes field availability, not every historical response. Applies when: A voice scheduler continues pickup calls after a pickup milestone is complete. Keywords: Aljex API stop departure pickup scheduler milestone completion structured timestamp