A reader who asked for a session and got nothing needs to know which of these happened — a mistyped id reads very differently from an archive that cannot be opened. Each case carries the words to show and the HTTP status a host answers with; the status is a plain number, so describing it costs the contract no server dependency.
A conversation this host answers about, which is in no session right now.
A conversation this host answers about, which is in no session right now.
Distinct from SessionNotFound because it is not a fault. A standing conversation outlives the CLI sessions that carry it: one expires when it has been idle long enough, and the next thing said starts another. There is nothing to read in between, and saying so in the vocabulary of a failed lookup answers "does the agent still remember" with an error rather than with the answer, which is no.
The transcript was read, and holds no such artifact.
The transcript was read, and holds no such artifact.
Carries nothing: what was asked for is a place in a conversation, and repeating a place back to whoever asked says more about the conversation than the answer needs to.
Carries nothing on purpose. Why a read failed is the host's own business — a path it could not open, a device that went away — and none of that is the asker's to know. A host that wants the detail logs it where it has the effects to do so.