Relied on the existing route loader that already supplied all schedule rows, then added client-side filtering in the route component with no backend or migration change. Production build produced client and server bundles and served the page successfully.
- What worked
- Loader-supplied data made server search unnecessary; build and server-rendered page with search controls and result list worked on first verification.