docs: clarify client-side debug prop behavior

Updated JSDoc and troubleshooting docs to accurately describe that
the client-side debug prop forwards config to the AG-UI transport
layer, not CopilotKit's own logging. Removed fabricated console.debug
output examples that don't exist.

Author: jpr5

.claude/docs/architecture.md

@@ -106,7 +106,7 @@ debug: {
 
 **Runtime:** Agent run started, SSE stream opened/completed/errored, every AG-UI event emitted (with Pino structured logger).
 
-**Client:** SSE events received, event validation, chunk transformation, event verification, subscriber dispatch, run lifecycle. Uses `console.debug` via a centralized `DebugLogger`.
+**Client:** The debug configuration is forwarded to the AG-UI transport layer (`transformChunks`). CopilotKit itself does not currently emit client-side `console.debug` calls — the flag configures the underlying AG-UI event pipeline for transport-level debug output.
 
 ### Architecture
 

docs/snippets/shared/troubleshooting/debug-mode.mdx

@@ -62,14 +62,7 @@ Pass `debug={true}` to the `<CopilotKit>` provider:
 </CopilotKit>
 ```
 
-This produces `console.debug` output in the browser devtools, showing the event pipeline at each stage:
-
-```
-[SSE] Event received: { type: "TEXT_MESSAGE_START" }
-[HTTP] Event validated: { type: "TEXT_MESSAGE_START", valid: true }
-[VERIFY] { type: "TEXT_MESSAGE_START" }
-[APPLY] Event applied: { type: "TEXT_MESSAGE_START", subscribers: 2 }
-```
+This forwards the debug configuration to the AG-UI client transport layer (`transformChunks`), which may produce transport-level debug output depending on the AG-UI library version. Note that the richest debug logging comes from the **server-side** `CopilotRuntime` — enable `debug: true` there for full structured Pino logs of every AG-UI event.
 
 <Callout type="info">
   The server and client debug toggles are independent. Enabling debug on the client does not affect the server, and vice versa.
@@ -117,26 +110,21 @@ debug: { events: true, lifecycle: false, verbose: true }
 
 ### Events Not Reaching the Client
 
-Enable debug on both sides:
+Enable debug on the server side for the most detailed visibility:
 1. Check server logs for `Event emitted` — are the expected events being sent?
-2. Check client logs for `[SSE] Event received` — are they arriving?
-3. Check `[HTTP] Event validated` — are any events failing validation?
-4. Check `[VERIFY]` — are events being rejected by the state machine?
-
-### Events Being Dropped
-
-Look for `[APPLY] Event dropped` in the client logs. This means a subscriber called `stopPropagation`, preventing the event from being applied to state.
+2. Verify `SSE stream completed` shows the expected `eventCount`.
+3. Use the browser Network tab to confirm SSE events are arriving over the wire.
 
 ### Tool Calls Not Executing
 
-Enable debug and look for:
+Enable server-side debug and look for:
 1. `TOOL_CALL_START` events being emitted on the server
 2. `TOOL_CALL_ARGS` and `TOOL_CALL_END` events following correctly
-3. The events being validated and applied on the client
+3. Confirm the events appear in the SSE stream via the browser Network tab
 
 ### State Not Updating
 
-Look for `STATE_SNAPSHOT` or `STATE_DELTA` events in both server and client logs. If they appear on the server but not the client, there may be a connection issue. If they appear on the client but state isn't updating, check for `stopPropagation` in the apply stage.
+Look for `STATE_SNAPSHOT` or `STATE_DELTA` events in server logs. If they appear on the server but not in the browser's SSE stream, there may be a connection issue.
 
 ## What Gets Logged
 
@@ -152,18 +140,9 @@ Look for `STATE_SNAPSHOT` or `STATE_DELTA` events in both server and client logs
 
 In **summary mode** (verbose off), event logs include key identifiers like `messageId`, `toolCallId`, `toolCallName`, `role`, and content lengths instead of full payloads.
 
-### Client-Side Logs
-
-Events pass through several pipeline stages. Debug mode logs at each one:
+### Client-Side
 
-| Stage | Prefix | What's Logged |
-|-------|--------|---------------|
-| SSE Parser | `[SSE]` | Raw events received from the server |
-| HTTP Transform | `[HTTP]` | Stream format detection, event validation (valid/invalid) |
-| Chunk Transform | `[TRANSFORM]` | Chunk events expanded into START/CONTENT/END sequences |
-| Event Verification | `[VERIFY]` | Each event passing through the state machine validator |
-| Event Application | `[APPLY]` | Events applied to state, or dropped via `stopPropagation` |
-| Agent Lifecycle | `[LIFECYCLE]` | Run started, finished, or errored |
+On the client, the `debug` configuration is passed through to the AG-UI transport layer. The AG-UI client library controls what (if any) debug output is produced. CopilotKit itself does not emit `console.debug` calls — the debug flag configures the underlying AG-UI event pipeline.
 
 <Callout type="warn">
   Debug mode can produce a large volume of log output, especially in verbose mode. Use it during development and debugging, not in production.

packages/react-core/src/components/copilot-provider/copilotkit-props.tsx

@@ -197,7 +197,11 @@ export interface CopilotKitProps extends Omit<
   enableInspector?: boolean;
 
   /**
-   * Enable debug logging for the client-side event pipeline.
+   * Enable debug logging. On the server (`CopilotRuntime`), this enables
+   * structured Pino logging of the AG-UI event pipeline. On the client,
+   * this configuration is forwarded to the AG-UI transport layer
+   * (`transformChunks`) for transport-level debug output.
+   *
    * Pass `true` for full output, or an object for granular control:
    *
    * ```tsx