osmaczko addcde03eb feat: introduce client event system
- Core returns `InboundResult` — a typed struct with an optional
  `NewConversation` and a `FrameOutcome` of decrypted messages.
- Client surfaces app-facing events via `Vec<Event>`, translated from
  `InboundResult` at the boundary.
- MLS group welcomes now produce a `ConversationStarted` event with no
  initial content, fixing the silent-group-join case where the inbox
  layer dropped the observation.
- C FFI exposes an `EventList` opaque type with indexed accessors and
  an `Invalid` sentinel for OOB / non-applicable reads.
- Symmetric `Inbox` / `InboxV2` handlers: both return
  `Result<InboundResult, _>` and own the persistence + ephemeral-key
  cleanup for the conversations they create.
- Updated and simplified `docs/adr/0001-client-event-system.md`.
2026-05-26 12:05:44 +02:00

38 lines
1.2 KiB
Rust

//! Application-facing chat events.
//!
//! Each variant of [`Event`] describes one observable thing the application
//! cares about: a new conversation has appeared, a message was decrypted on
//! an existing one, and so on. The enum is `#[non_exhaustive]` so new
//! variants can be added without breaking exhaustive matches in dependent
//! crates.
use libchat::ConversationIdOwned;
/// A discrete chat event.
#[non_exhaustive]
#[derive(Debug, Clone)]
pub enum Event {
/// A new conversation has appeared.
ConversationStarted {
convo_id: ConversationIdOwned,
class: ConversationClass,
},
/// User content arrived on an existing conversation.
MessageReceived {
convo_id: ConversationIdOwned,
content: Vec<u8>,
},
}
/// Coarse classification of a conversation, intended as a UI/UX hint.
///
/// Decoupled from the core's protocol-versioned kinds: future versions of
/// an existing class (e.g. a `PrivateV2`) map to the same variant here.
/// New variants are reserved for fundamentally different conversation
/// shapes and are intentionally breaking when added.
#[derive(Debug, Clone, Copy, PartialEq, Eq)]
pub enum ConversationClass {
Private,
Group,
}