engine-20260905-2256

The guest now forces a CRNG reseed as soon as the handshake completes, before anything can consume randomness. Every visitor resumes the same frozen pool, and only a reseed pulls fresh bytes from the CPU instruction QEMU answers out of the browser; until now that reseed fired only because the snapshot happened to be taken at 0.93 s of uptime. A snapshot taken 45 s in gave six identical boot ids from six resumes before this change and six distinct ones after. Engine files unchanged.