There was an error while loading. Please reload this page.
docs(search-stop, search-route): note no-match 200 as deliberate deviation Both endpoints' legacy behavior (return HTTP 404 with the standard error envelope when a search matches nothing) stays the documented spec. Add an Implementation Decisions entry to each (creating the section on search-route.md, which didn't have one) explaining that Maglev instead treats a no-match query as a successful, empty result (HTTP 200, data.list: []), and cross-reference it with pointers from Minimal Guarantees, Extensions, and the Response Structure fields that describe the legacy 404 behavior.
Update OBA API specs (2026-05-11T23:13:08Z)