Agent update

docs/modules/GAMEMANAGER.md

@@ -50,6 +50,8 @@ The current flow now points toward agent-truth status reporting via:
 - `remote_server_status`
 - `get_agent_server_status` in `home_handling_functions.php`
 - `server_status_without_decrypt` in both agents
+- fallback `is_screen_running` checks when structured status is unavailable or ambiguous
+- fallback agent-side `ss`/`netstat` port listening checks through `exec`
 
 Useful state labels:
 
@@ -62,6 +64,21 @@ Useful state labels:
 
 Query checks should remain optional metadata only.
 
+Current Panel fallback behavior:
+
+1. Try the structured `remote_server_status` response.
+2. Check the managed screen/session with `is_screen_running`.
+3. Check whether the configured game port is listening from the agent host using `ss` or `netstat`.
+4. Treat a confirmed session, process, or game port as `ONLINE`.
+5. Treat query failure as missing metadata only, not as offline or unknown.
+6. Show `UNKNOWN` only when the Panel cannot complete a reliable agent status check.
+
+Repair note:
+
+- `Panel/modules/gamemanager/home_handling_functions.php` contains the status fallback.
+- The port fallback intentionally parses full `ss`/`netstat` output instead of relying on one fixed field, because Cygwin and Linux output differ.
+- The Windows and Linux agents report `ONLINE` when the configured game port is listening even if the managed screen/session is missing, with a warning in `last_error`.
+
 ## Game Monitor Display Rules
 
 `Panel/modules/gamemanager/server_monitor.php` should display state from the agent status response, not from LGSL/GameQ query success alone.
@@ -85,7 +102,9 @@ Relevant files:
 
 The log view should be treated as live, AJAX-updated output rather than a full page reload workflow.
 
-`log.php` now renders the live log as a large monospace textarea with viewport-based height, preserved line breaks, vertical scrolling, and mobile sizing.
+`log.php` and `view_server_log.php` now render the live log as a dedicated `<pre id="live-server-log" class="gsp-live-log-panel">` block. They intentionally do not use the generic `log` class or a `textarea`, because theme styles can collapse textarea/log elements into one-line controls.
+
+The live panel uses viewport-based height, preserved line breaks, vertical scrolling, long-line overflow handling, and mobile sizing.
 
 ## What This Module Depends On
 

docs/modules/UPDATE.md

@@ -36,6 +36,12 @@ Defaults:
 - Panel Path: `/var/www/html/GSP/Panel`
 - Backup Before Update: enabled
 
+Important implementation note:
+
+- `gsp_update_settings()` and `gsp_validate_update_settings()` are defined at top level in `Panel/modules/administration/panel_update.php`.
+- These helpers must not be nested inside another function. A previous bad edit placed `gsp_update_settings()` inside `gsp_get_git_commit()`, which caused a fatal error when the update page called the helper before `gsp_get_git_commit()` had ever executed.
+- If the update page throws `Call to undefined function gsp_update_settings()`, first verify the deployed `Panel/modules/administration/panel_update.php` matches the repository version and that this helper exists near the top of the file before `gsp_panel_update_section()` is called.
+
 ## Update Flow
 
 1. Save or submit repository settings.
@@ -52,7 +58,7 @@ Defaults:
 
 Apache and SSL checks are diagnostics only. Missing SSL certificates do not block Panel updates.
 
-The old repeated SSL vhost disable buttons are not part of the primary update page. Apache path repair remains available under Advanced Diagnostics.
+The old repeated SSL vhost disable buttons are not part of the primary update page. Apache path repair remains available under Advanced Diagnostics, and SSL issues are shown as concise diagnostic warnings.
 
 ## Remaining Issues