maxPayloadBytes

The seam's budget, republished unchanged (#2069).

This transport hands message to Seam.sendTo exactly as the engine minted it and adds no bytes of its own, so there is nothing to subtract. Contrast RoutedRaftTransport, which wraps every frame in a RaftRelay envelope and therefore reports the delegate's limit less its own headerBudget — a decorator subtracts what it costs, and this one costs nothing.

A get() rather than a val initialiser because Seam.maxPayloadBytes is "a reading, not a lease": a mesh reports the minimum across its live links, so a peer attaching over a tighter transport lowers it. A snapshot taken at construction would go stale the first time the fabric changed shape.

The engine spends this on two things — chunking an InstallSnapshot, and refusing an over-budget propose before it can enter the log (RaftEngine.checkProposeFitsTransport).