feat: Add speaker_name to MCP conversation endpoint

[smian1]

Summary

• Adds speaker_name field to transcript segments in MCP API response
• Matches the developer API behavior from feat: Add speaker name mapping to transcript segments in developer API and webhook #3962

Changes

• Added speaker_name: Optional[str] to SimpleTranscriptSegment model
• Added _add_speaker_names_to_segments() helper (same logic as developer.py)
• Called in GET /v1/mcp/conversations/{conversation_id} endpoint

[gemini-code-assist]

Code Review

This pull request adds the speaker_name field to the transcript segments in the MCP API response, aligning it with the developer API. The implementation is clear and correctly adds the new field to the SimpleTranscriptSegment model and includes a helper function, _add_speaker_names_to_segments, to populate it. The logic for resolving speaker names seems robust. However, I've identified a significant maintainability issue regarding code duplication that should be addressed.

[Copilot]

Pull request overview

This PR adds speaker name information to transcript segments in the MCP conversation endpoint, matching the existing functionality from the developer API (PR #3962).

Key Changes:

• Added speaker_name field to the SimpleTranscriptSegment model
• Implemented _add_speaker_names_to_segments() helper function to populate speaker names
• Integrated speaker name enrichment into the conversation detail endpoint

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.