Record something the user did, for the agent running this session

What the user did. A closed set, because each member decides what the server does and what it says to the agent — there is no member meaning "something else, here is the text", which is the thing this endpoint exists instead of. test_configuration_edited is the user changing the configuration the agent saved, and is the one action that asks the agent to do something rather than merely telling it something. The four reference actions each name one thing the user pointed the session at. file_attached stores the file where the agent can read it by id. page_viewed says which page the user is on, which is the one action describing a state rather than an event: it is re-sent when they navigate, and each one replaces the last.

Which configuration the user edited, which is the only thing that changes how the edit is put to the agent. live is the configuration the conversation is working on. saved is a historical snapshot of a configuration the agent already saved, where editing it cannot rewrite anything, so the agent is told to adopt the values rather than that its own working copy moved.

Makes a retry safe, on the same terms as the inbox: the same key to the same session twice returns the message stored the first time and queues nothing new. The work behind the action is idempotent on its own — a re-sent attachment id resolves to the file already stored under it, and a reference action stores nothing to repeat.

What the agent will call the thing this action named — a test id, a case identifier, the session's own identifier for a tracker issue, or an attachment id. Assigned by the server for a tracker issue, because two issues from different trackers can present the same key and an identifier the agent has already read must never come to mean a different item. Absent for test_configuration_edited, which names nothing.