Module held_checkpoints 

What still stops a --yolo run for a person.

--yolo means “run without me”, so a run that stops anyway looks like a hang. It is not: a blueprint can declare that a particular checkpoint needs a person however the run was launched, and the flagship software-engineer does exactly that for its plan approval, because everything after that gate writes code.

Two mechanisms say it, and they answer different questions, so they are not merged. unattended = "ask" on an interaction point is a checkpoint the framework always raises at a stage boundary. required_tools keeps a blocking tool the model may choose to call. A verification agent that needs “here is a fact, is it right?” to be guaranteed uses the first; one happy to let the model decide when to ask uses the second.

This module reports both, so the wait is announced before the run starts rather than discovered twenty minutes later.

Structs

Held

One thing in a blueprint that will still stop a --yolo run.

Functions

held_points

Every interaction point declaring unattended = "ask", in stage order.

held_tools

Every blocking human tool a stage keeps through required_tools.

preflight_lines

The stderr block for a --yolo spawn. Empty when nothing holds.