we were wavering for a while between making a separate

InteractiveRunner

and modfiying

ExecuteProcessResult

to guarantee local foregrounding/interactivity, and ultimately decided to use a separate abstraction for when we wanted to guarantee local foregrounding/interactivity, which is what

InteractiveRunner

is