4 Commits

Include renames

Author	SHA1	Message	Date
arcodange	799e10dcc2	Phase 2b — durable Postgres queue + worker (gated on DATABASE_URL) ... Adds the async dispatch infrastructure : - Postgres pool + embedded migration (CREATE TABLE/INDEX IF NOT EXISTS gateway_jobs). Auto-applied at boot. lib/pq driver (matches webapp convention). - queue.go : Enqueue (idempotent on UNIQUE(bot_slug, update_id) — handles Telegram redelivery), Pop with FOR UPDATE SKIP LOCKED, MarkDone, MarkFailed with exponential backoff (30s → 2m → 10m → 1h → dead at 5). - worker.go : goroutine that drains the queue, dispatches via the same Handler interface as sync, schedules retries on failure, notifies the user once when a job goes to dead. - BotConfig gains `async: bool`. Registry refuses bots with async=true if DATABASE_URL is unset (queue=nil). - Server : when bot.Async, the webhook ack is immediate ; the update payload is enqueued for the worker. When DATABASE_URL is unset (current default), queue/worker stay disabled and only sync handlers (echo, http, auth) work — no breaking change to the running cluster. Refs ~/.claude/plans/pour-les-notifications-on-inherited-seal.md § Phase 2.	2026-05-09 14:38:41 +02:00
arcodange	8001460f14	Phase 2a — add 'http' handler (sync forwarder) ... The http handler POSTs the Telegram Update JSON to a configurable internal URL and expects a JSON {text} reply, which it sends back via sendMessage. Sync : the webhook ack waits for the upstream answer (timeout default 5s, capped at 30s — Telegram itself closes around 60s). For slow / unreliable backends use the Phase 3 async handlers once the queue is in place. YAML config : bots: webappbot: handler: http http: url: http://webapp.webapp.svc.cluster.local:8080/telegram/update timeout: 5s Refs ~/.claude/plans/pour-les-notifications-on-inherited-seal.md § Phase 2.	2026-05-09 14:27:58 +02:00
arcodange	07115e3162	Phase 1.5 — auth layer (Redis sessions, allowlist, requireAuth) ... Adds an authentication layer in front of the bot handlers : - Auth handler on the principal bot (@arcodange_factory_bot, slug factory) parses /start, /auth <code>, /whoami, /logout. On a successful /auth, the message containing the code is best-effort deleted from the user's chat (replay defense). - Redis-backed sessions (key tg-gw:auth:<from.id>, TTL 24h, configurable via AUTH_SESSION_TTL). Constant-time secret compare via crypto/subtle. - ALLOWED_USERS env (CSV of Telegram user IDs) — silent-drops anyone not in the list before the auth gate runs. - New per-bot field 'requireAuth' (pointer-bool). Default = true (secure by default). Auto-forced to false for handler=auth (chicken-and-egg). - Server gates: allowlist first, then requireAuth before handler dispatch. - Fail-at-startup if a bot is configured with handler=auth or requireAuth: true while AUTH_SECRET is unset. Design: factory/docs/adr/20260509-telegram-gateway-auth.md (in factory PR). User docs: AUTH.md (new), HOWTO_ADD_BOT.md (Cas 2 updated for default true and gated flow). New deps: github.com/redis/go-redis/v9. Refs ~/.claude/plans/pour-les-notifications-on-inherited-seal.md § Phase 1.5.	2026-05-09 13:56:30 +02:00
arcodange	ee832de089	Phase 1 MVP — echo bot factory	2026-05-09 12:23:59 +02:00