Post Leave

Signal meet-bot to leave the meeting.

Publishes leave_call on the session's voice-event stream — the SAME signal MeetVoiceAdapter.hangup_remote sends, and the reason this is not the Redis list it used to be.

The list (meet_bot:leave:<id>) was read by one loop in the bot, started after the join phase. A bot that has not joined yet is not idle: Google rejects an automated join, and the bot then HOLDS at pre-join for up to twenty minutes so an operator can carry it in by hand through noVNC. Nothing read that list during the hold. So this endpoint answered 200 and did nothing, for exactly as long as the hold lasted — six sessions stayed active with live containers and heartbeats after being asked to leave (2026-08-31).

leave_call is watched in BOTH phases: _hold_for_manual_join takes the same event (added when Cancel had this bug and was fixed for that button only), and the post-join loop races it. One signal, honoured wherever the bot happens to be.