[Fix] Automation reports post progress instead of results

[roomote-roomote]

​Opened on behalf of @daniel-lxs. View the task or mention @roomote-roomote for follow-up asks.

What changed

• Classify initial chat-bound automation runs as result-only delivery instead of user-started conversation turns.
• Keep acknowledgements, reactions, progress updates, partial findings, and routine status in the web task until the automation reaches its own reporting boundary.
• Leave each automation-specific prompt authoritative for whether to report, which chat tools to use, and how many final messages to send.
• Preserve normal conversational lifecycle instructions when a user sends a directed follow-up to an automation thread.
• Apply the same behavior to Slack, Teams, Telegram, and Discord, with regression coverage for initial reports and follow-ups.

Why this change was made

Scheduled automation reports could post an acknowledgement describing what the scan planned to do, making that in-progress message look like the automation's result. Automation report destinations should receive the result, not task narration.

Impact

Automation report destinations no longer receive pre-result chatter, while existing single-message, channel-post, and multi-message delivery contracts keep working unchanged. User replies to those reports still receive normal conversational acknowledgements and progress handling.

[roomote-community]

No new code issues found. See task

• Initial result-only directive overrides established automation delivery contracts (packages/cloud-agents/src/server/workflows/standardTask.ts:347).

_{Reviewed 4661a52}