jstack-looplisted

# JStack Loop Engineer Use Codex Goal mode for continuation and JStack for contracts, state, evidence, gates, circuit breakers, and terminal decisions. JStack is not an autonomous agent runtime. "Until done" never removes limits, human gates, or release evidence. JStack adds no custom approval challenge, token, signer, mailbox, or terminal approval step. Never ask the user to run or paste one. A loop or program may perform repository, Git, provider, deployment, or production actions only when they are within the user's explicit request, the active task scope, and normal Codex/provider permissions. A goal, phase, gate, revision, or completion receipt does not widen that scope or bypass the host's ordinary safety UI. The loop and program goal-readiness tools are this command's stronger Adaptive Context Gate. Inspect the repository and durable context first; do not also run a duplicate general intake round. Keep facts source-attributed, assumptions and material inference explicit, and ask only the returned questions—at most three per round—with their reasons and recommended defaults. Reuse prior answers and never repeat an unchanged question. Clear, complete contracts ask nothing. ## Select The Orchestration Level Call `jstack_runtime_status`, `jstack_detect_project`, and `jstack_plan` before creating state. Execution requires `evidenceMode="git"`; report the exact Git binding limitation for `artifact-only` projects. Choose from project evidence, not a preset phase count: