Really thorough rundown, especially the component table -- that's the kind of checklist that would have saved some pain on past projects. One thing I didn't see in the tool execution section: what happens when a caller interrupts mid-tool-call and then re-triggers the same intent ("wait, actually book it for 3pm") while the first call is still in flight on the backend. Interruption handling stops the audio, but nothing stops two overlapping tool calls hitting the same booking or charge unless the tool itself is idempotent or the backend tracks a call id per intent. Worth adding to the component list next to cancel semantics -- an interrupted-but-not-cancelled call plus a retried one is a pretty direct path to a double-booked slot.