Files
libchat/core
osmaczko 147d0b3b88 feat: surface what a GroupV2 conversation reports about itself
de-mls narrates its own commit-and-recovery cycle, and libchat consumes three of the fourteen events it emits and drops the rest. A group that has stopped moving therefore looks like one that is idle: the roster keeps reporting whatever it last committed, and the account of why sits in a log the application cannot reach.

Buffer the phase changes, the commit-round counts and the steps that did not go through the way causal-history observations are buffered, drain them after each drive of the core, and give each a client event. The count is the load-bearing one: a round that ends short of the candidates it expected is a round where members chose from different sets, which is how a group splits.
2026-08-24 10:23:11 +02:00
..
2026-03-24 18:21:00 -07:00

Core

Crates in this directory will one day be separated into a separate shared repository.

They could be moved now, but it's desirable to have a monorepo setup at this time.

These crates MUST not depend on any code outside of this folder.