fix(sessions): hide the Replay action for sessions with no recording

The Replay button rendered on every session row, including sessions the SDK
never recorded a screen for — clicking it opened a player that could only say
"no recorded events". The action is driven by the `session` summary tag, so the
tag is now emitted only when a `projects.replay_sessions` row exists.

Replay state lives in Postgres, never in telemetry, so it is a second lookup
over the page's ids only, project-scoped and batched. Session keys that are not
UUIDs (sessions derived from user id/email) can never have a recording, so they
are not even asked for.

Matched on the parsed UUID rather than its text: an SDK emitting an uppercase id
round-trips through UUID.toText as lowercase and would otherwise never match
itself, silently hiding Replay for a session that has a recording.
This commit is contained in:
Anthony Alaribe 2026-08-13 11:47:18 +02:00
commit cff87aeb77
3 changed files with 50 additions and 2 deletions