buildlisted

# /of-loop:build - one bounded build or repair pass The parent is a thin coordinator. It does not engineer source and does not own branch/worktree/state identity. ## Fast paths (single source of truth) | State | Action | |-------|--------| | APPROVED / BLOCKED / STOPPED | STOP | | READY_FOR_REVIEW / REVIEWING | WAIT | | AWAITING_APPROVAL / READY_TO_START | STARTABLE; invoke ofloop build claim; first claim may auto-seal | | READY_TO_BUILD / CHANGES_REQUESTED / replayed BUILDING | proceed normally | Internal state AWAITING_APPROVAL is preserved for compatibility. The operator-facing meaning is READY_TO_START (the run is startable; no approval ceremony is required). ## Substantial passes (F-5-01 v0.3.7) A bounded build pass is not required to be minimal. When the must-fix surface, scope, or refactor cut spans multiple files, the builder may produce a coherent substantial pass. The operator MUST NOT collapse or thin the change set to keep the pass small. ## First-start execution seal (v0.5.x) The first ofloop build claim invocation on an unstarted run creates the immutable execution seal: binding_method=build_start, binding_kind=execution_seal. The operator first build claim IS the authorization to execute the exact bounded packet locally. No prior human approval. No confirmation token. No program init. No legacy sealing command. No ofloop loop run. ## Pass responsibilities 1. Re-prove current packet bytes and execution binding. 2. Claim via ofloop build claim <repo> <