#[non_exhaustive]pub enum ToolReceiptOutcome {
Created,
Duplicate,
Deleted,
Missing,
Listed,
Rejected,
Completed,
Pending,
Failed,
TimedOut,
Cancelled,
Unknown(String),
}Expand description
What the operation did. Open, and a single shared vocabulary: a value
appearing in two families means the same thing in both, which is why the
permitted status values are bound to the value here rather than per
family.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
Created
A job was created.
Duplicate
The create matched an existing job.
Deleted
A job was deleted.
Missing
The delete matched no job.
Listed
The list was served.
Rejected
The call was refused before it ran — by a human at approval or by the
policy engine with no human in the loop. Its status is always
rejected or failed, never completed.
Completed
The Code Mode cell ran to its own completion; status completed.
Pending
The Code Mode call returned while its cell was still running; the item
is completed — the cell’s state, not the call’s.
Failed
The Code Mode cell or call failed; status failed.
TimedOut
The Code Mode cell or wait timed out; status timedOut.
Cancelled
The Code Mode cell or call was cancelled; status cancelled.
Unknown(String)
A value minted by a newer decision than this build knows. Preserved
verbatim so a client falls back only for the part it does not
recognize and can still read the discriminators and family fields it
does understand. Not a value any family registered, so it is excluded
from the generated schema while the enum stays declared open — the
SessionDurability::Unknown shape.
Never construct this with a registered word. Decoding never
produces it for one, so Unknown("create") does not survive a
round-trip: it re-decodes as the named variant and the two values
compare unequal. Producers build the named variant.