Bounded back-off between SyncEntities verify-after-acquire retries. A failed verify means a concurrent reparent (e.g. MapManager::Transfer) moved a requested entity out of the cover we just acquired; recomputing immediately re-races the same in-flight transfer, the busy-spin that exhausts the retry budget under sustained map-transfer churn. The first attempts only yield (the transfer usually compl
source not stored for this graph (policy: none)
no outgoing calls
no test coverage detected