⚠️ CUTOVER (do not merge until coordinated): Promote test → main — /api/chat rename (api#645)
Merged
SW
6mo ago+35+35+01234567890123456789-4-4-0123456789
Draft on purpose — this is the breaking half of the /api/chat/workflow → /api/chat cutover (chat#1767). Merging this promotes api#645 to prod, which deletes /api/chat/workflow (no alias).
🚦 Do NOT mark ready / merge until the cutover window is go
The moment this deploys to prod, every consumer still on /api/chat/workflow 404s. Required lockstep:
- ✅ Merge open-agents#47 (open-agents →
/api/chat) - Merge this (api
test→main) — prod api drops/workflow, adds/api/chat - Merge the chat promotion (chat test→main — sibling cutover PR) so prod chat is on
/api/chat - Ensure open-agents is deployed to prod in the same window
- Smoke-test prod: new chat streams via
POST /api/chat;POST /api/chat/workflow→ 404
⚠️ External API-key callers get no alias — they must move to /api/chat.
Net content
- api#645 — add
POST /api/chat(delegates tohandleChatWorkflowStream) + deleteapp/api/chat/workflow/route.ts. Verified on preview: authenticatedPOST /api/chat→ 200 SSE stream;/api/chat/workflow→ 404. - (Earlier test items #632/#634/#635 already on
mainvia api#643.)
Summary by cubic
Promotes the chat streaming endpoint rename to prod: /api/chat/workflow is removed and replaced by POST /api/chat (delegates to handleChatWorkflowStream). Adds route tests and CORS OPTIONS; consumers on the old path will 404.
- Migration
- Ensure
open-agentsand chat clients usePOST /api/chat; deploy them first. - Merge this PR during the cutover window to drop
/api/chat/workflow. - Smoke-test:
POST /api/chatstreams 200;POST /api/chat/workflowreturns 404. - External API-key callers must update to
/api/chat(no alias).
- Ensure
Summary by CodeRabbit
- Documentation
- Updated API endpoint documentation to clarify the canonical path for the chat agent loop and confirm backward compatibility of the alternative endpoint path during client migration.