archie-messaging builds the Telegram gateway without RunningVersions (internal/app/archiemessaging/compose.go; only tests set it), so formatPendingReport verifies against nil and every successful Telegram-initiated update ends with 'health check passed, but I still can't confirm which version is actually running'. The messaging process has no truthful source for the daemon's or agent's running version. archied already verifies the same report against its own versions in update_relay.go (releaseupdate.ReportEvent -> update_report event). Fix: have Telegram relay the daemon's verified update_report event instead of re-verifying the pending report file itself.
Imported from beads archie-core-twg3 · GitHub #1078 · type bug · priority P2 · created 2026-09-25 · closed 2026-10-17
archie-messaging builds the Telegram gateway without RunningVersions (internal/app/archiemessaging/compose.go; only tests set it), so formatPendingReport verifies against nil and every successful Telegram-initiated update ends with 'health check passed, but I still can't confirm which version is actually running'. The messaging process has no truthful source for the daemon's or agent's running version. archied already verifies the same report against its own versions in update_relay.go (releaseupdate.ReportEvent -> update_report event). Fix: have Telegram relay the daemon's verified update_report event instead of re-verifying the pending report file itself.
### Close reason
Already fixed in 436f3a8a
---
_Imported from beads `archie-core-twg3` · GitHub #1078 · type bug · priority P2 · created 2026-09-25 · closed 2026-10-17_
sam
added the mediumbug labels 2026-10-27 13:41:02 +00:00
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.
archie-messaging builds the Telegram gateway without RunningVersions (internal/app/archiemessaging/compose.go; only tests set it), so formatPendingReport verifies against nil and every successful Telegram-initiated update ends with 'health check passed, but I still can't confirm which version is actually running'. The messaging process has no truthful source for the daemon's or agent's running version. archied already verifies the same report against its own versions in update_relay.go (releaseupdate.ReportEvent -> update_report event). Fix: have Telegram relay the daemon's verified update_report event instead of re-verifying the pending report file itself.
Close reason
Already fixed in
436f3a8aImported from beads
archie-core-twg3· GitHub #1078 · type bug · priority P2 · created 2026-09-25 · closed 2026-10-17