[12] Add unit tests for `AuthService`

[EmeditWeb]

Problem

src/modules/auth/auth.service.ts has zero unit tests. All authentication paths (nonce generation, signature verification, token rotation) are untested. Any regression here logs every user out and is undetectable until production.

Context

Auth is the most security-sensitive module. A silent bug in token rotation could leak session lifetimes or allow refresh-token replay attacks. Unit tests are the cheapest line of defense.

Before Starting

Read these context files first:

• context/architecture-context.md
• context/code-standards.md
• context/progress-tracker.md
• src/modules/auth/auth.service.ts

What To Build

1. Create test/unit/auth.service.spec.ts with a Test.createTestingModule setup mocking SupabaseService, JwtService, and ConfigService.
2. Test getNonce(wallet): returns a 32-char nonce, inserts a row in nonces with wallet, nonce, expires_at.
3. Test verify(wallet, signature): valid signature path returns { accessToken, refreshToken }; invalid signature throws UnauthorizedException.
4. Test refresh(refreshToken): valid token returns new pair; refresh token is rotated (old one marked revoked).
5. Test nonce dedup: two getNonce(wallet) calls within expiry window return the same nonce.
6. Achieve ≥ 90% branch coverage on auth.service.ts.

Files To Touch

• test/unit/auth.service.spec.ts

Acceptance Criteria

• At least 5 distinct describe blocks covering each method
• All Supabase calls are mocked — no real DB hit
• Test runs in under 2 seconds
• npm test -- auth.service passes
• Branch coverage ≥ 90% on the service
• No any types in the test file

Mandatory Checks Before PR

• npm run build passes with zero TypeScript errors
• No new any types introduced anywhere
• Full Swagger @apioperation + @apiresponse decorators on any new endpoints
• New migration file created for any schema changes
• context/progress-tracker.md updated

[Iwayemi-Kehinde]

I would like to work on this issue as I have reviewed the scope, I should have a PR Ready in 50 minutes.

[teeschima]

Hi,

I'd like to work on this wallet integration issue.

From my understanding, this is a critical feature because all transaction-related workflows (loan applications, repayments, deposits, and future contract interactions) depend on users being able to connect and sign transactions through supported Stellar wallets.

My implementation plan is:

• Review the architecture, code standards, progress tracker, UI context, and authentication service before making changes.
• Configure WalletConnect v2 using EXPO_PUBLIC_WALLETCONNECT_PROJECT_ID.
• Implement wallet.service.ts with:

• initWalletConnect()
• connectFreighter()
• connectLobstr()
• signXdr()
• disconnectWallet()
  • Integrate Freighter using @stellar/freighter-api.
  • Integrate Lobstr using WalletConnect v2 with Stellar namespaces and transaction-signing methods.
  • Create a Zustand wallet store that persists connection state using SecureStore.
  • Implement automatic session cleanup and disconnection on WalletConnect session_delete events.
  • Build a reusable wallet connection modal with:
• Freighter option
• Lobstr QR-code flow
• Mobile deep-link support
  • Add a useWallet() hook for screen-level consumption.
  • Update the sign-in screen to clearly present both wallet options while following existing design standards.
  • Ensure loading, error, and empty states are handled.
  • Use only theme color constants and Lucide React Native icons.
  • Verify npx expo export --platform web passes before opening the PR.
  • Update context/progress-tracker.md and reference the issue in the PR.

I have experience working with TypeScript, React-based applications, authentication flows, state management, API integrations, and blockchain-connected user experiences. I can provide clean commits, testing notes, and documentation for the implemented wallet flow.

Looking forward to contributing.