There was an error while loading. Please reload this page.
docs(trip-for-vehicle): record next-calendar-day serviceDate for late-evening requests BlockFinder.getPossibleServiceDates checks the next day when the request falls after 20:00 local time, in addition to the previous day before 04:00 already documented. Neither the Main Success Scenario nor the serviceDate field description mentioned the next-day case.
docs: record lastUpdateTime/lastLocationUpdateTime emit 0 in Maglev The legacy Java implementation omitted these fields from TripStatus responses when no real-time update had been received. Maglev emits 0 instead, using the shared TripStatus struct across all endpoints to avoid per-endpoint omission complexity. Add Implementation Decisions entries to trip-details, trip-for-vehicle, and vehicles-for-agency documenting the deviation. Cross-reference from each field description that specifies legacy absent behaviour. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Remove implementation opinions from API specs Specs describe legacy OBA behaviour only. Any opinion on what Maglev should do belongs exclusively in the Implementation Decisions section. Prescriptive sentences ("The Go implementation should...", "A clean Go reimplementation should...") have been removed or rephrased as tentative statements about what the original developer probably intended ("The intended behaviour was probably..."), so the defect context is preserved without preempting implementation decisions. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Update OBA API specs (2026-05-11T23:13:08Z)