RPC batch partial failure scenarios not tested

Problem

Related to #8 - there are no tests verifying behavior when some requests in a batch succeed while others fail.

Current State

Tests likely only cover:

• All requests succeed
• All requests fail

Missing coverage for:

• Mixed success/failure in same batch
• Different error types in same batch
• Recovery from partial failures

Recommendation

Add tests for partial failure scenarios:

describe('batch requests', () => {
  it('should handle mixed success/failure responses', async () => {
    mockRpc.mockResponses([
      { result: '0x1' },
      { error: { code: -32000, message: 'execution reverted' } },
      { result: '0x3' },
    ]);
    
    const results = await rpc.batchCall([...]);
    
    expect(results[0]).toEqual({ success: true, value: '0x1' });
    expect(results[1]).toEqual({ success: false, error: expect.any(Error) });
    expect(results[2]).toEqual({ success: true, value: '0x3' });
  });
});

Priority

Medium - Important for reliability

Find the existing RPC batch request tests and the rpc.batchCall entry point first. Run the current test suite to confirm coverage for all-success and all-failure batches, then add cases for mixed outcomes, different error types, and recovery from partial failures. Done means the assertions verify successful and failed results remain correctly associated with their requests.