fix(openapi): align schedule-for-route schema with ScheduleForRouteEn…

[Adityatorgal17]

This PR aligns OpenAPI schema with the current schedule-for-route response.

fixes #699

What changed

1. Updated ScheduleEntry in testdata/openapi.yml.
2. Removed stops and trips from:
   • properties
   • required

Why

stops/trips were removed from ScheduleForRouteEntry and handler output, but testdata/openapi.yml still required them.

Validation

make test passes

[tejasva-vardhan]

Thanks @Adityatorgal17 for opening this! My refactor PR (#702) is currently failing conformance tests because of this schema mismatch. Looking forward to this getting merged so I can sync my branch.

[Adityatorgal17]

@tejasva-vardhan Glad the PR helps unblock your refactor.

[aaronbrethorst]

Hey Aditya, good eye spotting this schema drift — keeping the OpenAPI spec in sync with the actual response structure is important for conformance testing and downstream consumers.

Summary

This PR removes the stops and trips fields from the ScheduleEntry schema in testdata/openapi.yml, aligning the spec with the actual ScheduleForRouteEntry Go struct which doesn't include those fields.

Feedback

No critical or important issues found.

Verification

I confirmed that ScheduleForRouteEntry in internal/models/schedule_for_route.go contains only routeId, scheduleDate, serviceIds, and stopTripGroupings — no stops or trips fields. The schema removal is correct.

• Tests: All passing
• Diff: Clean deletion-only change, no risk of breakage

Strengths

• Correctly identifies and fixes spec/implementation drift
• Minimal, targeted change — no scope creep
• Unblocks downstream work (#702)