pub enum CanaryOutcome {
Confirmed,
Absent,
Unverified(String),
}Expand description
What one canary run established.
Absent and Unverified are kept apart on purpose, and collapsing them
would be a real loss of information: “the CLI ran and the behaviour is gone”
and “the CLI could not be run at all” call for completely different operator
action, and a merged variant would report a missing binary as a broken
premise (threat T-31-12 — the risk this guard carries is a FALSE refusal).
Variants§
Confirmed
The declared token came back from a trustworthy place. The notification path is alive. This says NOTHING about whether work happened.
Absent
The CLI ran and the token did not come back. The premise this arc rests on is no longer backed by observed behaviour.
Unverified(String)
The guard itself could not reach a conclusion — carries the reason. Not a statement about the CLI’s behaviour.
Trait Implementations§
Source§impl Clone for CanaryOutcome
impl Clone for CanaryOutcome
Source§fn clone(&self) -> CanaryOutcome
fn clone(&self) -> CanaryOutcome
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more