Allow for workbench job knowledge capture if > 0 prs merged

[michaeljguarino]

This is enough to indicate something was correct

Test Plan

n/a

Checklist

• If required, I have updated the Plural documentation accordingly.
• I have added tests to cover my changes.
• I have added a meaningful title and summary to convey the impact of this PR to a user.

Plural Flow: console

[greptile-apps]

Greptile Summary

Fixes the previously broken resolved/1 query on WorkbenchJob by replacing the COUNT(CASE WHEN … ELSE 0 END) approach (which always counted every row) with a subquery left-join on merged PRs filtered via a new PullRequest.for_status/2 helper, plus a WHERE pr.id IS NOT NULL guard and DISTINCT to correctly return workbench jobs with at least one merged PR.

Confidence Score: 5/5

Safe to merge — the new query logic is correct and directly addresses the previously flagged bug.

The subquery join pattern correctly identifies workbench jobs with ≥1 merged PR: the for_status(:merged) subquery narrows the joined rows to merged PRs, NOT NULL on pr.id converts the left join to an effective inner join, and distinct: true prevents duplicates for jobs with multiple merged PRs. All changes are small and focused.

No files require special attention.

Important Files Changed

Filename	Overview
lib/console/schema/workbench_job.ex	Rewrites resolved/1 to use a subquery join on merged PRs instead of the broken COUNT-based HAVING clause; logic is correct.
lib/console/schema/pull_request.ex	Adds for_status/2 helper used by the new resolved/1 implementation in WorkbenchJob; clean and consistent with existing patterns.
priv/pr/agent_review.md.eex	Minor cosmetic reordering of parenthetical in the PR review template — no functional impact.

_{Reviews (2): Last reviewed commit: "Allow for workbench job knowledge captur..." | Re-trigger Greptile}

[michaeljguarino]

@greptileai