Render the click (UBI) bucket in the judgment-list source-breakdown card

[SoundMindsAI]

Summary

A judgment list generated from UBI (or hybrid UBI+LLM) carries a non-zero source_breakdown.click count, but the judgment-list header's source-breakdown card renders only the llm and human buckets. The click bucket is silently dropped, so operators reviewing a UBI list can't see how many judgments came from real click behaviour — which is the whole point of the UBI path.

The data is already on the wire (_SourceBreakdown.click, added by feat_ubi_judgments); this is purely a display gap. The generated type's own doc comment already claims "the UI's source-breakdown card now renders all three buckets separately" — this issue makes that true.

Where

• ui/src/components/judgments/judgment-list-header.tsx — renders source_breakdown.llm and source_breakdown.human; add source_breakdown.click.

Fix

1. Add a third badge for the click bucket alongside llm and human, reusing the existing per-bucket styling. Suggested label: "UBI clicks".
2. Update/extend the component's vitest to assert the click bucket renders.

Definition of done

• Source-breakdown card shows all three buckets (llm / human / UBI clicks)
• vitest covers a list with a non-zero click count
• cd ui && pnpm lint && pnpm test pass

Background

Captured at docs/00_overview/planned_features/02_mvp2/bug_judgment_header_omits_click_bucket/idea.md.

Good first issue: frontend-only, single component + test, no backend changes.

[SoundMindsAI]

Advanced Idea → Plan — a cross-model-reviewed feature spec + implementation plan landed via #413 (merged 69af77eb, 2026-06-02). 2 stories / 1 epic, frontend-only (vitest + real-backend Playwright). The click bucket is already on the wire and in types.ts — pure render gap. GPT-5.5: spec 2 cycles 4/4 accepted, plan 1 clean cycle.

Artifacts:

• Spec: docs/00_overview/planned_features/02_mvp2/bug_judgment_header_omits_click_bucket/feature_spec.md
• Plan: docs/00_overview/planned_features/02_mvp2/bug_judgment_header_omits_click_bucket/implementation_plan.md

This is now ready to implement:

/impl-execute docs/00_overview/planned_features/02_mvp2/bug_judgment_header_omits_click_bucket/implementation_plan.md --all

No source code or migration was written — planning artifacts only.

[SoundMindsAI]

Shipped — finalized at docs/00_overview/implemented_features/2026_06_05_bug_judgment_header_omits_click_bucket/. Closing as completed (tracking-issue close-on-merge was missed at merge time; backfilled during a planned_features↔issues reconciliation).