Unclear The finding describes the new component structure but not what the expand/collapse behavior looks like or does for a user.
What
Several message-rendering components in the transcript view — task messages, user-channel messages, cross-session messages, and inbound/task-notification messages — now receive isExpanded, messageId, and origin props they didn't take before. New render functions support these props along with verbose and taskDelivery, and an existing inbound-message renderer was refactored to delegate to one of them. A single expanded/collapsed value is now computed once per render and passed through consistently to all of these components.
Why This lets any message in the transcript be expanded or collapsed consistently, regardless of what kind of message it is or where it came from.
The finding describes the new component structure but not what the expand/collapse behavior looks like or does for a user.