[polakamtejas]

What and why

The explorer's verifier tab renders verifiers that are not rubric, sandbox or aggregate shaped (env_outcome_verifier, for one) through a generic panel in task-instance-viewer.tsx. With a task that has two env_outcome_verifier steps (records on weighted_average, db_match on all_pass), that panel had three gaps:

1. No verifier label. The summary row showed only {passed}/{total} checks passed and the score, so two verifiers rendered as two identical-looking blocks ("1/2 checks passed · Score: 0%" twice) with no way to tell which was which. The rubric, sandbox and aggregate cards all show the verifier id; this branch dropped it.
2. Check descriptions hidden. Each check showed r.id and r.message, but env_outcome_verifier checks carry description (the shipped examples/mail-mcp/artifacts/check_mail/verify.py returns one), so their explanation never appeared.
3. Penalties looked like ordinary checks. weighted_average (verifiers/scoring.py) treats a negative weight as a penalty: a failing check with weight -w subtracts w from the weighted sum, and a passing one adds nothing. Nothing marked such a check, so "1/2 checks passed" next to "Score: 0%" read as a contradiction.

What changed

In the generic branch only, no restructuring:

• The summary row ends with the verifier id, styled like the other verifier cards (text-[10px] font-mono text-[var(--muted-foreground)]).
• A check's text is r.message ?? r.description.
• A check with a negative weight gets a small amber penalty −w badge whose tooltip says that when it fails weighted_average subtracts w from the weighted sum.
• The inline result type gains optional description and weight, and message becomes optional, matching what verifiers write.

The aggregator is not persisted with an env_outcome_verifier's output, so the panel can't name it; the tooltip names weighted_average because it is the only aggregator that reads weights.

How it was tested

From src/agent_env/explorer/ui, on Node 20.11 (CI uses 22; npm prints an EBADENGINE warning for eslint-visitor-keys, nothing else):

• npm ci: exit 0
• npm run typecheck: exit 0
• npm run lint: exit 0, 0 errors and 59 warnings, the same 59 as on main (none in the changed lines)
• npm run test:smoke: exit 0, 15 ran, 2 skipped (the two allowed trajectory-fixture capabilities), 0 failed
• npm run build:static: exit 0; the exported CSS includes the new bg-amber-500/10 and text-amber-600 classes

The change is JSX inside TaskInstanceViewer with no pure helper to test, so no smoke test was added (the smokes cover src/lib helpers). It was not checked in a browser.

🤖 Generated with Claude Code

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking correction needed in the penalty tooltip.

Findings

1.  Tooltip overstates partial penalties ▶

Fix with agent prompt

### Issue 1
src/agent_env/explorer/ui/src/components/task-instance-viewer.tsx:1118
For a check with `weight: -2`, `score: 0.5`, and `result: false`, the tooltip says 2 is subtracted from the weighted sum. The actual subtraction is 1: `weighted_average` uses `score`, not `result`, to calculate the penalty. This makes the explanation disagree with the displayed score. Describe the subtraction as `(1 - score) * abs(weight)`, or qualify the current explanation as applying only to binary scores.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The generic verifier panel now shows verifier IDs, falls back to check descriptions, and marks negative weights.

• Generic verifier panels show who ran each check and what it means.

Acknowledged scope: polakamtejas explicitly noted that the aggregator is not saved and intentionally named weighted_average in the tooltip.

_{Reviews (1) · Last reviewed commit: "fix(explorer): label each verifier's res..." · Reviewed by Greptile}

[greptile-apps]

Tooltip overstates partial penalties

For a check with weight: -2, score: 0.5, and result: false, the tooltip says 2 is subtracted from the weighted sum. The actual subtraction is 1: weighted_average uses score, not result, to calculate the penalty. This makes the explanation disagree with the displayed score. Describe the subtraction as (1 - score) * abs(weight), or qualify the current explanation as applying only to binary scores.

Knowledge Base Used: Evaluation, review, and scoring

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/agent_env/explorer/ui/src/components/task-instance-viewer.tsx
Line: 1118

Comment:
**Tooltip overstates partial penalties**

For a check with `weight: -2`, `score: 0.5`, and `result: false`, the tooltip says 2 is subtracted from the weighted sum. The actual subtraction is 1: `weighted_average` uses `score`, not `result`, to calculate the penalty. This makes the explanation disagree with the displayed score. Describe the subtraction as `(1 - score) * abs(weight)`, or qualify the current explanation as applying only to binary scores.

**Knowledge Base Used:** [Evaluation, review, and scoring](https://app.greptile.com/scale-ai/-/custom-context/knowledge-base/scaleapi/agentenv-framework/-/docs/evaluation-and-review.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.