Hermes records unhandled Telegram updates as delivered without running an agent turn

The Hermes Telegram issue describes an admission observer completing a receipt for an update type that has no matching core handler. The gateway records that the event was handled although no agent turn occurred, and subsequent redelivery can be suppressed by the durable receipt. The false completion indicator is a delivery-integrity bug, not a prompt bypass.

The reporter supplies a group-99 dice-update reproduction and negative control cases for ordinary text. A candidate patch limits receipt completion to the responsible core handlers, but a released fix has not been established. The failure generalizes as a risk to workflows where detecting an event is treated as proof that an authorized consumer processed it.

The observer and handler performed different jobs. Seeing a Telegram update and recording a durable acknowledgment did not mean a matching handler processed it. Once the acknowledgment was written, a legitimate retry could be suppressed. The reported dice-update reproduction demonstrates this specific path; extrapolation to normal text delivery or a platform-wide Telegram vulnerability would exceed the evidence.