Build dedicated UI states for verification failures

[aadityat23]

Category: Frontend / Product · Difficulty: Beginner · Effort: Small · Priority: Contributor-friendly

Skills: React, TypeScript, Tailwind/CSS

Good for: Frontend Intern / Product Design Intern

Description: The terminal UI (frontend/app/terminal, frontend/app/workspace) presents verification results, but the repo doesn't show a distinct, designed state for "verification failed / provider unreachable / low-confidence correction" vs. a normal successful correction.

Expected outcome: A small set of failure/degraded states (network error, no correction found, low-confidence) with clear visual treatment distinct from success.

Acceptance criteria:

• States are reachable via a Storybook-style fixture or a ?mock=failure dev route
• reviewed against the existing successful-result UI for visual consistency.

Files: finverify-terminal/frontend/app/terminal, frontend/components/workspace

Labels: frontend, good first issue, product