Dashboard Telegram channel config not persisted to .env

[ntamero]

Bug Description

When configuring Telegram in the Dashboard (Channels > Telegram), entering the bot token and saving does not persist the TELEGRAM_BOT_TOKEN to ~/.openfang/.env. The [channels.telegram] section in config.toml also remains empty.

Steps to Reproduce

1. Fresh install OpenFang v0.3.2
2. Open dashboard, go to Channels > Telegram
3. Enter a valid Telegram bot token
4. Save/apply the configuration
5. Check ~/.openfang/.env — TELEGRAM_BOT_TOKEN is missing
6. Check config.toml — [channels.telegram] is empty

Expected Behavior

The bot token should be saved to .env as TELEGRAM_BOT_TOKEN and [channels.telegram] should be populated with at least enabled = true.

Actual Behavior

Token is not saved anywhere. Telegram channel remains disconnected after restart.

Environment

• OpenFang v0.3.2
• Ubuntu 24.04

[jaberjaber23]

Fixed in v0.3.4. The build_field_json() function was only returning a has_value boolean for env var fields and nothing for non-secret config fields. Added channel_config_values() that serializes the live ChannelsConfig to JSON per channel, then build_field_json() includes the actual saved value for non-secret fields (text, number, list types). List values are converted to comma-separated strings for display. The frontend openSetup() now pre-populates formValues from these returned values instead of always starting empty.