Wolfram EntityStore Property Type Change Rollback Safety

Goal: Verify the effect of reloading an EntityStore after a property type definition change on the readability of existing entities.

Uncertainty: The Wolfram Language documentation states that adding properties is tolerated on reload, but it does not specify whether modifying an existing property’s type triggers lazy coercion, validation errors, or silent data loss when those entities are subsequently accessed.

Questions:

• Does reloading the store cause existing entities to be automatically coerced to the new type, or are they rejected with an error on first access?
• If coercion occurs, what rules govern the conversion, and are there any conditions under which the operation fails?