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
High risk because this introduces new onchain logic that redeems delegations to move ERC20s/vault shares and sets unlimited token allowances to an external vault, making correctness of caveat parsing and redemption flows security-critical.

Overview
Implements a new VedaAdapter helper contract that lets an operator execute delegation-redeemed deposits and withdrawals into Veda’s BoringVault via IVedaTeller, including per-call events plus depositByDelegationBatch/withdrawByDelegationBatch batch execution and an owner-only withdrawEmergency token recovery path.

Adds a Forge deployment script (DeployVedaAdapter.s.sol), a large Arbitrum-fork integration test suite (VedaLending.t.sol) covering happy paths, validation/reverts, batch behavior, replay/slippage checks, and updates CI/env examples to include the Veda addresses and Arbitrum RPC secrets needed to run the new forked tests.

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

[McOso]

hmm im thinking we get rid of this function. It doesnt seem possible for tokens to be left in this contract without the tx reverting, since it's atomic. If we remove, it really makes the adapter clean and lightweight, removes the need for owner / state.

[MoMannn]

This is in case of someone sending tokens directly to the contract (mistaking it for EOA).

[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 adb6c64. Configure here.}