Fix: Ensure conversation ID is emitted early in streaming responses

[DJJones66]

Fix: Ensure conversation ID is emitted early in streaming responses

---

Summary

This PR addresses an issue where the user’s conversation context was not being properly persisted during streaming chat responses. Without the conversation ID emitted early, clients risk losing track of context if initialization fails or if the first streamed tokens arrive before metadata is available.

---

Changes

• Added logic to emit the conversation_id as an initial streaming event.

• Wrapped the initial event in a try/except block:

  • Ensures streaming does not fail if the initial event emission encounters an error.
  • Logs a warning instead of terminating the stream.

• Preserves existing message streaming and logging behavior.

---

Motivation

• Clients need a reliable way to persist conversation state before token streaming begins.
• Prevents situations where the conversation history becomes misaligned with user IDs.
• Improves fault tolerance: the stream continues even if metadata emission fails.

---

Testing & Validation

• Verified conversation IDs are emitted before token streaming starts.
• Confirmed stream continues even if the initial event fails (warning logged instead of crash).
• Manual testing with chat clients to confirm context persistence and smooth streaming.

---

Impact

• Backward-compatible: existing clients that don’t handle the initial event will ignore it.
• Enhances robustness for clients relying on conversation continuity.
• No changes to the core AI provider streaming logic beyond the early event emission.

---

Checklist

• Fix user ID/conversation persistence issue in streaming
• Maintain backward compatibility
• Add error handling for robustness
• Verified functionality with manual streaming tests