Problem

When a cron job delivers a message to a Discord channel (via delivery.mode="announce"), the message appears in the Discord UI but is not injected into the channel session context. This means the agent operating in that channel has no awareness of what cron jobs have previously reported there.

Steps to Reproduce

1. Create a cron job with payload.kind="agentTurn" and delivery targeting a Discord channel (e.g. channel:123456)
2. The cron runs in an isolated session, produces output, and delivers it to the channel — visible in Discord UI ✅
3. When the agent later operates in that channel session (e.g. user asks a question), query sessions_history for the channel session
4. The cron-delivered messages are absent from the channel session transcript ❌

Expected Behavior

Cron-delivered messages should be visible (or at least queryable) within the target channel session context, so the agent can reference prior cron reports when interacting in that channel.

Actual Behavior

Cron delivery is UI-only — messages appear in the chat surface but never enter the channel session. The agent operating in that channel has a "split brain" view: users see cron reports + interactive messages, but the agent only sees interactive messages.

Impact

• Agent cannot reference its own cron-generated reports when users ask about them in the channel
• Creates confusion when users reference information the agent "posted" but has no memory of
• Breaks the mental model that a channel is a unified conversation history

Environment

• OpenClaw 2026.5.3-1
• Discord channel with daily cron delivery (openclaw-version-check → #openclaw-dogfood)

Discovery

Found during dogfooding: user asked about the daily version report in #openclaw-dogfood. The agent searched the channel session history but could not find any cron-delivered reports — only interactive conversation from days ago. The cron reports were visible to the user in Discord but invisible to the agent.