fix: `ChatManager.get_escalations` iterates the entire escalations list on every call — replace with per-conversation index

[BigBen-7]

Description

src/chat.py stores all escalation events in a single flat list:

self.escalations: List[EscalationEvent] = []

get_escalations(conversation_id) filters this list on every call:

def get_escalations(self, conversation_id=None) -> List[EscalationEvent]:
    if conversation_id:
        return [e for e in self.escalations if e.conversation_id == conversation_id]
    return self.escalations.copy()

In a high-volume support environment with thousands of escalations, every call to GET /chat/{id}/escalations scans the entire list. With 10,000 escalations and 100 concurrent requests, this is 1,000,000 comparisons per second.

Requirements & context

• Replace the flat self.escalations: List[EscalationEvent] with a per-conversation dict:

  self.escalations: Dict[str, List[EscalationEvent]] = {}

• Update escalate_conversation to append to self.escalations.setdefault(conversation_id, [])
• Update get_escalations(conversation_id):
  • With conversation_id: return self.escalations.get(conversation_id, [])
  • Without: return a flat list from all values (only used for admin queries)
• The change must be backward-compatible — existing callers of get_escalations must work without modification
• Write a performance test confirming lookup time is O(1) per conversation, not O(n) global

Suggested execution

git checkout -b fix/chat-escalations-dict-index

• Update src/chat.py
• Write tests confirming O(1) lookup

Guidelines

• PR must include: Closes #[issue_id]
• Timeframe: 24 hours

[BigJohn-dev]

@BigJohn-dev has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

This issue appeals to me because it combines the challenge of solving complex frontend performance problems with the opportunity to deliver a smoother, more reliable user experience, while also sharpening my skills with emerging design and resolution patterns.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @BigJohn-dev to this issue.

[Jacques-codes]

@Jacques-codes has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi, I'm a seasoned senior developer, and I would love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jacques-codes to this issue.