issue-executionlisted

# Issue Execution Consume one approved backlog item without expanding its authority. Compose [github-triage](../github-triage/SKILL.md) for queue and lease mechanics, [repository-review](../repository-review/SKILL.md) for evidence and proof boundaries, [feature-branch](../feature-branch/SKILL.md) for branch creation, [git-add-commit-push](../git-add-commit-push/SKILL.md) for authorized publication, and [github-pull-request](../github-pull-request/SKILL.md) for the handoff PR. Load the applicable language, CI, security, documentation, deployment, or release skill only when the issue scope requires it. Use the [handoff contract](references/handoff-contract.md) before reporting completion. The offline failure cases are versioned in [cases.json](tests/fixtures/cases.json). Agent metadata is in [openai.yaml](agents/openai.yaml). ## 1. Resolve before claiming 1. Resolve the local root and confirmed `owner/repo`; read repository instructions and record the current branch, `HEAD`, upstream, staged, unstaged, and untracked state. 1. Read the issue's complete body, comments, labels, state, assignees, native `blockedBy` and `blocking` relationships, linked pull requests, and recent lease comments. Fetch relevant source, tests, documentation, workflows, and authorized live evidence before deciding that the issue is runnable. 1. Confirm the issue appears in the `github-triage` runnable queue and has the required problem, evidence, acceptance criteria, boundaries, validation, area, pri