Archive a session
Archives the session. This is an archive, not a destroy: the transcript is durable product state and remains fully queryable through the records surface and exportable. An archived session accepts no new work; branch it to continue from any entry. It is ONE WAY, and there is no operation here that undoes it: once a session is archived, nothing can move it back to accepting work. What continues from it is a branch, which is a new session with a new id — so every reference to the archived id (a link, a script, a teammate’s note) keeps pointing at a conversation that will never run again. A client that offers this to a person should ask them first. A session with a turn in flight is refused (409) rather than archived: that turn would finish into a session no write can move afterwards. On a hosted home, archiving the last session bound to a container the home made for a conversation deletes that container with its disks and its record; a branch made from the archive later starts in an empty one and is told so. An environment a client named is untouched.
Autorizações
Enforced on every transport, with no exempt operation. A person's request must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011 — except a request with no token on a laptop's socket from the OS user the kernel names as the host's own, which is that machine's user.
Parâmetros de caminho
The session's id.
Resposta
Archived. The transcript remains in the record.

