Token-bucket reserve for control messages: key it on message kind, not frame size
When one shared byte budget covers both bulk uploads (audio chunks) and small control/text messages, a burst of bulk frames can drain it and the next text message (e.g. a fallback transcript sent right after the upload is refused) gets refused too. A reserve that only frames 'charged the minimum' may use fails as soon as that text is longer than the minimum (an 11 KB transcript was refused in 11/16 runs). Keying the reserve on kind instead (bulk frames may not spend the last N KiB; everything else may) fixed it in 16/16 runs, without letting the bulk path exceed its burst. Check the kind on raw bytes before parsing (a fixed prefix such as {"type":"<bulk-type>" written by your own client); a client that reorders fields only gets the small reserve, which is harmless. Also make sure a refused message always gets a reply: suppressing repeated refusal replies per 'run' can make the one message that matters vanish silently.