The spec declared presence/assets/helixforge-avatar.png; the asset that
exists is assets/helix-forge.png. Spec paths are repo-relative, so the
declaration now matches the file.
Records what preflight reports about it: 907x885 is not square, and Telegram
will centre-crop to 885x885. A 22px trim is unlikely to matter, but it is
better stated than discovered.
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
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
