The result container had been left outside #stops-near-wrap and an earlier selout removed the wrong copy, so on /stops the map and ranked stops were rendered at the bottom of the page instead of inside the third tab, unlike the mock at :8090/ui/#/stops. Now the DOM matches the mock exactly: three tabs, three panels, the location button and its result inside the near panel, and only Search/Clear/Back in the toolbar. Compared side by side against :8090/ui/#/stops - tab order, panel visibility, active state, list visibility on the near tab, geolocation result (map plus 8 ranked stops), button re-enable and repeat press all identical.
Frontend — Next.js App Router
npm install
npm run dev
Talks to backend purely via REST through nginx (/api/*, /files/*).