config.transactions must be updated for the batch's retryable operation only on the terminal applyOps entry because its optime becomes the session record's lastWriteOpTime, and TransactionParticipant (via TransactionHistoryIterator) walks the chain backward from that optime through each entry's prevOpTime to recover the chain's committed statement IDs and dedup retries.