committed

A hot Flow of committed instructions in index order, delivered as Committed values.

Every node in the cluster — leader and followers alike — emits the same sequence here. Collect this flow to drive a state machine: apply Committed.Entry entries and reset to Committed.Install snapshots as they arrive.

The internal §5.4.2 election no-op (LogEntry.isNoOp) is withheld: it advances commitIndex but never appears here, so consumers see only application commands and need not filter. Application-proposed entries always surface, including those with an empty LogEntry.command.

Replay=0; late collectors miss entries emitted before they subscribed. To resume without gaps after subscribing late (e.g. on crash recovery), use committedFrom.