Agent update

docs/agents/WINDOWS_AGENT.md

@@ -43,6 +43,42 @@ The session naming scheme also follows the OGP convention:
 OGP_HOME_000000123
 ```
 
+### Windows Startup Launcher
+
+Relevant files:
+
+- `Agent-Windows/Install/agent_start.bat`
+- `Agent-Windows/Install/agent_start_cygwin.sh`
+- `/OGP/Cfg/bash_prefs.cfg` on an installed node
+
+The batch launcher must not assume that `bash` is in the Windows `PATH`. It explicitly checks:
+
+- the Cygwin root beside the launcher
+- `C:\cygwin64\bin\bash.exe`
+- `C:\cygwin\bin\bash.exe`
+
+The Cygwin-side helper performs the shell work:
+
+1. enter `/OGP`
+2. normalize CRLF to LF for `.pl`, `.pm`, `.sh`, and `.cfg` files under `/OGP`
+3. source `/OGP/Cfg/bash_prefs.cfg`
+4. optionally update only `Agent-Windows/ogp_agent.pl` from Forgejo when `agent_auto_update=1`
+5. backup the current `/OGP/ogp_agent.pl`
+6. validate the updated agent with `perl -c`
+7. restore the backup if validation fails
+8. launch `/OGP/ogp_agent.pl`
+
+Default optional update source:
+
+- repo: `http://forge.runlevelsystems.com/dev/GSP.git`
+- branch: `Panel-unstable`
+- source file: `Agent-Windows/ogp_agent.pl`
+- target file: `/OGP/ogp_agent.pl`
+
+Auto-update failure is non-fatal. Missing `git`, clone failure, missing source file, or failed validation should warn and continue with the current installed agent.
+
+The Windows agent file does not use `DBI` at startup. If a Windows node reports `Can't locate DBI.pm` at line 48, it is a strong signal that a Linux agent file was copied onto the Windows node.
+
 ## Status Logic
 
 Relevant functions:
@@ -61,6 +97,8 @@ The status model should check:
 
 The old `SERVER_STOPPED` file should not be the source of truth.
 
+If the game port is listening but the managed screen session is not found, the agent reports `ONLINE` with a warning. This protects customers from false offline/unknown states when a process survives a screen/session mismatch or an older agent cannot report the session correctly.
+
 ## Logging
 
 Relevant function:
@@ -91,4 +129,3 @@ The Windows scheduler implementation should remain aligned with the Linux schedu
 - Batch wrappers are often needed for Windows executables.
 - Process cleanup must avoid killing unrelated processes that happen to share an executable name.
 - The agent should continue to use `screen` where it already does so, to stay aligned with Linux behavior.
-