[FEATURE] UI Leaderboard should indicate the total assessments count with the submission score

[kami619]

Problem Statement

With the fix for issue #309, leaderboard submissions can now include assessments with fewer than 25 attributes (when --exclude is used). However, users viewing the leaderboard have no way to know if a submission used exclusions, making it difficult to compare scores fairly.

Proposed Solution

Add a visual indicator on the leaderboard UI to show when a submission has excluded attributes. This could be:

• A badge or icon next to the score (e.g., "22/25 attributes")
• A tooltip explaining which attributes were excluded
• A filter option to show only full assessments (25/25)

Alternatives Considered

1. Reject exclusions for leaderboard — Too restrictive; some attributes may not apply to all projects
2. Separate leaderboards — Full vs. partial assessments; adds complexity
3. Score normalization — Adjust scores based on attributes assessed; could be misleading

Use Cases

1. User wants to compare their full assessment against others and filter out partial submissions
2. User wants to understand why a project has a high score with fewer attributes
3. Maintainer wants to identify trends in which attributes are commonly excluded

Additional Context

Related to issue #309 (schema validation fix) which enabled partial assessments to be submitted.

The attributes_total and attributes_assessed fields are already present in the assessment JSON, so no data changes are needed — only UI updates.

Acceptance Criteria

• Leaderboard shows attribute count (e.g., "22/25") for each submission
• Submissions with < 25 attributes have a visual indicator (badge, icon, or color)
• Optional: Filter to show only full assessments (25/25)
• Optional: Tooltip showing which attributes were excluded (if available in metadata)

Priority

• Medium (nice to have)

[github-actions]

👋 This issue has been inactive for 21 days and will be closed in 7 days if there is no further activity.

If this issue is still relevant, please:

• Add a comment with updates
• Remove the stale label
• Add the pinned label to prevent future stale marking

Thank you for your contributions to AgentReady!

[github-actions]

🔒 This issue has been automatically closed due to 28 days of inactivity.

If you believe this issue should remain open, please reopen it and provide an update.

[kami619]

Analysis: This feature isn't needed

After investigating the implementation, we found that the concern raised here — that partial assessments make leaderboard scores unfair to compare — is already addressed by the scoring system.

Key findings

1. Scores are already normalized percentages. The overall_score (0-100) is a weighted average of assessed attributes. A score of 78.6 on 18 attributes is directly comparable to 78.4 on 25 attributes — the scorer accounts for this.

2. attributes_total variation isn't from --exclude. Current submissions show attributes_total values of 18, 22, 23, 25, and 30 — these reflect different rulesets/assessment versions, not users excluding attributes to inflate scores. 15 of 25 submissions use an 18-attribute ruleset.

3. Adding an indicator creates noise, not signal. 17/25 rows would be flagged as "partial," which doesn't help users distinguish anything meaningful. The existing "Ruleset" column already communicates assessment configuration differences.

Recommendation

No UI changes needed. The scoring system already normalizes for different attribute counts, making scores comparable regardless of how many attributes were assessed.

If --exclude abuse becomes an actual problem in the future, a better approach would be to track which attributes were excluded and whether they correlate with score inflation — but there's no evidence of this happening today.

[github-actions]

👋 This issue has been inactive for 21 days and will be closed in 7 days if there is no further activity.

If this issue is still relevant, please:

• Add a comment with updates
• Remove the stale label
• Add the pinned label to prevent future stale marking

Thank you for your contributions to AgentReady!

[github-actions]

🔒 This issue has been automatically closed due to 28 days of inactivity.

If you believe this issue should remain open, please reopen it and provide an update.