telegram-gateway/AGENTS.md

telegram-gateway — agent guide

Telegram webhook gateway for the Arcodange lab (k3s, tg.arcodange.fr via Cloudflared). Full architecture, routes, local dev: README.md. Phase 1 (sync echo handler) is live; phases 2–3 (durable queue, async handlers) are the roadmap.

Fleet role — why this repo matters now

This gateway is the human channel of the AI back-office fleet (operator-endorsed, 2026-07): digests and approval cards are served from the cluster so approvals never wait for a laptop, and its planned Postgres queue is the fleet's work queue (decision D1). Context: the AI back-office PRD — notably agent-architecture (human channel, runtimes).

The backlog

Work items live as self-contained issues (context, deliverables, acceptance):

• #1 — Postgres durable queue + http handler (phase 2, fleet work queue)
• #2 — fleet daily digest + approval cards (depends on #1)

The wider backlog map (erp milestones, factory ADRs): the PRD STATUS.md. ⚠️ This repo's owner is arcodange (user org), not arcodange-org — Gitea MCP calls need the right owner.

Operating rules

• Work on a branch, PR via the mcp__gitea__* tools (this forge is Gitea; gh fails).
• Secrets via env (AUTH_SECRET, bot tokens from @BotFather) — never committed; bots.example.yaml is the template.
• A missing daily digest must be treated as an alarm by fleet consumers — keep the digest path dumb and reliable (an empty day still sends "all green").