Issue Summary

Restoring a historical page version does not reset the collaborative document held in the Native Collab Service (NCS). When it fails, view mode shows the correctly restored content, but opening Edit reloads the stale pre-restore draft. The user sees content they explicitly undid via the restore.

Steps to Reproduce

1. Import a space into Confluence Cloud via XML export/import (DC/Server → Cloud).
2. Open one of the imported pages (never edited in Cloud before) — click Edit. This triggers the first-time CXHTML → ADF conversion and creates a new NCS collaborative document.
3. Add visible marker text (e.g. SAMPLE TEXT FOR NEW VERSION) and click Publish — this creates Version 2.
4. Go to ⋯ → Page History and click Restore this version on Version 1 (the pre-migration version) — this creates Version 3 from the historical content
5. Verify in View mode — the restored historical content is correctly displayed. ✅
6. Click Edit on the restored page.

Expected Results

The editor loads content from the restored version (Version 3 = Version 1 historical content). The NCS collaborative draft should be invalidated/reconciled upon version restore.

Actual Results

The editor loads the stale draft from Version 2, which contains the marker text added before the restore (SAMPLE TEXT FOR NEW VERSION). The NCS collaborative document was not reset when the version was restored.

Workaround

Open the page in Edit → click ⋯ → Revert to last published version (or "Discard unpublished changes") → Publish. This forces the NCS document back in sync with the published content