reproduce-agent: backlog fix issue created without backlog label, not picked up by dev-poll #331

New issue

Closed

opened 2026-04-06 20:59:30 +00:00 by dev-bot · 0 comments

dev-bot commented

2026-04-06 20:59:30 +00:00

Collaborator

Flagged by AI reviewer in PR #330.

Problem

In docker/reproduce/entrypoint-reproduce.sh, when the reproduce-agent creates a backlog fix issue (for bugs with obvious root cause), the issue is created via API with no labels:

curl -sf -X POST ...   -d "$(jq -nc --arg t "..." --arg b "$BACKLOG_BODY" '{title:$t, body:$b}')"

Since dev-poll.sh only picks up issues with the backlog label, these auto-created fix issues are never picked up by the dev-agent pipeline. The backlog issue exists on forge but is effectively orphaned — no agent will ever act on it.

Fix

Add "labels":[$backlog_label_id] to the issue creation payload. The label ID can be fetched/ensured via the same _label_id helper already in scope.

Auto-created from AI review of PR #330

Flagged by AI reviewer in PR #330. ## Problem In `docker/reproduce/entrypoint-reproduce.sh`, when the reproduce-agent creates a backlog fix issue (for bugs with obvious root cause), the issue is created via API with no labels: ```bash curl -sf -X POST ... -d "$(jq -nc --arg t "..." --arg b "$BACKLOG_BODY" '{title:$t, body:$b}')" ``` Since `dev-poll.sh` only picks up issues with the `backlog` label, these auto-created fix issues are never picked up by the dev-agent pipeline. The backlog issue exists on forge but is effectively orphaned — no agent will ever act on it. ## Fix Add `"labels":[$backlog_label_id]` to the issue creation payload. The label ID can be fetched/ensured via the same `_label_id` helper already in scope. --- *Auto-created from AI review of PR #330*