fix: handle unreadable stellarWallet blobs gracefully (#254)

[ejiromowarin]

Summary

Fixes #254.

User.stellarWallet is nullable text, and several handlers called JSON.parse() on it without a guard. A row whose column is truncated, written in the pre-encryption format (a bare public key), or otherwise not the canonical wallet JSON made the handler throw a SyntaxError. That error escaped to the top-level catch, so the user saw a generic internal error instead of an actionable message — and the command did not recover.

Root cause

if (!user.stellarWallet) return no_wallet;
const { publicKey } = JSON.parse(user.stellarWallet); // throws on malformed data

The presence check only handled NULL/empty. PROFILE and both sending flows (SEND, CONTRIBUTE) had the same pattern, and a malformed recipient blob also aborted the transfer.

Changes

• New src/utils/wallet.util.ts — parseStellarWallet() never throws and returns one of:
  • absent — the column is NULL/blank (existing *.no_wallet message),
  • unreadable — something is stored but it is not a usable wallet blob,
  • ok — the blob parsed and carries publicKey, encryptedSecret, iv, authTag.
    keyVersion is optional; a non-numeric value is ignored instead of rejecting the blob.
• src/services/message-processor.service.ts — BALANCE, HISTORY, PROFILE, SEND and CONTRIBUTE read the column through the guard. unreadable now returns the new wallet.unreadable message, while an unreadable recipient is reported as send.no_recipient so the sender knows the transfer did not start.
• Locales — wallet.unreadable added to en, fr, ha, ig, pcm and yo.
• Tests — src/__tests__/wallet.util.test.ts covers the parser (NULL, blank, truncated JSON, bare public key, JSON string/array/null, missing fields, non-numeric keyVersion); message-processor.service.test.ts covers each affected handler, the recipient case and the unchanged empty-column behaviour.

Test-hygiene changes needed to get CI green

main was already failing these suites (they fail on main too); the fixes are test-only:

• user.service.test.ts, contribution-scheduler.worker.test.ts: the mocked Prisma client was missing $use(), which src/lib/prisma.ts calls to register the encryption middleware on construction. Assertions also follow the service's current findFirst() lookups and id-based update().
• user.service.test.ts: decrypt() returns a Buffer, so the mock/assertion no longer uses a string.
• key-rotation.worker.test.ts: decrypt() returns a Buffer; compare decrypted.toString('utf8').
• soroban.service.integration.test.ts: the suite uploads a real contract to Testnet and needs a compiled artifact, but the repo ships an 8-byte placeholder wasm. It is now gated behind RUN_SOROBAN_INTEGRATION=1 (skipped by default, run explicitly with RUN_SOROBAN_INTEGRATION=1 npm test).

Verification

npx tsc --noEmit                 # passes
npm test                         # 31 passed, 1 skipped, 423 tests passed

The skipped suite is the Soroban integration suite described above.

[drips-wave]

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