An analysis of atomic synchronization in test/format found that many accesses likely use stronger ordering than necessary. Audit these sites and use the most relaxed synchronization that preserves correctness.

At the time of analysis, the following shared state had accesses that were not consistently protected:

• TINFO::commit_ts between worker and timestamp threads.
• GLOBAL::stop_timestamp between the controller and predictable-replay workers.
• GLOBAL::timestamp where plain reads can run concurrently with atomic updates.
• GLOBAL::disagg_leader between asynchronous role transitions and key-rotation logic. Role-sensitive check-and-act sequences may require serialization rather than only atomic access.

test/format should use the weakest valid synchronization. Synchronization that is stronger than required can suppress concurrency and ordering behaviors, potentially hiding real WiredTiger issues that the test is intended to expose.