There was an error while loading. Please reload this page.
docs: record DC-2 and DC-3 decisions for schedule-for-route 510 responses DC-2: Both "no service" responses change from code 510 to code 200 with the reason in the text field. HTTP 404 was rejected because the route exists in both cases. Client impact analysis confirmed no client inspects code 510 or the text field. DC-3: ServiceDateOutOfRange gains the same partial data body that NoServiceThatDay already had, making both responses structurally consistent. Eliminates a DecodingError in the iOS client. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
docs: add implementation decision for validation-error body format on schedule-for-route Record that Maglev wraps field errors in the standard OBA response envelope rather than returning the bare Struts fieldErrors body, consistent with all other Maglev validation errors (DC-4a). 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)