Optionaloptions: MessageChunkerOptionsStatic ReadonlydefaultStaticdefaultStatic ReadonlyminimumchunkSecureMessage for an asynchronously-signing chunk manager
(the OPN signature produced by a remote HSM/KMS provider): chunks are
delivered to the callback as each one's signing settles, in order, and
the returned promise settles after the final null callback. A
provider failure rejects.
The largest message body prepareChunk accepts with these parameters, or 0 when neither limit applies: the negotiated maxMessageSize, and maxChunkCount times what one chunk carries under the channel's security. The second is the tighter one whenever a peer derives its chunk count as maxMessageSize / bufferSize, as the CTT does, because every chunk also spends bytes on headers.
floor for the growable encode buffer, so tiny messages do not keep reallocating