boost-backend — Streaming chat and normalized event pipeline (issue 6 of 15)

[gabemontero]

Labels: ready-to-code
Depends on: Issue 2

Implement the SSE streaming endpoint, normalized stream event processing, and the chat route that connects providers to the frontend via NormalizedStreamEvent.

Tasks

From openspec/changes/platform-operations-deployment/tasks.md:

• 1.8 Conversation-agent maps: session-scoped cacheService
• 1.9 Rate limiter state: per-window cacheService

Specifications

• openspec/changes/pluggable-ai-platform-architecture/specs/normalized-streaming/spec.md
• openspec/changes/ai-chat-interaction-experience/specs/streaming-chat/spec.md
• openspec/changes/pluggable-ai-platform-architecture/design.md — Decision 3 (cacheService for all caches)

[fullsend-ai-triage]

Triage: Blocked

This issue is blocked by #3298 (boost-backend — Core plugin scaffold, ProviderManager, and security middleware, issue 2 of 15), which is still open.

The streaming chat endpoint and normalized event pipeline described here depend on the core plugin scaffold, ProviderManager, and security middleware that #3298 will deliver. Work on this issue cannot meaningfully begin until that foundation is in place.

Once #3298 is resolved, this issue can be re-triaged for implementation readiness.

---

Labels: This boost-backend issue falls under the ai-integrations workspace and is a new feature enhancement.