Fix prettier formatting for case status page

[beastoin]

Summary

Run prettier on web/frontend/src/app/case/[ref]/page.tsx to fix CI lint failures from PR #5847.

Test plan

• npx prettier --check passes
• npx eslint passes

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR applies automated Prettier formatting to web/frontend/src/app/case/[ref]/page.tsx to fix CI lint failures introduced in PR #5847. No logic, behaviour, or API surface was changed.

Key formatting changes:

• Long object literals and JSX props expanded to multi-line to respect the configured print-width
• Tailwind CSS utility classes reordered to follow the configured prettier-plugin-tailwindcss canonical sort order (e.g. flex min-h-screen items-center justify-center instead of min-h-screen … flex items-center justify-center)
• Trailing commas added to function arguments and object entries to match the "trailingComma": "all" Prettier config
• No functional, type, or routing changes of any kind

Confidence Score: 5/5

• This PR is safe to merge — it contains only mechanical Prettier formatting changes with zero logic impact.
• Every diff hunk is a pure whitespace/line-wrapping/comma/class-order change produced by the Prettier formatter. No logic, control flow, types, API calls, or component behaviour were altered. The change is fully automated and deterministic.
• No files require special attention.

Important Files Changed

Filename	Overview
web/frontend/src/app/case/[ref]/page.tsx	Pure Prettier reformatting: long lines split, Tailwind classes reordered alphabetically, trailing commas added, JSX attributes expanded to multi-line — no logic or behaviour changes.

Sequence Diagram

sequenceDiagram
    participant Browser
    participant CaseStatusPage as CaseStatusPage (Server Component)
    participant API as API (api.omi.me)

    Browser->>CaseStatusPage: GET /case/[ref]
    CaseStatusPage->>CaseStatusPage: Validate ref format (FU-[hex]{6-12})
    alt Invalid format
        CaseStatusPage-->>Browser: notFound() → 404
    else Valid format
        CaseStatusPage->>API: GET /v1/fair-use/case/{ref}/status (10s timeout, no-store)
        alt 404
            API-->>CaseStatusPage: 404
            CaseStatusPage-->>Browser: "Case Not Found" UI
        else Non-2xx
            API-->>CaseStatusPage: error status
            CaseStatusPage-->>Browser: "Something Went Wrong" UI
        else 200 OK
            API-->>CaseStatusPage: CaseStatus JSON
            CaseStatusPage->>CaseStatusPage: safeEmail(), daysSince(), STAGE_META lookup
            CaseStatusPage-->>Browser: Case Status UI (stage badge, dates, message)
        end
    end

Loading

_{Last reviewed commit: "Fix prettier formatt..."}

[beastoin]

lgtm