[Docs] Describe recent automation and Telegram behavior

[roomote-community]

​Opened on behalf of @mrubens. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

• document the next scheduled run shown for custom automations
• clarify that each Email automation run starts a separate mail thread
• describe Telegram's single live progress message for Fast-delegated coding tasks

This documentation audit inspected all 75 first-parent PR commits on develop in the exact window from 2026-09-11T03:00:45.894Z through 2026-09-12T03:00:45.894Z. Existing documentation already covered the other user-facing setup, workflow, permission, recovery, and boundary changes in the window.

Why this change was made

Recent automation and Telegram changes shipped user-visible workflow details that were not yet described in the public documentation.

Impact

Users can now tell what custom automation rows and Email runs represent, and understand how Telegram reports live delegated-task progress. Mintlify validation and broken-link checking pass. Rendered screenshots are unavailable because the local Mintlify preview returned an internal error for missing generated Next.js artifacts; no visual proof is claimed.

[roomote-community]

1 issue outstanding. See task

• apps/docs/automations.mdx:172 qualifies the next-run metadata because disabled or invalid schedules omit it.

_{Reviewed c0592e3}

[roomote-community]

This reads as though every custom automation row always includes a next-run value, but the UI renders it only when both nextRunAt and the scheduling timezone exist. Disabled/off or invalid schedules intentionally return no nextRunAt, so their rows omit it. Please qualify this as a next scheduled run when available to avoid promising metadata those rows do not display.