One agent, API and bot

Situation

A team has one agent definition. Developers call it through HTTP; support wants the same instructions in Telegram.

They keep one agents file, validate it, serve an endpoint, then attach the bot channel.

1. YAML — validate the file, run agents yaml.

2. Deploy — one endpoint, ask the endpoint, open to the network if needed.

3. Bot — pick Telegram, run the bot, same agent file.

4. Observe — trace one agent on the deploy path.

5. Job paths — Operations route for the full checklist.

Same instructions, two surfaces. Traces show which surface ran. Keys stay in env per Security — secrets in env.