docs: add current developer feature index

docs/ECONOMIC_EVENTS.md

@@ -10,6 +10,10 @@ resource_extracted
 storage_deposited
 storage_withdrawn
 item_consumed
+npc_slept
+npc_died
+task_started
+resource_depleted
 animal_fed
 villager_weak
 home_damaged
@@ -19,6 +23,13 @@ raid_started
 war_resolved
 war_aborted
 wolf_hunt
+activity_completed
+task_blocked
+commitment_accepted
+commitment_fulfilled
+commitment_broken
+commitment_released
+commitment_superseded
 ```
 
 Each record contains a monotonically increasing event ID, event type,
@@ -75,17 +86,17 @@ transfer occurred.
 
 ## Persistence and determinism
 
-`SimulationStateRecord` schema v11 stores the ordered event stream,
+`SimulationStateRecord` schema v16 stores the ordered event stream,
 `next_event_id`, directed relationships that may reference an exact event, and
 per-NPC known-event references with first-acquisition provenance, plus
-opportunity records that reference exact trigger/resolution events. Schema v1
-and v2 saves migrate to an empty stream beginning at ID zero; world schemas
-v1–v7 migrate to an empty opportunity list, while world schemas v8–v10
-preserve and normalize opportunity history. World v9 adds an empty animal list
-during migration; world v10 preserves and upgrades its animal records. Parsing
-rejects duplicate event IDs, invalid or duplicate knowledge/opportunity
-references, impossible communicator sources, relationship causes the observer
-does not know, and next IDs that could collide with restored history.
+opportunity, situation, journal, commitment, and conversation records that
+reference exact trigger/resolution/outcome events. Historical world schemas
+migrate explicitly through nested record versions; current v16 adds non-empty
+world/location scope and rejects a save whose scope differs from the active
+adapter before mutating the simulation. Parsing rejects duplicate event IDs,
+invalid or duplicate knowledge/situation/commitment references, impossible
+communicator sources, relationship causes the observer does not know, forged
+activity facts, and next IDs that could collide with restored history.
 
 Animal-feed facts receive an additional cross-record check: actor is either an
 existing NPC or the player sentinel, destination is an existing animal, item