Struct StatusOutcome 

pub struct StatusOutcome {
    pub issue: Issue,
    pub decision: Option<TransitionDecision>,
    pub written: bool,
}

What the seam did (WP03 T013).

written and decision are deliberately redundant. Either alone would do: written == false implies decision.is_none(), and a decision always implies a write. They are both here because the two questions a caller asks are different — “did anything happen?” and “what gets appended?” — and reading the answer to one off the other is the kind of inference that breaks silently when a fourth outcome is added later.

Fields

issue: Issue

The issue as it now stands in the store: the accepted column, the bumped updated, and the appended decision. On an inert no-op this is the issue exactly as it was.

decision: Option<TransitionDecision>

The decision appended to the issue’s History, or None when nothing was written.

written: bool

Whether the file was written at all.

false for a same-column re-apply and for any path that carries no change. A refusal is not represented here — it is an Err, so “refused” and “accepted but did nothing” are different types rather than one Outcome with a flag.

Trait Implementations

impl Clone for StatusOutcome

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for StatusOutcome

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Eq for StatusOutcome

impl PartialEq for StatusOutcome

fn eq(&self, other: &Self) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for StatusOutcome