Add an incident journal the troubleshooter reads back, and thinking for diagnosis

Plugin/unraid/Tools/ai_chat_worker.php

@@ -189,6 +189,20 @@ if ($profile === 'troubleshoot' && $scope !== '') {
     }
 }
 
+// What has gone wrong with this same thing before, and what actually fixed it. Operator-written,
+// so it outranks anything the model would infer from the log — it is the only input here that
+// records a confirmed outcome rather than a reading of evidence.
+if ($scope !== '') {
+    $past = vv_ai_incidents_for($scope, 4);
+    if ($past) {
+        $diagBlock .= "PREVIOUSLY ON THIS, WRITTEN BY THE OPERATOR AFTER IT WAS RESOLVED\n"
+                    . "Confirmed outcomes, not guesses. If the current symptom matches one of "
+                    . "these, say so and lead with it. If it clearly does not, ignore them "
+                    . "rather than forcing a fit.\n\n"
+                    . implode("\n", $past) . "\n\n";
+    }
+}
+
 // Where a named conf key really lives, resolved before the model sees the question. Deterministic
 // so the answer cannot be a guess: the operator may be certain a setting is in master.conf when
 // it is in the host conf, and the useful reply names the file and line rather than not finding it.