tegwick 305e6cd313 Declare the Telegram presence and state the campaign's boundary ... The presence spec is editorial -- a bot's name, its description and the channel titles a stranger reads are brand, not mechanism -- so it belongs to the campaign rather than to the delivery interface. fluid-telegram's provisioner consumes it by path, which keeps that interface reusable by campaigns other than this one. The avatar is referenced but deliberately absent: it is the first thing a stranger sees of HelixForge on Telegram, and a generated placeholder would quietly become permanent. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0172sgCZEEDJcnQmr4SGDvKa Assistant: claude-code Assistant-Model: opus Assistant-Process: 1361245@bnt-lap001 Assistant-Session: b3b428ef-f3e6-4688-b091-01f71461d66a		2026-09-04 19:30:39 +02:00
..
assets	Declare the Telegram presence and state the campaign's boundary	2026-09-04 19:30:39 +02:00
telegram.yaml	Declare the Telegram presence and state the campaign's boundary	2026-09-04 19:30:39 +02:00