Current outcome of an accepted command

Reads the current outcome of a command by the receipt_id its response returned: accepted while it is in progress, then succeeded, failed (with error) or unknown (nobody can say; error explains). Poll until it leaves accepted. result depends on operation:

• create_session, append_message: the acceptance response exactly as first returned, never rewritten. The turn's outcome is read from GET /v1/sessions/{session_id}/turns/{turn_id} using target_ref.
• interrupt: {turn_id, terminal, no_op} once settled.
• pause, resume: {resulting_admission_state, checkpoint_revision, queued_turn_count}.
• close: {resulting_admission_state, checkpoint_revision, cancelled_turn_count}; checkpoint_revision is null only for a session that never ran a turn.
• terminate: {execution_gone, checkpoint_revision, unconfirmed_turn_id, external_effects_reverted}.
• recovery_decision: {resulting_admission_state, checkpoint_revision, resumable}.
• answer: null; only status and error change.
• request_push, resolve_push, push: {push_request_id, action, verdict, refusal, repository_id, checkpoint_revision, git_commit, target_branch}; verdict is allow or refuse, a refused attempt is failed with the reason in refusal and error, and fields the attempt never read are null. actor names who made it. Receipts written before the rename say decide_push, decision, already_decided and PUSH_REQUEST_DECIDED instead.
• open_pull_request, update_pull_request, comment_pull_request: {push_request_id, verdict, refusal, repository_id, number, url, head, base, created}, and for a comment also {comment_id, comment_url, marker}, and for an open or update whose body came from structured fields also template ({commit, path?, blob_sha?, skipped?}: the default branch's commit read, the template used or the reason one was passed over; never its text); created is false when the call answered an open pull request, edited the marked comment, or (always, for update_pull_request) changed the title or body of the pull request with the built-in github MCP server's update_pull_request.
• close_pull_request, reopen_pull_request: the same fields plus {state, changed}, written when the session's agent closes or reopens the pull request of its push request with the built-in github MCP server's tools of those names; state is the pull request's state after the call and changed is false when it was already in that state. A merged pull request is refused with pull_request_merged (PULL_REQUEST_MERGED).
• merge_pull_request: the same fields as close_pull_request plus {merged, changed, head_sha, merge_commit_sha, method}, written when the session's agent squash-merges the pull request of its push request with the built-in github MCP server's merge_pull_request; method is squash, or null when the pull request was already merged on the pushed commit (changed false). A refusal is failed with reason_code merge_off (the workspace has not allowed merging; GITHUB_REFUSED) before GitHub is called, or merge_blocked (PULL_REQUEST_MERGE_BLOCKED), head_moved or pull_request_closed (PULL_REQUEST_CLOSED). A receipt refused with merge_off names no connection, App or role.
• attach_repository: {session_id, attempt_id, agent_id, agent_release_id, repository_id, branch, commit, failure, reason_code}, written when the session's agent attaches a repository with the built-in github MCP server's attach_repository. It is accepted until the worker reports the fetch, then succeeded with commit or failed with failure (fetch_timeout, fetch_too_large, fetch_failed). A refused call is failed at once with reason_code repository_not_allowed (not on the release's list, not allowed for the profile, or the agent's GitHub off; error.code GITHUB_REFUSED), allowed_in_newer_release (off the session's release but allowed by the agent's active release: the session keeps the release it started with, and a new session can attach it; GITHUB_REFUSED) or attempt_ended (STALE_EPOCH). agent_release_id is the release whose list allowed it.
• set_slack_secret, delete_slack_secret: {purpose, last4}; the value itself is never in a receipt.
• set_github_app, delete_github_app: {app_id}; the private key is never in a receipt.

Any credential of the same owner can read a receipt, except that a receipt about a session needs that session to be visible to the caller, and one that changed an agent's settings (target_ref.resource an agent or one of its Slack bindings, other than a refused create_session) is read only by those who read the agent's settings: its workspace's owners and admins, its admins, the live members of its managing team, and their personal keys; anyone else gets 403. A receipt that names an agent or a release of one (agent_id, agent_ids, release_id, agent_release_id, or the agent as target_ref or actor.agent_id) is shown only with those ids to a reader who may use that agent (GET /v1/usable-agents); for anyone else a private agent's ids are left out (a list loses them, a single field is null) and a receipt whose target is that agent or one of its releases answers 404, as a receipt that does not exist does. It changes nothing.

Scope: sessions:read (API key or cookie session).