docs(mcp): document existing recurring-task tools#23206

@@ -445,6 +451,19 @@ Without `runId`, it selects the newest interruptible run. A terminal run is
 returned unchanged, and a thread with no active provider turn returns
 `no_active_run`.
 
+### Scheduled tasks
+
+`schedule_task`, `list_scheduled_tasks`, `update_scheduled_task`, and
+`delete_scheduled_task` manage recurring work in the app scheduler. A schedule
+runs its prompt on an interval, at a fixed time in the server's local time
+zone, or on each qualifying webhook request, even when no turn is active.
+Signature checks, filters, and dedupe can skip a webhook request. For a task

@@ -445,6 +451,20 @@ Without `runId`, it selects the newest interruptible run. A terminal run is
 returned unchanged, and a thread with no active provider turn returns
 `no_active_run`.
 
+### Scheduled tasks
+
+`schedule_task`, `list_scheduled_tasks`, `update_scheduled_task`, and
+`delete_scheduled_task` manage recurring work in the app scheduler. A schedule
+runs its prompt on an interval, at a fixed time in the server's local time
+zone, or on each qualifying webhook request, even when no turn is active.
+Without a signature, anyone with the webhook URL can trigger a run.
+Signature checks, filters, and dedupe can skip a webhook request. For a task
+in the caller's project, runs post into the calling thread by default, so an
+orchestrator sees every trigger. With `bindToCurrentThread: false`, or for a
+task in another project, each run launches a fresh thread in the task's