Batch Cache Operations can't return an empty list

For batch cache operations, a request/response is appended to the list for every operation, so the list always has a size of number of operations.

• Let resultList be an empty list.
• For each operation in operations:
• • Append operation’s request/operation’s response to resultList.
• Return resultList.

Then the cache.delete steps are

• Let requestResponses be the result of running Batch Cache Operations with operations. If this throws an exception, set errorData to the exception.
• If requestResponses is not empty, resolve cacheJobPromise with true.

But this also means that when no entries are matched, it also returns a length of 1, meaning it always should be returning true?

I'm sorry if I'm misunderstanding anything but I'm stuck here.

Start by reading the linked Batch Cache Operations algorithm and the cache.delete steps in the Service Workers specification. Trace how an operation with no matching cache entry contributes to requestResponses. Done means the specification clearly defines the empty-match case and the resulting cache.delete value, with any needed wording or algorithm correction reflected in both steps.