Let troubleshoot see the machine and answer with a route

It could describe a conf edit but not the switch that makes it, and knew
nothing about containers, pools or the array it was reasoning about.

Plugin/unraid/include/ai_profiles.php

@@ -113,7 +113,11 @@ const VV_AI_PROFILES_DEF = [
         'hint'  => 'Reasons from evidence — the log you have open, or one you name. Says so when there is none.',
         'turns' => 2,
         'ui'    => true,
-        'caps'  => ['retrieve', 'health', 'run_evidence', 'scoped_log', 'incidents', 'conf_lookup', 'file_bugs'],
+        // system_state is read-only and shared with repair. Both need to know a container is down
+        // or a pool is full to explain anything about this machine rather than about Unraid in
+        // general; neither gets a way to act on it, and only repair can change a setting.
+        'caps'  => ['retrieve', 'health', 'system_state', 'run_evidence', 'scoped_log',
+                    'incidents', 'conf_lookup', 'file_bugs'],
     ],
     // The only profile that may change a setting, and the only one not offered as a button.
     //
@@ -132,8 +136,8 @@ const VV_AI_PROFILES_DEF = [
         'hint'  => 'Works through a finding with you, and can apply a fix you approve.',
         'turns' => 3,
         'ui'    => false,
-        'caps'  => ['retrieve', 'health', 'run_evidence', 'scoped_log', 'incidents', 'conf_lookup',
-                    'conf_write', 'probe', 'file_findings', 'phrasebook', 'past_fixes'],
+        'caps'  => ['retrieve', 'health', 'system_state', 'run_evidence', 'scoped_log', 'incidents',
+                    'conf_lookup', 'conf_write', 'probe', 'file_findings', 'phrasebook', 'past_fixes'],
     ],
 ];
 
@@ -142,7 +146,8 @@ const VV_AI_PROFILES_DEF = [
 const VV_AI_CAP_MEANING = [
     'retrieve'     => 'retrieval passages from the documentation index',
     'kind_filter'  => 'the retrieval kind filter the page exposes',
-    'health'       => 'live health sweep measured at question time',
+    'health'       => 'live health sweep measured at question time — the AI subsystem only',
+    'system_state' => 'read-only view of the machine: hardware, containers, pools, array, UPS',
     'run_evidence' => 'run record and log tail for a script named in the question',
     'scoped_log'   => 'log tail for whatever the operator currently has open',
     'incidents'    => 'operator-written history of what previously went wrong with this thing',