Description
The miner details page shows PR statistics (merged, open, closed) based on full history instead of the 35-day scoring window. This makes the numbers inconsistent with what the scoring system actually evaluates.
Steps to Reproduce
- Go to the miner details page for any miner
- Look at the PR counts in the Overview tab (credibility tile, donut chart)
- Switch to the Pull Requests tab and check the status counts
- Compare these numbers with what the 35-day scoring window should reflect
Expected Behavior
Users should be able to view PR stats scoped to the 35-day lookback window that the scoring system uses. There should be a filter option to switch between full history and the 35-day window so the numbers match the actual evaluation period.
Actual Behavior
All PR counts (merged, open, closed) show full history with no way to filter by the 35-day scoring window. The credibility chart, score card, and PR table all display all-time totals.
Environment
Additional Context
The individual PR records with timestamps (prCreatedAt) are already available client-side, so the filtering can be handled on the frontend.
The default view can remain as full history, with an option to toggle to the 35-day window.
Description
The miner details page shows PR statistics (merged, open, closed) based on full history instead of the 35-day scoring window. This makes the numbers inconsistent with what the scoring system actually evaluates.
Steps to Reproduce
Expected Behavior
Users should be able to view PR stats scoped to the 35-day lookback window that the scoring system uses. There should be a filter option to switch between full history and the 35-day window so the numbers match the actual evaluation period.
Actual Behavior
All PR counts (merged, open, closed) show full history with no way to filter by the 35-day scoring window. The credibility chart, score card, and PR table all display all-time totals.
Environment
Additional Context
The individual PR records with timestamps (
prCreatedAt) are already available client-side, so the filtering can be handled on the frontend.The default view can remain as full history, with an option to toggle to the 35-day window.