[biglittlebigben]

Summary

A room's session ID can change while the egress stays connected (a new server session for a live room, a reconnect, a move). Egress now follows it instead of keeping the ID from the request.

• SDK source: after connecting, reports the room's name and SID (it may differ from the request), then again on every OnRoomSIDChanged. The SDK callback only signals; a single goroutine owned by the source does the reporting.
• Web source: room composite and template pages log ROOM_INFO:{"name","sid"}; the chromedp listener only stores and signals, and a reporter goroutine forwards it.
• Controller: onRoomChanged updates Info.RoomId/RoomName and the manifest. While the egress is active or ending it sends a handler update; before that, the activating update carries the room. Replays keep the recorded room.
• template-sdk (0.2.2): EgressHelper.setRoom logs ROOM_INFO on connect, reconnect, move, and session ID changes, using RoomEvent.RoomSidChanged when the installed livekit-client has it.
• go.mod pins server-sdk-go to feat(room): report room SID changes with OnRoomSIDChanged server-sdk-go#1038 for OnRoomSIDChanged. RoomSidChanged is added in Add RoomEvent.RoomSidChanged client-sdk-js#2155.

Testing

• New TestOnRoomChanged and TestWebSourceOnRoomInfo; go test ./pkg/pipeline/... ./pkg/config/... and golangci-lint pass.
• template-sdk type-checks; exercised against a fake room with and without RoomSidChanged.
• Integration suite not run.

🤖 Generated with Claude Code

[github-actions]

AV-sync stats summary: view in run #38985309958