hermes - 💡(How to fix) Fix feat(simplex): treat an edited inbound message as a correction that supersedes the in-flight/queued original

Use case

On SimpleX it's common to realize, a second or two after hitting send, that you made a mistake or left something out — while the agent is already mid-reply, or while the message is still sitting in the processing queue. SimpleX lets you edit a sent message, but today that edit is dropped: the adapter handles newChatItem(s) but not chatItemUpdated, so the agent acts on the original (mistaken) text.

Desired behavior

When an inbound SimpleX message is edited (chatItemUpdated), treat it as "I meant this instead," correlated to that specific original message:

• still queued → replace the queued message's text with the edit;
• already being processed → interrupt/steer the in-flight turn with the corrected text (supersede), instead of finishing on the stale original.

Why this is gateway-core, not adapter-only

An adapter can surface the chatItemUpdated event, but correlating an edit to the specific in-flight or queued original and superseding it needs gateway-side support: an edit→original message-id correlation, plus a supersede/replace API on the active turn and the pending queue. On its own, an adapter can only re-inject the edited text as a brand-new message (no correlation) — which doesn't achieve "fix the message I just sent."

Notes

• Adapter prerequisite: handle chatItemUpdated and carry the original item id (pairs with populating inbound message_id from itemId).
• Likely applies to other platforms with inbound edits (Signal receives edits today, but as new messages, not correlated supersedes).