workshop fix 37

docs/features/WORKSHOP_SYSTEM.md

@@ -49,6 +49,8 @@ Current rule:
 - post-install scripts still run
 - `WorkshopModsInfo` still records installed items
 - uninstall can rely on `WorkshopModsInfo` when no config file is managed
+- installed-mod tracking is per home when the agent supports `get_workshop_mods_info(home_id)`
+- Workshop installs write `<game_home>/WorkshopInstallStatus.json` and terminal log markers so the Panel can clear stale Workshop update messages without hiding unrelated running updates
 
 This keeps advanced regex editing available without forcing it for simple Arma/DayZ-style `@mod` installs.
 

docs/modules/steam_workshop.md

@@ -57,6 +57,7 @@ Dedicated Steam Workshop support for game servers.
 
 - the main Workshop page `Back` link is rendered as a real panel button
 - uninstall remains in the dedicated `steam_workshop` module
+- the uninstall page is also the installed-mods view and shows tracked title, Workshop ID, installed folder/path, status, install time, and a copyable mod line
 
 ## Legacy RPC Behavior
 
@@ -65,6 +66,10 @@ Dedicated Steam Workshop support for game servers.
 - both agents skip the generated `cat` / regex / config-write block when `config_file_path` is blank
 - both agents still run custom post-install scripts and still write `WorkshopModsInfo`
 - uninstall falls back to `WorkshopModsInfo` when no config file is managed
+- new agents write per-home installed mod records under `WorkshopModsInfo/home_<home_id>/`
+- each installed record includes mod string, Workshop item ID, title, installed folder/path, Workshop App ID, status, and timestamps
+- agents also write `<game_home>/WorkshopInstallStatus.json` with `running`, `completed`, or `failed` Workshop install state
+- Workshop install logs end with `GSP_WORKSHOP_INSTALL_COMPLETE` or `GSP_WORKSHOP_INSTALL_FAILED`; the Panel uses these markers to avoid stale `Update in progress` displays when the generic update screen remains visible
 
 ## Security Concerns