[jpalvarezl]

Motivation & Context

ClaudeAgent currently flattens incoming messages into a single prompt without preserving their roles. In multi-agent workflows, this makes user input and previous agents' responses indistinguishable. This change retains role information and explicitly frames the supplied transcript as conversation history for the receiving agent's assigned task.

Description & Review Guide

• What are the major changes? Update _format_prompt() to prepend a conversation-history explanation and label each message with its role, while leaving a single user message unchanged. Add regression coverage for mixed-role history, messages from named and unnamed agents, and a single assistant message. Add a documented SequentialBuilder sample that passes a grammar inspector's output to a second Claude agent. Broaden the function_invocation_kwargs and client_kwargs annotations from dict to Mapping in the run() signatures.
• What is the impact of these changes? Claude receives explicit role boundaries instead of undifferentiated text. The transcript is still sent as one SDK user message; this does not introduce native multi-role history replay or shared Claude sessions. Labels preserve message roles, not individual agent names. Existing single-user-message behavior remains unchanged.
• What do you want reviewers to focus on? Whether the transcript framing clearly distinguishes supplied history from the receiving agent's instructions, whether the formatting coverage captures agent-to-agent handoff scenarios, and whether the sequential sample demonstrates the intended behavior.

Related Issue

Fixes microsoft#7894

This overlaps with microsoft#7895, which also introduces role labels. This PR additionally provides explicit conversation-history framing, broader formatting coverage, a sequential-agent sample, and the Mapping annotation updates.

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR is linked to an issue, and the overlapping open PR and differences are explained in Related Issue above.
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.