Telegram: follow the messaging signature flip + behavioural verification #1056
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#1056
Reference in new issue
Block a user
Behavioural verification only. archie-core-9g5e (closed, merged 23e29b0) already
flipped the channel boundary onto domain/messaging.Message and changed the
Telegram construction sites. Nothing structural remains here.
Run the Telegram channel's history, branching and tool-call rendering behaviour
against the canonical type and confirm no regression from 9g5e across:
This is the "own behavioural verification" migration-decisions.md section 2
requires per channel. If a regression appears, fix it in internal/gateway (the
boundary) rather than papering over it in this channel.
Close reason
Verified by reading and build: Telegram builds the canonical Inbound; the /model gap is filed as olycr.
Imported from beads
archie-core-4hof· GitHub #667 · type task · priority P2 · created 2026-08-31 · closed 2026-10-10