feat(client): matching screen step 6 — comparison detail cards

[gilgardosh]

Step 6 of the matching-screen plan (Prompt 6: Comparison Cards). Stacked on #3900.

What

• ChargeDetailCard — the shared visual card for 1:1 side-by-side comparison:
  • Core metadata: date, exact server-formatted amount with currency symbol (rendered as-is, no client-side conversion, per the spec's render rules), counterparty, document type(s), description
  • Document image thumbnail (links to the original file) with a graceful "No document preview" fallback when image is null
  • Expandable "More Details" accordion revealing secondary transactions and misc expenses
  • Optional match-confidence gauge (reuses the existing shared Score component) rendered only when confidenceScore is provided
• Screen split view now renders two ChargeDetailCard instances: the active base charge from useChargeMatchQueue on the left and the top-scoring suggestion (with confidence badge) on the right; empty/completed states preserved
• Shared chargeDate/chargeTitle helpers extracted to utils.ts

Tests

__tests__/charge-detail-card.test.tsx — 4 component tests: exact amount string rendering, missing-image null fallback (no crash), thumbnail rendering, conditional score badge — covering the spec's §5.2 "Render Core" requirements.

Verification

• yarn vitest run --project unit — 4/4 pass
• yarn workspace @accounter/client build passes; lint + prettier clean

🤖 Generated with Claude Code

https://claude.ai/code/session_01JBQoeDJraws6oq8cyxPri3

---

Generated by Claude Code

[gemini-code-assist]

Code Review

This pull request introduces the ChargeDetailCard component to display detailed charge information, including transactions, miscellaneous expenses, and document previews, within a split comparison view on the charge matching review screen. It also extracts utility functions into a separate utils.ts file and adds comprehensive unit tests. The review feedback highlights several important improvements: implementing optional chaining and nullish coalescing to safely handle potentially nullable GraphQL fields, addressing a potential timezone bug in date formatting by specifying UTC, and removing redundant .toString() calls on image and file fields.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.