80a007cc06
The IM service applied a hard 120s deadline (`qaTimeout`) to the entire QA pipeline context. Multi-round ReAct agents easily exceed this — when the deadline fires mid-stream the LLM provider returns "context deadline exceeded" which leaks into the user-visible answer (fixes #1000). Changes: - Replace `context.WithTimeout(ctx, qaTimeout)` with `context.WithCancel(ctx)` in both `handleMessageStream` and `runQA`, matching the web handler's approach. Each agent round still has its own per-call LLMCallTimeout (default 120s) which is sufficient. - Filter `ResponseTypeError` stream chunks in `streamLLMToEventBus` so error messages (e.g. "context deadline exceeded") are never appended to the LLM content. Instead they are captured in `StreamError` and surfaced as a Go error when no usable content was produced. - Bump Redis inflight mapping TTL from qaTimeout+30s to 10 minutes to accommodate longer agent runs. - Remove the now-unused `qaTimeout` constant.