disagg_storage/status.js reads replSetGetStatus and the last oplog entry in two separate commands, asserting the "last applied" optime matches the oplog entry. A background write (e.g. the monitoring-keys-for-HMAC thread) can land in the window between the two reads, advancing the oplog past the status snapshot and causing a spurious Timestamp mismatch failure.