[Naveen Chatlapalli (1aifanatic)]

Motivation & Context

Three docstring examples in core fail when run:

• BaseChatClient custom client declares async def _inner_get_response. The method must return an awaitable or a ResponseStream, but an async def always returns a coroutine. So the example's own async for update in client.get_response(..., stream=True) raises TypeError: 'async for' requires an object with __aiter__ method, got coroutine. Its streaming update also passes a dict as content.
• WorkflowBuilder.add_fan_in_edges starts at prod_1 and never connects prod_2, so build() raises GraphConnectivityError: ... unreachable from the start executor 'prod_1': ['prod_2'].
• Executor has three blocks with comment-only handler bodies, which isn't valid Python. The prose line after each block also has no blank line, so it isn't separated from the block.

Description & Review Guide

• What are the major changes? Docstring examples only:
  • The custom client follows samples/02-agents/chat_client/custom_chat_client.py: a plain def that returns a ResponseStream when stream is True, or a coroutine otherwise, with Content.from_text.
  • The fan-in example adds a Dispatcher start executor that fans out to both producers.
  • The Executor blocks get ... bodies and blank lines.
• What is the impact of these changes? Documentation only.
• What do you want reviewers to focus on? Nothing in particular.

I ran the fixed examples. The client returns Hello! both with and without streaming. The fan-in workflow runs and outputs Combined: result_7, result_7. The three Executor blocks compile. test_docstrings.py passes.

Related Issue

N/A - trivial change: docstring examples are corrected so they run, with no behavior change.

AI Assistance

• No material AI assistance was used.
• This is an AI-assisted contribution. I reviewed, understood, and verified all submitted content and accept responsibility for it.

AI assistance details: Claude Code helped find the failing examples by executing docstring code blocks against a stub client, fix them, re-run them, and draft this description.

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 links to an agreed issue with no competing open PR, or the Related Issue section documents a trivial-change or repository-automation exception.
• 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.

🤖 Generated with Claude Code

[Copilot]

🟢 Approval recommended

No active review issues are reported for the docstring example updates.

No open issues 🎉

What changed in this PR

This PR corrects Python core docstring examples for custom chat clients and workflows without changing runtime behavior.

Changes:

• Updates the custom client example to return a ResponseStream for streaming and a coroutine otherwise, using Content.from_text for streaming content.
• Adds a dispatcher so both producers in the fan-in example are reachable.
• Adds valid placeholder bodies and separates following prose in three executor examples.

File	Description
python/​packages/​core/​agent_framework/​_workflows/​_workflow_builder.py	Connects both fan-in producers through a dispatcher.
python/​packages/​core/​agent_framework/​_workflows/​_executor.py	Fixes syntax and prose spacing in handler examples.
python/​packages/​core/​agent_framework/​_clients.py	Corrects custom client response handling and streaming content.

_{Review effort: Balanced}