we could spy on calls to arweave.api for Contract Manifests and ensure they are only called once for multiple requests for one contract, but we haven’t introduced any stubbing or mocking in this repo yet.
alternatively, add a timestamp/uuid to the the cacheKey on first insert to the cache and return it as a response header x-contract-cache-key, then check it's the same for multiple requests
regarding tests for this:
x-contract-cache-key, then check it's the same for multiple requestswe can add tests in a separate PR to get this out