poll-jiralisted

# Poll Jira for Assigned Tickets Check Jira for tickets assigned to configured users that need implementation. Supports multiple Jira projects per engineer-agent project, with routing via `references/routing-ladder.md`. ## Tools Needed - `mcp__atlassian__searchJiraIssuesUsingJql` — search for tickets by JQL - `mcp__atlassian__getJiraIssue` — fetch individual ticket details - `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: - `jira_projects.<key>.last_checked` — per-Jira-project-key timestamps - `projects.<slug>.jira.seen_tickets` — per-engineer-agent-project seen ticket lists ### 3. Normalize Jira Sources (Backward Compat) For each project slug in the `projects` config map: - Skip projects where `tracker` is explicitly set to something other than `"jira"` (e.g., `"github-issues"` or `"none"`) - For projects without a `tracker` field, proceed only if a `jira` section exists - Skip projects that have no `jira` section configured Normalize the jira config for each project: - If `jira.sources` (array) exists, use it as