coulomb/fluid-telegram
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Implement the avatar and a preflight dry run

Browse source 
The avatar is now applied rather than deferred: BotFather's /setuserpic is a
conversation in which you send a photo, so the file is uploaded and sent as
a message. It is content addressed -- replacing the file is what triggers an
update, and the digest is recorded only after BotFather confirms, so a failed
upload retries rather than being remembered as done. The image is validated
before the conversation starts, because an image rejected halfway leaves the
bot registered without a picture.

Adds `provision preflight`: spec, avatar, OpenBao reachability, credentials,
session presence, salt and the resulting plan, checked in one run that writes
nothing and never contacts Telegram. Every failure it reports is one that
would otherwise surface after a phone number had been spent.

Two bugs it found immediately. The avatar path is documented as repo-relative
but resolved against the spec's own directory, so the real campaign spec
failed to find its own asset. And the OpenBao error named both variables when
only one was missing, sending the reader to check the one already set.

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:12:56 +02:00
parent 014ee5c746
commit 7347bd6302
11 changed files with 661 additions and 46 deletions
Download patch file Download diff file Expand all files Collapse all files

10
workplans/FT-WP-0002-declared-presence-provisioning.md
View file

@ -64,7 +64,7 @@ else in this workplan is interactive.
```task
id: FT-WP-0002-T02
status: progress
status: done
priority: high
state_hub_task_id: "01684264-37a5-5fe8-a491-37686e094428"
```
@ -83,11 +83,9 @@ The schema enforces rather than describes: an `admin_rights` entry other than
public one must, and unknown fields fail instead of being ignored. A silently
dropped field is how a spec stops describing what actually exists.
**Remaining:** the avatar asset. `presence/assets/helixforge-avatar.png` is
referenced but absent, and `apply` will fail on `/setuserpic` until it exists.
It is left for a person on purpose — it is the first thing a stranger sees of
HelixForge on Telegram, and a generated placeholder would quietly become
permanent.
**Done.** The avatar is provided at `assets/helix-forge.png` and validated:
PNG, dimensions, size, and a content digest so replacing the file is what
triggers an update.
## T03 — Implement `provision plan`