codex-feature-issuelisted

# Codex Feature-Issue Automation Use this workflow only for issues authored by `KonH` and labeled `codex`. Work in the existing dedicated clone; never create a Git worktree. All automation comments and checklist edits belong on the issue, not its PR. ## Identity and safety - Start automation comments with `<!-- codex-automation -->`. - Start the one editable tracking comment with `<!-- codex-automation:checklist -->`. - Use branches `codex/issue-<number>-<slug>` for spec/plan work and `ralph/<spec-id>` for implementation. - Apply `codex-in-progress` only while processing an issue. Remove it before stopping. - Apply `codex-needs-attention` when an unsafe conflict, missing prerequisite, or fourth clarification round blocks progress. - Process only the issue candidates supplied by the runner. Do not discover additional issues. - Do not invoke `git worktree`. The runner resets this dedicated clone to `origin/main` before each poll. - Treat a comment from the owner as higher priority than an owner reaction. A reaction means approval only when it is newer than the latest automation comment. - End the final agent message with exactly one result line: `AUTOMATION_RESULT: COMPLETED` after every supplied candidate reaches its intended stopping point, or `AUTOMATION_RESULT: BLOCKED` when a missing prerequisite prevents that transition. Never report `COMPLETED` when blocked. - Whenever this run completes drafting a spec or completes drafting a plan for an issue, emit a line of the for