OpenClaw: verify live Telegram routing to Rosie and Lenny

[mfethe1]

Parent

#10

Type

HITL - live Telegram and production host verification.

What to build

Run the end-to-end production verification that proves Telegram messages route through the Railway controller and canonical broker to the intended Rosie or Lenny host, with stable host IDs, ACKs, and replay safety.

Acceptance criteria

• GET https://openclaw-controller-production.up.railway.app/ready returns ready.
• GET https://openclaw-controller-production.up.railway.app/fleet shows both lenny and rosie online with recent heartbeats.
• Sending @lenny summarize the local repo status creates one task with a telegram-msg: task ID and routes only to Lenny.
• Sending @rosie check the graph server health creates one task with a telegram-msg: task ID and routes only to Rosie.
• Sending /assign task-lenny-smoke @lenny summarize the local repo status publishes to openclaw.task.host_6a163e09f5744561a0827d30253b3ba8.assigned.
• Sending /assign task-rosie-smoke @rosie check the graph server health publishes to openclaw.task.host_a23037f43daa41b19d1d441ec514af33.assigned.
• Lenny ACKs arrive on openclaw.task.host_6a163e09f5744561a0827d30253b3ba8.ack.
• Rosie ACKs arrive on openclaw.task.host_a23037f43daa41b19d1d441ec514af33.ack.
• Replaying the same Telegram update ID returns the existing message/command state and does not publish a second task.
• Verification evidence is captured in an issue comment with secrets redacted.

Blocked by

• OpenClaw: configure production Telegram group, bot, webhook, and room policy #14

Sandcastle notes

Do not run this as a Sandcastle job. This is live production verification with Telegram and host services.

[mfethe1]

Fleet side is ready for live Telegram routing verification:

• Railway /fleet shows both hosts healthy:
  • lenny -> host_6a163e09f5744561a0827d30253b3ba8
  • rosie -> host_a23037f43daa41b19d1d441ec514af33
• Both hosts subscribe to canonical openclaw.task.<host_id>.assigned and legacy durable delivery subjects on Railway NATS.
• The controller webhook endpoint is deployed and rejects missing Telegram secret headers.

Remaining blocker for this issue is #14: Telegram bot token, private supergroup chat ID, trusted operator Telegram user ID(s), and webhook registration are still missing. After #14 is completed, this issue can run the live @lenny, @rosie, and untagged claimable-work checks.