feat(e2e): failure-path matrix for Send with reusable fixture surface

[Labi-Joy]

Closes #187

Delivers PR 1 of 3 for the failure-path matrix: fixture surface for all six axes, the Send-flow matrix on top of it, and a Playwright CI job so the matrix runs on every PR. Receive, Batch, Schedule, and Vault will follow in later PRs once the pattern is approved, as flagged in the assignment thread.

Failure axes covered (Send)

#	Axis	Fixture surface	Status
1	Signature rejected	freighter.mock({ shouldFailSignTx: true })	passing
2	RPC exhausted	horizon.mock({ accountFetchStatus: 503 })	passing
3	Wrong network	freighter.mock({ network, networkPassphrase })	passing
4	Insufficient balance	horizon.mock({ accountBalance: '2' })	passing
5	Missing trustline	horizon.mock({ senderTrustlines: [...] })	skipped
6	Stale session	session.expire() (new fixture)	passing

App fixes required to unblock coverage

Working through the matrix surfaced four pre-existing bugs that kept the whole e2e suite red. Fixed in this PR so the failure-path assertions have something real to assert against:

1. index.html FOUC guard never released. <body style=\"visibility:hidden\"> was added alongside the theme boot script, but the boot only unhid document.documentElement, so <body> stayed hidden forever and Playwright saw a blank body on every navigation. Theme class is applied synchronously in <head> before first paint, so the inline body visibility was overkill; removed it.
2. handleSend useCallback deps stale. [address, recipient, amount, assetKey, signTransaction, t] did not include canSubmit, validationError, isNetworkMismatch, or memo, all of which change after the debounced balance / trustline effects settle. Every click fired with the closure from the last keystroke and short-circuited on the generic Enter valid send details message.
3. stealthResult pinned the pending panel after a signing failure. setStealthResult(result) runs before signTransaction. On rejection or submit-time network error, the panel stayed set and the error paragraph inside {!stealthResult && ...} never rendered; the UI showed PENDING forever with no retry affordance. Reset in the catch so the failure surface is reachable.
4. AssetPicker emitted <code>:<issuer> for non-XLM entries but getAssetByKey only knows short codes. Selecting USDC threw Unknown Stellar asset: USDC:GBBD47IF... and crashed the tree. Store entry.key = code in the balance-entries list so the picker emits USDC and downstream getAssetByKey resolves it.

Deferred: axis 5 (missing trustline)

Fifth pre-existing bug surfaced by the same recon: STELLAR_USDC.issuer in src/lib/stellar/assets.ts fails StrKey.isValidEd25519PublicKey, so getAssetByKey('USDC').toAsset() throws Issuer is invalid and the entire USDC path (including the trustline check) is unreachable end to end. Replacing the placeholder with a real testnet USDC issuer is a scope-of-USDC-support change, not a failure-path change; the trustline spec is committed as test.skip with an inline pointer and will land in the follow-up alongside the issuer fix.

Fixture additions

• FreighterMockConfig: network, networkPassphrase. Mock now also exposes getNetworkDetails, isAllowed, and WatchWalletChanges so the wallet context can walk its mount path without silently failing.
• HorizonMockConfig: accountFetchStatus (retryable-status branch for the sender lookup), senderTrustlines (extra credit_alphanum4 balances on the sender account only; the stealth address stays native-only so the trustline check still fires the missing branch).
• session.expire(): fires window.__wraithForceIdleLock, a dev/test hook wired in src/App.tsx and dropped from production by Vite dead code elimination (!import.meta.env.PROD).

CI

.github/workflows/e2e.yml runs pnpm exec playwright test --project=chromium inside the Playwright container image. Chromium-only keeps the run under two minutes; the full multi-browser matrix stays available locally via pnpm test:e2e.

Acceptance criteria

• Mock wallet and RPC failures deterministically (fixture-level).
• Cover send with the failure matrix; receive / batch / schedule / vault to follow in subsequent PRs, as proposed in the assignment.
• Assert user-facing recovery actions and no stuck spinners.
• Run the matrix in CI.

Local verification

• pnpm exec playwright test send-failure-matrix.spec.ts --project=chromium: 5 passed, 1 skipped, 0 failed (~1.4 min).
• pnpm build: green.
• pnpm format:check: green.

[vercel]

@Labi-Joy is attempting to deploy a commit to the truthixify's projects Team on Vercel.

A member of the Team first needs to authorize it.

[truthixify]

This only covers Send, leaves trustline skipped, and does not cover receive, batch, schedule, or vault as required by #187. Please complete the full matrix before marking the issue closed.

[Labi-Joy]

Thanks for the review. Just pushed 483c0bb which extends the matrix to the remaining flows and un-skips the missing-trustline case.

Coverage now:

• Send (6 tests): signature-rejected, RPC-exhausted, wrong-network, insufficient-balance, missing-trustline, stale-session.
• Receive (2 tests): signature-rejected on Derive Keys, stale-session. Insufficient-balance / missing-trustline / RPC-exhaust are n/a on Receive (no sender funds, no AssetPicker).
• Batch (2 tests): signature-rejected on Send Batch, stale-session. Row-scoped balance/trustline live inside sendBatch and are noted for a follow-up spec.
• Schedule (1 test): stale-session. Schedule is a local Zustand store with a mock tick executor and does not touch the wallet / Horizon / Soroban, so the other axes have no surface to fail on.
• Vault (3 tests): wrong-network on Claim, signature-rejected on Claim, stale-session. Other axes n/a on today's Vault UI (simulated executor pending the on-chain contract).

Total: 14 passed / 0 skipped / 0 failed locally against the pinned Chromium image.

Two more app fixes were needed to enable coverage:

1. STELLAR_USDC.issuer in src/lib/stellar/assets.ts was a placeholder that failed StrKey.isValidEd25519PublicKey, so new Asset('USDC', issuer) threw and the whole USDC path (including the trustline check) was unreachable. Swapped in Circle's canonical USDC issuer.
2. StellarReceive.tsx had toggleSelectAll (with dep filteredMatched) declared above filteredMatched. React evaluates useCallback deps on every render, so the initial render hit a TDZ ReferenceError and Receive crashed before any assertion could reach the DOM. Reordered so the callback lives below its dep.

Ready for another look.

[truthixify]

CI now runs both specs and all five flows are represented. Please add recovery and no-stuck-spinner assertions for the Batch and Vault failures, which currently stop after finding an error message.