Offer Troubleshoot as a profile, and say plainly when it has no log

AI/README-AI.md

@@ -69,7 +69,7 @@ buries it. `--kind=readme` is the hard filter for that case:
 bash AI/ai_query.sh --kind=readme "what is Varaverk"
 ```
 
-`--kind` filters on where a chunk came from — `header`, `readme`, `manual`, `template`, `doc` —
+`--kind` filters on where a chunk came from — `header`, `readme`, `manual`, `template`, `doc`, `ui` —
 and composes with `--section`. Prefer it over `--section` for "what is" and "why does this
 exist" questions, where the answer is narrative rather than a header field.
 
@@ -109,6 +109,7 @@ Roughly 2,900 chunks across ~180 files:
 | `manual` | Every `Manual-*.md` |
 | `template` | `Deployment/*.template` — the versioned conf schema |
 | `doc` | Top-level `README.md`, `Manual.md`, design notes |
+| `ui` | `Plugin/unraid/pages/readme/*.md` — the WebGUI's own help panels |
 
 **Script bodies are not indexed.** Headers state intent, code states mechanism; for the
 questions this answers, intent retrieves better and costs far less.
@@ -239,7 +240,7 @@ dock.
 | `varaverk` | 3 | yes | answers only from the index, with citations. The default. |
 | `chat` | 8 | **no** | ordinary conversation. Holds zero capabilities, deliberately. |
 | `code` | 4 | no | drafts shell for Custom Scripts; scans its own output for destructive ops |
-| `troubleshoot` | 2 | yes | reasons from an open log first, docs second. May file bug reports. |
+| `troubleshoot` | 2 | yes | reasons from evidence — an open log, or one you name. May file bug reports. |
 
 Capabilities are granted per profile — retrieval, live health, run evidence, scoped log,
 incidents, conf lookup, bug filing, code scanning. `chat` holding an empty list is a guarantee,