Replay response wrapped in top-level `data` envelope
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The response schema for the Replay detail endpoint has been restructured: all previously top-level fields (id, project_id, trace_ids, user, sdk, os, browser, device, etc.) are now nested under a required data property. Any client code that reads replay fields directly from the response root (e.g. response.id, response.user) will break — it must now access response.data.id, response.data.user, etc.