Add staging step and reorganize assets

Add stage-mod.bat and update build scripts to stage the mod package instead of automatically deploying (build-all.bat now calls stage-mod.bat; build.bat prints plugin output path and packaging hint). Reorganize Creation Kit assets into DataFolder and RawAssets directories, add new mesh/texture files, and update CommonwealthOnline_Vault109.esp. Also include ancillary updates to deploy scripts, docs, and server code to reflect the new packaging workflow.

plugin/setup.md

@@ -71,15 +71,28 @@ Build PrismaUI_F4:
 build-prismaui.bat
 ```
 
-Build and deploy everything:
+Build and package everything:
 
 ```bat
-build.bat
-build-prismaui.bat
-deploy-all.bat
+build-all.bat
 ```
 
-Or use `build-all.bat` to build and deploy in one step.
+This produces a mod folder at the repo root with the full game path:
+
+```text
+build/
+└─ Fallout 4/
+   └─ Data/
+      ├─ *.esp
+      ├─ F4SE/Plugins/CommonwealthOnline.dll
+      ├─ F4SE/Plugins/PrismaUI_F4.dll
+      ├─ Materials/
+      ├─ Meshes/
+      ├─ Textures/
+      └─ PrismaUI_F4/...
+```
+
+Merge `build\Fallout 4` into your Fallout 4 install, or run `deploy-all.bat` to copy `Data` contents directly.
 
 `deploy-all.bat` and `deploy-ui.bat` prompt for your Fallout 4 install folder on first use (or when the saved path is missing). The choice is stored locally in `.fallout4-path` (gitignored). You can still pass a path on the command line:
 
@@ -88,13 +101,7 @@ deploy-all.bat "D:\SteamLibrary\steamapps\common\Fallout 4"
 deploy-ui.bat "D:\SteamLibrary\steamapps\common\Fallout 4\Data"
 ```
 
-`deploy-all.bat` installs:
-
-* `Data/F4SE/Plugins/PrismaUI_F4.dll`
-* `Data/F4SE/Plugins/CommonwealthOnline.dll`
-* `Data/PrismaUI_F4/libs/*.dll`
-* `Data/PrismaUI_F4/resources/*`
-* `Data/PrismaUI_F4/views/CommonwealthOnline/browser/index.html`
+`stage-mod.bat` assembles the same layout into `build/Fallout 4/Data` without touching the game install. `deploy-all.bat` runs staging first, then copies into `Data`.
 
 In-game controls: