Enum PlannedCall 

pub enum PlannedCall<'a> {
    Tool {
        name: &'a str,
        input_json: &'a str,
    },
    Shell {
        binary: &'a str,
        command: &'a str,
        argv: &'a [String],
    },
}

What a step is about to dispatch, as SchedulerContext::gate_step is shown it.

The scheduler holds no session state and resolves nothing itself: it hands over the same values it is about to hand the executor, and the gate turns them into whatever its own decision point reads.

Variants

Tool

Fields

name: &'a str

input_json: &'a str

The step’s input, interpolated, exactly as the tool will receive it.

Shell

Fields

binary: &'a str

The first word of the step’s shell command.

command: &'a str

The step’s shell command as written, untruncated.

argv: &'a [String]

The argument list the executable will receive, already split. No shell expands it, so what is here is literally what runs.