Session log: GuruRMM audit, installer system, infrastructure fixes

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

projects/gururmm-agent/TESTING_AND_DEPLOYMENT.md

@@ -8,6 +8,9 @@ This guide covers testing and deployment of the Claude Code integration for the
 
 ## Prerequisites
 
+**Source Repo:** `azcomputerguru/gururmm` on git.azcomputerguru.com (active development, 53+ commits).
+Note: A `guru-rmm` repo also exists but is a restructured copy with only 2 commits -- use `gururmm` as the primary reference.
+
 ### On Development Machine
 - Rust toolchain (1.70+)
 - cargo installed
@@ -69,6 +72,14 @@ cargo fmt -- --check
 
 ## Integration Testing (On AD2 Server)
 
+> **Note:** `claude_task` is a NEW command type added by this integration. The existing
+> GuruRMM command types are: `shell`, `powershell`, `python`, `script`.
+>
+> **How commands reach the agent:** The curl commands below create the command on the
+> server via the REST API (`POST /api/agents/:id/command`). The server then delivers the
+> command to the connected agent over WebSocket (ServerMessage::Command). The agent does
+> NOT poll for commands via REST.
+
 ### Test 1: Simple Task Execution
 
 **Test Command via GuruRMM API:**
@@ -476,7 +487,7 @@ Monitor Claude task execution metrics:
 
 ```powershell
 # Query GuruRMM API for task statistics
-curl "http://172.16.3.30:3001/api/agents/{AD2_AGENT_ID}/stats"
+curl "http://172.16.3.30:3001/api/agents/stats"
 ```
 
 **Key metrics to watch:**
@@ -558,7 +569,7 @@ Prevents abuse:
 
 For issues or questions:
 1. Check agent logs: `C:\Program Files\GuruRMM\logs\agent.log`
-2. Check GuruRMM server logs: `http://172.16.3.30:3001/logs`
+2. Check GuruRMM server logs on disk (no `/logs` HTTP endpoint exists)
 3. Review this documentation
 4. Contact GuruRMM support team