Proposal: improve multiple agents — enforce required label set (Type/Automation, State/In Progress, Priority/Medium) on all automation tracking issues #5004

New issue

Open

opened 2026-04-09 00:43:47 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 00:43:47 +00:00

Owner

Agent Improvement Proposal

Pattern Detected

Type: workflow_fix
Affected Agents: product-builder, backlog-groomer, human-liaison, system-watchdog, and other agents creating tracking issues
Evidence: Multiple automation tracking issues are missing required labels (Type/Automation, State/In Progress, Priority/Medium)

Detailed Evidence

During the current build session (started 2026-04-09), several automation tracking issues are missing the required label set:

Issue	Title	Labels Present	Missing
#4982	[AUTO-PROD-BLDR] Product Builder Status (Cycle 2)	`Automation Tracking` only	`Type/Automation`, `State/In Progress`, `Priority/Medium`
#4983	[AUTO-LIAISON] Human Liaison Status (Cycle 1)	`[]`	ALL labels
#4968	[AUTO-WATCHDOG] System Health Report (Cycle 1)	`Priority/Medium`, `State/In Progress`, `Type/Automation`	`Automation Tracking`

The required label set for ALL automation tracking issues is:

Automation Tracking — for discoverability by other agents
Type/Automation — for type classification
State/In Progress — to indicate active automation
Priority/Medium — default priority for tracking issues

Root Cause Analysis:

Each agent has its own tracking issue creation function, and they apply labels inconsistently. Some apply only Automation Tracking, others apply Type/Automation + State/In Progress + Priority/Medium but forget Automation Tracking, and some apply no labels at all.

The create_tracking_issue() functions in each agent's definition use PUT /labels with only ["Automation Tracking"] — they don't include the full required set.

Impact:

Agents that search for tracking issues by label may miss issues with incomplete labels
System watchdog label compliance checks flag these as violations
Inconsistent label sets make it harder to filter and monitor automation health

Proposed Change

Update the tracking issue creation functions in ALL agents that create automation tracking issues to apply the full required label set:

# CORRECT: Apply ALL required labels to tracking issues
curl -s -X PUT "https://git.cleverthis.com/api/v1/repos/$owner/$repo/issues/$issue_number/labels" \
  -H "Authorization: token $FORGEJO_PAT" \
  -H "Content-Type: application/json" \
  -d '{"labels": [1398, 1397, 843, 860]}'
  # 1398 = Automation Tracking
  # 1397 = Type/Automation
  # 843 = State/In Progress
  # 860 = Priority/Medium

Agents to update:

product-builder.md — tracking issue creation
backlog-groomer.md — tracking issue creation
human-liaison.md — tracking issue creation
system-watchdog.md — tracking issue creation
implementation-orchestrator.md — tracking issue creation
continuous-pr-reviewer.md — tracking issue creation
uat-tester.md — tracking issue creation
bug-hunter.md — tracking issue creation
test-infra-improver.md — tracking issue creation
agent-evolver.md — tracking issue creation (self-improvement)

The fix is the same in each: change the labels array from ["Automation Tracking"] to the full set [1398, 1397, 843, 860] (using numeric IDs for reliability).

Expected Impact

All automation tracking issues will have consistent, complete label sets
System watchdog label compliance checks will pass
Agents searching for tracking issues by label will find all relevant issues
Monitoring and filtering of automation health becomes more reliable

Risk Assessment

Very low risk: Adding labels to tracking issues is purely additive
No functional impact: Labels don't affect issue content or agent behavior
Idempotent: Applying labels that are already applied is a no-op
Label IDs are stable: The numeric IDs (1397, 1398, 843, 860) are org-level labels that don't change

This is a proposal from the agent evolver. 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 Evolver | Agent: agent-evolver

## Agent Improvement Proposal ### Pattern Detected **Type**: workflow_fix **Affected Agents**: `product-builder`, `backlog-groomer`, `human-liaison`, `system-watchdog`, and other agents creating tracking issues **Evidence**: Multiple automation tracking issues are missing required labels (Type/Automation, State/In Progress, Priority/Medium) ### Detailed Evidence During the current build session (started 2026-04-09), several automation tracking issues are missing the required label set: | Issue | Title | Labels Present | Missing | |-------|-------|----------------|---------| | #4982 | [AUTO-PROD-BLDR] Product Builder Status (Cycle 2) | `Automation Tracking` only | `Type/Automation`, `State/In Progress`, `Priority/Medium` | | #4983 | [AUTO-LIAISON] Human Liaison Status (Cycle 1) | `[]` | ALL labels | | #4968 | [AUTO-WATCHDOG] System Health Report (Cycle 1) | `Priority/Medium`, `State/In Progress`, `Type/Automation` | `Automation Tracking` | The required label set for ALL automation tracking issues is: - `Automation Tracking` — for discoverability by other agents - `Type/Automation` — for type classification - `State/In Progress` — to indicate active automation - `Priority/Medium` — default priority for tracking issues **Root Cause Analysis:** Each agent has its own tracking issue creation function, and they apply labels inconsistently. Some apply only `Automation Tracking`, others apply `Type/Automation` + `State/In Progress` + `Priority/Medium` but forget `Automation Tracking`, and some apply no labels at all. The `create_tracking_issue()` functions in each agent's definition use `PUT /labels` with only `["Automation Tracking"]` — they don't include the full required set. **Impact:** - Agents that search for tracking issues by label may miss issues with incomplete labels - System watchdog label compliance checks flag these as violations - Inconsistent label sets make it harder to filter and monitor automation health ### Proposed Change Update the tracking issue creation functions in ALL agents that create automation tracking issues to apply the full required label set: ```bash # CORRECT: Apply ALL required labels to tracking issues curl -s -X PUT "https://git.cleverthis.com/api/v1/repos/$owner/$repo/issues/$issue_number/labels" \ -H "Authorization: token $FORGEJO_PAT" \ -H "Content-Type: application/json" \ -d '{"labels": [1398, 1397, 843, 860]}' # 1398 = Automation Tracking # 1397 = Type/Automation # 843 = State/In Progress # 860 = Priority/Medium ``` Agents to update: 1. `product-builder.md` — tracking issue creation 2. `backlog-groomer.md` — tracking issue creation 3. `human-liaison.md` — tracking issue creation 4. `system-watchdog.md` — tracking issue creation 5. `implementation-orchestrator.md` — tracking issue creation 6. `continuous-pr-reviewer.md` — tracking issue creation 7. `uat-tester.md` — tracking issue creation 8. `bug-hunter.md` — tracking issue creation 9. `test-infra-improver.md` — tracking issue creation 10. `agent-evolver.md` — tracking issue creation (self-improvement) The fix is the same in each: change the labels array from `["Automation Tracking"]` to the full set `[1398, 1397, 843, 860]` (using numeric IDs for reliability). ### Expected Impact - All automation tracking issues will have consistent, complete label sets - System watchdog label compliance checks will pass - Agents searching for tracking issues by label will find all relevant issues - Monitoring and filtering of automation health becomes more reliable ### Risk Assessment - **Very low risk**: Adding labels to tracking issues is purely additive - **No functional impact**: Labels don't affect issue content or agent behavior - **Idempotent**: Applying labels that are already applied is a no-op - **Label IDs are stable**: The numeric IDs (1397, 1398, 843, 860) are org-level labels that don't change --- *This is a proposal from the agent evolver. 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 Evolver | Agent: agent-evolver

Rows
Columns