roll-looplisted

# Roll Loop (Autonomous BACKLOG Executor) > Follows the Architecture Constraints, Development Discipline, and Engineering > Common Sense defined in the project AGENTS.md. Runs on a schedule. Picks up pending BACKLOG items and executes them without human intervention. The human stays informed via `roll-brief` and retains sole authority over releases. ## Execution Boundary **What roll-loop executes autonomously:** - US-XXX (User Stories) → `$roll-build` - FIX-XXX (Bug fixes) → `$roll-fix` - REFACTOR-XXX (Refactors) → `$roll-build` **What roll-loop never executes:** - Releases — production deployment is always a human decision (requires 2FA in real terminal) - Any Story marked 🚫 Hold or flagged for human review - Destructive operations outside normal skill scope **Human bypass path** — roll-loop 是默认调度器，不垄断执行权。任何时刻人可直接 `$roll-build US-XXX` 或 `$roll-fix FIX-XXX` 绕过 loop 立即执行（紧急 bug、中断插入、 故事评审等场景）。loop 通过 LOCK 和 `🔨 In Progress` 状态识别并跳过人正在做的故事， 人机并行不会撞车（见 Concurrency Safety）。 ## Environment Constraints (autonomous loop) You are running inside an autonomous cycle. No human is watching this turn. Adapt commands to the constraints below — otherwise you will burn turns on denied operations and the cycle will idle-exit. - **No `AskUserQuestion`**: no human can answer. If you genuinely cannot proceed without a decision, write an entry to `${HOME}/.shared/roll/loop/ALERT-<slug>.md` describing what's needed and exit cleanly. - **Avoid compound bash**: each `Bash` call must ru