docs: capture player standing and quest system in plans and schema

docs/SIMULATION_STATE_SCHEMA.md

@@ -3,7 +3,7 @@
 ## Current contract
 
 `SimulationStateRecord` is the versioned JSON boundary for the current
-simulation. The current world schema is v11 and captures:
+simulation. The current world schema is v12 and captures:
 
 - simulation seed, tick interval, tick count, clock remainder, and elapsed
   clock ticks;
@@ -25,14 +25,18 @@ simulation. The current world schema is v11 and captures:
   historical communicator provenance;
 - opportunity records with stable type/status, interested NPC, trigger event,
   target storage/resource/amount, exact later resolution event identity, or a
-  deterministic invalidation reason and close tick.
+  deterministic invalidation reason and close tick;
+- the player's Standing reputation (0–100), resolved-need count, and per-NPC
+  gratitude, plus named player quest records that reference the originating
+  opportunity or animal, requester NPC, resource/target/amount, Standing
+  reward, and exact resolution or invalidation tick.
 
 The top-level identity is:
 
 ```json
 {
   "schema": "the_steward.simulation",
-  "schema_version": 11
+  "schema_version": 12
 }
 ```