Currently replication just checks that we become >= minValid before becoming secondary, without checking that we actually applied the exact minValid optime. This can lead to an undetected corruption if there was an upstream rollback between the time we fetched documents that caused us to set minValid and the time we fetched the oplog entry that is >= minValid. Note that if we detect this state, the only possible fix is to do a full resync.