Enum ChatPersist 

pub enum ChatPersist {
    New(Message),
    Updated {
        message: Message,
        edit_event: Option<Box<StoredEvent>>,
    },
    Removed(String),
    ReactionRemoved {
        reaction_id: String,
        message: Message,
    },
}

What applying a v2 chat event to STATE yielded — the caller persists it (async) once the STATE lock is dropped. Mirrors v1’s IncomingEvent for the chat sub-kinds: a message row is saved fresh or re-saved (a landed reaction rides the row), a delete drops it. Persistence is the caller’s so the apply step stays sync + lock-scoped.

Variants

New(Message)

A brand-new message — save its row.

Updated

A message changed: a reaction landed (edit_event None → re-save the row, which carries reactions) or an edit applied (edit_event Some → save the folded MESSAGE_EDIT event, event-sourced like v1 + DMs, never a row overwrite).

Fields

message: Message

edit_event: Option<Box<StoredEvent>>

Removed(String)

A message removed by its author — drop its row.

ReactionRemoved

A reaction revoked by its reactor — drop the kind-7 row (save is additive; a lingering row would resurrect the chip on the next load) and re-save the parent so its embedded reactions refresh.

Fields

reaction_id: String

message: Message