docs: mark action separation phase complete

docs/decisions/0001-simulation-authority-boundary.md

@@ -48,17 +48,21 @@ random streams, and no dependency on a loaded gameplay scene.
 2. ✅ Introduce serializable village, NPC, and resource-state records.
 3. ✅ Bind `ResourceNode` presentation to resource records instead of owning
    authoritative amount and reservation.
-4. **Next:** Move target choice and reservation coordination out of
+4. ✅ Move target choice and reservation coordination out of
    `WorldViewManager` into an action/target system with an active-world query
    adapter.
-5. Split action selection, execution, and presentation travel.
-6. Add versioned save/load before inventories, schedules, or relationships
+5. ✅ Split action selection, execution, and presentation travel.
+6. **Next:** Synchronize active position and prove visual unload/reload
+   invariance.
+7. Add versioned save/load before inventories, schedules, or relationships
    substantially expand mutable state.
 
 Schema v1 and its deterministic continuation contract are documented in
 [the simulation state schema](../SIMULATION_STATE_SCHEMA.md).
 Stable action/profession identity and immutable metadata are documented in
 [the simulation definitions](../SIMULATION_DEFINITIONS.md).
+System responsibilities and event flow are documented in
+[the action system architecture](../ACTION_SYSTEM_ARCHITECTURE.md).
 
 ## Consequences