Implemented the Sender & Receipt User Flow Diagram

[KAMALDEEN333]

Executive Summary

Created the Sender & Recipient User Flow Diagrams
Description was followed as described below
📌 Overview
We need clear visual flow diagrams representing:
• Sender journey
• Recipient journey
• Error flows
These must be derived from:
• /docs
• ROADMAP.md
• Existing architecture
• (If completed) bridgelet-frd-ui-ux.md

📦 Deliverables
Inside:
/docs/flows/
Provide:
• Sender flow diagram (PNG or SVG)
• Recipient flow diagram
• Error state flow diagram
Also include:
/docs/flows/README.md
Explaining:
• Entry points
• Decision points
• System actions vs user actions

🎯 Acceptance Criteria were achieved
• Clear start/end states
• Shows all major decision branches
• Includes failure scenarios
• Mobile-first assumptions considered
• Clean, readable diagram structure
• No contradictions with roadmap

Linked Issues & References

• Issue: Resolves docs: Create Sender & Recipient User Flow Diagrams #32 the Sender & Recipient User Flow Diagrams
• Related PRs:

Type of Change

Created new folder called 'flows'
Added new files :
1.Sender flow.mmd
2.receipt-flow.mmd
3.error-flows.mmd
4.Readme.md

Category

• New Feature (Non-breaking change adding functionality)
• Bug Fix (Non-breaking change fixing an issue)
• Performance Optimization (Code change to improve efficiency)
• Refactoring (Code structure change without external API modification)
• Security Patch (Fixing a vulnerability or security concern)
• Documentation (Updates to README, Wiki, or inline docs)
• Infrastructure (CI/CD, build scripts, Docker)

Domain

• Smart Contracts (Rust/Soroban)
• SDK/Backend (NestJS/TypeScript)
• Frontend/UI

Technical Implementation Details

Breaking Changes

• No - Backward compatibility is maintained.
• Yes - This change requires consumers of the SDK/Contract to update their code.

Verification & Testing Strategy

Automated Tests

• Unit Tests: Added/Updated new unit tests.
• Integration Tests: Verified interaction between modules.
• Linting: Code follows the project's style guide.

Manual Verification

1. Environment:

• Target Environment:

2. Reproduction Steps:

3. Proof of Execution:

Quality Assurance Checklist

• I have performed a self-review of my own code.
• I have commented on my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect these changes.
• My changes do not generate new warnings or errors.
• I have verified that new dependencies are necessary and secure.
• (If Smart Contract) I have verified gas usage and storage footprints are optimized.

---

By submitting this Pull Request, I acknowledge that I have adhered to the Bridgelet contribution guidelines.

closes #32

[phertyameen]

Perfecly implemented!