fix: AI can now exec on Proxmox nodes (they have WolfStack agents)

Removed the node_type != "proxmox" filter from AI chat cluster_nodes,
so [EXEC_ALL] reaches ALL online nodes including Proxmox ones.
Updated system prompt to correctly state Proxmox nodes have agents
and can be targeted with commands.

Author: Paul C

src/ai/mod.rs

@@ -1384,15 +1384,15 @@ fn build_system_prompt(knowledge: &str, server_context: &str) -> String {
          - Keep commands simple and focused\n\
          - When showing results from [EXEC_ALL], clearly label which node each result came from\n\n\
          ## Cluster Topology\n\
-         - All WolfStack nodes are **equal peers** — do NOT label any node as 'main', 'primary', or 'secondary'\n\
-         - Each node runs whatever Wolf components it needs; not all nodes run the same services\n\
-         - Do NOT assume a service should be running on a node just because it runs on others\n\
-         - [EXEC_ALL] only targets WolfStack nodes, NOT Proxmox nodes\n\n\
+         - All nodes are **equal peers** — do NOT label any node as 'main', 'primary', or 'secondary'\n\
+         - Each node runs whatever components it needs; not all nodes run the same services\n\
+         - Some nodes also run Proxmox VE — they are full WolfStack nodes AND Proxmox hypervisors\n\
+         - [EXEC_ALL] targets ALL online nodes including Proxmox nodes (they all have WolfStack agents)\n\
+         - Do NOT assume a service should be running on a node just because it runs on others\n\n\
          ## Proxmox Nodes\n\
-         - Proxmox nodes are **monitored but not managed** — you can see their metrics, VM/CT counts, and status\n\
-         - You CANNOT execute commands on Proxmox nodes (they don't run WolfStack agents)\n\
-         - For Proxmox node issues (high CPU, high memory), use the metrics data provided below — you cannot SSH or exec into them\n\
-         - When a user asks about a Proxmox node, answer from the metrics/VM/CT data, and explain you cannot run commands on it\n\
+         - Proxmox nodes have WolfStack agents — you CAN execute commands on them via [EXEC_ALL]\n\
+         - They appear in both the WolfStack node list and as Proxmox hypervisors\n\
+         - Proxmox data (VM/CT counts, per-guest CPU) is shown in the server state below\n\
          - When reporting on the full infrastructure, include Proxmox node health data (CPU, RAM, disk)\n\n\
          ## Proposed Actions (Fix It)\n\
          When you identify a problem and know how to fix it, propose the fix using ACTION tags.\n\

src/api/mod.rs

@@ -5133,13 +5133,12 @@ pub async fn ai_chat(
     };
 
     // Build cluster node list for remote command execution
+    // Include ALL online nodes (including Proxmox nodes that have WolfStack agents)
     let cluster_nodes: Vec<(String, String, String, String)> = {
         let nodes = state.cluster.get_all_nodes();
         nodes.iter()
-            .filter(|n| !n.is_self && n.online && n.node_type != "proxmox")
+            .filter(|n| !n.is_self && n.online)
             .map(|n| {
-                // When TLS is enabled, main port serves HTTPS; inter-node HTTP is on port+1.
-                // Try port+1 first (works for HTTPS nodes), fall back to original port (HTTP-only).
                 let url1 = format!("http://{}:{}", n.address, n.port + 1);
                 let url2 = format!("http://{}:{}", n.address, n.port);
                 (n.id.clone(), n.hostname.clone(), url1, url2)