feat: score resource discovery by comfort and safety

docs/SIMULATION_STATE_SCHEMA.md

@@ -74,8 +74,8 @@ duplicate IDs, and preserve deterministic ordering across save/restore. See
 
 `SimulationManager` owns `ResourceStateRecord` instances independently of the
 scene tree. Amount, reservation, enabled state, action/resource identity,
-yield, and usage permissions remain available and serializable while no
-ResourceNode is loaded.
+yield, usage permissions, and discovery metadata remain available and
+serializable while no ResourceNode is loaded.
 
 ResourceNode binds to a record by stable ID and provides presentation,
 interaction transforms, and active-world discoverability. Unloading a node does
@@ -83,9 +83,10 @@ not delete its record. Loading another node with the same stable ID rebinds to
 the existing record and cannot overwrite its amount or reservation with scene
 defaults.
 
-ResourceStateRecord v2 adds the definition facts needed while unloaded. Nested
-v1 resource records are migrated explicitly and hydrate their missing
-definition from a matching presentation node when one becomes available.
+ResourceStateRecord v3 adds `safety_risk`, `comfort_distance`, and
+`discovery_priority` so unloaded resources keep the same target-selection
+meaning after save/restore. Nested v1 and v2 resource records are migrated
+explicitly.
 
 ## Local quicksave boundary