chore: Implement VedaAdapter

[MoMannn]

What?

• Adds VedaAdapter.sol — a new adapter contract for delegation-based deposits and withdrawals on Veda BoringVault
• Adds IVedaTeller.sol — minimal interface for Veda's TellerWithMultiAssetSupport
• Adds VedaLending.t.sol — comprehensive test suite (fork tests, happy paths, input validation, events, batch operations, edge cases, 3-level delegation chain, terms validation, replay prevention, slippage protection, alternative delegator)
• Adds BatchDepositExecuted and BatchWithdrawExecuted events for off-chain indexing of batch operations

Why?

• Enables users to deposit into and withdraw from Veda BoringVaults through the delegation framework, without requiring direct token approvals
• Allows operators to execute vault operations on behalf of users via the redelegation pattern, with fine-grained control over tokens, amounts, and who can redeem

How?

• Uses the redelegation pattern (user → operator → adapter) consistent with DelegationMetaSwapAdapter
• Parses deposit token/amount and withdrawal share amount from the leaf delegation's caveat terms via a shared _parseERC20TransferTerms helper, which validates that terms are at least 52 bytes (ERC20TransferAmountEnforcer format) before reading with assembly
• On deposit: redeems the delegation chain to transfer tokens to the adapter, approves the BoringVault, and calls the 5-arg teller.deposit() to mint shares directly to the root delegator
• On withdraw: redeems the delegation chain to transfer vault shares to the adapter, then calls teller.withdraw() to burn shares and send the desired underlying output asset to the root delegator. The output token is passed as a function parameter (distinct from the vault share token in the caveat)
• Supports batched operations via depositByDelegationBatch / withdrawByDelegationBatch, each emitting a batch-level event alongside per-stream DepositExecuted / WithdrawExecuted events
• Includes withdrawEmergency (owner-only) for recovering tokens accidentally sent to the contract

Note

• Tests are being run on a mainnet fork of Arbitrum on a deployment of Veda protocol

---

Note

High Risk
New on-chain path moves user ERC20 and vault shares with permissionless depositByDelegation / withdrawByDelegation; safety depends on correct delegation caveats and Teller authorization, not caller identity.

Overview
Adds VedaAdapter, a delegation-driven bridge to Veda BoringVault deposit and withdraw flows (same redeem-then-call pattern as the MetaSwap adapter). Operators redeem a user → operator → adapter chain via DelegationManager, pull depositToken or vault shares into the adapter, then call IVedaTeller so assets/shares land on the root delegator. Amounts come from caveats[0] (ERC20TransferAmountEnforcer terms, 52-byte check); batch entrypoints and owner withdrawEmergency / ensureAllowance are included.

Also adds DeployVedaAdapter (CREATE2 + env knobs), .env.example Veda vars, chain 143 broadcast artifacts, and VedaLending.t.sol (Arbitrum fork). CI tests gain ARBITRUM_RPC_URL and RPC_API_KEY.

^{Reviewed by Cursor Bugbot for commit e2227ef. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ede87fa. Configure here.}