goal-looplisted

# goal-loop ## Purpose Coordinate an approved GOAL.md-backed `/goal` run through preflight, implementation, deterministic eval, judgment eval, repair, closeout, or stopped. `status: done` is reserved for GOAL-level terminal completion after closeout. ## Use When - An approved GOAL.md exists and `/goal` is the active execution entrypoint. - The run needs coarse routing between final Skills. - Preflight, transition reasons, stop reasons, and run artifacts must be recorded. - A natural-language paste command such as `Start review fix` with alias label `review-fix` has an approved implementation-fix GOAL.md and needs preflight before routing to bounded implementation. - `Start autonomous execution` with alias label `autonomous-run` has an approved GOAL.md after goal-prep approval or evidence-gated fixed-panel approval and needs full lifecycle preflight. ## Do Not Use When - GOAL.md is missing, draft, superseded, unreadable, or hash-mismatched; use `goal-prep`. - The user wants to bypass `/goal`; propose a GOAL.md patch through `contract_revision_required`. - The task is only a direct review or closeout request outside an approved GOAL.md-backed run. ## Default Protocol Default scope is GOAL.md-backed `/goal` preflight, routing, run artifacts, transition/stop reasons, and `next_route` coordination only. Allowed actions are capability checks, objective-shape checks, run artifact writes after preflight passes, deterministic eval routing, judgment eval routing, and closeout r