hermes - 💡(How to fix) Fix cronjob deliver=local still delivers agent response to Telegram topic

Bug Description

When a cron job has deliver: local, the scheduler correctly skips the normal delivery path but still sends the agent's final response text to the Telegram topic where the job was created. This causes spam of verbose summaries in topics that should only receive intentional content.

Steps to Reproduce

1. Create a cron job with deliver: local in a Telegram topic
2. Wait for the job to run
3. Observe: the agent's final response text is delivered to the Telegram topic despite deliver: local

Expected Behavior

deliver: local should mean no delivery at all — the job output is saved to disk only. Nothing should appear in any chat/topic.

Actual Behavior

The agent's final response text is sent to the Telegram topic. This forces workarounds like making the agent respond with "." to minimize spam.

Environment

• OS: macOS 26.4.1
• Hermes Agent: latest (git main)
• Platform: Telegram gateway

Proposed Solution

Make deliver: local truly silent, or add a deliver: silent option where the scheduler does not deliver the agent's final response at all — only explicit send_message tool calls during execution reach the user.