[Frontend] Consolidate Duplicate Component Directory Structure

[KuchiMercy]

Summary

The frontend has two parallel component directories: component/ and components/. This creates confusion about where new components should live and leads to inconsistent import paths.

Current State

• component/ contains: dashboard (EscrowCard, EscrowList, Filters, StatusTabs), escrow creation (CreateEscrowWizard, ConditionsList, PartyAcceptanceModal), homepage (Hero, HowItWorks, KeyFeatures), layout (Navbar, Footer), wallet (ConnectWalletModal, WalletButton), and basic UI primitives (Input, Select, TextArea)
• components/ contains: common (ActivityFeed, ActivityItem), escrow detail views and modals (ReleaseFundsModal, FileDisputeModal, FulfillConditionModal), stellar (TransactionTracker), and shadcn UI components (button, dialog, skeleton, select)
• Some types are duplicated locally in components (e.g., EscrowCard.tsx line 2 has a temporary interface definition)

Acceptance Criteria

• Merge all components into a single components/ directory following Next.js/shadcn conventions
• Update all import paths across pages, hooks, and other components
• Establish clear directory conventions: components/ui/ for shadcn primitives, components/escrow/ for escrow-related, components/dashboard/ for dashboard, components/layout/ for navbar/footer, components/wallet/ for wallet UI
• Remove duplicate type definitions in favor of centralized types/ directory
• Verify build passes with no broken imports

Rollout Order

Frontend Issue 1 of 10 - Foundational cleanup. Must be done first to establish a clean base for all subsequent frontend work.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Swayymalcolm99]

@Swayymalcolm99 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Swayymalcolm99 to this issue.

[drips-wave]

Congratulations, @Swayymalcolm99! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Swayymalcolm99: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊