Enum MonitorLaunch 

pub enum MonitorLaunch {
    PipeOwning {
        prompt: String,
    },
    Legacy,
}

Which supervision shape spawn_monitor should launch.

This is a MODE selection on one supervisor, not two monitors: both arms write the same capture, exit-code and agent-pid files under .devflow/, and both end by advancing the same stage machine. Nothing downstream needs to know which arm ran.

Variants

PipeOwning

Phase 31: a Rust supervisor that owns BOTH of the child’s pipes, delivers prompt as a JSON user turn on the child’s stdin, and holds that stdin open past the child’s first turn so a task-notification turn can still be delivered (constraint 4).

Fields

prompt: String

The stage prompt, delivered on the child’s stdin rather than argv.

Legacy

The pre-31 detached sh script: stdin is /dev/null, stdout is redirected to the capture file by the shell, and the script waits on the agent then runs devflow advance. Every non-Claude adapter, every stage not yet widened by D-09/D-10’s rollout, and the checkpoint-resume relaunch all run through here, unchanged.