DotMapSerializer

Custom KSerializer for DotMap<K, S> that emits DotMap.entries in a canonical order, producing identical bytes for any two replicas at the same logical state regardless of delivery order (issue #713).

Wire format: Map<K, S> — same structural layout as the auto-generated serializer, but with entries emitted in a canonical sorted order.

Sort order: entries are sorted by the structural encoding of their key: each K is serialized to a sequence of primitive leaf values via its KSerializer, and those sequences are compared lexicographically. This produces a deterministic order for any serializable key type — including data classes, inline value classes, and compound keys — and is robust where a toString-based sort is not: Double (-0.0/NaN), ByteArray (identity hash), and any type whose toString is not injective or platform-stable would silently produce a non-canonical sort. See sortedByCanonicalKey (issues #752, #1964).

The auto-generated serializer is delivery-order-dependent because DotMap.join builds a LinkedHashMap whose iteration order depends on which side is self vs other in the merge. Sorting before encoding makes the wire form a function of the logical value.