fix: dev-poll stale detection should skip vision-labeled issues #448

New issue

Closed

opened 2026-04-08 19:27:34 +00:00 by dev-bot · 0 comments

dev-bot commented

2026-04-08 19:27:34 +00:00

Collaborator

Problem

dev-poll.sh stale detection flags vision + in-progress issues as stale because they have no assignee, no open PR, and no dev-agent lock. But vision issues are managed by the architect agent (via ops repo sprint PRs), not by the dev agent.

Observed: #419 (Vault blast-radius, vision + in-progress) got a stale detection comment from dev-qwen immediately after the in-progress label was added.

Fix

In the stale detection section of dev-poll.sh, skip issues that have the vision label:

issue_labels=$(echo "$issue_json" | jq -r '[.labels[].name] | join(",")')
if echo "$issue_labels" | grep -q "vision"; then
  continue  # vision issues managed by architect, not dev-poll
fi

Affected files

dev/dev-poll.sh (stale detection section)

Acceptance criteria

Dev-poll does not flag vision + in-progress issues as stale
Non-vision in-progress issues are still detected as stale when appropriate

## Problem dev-poll.sh stale detection flags vision + in-progress issues as stale because they have no assignee, no open PR, and no dev-agent lock. But vision issues are managed by the architect agent (via ops repo sprint PRs), not by the dev agent. Observed: #419 (Vault blast-radius, vision + in-progress) got a stale detection comment from dev-qwen immediately after the in-progress label was added. ## Fix In the stale detection section of dev-poll.sh, skip issues that have the vision label: issue_labels=$(echo "$issue_json" | jq -r '[.labels[].name] | join(",")') if echo "$issue_labels" | grep -q "vision"; then continue # vision issues managed by architect, not dev-poll fi ## Affected files - dev/dev-poll.sh (stale detection section) ## Acceptance criteria - [ ] Dev-poll does not flag vision + in-progress issues as stale - [ ] Non-vision in-progress issues are still detected as stale when appropriate