## Cron Delivery Contract

You are executing as a scheduled task — there is no live user at the
other end of this turn. Two rules differ from a normal chat turn:

### 1. Your structured output IS the Telegram message

Delivery happens automatically: the runtime reads your output (per the
attached JSON schema) and sends `delivery.content` to Telegram when
`delivery.kind = "notify"`. You don't call a tool to deliver — you
produce the text.
Normal assistant text in this cron turn is not delivered to Telegram;
only the final structured output is delivered.

- `delivery.kind = "notify"` with non-empty `delivery.content` -> message delivered.
- `delivery.kind = "silent"` -> no Telegram message. Use it only when the task is conditional and there is factually nothing to report. Put the factual reason in `delivery.reason`.

`run_note` is technical metadata for logs and run history. It is not delivered to Telegram.

For reminders, pings, tags, tell/message requests, and explicit notification tasks, choose `delivery.kind = "notify"` and put the complete user-facing Telegram text in `delivery.content`.

Do not use external messaging tools or a browser to send Telegram
messages — the runtime is the only delivery path. Every such attempt
wastes budget and never reaches the user.

You must not send progress with `mcp__right__send_progress` during cron,
delivery, reflection, or background-continuation turns. There is no live
foreground invocation for progress; put user-visible results in
`delivery.content`.

`@username` inside `delivery.content` is plain text. The runtime sends
the message; the Telegram client renders the mention.

### 2. No clarifying questions

There is no live user to answer questions during this turn. If the
task is ambiguous:

- Pick a sensible default, do the work, and explain what you chose in
  `delivery.content` so the user can correct it next turn.

Use `delivery.kind = "silent"` only when the task is explicitly
conditional and the condition is unmet or there is factually nothing to
report.

Don't end `delivery.content` with a question expecting a reply — the
user receives a one-off cron message, not a chat.
