When a client's world hash differs from the server's, the soak report
now names the part that differs (tide, props, pieces or loot), the
client's ClientWorld tick, and each piece whose entry differs on the
two sides, so the next transient mismatch can be traced.
- NetWorld.world_detail(): part hashes and a piece list. world_hash()
is unchanged: the same bytes, hashed in four parts.
- The server's world_hash log lines and the soak clients' hash lines
carry the detail.
A full soak with this (24 clients, 2 matches) compared 3,743 hashes
with 0 differing, so the mismatch didn't come back to trace yet.
Refs #80
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>