Module fragment 

Outbound fragmentation planning and fixed-capacity reassembly.

Reassembly storage is one global page pool shared by all conversations: a fragment’s bytes are stored in linked 80-byte pages, and a slot holds only its key, presence bitmaps, per-fragment lengths/page heads, first-fragment metadata, and deadlines. A conversation with no incomplete fragmented message consumes no page storage.

Structs

BodyTooLarge

The body exceeds the wire maximum of 10 fragments × 160 bytes.

FirstMeta

Message-level metadata retained from fragment zero (spec: options from the first fragment apply to the entire reassembled message).

FragmentPlan

Plan for splitting an outbound body into fragments.

ReassemblyPool

Fixed-capacity reassembly pool.

RenderResult

Result of rendering a slot.

RenderSentinels

Sentinels inserted for absent portions of a partial message.

Slot

One in-progress reassembly.

Enums

InsertOutcome

Outcome of storing one received fragment.

Constants

PAGE_SIZE

Functions

empty_slot

render_slot

Render a slot’s fragments into out as UTF-8, inserting one sentinel per absent run and skipping code points damaged by missing byte boundaries.