fix(discord): remove channel run timeouts

docs/.generated/config-baseline.sha256

@@ -1,4 +1,4 @@
-8903fd57a58acb9a7c949efc6b4197b249220dcd965420ceb7d884cb45fbc48d  config-baseline.json
-86ad0927d992bc873affb3e20a31c6e3c95b2185a91f46cc8e6262a723a78f7d  config-baseline.core.json
-bb7234c52b0bbf12de2a87fa553ec4e89e13aaba9d0d81cf1370621292da13e9  config-baseline.channel.json
-1f5592bfd141ba1e982ce31763a253c10afb080ab4ea2b6538299b114e29cee1  config-baseline.plugin.json
+ab654d17b4d3520c81de45dbcf96a8ecef35254cfd6df21af170dd2ebe550799  config-baseline.json
+8bc9fda7c1096472beaa416a61043ce51d691d4dcad9ed3e0be46e68bb70b0ce  config-baseline.core.json
+56db8ae09c5573a453b8fb01ac579c5b9d8a69fa3fffff2ba2956e5e2ccb2f99  config-baseline.channel.json
+0dd6583fafae6c9134e46c4cf9bddee9822d6436436dcb1a6dcba6d012962e51  config-baseline.plugin.json

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

@@ -1,2 +1,2 @@
-c65b1aa1fb4cf402b90bedd3614eb5d7c3903ab860856392d1ee2481818a7a22  plugin-sdk-api-baseline.json
-da172742470204044c1542a3bba7f183161e90e742f6865c1c7f822dbdc7a7d6  plugin-sdk-api-baseline.jsonl
+427eb476f48ad368fd7061297727a7634be75612aedef5de91e351ac446553ce  plugin-sdk-api-baseline.json
+6065b278792b4664d31c07ec46f852c3d99c8882adb4b37db3d4f2fe78a74af8  plugin-sdk-api-baseline.jsonl

docs/channels/discord.md

@@ -1090,26 +1090,26 @@ openclaw logs --follow
 
   </Accordion>
 
-  <Accordion title="Long-running handlers time out or duplicate replies">
+  <Accordion title="Long-running Discord turns or duplicate replies">
 
     Typical logs:
 
-    - `Listener DiscordMessageListener timed out after 30000ms for event MESSAGE_CREATE`
     - `Slow listener detected ...`
-    - `discord inbound worker timed out after ...`
+    - `stuck session: sessionKey=agent:...:discord:... state=processing ...`
 
-    Listener budget knob:
+    Carbon gateway queue knobs:
 
     - single-account: `channels.discord.eventQueue.listenerTimeout`
     - multi-account: `channels.discord.accounts.<accountId>.eventQueue.listenerTimeout`
+    - this only controls Carbon gateway listener work, not agent turn lifetime
 
-    Worker run timeout knob:
+    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.
 
-    - single-account: `channels.discord.inboundWorker.runTimeoutMs`
-    - multi-account: `channels.discord.accounts.<accountId>.inboundWorker.runTimeoutMs`
-    - default: `1800000` (30 minutes); set `0` to disable
+    Deprecated compatibility setting:
 
-    Recommended baseline:
+    - `channels.discord.inboundWorker.runTimeoutMs`
+    - `channels.discord.accounts.<accountId>.inboundWorker.runTimeoutMs`
+    - ignored by current Discord message handling
 
 ```json5
 {
@@ -1120,9 +1120,6 @@ openclaw logs --follow
           eventQueue: {
             listenerTimeout: 120000,
           },
-          inboundWorker: {
-            runTimeoutMs: 1800000,
-          },
         },
       },
     },
@@ -1130,9 +1127,6 @@ openclaw logs --follow
 }
 ```
 
-    Use `eventQueue.listenerTimeout` for slow listener setup and `inboundWorker.runTimeoutMs`
-    only if you want a separate safety valve for queued agent turns.
-
   </Accordion>
 
   <Accordion title="Gateway metadata lookup timeout warnings">
@@ -1193,7 +1187,7 @@ 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`
-- inbound worker: `inboundWorker.runTimeoutMs`
+- deprecated compatibility: `inboundWorker.runTimeoutMs` (ignored)
 - gateway metadata: `gatewayInfoTimeoutMs`
 - reply/history: `replyToMode`, `historyLimit`, `dmHistoryLimit`, `dms.*.historyLimit`
 - delivery: `textChunkLimit`, `chunkMode`, `maxLinesPerMessage`