docs: add current developer feature index

docs/SIMULATION_STATE_SCHEMA.md

@@ -2,7 +2,7 @@
 
 ## Current contract
 
-`SimulationStateRecord` is the versioned JSON boundary for the current
+`SimulationStateRecord` is the versioned JSON boundary for the current local
 simulation. The current world schema is v16 and captures:
 
 - simulation seed, stable regional world/location scope, tick interval, tick
@@ -445,7 +445,7 @@ replayed after restore.
 
 ## Local quicksave boundary
 
-`SaveSlotStore` writes the existing versioned JSON record to
+`SaveSlotStore` writes the existing versioned local JSON record to
 `user://saves/quicksave.json`. It validates the serialized record before
 replacement, limits file size, restricts slot names, preserves the previous
 file during replacement, and can recover that backup if replacement is
@@ -461,7 +461,7 @@ This phase does not yet provide:
 
 - a save-slot menu, metadata, thumbnails, autosaves, or multiple profiles;
 - migrations from any historical world schema other than the explicitly
-  supported v1-v14 layouts;
+  supported v1-v16 layouts;
 - line-of-sight/hearing evidence, personalized confidence decay,
   reinforcement, false beliefs, or multi-hop rumours;
 - the full regional situation predicate library, regional quest bounds,
@@ -470,8 +470,8 @@ This phase does not yet provide:
 - persistence of a currently open dialogue UI/turn. Semantic conversation
   history and commitment authority persist, while a balloon is regenerated
   after restore;
-- chunked regional saves, lazy location loading, or aggregate population
-  persistence;
+- production integration of the regional chunked save manifest, lazy location
+  loading, or aggregate population promotion/persistence;
 - persistence for the player transform or presentation-only scene state.
 
 Those features should build on this boundary rather than inventing parallel