test: WalletStatusCard state coverage, wallet-api tests, e2e, escrow contract tests

[A6dulmalik]

Summary

Four test-coverage fixes across the frontend and the escrow contract:

#1705 — wallet-api.ts tests
Added tests for every exported function's success path and walletFetch's
non-ok error path (JSON error body with/without a message field, and a
non-JSON body). Writing the error-path test surfaced a real bug blocking
it entirely: walletFetch's non-ok branch calls
Sentry.captureException(...), but Sentry was never imported in this
file — every failed wallet request would throw a ReferenceError instead
of the intended error, in production as much as in a test. Fixed with the
same import * as Sentry from "@sentry/nextjs" already used elsewhere in
this app (app/wallet/error.tsx).

#1704 — WalletStatusCard state coverage
Only an accessibility test existed. Added coverage of: initial load, load
error, provision flow (success and failure), link-challenge flow, and
link-verify (success and failure). Both this new suite and the
pre-existing a11y test needed a QueryClientProvider wrapper —
WalletStatusCard calls useQuery/useMutation, which throw without one,
and the a11y test's bare render() call had neither a provider nor a
correct prop (it was passing accessToken, which the component doesn't
accept — auth comes from useSessionStore). Fixed both alongside adding
the real coverage.

#1706 — Playwright e2e
CI already runs a "Frontend E2E" job and playwright.config.ts already
pointed testDir at ./e2e, but that directory never existed — the job
was green purely because test:e2e uses --pass-with-no-tests, silently
running zero tests on every PR. Added e2e/wallet.spec.ts covering wallet
load + provisioning (mocked backend via page.route(), a fake
accessToken cookie past the auth middleware) plus a load-error case, and
a webServer block in playwright.config.ts so the Next dev server
starts itself for both local runs and CI.

#1707 — escrow contract happy-path tests
Chains create -> get_status=Locked -> release -> get_status=Released,
and the equivalent refund path, using soroban-sdk's testutils.

Tests / verification

• wallet-api.test.ts, wallet-status-card.test.tsx, wallet-status-card.a11y.test.tsx, e2e/wallet.spec.ts — all new/fixed, verified by careful manual review against this repo's existing test conventions. Could not run vitest/playwright locally — this sandbox's npm registry connectivity was severely degraded across this whole PR set (a dozen-plus install attempts, every kind of failure from ECONNRESET to Windows file-lock races to genuine multi-minute stalls).
• payment_escrow's new tests: partially verified. cargo test -p payment_escrow initially failed to compile soroban-sdk's own testutils.rs at all ("cannot find crate serde_json/rand") — traced this to contracts/.cargo/config.toml pinning [build] target = "wasm32-unknown-unknown" as the default for every cargo invocation including test, and rand's OS-entropy code isn't available on bare wasm32. Running cargo test --target x86_64-pc-windows-msvc gets past that and compiles most of the dependency graph, but then hits a genuine version conflict inside soroban-env-host 21.2.1 itself (ChaCha20Rng doesn't satisfy the CryptoRng bound ed25519-dalek expects — two different major versions of ed25519-dalek coexist in this workspace's Cargo.lock). That's an upstream dependency-graph issue unrelated to this file's code, and out of scope to fix here — re-resolving/pinning versions workspace-wide isn't something four test-coverage issues should carry. I'm confident in the tests from manual review against soroban-sdk 21.x's documented testutils API, but flagging this for CI/reviewer attention since I couldn't get a passing local run.

Closes

Closes #1704
Closes #1705
Closes #1706
Closes #1707

[vercel]

@A6dulmalik is attempting to deploy a commit to the naijabuz's projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

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

[yusuftomilola]

No merge conflicts with main. Good test coverage additions for WalletStatusCard state handling, wallet-api, the e2e suite, and the escrow contract - approving.