One consequence of the $match pushdown work in SERVER-56871 is that resume tokens may be filtered out if the pipeline used to resume the stream is more restrictive than the original stream. We are OK with this, because resume tokens are not really intended to be applicable to streams other than the one that generated them. However, we found an edge case where startAfter with an invalidation token could render the stream unresumable even with the same pipeline as the original stream, and addressed this in SERVER-57792.

Since it is not desirable to have a special-case for this scenario, and since the invalidate stage should ideally have minimal exposure to resume semantics, we should generalize the work done under SERVER-57792 to apply to all resume tokens.