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. ## 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: - Use one bounded loop for one coherent goal with one acceptance boundary. - Use a program when the outcome has independently verifiable phases, a dependency graph, different execution modes or scopes, long human/external waits, or program-level integration evidence. - Never hardcode a phase count or any domain-specific roadmap. The program accepts a project-derived DAG from one phase up to its policy ceiling. - Do not split work merely to create activity. Every