4 Commits

Include renames

Author	SHA1	Message	Date
arcodange	f90d5efdae	docs(HOWTO): add Cas 2.5 — http forward handler (Phase 2a livrée)	2026-05-09 14:29:40 +02:00
arcodange	515b407db4	docs: align ADR path references to doc/adr (singular) ... Mirror of factory#8 path correction. Updates Gitea URLs in AUTH.md / HOWTO_ADD_BOT.md and the '// Voir factory/...' header comments in code.	2026-05-09 14:26:12 +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	6228169ac1	docs: HOWTO_ADD_BOT — 3 cases (outbound only / echo via gateway / agent-driven)	2026-05-09 13:12:55 +02:00