Running and Controlling a Conversation

runConversation() starts an idle, prepared Conversation. Once execution is underway, the application can stop, pause, resume, or redirect it.

stopConversation() terminates processing; calling it while already idle succeeds as a no-op.

pauseConversation() requires active processing. resumeConversation() resumes processing, while idle or stopping states are treated as successful no-ops.

interruptConversation(goTo:) is different from stop: it interrupts the current work and redirects execution to another module. This makes it useful for application-driven changes in conversational flow.

These APIs operate at the Conversation level. Lower-level playback and recording controls remain part of STMediaRunner.