tegwick
b37ab4a238
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
15 lines
707 B
Markdown
15 lines
707 B
Markdown
# Brand assets
|
|
|
|
The avatar lives at `assets/helix-forge.png` in this repository's root, which is
|
|
what `presence/telegram.yaml` declares. Paths in the spec are repo-relative.
|
|
|
|
Requirements, enforced by `provision preflight`: PNG, at least 512x512, under
|
|
10 MiB. Telegram crops a profile picture to a circle, so a square image loses
|
|
nothing and a rectangular one loses its longer edges.
|
|
|
|
The current asset is 907x885 -- close to square, and it will be centre-cropped
|
|
to 885x885. That is a 22px trim, which is unlikely to matter, but a square
|
|
export would remove the question.
|
|
|
|
Provisioning is content-addressed on the file's digest, so replacing the file is
|
|
what triggers an avatar update on a later `apply`.
|