Does restoring a Sulu page version preserve properties removed from the current template?

Sulu's Administration UI offers a documented versions list that lets editors restore a previous page version, but the behavior is uncertain when the page template's property schema changed after that version was saved. In Sulu 2.x, templates are defined in XML and content is persisted through Doctrine, so a restored version may contain properties the current template no longer defines, or lack properties the template now requires.

The unresolved decision is whether the restore operation drops properties absent from the current template, retains them as orphaned data, or blocks the restore entirely. This editor-facing rollback is separate from Doctrine migration downgrades, which Sulu upgrade guidance does not document as a supported path. The merge-or-drop semantics are version-sensitive and should be confirmed against the installed PageBundle restore logic.

Which behavior does Sulu apply when restoring a version saved under an older template: property removal, orphan retention, or a validation block? Does the outcome differ between draft and published versions? Where in the installed PageBundle version service should this be verified for a Sulu 2.x project?