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
..
2026-05-26 12:05:44 +02:00

message-exchange

An example C application built on top of crates/client-ffi.

It demonstrates that the C ABI exposed by crates/client-ffi is straightforward to consume from plain C — or from any language that can call into a C ABI. No Rust code, no Cargo project: just a C source file linked against the pre-built static library.

Building and running

make        # builds client-ffi with Cargo, then compiles src/main.c
make run    # build + execute
make clean  # remove the compiled binary

For a release build:

make CARGO_PROFILE=release