Agent update

docs/features/STATUS_SYSTEM.md

@@ -29,6 +29,23 @@ Panel display mapping:
 
 LGSL/GameQ query failure is not enough to mark a server offline. Query success may add player/map/hostname metadata, but query failure should only show a small unavailable note when the agent says the server is otherwise active.
 
+Current repaired Panel flow:
+
+1. `Panel/modules/gamemanager/server_monitor.php` calls `get_agent_server_status`.
+2. `get_agent_server_status` first asks for structured `remote_server_status` data when available.
+3. If the structured response is missing or ambiguous, the Panel uses existing agent calls to check `is_screen_running`.
+4. The Panel also asks the agent to test the configured game port with `ss` or `netstat`.
+5. A confirmed managed session, process flag, or listening game port is enough to display `ONLINE`.
+6. `UNKNOWN` is reserved for an unavailable or inconclusive agent status check.
+
+The port fallback is deliberately cross-platform:
+
+- Linux normally uses `ss -lntu`, then `netstat`.
+- Cygwin/Windows normally uses `netstat -an`.
+- The Panel-side fallback parses complete command output instead of assuming the listening address is always in the same column.
+
+Agent behavior now treats a listening game port as `ONLINE` even if the managed screen/session cannot be found. The UI may still show the warning from `last_error`, but it must not show a false red/offline or gray/unknown state when the game port proves the server is running.
+
 ## Recommended State Model
 
 | State | Meaning |
@@ -50,6 +67,8 @@ The agent should check, in this order:
 4. optional query/RCON port listening
 5. optional query metadata
 
+The Panel fallback does not replace a full agent-owned status model. It exists so existing running servers do not show false unknown/offline when the structured status RPC is missing, partial, or query metadata fails.
+
 ## Known Problems To Remember
 
 - LGSL/GameQ may fail for supported games, blocked ports, or slow startups.