reconcile's pinProcessBindings (internal/app/archiemessaging/reconcile.go) refuses a Telegram enable or disable from stored settings and reports 'chat.telegram enabled/disabled; takes effect on restart'. composeChannels only composes Telegram when it was enabled at startup, so a channel turned on later has no instance for the supervisor to start.
Design
Compose the Telegram instance always; its channel is nil until a token resolves, which is what disabled means. The parked supervisor runs it when it appears and parks again when it goes. reconcile applies enablement: enableChannel builds and swaps a channel in, disableChannel swaps it out; both update the status declaration (Configured, ReloadSupported) and wait for the channel to leave or reach stopped before reporting applied, via a status poll bounded by channelApplyTimeout. channelChanges no longer treats enable/disable as a transport change.
Acceptance criteria
Tests drive reconcileOnce with stored settings: version 1 with a token enables Telegram and is recorded applied only once the channel is running it; version 2 clears the token, disables it and records applied.
Imported from beads archie-core-teaq · GitHub #1558 · type bug · priority P2 · created 2026-10-08
reconcile's pinProcessBindings (internal/app/archiemessaging/reconcile.go) refuses a Telegram enable or disable from stored settings and reports 'chat.telegram enabled/disabled; takes effect on restart'. composeChannels only composes Telegram when it was enabled at startup, so a channel turned on later has no instance for the supervisor to start.
### Design
Compose the Telegram instance always; its channel is nil until a token resolves, which is what disabled means. The parked supervisor runs it when it appears and parks again when it goes. reconcile applies enablement: enableChannel builds and swaps a channel in, disableChannel swaps it out; both update the status declaration (Configured, ReloadSupported) and wait for the channel to leave or reach stopped before reporting applied, via a status poll bounded by channelApplyTimeout. channelChanges no longer treats enable/disable as a transport change.
### Acceptance criteria
Tests drive reconcileOnce with stored settings: version 1 with a token enables Telegram and is recorded applied only once the channel is running it; version 2 clears the token, disables it and records applied.
---
_Imported from beads `archie-core-teaq` · GitHub #1558 · type bug · priority P2 · created 2026-10-08_
The supervisor's enableChannel/disableChannel/restartChannel helpers and the per-instance rebuild closures were deleted in c5f24ec9: since #1399 channels are extensions composed at startup, and nothing called them. The design above (built-in Telegram, pinProcessBindings) is stale. A fix now means recomposing an extension channel on a settings change and swapping it in with setChannelState, which org channels already use.
The supervisor's enableChannel/disableChannel/restartChannel helpers and the per-instance rebuild closures were deleted in c5f24ec9: since #1399 channels are extensions composed at startup, and nothing called them. The design above (built-in Telegram, pinProcessBindings) is stale. A fix now means recomposing an extension channel on a settings change and swapping it in with setChannelState, which org channels already use.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
reconcile's pinProcessBindings (internal/app/archiemessaging/reconcile.go) refuses a Telegram enable or disable from stored settings and reports 'chat.telegram enabled/disabled; takes effect on restart'. composeChannels only composes Telegram when it was enabled at startup, so a channel turned on later has no instance for the supervisor to start.
Design
Compose the Telegram instance always; its channel is nil until a token resolves, which is what disabled means. The parked supervisor runs it when it appears and parks again when it goes. reconcile applies enablement: enableChannel builds and swaps a channel in, disableChannel swaps it out; both update the status declaration (Configured, ReloadSupported) and wait for the channel to leave or reach stopped before reporting applied, via a status poll bounded by channelApplyTimeout. channelChanges no longer treats enable/disable as a transport change.
Acceptance criteria
Tests drive reconcileOnce with stored settings: version 1 with a token enables Telegram and is recorded applied only once the channel is running it; version 2 clears the token, disables it and records applied.
Imported from beads
archie-core-teaq· GitHub #1558 · type bug · priority P2 · created 2026-10-08The supervisor's enableChannel/disableChannel/restartChannel helpers and the per-instance rebuild closures were deleted in
c5f24ec9: since #1399 channels are extensions composed at startup, and nothing called them. The design above (built-in Telegram, pinProcessBindings) is stale. A fix now means recomposing an extension channel on a settings change and swapping it in with setChannelState, which org channels already use.Fixed in
a9621b91c, on main and deployed.