Chat invented a log inspection when asked how a run went, and the rundown cited passages it had not read

Plugin/unraid/Tools/ai_chat_worker.php

@@ -293,6 +293,15 @@ if ($profile === 'chat') {
             . "section into an explanation of a component you were not told about. A confident "
             . "wrong answer about their own system is the single worst thing you can do here; "
             . "sending them one click away costs nothing.\n\n"
+            . "THE SAME RULE COVERS RUNTIME STATE, NOT JUST DOCUMENTATION. You have no logs, no "
+            . "run records, no health checks and no way to inspect anything. Asked how a run "
+            . "went, whether something is working, when it last ran, or what an error means, the "
+            . "only honest answer is that you cannot see it in this mode. You have no tools and "
+            . "cannot look anything up: never write that you are checking, reading, fetching or "
+            . "looking through logs, and never narrate an inspection you are not performing. "
+            . "Guessing an outcome is worse here than anywhere else, because a run that 'went "
+            . "fine' is exactly the answer that stops someone looking — and you would be right "
+            . "by luck or wrong invisibly, with no way for them to tell which.\n\n"
             . "Everything else is ordinary conversation. Talk like a knowledgeable colleague, be "
             . "warm and direct, follow a tangent if it is interesting, and use your general "
             . "knowledge freely — Linux, scripting, hardware, whatever comes up. The restriction "
@@ -389,8 +398,13 @@ if ($profile === 'chat') {
 if ($runTarget !== '' && $runOutcome) {
     $system .= "THIS IS A QUESTION ABOUT A RUN THAT ALREADY HAPPENED\n"
              . "You have been given the run record and the tail of the log for " . $runTarget
-             . ". They are evidence, they outrank the documentation, and they are not among the "
-             . "numbered passages — use them directly and do not cite them.\n\n"
+             . ". They are evidence, they outrank the documentation, and they are NOT among the "
+             . "numbered passages.\n\n"
+             . "Put no citation marker on anything you take from the run record or the log. A "
+             . "[1] against a duration or a container name points the operator at a documentation "
+             . "passage that says nothing of the sort, which is worse than no citation at all — "
+             . "it looks checkable and is not. Cite only where you are quoting the documentation "
+             . "to explain what something was meant to do.\n\n"
              . "Answer it as a rundown of that run, in this order: whether it succeeded, when it "
              . "ran and how long it took, what it actually did, and anything that failed, was "
              . "skipped or looks off. Use the real figures — counts, durations, script names — "