chore(sync): mirror docs from openclaw/openclaw@86328585fa

.openclaw-sync/source.json

@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "b277eac656082954174def3a07c3b5df4481a943",
-  "syncedAt": "2026-04-26T04:02:33.696Z"
+  "sha": "86328585fac2dfe150fc8036e9d65547a20c3381",
+  "syncedAt": "2026-04-26T04:07:30.185Z"
 }

docs/automation/tasks.md

@@ -115,12 +115,23 @@ stateDiagram-v2
 
 Transitions happen automatically — when the associated agent run ends, the task status updates to match.
 
+Agent run completion is authoritative for active task records. A successful
+detached run finalizes as `succeeded`, ordinary run errors finalize as
+`failed`, and timeout or abort outcomes finalize as `timed_out`. If an operator
+already cancelled the task, or the runtime already recorded a stronger terminal
+state such as `failed`, `timed_out`, or `lost`, a later success signal does not
+downgrade that terminal status.
+
 `lost` is runtime-aware:
 
 - ACP tasks: backing ACP child session metadata disappeared.
 - Subagent tasks: backing child session disappeared from the target agent store.
 - Cron tasks: the cron runtime no longer tracks the job as active.
-- CLI tasks: isolated child-session tasks use the child session; chat-backed CLI tasks use the live run context instead, so lingering channel/group/direct session rows do not keep them alive.
+- CLI tasks: isolated child-session tasks use the child session; chat-backed
+  CLI tasks use the live run context instead, so lingering
+  channel/group/direct session rows do not keep them alive. Gateway-backed
+  `openclaw agent` runs also finalize from their run result, so completed runs
+  do not sit active until the sweeper marks them `lost`.
 
 ## Delivery and notifications