OpenClaw: decide outbound Telegram notification posture for launch

[mfethe1]

Parent

#10

Type

HITL decision, then possible AFK follow-up.

What to build

Decide whether the first Telegram launch requires outbound status/completion replies in the Telegram group. If inbound-only control is enough for launch, document the deferral. If replies are required, create a follow-up AFK implementation issue for a controller-side Telegram outbound worker.

Acceptance criteria

• Product/operator decision is recorded: inbound-only launch or outbound replies required.
• If inbound-only launch is accepted, docs state outbound Telegram notifications are deferred and no host-side Telegram sender should be added.
• If outbound replies are required, a new implementation issue exists for a controller-side worker that reads adapter delivery records, calls Telegram sendMessage, and ACKs delivery rows.
• The decision preserves the single Telegram adapter posture; no per-host Telegram bots, command parsers, or direct host senders are introduced.
• No bot tokens or chat IDs are committed to the repo.

Blocked by

• OpenClaw: verify live Telegram routing to Rosie and Lenny #15

Sandcastle notes

The decision itself is HITL. If the decision is to implement outbound replies, the follow-up worker issue should be AFK-ready for Sandcastle on a branch like agent/openclaw-telegram-outbound-worker.