AvatarKit v1.3.3-beta.1

Internal telemetry only — no public API or runtime behaviour changes.

• Avatar-loading and connection timings are now reported for failed attempts as well, each tagged with what went wrong. They were previously only sent on success, so the data could not tell a healthy integration apart from one where every load was failing. HTTP status codes alone could not fill the gap — this is what hid the earlier "Avatar data is invalid" incident, where the server answered 200 and decoding failed afterwards, leaving the request success rate at 100% throughout.
• Motion data received in .host mode now continues the trace started upstream, so one round of playback reads as a single trace end to end instead of two unrelated ones.