SERVER-138937ClosedFixed

Cover change stream recovery from a rename invalidate by reopening the stream on the renamed collection

h2. Background A collection-level change stream is invalidated when its watched collection is renamed (A→B): the stream delivers a {{rename}} event followed by an {{invalidate}}. To keep consuming, the client must reopen a stream — the natural recovery is to open it over the RENAMED collection B, resuming from the invalidate token. That recovery path is untested today: existing coverage only resumes on the original namespace. h2. Behavior (pinned by the new test) * {{resumeAfter}} with an inval

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
9.1.0-rc09.1.0-rc1025
Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.