fix(ui): operator messages show in Agent Conversations instead of Your Conversations

[jsell-rh]

Root Cause

Both 'boss' (legacy) and 'operator' agents have agent_type='human' in the DB. The operatorName computed returned whichever was found first via Object.entries, which follows insertion order. In spaces where 'boss' was created first, operatorName='boss'.

Bug consequences when operatorName='boss' but messages carry sender 'operator':

• Conversations with 'operator' as participant appear under Agent Conversations (not Your Conversations)
• composeRecipient is null for those conversations → no compose box shown → operator cannot send messages
• Unread acknowledgement uses wrong recipient name

Fix

Collect ALL agent_type='human' agents into a humanAgentNames Set (instead of picking just one). Use that Set consistently:

Usage	Before	After
isOperatorConversation	participants.includes(operatorName)	participants.some(p => humanAgentNames.has(p))
composeRecipient	!participants.includes(operatorName)	!participants.some(p => humanAgentNames.has(p))
unreadCount	recipient === operatorName	humanAgentNames.has(recipient)
ackOperatorMessages	hard-coded operatorName as ack target	ack per msg.recipient
operatorName itself	first human found	prefer 'operator'; fall back to first human then 'operator'

Test Plan

• Open Conversations view in a space that has both boss and operator agents
• Verify messages sent by operator appear under Your Conversations
• Verify compose box appears for all human↔agent threads
• Verify unread badges and ack work for messages in operator inbox

Frontend TypeScript build: ✓ clean (vue-tsc -b + vite build)

🤖 Generated with Claude Code