SERVER-130332Needs Scheduling

Switch participant term transport from $replData.term to dedicated participantTerm field once 9.0 is last-LTS

h3. Context SERVER-128128 carries the participant replication term in {{$replData.term}} rather than a dedicated {{participantTerm}} reply field. This was necessary because adding a new top-level generic reply field and backporting it to older branches causes {{IDLUnknownField}} failures in mixed-version clusters — older mongos binaries use {{strict: true}} IDL reply structs, which reject unknown fields as hard errors. This ticket tracks switching to a dedicated {{participantTerm}} field o

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.