[Psalmuel01]

Summary

Replace the existing interface with a cohesive dark finance console across the public site, documentation and wallet workspace. Payments, funding, payroll and escrow now use clearer review states, recipient validation, precise amount handling and feedback for confirmed, declined and uncertain transactions.

• Add responsive navigation, shared typography, reduced-motion support, accessible controls and expanded documentation with developer and recovery guidance.
• Defer wallet initialization and workspace prefetch on public pages; self-host fonts and add reproducible startup measurements and resource budgets.
• Rebuild confidential state in memory and persist it only after both balance commitments match the chain. Preserve cached state and the account view when recovery fails.
• Delay activity scans until account loading completes, reuse the wallet event fetcher, disable the overview send action when balances are unverified, and explain unavailable RPC ledger ranges without skipping events.

Validation

Completed locally during implementation:

• Production app and SDK builds; TypeScript checks, including unused-local and unused-parameter checks.
• SDK fast regression suite, including recovery failure preservation, commitment verification, pagination and ledger-range errors. Live indexer parity was skipped because no endpoint was configured.
• Real WalletProvider lifecycle tests with mocked wallet boundaries, plus mocked financial workflow tests and responsive accessibility checks.
• Production browser checks across 13 routes and five viewport widths; local startup measurements are recorded in docs/design/performance.md.

The latest recovery and overview changes passed the production build, TypeScript checks, SDK regression tests and mocked UI suite. These checks do not establish live financial settlement correctness or recovery of the affected user account.

Limitations

A full-history indexer with verified historical coverage is still required for reliable reconstruction after browser-state loss when required events have aged out of the RPC window. This PR does not deploy that service, restore missing historical events, or recover previously lost balances. Soroban contracts and proof circuits are unchanged.