The generic delegator's /estimate/clauses endpoint simulates the user's
raw clauses without the executeWithAuthorization wrapper and without the
embedded-wallet typed-data signature, so it under-estimates gas (and for
NFT-heavy clauses can revert outright in simulation). The returned
transactionCost was then used to build the transfer clause that pays the
delegator's deposit account, leaving it insufficient to cover the actual
on-chain gas. The failure was masked by a catch-all that surfaced a
misleading "no gas tokens have sufficient balance" error even when the
wallet had ample balance.

Mirror VeWorld mobile's approach: trust the delegator only for the
gas-token-per-gas rate (a market price independent of the gas amount),
recompute the gas number locally with thor.gas.estimateGas (caller =
smart account), add a fixed wrapper overhead per smart-account version
plus a fixed fee-payer overhead per gas token, apply a 1.1 safety
multiplier, then reapply the rate. New shared helper
computeCorrectedGasTokenCost is used by the send path, the fee-estimation
UI hook, and the all-tokens hook so they all agree.

Also revert the homepage/playground feeDelegation override introduced in
the cross-app PR. It set feeDelegation.delegatorUrl (dApp-sponsored mode)
to the generic-delegator URL, which routed transactions through the
dapp-kit fee-delegator path that POSTs to the bare base URL and 404s.
With no override the kit's default getGenericDelegatorUrl() takes over
and the request hits the correct /api/v1/sign/transaction/authorized/...
endpoint.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

The cross-app-connect-check workflow runs `tsc --noEmit` before
`next build`, but Next.js only generates CSS Module type stubs
under `.next/types/` as part of a build. Without those stubs the
typecheck step fails with "Cannot find module './foo.module.css'
or its corresponding type declarations" on every styled component.

Add a small `src/types/css-modules.d.ts` ambient declaration so TS
resolves `*.module.css` imports without depending on Next's
build-time output. Same `{ readonly [key: string]: string }` shape
Next eventually generates; the runtime stays identical because
CSS Modules are still handled by the bundler.