Convert callout syntax to GitHub-flavored alerts

Convert 27 callouts across 15 files from bold-text style
(> **Note:**) to GitHub alert syntax (> [!NOTE]).

Language-qualified tips (e.g., > **Tip (Python / Go):**) preserve
the qualifier as bold text in the alert body.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: sunbrye

docs/auth/byok.md

@@ -293,7 +293,8 @@ provider: {
 }
 ```
 
-> **Note:** Foundry Local starts on a **dynamic port** — the port is not fixed. Use `foundry service status` to confirm the port the service is currently listening on, then use that port in your `baseUrl`.
+> [!NOTE]
+> Foundry Local starts on a **dynamic port** — the port is not fixed. Use `foundry service status` to confirm the port the service is currently listening on, then use that port in your `baseUrl`.
 
 To get started with Foundry Local:
 
@@ -334,7 +335,8 @@ provider: {
 }
 ```
 
-> **Note:** The `bearerToken` option accepts a **static token string** only. The SDK does not refresh this token automatically. If your token expires, requests will fail and you'll need to create a new session with a fresh token.
+> [!NOTE]
+> The `bearerToken` option accepts a **static token string** only. The SDK does not refresh this token automatically. If your token expires, requests will fail and you'll need to create a new session with a fresh token.
 
 ## Custom model listing
 

docs/features/custom-agents.md

@@ -254,7 +254,8 @@ try (var client = new CopilotClient()) {
 | `infer` | `boolean` | | Whether the runtime can auto-select this agent (default: `true`) |
 | `skills` | `string[]` | | Skill names to preload into the agent's context at startup |
 
-> **Tip:** A good `description` helps the runtime match user intent to the right agent. Be specific about the agent's expertise and capabilities.
+> [!TIP]
+> A good `description` helps the runtime match user intent to the right agent. Be specific about the agent's expertise and capabilities.
 
 In addition to per-agent configuration above, you can set `agent` on the **session config** itself to pre-select which custom agent is active when the session starts. See [Selecting an Agent at Session Creation](#selecting-an-agent-at-session-creation) below.
 
@@ -757,7 +758,8 @@ const session = await client.createSession({
 });
 ```
 
-> **Note:** When `tools` is `null` or omitted, the agent inherits access to all tools configured on the session. Use explicit tool lists to enforce the principle of least privilege.
+> [!NOTE]
+> When `tools` is `null` or omitted, the agent inherits access to all tools configured on the session. Use explicit tool lists to enforce the principle of least privilege.
 
 ## Agent-exclusive tools
 
@@ -905,7 +907,8 @@ Precedence:
 1. Session-level `availableTools`/`excludedTools` are applied first (globally)
 2. `defaultAgent.excludedTools` is applied on top, further restricting the main agent only
 
-> **Note:** If a tool is in both `excludedTools` (session-level) and `defaultAgent.excludedTools`, the session-level exclusion takes precedence — the tool is unavailable to everyone.
+> [!NOTE]
+> If a tool is in both `excludedTools` (session-level) and `defaultAgent.excludedTools`, the session-level exclusion takes precedence — the tool is unavailable to everyone.
 
 ## Attaching MCP servers to agents
 

docs/features/hooks.md

@@ -223,7 +223,8 @@ try (var client = new CopilotClient()) {
 
 </details>
 
-> **Tip:** Every hook handler receives an `invocation` parameter containing the `sessionId`, which is useful for correlating logs and maintaining per-session state.
+> [!TIP]
+> Every hook handler receives an `invocation` parameter containing the `sessionId`, which is useful for correlating logs and maintaining per-session state.
 
 ---
 

docs/features/mcp.md

@@ -2,7 +2,8 @@
 
 The Copilot SDK can integrate with **MCP servers** (Model Context Protocol) to extend the assistant's capabilities with external tools. MCP servers run as separate processes and expose tools (functions) that Copilot can invoke during conversations.
 
-> **Note:** This is an evolving feature. See [issue #36](https://github.com/github/copilot-sdk/issues/36) for ongoing discussion.
+> [!NOTE]
+> This is an evolving feature. See [issue #36](https://github.com/github/copilot-sdk/issues/36) for ongoing discussion.
 
 ## What is MCP?
 
@@ -240,7 +241,8 @@ and subdirectories including temporary system files, log files, and
 directories for different applications.
 ```
 
-> **Tip:** You can use any MCP server from the [MCP Servers Directory](https://github.com/modelcontextprotocol/servers). Popular options include `@modelcontextprotocol/server-github`, `@modelcontextprotocol/server-sqlite`, and `@modelcontextprotocol/server-puppeteer`.
+> [!TIP]
+> You can use any MCP server from the [MCP Servers Directory](https://github.com/modelcontextprotocol/servers). Popular options include `@modelcontextprotocol/server-github`, `@modelcontextprotocol/server-sqlite`, and `@modelcontextprotocol/server-puppeteer`.
 
 ## Configuration options
 

docs/features/session-persistence.md

@@ -418,7 +418,8 @@ Each SDK also provides idiomatic automatic cleanup patterns:
 | **C#** | `IAsyncDisposable` | `await using var session = await client.CreateSessionAsync(config);` |
 | **Go** | `defer` | `defer session.Disconnect()` |
 
-> **Note:** `destroy()` is deprecated in favor of `disconnect()`. Existing code using `destroy()` will continue to work but should be migrated.
+> [!NOTE]
+> `destroy()` is deprecated in favor of `disconnect()`. Existing code using `destroy()` will continue to work but should be migrated.
 
 ### Permanently deleting a session (`deleteSession`)
 
@@ -443,7 +444,8 @@ const client = new CopilotClient({
 
 When a timeout is configured, sessions without activity for that duration are automatically cleaned up. Set to `0` or omit to disable.
 
-> **Note:** This option only applies when the SDK spawns the runtime process. When connecting to an existing server via `cliUrl`, the server's own timeout configuration applies.
+> [!NOTE]
+> This option only applies when the SDK spawns the runtime process. When connecting to an existing server via `cliUrl`, the server's own timeout configuration applies.
 
 ```mermaid
 flowchart LR
@@ -572,7 +574,8 @@ const session = await client.createSession({
 });
 ```
 
-> **Note:** Thresholds are context utilization ratios (0.0-1.0), not absolute token counts. See the [Compatibility Guide](../troubleshooting/compatibility.md) for details.
+> [!NOTE]
+> Thresholds are context utilization ratios (0.0-1.0), not absolute token counts. See the [Compatibility Guide](../troubleshooting/compatibility.md) for details.
 
 ## Limitations and considerations
 

docs/features/skills.md

@@ -378,7 +378,8 @@ const session = await client.createSession({
     onPermissionRequest: async () => ({ kind: "approved" }),
 });
 ```
-> **Note:** Skills are opt-in — when `skills` is omitted, no skill content is injected. Sub-agents do not inherit skills from the parent; you must list them explicitly per agent.
+> [!NOTE]
+> Skills are opt-in — when `skills` is omitted, no skill content is injected. Sub-agents do not inherit skills from the parent; you must list them explicitly per agent.
 
 ### Skills + MCP servers
 

docs/features/steering-and-queueing.md

@@ -217,7 +217,8 @@ try (var client = new CopilotClient()) {
 3. The agent sees the steering message as a new user message and adjusts its response
 4. If the turn completes before the steering message is processed, it is automatically moved to the regular queue for the next turn
 
-> **Note:** Steering messages are best-effort within the current turn. If the agent has already committed to a tool call, the steering takes effect after that call completes but still within the same turn.
+> [!NOTE]
+> Steering messages are best-effort within the current turn. If the agent has already committed to a tool call, the steering takes effect after that call completes but still within the same turn.
 
 ## Queueing (enqueue mode)
 
@@ -624,7 +625,8 @@ class InteractiveChat {
 | `"enqueue"` | Queue for next turn | Waits in FIFO queue | Starts a new turn immediately |
 | `"immediate"` | Inject into current turn | Injected before next LLM call | Starts a new turn immediately |
 
-> **Note:** When the session is idle (not processing), both modes behave identically — the message starts a new turn immediately.
+> [!NOTE]
+> When the session is idle (not processing), both modes behave identically — the message starts a new turn immediately.
 
 ## Best practices
 

docs/features/streaming-events.md

@@ -206,11 +206,14 @@ session.on(AssistantMessageDeltaEvent.class, event ->
 
 </details>
 
-> **Tip (Python / Go):** These SDKs use a single `Data` class/struct with all possible fields as optional/nullable. Only the fields listed in the tables below are populated for each event type — the rest will be `None` / `nil`.
+> [!TIP]
+> **(Python / Go)** These SDKs use a single `Data` class/struct with all possible fields as optional/nullable. Only the fields listed in the tables below are populated for each event type — the rest will be `None` / `nil`.
 >
-> **Tip (.NET):** The .NET SDK uses separate, strongly-typed data classes per event (e.g., `AssistantMessageDeltaData`), so only the relevant fields exist on each type.
+> [!TIP]
+> **(.NET)** The .NET SDK uses separate, strongly-typed data classes per event (e.g., `AssistantMessageDeltaData`), so only the relevant fields exist on each type.
 >
-> **Tip (TypeScript):** The TypeScript SDK uses a discriminated union — when you match on `event.type`, the `data` payload is automatically narrowed to the correct shape.
+> [!TIP]
+> **(TypeScript)** The TypeScript SDK uses a discriminated union — when you match on `event.type`, the `data` payload is automatically narrowed to the correct shape.
 
 ---
 

docs/getting-started.md

@@ -1543,7 +1543,8 @@ const session = await client.createSession({
 });
 ```
 
-> **Tip:** You can also set `agent: "pr-reviewer"` in the session config to pre-select this agent from the start. See the [Custom Agents guide](./features/custom-agents.md#selecting-an-agent-at-session-creation) for details.
+> [!TIP]
+> You can also set `agent: "pr-reviewer"` in the session config to pre-select this agent from the start. See the [Custom Agents guide](./features/custom-agents.md#selecting-an-agent-at-session-creation) for details.
 
 ### Customize the system message
 
@@ -1606,7 +1607,8 @@ By default the headless server only accepts connections from loopback (`127.0.0.
 copilot --headless --host 0.0.0.0 --port 4321
 ```
 
-> **Warning:** Exposing the headless server on a non-loopback address makes it reachable by anyone who can route to that address. Pair it with network controls (firewall, private network, reverse proxy) and authentication appropriate for your environment.
+> [!WARNING]
+> Exposing the headless server on a non-loopback address makes it reachable by anyone who can route to that address. Pair it with network controls (firewall, private network, reverse proxy) and authentication appropriate for your environment.
 
 ### Connecting the SDK to the external server
 

docs/integrations/microsoft-agent-framework.md

@@ -13,7 +13,8 @@ The Microsoft Agent Framework is the unified successor to Semantic Kernel and Au
 | **Orchestrator** | A MAF component that coordinates agents in sequential, concurrent, or handoff workflows |
 | **A2A protocol** | Agent-to-Agent communication standard supported by the framework |
 
-> **Note:** MAF integration packages are available for **.NET** and **Python**. For TypeScript, Go, and Java, use the Copilot SDK directly — the standard SDK APIs already provide tool calling, streaming, and custom agents.
+> [!NOTE]
+> MAF integration packages are available for **.NET** and **Python**. For TypeScript, Go, and Java, use the Copilot SDK directly — the standard SDK APIs already provide tool calling, streaming, and custom agents.
 
 ## Prerequisites
 
@@ -49,7 +50,8 @@ pip install copilot-sdk agent-framework-github-copilot
 <details>
 <summary><strong>Java</strong></summary>
 
-> **Note:** The Java SDK does not have a dedicated MAF integration package. Use the standard Copilot SDK directly — it provides tool calling, streaming, and custom agents out of the box.
+> [!NOTE]
+> The Java SDK does not have a dedicated MAF integration package. Use the standard Copilot SDK directly — it provides tool calling, streaming, and custom agents out of the box.
 
 ```xml
 <!-- Maven -->