Build Cove, a polished, responsive crypto lending web application DEMO, using the attached better-interface reference throughout implementation, review, and final design documentation. This is a test of the live IMD website/design workflow. Deliver the finished application, not a proposal or a landing-page mockup.

PRODUCT AND DESIGN

Create a credible, thoughtfully designed lending dashboard for a crypto-literate person supplying collateral and borrowing a stablecoin. Include a restrained product identity, useful navigation, a compact market overview, a position summary, and a focused action panel. Give the agent freedom over the visual direction, typography, palette and layout; favor clear financial information and deliberate hierarchy over decoration. Keep the main task prominent on both desktop and mobile. Use a single page or hash routing.

DEMO BOUNDARY

Clearly label the product as a simulation using illustrative rates and prices. No real wallet connection, private keys, RPC calls, signatures, token approvals, transactions, contracts, live financial services, analytics, or paid media generation. Do not imply this is an audited or launched protocol. Use local deterministic data and locally bundled assets. Show no fabricated testimonials, audits, partners, or claims of real deposits.

FUNCTIONAL SCOPE

The primary working market is ETH collateral with USDC borrowing. A small overview can also show WBTC and USDC reference markets, clearly marked illustrative and view-only if not implemented. Keep the interactive position intentionally simple: initial demo wallet 2 ETH and 1,000 USDC; no supplied collateral or debt; illustrative ETH price 3,000 USD; maximum borrowing LTV 70%; liquidation threshold 80%. Label all rates as illustrative annualized rates, with supply APY and borrow APR distinguished; interest need not accrue in this demo.

Implement supply ETH, borrow USDC, repay USDC, and withdraw ETH. Each operation must validate positive finite amounts, available wallet/position balances, and applicable collateral limits, then show a review/confirmation state and an honest simulated success state. Update balances and position figures consistently; avoid floating-point display artifacts. Borrowing and collateral withdrawals must not push debt above the 70% maximum LTV. Health factor is collateral USD times 0.80 divided by debt USD; with no debt, show 'No debt' instead of a misleading zero or error. Preview the projected LTV and health factor before consequential demo actions. Repayment cannot exceed either wallet USDC or debt. Include an explicit reset-demo action. No artificial loading state is necessary unless it represents an implemented transition.

PRIMARY ACCEPTANCE SCENARIO

Starting fresh, supply 1 ETH, then borrow 1,000 USDC. The position should show 1 ETH collateral (3,000 USD), 1,000 USDC debt, approximately 33.33% LTV, and health factor 2.40; the wallet should contain 1 ETH and 2,000 USDC. Verify invalid/over-limit requests are blocked with clear recovery messages; verify repayment and withdrawal update all affected values. Test the actual controls and keyboard flow, not just calculation helpers.

BROWSER REVIEW AND DELIVERY

Use the assigned browser tool to inspect the final built static export at desktop and mobile widths. Test keyboard focus, primary actions, validation/recovery, dialogs and focus return where used, overflow, console errors and failed resource loads. Review with Better Interface's six design disciplines and correct confirmed defects within this assignment. Record exactly what ran and any limits; do not invent browser evidence. Keep this test focused on the current design skill; do not add an Impeccable critique/polish phase or a new sub-agent workflow.

Use Vite/React/TypeScript unless a stronger task-specific reason dictates otherwise; run the production build and typecheck. Commit the finished source, lockfile, README, root DESIGN.md and static dist/ export with relative asset paths. Write DESIGN.md from the final implemented tokens/components and include a recipe for creating a matching future page. Provide an identical artifacts/DESIGN.md, artifacts/validation.md with commands, viewport sizes, interaction evidence, findings/fixes and limitations, and actual final artifacts/desktop.png and artifacts/mobile.png screenshots. Package the final dist contents in artifacts/website.zip with index.html at the archive root. Named artifacts are separate deliverables; follow the worker's rules for their handling. Close browser sessions after validation. Public source delivery to GitHub and a hosted IPFS preview are requested.