cleveragents/cleveragents-core

Fork 3

Proposal: fix ca-architecture-guard — add explicit label instructions when creating issues #3244

New issue

Closed

opened 2026-04-05 08:26:40 +00:00 by freemo · 2 comments

freemo commented

2026-04-05 08:26:40 +00:00

Owner

Agent Improvement Proposal

Pattern Detected

Type: Prompt improvement — label compliance enforcement
Affected Agent: ca-architecture-guard
Evidence: System Watchdog report on issue #3197 (cycle 1) states:

"ca-architecture-guard consistently creates issues without labels. The backlog groomer is also fixing these in parallel."

Specifically, the watchdog had to fix 5 issues created by ca-architecture-guard that were missing ALL required labels:

Issue #3170
Issue #3168
Issue #3166
Issue #3181
Issue #3183

All were created without State/, Type/, or Priority/ labels, violating CONTRIBUTING.md requirements.

Root Cause Analysis

The ca-architecture-guard.md agent definition instructs the agent to "create a Forgejo issue (Type/Refactoring, appropriate priority, State/Unverified)" in its scanning loop, but:

The agent only has ca-ref-reader as a task permission — it cannot invoke ca-new-issue-creator which has built-in label enforcement
The agent creates issues via direct Forgejo API calls (bash curl), but the instructions don't explicitly tell it to use forgejo_add_issue_labels or include labels in the API call
The Forgejo create_issue API does not automatically add labels — they must be added separately

Proposed Change

Add an explicit "Label Requirements" section to ca-architecture-guard.md that instructs the agent to add all three required labels immediately after creating each issue:

Add a clear instruction block after the "For each finding: create a Forgejo issue" step:

After creating each issue, IMMEDIATELY add these labels via the Forgejo API:
- `State/Unverified` — every new issue starts unverified
- `Type/Refactor` (or `Type/Bug` for bugs) — matching the finding type
- `Priority/Backlog` — architecture guard findings are non-blocking

Use `forgejo_add_issue_labels` or the equivalent curl API call.

Add a post-creation verification step:

After adding labels, verify the issue has all three required labels
by re-reading it. If any label is missing, retry the label addition.

Expected Impact

Eliminates the persistent pattern of unlabeled issues from ca-architecture-guard
Reduces remediation work by the watchdog and backlog groomer
Ensures all architecture guard findings are immediately triageable

Risk Assessment

Very low risk: Only adds label instructions to issue creation. Does not modify scanning logic, analysis behavior, or any other agent.
No downside: Correctly labeled issues are always better than unlabeled ones.

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: ca-agent-evolver

## Agent Improvement Proposal ### Pattern Detected **Type**: Prompt improvement — label compliance enforcement **Affected Agent**: `ca-architecture-guard` **Evidence**: System Watchdog report on issue #3197 (cycle 1) states: > "ca-architecture-guard consistently creates issues without labels. The backlog groomer is also fixing these in parallel." Specifically, the watchdog had to fix 5 issues created by ca-architecture-guard that were missing ALL required labels: - Issue #3170 - Issue #3168 - Issue #3166 - Issue #3181 - Issue #3183 All were created without `State/`, `Type/`, or `Priority/` labels, violating CONTRIBUTING.md requirements. ### Root Cause Analysis The `ca-architecture-guard.md` agent definition instructs the agent to "create a Forgejo issue (Type/Refactoring, appropriate priority, State/Unverified)" in its scanning loop, but: 1. The agent only has `ca-ref-reader` as a task permission — it cannot invoke `ca-new-issue-creator` which has built-in label enforcement 2. The agent creates issues via direct Forgejo API calls (bash curl), but the instructions don't explicitly tell it to use `forgejo_add_issue_labels` or include labels in the API call 3. The Forgejo `create_issue` API does not automatically add labels — they must be added separately ### Proposed Change Add an explicit "Label Requirements" section to `ca-architecture-guard.md` that instructs the agent to add all three required labels immediately after creating each issue: 1. Add a clear instruction block after the "For each finding: create a Forgejo issue" step: ``` After creating each issue, IMMEDIATELY add these labels via the Forgejo API: - `State/Unverified` — every new issue starts unverified - `Type/Refactor` (or `Type/Bug` for bugs) — matching the finding type - `Priority/Backlog` — architecture guard findings are non-blocking Use `forgejo_add_issue_labels` or the equivalent curl API call. ``` 2. Add a post-creation verification step: ``` After adding labels, verify the issue has all three required labels by re-reading it. If any label is missing, retry the label addition. ``` ### Expected Impact - Eliminates the persistent pattern of unlabeled issues from ca-architecture-guard - Reduces remediation work by the watchdog and backlog groomer - Ensures all architecture guard findings are immediately triageable ### Risk Assessment - **Very low risk**: Only adds label instructions to issue creation. Does not modify scanning logic, analysis behavior, or any other agent. - **No downside**: Correctly labeled issues are always better than unlabeled ones. --- *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: ca-agent-evolver

freemo referenced this issue

2026-04-05 08:30:25 +00:00

[CA-AUTO] Human Liaison — Session Tracker — 2026-04-05 #3177

freemo referenced this issue

2026-04-05 09:08:33 +00:00

[CA-AUTO] Backlog Groomer — Session Tracker — groomer-1 — 2026-04-05 #3182

freemo referenced this issue

2026-04-05 09:42:40 +00:00

Task: System Watchdog session state — 2026-04-05 #3120

freemo referenced this issue

2026-04-05 09:50:04 +00:00

[CA-AUTO] Human Liaison — Session Tracker — 2026-04-05 #3177

freemo referenced this issue

2026-04-05 10:14:37 +00:00

Task: Autonomous build progress report — 2026-04-05 #3075

freemo referenced this issue

2026-04-05 10:20:00 +00:00

Task: System Watchdog session state — 2026-04-05 #3120

freemo referenced this issue

2026-04-05 10:21:42 +00:00

Task: Autonomous build progress report — 2026-04-05 #3075

freemo commented

2026-04-05 14:40:03 +00:00

Author

Owner

There is another issue about this already, search for it and mark one of them as a duplicate and close it, likely this one since the other one no longer has the "needs attention" label. In fact yea, ill close this.

freemo closed this issue

2026-04-05 14:40:03 +00:00

freemo commented

2026-04-05 14:42:04 +00:00

Author

Owner

Acknowledged. The CTO has closed this issue as a duplicate. The broader issue #3321 ("fix multiple agents — add mandatory label assignment when creating issues") covers this same scope and has been approved and verified.

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

freemo referenced this issue

2026-04-05 16:24:04 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3377