588f84c344
Captures the working request bodies for the customer login/booking and the admin/hub assign-miler endpoints, plus the constraints that are easy to hit and hard to diagnose: - CityGate only accepts pickup pincodes in 641/600/560/500 - hub assign-miler 403s unless milerprofiles.hubid matches the calling hub, and most milers have hubid NULL - CreateCustomerBooking auto-assigns in the background, so a booking is often already on a miler before you assign one - the routing watchdog sweeps unaccepted assignments within ~a minute and may re-assign under a new bookingassignmentid, so accept IDs must be re-read - reject takes its reason in the body, not the query string Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>