[Improve] Keep routine 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

• Removed the runtime requirement that automation-started tasks always send a terminal communication-channel closeout.
• Updated custom automation and late-bound work-item guidance to default to silent completion and reserve reports for actionable or important findings, meaningful completed results, durable blockers, or required input.
• Kept configured destinations available when a report is warranted, while allowing explicit automation instructions to request routine or no-action reporting.

Why this change was made

Routine successful and no-change automation runs should remain auditable without unnecessarily interrupting people in communication channels.

Impact

Custom automations and late-bound work items can now finish without posting. By default, human-facing messages are limited to outcomes worth immediate attention, while automations with explicit reporting requirements retain that behavior.

[roomote-community]

No code issues found. See task

• Late-bound automation work items can now finish without creating their report thread or posting the required final outcome (apps/worker/src/run-task/__tests__/run-task.test.ts:1157).

_{Reviewed 75c546b}

[roomote-roomote]

Updated late-bound automation work items to follow the same interruption-worthy reporting default: meaningful results, actionable findings, blockers, and required input can post, while routine no-op or no-change outcomes finish silently. Pushed in 75c546b.