- A speaker who starts their next utterance within call.continueMs holds their request open for that final, also if the answer starts playing meanwhile; an empty final (rejected noise) joins nothing and asks nothing again - The engine checks the cancel before the tool router, the planner and a planned tool call too - Finals with a context are batched again: each context is cut from its end to the shortest one in the batch (ctranslate2 needs the start token at one position); ten finals at once 1.3 s - Measured harsh conditions (docs/v2/stt-accuracy-plan.md): the context never made them worse Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>