Under the hood
A server-side session relay now refuses to start if the transcript is already marked complete
What
Before a server-driven 'teleport relay' (a mechanism for continuing a session on the server) arms itself, it now checks the lines after its starting point for a marker that indicates the whole conversation history has already ended. If that marker is present, it refuses to arm and reports a new relay_already_ended error instead of proceeding as if there were more to relay.
Why
This prevents the relay from starting up on a transcript that's already finished, avoiding wasted or incorrect work on a conversation that has nothing left to continue.