poll-github-issueslisted

# Poll GitHub Issues for Assigned Issues Check GitHub Issues for issues assigned to the configured user that need implementation. Supports multiple engineer-agent projects watching the same repo, with routing via `references/routing-ladder.md`. ## Tools Needed - `Bash` — run `gh` CLI commands to query GitHub Issues - `Read` — read config, state, and the routing ladder - `Write` — create queue items - `Glob` — check for existing queue items ## Steps ### 1. Load Config Read `~/.local/share/engineer-agent/engineer.yaml`. Extract the `projects` map and `agent.branch_prefix` (required — read the literal string from the yaml; do not assume a default. If missing or empty, stop and tell the user to set `agent.branch_prefix`). ### 2. Load Dedup State Read `~/.local/share/engineer-agent/state/last-poll.yaml`. This contains: - `github_repos.<owner>/<repo>.last_checked` — per-repo timestamps (the collection boundary) - `projects.<slug>.github_issues.seen_issues` — per-engineer-agent-project seen issue lists ### 3. Select Projects For each project slug in the `projects` config map where the tracker resolves to `github-issues`: - If `tracker` is explicitly `"github-issues"`, proceed - If `tracker` is absent, proceed only if a `github.issues` section exists and no `jira` section exists - Skip projects where `tracker` is explicitly set to something other than `"github-issues"` Extract `projects.<slug>.github.owner`, `projects.<slug>.github.repos`, and `projects.<slug>.github.issu