Status: IN
KV vector clocks return new instances on every operation and leaderboard updates by remove-then-reinsert rather than mutating in place; both approaches avoid aliasing bugs where shared mutable references could cause unintended state corruption.
Immutable-value semantics eliminate shared-reference aliasing at the cost of allocation overhead
Depends on (SL): kv-vector-clock-immutable, leaderboard-update-by-remove-reinsert