refactor(discord): share channel run queue

docs/.generated/config-baseline.sha256

@@ -1,4 +1,4 @@
-ab654d17b4d3520c81de45dbcf96a8ecef35254cfd6df21af170dd2ebe550799  config-baseline.json
+6a67688ac174403c996027d90fa16eabb9aeff6a8af890b17d4628910c3b440f  config-baseline.json
 8bc9fda7c1096472beaa416a61043ce51d691d4dcad9ed3e0be46e68bb70b0ce  config-baseline.core.json
-56db8ae09c5573a453b8fb01ac579c5b9d8a69fa3fffff2ba2956e5e2ccb2f99  config-baseline.channel.json
+9f5fad66a49fa618d64a963470aa69fed9fe4b4639cc4321f9ec04bfb2f8aa50  config-baseline.channel.json
 0dd6583fafae6c9134e46c4cf9bddee9822d6436436dcb1a6dcba6d012962e51  config-baseline.plugin.json

docs/.generated/plugin-sdk-api-baseline.sha256

@@ -1,2 +1,2 @@
-427eb476f48ad368fd7061297727a7634be75612aedef5de91e351ac446553ce  plugin-sdk-api-baseline.json
-6065b278792b4664d31c07ec46f852c3d99c8882adb4b37db3d4f2fe78a74af8  plugin-sdk-api-baseline.jsonl
+eedcf9070e222077f618d68510c909b571dc51fbb030284ff3b30728719f7ae0  plugin-sdk-api-baseline.json
+02043e1f48a15625580ed1e1ec569ccd1c7c9ad393be2aa54a1fa36afeeca7b5  plugin-sdk-api-baseline.jsonl

docs/channels/discord.md

@@ -1105,12 +1105,6 @@ openclaw logs --follow
 
     Discord does not apply a channel-owned timeout to queued agent turns. Message listeners hand off immediately, and queued Discord runs preserve per-session ordering until the session/tool/runtime lifecycle completes or aborts the work.
 
-    Deprecated compatibility setting:
-
-    - `channels.discord.inboundWorker.runTimeoutMs`
-    - `channels.discord.accounts.<accountId>.inboundWorker.runTimeoutMs`
-    - ignored by current Discord message handling
-
 ```json5
 {
   channels: {
@@ -1187,7 +1181,6 @@ Primary reference: [Configuration reference - Discord](/gateway/config-channels#
 - policy: `groupPolicy`, `dm.*`, `guilds.*`, `guilds.*.channels.*`
 - command: `commands.native`, `commands.useAccessGroups`, `configWrites`, `slashCommand.*`
 - event queue: `eventQueue.listenerTimeout` (listener budget), `eventQueue.maxQueueSize`, `eventQueue.maxConcurrency`
-- deprecated compatibility: `inboundWorker.runTimeoutMs` (ignored)
 - gateway metadata: `gatewayInfoTimeoutMs`
 - reply/history: `replyToMode`, `historyLimit`, `dmHistoryLimit`, `dms.*.historyLimit`
 - delivery: `textChunkLimit`, `chunkMode`, `maxLinesPerMessage`

docs/concepts/messages.md

@@ -128,6 +128,14 @@ current run, or collected for a followup turn.
 
 Details: [Queueing](/concepts/queue).
 
+## Channel run ownership
+
+Channel plugins may preserve ordering, debounce input, and apply transport
+backpressure before a message enters the session queue. They should not impose a
+separate timeout around the agent turn itself. Once a message is routed to a
+session, long-running work is governed by the session, tool, and runtime
+lifecycle so all channels report and recover from slow turns consistently.
+
 ## Streaming, chunking, and batching
 
 Block streaming sends partial replies as the model produces text blocks.

docs/plugins/sdk-subpaths.md

@@ -64,7 +64,7 @@ For the plugin authoring guide, see [Plugin SDK overview](/plugins/sdk-overview)
     | `plugin-sdk/telegram-command-config` | Telegram custom-command normalization/validation helpers with bundled-contract fallback |
     | `plugin-sdk/command-gating` | Narrow command authorization gate helpers |
     | `plugin-sdk/channel-policy` | `resolveChannelGroupRequireMention` |
-    | `plugin-sdk/channel-lifecycle` | `createAccountStatusSink`, draft stream lifecycle/finalization helpers |
+    | `plugin-sdk/channel-lifecycle` | `createAccountStatusSink`, `createChannelRunQueue`, draft stream lifecycle/finalization helpers |
     | `plugin-sdk/inbound-envelope` | Shared inbound route + envelope builder helpers |
     | `plugin-sdk/inbound-reply-dispatch` | Shared inbound record-and-dispatch helpers |
     | `plugin-sdk/messaging-targets` | Target parsing/matching helpers |