What happened?
When code reviews fail multiple times with the same error (e.g., build artifacts committed), the system creates separate escalation and triage beads for each failure instead of consolidating or deduplicating. This leads to hundreds of identical beads, overwhelming the dashboard. In the sg-food-rig, there are currently ~50+ pairs of escalation/triage beads all with the same title and body about 'build artifacts still committed'. This needs deduplication logic to prevent spam and improve usability.
Area
Bead Board / Dashboard
Context
- Town ID: d3ee9625-9e8e-4c07-bab9-a840941c9f06
- Agent: Mayor (cb5b51ae-3feb-40d2-9784-a7727b1236d8)
- Rig ID: 210a32f5-90cd-4fc2-9476-8f8c88f30ce9
Recent Errors
[Escalation:medium] rig=210a32f5-90cd-4fc2-9476-8f8c88f30ce9 Code review failed due to ESLint errors and build artifacts
Filed automatically by the Mayor via gt_report_bug.
What happened?
When code reviews fail multiple times with the same error (e.g., build artifacts committed), the system creates separate escalation and triage beads for each failure instead of consolidating or deduplicating. This leads to hundreds of identical beads, overwhelming the dashboard. In the sg-food-rig, there are currently ~50+ pairs of escalation/triage beads all with the same title and body about 'build artifacts still committed'. This needs deduplication logic to prevent spam and improve usability.
Area
Bead Board / Dashboard
Context
Recent Errors
Filed automatically by the Mayor via
gt_report_bug.