fixed installer

docs/AGENT_ACTIVITY_EVENTS.md

@@ -4,7 +4,7 @@ The Linux agent can report meaningful server lifecycle events to the GSP Panel a
 
 ## Configuration
 
-Set these values in `Cfg/Config.pm`:
+Set these values in `Cfg/Config.pm` under the selected install directory:
 
 ```perl
 agent_event_url => 'https://panel.example.com/agent_event_receiver.php',
@@ -13,6 +13,12 @@ remote_server_id => '1',
 
 If `agent_event_url` is empty, the agent attempts to derive it from `web_api_url`. The `key` value must match the Panel remote server encryption key because it is used to sign event payloads.
 
+Default new install path:
+
+```text
+/home/gameserver/GSP/Cfg/Config.pm
+```
+
 ## Authentication
 
 Events are JSON POST requests signed with HMAC-SHA256:

docs/PANEL_INTEGRATION.md

@@ -4,6 +4,17 @@ Workspace reference: [`GSP-WORKSPACE.md`](../../GSP-WORKSPACE.md)
 
 The Panel is authoritative. The Linux agent executes the work the Panel requests.
 
+## Current Install And Config Defaults
+
+New Linux installs default to:
+
+- agent root: `/home/gameserver/GSP`
+- run script: `gsp_agent_run`
+- service: `gsp_agent.service`
+- log file: `/home/gameserver/GSP/gsp_agent.log`
+
+Legacy names such as `ogp_agent_run` remain wrappers or protocol compatibility details only.
+
 ## Legacy Workshop RPC
 
 The dedicated Panel `steam_workshop` module still uses the legacy `steam_workshop` XML-RPC call.
@@ -17,3 +28,14 @@ Current compatibility rule:
 - each record stores mod string, Workshop item ID, title, installed folder/path, Workshop App ID, install status, and timestamps
 - the generated job writes `<game_home>/WorkshopInstallStatus.json` as `running`, `completed`, or `failed`
 - the generated job prints `GSP_WORKSHOP_INSTALL_COMPLETE` or `GSP_WORKSHOP_INSTALL_FAILED` so the Panel can avoid stale `Update in progress` displays if the generic update screen lingers
+
+## Server Content Hook Runtime
+
+The Linux agent prepares this runtime layout for generated content hooks:
+
+- `_gsp_content/hooks/`
+- `_gsp_content/generated/`
+- `_gsp_content/runtime/`
+- `_gsp_content/runtime/server_content.pids`
+
+During stop/restart, hook watchdog PIDs are cleaned up before hook application PIDs. Main game server watchdog PIDs should not be written to `server_content.pids`.