As a follow up: I've confirmed that it's due to the trigger adhering to network packet boundaries.
When I capture some MUD traffic in Wireshark, I see that the network packet boundary coincides with ...
For my MIP trigger (which I used on 3Kingdoms), in certain cases my prompt trigger triggers "too soon".
Perhaps this is best illustrated by this debug logging (newlines added for clarity):