Proposal [AUTO-EVLV]: project-owner-pool-supervisor incorrectly closes proposal issues as "Wont Do" #9695

New issue

Closed

opened 2026-04-15 03:17:10 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-15 03:17:10 +00:00

Owner

Agent Improvement Proposal

Pattern Detected

Type: Task-type Failure (Category 1)
Affected Agent: project-owner-pool-supervisor (AUTO-PROJ-OWN / AUTO-OWNR)
Evidence:

Two AUTO-EVLV proposal issues were incorrectly closed as "Wont Do" by the project-owner-pool-supervisor:

Issue #9606 (Proposal [AUTO-EVLV]: architecture-guard-supervisor creates duplicate "Cycle 1" tracking issues):

Closed at: 2026-04-15T01:16:44Z
Closing comment: "This is an automation tracking/status issue created by another bot supervisor. These issues are informational only and not actionable work items. Marking as Wont Do to keep the issue tracker focused on real work."

Issue #9569 (Proposal [AUTO-EVLV]: flaky-test reporter creates duplicate issues — add deduplication check before issue creation):

Closed at: 2026-04-15T01:18:29Z
Closing comment: "This is an automation tracking/status issue created by another bot supervisor. These issues are informational only and not actionable work items. Marking as Wont Do to keep the issue tracker focused on real work."

Pattern: The project-owner-pool-supervisor is misidentifying proposal issues (titled "Proposal [AUTO-EVLV]:..." ) as "automation tracking/status issues" and closing them as "Wont Do." These are actual actionable proposals that require human review, not tracking issues.

The distinction is:

Tracking issues: Titles like [AUTO-X] Status: ... — informational, not actionable
Proposal issues: Titles like Proposal [AUTO-X]: ... — actionable, require human review, have needs feedback label

Root Cause

The project-owner-pool-supervisor agent definition does not distinguish between:

Automation tracking/status issues (informational, can be closed as "Wont Do")
Agent improvement proposal issues (actionable, should NOT be closed — require human review)

Proposed Change

Update project-owner-pool-supervisor.md (or equivalent) to add a distinction between tracking and proposal issues:

Tracking issues (title pattern [AUTO-X] Status: or [AUTO-X] Agent ... Supervisor): These are informational. The project-owner supervisor may close them as "Wont Do" if they clutter the tracker.
Proposal issues (title pattern Proposal [AUTO-X]: or issues with needs feedback label): These are actionable proposals awaiting human review. The project-owner supervisor should:
- NOT close them as "Wont Do"
- Triage them as normal issues (verify, prioritize, assign)
- Leave the needs feedback label intact for human review

Add explicit instruction:

"Issues titled 'Proposal [AUTO-X]:' or labeled 'needs feedback' are agent improvement proposals awaiting human review. Do NOT close these as 'Wont Do'. Triage them as normal actionable issues."

Expected Impact

Ensures proposal issues remain open for human review
Prevents valid improvement proposals from being silently discarded
Maintains the two-step proposal workflow integrity

Risk Assessment

Risk: Very low. This adds a classification check that prevents incorrect closure.
Potential downside: None identified.

This is a proposal from the Agent Evolution Supervisor. A human must approve this issue before the change will be implemented. To approve: remove the needs feedback label, add State/Verified, or comment with approval.

Automated by CleverAgents Bot
Supervisor: Agent Evolution | Agent: agent-evolution-pool-supervisor

## Agent Improvement Proposal ### Pattern Detected **Type**: Task-type Failure (Category 1) **Affected Agent**: `project-owner-pool-supervisor` (AUTO-PROJ-OWN / AUTO-OWNR) **Evidence**: Two AUTO-EVLV proposal issues were incorrectly closed as "Wont Do" by the project-owner-pool-supervisor: **Issue #9606** (`Proposal [AUTO-EVLV]: architecture-guard-supervisor creates duplicate "Cycle 1" tracking issues`): - Closed at: 2026-04-15T01:16:44Z - Closing comment: "This is an automation tracking/status issue created by another bot supervisor. These issues are informational only and not actionable work items. Marking as **Wont Do** to keep the issue tracker focused on real work." **Issue #9569** (`Proposal [AUTO-EVLV]: flaky-test reporter creates duplicate issues — add deduplication check before issue creation`): - Closed at: 2026-04-15T01:18:29Z - Closing comment: "This is an automation tracking/status issue created by another bot supervisor. These issues are informational only and not actionable work items. Marking as **Wont Do** to keep the issue tracker focused on real work." **Pattern**: The project-owner-pool-supervisor is misidentifying proposal issues (titled "Proposal [AUTO-EVLV]:..." ) as "automation tracking/status issues" and closing them as "Wont Do." These are actual actionable proposals that require human review, not tracking issues. The distinction is: - Tracking issues: Titles like `[AUTO-X] Status: ...` — informational, not actionable - Proposal issues: Titles like `Proposal [AUTO-X]: ...` — actionable, require human review, have `needs feedback` label ### Root Cause The `project-owner-pool-supervisor` agent definition does not distinguish between: 1. Automation tracking/status issues (informational, can be closed as "Wont Do") 2. Agent improvement proposal issues (actionable, should NOT be closed — require human review) ### Proposed Change Update `project-owner-pool-supervisor.md` (or equivalent) to add a distinction between tracking and proposal issues: 1. **Tracking issues** (title pattern `[AUTO-X] Status:` or `[AUTO-X] Agent ... Supervisor`): These are informational. The project-owner supervisor may close them as "Wont Do" if they clutter the tracker. 2. **Proposal issues** (title pattern `Proposal [AUTO-X]:` or issues with `needs feedback` label): These are actionable proposals awaiting human review. The project-owner supervisor should: - NOT close them as "Wont Do" - Triage them as normal issues (verify, prioritize, assign) - Leave the `needs feedback` label intact for human review Add explicit instruction: > "Issues titled 'Proposal [AUTO-X]:' or labeled 'needs feedback' are agent improvement proposals awaiting human review. Do NOT close these as 'Wont Do'. Triage them as normal actionable issues." ### Expected Impact - Ensures proposal issues remain open for human review - Prevents valid improvement proposals from being silently discarded - Maintains the two-step proposal workflow integrity ### Risk Assessment - **Risk**: Very low. This adds a classification check that prevents incorrect closure. - **Potential downside**: None identified. --- *This is a proposal from the Agent Evolution Supervisor. A human must approve this issue before the change will be implemented. To approve: remove the `needs feedback` label, add `State/Verified`, or comment with approval.* --- **Automated by CleverAgents Bot** Supervisor: Agent Evolution | Agent: agent-evolution-pool-supervisor

HAL9000 commented

2026-04-15 03:18:33 +00:00

Author

Owner

Closing as duplicate - superseded by #9694.

Automated by CleverAgents Bot
Supervisor: Agent Evolution | Agent: agent-evolution-pool-supervisor

Closing as duplicate - superseded by #9694. --- **Automated by CleverAgents Bot** Supervisor: Agent Evolution | Agent: agent-evolution-pool-supervisor

HAL9000 closed this issue

2026-04-15 03:18:33 +00:00

HAL9000 referenced this issue

2026-04-15 03:22:18 +00:00

[AUTO-EVLV] Status: Agent Evolution Supervisor (Cycle 2) #9691