Proposal: improve ca-uat-tester — consolidate progress reports into comments instead of new issues #1483

Closed
opened 2026-04-02 19:30:17 +00:00 by freemo · 6 comments
Owner

Agent Improvement Proposal

Pattern Detected

Type: Workflow fix — issue tracker pollution from progress report spam
Affected Agent: ca-uat-tester (Pool Supervisor Mode)
Evidence: During the current v3.7.0 session (started 2026-04-02T18:44Z), the UAT pool supervisor created 13 separate issues for progress reports in just ~65 minutes:

Issue Title Created
#1453 [UAT-SUPERVISOR] Progress Report — Cycle 11 — v3.7.0 TUI 18:52
#1454 [UAT-SUPERVISOR] Progress Report — Cycle 21 — v3.7.0 TUI 18:55
#1455 [UAT-SUPERVISOR] Progress Report — Cycle 31 — v3.7.0 TUI 18:57
#1456 [UAT-SUPERVISOR] Progress Report — Cycle 41 — v3.7.0 TUI 18:59
#1457 [UAT-SUPERVISOR] Progress Report — Cycle 51 — v3.7.0 TUI 19:01
#1459 [UAT-SUPERVISOR] Progress Report — Cycle 61 — v3.7.0 TUI 19:04
#1460 [UAT-SUPERVISOR] Progress Report — Cycle 71 — v3.7.0 TUI 19:07
#1462 [UAT-SUPERVISOR] Progress Report — Cycle 81 — v3.7.0 TUI 19:10
#1464 [UAT-SUPERVISOR] Progress Report — Cycle 91 — v3.7.0 TUI 19:13
#1467 [UAT-SUPERVISOR] Progress Report — Cycle 101 — v3.7.0 TUI 19:16
#1470 [UAT-SUPERVISOR] Progress Report — Cycle 111 — v3.7.0 TUI 19:19
#1474 [UAT-SUPERVISOR] Progress Report — Cycle 121 — v3.7.0 TUI 19:22
#1477 [UAT-SUPERVISOR] Progress Report — Cycle 131 — v3.7.0 TUI 19:25

Impact: These 13 issues pollute the issue tracker, inflate the open issue count (300+ open issues), and make it harder for humans and other agents to find real bugs and feature requests. At the current rate (~1 issue every 5 minutes), a full session would create 100+ noise issues.

The agent definition (line 178-184) correctly says "post comment on session state issue" but the supervisor is creating new issues instead of posting comments on its launch issue (#1447) or the session state issue (#1458).

Proposed Change

Modify the Pool Supervisor Mode section in ca-uat-tester.md to:

  1. Explicitly require a single tracking issue — at startup, the pool supervisor should create ONE tracking issue (e.g., [UAT-SUPERVISOR] v3.7.0 TUI — Pool Supervisor LAUNCHED) and use it for ALL subsequent progress reports as comments.

  2. Replace the vague "post comment on session state issue" with explicit instructions — specify that progress reports MUST be posted as comments on the supervisor's own tracking issue, NOT as new issues.

  3. Add a warning — "NEVER create a new Forgejo issue for progress reports. Always post as a comment on your tracking issue."

  4. Reduce progress report frequency — change from every 2 cycles (~20 seconds) to every 10 cycles (~100 seconds) to reduce comment volume.

Expected Impact

  • Eliminates 13+ noise issues per hour from the issue tracker
  • Reduces open issue count inflation
  • Consolidates progress history into a single issue's comment thread (easier to review)
  • Reduces Forgejo API load from issue creation

Risk Assessment

  • Very low risk: This change only affects how progress is reported, not what is tested. No testing logic is modified.
  • Potential concern: If the tracking issue is not created at startup (e.g., due to API failure), progress reports would be lost. Mitigated by the existing launch issue (#1447) which can serve as the fallback.

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**: Workflow fix — issue tracker pollution from progress report spam **Affected Agent**: `ca-uat-tester` (Pool Supervisor Mode) **Evidence**: During the current v3.7.0 session (started 2026-04-02T18:44Z), the UAT pool supervisor created **13 separate issues** for progress reports in just ~65 minutes: | Issue | Title | Created | |---|---|---| | #1453 | [UAT-SUPERVISOR] Progress Report — Cycle 11 — v3.7.0 TUI | 18:52 | | #1454 | [UAT-SUPERVISOR] Progress Report — Cycle 21 — v3.7.0 TUI | 18:55 | | #1455 | [UAT-SUPERVISOR] Progress Report — Cycle 31 — v3.7.0 TUI | 18:57 | | #1456 | [UAT-SUPERVISOR] Progress Report — Cycle 41 — v3.7.0 TUI | 18:59 | | #1457 | [UAT-SUPERVISOR] Progress Report — Cycle 51 — v3.7.0 TUI | 19:01 | | #1459 | [UAT-SUPERVISOR] Progress Report — Cycle 61 — v3.7.0 TUI | 19:04 | | #1460 | [UAT-SUPERVISOR] Progress Report — Cycle 71 — v3.7.0 TUI | 19:07 | | #1462 | [UAT-SUPERVISOR] Progress Report — Cycle 81 — v3.7.0 TUI | 19:10 | | #1464 | [UAT-SUPERVISOR] Progress Report — Cycle 91 — v3.7.0 TUI | 19:13 | | #1467 | [UAT-SUPERVISOR] Progress Report — Cycle 101 — v3.7.0 TUI | 19:16 | | #1470 | [UAT-SUPERVISOR] Progress Report — Cycle 111 — v3.7.0 TUI | 19:19 | | #1474 | [UAT-SUPERVISOR] Progress Report — Cycle 121 — v3.7.0 TUI | 19:22 | | #1477 | [UAT-SUPERVISOR] Progress Report — Cycle 131 — v3.7.0 TUI | 19:25 | **Impact**: These 13 issues pollute the issue tracker, inflate the open issue count (300+ open issues), and make it harder for humans and other agents to find real bugs and feature requests. At the current rate (~1 issue every 5 minutes), a full session would create 100+ noise issues. The agent definition (line 178-184) correctly says "post comment on session state issue" but the supervisor is creating new issues instead of posting comments on its launch issue (#1447) or the session state issue (#1458). ### Proposed Change Modify the Pool Supervisor Mode section in `ca-uat-tester.md` to: 1. **Explicitly require a single tracking issue** — at startup, the pool supervisor should create ONE tracking issue (e.g., `[UAT-SUPERVISOR] v3.7.0 TUI — Pool Supervisor LAUNCHED`) and use it for ALL subsequent progress reports as comments. 2. **Replace the vague "post comment on session state issue" with explicit instructions** — specify that progress reports MUST be posted as comments on the supervisor's own tracking issue, NOT as new issues. 3. **Add a warning** — "NEVER create a new Forgejo issue for progress reports. Always post as a comment on your tracking issue." 4. **Reduce progress report frequency** — change from every 2 cycles (~20 seconds) to every 10 cycles (~100 seconds) to reduce comment volume. ### Expected Impact - Eliminates 13+ noise issues per hour from the issue tracker - Reduces open issue count inflation - Consolidates progress history into a single issue's comment thread (easier to review) - Reduces Forgejo API load from issue creation ### Risk Assessment - **Very low risk**: This change only affects how progress is reported, not what is tested. No testing logic is modified. - **Potential concern**: If the tracking issue is not created at startup (e.g., due to API failure), progress reports would be lost. Mitigated by the existing launch issue (#1447) which can serve as the fallback. --- *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
Author
Owner

Approved

Approved
freemo added this to the v3.8.0 milestone 2026-04-02 23:02:37 +00:00
Author
Owner

PR #1545 reviewed, approved, and merged.

The UAT supervisor agent definition has been updated to:

  1. Create ONE tracking issue at startup for all progress reports
  2. Post progress as comments on the tracking issue (never as separate issues)
  3. Reduce report frequency from every 2 cycles to every 10 cycles
  4. Add explicit "NEVER create new issues for progress reports" rule

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

PR #1545 reviewed, approved, and merged. The UAT supervisor agent definition has been updated to: 1. Create ONE tracking issue at startup for all progress reports 2. Post progress as comments on the tracking issue (never as separate issues) 3. Reduce report frequency from every 2 cycles to every 10 cycles 4. Add explicit "NEVER create new issues for progress reports" rule --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
Author
Owner

PR #1545 has been merged successfully. Issue should now be resolved.


Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

PR #1545 has been merged successfully. Issue should now be resolved. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
Author
Owner

PR #1588 has been merged successfully. Issue should now be resolved.


Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

PR #1588 has been merged successfully. Issue should now be resolved. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
Author
Owner

Closing — this proposal has been implemented. PR #1545 (merged) implemented the core change to consolidate UAT supervisor progress reports into comments. PR #1588 (open) is implementing additional improvements. The proposal's primary goal has been achieved.


Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

Closing — this proposal has been implemented. PR #1545 (merged) implemented the core change to consolidate UAT supervisor progress reports into comments. PR #1588 (open) is implementing additional improvements. The proposal's primary goal has been achieved. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
Author
Owner

Milestone compliance fix applied:

  • Assigned to milestone: v3.8.0
  • Reason: Per CONTRIBUTING.md, non-Epic/non-Legendary issues in State/Verified or later MUST have a milestone. This issue was in State/Verified without a milestone and has been assigned to v3.8.0 as the most appropriate active milestone.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

Milestone compliance fix applied: - Assigned to milestone: `v3.8.0` - Reason: Per CONTRIBUTING.md, non-Epic/non-Legendary issues in `State/Verified` or later MUST have a milestone. This issue was in `State/Verified` without a milestone and has been assigned to `v3.8.0` as the most appropriate active milestone. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
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#1483
No description provided.