Checkpoint.NativePeerPublication

A star capture and durable publication strategy over owners 0..peers. State meaning, local computation, source placement and numerical policy belong to the caller. Owner 0 publishes: it prepares its own shards from its local state, then receives each other owner's captured state in turn over that owner's edge, checks that the agreed leading bytes (at least the (version, cursor, epoch) prefix) are identical to its own, and prepares that owner's shards from it. Only after every shard and the manifest are durable does it release each owner with the committed version; every owner, publisher included, completes only then. A missing, late or differently advanced owner publishes nothing. Per-owner frames carry that owner's identity, so a capture received on the wrong edge fails its frame check. All capture frames share one storage region (and all committed frames another): they are used one owner at a time, so the publisher's frame storage does not grow with the owner count.

51field unrestricted peerPublicationStateBytes : Nat