feat: driver assignment drag-and-drop, load matching board, dispute resolution portal, dispute service

[theladyanina]

Summary

Closes #834
Closes #838
Closes #842
Closes #845

Implements four assigned issues following this repo's Component -> Hook -> Service layering.

#834: DriverAssignmentPanel (drag-and-drop shipment assignment)

• types/driverAssignment.ts, services/driverAssignmentService.ts, hooks/useDriverAssignment.ts, components/fleet/DriverAssignmentPanel.tsx
• Built on @dnd-kit/core (added as a dependency; named in the issue's technical scope but not previously installed). Pending shipments render as draggable cards, drivers as drop zones. Dropping a shipment on a driver opens a confirmation modal before the assignment API call fires, and a success notification appears afterward. Falls back to a stacked list layout on mobile (lg:hidden / hidden lg:grid) instead of the drag-and-drop grid.

#838: BiddingBoard (courier load matching with bid negotiation)

• types/loadMatching.ts, services/loadMatchingService.ts, hooks/useLoadMatching.ts, components/driver/BiddingBoard.tsx
• Board of bulk delivery contracts (cargo type, route, timeline, base rate) with a custom bid form (numeric validation on amount, required timeline) and a cargo type / region / rate-range filter bar. The underlying TanStack Query hook uses keepPreviousData, so the filter bar and existing results stay visible while a new filter combination loads rather than the whole board unmounting to a loading state on every filter change. Once a bid exists for a contract, its status badge (submitted/accepted/rejected/expired) replaces the bid form.

#842: DisputeResolutionPortal + EvidenceDropzone (evidence upload media dropzone)

• components/escrow/DisputeResolutionPortal.tsx, components/escrow/EvidenceDropzone.tsx
• Multi-step flow (issue selection -> evidence upload -> confirmation) using react-dropzone (already a declared dependency in package.json, just not yet installed) for drag-and-drop or click-to-upload of images and video up to 10MB, with previews and per-file removal. Shows a prominent escrow-freeze warning before submission and the assigned case ID afterward.

#845: disputeService

• types/dispute.ts, services/disputeService.ts, hooks/useDisputeCase.ts
• fileDispute, uploadEvidence (axios onUploadProgress wired to a 0-100 percentage callback), freezeEscrow, getDisputeStatus, resolveDispute, each typed and each rejecting with a normalized APIError ({ message, statusCode, code }) instead of a raw axios error, per the issue's acceptance criteria.

Also included: ThemeToggle fix (blocking issue for screenshots)

components/ui/ThemeToggle.tsx imported hooks/useTheme.ts, which calls methods that don't exist on services/themeService.ts, and whose own return shape doesn't match what ThemeToggle destructures. Since ThemeToggle is rendered from app/layout.tsx, this broke every route in both dev and prod. Redirected ThemeToggle to import useTheme from the next-themes package instead, matching what components/shared/ThemeProvider.tsx already uses elsewhere in the app. hooks/useTheme.ts and services/themeService.ts themselves are untouched; they're orphaned, dead code and fixing them is out of scope here. (This is the same fix as a companion PR on this same upstream repo, since both hit the identical pre-existing break.)

Pre-existing issues found (not fixed, out of scope for this PR)

• app/page.tsx has an unbalanced JSX tag that fails both next build and tsc --noEmit, blocking production builds for the entire repo even after the ThemeToggle fix above. Reproduced on a clean checkout of this branch's base commit, unrelated to any file touched here.
• escrow/DisputeForm.tsx / hooks/useDisputeForm.ts / services/escrowService.ts are broken due to a missing stellar-sdk dependency. The new dispute-resolution code in this PR does not build on that precedent.

Test plan

• npx jest on all new/touched test files: 9 suites, 62 tests passing, 97%+ statement coverage across all new files
• npx tsc --noEmit: no new errors (only the pre-existing, unrelated app/page.tsx and CheckoutFlow.keyboard.test.tsx failures noted above)
• npx eslint: 0 errors on all touched files (a few pre-existing-style warnings from an unused-vars rule flagging documentation-only parameter names in function-type signatures)
• Manually rendered all four new components together in a local preview route (screenshot below) and confirmed no runtime errors; the "Network Error" shown for BiddingBoard there is the intended error-state UI, since this sandbox has no live backend for that endpoint
• Confirmed both pre-existing issues above via git stash against a clean checkout, not introduced by this PR

Screenshots

Test suite passing (62/62, coverage table):

Components rendered (DriverAssignmentPanel, BiddingBoard, DisputeResolutionPortal):

[drips-wave]

@theladyanina Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[johdanike]

Multiple merge conflicts, please resolve.
Thank you for contributing to Swiftchainn

[johdanike]

extensive work done, thanks for contributing to Swiftchainn