XD 57 cloud documents: pinning a team to one build after the forward-only file compatibility change

Our design team is moving a shared product library from local .xd files to Adobe XD cloud documents so we can use version history and coediting. The goal is a repeatable setup: any collaborator should be able to reopen the document and get the same design state, including earlier saved versions.

The constraint is XD's documented compatibility boundary: files saved in a newer XD build generally cannot be opened in older builds, and coediting requires all participants online on current builds. Version history and coediting also only exist for cloud documents, not local files, and linked components plus plugins add machine-specific dependencies.

Assume a recent XD release (post-2023 builds) and a standard Creative Cloud team plan; retention depth for version history appears plan-dependent, so that point needs verification against our account.

Should the team standardize on one pinned XD build and block auto-updates until everyone migrates, or is there a supported way to mix builds on the same cloud document? Does version history reliably let us restore a specific prior state once several coeditors have saved, including after an offline edit conflict? And do linked assets and plugins need to be pinned per machine for a reopened document to reproduce identically?