Split event batches would say nothing was dropped, but the path is off in this build.
A batch-split note rendered on the poll-event delivery path, which is switched off.
What's wrong with this entry?
When more queued events are waiting than fit in a single delivery, a system note is appended saying the batch was split, oldest first, and nothing was lost. The poll-event path this renders on is switched off in this build, so no one sees it.
more queued event(s) follow in the next delivery, oldest first; nothing was dropped.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.