[WIP] Build review UI for imported data usability

[Copilot]

Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>feat(ingestion): review UI — import, merchant merge, recurring, category correction</issue_title>
<issue_description>## Summary
Build the review UI that makes imported data usable. Without review, raw imports are just noise.

Four Review Flows

1. Import Review

• Show imported transactions grouped by import session
• Highlight parse errors, duplicates, unmapped accounts
• Allow user to fix/skip/retry individual rows
• Design-dojo components: Table, StatusBar, Dialog, Toast

2. Merchant Merge Review

• Show resolution candidates: raw description → suggested merchant
• Confidence indicator (high/medium/low)
• Accept, reject, or manually set merchant
• Merge duplicate merchants
• Design-dojo components: Input (search), Toggle, Button

3. Recurring Detection Review

• Show detected recurring series with pattern info
• Accept as subscription/bill/income, reject, or adjust
• Show next expected date and amount
• Design-dojo components: Toggle, Text, Tooltip

4. Category Correction Review

• Show categorized transactions
• Allow re-categorization (single or bulk)
• Learn from corrections (feed back to resolution)
• Design-dojo components: Select, ContextMenu, Button

Acceptance

• All four review flows functional with design-dojo components
• User corrections persist and feed back to resolution engine
• Review state tracked (pending/reviewed/skipped)</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes feat(ingestion): review UI — import, merchant merge, recurring, category correction #65

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[kayodebristol]

Closing this PR to enforce the 1-PR-per-repo rule. Only one Copilot PR is allowed per repository at a time. The oldest PR (#48) will be kept active.