Issue pool progression

Advance one unblocked issue without guessing around an external decision.

When to use

• The project defines an authorized label or issue list for agent work.
• Scheduled work should choose one eligible issue.
• Claims, merge state, deployment, and cleanup need a consistent protocol.

When not to use

• The issue pool or repository is outside the written authorization.
• A hold, dependency, or owner decision blocks the next step.
• Another active claim owns the issue.
• The user asked for a plan only.

What you need