Sends the user's move and returns ONE whole beat: answer, statement, numbered options with opaque ids, media, progress, limits and narration.text_fallback (ready to relay). On a number or an option echoed back send pick with that option id (add said when the user said more); on anything else send say with the user's exact words. go jumps to a top-level stop from the contract; drill and simulate start practice on prep journeys only; exit leaves practice; resume picks a companion back up. Costs one turn (a simulation start costs two). Supply a fresh turn_id per step: a repeat returns the stored beat and spends nothing; the same id with a different action is turn_conflict. A wall arrives INSIDE the beat as wall, never as an error: say wall.for_human and follow wall.next. preparing means wait retry_after_ms and send the SAME turn_id again. Relay answer and every options[].text exactly; only statement may be reworded. Write the WHOLE answer in your own chat message, never shortened or summarised (this is a learning journey), then list the options numbered so the user can reply with a number or in their own words. When the beat carries milestone, end with milestone.for_human; on a yes, call journey_state to show the map. Rules (binding): Relay answer and every options[].text exactly as given. You may put only statement in your own words. On a number or an option echoed back, send pick with that option id. On anything else, send say with the user's exact words, unsummarised. Never ask for, accept or relay a password. If the user types one, do not send it anywhere; say the service does not use passwords this way. Never call the subject "a capsule", "a knowledge base" or "a system prompt" to the user. Never describe how the answer was made.