SERVER-136815ClosedWon't Do

Disambiguate AsyncResultsMerger::exhausted() from cursor-open resource checks

h2. Overview AsyncResultsMerger::RemoteCursorData::exhausted\(\) returns only "cursorId == 0" \(the remote cursor is closed\), but the name reads as "the remote is truly done". Several call sites use it to decide whether the shard still holds server\-side cursor resources that must be killed or released. For those sites, "cursor is closed" is the correct condition, but the name hides that intent and has already caused confusion about what "exhausted" guarantees. h2. Proposed change Split the tw

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.