Status: IN
`apply_remote_change` always advances the node's Lamport clock to `max(local_clock, remote_ts) + 1` before any conflict resolution, ensuring subsequent local writes have causally-later timestamps than any received change.
Source: entries/2026/05/29/multi-leader-replication-multi_leader-apply_remote_change.md