Fix: assistant history always null due to mismatched JSON field key in buildConversationContext

[Copilot]

buildConversationContext() was reading agentSummary from Redis history entries, but SessionStore.saveChatEntry() persists the field as agentOutput. This caused the assistant side of every history turn to deserialize as null, meaning multi-turn conversations only replayed user messages.

Changes

• SecuritySupervisorAgentService.java
  • Changed JSON field read from agentSummary → agentOutput to align with what SessionStore writes
  • Updated Javadoc to document the correct Redis entry shape and added @link cross-reference to SessionStore#saveChatEntry

// Before — always resolved to null
String summary = node.path("agentSummary").asText(null);

// After — correctly reads the persisted field
String summary = node.path("agentOutput").asText(null);

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.