Evaluation: Display overall score summary

Open
#271 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
70/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start at the run detail page and inspect how v1 and v2 run data is currently rendered, especially the score fields. Done means the page shows the overall score and breakdown, displays the AI summary when available, and remains usable when the summary is null or overall data is absent.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem?
v2 runs include score.overall and an ai_summary for identifying the weakest questions, but these are not displayed on the run detail page. This makes it difficult for users to quickly assess the overall performance of their runs.

Describe the solution you'd like

  • Display score.overall at the top of the run detail page, including overall_score, verdict, and breakdown (score, weight, delta, verdict)
  • Show ai_summary as a diagnostic note above the per-row table
  • Ensure graceful degradation when ai_summary is null or when overall is absent on v1 runs
Original issue

Is your feature request related to a problem?
v2 runs carry score.overall — a weighted rollup across the judge metrics plus a natural-language ai_summary pointing at the worst questions. Today the run detail page shows neither, so the reader has to eyeball three metrics and every row to work out how the run went.

Describe the solution you'd like

  • Render score.overall at the top of the run detail page: overall_score, verdict, and the per-metric breakdown (score, weight, delta, verdict)
  • Render ai_summary as a diagnostic note above the per-row table
  • Degrade gracefully when ai_summary is null (best-effort, never fails the run) or when overall is absent on v1 runs

Parent: #265

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
10h 40m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ProjectTech4DevAI/kaapi-frontend

All issues in ProjectTech4DevAI/kaapi-frontend

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.