feat: connection pooling, loyalty gamification, merchant onboarding, …

[susanyusuf]

Closes #414

Closes #394

Closes #386

Closes #405
…repository pattern

• Reduce API latency with connection pooling and keep-alive #414: HTTP/2 connection pool with keep-alive, DNS cache, TLS session resumption, pool metrics, leak detection, graceful drain
• Implement loyalty dashboard with gamification and rewards tracking #394: Loyalty dashboard with streaks, achievements, badges, progress bars, rewards catalog, social sharing; race condition mutex in store
• Build merchant onboarding flow with compliance verification #386: Merchant onboarding wizard with compliance screening, save-and- resume, document retry, payment setup, welcome tour modal
• Refactor service layer to use repository pattern for data access #405: Repository pattern with interfaces, in-memory implementations, unit-of-work, and full test coverage

Pull Request Checklist

Quality Gates (All must pass before merge)

• Lint: Code passes ESLint and Prettier checks
• Type Check: TypeScript compilation succeeds
• Tests: All tests pass
• Build: Project builds successfully
• Rust Format: Smart contract formatting is correct
• Rust Clippy: Smart contract linting passes
• Rust Tests: All smart contract tests pass
• Rust Build: Smart contracts compile successfully

Additional Requirements

• New code has appropriate TypeScript types
• No hardcoded secrets or credentials
• New features have corresponding tests
• Documentation updated if needed

Reviewers

• At least 1 approval required for merge
• All CI checks must be green

---

This PR will not be mergeable until all quality gates pass.

[drips-wave]

@susanyusuf 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