Implement design tokens mapping in dispute_raise_modal

[francisdouglas-ux]

Problem & Goal

Link Tailwind class allocations on dispute_raise_modal to our core design variables config files.

Context & Components

• Target Repository: escrow-frontend
• Module/Component: dispute_raise_modal (Dispute raise confirmation modal)

Implementation Details

1. Review the existing codebase inside the escrow-frontend directory.
2. Locate the source files relating to dispute_raise_modal.
3. Implement the feature logic/validation rules step-by-step.
4. Ensure code conforms to codebase patterns (lints, formats, types).

Verification & Testing Requirements

• Validation check: Assert component layout matches color scheme config files.
• Add comprehensive test cases matching these validation requirements.
• Ensure all other existing project tests continue to compile and pass.

---

Note: This issue is completely self-contained and does not block or require any other issues to be resolved.

[Nwapu-TrustJah]

@Nwapu-TrustJah has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi @Goldii-locks! I would like to work on this issue.
Implementation Plan:
Design Token Mapping: Locate dispute_raise_modal and refactor Tailwind class allocations to link directly with your core design variables configuration files.
Testing & Validation: Write comprehensive test cases asserting that the modal layout matches the color scheme tokens, ensuring all existing tests pass cleanly.
Code Quality: Maintain strict compliance with repo patterns, linting, formatting, and TypeScript safety.
Since this issue is self-contained, I'm ready to pick it up immediately. Please assign this to me!

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

[She-ge]

@She-ge has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I would love to work on this issue please

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

[drips-wave]

Congratulations, @She-ge! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @She-ge: 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 🌊