Jason Woltje 23036cb1dd fix(web): route Mission Control API calls through orchestrator proxy ...

The Mission Control components were calling /api/mission-control/* which
routes to mosaic-api.woltje.com (the main API) — those routes don't exist
there, causing 404s.

These routes live on the orchestrator service and must go through the
Next.js server-side proxy (which injects ORCHESTRATOR_API_KEY):

Changes:
- Add catch-all proxy route at /api/orchestrator/[...path]/route.ts
  Forwards any GET/POST/PATCH/PUT/DELETE to ORCHESTRATOR_URL/<path>
  Replaces the need for per-endpoint proxy files for new routes.
- Update all Mission Control components to call
  /api/orchestrator/api/mission-control/* instead of /api/mission-control/*
- Update test expectations to match new paths

2026-03-08 11:45:31 -05:00

..

api

feat(api): MS23 mission control Prisma schema (#699)

2026-03-07 01:18:06 +00:00

coordinator

fix(test): make queue completion test more robust (#663)

2026-03-03 02:36:36 +00:00

orchestrator

fix(mission-control): increase rate limit for events/recent, add error handling

2026-03-07 18:42:50 -06:00

web

fix(web): route Mission Control API calls through orchestrator proxy

2026-03-08 11:45:31 -05:00