AvaProtocol/EigenLayer-AVS

Context The pkg/erc4337/ package contains utility functions for ERC-4337 (Account Abstraction) operations — UserOp building, nonce management, bundler interaction, etc. Some of these utilities have thin test coverage and would benefit from additional table-driven unit tests. What needs to be done Pick one or more files in pkg/erc4337/ and add tests for exported functions. Good candidates: pkg/erc4337/bundler/ — utility/helper functions pkg/erc4337/preset/ — builder helper functions Follow the existing test patterns in the repo: Use table-driven tests (tests := []struct{ ... }) Use the testutil package where applicable See pkg/erc4337/bundler/nonce_manager_test.go for a good example How to test make test/package PKG=./pkg/erc4337/... Progress pkg/erc4337/bundler/client.go (PR #493) NewBundlerClient SimulateUserOperation EstimateUserOperationGas SendUserOperation GetUserOperationByHash GetUserOperationReceipt SendBundleNow DumpMempool GetPendingUserOpsForSender Flush

Context Our RPC APIs use inconsistent naming for the same concept: SimulateTaskReq uses input_variables ✅ RunTriggerReq uses trigger_input ❌ TriggerTaskReq uses trigger_input ❌ This should be unified to input_variables everywhere. What needs to be done Proto field rename (breaking API change — requires SDK/client coordination) In protobuf/avs.proto: Change trigger_input → input_variables in RunTriggerReq (around line 1295) In protobuf/avs.proto: Change trigger_input → input_variables in TriggerTaskReq (around line 987) Run make protoc-gen to regenerate Go bindings Update all Go code that references payload.TriggerInput / req.TriggerInput to use InputVariables Internal Go cleanup (PR #491) Rename triggerInputs → inputVariableKeys in engine.go SimulateTask Update comments to document the relationship between proto field name and semantic role How to test make build — must compile cleanly make test — all tests must pass Useful references Related: #428 prot