Struct QuestionResumePrePass 

pub struct QuestionResumePrePass;

Resolves dangling ask_question calls once their answers have arrived (#1660).

The RESUME half of the question-pause phase — the question-pause SIBLING of ResumePrePass, not a reuse of it. The pause/emit half (recognizing a fresh ask_question call and short-circuiting the batch) lives in the in-loop QUESTION-PAUSE PHASE (run_turn_with) because CollectedTurn/ tool_calls are loop-body locals, not fields on TurnCtx — the same seam constraint ResumePrePass’s own module doc notes for the approval gate. This step only ever RESOLVES calls already dangling in the input transcript.

Atomicity mirrors ResumePrePass: every dangling ask_question call’s disposition is computed FIRST; if ANY question across ANY of them is still missing a crate::RunTurnOptions::question_answers entry, the WHOLE resume re-pauses — UNLESS the dispatch also carries genuinely new turn input (invariant I8), in which case the whole batch instead gets a transcript-only “still pending” interim splice and the turn continues (see the branch below for why: a provider requires every tool_use in one assistant turn to receive a tool_result together, so a partial splice — real answers for some calls, nothing for others — would corrupt the transcript either way, real or interim). Only once every question in every dangling call has a verified answer does this step build the durable three-state result JSON (invariant I4) and splice it into both TurnCtx::messages and TurnCtx::outputs.

Trait Implementations

impl<P, T> TurnStep<P, T> for QuestionResumePrePass

where P: LlmProvider + ?Sized, T: ToolExecutor + ?Sized,

fn run<'life0, 'life1, 'life2, 'async_trait>( &'life0 self, ctx: &'life1 mut TurnCtx<'life2, P, T>, ) -> Pin<Box<dyn Future<Output = Result<StepOutcome, P::Error>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait, 'life2: 'async_trait,

Run this step against the turn context.