Enum ResumeEvent 

pub(super) enum ResumeEvent {
    SpawnedWithResume {
        generation: u64,
        attempted_sid: String,
        retry: RetryPayload,
    },
    SpawnedFresh {
        generation: u64,
    },
    SessionCaptured {
        generation: u64,
        sid: String,
        is_confirmed_success: bool,
    },
    MessageAppendedToRetryBatch {
        generation: u64,
        entry: QueuedRetryEntry,
    },
    ResumeUnreachable {
        generation: u64,
        sid: String,
    },
    ErrorResultLine {
        generation: u64,
        line: String,
    },
    ProcessExited {
        generation: u64,
    },
    StopRequested {
        generation: u64,
    },
}

Events the stdin writer / stdout reader / stderr reader / process- waiter sensor tasks report. Each carries the exact spawn generation it was observed for.

Variants

SpawnedWithResume

A fresh spawn attached --resume <attempted_sid>; generation is this spawn’s identity for the rest of its lifetime.

Fields

generation: u64

attempted_sid: String

retry: RetryPayload

SpawnedFresh

A fresh spawn did NOT attach --resume (no session id held yet). generation is this spawn’s identity, carried so NotTracking can tell a later, legitimate ProcessExited for THIS generation apart from a stale one for whatever generation it superseded.

Fields

generation: u64

SessionCaptured

A session-id-bearing stdout frame arrived for this generation. sid is the id it carried; is_confirmed_success is true only when THIS exact frame is a terminal result with is_error:false — a fully-completed, genuinely successful turn.

reagentx P0 on PR #2371: the CLI echoes back whatever --resume sid it was given as its FIRST stdout line REGARDLESS of whether that resume goes on to succeed or fail — this is true even for a frame that isn’t itself an error (e.g. a “system”/init frame), and this first echo can arrive before the independently-scheduled stderr reader has had a chance to report “No conversation found” and poison it. So sid == attempted_sid alone is NOT proof of genuine progress — it’s ambiguous until EITHER a different sid appears (the CLI gave up and started fresh — unambiguous) OR a successful terminal result confirms the WHOLE turn actually completed (also unambiguous). Only those two cases resolve tracking; a same-sid echo on any other frame type is left untouched, giving ResumeUnreachable a real chance to promote the retry first if this turns out to be the doomed case.

Fields

generation: u64

sid: String

is_confirmed_success: bool

MessageAppendedToRetryBatch

The drain appended another message to this generation’s retry batch before it was known to be doomed (or after it was confirmed doomed but before the process actually exited).

Fields

generation: u64

entry: QueuedRetryEntry

ResumeUnreachable

stderr reader saw “No conversation found” for this exact sid.

Fields

generation: u64

sid: String

ErrorResultLine

stdout reader saw a terminal result/is_error:true line.

Fields

generation: u64

line: String

ProcessExited

The process actually exited.

Fields

generation: u64

StopRequested

stop_process was called while this generation was live.

Fields

generation: u64

Trait Implementations

impl Clone for ResumeEvent

fn clone(&self) -> ResumeEvent

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ResumeEvent

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

Formats the value using the given formatter.