Skip to content

History / schedule for stop

Revisions

  • docs: clarify schedule-for-stop references block is always present includeReferences=false was described as omitting data.references entirely. In practice (and consistent with route.md/stop.md and the legacy BeanFactoryV2 behavior), the block stays present with empty lists. Tightened three spots: the request-param schema, the prose description, and the envelope's data.references description.

    @burma-shave burma-shave committed Jul 9, 2026
  • 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>

    @burma-shave burma-shave committed May 28, 2026
  • Record Maglev decision to return 404 for unknown stop in schedule-for-stop Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

    @burma-shave burma-shave committed May 28, 2026
  • Update OBA API specs (2026-05-11T23:13:08Z)

    @burma-shave burma-shave committed May 11, 2026