decision-escalatelisted

# Decision escalate Put every open decision that belongs to the operator as one batch, each carrying its options and a recommended default, then stop until the batch is answered. One batch is the whole point. A session that asks one question, acts, then asks the next spends the operator's attention once per decision and hides how many are open. ## Guards - If nothing is open, stop: `❌ Nothing to escalate. Every open call is one this session can make.` - Escalate only a decision whose answer turns on the operator's preference. A judgment call with two or three reasonable options the session can weigh is a pick with the tradeoff stated in one sentence, taken without asking. - Escalate only what is open now. A decision already taken this session goes to the artifact that records it rather than back to the operator. - Do not act on any decision in the batch before it is answered. Continue the work that depends on none of them. - Do not escalate a question the session can answer by reading the repository. Read first, and escalate what the tree does not settle. ## Step 1: collect what is open Sweep the session for every decision still unmade. The usual sources: - A plan question whose answer turns on preference rather than measurement - A fork the session parked to keep moving, where both branches still ship - A default the session took silently that changes what the operator receives - A scope boundary the request left ambiguous, where the two readings produce different wor