Redacted excerpt; full evidence withheld.

$ cd <guest-path> && pwd && ls -la && id -u && python3 --version && git status 2>&1 | head -3 && cat README.md | head -c 6000
exit: 0
ice-offerer`) | supported with `--ice-full`, else refused (`ws-takeover-ice-unsupported`) |
| `RTP/SAVP` + `a=crypto` (SDES-SRTP) | refused (`ws-takeover-secure-offerer`) | supported |
| `UDP/TLS/RTP/SAVPF` (DTLS-SRTP) | refused (`ws-takeover-secure-offerer`) | supported |

On a supported secure takeover the engine mints its **own** keying rather than echoing the caller's,
decrypts the caller's ingress before it becomes the audio your bot hears, and encrypts the downlink
on the way back out. It is fail-closed: nothing leaves in the clear toward a peer that negotiated
encryption. Every refusal comes back at offer time with a stable token at the front of the reason,
so a controller can branch on it without parsing prose. Before 0.3.0 those same offers returned `ok`
and produced a call that answered and bridged nowhere, which is worth knowing if you are moving a
[excerpt truncated]