Agent batch system

[Jumongweb]

Summary

Closes #223

Completes the agent badge system by wiring badge awards into the live XP, quest, and task-completion flows, persisting earned badges per agent, and rendering badges on the agent detail page with hover tooltips.

What changed

• Implemented all 5 badge types in lib/agents/badges.ts
  • first_task
  • quest_master
  • level_10
  • veteran
  • top_earner
• Kept badge persistence in .data/badges/[agentId].json
• Ensured badges are only awarded once per agent
• Added automatic quest-triggered badge evaluation in lib/gamification/quests.ts
• Added recordTaskCompletion() in lib/reputation/reputation-store.ts
• Wired task completion updates into:
  • lib/agent-runtime/agent.ts
  • app/agent-functions/[id]/route.ts
  • app/api/agents/[id]/tasks/drain/route.ts
• Fixed the first_task condition so it depends on actual completed tasks rather than any XP gain
• Corrected default reputation metrics for new agents to start from 0 completed tasks
• Exposed badges through GET /api/agents/[id]/badges as:
  • { badges: Badge[], count: number }
• Updated the agent detail page to display earned badges as an icon grid with hover tooltips

Testing

Added/updated tests covering:

• badge conditions for all supported badge types
• badges not being awarded twice
• automatic first_task awarding on task completion
• automatic quest_master awarding after the fifth completed quest
• preventing first_task from being awarded by quest XP alone

Proof

This issue requires visual proof for review.
Please attach a short demo video or screenshots showing:

• badges being returned from /api/agents/[id]/badges
• badges appearing on the agent detail page
• automatic awarding after task / quest / level milestones

[leocagli]

Hi @Jumongweb 👋 — two things before this can be reviewed/merged:

1. Required check failing: Typecheck, tests, build, and guards fails (Playwright E2E also red). Check the logs and fix.
2. Missing evidence: please add a video or screenshots showing the agent batch feature working end-to-end.

Happy to merge once both are green. 🙏

[leocagli]

Hi @Jumongweb 👋 — quick update: video/screenshots are not required to merge anymore, just a bonus — if you add one it'll be considered for GrantFox rewards on this issue. So I'll review this on code + checks alone now. 🙏

[Jumongweb]

I have added the screenshot.

[Jumongweb]

Please merge

[leocagli]

Needs a rebase — and that is our fault, not yours

We just merged a batch of PRs that had been waiting far too long for review. Yours was in that batch and was green, but the merges ahead of it touched overlapping files, so this branch now conflicts with main.

To get it in:

git fetch origin
git rebase origin/main
# resolve conflicts, then
git push --force-with-lease

Once CI goes green again, comment here and it gets merged — no second review round needed for the parts that were already approved.

Sorry for the churn. The delay that caused this was on our side: this PR sat for weeks while other work landed on top of it.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud