574e3ca567
The harness failed about 1 run in 3 on CI with "play-trade villager false" on Horizon's side: the protocol client never saw the villager it trades with. A server pairs a player with an entity only while the entity's chunk has been sent to it, and checks again when either moves (ChunkMap.move / updatePlayers). VanillaProtocolClient sent its position once, at the spawn teleport, and never again. Horizon's first chunk batch goes out two ticks after the player is placed (after the first tick's packets, as vanilla orders them); when a busy machine held the tick thread back long enough for the client's move to be handled one tick after placement, the villager's chunk wasn't sent yet, and with no later move the villager was never paired. The 26.3 client re-sends its position every 20 ticks standing still (LocalPlayer.sendPosition, after a ServerboundClientTickEnd each tick). The parity client now does the same from the time it is loaded until its death, so an entity whose chunk comes late is paired at the next reminder, on either server. On failure the harness now adds the servers' and clients' warnings and errors to its message and the client log's tail when the client fails, and parity.py's summary prints the end of the first failing harnesses' logs, so CI shows why. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>