[Improve] Keep clean custom automation runs quiet

[roomote-roomote]

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

What changed

• Custom automations with chat destinations can finish clean runs without creating a report thread.
• Actionable findings, explicitly requested reports, durable blockers, and required input still report normally.
• Work-item execution tasks retain their required terminal closeout behavior.
• Automation settings show the five most recent launched tasks with state, trigger, timestamp, and task links, plus a link to older task history.

Why this change was made

Frequent checks lose value when every successful no-action run creates another notification. Separating execution from reporting keeps high-frequency automations useful without making quiet runs invisible.

Impact

Teams can schedule custom automations more frequently without proportional chat noise. Completed runs remain inspectable in automation settings and the task history, while findings and blockers continue to reach the configured destination.

Screenshots

[roomote-community]

1 issue outstanding. See task

• Avoid repeated unindexed scans of custom-automation task history from the settings page.

_{Reviewed a896005}

[roomote-community]

This lookup runs once per configured custom automation on every settings-page load. tasks only has an index on initiatorAutomation, so each query must scan/filter the whole custom_automation task population by actorExternalId and then order it before taking five rows. With up to 25 hourly automations, that cost grows quickly. Add a matching composite (ideally partial) index, or fetch all recent runs in one batched query.