refactor(trigger): share automation turn delivery

docs/chat-commands.md

@@ -78,17 +78,18 @@ nanobot trigger trg_8K4P2Q9X "Review PR #4502"
 Replace `"Review PR #4502"` with the message you want nanobot to receive. The
 trigger is bound to the session where it was created, so the message goes back
 to that same chat. Keep `nanobot gateway` running so trigger messages can be
-delivered. The trigger message starts an automation turn; it is not shown in
-the chat as a normal user message. If that session is already running a turn,
-the trigger waits until the session is idle instead of being injected into the
-active turn.
+delivered. The trigger message starts an automation turn recorded in that
+session with the message you passed to the CLI; it is not treated as a normal
+user message. If that session is already running a turn, the trigger waits
+until the session is idle instead of being injected into the active turn.
 
 Trigger deliveries are stored in the workspace until their linked agent turn
 finishes successfully. If the gateway exits after claiming a delivery but before
 the turn completes, the next gateway start requeues that delivery. This is an
 at-least-once local queue: a delivery may run more than once if the process
 exits at the wrong time, so external scripts should make repeated trigger
-messages safe.
+messages safe. If the delivery reaches the agent and the agent turn fails, the
+delivery is marked failed in Automations instead of retrying forever.
 
 For longer or generated content, omit the message argument and pipe stdin:
 

docs/cli-reference.md

@@ -133,7 +133,8 @@ nanobot trigger trg_8K4P2Q9X "Review PR #4502"
 ```
 
 Keep `nanobot gateway` running so the message can be delivered to the linked
-chat/session.
+chat/session. The message is recorded as an automation turn in that session,
+not as a normal chat message typed by the user.
 
 The command writes to a workspace-local durable queue. If `nanobot gateway` is
 not running yet, the message waits in that workspace. If the target session is
@@ -141,8 +142,9 @@ already running a turn, the trigger waits for that session to become idle. If th
 gateway exits after claiming a delivery but before the linked turn completes,
 the next gateway start requeues that delivery. The queue is at-least-once, not
 exactly-once, so the same message can be delivered again after an interrupted
-process. Run one gateway consumer per workspace; this local queue is not a
-distributed multi-consumer queue.
+process. If the agent receives the delivery and the turn fails, the delivery is
+marked failed instead of retried indefinitely. Run one gateway consumer per
+workspace; this local queue is not a distributed multi-consumer queue.
 
 Use stdin when another local process generates the message:
 

docs/concepts.md

@@ -150,8 +150,10 @@ nanobot to respond in that session. Webhook servers, third-party auth, and
 event-to-message formatting stay outside nanobot. Trigger deliveries are stored
 in the workspace until the linked agent turn finishes successfully. If the
 target session is busy, the trigger waits until that session is idle instead of
-being injected into the active turn. Delivery is at-least-once, so external
-systems should tolerate repeated trigger messages.
+being injected into the active turn. The message is recorded as an automation
+turn in that session. Delivery is at-least-once, so external systems should
+tolerate repeated trigger messages; a delivery that reaches the agent but fails
+is marked failed rather than retried forever.
 
 ## Where to Go Next
 

docs/webui.md

@@ -137,7 +137,9 @@ restarts and are requeued if the process exits before the linked turn completes.
 If the linked session is already running a turn, the local trigger waits until
 that session is idle instead of being injected into the active turn. This is an
 at-least-once local queue, so repeated delivery is possible after an interrupted
-process.
+process. A delivered trigger is recorded as an automation turn in the linked
+session; if the agent receives it but the turn fails, Automations marks the run
+failed instead of retrying indefinitely.
 
 For recurring background checks that should stay quiet unless there is something
 useful to report, use the protected heartbeat job by editing `HEARTBEAT.md`