Validate actual recovery dispatch timing and observed handler outcomes

Retain 34 packets captured from actual native Player/Physics update dispatch for the paired recovery clock correction in client issue #1. Exact source/binary/map provenance and a simulation-time manifest cover all MP Recovery ranks plus the unlearned control at 10/20 seconds.

NativeRecoveryClock checks the exact protocol/trace corpus offline and, in the existing disposable runner, observes actual HP/MP with logged-in non-GM classless fixtures. Unlogged requests leave pools unchanged and currency is preserved. The complete running-server suite passed 15,263 assertions; the paired client passed 4,062 native checks.

This deliberately does not certify or approve healing amounts merely because the existing handler accepts them. Original formulas, posture, passive stacking and other recovery/lifecycle rules remain unverified. No server production logic change. Related #42 and client #1 (closed), neither closed. Depends on !90. No merge/deployment; private Docker/tmpfs fixtures preserve campaign state.