Distinguish between agent conversation model update types

[peicodes]

Tracking issue for PR #9864.

Differentiates between types of agent conversation model updates to avoid costly full-list rebuilds in the agent management view.

[oz-for-oss]

@peicodes

Here's what I found while triaging this issue:

This appears to be an internal tracking issue for PR #9864, which has already been merged and closes #10076.

Maintainer details

I concluded that internal tracking issue for a merged agent-management performance improvement that adds typed conversation update events so subscribers can avoid unnecessary list rebuilds..

Triage

This is an internal tracking issue for PR #9864, which is merged and explicitly closes #10076. The change is best classified as an agent-management performance enhancement rather than an external bug report.

The underlying problem was that conversation status/update events did not carry enough detail for subscribers to distinguish restoration, same-filter status updates, and filter-bucket-changing status updates. As a result, the Runs/agent management view had to refresh its list on every conversation status event. The merged implementation adds typed update payloads (ConversationStatusUpdate and ConversationUpdateKind) plus previous/new status filter buckets so follow-up view logic can avoid unnecessary rebuilds.

Relevant code paths:

• app/src/ai/blocklist/history_model.rs defines the enriched UpdatedConversationStatus event and emits restore events during conversation restoration.
• app/src/ai/agent/conversation.rs emits changed status updates with the previous status.
• app/src/ai/agent_conversations_model.rs maps history events into typed ConversationUpdated events for agent-management consumers.
• app/src/ai/agent_management/view.rs subscribes to AgentConversationsModelEvent::ConversationUpdated and is the view targeted by the follow-up optimization.
• app/src/ai/agent_conversations_model_tests.rs covers restored updates, filter-bucket transitions, and same-bucket re-emissions.

Related but not a duplicate: #10075 tracks the follow-up PR #9866 that uses these typed events to avoid unnecessary re-renders in the management view.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz