docs: consolidate pytest-examples into single test and add skip tags

Consolidate the separate README.v2.md and docs/ pytest-examples tests
into a single unified test using `find_examples("README.v2.md", "docs/")`.

Add skip tags to pre-existing code blocks that aren't self-contained:
- migration.md: all blocks (before/after migration patterns)
- experimental/*.md: all blocks (experimental API patterns)
- testing.md: test blocks (reference local server module)
- README.v2.md: 4 context-dependent snippets

Author: Kludex

README.v2.md

@@ -595,7 +595,7 @@ _Full example: [examples/snippets/servers/basic_prompt.py](https://github.com/mo
 
 MCP servers can provide icons for UI display. Icons can be added to the server implementation, tools, resources, and prompts:
 
-```python
+```python skip-run="true"
 from mcp.server.mcpserver import MCPServer, Icon
 
 # Create an icon from a file path or URL
@@ -1079,7 +1079,7 @@ The MCPServer server instance accessible via `ctx.mcp_server` provides access to
   - `stateless_http` - Whether the server operates in stateless mode
   - And other configuration options
 
-```python
+```python skip-run="true"
 @mcp.tool()
 def server_info(ctx: Context) -> dict:
     """Get information about the current server."""
@@ -1106,7 +1106,7 @@ The session object accessible via `ctx.session` provides advanced control over c
 - `await ctx.session.send_tool_list_changed()` - Notify clients that the tool list changed
 - `await ctx.session.send_prompt_list_changed()` - Notify clients that the prompt list changed
 
-```python
+```python skip-run="true"
 @mcp.tool()
 async def notify_data_update(resource_uri: str, ctx: Context) -> str:
     """Update data and notify clients of the change."""
@@ -1134,7 +1134,7 @@ The request context accessible via `ctx.request_context` contains request-specif
 - `ctx.request_context.request` - The original MCP request object for advanced processing
 - `ctx.request_context.request_id` - Unique identifier for this request
 
-```python
+```python skip-run="true"
 # Example with typed lifespan context
 @dataclass
 class AppContext:

docs/experimental/index.md

@@ -26,7 +26,7 @@ Tasks are useful for:
 
 Experimental features are accessed via the `.experimental` property:
 
-```python
+```python skip="true"
 # Server-side
 @server.experimental.get_task()
 async def handle_get_task(request: GetTaskRequest) -> GetTaskResult:

docs/experimental/tasks-client.md

@@ -10,7 +10,7 @@ This guide covers calling task-augmented tools from clients, handling the `input
 
 Call a tool as a task and poll for the result:
 
-```python
+```python skip="true"
 from mcp.client.session import ClientSession
 from mcp.types import CallToolResult
 
@@ -38,7 +38,7 @@ async with ClientSession(read, write) as session:
 
 Use `call_tool_as_task()` to invoke a tool with task augmentation:
 
-```python
+```python skip="true"
 result = await session.experimental.call_tool_as_task(
     "my_tool",           # Tool name
     {"arg": "value"},    # Arguments
@@ -62,7 +62,7 @@ The response is a `CreateTaskResult` containing:
 
 The `poll_task()` async iterator polls until the task reaches a terminal state:
 
-```python
+```python skip="true"
 async for status in session.experimental.poll_task(task_id):
     print(f"Status: {status.status}")
     if status.statusMessage:
@@ -79,7 +79,7 @@ It automatically:
 
 When a task needs user input (elicitation), it transitions to `input_required`. You must call `get_task_result()` to receive and respond to the elicitation:
 
-```python
+```python skip="true"
 async for status in session.experimental.poll_task(task_id):
     print(f"Status: {status.status}")
 
@@ -95,7 +95,7 @@ The elicitation callback (set during session creation) handles the actual user i
 
 To handle elicitation requests from the server, provide a callback when creating the session:
 
-```python
+```python skip="true"
 from mcp.types import ElicitRequestParams, ElicitResult
 
 async def handle_elicitation(context, params: ElicitRequestParams) -> ElicitResult:
@@ -124,7 +124,7 @@ async with ClientSession(
 
 Similarly, handle sampling requests with a callback:
 
-```python
+```python skip="true"
 from mcp.types import CreateMessageRequestParams, CreateMessageResult, TextContent
 
 async def handle_sampling(context, params: CreateMessageRequestParams) -> CreateMessageResult:
@@ -150,7 +150,7 @@ async with ClientSession(
 
 Once a task completes, retrieve the result:
 
-```python
+```python skip="true"
 if status.status == "completed":
     result = await session.experimental.get_task_result(task_id, CallToolResult)
     for content in result.content:
@@ -174,7 +174,7 @@ The result type matches the original request:
 
 Cancel a running task:
 
-```python
+```python skip="true"
 cancel_result = await session.experimental.cancel_task(task_id)
 print(f"Cancelled, status: {cancel_result.status}")
 ```
@@ -185,7 +185,7 @@ Note: Cancellation is cooperative—the server must check for and handle cancell
 
 View all tasks on the server:
 
-```python
+```python skip="true"
 result = await session.experimental.list_tasks()
 for task in result.tasks:
     print(f"{task.taskId}: {task.status}")
@@ -205,7 +205,7 @@ Servers can send task-augmented requests to clients. This is useful when the ser
 
 Register task handlers to declare what task-augmented requests your client accepts:
 
-```python
+```python skip="true"
 from mcp.client.experimental.task_handlers import ExperimentalTaskHandlers
 from mcp.types import (
     CreateTaskResult, GetTaskResult, GetTaskPayloadResult,
@@ -279,7 +279,7 @@ This enables flows where:
 
 A client that handles all task scenarios:
 
-```python
+```python skip="true"
 import anyio
 from mcp.client.session import ClientSession
 from mcp.client.stdio import stdio_client
@@ -336,7 +336,7 @@ if __name__ == "__main__":
 
 Handle task errors gracefully:
 
-```python
+```python skip="true"
 from mcp.shared.exceptions import MCPError
 
 try:

docs/experimental/tasks-server.md

@@ -10,7 +10,7 @@ This guide covers implementing task support in MCP servers, from basic setup to
 
 The simplest way to add task support:
 
-```python
+```python skip="true"
 from mcp.server import Server
 from mcp.server.experimental.task_context import ServerTaskContext
 from mcp.types import CallToolResult, CreateTaskResult, TextContent, Tool, ToolExecution, TASK_REQUIRED
@@ -57,7 +57,7 @@ That's it. `enable_tasks()` automatically:
 
 Tools declare task support via the `execution.taskSupport` field:
 
-```python
+```python skip="true"
 from mcp.types import Tool, ToolExecution, TASK_REQUIRED, TASK_OPTIONAL, TASK_FORBIDDEN
 
 Tool(
@@ -75,7 +75,7 @@ Tool(
 
 Validate the request matches your tool's requirements:
 
-```python
+```python skip="true"
 @server.call_tool()
 async def handle_tool(name: str, arguments: dict):
     ctx = server.request_context
@@ -95,7 +95,7 @@ async def handle_tool(name: str, arguments: dict):
 
 `run_task()` is the recommended way to execute task work:
 
-```python
+```python skip="true"
 async def handle_my_tool(arguments: dict) -> CreateTaskResult:
     ctx = server.request_context
     ctx.experimental.validate_task_mode(TASK_REQUIRED)
@@ -127,7 +127,7 @@ async def handle_my_tool(arguments: dict) -> CreateTaskResult:
 
 Keep clients informed of progress:
 
-```python
+```python skip="true"
 async def work(task: ServerTaskContext) -> CallToolResult:
     await task.update_status("Starting...")
 
@@ -149,7 +149,7 @@ Tasks can request user input via elicitation. This transitions the task to `inpu
 
 Collect structured data from the user:
 
-```python
+```python skip="true"
 async def work(task: ServerTaskContext) -> CallToolResult:
     await task.update_status("Waiting for confirmation...")
 
@@ -177,7 +177,7 @@ async def work(task: ServerTaskContext) -> CallToolResult:
 
 Direct users to external URLs for OAuth, payments, or other out-of-band flows:
 
-```python
+```python skip="true"
 async def work(task: ServerTaskContext) -> CallToolResult:
     await task.update_status("Waiting for OAuth...")
 
@@ -198,7 +198,7 @@ async def work(task: ServerTaskContext) -> CallToolResult:
 
 Tasks can request LLM completions from the client:
 
-```python
+```python skip="true"
 from mcp.types import SamplingMessage, TextContent
 
 async def work(task: ServerTaskContext) -> CallToolResult:
@@ -220,7 +220,7 @@ async def work(task: ServerTaskContext) -> CallToolResult:
 
 Sampling supports additional parameters:
 
-```python
+```python skip="true"
 result = await task.create_message(
     messages=[...],
     max_tokens=500,
@@ -235,7 +235,7 @@ result = await task.create_message(
 
 Check for cancellation in long-running work:
 
-```python
+```python skip="true"
 async def work(task: ServerTaskContext) -> CallToolResult:
     for i in range(1000):
         if task.is_cancelled:
@@ -254,7 +254,7 @@ The SDK's default cancel handler updates the task status. Your work function sho
 
 For production, implement `TaskStore` with persistent storage:
 
-```python
+```python skip="true"
 from mcp.shared.experimental.tasks.store import TaskStore
 from mcp.types import Task, TaskMetadata, Result
 
@@ -287,7 +287,7 @@ class RedisTaskStore(TaskStore):
 
 Use your custom store:
 
-```python
+```python skip="true"
 store = RedisTaskStore(redis_client)
 server.experimental.enable_tasks(store=store)
 ```
@@ -296,7 +296,7 @@ server.experimental.enable_tasks(store=store)
 
 A server with multiple task-supporting tools:
 
-```python
+```python skip="true"
 from mcp.server import Server
 from mcp.server.experimental.task_context import ServerTaskContext
 from mcp.types import (
@@ -382,7 +382,7 @@ async def handle_tool(name: str, arguments: dict) -> CallToolResult | CreateTask
 
 Tasks handle errors automatically, but you can also fail explicitly:
 
-```python
+```python skip="true"
 async def work(task: ServerTaskContext) -> CallToolResult:
     try:
         result = await risky_operation()
@@ -407,7 +407,7 @@ For custom error messages, call `task.fail()` before raising.
 
 For web applications, use the Streamable HTTP transport:
 
-```python
+```python skip="true"
 from collections.abc import AsyncIterator
 from contextlib import asynccontextmanager
 
@@ -484,7 +484,7 @@ if __name__ == "__main__":
 
 Test task functionality with the SDK's testing utilities:
 
-```python
+```python skip="true"
 import pytest
 import anyio
 from mcp.client.session import ClientSession
@@ -530,7 +530,7 @@ async def test_task_tool():
 
 ### Keep Work Functions Focused
 
-```python
+```python skip="true"
 # Good: focused work function
 async def work(task: ServerTaskContext) -> CallToolResult:
     await task.update_status("Validating...")
@@ -544,7 +544,7 @@ async def work(task: ServerTaskContext) -> CallToolResult:
 
 ### Check Cancellation in Loops
 
-```python
+```python skip="true"
 async def work(task: ServerTaskContext) -> CallToolResult:
     results = []
     for item in large_dataset:
@@ -558,7 +558,7 @@ async def work(task: ServerTaskContext) -> CallToolResult:
 
 ### Use Meaningful Status Messages
 
-```python
+```python skip="true"
 async def work(task: ServerTaskContext) -> CallToolResult:
     await task.update_status("Connecting to database...")
     db = await connect()
@@ -575,7 +575,7 @@ async def work(task: ServerTaskContext) -> CallToolResult:
 
 ### Handle Elicitation Responses
 
-```python
+```python skip="true"
 async def work(task: ServerTaskContext) -> CallToolResult:
     result = await task.elicit(message="Continue?", requestedSchema={...})
 

docs/experimental/tasks.md

@@ -101,7 +101,7 @@ Server                              Client
 
 When augmenting a request with task execution, include `TaskMetadata`:
 
-```python
+```python skip="true"
 from mcp.types import TaskMetadata
 
 task = TaskMetadata(ttl=60000)  # TTL in milliseconds
@@ -113,7 +113,7 @@ The `ttl` (time-to-live) specifies how long the task and result are retained aft
 
 Servers persist task state in a `TaskStore`. The SDK provides `InMemoryTaskStore` for development:
 
-```python
+```python skip="true"
 from mcp.shared.experimental.tasks import InMemoryTaskStore
 
 store = InMemoryTaskStore()
@@ -140,7 +140,7 @@ The SDK manages these automatically when you enable task support.
 
 **Server** (simplified API):
 
-```python
+```python skip="true"
 from mcp.server import Server
 from mcp.server.experimental.task_context import ServerTaskContext
 from mcp.types import CallToolResult, TextContent, TASK_REQUIRED
@@ -163,7 +163,7 @@ async def handle_tool(name: str, arguments: dict):
 
 **Client:**
 
-```python
+```python skip="true"
 from mcp.client.session import ClientSession
 from mcp.types import CallToolResult