V2-FE-089 — Run Adversarial End-to-End and Production Smoke Tests

[dDevAhmed]

Objective

Run Adversarial End-to-End and Production Smoke Tests as a focused, independently reviewable V2 frontend work item.

Technical Scope

Exercise wallet rejection, wrong chain, allowance failure, revert, replacement, reorg, API lag, accessibility, and deployed read-only smoke checks.

Security and Architecture Requirements

• Wagmi/Viem and confirmed Optimism/EVM receipts remain authoritative for protocol mutations.
• Never fabricate calldata, gas, rewards, transaction hashes, receipts, settlement, or finality.
• Do not introduce Stellar, Soroban, Freighter, mock-wallet, or simulator runtime dependencies.
• Fail closed on unsupported chain, address, ABI, session, allowance, or configuration state.
• Treat all API, wallet, RPC, claim, and evidence content as untrusted input.

Required Tests

• Unit/component tests for loading, empty, success, rejection, error, and recovery states.
• Wallet/integration coverage for transaction-affecting work.
• Accessibility assertions and keyboard testing for changed interactive UI.
• Regression tests proving mocks and placeholders cannot enter the production bundle.

Acceptance Criteria

• The task is delivered without unrelated visual redesign.
• Every asynchronous state has accurate accessible feedback and recovery.
• Canonical receipts/projections, not timers or client guesses, drive lifecycle state.
• Lint, typecheck, tests, accessibility, artifact-drift, and production build pass.
• The PR maps evidence to every acceptance criterion.
• Human maintainer approval is recorded for wallet/signature/security-sensitive changes.

Dependencies

• V2-FE-044
• V2-FE-074
• V2-FE-088

Non-Goals

• Backend-authoritative protocol mutation.
• Reintroducing legacy wallet/runtime integrations.
• Pure redesign unrelated to the stated workflow.

---

🏷 Labels

• frontend
• web3
• complexity-high
• wave-candidate

---