feat: Use stored session-id to trigger lightweight finding re-evaluation on comment/rebuttal #583
Description
Summary
Now that session-id is stored for some agents, it would be useful to leverage it to trigger a lightweight re-evaluation of a finding when a user has furnished an explanation or rebuttal in the comment before closing.
Motivation
The current workflow when a finding is wrong or doesn't apply is to dismiss and close it. More diligent users will leave a comment explaining why before doing so; but that explanation is a dead end. It's recorded, but never fed back to the agent.
With session-id now available on some agents, there's an opportunity to make that comment actionable: before the finding is closed, the stored session-id could be used to pass the original finding + the user's comment back to the agent for a lightweight re-evaluation scoped to just that finding — without triggering a full re-review.
Proposed Solution
When a user adds a comment on a finding and closes it, roborev could:
- Check if a session-id is stored for that review's agent
- Feed the original finding + comment back to the agent session
- Let the agent update the finding (e.g. retract, downgrade severity, or stand by) before it's closed
Alternatives Considered
- roborev compact — filters false positives against current code but doesn't factor in user-supplied context
- Closing without comment — current default, but loses the rebuttal signal entirely