Save schema mismatch

Persistent state does not match the registered save policy, schemas or codecs. Capture, migration or restore fails; schema incompatibility does not trigger automatic backup fallback. If the message reports a restored-state hash mismatch, restoration has already run and verification failed afterward.

#Common causes

• Persistent types are unknown, duplicated, registered with the wrong storage class, or lack the required simulation codecs.
• Saved type sets differ, versions are zero or from the future, or a required migration cannot complete.
• State contains invalid identities, hierarchy cycles, missing parents, excluded data or references into missing/excluded state.

#Fixes

• Register matching reflected types and component/resource codecs in SaveSchema and SimRegistry before capture or restore.

• Provide explicit policy migration for changes to the persistent type set and schema upgrade hooks for supported older field versions; use a compatible engine for future versions.

• Repair the persistent hierarchy and references, retaining a selected component on referenced entities.

• For a post-restore hash mismatch, inspect the restored session and codec behavior before resuming play; do not assume the prior state was retained.

• Code: ARA7502

• Constant: save::SCHEMA

• Reported by: ara-save