Rename project to Commonwealth Online

Replace occurrences of "Fallout 4 Together" with "Commonwealth Online" across docs and testing guidance. Add Interface assets and tooling: MainMenu/Pipboy SWFs, translation/fonts, exported scripts (Interface/exported/scripts/MainMenu.as) and a PATCH_MainMenu_Multiplayer.md describing how to add a Multiplayer menu entry that calls root.f4se.plugins.commonwealthOnline.openManager(). Also add build/run batch scripts and apply assorted updates to README, plugin, server and protocol documentation/source to align with the rename and UI changes.

.cursor/rules/project-overview.mdc

@@ -1,11 +1,11 @@
 ---
-description: Fallout 4 Together project architecture and goals
+description: Commonwealth Online project architecture and goals
 alwaysApply: true
 ---
 
 # Project Overview
 
-Fallout 4 Together is an experimental Fallout 4 multiplayer mod. It uses a C++ F4SE plugin, a Python relay server, fake clients for protocol testing, and project documentation in `docs/`.
+Commonwealth Online is an experimental Fallout 4 multiplayer mod. It uses a C++ F4SE plugin, a Python relay server, fake clients for protocol testing, and project documentation in `docs/`.
 
 The goal is to sync players across separate Fallout 4 instances by sending player transform and state data through a server, then representing remote players in-game with proxy actors.
 

.cursor/rules/testing-rules.mdc

@@ -1,5 +1,5 @@
 ---
-description: Practical manual testing guidance for Fallout 4 Together changes
+description: Practical manual testing guidance for Commonwealth Online changes
 alwaysApply: true
 ---
 
@@ -12,7 +12,7 @@ Useful project tests include:
 - Connecting one Fallout 4 instance.
 - Connecting two Fallout 4 instances.
 - Running `server/fake_client.py`.
-- Checking `Fallout4Together.log`.
+- Checking `CommonwealthOnline.log`.
 - Verifying transform packets are sent.
 - Verifying remote player state is received.
 - Verifying proxy actor movement in `F4TTestCell01`.