coulomb/pr-hall-of-helix
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Point the presence at the provided avatar

Browse source 
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
This commit is contained in:
tegwick 2026-09-04 22:13:01 +02:00
parent 20b1ad077f
commit b37ab4a238
3 changed files with 11 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

BIN
assets/helix-forge.png Executable file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 832 KiB

22
presence/assets/README.md
View file

@ -1,17 +1,15 @@
# Brand assets # Brand assets
## helixforge-avatar.png — MISSING 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.
`presence/telegram.yaml` references `presence/assets/helixforge-avatar.png`. Requirements, enforced by `provision preflight`: PNG, at least 512x512, under
It does not exist yet, and `provision apply` will fail on `/setuserpic` until 10 MiB. Telegram crops a profile picture to a circle, so a square image loses
it does. nothing and a rectangular one loses its longer edges.
Requirements: square, at least 512×512, PNG. Telegram crops to a circle, so The current asset is 907x885 -- close to square, and it will be centre-cropped
keep the mark clear of the corners. to 885x885. That is a 22px trim, which is unlikely to matter, but a square
export would remove the question.
Deliberately not generated. This is the first thing a stranger sees of Provisioning is content-addressed on the file's digest, so replacing the file is
HelixForge on Telegram, and it should be a considered choice rather than a what triggers an avatar update on a later `apply`.
placeholder that quietly becomes permanent.
Provisioning is content-addressed on the file's digest, so replacing this file
is what triggers an avatar update on a later `apply`.

2
presence/telegram.yaml
View file

@ -36,7 +36,7 @@ presence:
and sessions doing that work are acknowledged. This channel carries short and sessions doing that work are acknowledged. This channel carries short
accounts of it, each linking back to the entry it was written from. accounts of it, each linking back to the entry it was written from.
avatar: "presence/assets/helixforge-avatar.png" avatar: "assets/helix-forge.png"
channels: channels:
# Created first. Every rendering is checked here, and nothing reaches the # Created first. Every rendering is checked here, and nothing reaches the