Refactored all api endpoints to /bus/xxxxx

monitoring_ui/docs/admin_ui/README.md

@@ -3,15 +3,15 @@
 The schedule manager uses the weekly template model. Administrators create a
 departure for a bus line in one of three categories: weekdays, Saturday, or
 Sunday. The UI creates the corresponding `day_of_week` rows and assigns drivers
-through `transit.shifts`, rather than storing a driver on `transit.schedules`.
+through `"transit.bus".shifts`, rather than storing a driver on `"transit.bus".schedules`.
 
 The active UI uses these transit API endpoints:
 
-- `GET /admin/weekly-schedules`
-- `GET /admin/shift-drivers`
-- `POST /admin/weekly-schedules`
-- `PUT /admin/weekly-schedules/:scheduleId/shift`
-- `DELETE /admin/weekly-schedules/:scheduleId`
+- `GET /bus/admin/weekly-schedules`
+- `GET /bus/admin/shift-drivers`
+- `POST /bus/admin/weekly-schedules`
+- `PUT /bus/admin/weekly-schedules/:scheduleId/shift`
+- `DELETE /bus/admin/weekly-schedules/:scheduleId`
 
 # Transit Admin Control Center
 
@@ -142,7 +142,7 @@ When running in Docker, environment variables are injected at runtime via `docke
 The app communicates with:
 
 - **Auth API** (/login, /me)
-- **Transit API** (/admin/stops, /admin/bus-lines, /admin/fleet/buses)
+- **Transit API** (/bus/admin/stops, /bus/admin/bus-lines, /bus/admin/fleet/buses)
 - **Error Log API** (/error_log)
 
 All requests include JWT Bearer token for authentication.