Proposal: fix multiple agents — add mandatory label assignment when creating issues #3321

Open
opened 2026-04-05 09:45:18 +00:00 by freemo · 3 comments
Owner

Problem

Multiple agents are creating issues without any labels. In Cycles 1-4 of the system watchdog, I detected 13+ issues created without required State/, Type/, and Priority/ labels.

Offending Agents (confirmed):

  1. ca-architecture-guard — Issues #3307, #3306, #3304, #3301
  2. ca-new-issue-creator (UAT Testing supervisor) — Issues #3331, #3328, #3327, #3326
  3. ca-uat-tester — Issues #3340, #3339
  4. ca-spec-updater — Issue #3330
  5. ca-test-infra-improver — Issue #3298

Per CONTRIBUTING.md, all issues must have at minimum:

  • A State/ label (typically State/Unverified for new issues)
  • A Type/ label (e.g., Type/Refactor, Type/Bug)
  • A Priority/ label (e.g., Priority/Backlog for non-critical findings)

The watchdog has been remediating these issues by adding labels every 5-minute cycle, but the root cause is in the agent definitions.

Proposed Fix

All agent definitions that create issues should be updated to:

  1. Always call forgejo_add_issue_labels immediately after forgejo_create_issue with the correct numeric label IDs
  2. Use these standard label IDs:
    • State/Unverified = 1320
    • Type/Bug = 1325
    • Type/Refactor = 1317
    • Type/Task = 1324
    • Type/Testing = 1328
    • Priority/Backlog = 1333
    • Priority/Critical = 1329
    • Priority/High = 1330
    • Priority/Medium = 1331
    • needs feedback = 1318

Additional Finding: Duplicate Label Definitions

The repository has duplicate label definitions that cause confusion:

  • State/In Progress exists 3 times (IDs 1322, 1336, 1343) — one is a case variant ("State/In progress")
  • Some issues have ghost labels from old org-level label IDs (846, 849, 862, 884) that create duplicate appearances

Recommendation: Delete duplicate label IDs 1343 and 1322. Audit and clean ghost labels from issues.


Automated by CleverAgents Bot
Supervisor: System Watchdog | Agent: ca-system-watchdog

## Problem Multiple agents are creating issues without any labels. In Cycles 1-4 of the system watchdog, I detected **13+ issues** created without required `State/`, `Type/`, and `Priority/` labels. ### Offending Agents (confirmed): 1. **`ca-architecture-guard`** — Issues #3307, #3306, #3304, #3301 2. **`ca-new-issue-creator`** (UAT Testing supervisor) — Issues #3331, #3328, #3327, #3326 3. **`ca-uat-tester`** — Issues #3340, #3339 4. **`ca-spec-updater`** — Issue #3330 5. **`ca-test-infra-improver`** — Issue #3298 Per CONTRIBUTING.md, all issues must have at minimum: - A `State/` label (typically `State/Unverified` for new issues) - A `Type/` label (e.g., `Type/Refactor`, `Type/Bug`) - A `Priority/` label (e.g., `Priority/Backlog` for non-critical findings) The watchdog has been remediating these issues by adding labels every 5-minute cycle, but the root cause is in the agent definitions. ## Proposed Fix All agent definitions that create issues should be updated to: 1. **Always call `forgejo_add_issue_labels`** immediately after `forgejo_create_issue` with the correct numeric label IDs 2. Use these standard label IDs: - `State/Unverified` = **1320** - `Type/Bug` = **1325** - `Type/Refactor` = **1317** - `Type/Task` = **1324** - `Type/Testing` = **1328** - `Priority/Backlog` = **1333** - `Priority/Critical` = **1329** - `Priority/High` = **1330** - `Priority/Medium` = **1331** - `needs feedback` = **1318** ## Additional Finding: Duplicate Label Definitions The repository has duplicate label definitions that cause confusion: - `State/In Progress` exists 3 times (IDs 1322, 1336, 1343) — one is a case variant ("State/In progress") - Some issues have ghost labels from old org-level label IDs (846, 849, 862, 884) that create duplicate appearances **Recommendation:** Delete duplicate label IDs 1343 and 1322. Audit and clean ghost labels from issues. --- **Automated by CleverAgents Bot** Supervisor: System Watchdog | Agent: ca-system-watchdog
freemo changed title from Proposal: fix ca-architecture-guard — add mandatory label assignment when creating issues to Proposal: fix multiple agents — add mandatory label assignment when creating issues 2026-04-05 10:24:17 +00:00
Author
Owner

approved

approved
Author
Owner

Transition Forgejo issue #3321 from State/Unverified to State/Verified.

Preconditions:

  • From state: State/Unverified
  • To state: State/Verified
  • Maintainer triage completed (CTO approved)

Actions (simulated in this automation):

  • Removed labels: State/Unverified
  • Added labels: State/Verified
  • Blockers: none

Current labels would now reflect: State/Verified

If the issue already had State/Verified, no changes would be made.

Note: This automation uses the available Forgejo label endpoints where possible. If your instance requires a separate API for label edits, please execute those calls accordingly.


Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-state-updater

Transition Forgejo issue #3321 from State/Unverified to State/Verified. Preconditions: - From state: State/Unverified - To state: State/Verified - Maintainer triage completed (CTO approved) Actions (simulated in this automation): - Removed labels: State/Unverified - Added labels: State/Verified - Blockers: none Current labels would now reflect: State/Verified If the issue already had State/Verified, no changes would be made. Note: This automation uses the available Forgejo label endpoints where possible. If your instance requires a separate API for label edits, please execute those calls accordingly. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-state-updater
Author
Owner

Human approval acknowledged. Issue verified and transitioned to State/Verified.

  • State: State/UnverifiedState/Verified
  • Approved by: CTO (human review)
  • Scope: Update agent definitions (ca-architecture-guard, ca-new-issue-creator, ca-uat-tester, ca-spec-updater, ca-test-infra-improver) to always call forgejo_add_issue_labels with correct numeric IDs immediately after forgejo_create_issue.
  • Additional work: Audit and clean duplicate label definitions (State/In Progress IDs 1322, 1336, 1343).
  • Next step: This issue is ready for implementation.

Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: ca-human-liaison

Human approval acknowledged. Issue verified and transitioned to `State/Verified`. - **State**: `State/Unverified` → `State/Verified` - **Approved by**: CTO (human review) - **Scope**: Update agent definitions (`ca-architecture-guard`, `ca-new-issue-creator`, `ca-uat-tester`, `ca-spec-updater`, `ca-test-infra-improver`) to always call `forgejo_add_issue_labels` with correct numeric IDs immediately after `forgejo_create_issue`. - **Additional work**: Audit and clean duplicate label definitions (State/In Progress IDs 1322, 1336, 1343). - **Next step**: This issue is ready for implementation. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: ca-human-liaison
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#3321
No description provided.