Revert "Handle Vault 109 quest handoff"

This reverts commit 6fdc63c36d.

docs/architecture.md

@@ -46,10 +46,8 @@ both send and receive paths:
     creation. On entry it can send one location update so other clients hold any
     stale proxy, then outgoing transform packets are suppressed and remote proxy
     representation is skipped while the local player remains inside. Looks and
-    SPECIAL setup therefore stay visually single-player. When the local player
-    leaves this cell, the plugin completes MQ101 (`War Never Changes`) and starts
-    MQ102 (`Out of Time`) at stage 10. The relay protocol is unchanged; the rule
-    is enforced client-side by the plugin.
+    SPECIAL setup therefore stay visually single-player. The relay protocol is
+    unchanged; the rule is enforced client-side by the plugin.
 14. On the game-thread update path, the proxy controller reads a copied
     remote-player snapshot before attempting any actor work. The snapshot is
     sorted by `playerId`, and only remote players with valid transform data in

docs/dev-log.md

@@ -9,37 +9,6 @@ failed experiments, successful tests, and next steps.
 
 ---
 
-## 2026-06-30 - Vault 109 Main Quest Handoff
-
-### Summary
-Added a game-thread quest handoff when the local player exits `COVault109`, completing `War Never Changes` and starting `Out of Time` at stage 10.
-
-### Files Changed
-- `plugin/src/main.cpp`
-- `changelog.md`
-- `docs/dev-log.md`
-- `docs/architecture.md`
-
-### Details
-- Reused the existing `COVault109` solo-cell tracking in local transform polling so the trigger fires as soon as the previous known location was the solo cell and the current location is not.
-- Runs Fallout 4 console quest commands on the plugin game-thread update path: `completequest MQ101`, `startquest MQ102`, and `setstage MQ102 10`.
-- Logs the handoff with the quest editor IDs and form IDs for confirmation in `CommonwealthOnline.log`.
-
-### Testing
-- Ran `build.bat`; `CommonwealthOnline.dll` compiled and linked successfully.
-- Not run in-game in this session.
-- Expected result: leaving `COVault109` completes MQ101 (`0001ED86`) and starts MQ102 (`0001CC2A`) at stage 10.
-- Recommended log check: confirm `CommonwealthOnline.log` contains the Vault 109 quest handoff message after exiting the cell.
-
-### Known Issues
-- In-game confirmation is still needed to verify the vanilla quest scripts accept the handoff cleanly from the custom Vault 109 flow.
-
-### Next Steps
-- Start the server, connect one Fallout 4 instance, leave `COVault109`, and verify MQ101 is completed while MQ102 is active at stage 10.
-- Connect two Fallout 4 instances and confirm outgoing transform packets, server relay, remote state parsing, and visible proxy movement still work after leaving the solo cell.
-
----
-
 ## 2026-06-30 - Pip-Boy Third-Person Behavior Investigation
 
 ### Summary